Startup classes arguments

In weblogic 5.0, I can specify the arguments for my startup classes. I tried
to specify the arguments in WebLogic 6.0 through the console. However, the
arguments field has a length limitation which I can not type in all of the
arguments I would like to pass.
Any suggestions?
Thx,
Zhiyong

If you put it manually in the config.xml file for the domain in question -
and don't edit the startup parms through the console - does the console
corrupt it by only saving what the console's edit saves?
"Zhiyong Li" <[email protected]> wrote in message
news:3a5ce2a9$[email protected]..
In weblogic 5.0, I can specify the arguments for my startup classes. Itried
to specify the arguments in WebLogic 6.0 through the console. However, the
arguments field has a length limitation which I can not type in all of the
arguments I would like to pass.
Any suggestions?
Thx,
Zhiyong

Similar Messages

Probelems with MDB listening to MQ (Startup class issue )

Hello ,
          I am supposed to write a Message driven bean that would reside on
          Weblogic7.0 and listen to a particular queue of IBM MQ.
          I understand that we need to write a Start-up class for this. I have
          written the start-up class but I am getting the following error:
          <Apr 16, 2003 3:17:14 PM EDT> <Warning> <EJB> <010061> <The
          Message-Driven EJB: SimpleMDB is unable
          to connect to the JMS destination: ivtQ. The EJB container will
          automatically attempt to re-establis
          h the connection with the JMS server. This warning may occur during
          WebLogic Cluster start-up if the
          JMS destination is located on another server. When the JMS server
          connection is re-established, the
          Message-Driven EJB will again receive JMS messages.
          The Error was:
          The JMS destination with the JNDI name: ivtQ could not be found.
          Please ensure that the JNDI name in
          the weblogic-ejb-jar.xml is correct, and the JMS destination has been
          deployed.>
          I understand that there are some configuration issues:
          Can you please guide where am I going wrong:
          1.     What should be the value of the <destination-jndi-name> in the
          Weblogic-ejb-jar. I have not passed any Queue name through the
          start-up class …Is it ok?
          2.     Then what queue name should I specify. (ofcousrse it should be the
          MQ queue name but do I need to add that in the JNDI or in the
          weblogic console…?
          3.     Please confirm that the <connection-factory-jndi-name> mentioned in
          the weblogic-ejb-jar.xml should be the same as what I am passing as
          JNDIName (through weblogic console).
          4.     Kindly advice if I am missing anything (especially in my start-ip
          class)
          Here are my Deployemnt descriptors:
          weblogic-ejb-jar
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic
          7.0.0 EJB//EN" "http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd">
          <weblogic-ejb-jar>
               <weblogic-enterprise-bean>
                    <ejb-name>SimpleMDB</ejb-name>
                    <message-driven-descriptor>
                         <pool>
                              <max-beans-in-free-pool>8</max-beans-in-free-pool>
                              <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
                         </pool>
                         <destination-jndi-name>ivtQ</destination-jndi-name>
                         <initial-context-factory>
          com.sun.jndi.fscontext.RefFSContextFactory
          </initial-context-factory>
                         <provider-url>
          file:/D:/JNDI/
          </provider-url>
                         <connection-factory-jndi-name>
          MyQCF
          </connection-factory-jndi-name>
                    </message-driven-descriptor>
               </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ejb-jar.xml
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
          JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
          <ejb-jar>
               <enterprise-beans>
                    <message-driven>
                         <ejb-name>SimpleMDB</ejb-name>
                         <ejb-class>weblogic.jms.whitepaper.SimpleMDB</ejb-class>
                         <transaction-type>Container</transaction-type>
                         <message-driven-destination>
                              
                              <destination-type>javax.jms.Queue</destination-type>
                         </message-driven-destination>
                    </message-driven>
               </enterprise-beans>
               <assembly-descriptor>
                    <container-transaction>
                         <method>
                              <ejb-name>SimpleMDB</ejb-name>
                              <method-name>*</method-name>
                         </method>
                         <trans-attribute>Required</trans-attribute>
                    </container-transaction>
               </assembly-descriptor>
          </ejb-jar>
          My Start-up class is as follows:
          import com.ibm.mq.jms.*;
          import java.util.*;
          import javax.jms.*;
          import javax.naming.*;
          import weblogic.common.*;
          public class MQJMSStartup implements T3StartupDef
               /** * The name of the queue manager to connect to. The startup class
          * will throw an exception if this parameter is not set. */
               public final static String QM_NAME_PROPERTY = "QManager";
               /** * The host name where the queue manager runs. If not set, the *
          startup class will create a "bindings mode" connection to a * queue
          manager on the local host. */
               public final static String QM_HOST_PROPERTY = "QManagerHost";
               /** * The port number where the queue manager listens. If not set,
          this * defaults to 1414, the default MQSeries port */
               public final static String QM_PORT_PROPERTY = "QManagerPort";
               /** * The name in JNDI to store this queue manager object under. * If
          not set, the startup class will throw an exception. */
               public static final String JNDI_NAME_PROPERTY = "JNDIName";
               // Required
               public MQJMSStartup()
               // Required, but not needed
               public void setServices(T3ServicesDef services)
                    public String startup(String name, Hashtable args) throws Exception
                    String qmName = (String)args.get(QM_NAME_PROPERTY);
                    System.out.println("*****The qmName is "+qmName);
                    if (qmName == null)
                         throw new Exception("Startup parameter " + QM_NAME_PROPERTY + "
          must be set");
                    String jndiName = (String)args.get(JNDI_NAME_PROPERTY);
                    System.out.println("***The JNDI Nname is "+jndiName);
                    if (jndiName == null)
                         throw new Exception("Startup parameter " + JNDI_NAME_PROPERTY + "
          must be set");
                    String qmHost = (String)args.get(QM_HOST_PROPERTY);
                    System.out.println("*****The qmHost is "+qmHost);
                    String qmPort = (String)args.get(QM_PORT_PROPERTY);
                    System.out.println("*****The qmPort is "+qmPort);
                    MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
                    factory.setQueueManager(qmName);
                    if (qmHost == null)
                         factory.setTransportType(JMSC.MQJMS_TP_BINDINGS_MQ);
                         factory.setHostName(qmHost);
                         if (qmPort != null)
                              try
                                   int portNum = Integer.parseInt(qmPort);
                                   factory.setPort(portNum);
                              catch (NumberFormatException ignore)
                    else
                         factory.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);
                    InitialContext context = new InitialContext();
                    context.bind(jndiName, factory);
                    context.close();
                    StringBuffer buf = new StringBuffer();
                    buf.append( "A connection factory was created for the MQ Queue
          Manager ");
                    buf.append(qmName);
                    buf.append(" and stored in JNDI at ");
                    buf.append(jndiName);
                    System.out.println("*****The mqstartup is executed
          succesfully"+buf.toString());
                    return buf.toString();
          The args that I pass through the weblogic console is as follows:
          QManager=QM_mphasis_eight, JNDIName=MyQCF
          Please advice,
          regards,
          Milan Doshi


Thanks for the response.
          I have written the startUp class but I am getting the following error:
          The Error was:
          The JMS destination with the JNDI name: MySenderQueue could not be
          found. Please ensure that the
          JNDI name in the weblogic-ejb-jar.xml is correct, and the JMS
          destination has been deployed.>
          =====
          My startup class is as follows:
          String qmPort = (String)args.get(QM_PORT_PROPERTY);
          String qmHost = (String)args.get(QM_HOST_PROPERTY);
          String qmName = (String)args.get(QM_NAME_PROPERTY);
          MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          factory.setQueueManager(qmName);
          factory.setHostName(qmHost);
          if (qmPort != null)
          try
          int portNum = Integer.parseInt(qmPort);
          factory.setPort(portNum);
          catch (NumberFormatException ignore)
          if (qmHost == null)
          factory.setTransportType(JMSC.MQJMS_TP_BINDINGS_MQ);
          else
          factory.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);
          InitialContext context = new InitialContext();
          context.bind(jndiName, factory);
          QueueConnection connection = factory.createQueueConnection();
          boolean transacted = false;
          QueueSession session = connection.createQueueSession( transacted,
          Session.AUTO_ACKNOWLEDGE);
          Queue ioQueue = session.createQueue("MySenderQueue");
          context.bind("MySenderQueue",ioQueue);
          context.close();
          ===================================================
          My Weblogic-ejb-jar.xml is like this:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>SimpleMDB</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>8</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>MySenderQueue</destination-jndi-name>
          <connection-factory-jndi-name>
          MyQCF
          </connection-factory-jndi-name>
          </message-driven-descriptor>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ======================================================
          Can you please guide me what is wrong in registering the Queue?
          Thanks once again for the response,
          Milan Doshi
          "sudhir" <[email protected]> wrote in message news:<[email protected]>...
          > Mian,
          >
          > You should pass the Queue Name in the startup class arguments. This would be
          > the same name as the MQ Queue you have defined. There is no need to specify to
          > provider URL to the file ... If you do, then ensure that the the queue name should
          > refer to the MQ Administered Queue object defined by jmsadmin.
          >
          > -Sudhir
          >
          >
          >
          > [email protected] (Milan Doshi) wrote:
          > >Hello ,
          > >
          > >I am supposed to write a Message driven bean that would reside on
          > >Weblogic7.0 and listen to a particular queue of IBM MQ.
          > >
          > >I understand that we need to write a Start-up class for this. I have
          > >written the start-up class but I am getting the following error:
          > >
          > ><Apr 16, 2003 3:17:14 PM EDT> <Warning> <EJB> <010061> <The
          > >Message-Driven EJB: SimpleMDB is unable
          > >to connect to the JMS destination: ivtQ. The EJB container will
          > >automatically attempt to re-establis
          > >h the connection with the JMS server. This warning may occur during
          > >WebLogic Cluster start-up if the
          > > JMS destination is located on another server. When the JMS server
          > >connection is re-established, the
          > > Message-Driven EJB will again receive JMS messages.
          > >The Error was:
          > >The JMS destination with the JNDI name: ivtQ could not be found.
          > >Please ensure that the JNDI name in
          > > the weblogic-ejb-jar.xml is correct, and the JMS destination has been
          > >deployed.>
          > >
          > >I understand that there are some configuration issues:
          > >
          > >Can you please guide where am I going wrong:
          > >1.     What should be the value of the <destination-jndi-name> in the
          > >Weblogic-ejb-jar. I have not passed any Queue name through the
          > >start-up class ?Is it ok?
          > >2.     Then what queue name should I specify. (ofcousrse it should be the
          > >weblogic console??
          > >3.     Please confirm that the <connection-factory-jndi-name> mentioned in
          > >the weblogic-ejb-jar.xml should be the same as what I am passing as
          > >JNDIName (through weblogic console).
          > >4.     Kindly advice if I am missing anything (especially in my start-ip
          > >class)
          > >
          > >Here are my Deployemnt descriptors:
          > >
          > >weblogic-ejb-jar
          > >
          > ><?xml version="1.0"?>
          > ><!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic
          > >7.0.0 EJB//EN" "http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd">
          > ><weblogic-ejb-jar>
          > >     <weblogic-enterprise-bean>
          > >          <ejb-name>SimpleMDB</ejb-name>
          > >          <message-driven-descriptor>
          > >               <pool>
          > >                    <max-beans-in-free-pool>8</max-beans-in-free-pool>
          > >                    <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          > >               </pool>
          > >               <destination-jndi-name>ivtQ</destination-jndi-name>
          > >               <initial-context-factory>
          > > com.sun.jndi.fscontext.RefFSContextFactory
          > > </initial-context-factory>
          > >               <provider-url>
          > > file:/D:/JNDI/
          > > </provider-url>
          > >               <connection-factory-jndi-name>
          > > MyQCF
          > > </connection-factory-jndi-name>
          > >          </message-driven-descriptor>
          > >     </weblogic-enterprise-bean>
          > ></weblogic-ejb-jar>
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >ejb-jar.xml
          > >
          > ><?xml version="1.0"?>
          > ><!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
          > >JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
          > ><ejb-jar>
          > >     <enterprise-beans>
          > >          <message-driven>
          > >               <ejb-name>SimpleMDB</ejb-name>
          > >               <ejb-class>weblogic.jms.whitepaper.SimpleMDB</ejb-class>
          > >               <transaction-type>Container</transaction-type>
          > >               <message-driven-destination>
          > >                    
          > >                    <destination-type>javax.jms.Queue</destination-type>
          > >               </message-driven-destination>
          > >          </message-driven>
          > >     </enterprise-beans>
          > >     <assembly-descriptor>
          > >          <container-transaction>
          > >               <method>
          > >                    <ejb-name>SimpleMDB</ejb-name>
          > >                    <method-name>*</method-name>
          > >               </method>
          > >               <trans-attribute>Required</trans-attribute>
          > >          </container-transaction>
          > >     </assembly-descriptor>
          > ></ejb-jar>
          > >
          > >
          > >My Start-up class is as follows:
          > >
          > >import com.ibm.mq.jms.*;
          > >import java.util.*;
          > >import javax.jms.*;
          > >import javax.naming.*;
          > >import weblogic.common.*;
          > >
          > >
          > >public class MQJMSStartup implements T3StartupDef
          > >{
          > >     /** * The name of the queue manager to connect to. The startup class
          > >* will throw an exception if this parameter is not set. */
          > >     public final static String QM_NAME_PROPERTY = "QManager";
          > >
          > >     /** * The host name where the queue manager runs. If not set, the *
          > >startup class will create a "bindings mode" connection to a * queue
          > >manager on the local host. */
          > >     public final static String QM_HOST_PROPERTY = "QManagerHost";
          > >
          > >     /** * The port number where the queue manager listens. If not set,
          > >this * defaults to 1414, the default MQSeries port */
          > >     public final static String QM_PORT_PROPERTY = "QManagerPort";
          > >
          > >     /** * The name in JNDI to store this queue manager object under. * If
          > >not set, the startup class will throw an exception. */
          > >     public static final String JNDI_NAME_PROPERTY = "JNDIName";
          > >
          > >     // Required
          > >     public MQJMSStartup()
          > >     {
          > >     }
          > >
          > >     // Required, but not needed
          > >     public void setServices(T3ServicesDef services)
          > >     {
          > >     }
          > >
          > >          public String startup(String name, Hashtable args) throws Exception
          > >     {
          > >          String qmName = (String)args.get(QM_NAME_PROPERTY);
          > >          System.out.println("*****The qmName is "+qmName);
          > >          if (qmName == null)
          > >          {
          > >               throw new Exception("Startup parameter " + QM_NAME_PROPERTY + "
          > >must be set");
          > >          }
          > >          String jndiName = (String)args.get(JNDI_NAME_PROPERTY);
          > >          System.out.println("***The JNDI Nname is "+jndiName);
          > >          if (jndiName == null)
          > >          {
          > >               throw new Exception("Startup parameter " + JNDI_NAME_PROPERTY + "
          > >must be set");
          > >          }
          > >          String qmHost = (String)args.get(QM_HOST_PROPERTY);
          > >          System.out.println("*****The qmHost is "+qmHost);
          > >          String qmPort = (String)args.get(QM_PORT_PROPERTY);
          > >          System.out.println("*****The qmPort is "+qmPort);
          > >          MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          > >          factory.setQueueManager(qmName);
          > >          if (qmHost == null)
          > >          {
          > >               factory.setTransportType(JMSC.MQJMS_TP_BINDINGS_MQ);
          > >               factory.setHostName(qmHost);
          > >               if (qmPort != null)
          > >               {
          > >                    try
          > >                    {
          > >                         int portNum = Integer.parseInt(qmPort);
          > >                         factory.setPort(portNum);
          > >                    }
          > >                    catch (NumberFormatException ignore)
          > >                    {
          > >
          > >                    }
          > >               }
          > >          }
          > >          else
          > >          {
          > >               factory.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);
          > >          }
          > >
          > >          InitialContext context = new InitialContext();
          > >          context.bind(jndiName, factory);
          > >          context.close();
          > >          StringBuffer buf = new StringBuffer();
          > >          buf.append( "A connection factory was created for the MQ Queue
          > >Manager ");
          > >          buf.append(qmName);
          > >          buf.append(" and stored in JNDI at ");
          > >          buf.append(jndiName);
          > >          System.out.println("*****The mqstartup is executed
          > >succesfully"+buf.toString());
          > >          return buf.toString();
          > >     }
          > >}
          > >
          > >
          > >
          > >
          > >The args that I pass through the weblogic console is as follows:
          > >
          > >QManager=QM_mphasis_eight, JNDIName=MyQCF
          > >
          > >
          > >
          > >
          > >
          > >Please advice,
          > >
          > >regards,
          > >
          > >Milan Doshi

Startup Classes w/ Arguments and Startup Order

Hi,
I know we can control the order of startup classes by specifying them in a
comma delimited list like this:
weblogic.system.startupClass.a=class1,class2,class3
Now what if class1 and class2 have several startup arguments that I need to
pass??? I would hate to think that I'll have to write my own startup
manager just to do this one simple thing?
So... if anyone knows how to specify startup arguments AND control the order
of startup classes please let me know...
Thanks in advance,
Stephen Earl
SmartPoint, Inc.

Hi Don,
I've attempted to mirror the functionality of the Weblogic startup system
with no success. Basically I have an xml document specifying the startup
specifications much like the WL startup system (ie. Description, ClassName,
Args). To mirror the WL system I apparently need access to StartupThread
which, like most other WL classes, is undocumented and unexposed for use.
How would you suggest implementing such functionality??? Considering that
I'd like to have similar functionality to the current system (ie.
T3StartupDefs, RMI Servers, etc.) how can I and any other BEA customer
achieve this short of rewriting the startup mechanism???
Stephen Earl
SmartPoint, Inc.
"Don Ferguson" <[email protected]> wrote in message
news:[email protected]...
I have looked over the source code for startup classes and how thearguments
are processed, and I'm afraid I don't see any mechanism to accomplish what
you want, i.e., to specify the order that startup classes are executed,
and provide names-value pairs that are associated with each class.
You might have to come up with your own mechanism for associating
arguments with startup classes.
Anne-Katrin Schroeder-Lanz wrote:
well, if you absolutely must have identically named args for each class,
then you're stumped. should you be able to extract any kind of support
from
BEA here, I'd appreciate a notification, since we've got the sameproblem to
deal with.
happy hacking, anne
Anne-Katrin Schroeder-Lanz
Development
memIQ AG
T: +49-89-45639-19385
F: +49-89-45639-33-385
mailto:[email protected]
"Stephen Earl" <[email protected]> wrote in message
news:[email protected]...
OK... and now say that I have a startup argument called RETRIES. This
argument needs to be 10 for startup class A and 20 for startup class
B.
Now
way I can see to handle this situation.
BEA... I've logged a production 3 case regarding this issue and have
not
even received an initial response from support. Hello... Hello...
Steve...
"Anne-Katrin Schroeder-Lanz" <[email protected]> wrote in message
news:[email protected]...
hi,
just use the startArgs as documented on the list of startup classes
and
pass
a collective list of args, e.g.:
weblogic.system.startupClass.<logical_name>= xxx.yyy.Foo,
xxx.yyy.Bar
weblogic.system.startupArgs.<logical_name>= arg4Foo=some_value,
arg4Bar=another_value
hth,
cheers, anne
Anne-Katrin Schroeder-Lanz
Development
memIQ AG
T: +49-89-45639-19385
F: +49-89-45639-33-385
mailto:[email protected]
"Stephen Earl" <[email protected]> wrote in message
news:[email protected]...
Hi,
I know we can control the order of startup classes by specifying
them
in
a
comma delimited list like this:
weblogic.system.startupClass.a=class1,class2,class3
Now what if class1 and class2 have several startup arguments that
I
need
to
pass??? I would hate to think that I'll have to write my own
startup
manager just to do this one simple thing?
So... if anyone knows how to specify startup arguments AND controlthe
order
of startup classes please let me know...
Thanks in advance,
Stephen Earl
SmartPoint, Inc.

Startup class cannot find a config file.

I have written a startup class to configure log4j in Weblogic.
The class runs but cannot find the configuration file. The
code for the startup class is as follows....
package com.n2bb.ams.common.util;
import java.io.FileInputStream;
import java.io.File;
import java.io.IOException;
import java.net.URL;
import java.util.Properties;
import com.n2bb.ams.common.util.FileLocator;
import org.apache.log4j.xml.DOMConfigurator;
* Insert the type's description here.
* Creation date: (12/5/00 11:12:13 AM)
* @author: Administrator
public class ApplicationStartUp implements weblogic.common.T3StartupDef {
     * ApplicationStartUp constructor comment.
     public ApplicationStartUp() {
          super();
     * setServices method comment.
     public void setServices(weblogic.common.T3ServicesDef arg1) {
     * startup method comment.
     public String startup(String arg1, java.util.Hashtable arg2) throws Exception {
          String resource = null;
          try {
               resource = (String) arg2.get("configFileName");
               System.out.println("ConfigFileName: " + resource);
               URL configFileResource = ApplicationStartUp.class.getResource(resource);
               System.out.println("configFileResource: " + configFileResource.toString());
               String file = configFileResource.getFile();
               DOMConfigurator.configure(file);
               return "Log4j configuration initialized completed.";
          } catch (Exception e) {
               System.out.println("Cannot open config file: " + resource);
               return "Log4j configuration failed to initialized.";
The section of the config.xml the calls my startup class looks
like....
<StartupClass
Arguments="configFileName=/bea/user_projects/mydomain/log4j-config.xml"
ClassName="com.n2bb.ams.common.util.ApplicationStartUp"
Name="AMS Startup Class" Targets="myserver"/>
I have tested the code in a standalone class and it works fine.
Why can't I find the log4j-config.xml file? Any help would be
greatly appreciated.

Wow, your system must have a long history of having picked up assorted bad stuff ...
You have CleanMyMac2, which should definitely be removed.
You have other stuff (MacCleanse, for example) that I don't have first-hand knowledge about but should very likely be removed.
You are using Google Chrome which is a resource hog.
Further, your Adobe Flash player is not current.
If I had all these issues, I would do a clean install of Yosemite and only reintroduce the essential stuff.
You can search for the .plist files by opening finder, holding down the Option key, and doing Go > Library from Finder's menu and then searching for the file(s).

JNDI from Startup class

I'm having a problem when I do a JNDI lookup for JMS connection factory from startup
class. I can use JNDI normally to bind and lookup but when I do lookup for JMS
connection factory like this:
Context naming = new InitialContext();
factory = (TopicConnectionFactory)naming.lookup("myapp.factory");
It fails like this:
java.lang.NullPointerException:
at javax.naming.InitialContext.getURLScheme (InitialContext.java:222)
at javax.naming.InitialContext.getURLOrDefaultInitCtx (InitialContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:345)
The same lookup is successful when I do it from EJB or from client. What could
be the problem?

Sorry, my fault. I double checked and triple checked the code before posting, but
I should have quadruple checked it. NullPointerException was propably caused by
calling lookup() with null argument :)

Startup classes in WL6.0

Hi everybody,
Is the use of T3StartupDef interface deprecated in
weblogic 6.0 for writing startup classes? If yes how do I write startup classes?
Thanx,
Sunil

One feature of WebLogic startup classes is that you do not have to implement
T3StartupDef - if you class has static void main(String[] args) it will be
invoked.
Also, note that startup classes have to be in the system classpath, which
creates problems when they need to use application classes.
Sunil Naik <[email protected]> wrote:
Hi William,
Thanx for the explanation.I assume that use of T3StartupDef is not
deprecated and I'll go ahead with it.
thanx,
Sunil
"William Stewart" <[email protected]> wrote:
Startup classes using the T3StartupDef interface do work in WebLogic
6.0 - I am
just now porting a project from WL 4.5 to WL 6.0 and got it to work okay,
but
with these caveats:
(1) BEA's Javadoc documentation on the T3StartupDef interface is outdated
- it
mentions 'weblogic.properties', which no longer exists in WL 6.0 (replaced
by
config.xml and the Web-based Admin console).
(2) BEA's documentation for configuring startup classes in the Admin
console is
poor - for the 'Arguments' attribute, it doesn't specify how to format
arguments
for the startup class - you separate them with a comma like this:
ARG1=value1,ARG2=value2
(3) There is no documentation on how to write a Startup class in the
programming
section of BEA's documentation. It's very simple though; here is what
you do:
(a) Write a class that implements T3StartupDef.
(b) Give it a default, do-nothing constructor.
(c) Provide the interface's #setServices(T3ServicesDef) method - just
save the
parm in a field or something.
(d) Provide the interface's #startup(String, Hashtable) method - the
Hashtable
contains your arguments (set in the Admin console) and this is where
you put your
desired startup code.
"Sunil Naik" <[email protected]> wrote:
Hi everybody,
Is the use of T3StartupDef interface deprecated in
weblogic 6.0 for writing startup classes? If yes how do I write startup
classes?
Thanx,
Sunil
Dimitri

Weblogic6.0 Startup Classes!

Hi there!
I'm new in testing WLS6.0, and I'd like to know where should I put my
startup classes.
I mean in what place of the directory structure.
Thanks to BEA to change the functionallity of WLS. I'm thinking I will need
a traning course again.!
I've been testing the new release and is very nice but it changes a lot.
Thanks&Regards

I would also like to know; 5.1 had the classes in 'myserver\serverclasses',
where is it registered in 6.0?
When we migrated, our startup class was put in the domain's config.xml, as
follows:
<StartupClass Arguments="testFlag=Y" ClassName="OurStartup"
Name="OurStartup" Targets="myserver" />
Should the location be relative to the 'myserver' directory, or to the WL
home, or to the domain, or to a particular application?
"Mauricio Del Moral" <[email protected]> wrote in message
news:[email protected]..
Hi there!
I'm new in testing WLS6.0, and I'd like to know where should I put my
startup classes.
I mean in what place of the directory structure.
Thanks to BEA to change the functionallity of WLS. I'm thinking I willneed
a traning course again.!
I've been testing the new release and is very nice but it changes a lot.
Thanks&Regards

Cannot start Startup class in WL6.0

Hi, I have a question regarding the startup class with WL6.0. here is the config.xml:
=================================================================
<StartupClass
Arguments="connectionFactory=javax.jms.QueueConnectionFactory,queue=com.lasso.email.emailQueue"
ClassName="com.lasso.service.mail.StartupEmailSender"
FailureIsFatal="true" Name="EmailSender" Targets="localserver"/>
<StartupClass Arguments="" ClassName="com.lasso.util.StartupLoad"
FailureIsFatal="true" Name="StartupLoad1" Targets="localserver"/>
<Security Name="lassov2" PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
================================================================
Here is what I got after start weblogic server 6.0:
================================================================
<Jul 9, 2001 1:50:35 PM CDT> <Notice> <WebLogicServer> <WebLogic Server started>
<Jul 9, 2001 1:50:35 PM CDT> <Notice> <WebLogicServer> <ListenThread listening
o
n port 80>
<Jul 9, 2001 1:50:35 PM CDT> <Notice> <WebLogicServer> <SSLListenThread listenin
g on port 443>
<Jul 9, 2001 1:50:35 PM CDT> <Error> <Performance Pack> <Unable to load performa
nce pack, using Java I/O.
java.lang.ThreadDeath
>
<Jul 9, 2001 1:50:36 PM CDT> <Emergency> <WebLogicServer> <ListenThread.run()
fa
iled: java.lang.ThreadDeath>
<Jul 9, 2001 1:50:36 PM CDT> <Emergency> <WebLogicServer> <The WebLogic Server
i
s no longer listening for connections. You should probably restart it.>
<Jul 9, 2001 1:50:36 PM CDT> <Alert> <WebLogicServer> <Server shutdown has been
requested by system>
<Jul 9, 2001 1:50:36 PM CDT> <Alert> <WebLogicServer> <The shutdown sequence has
been initiated.>
<Jul 9, 2001 1:50:58 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
: '0' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
: '1' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
: '2' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
: '3' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
: '4' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
: '5' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread: 'ExecuteThread
==============================================================
What can I do to start those StartUp classes successfully?
Thanks.
Alan Zhang

Seems like your startup class is generating error that causing wl to
shutdown. This is because you told wls that you don't want it to start if
your startup class fails (FailureIsFatal="true" ).
Take a look at your startup calss and see why is it failing...
.raja
"Alan Zhang" <[email protected]> wrote in message
news:[email protected]...
>
Hi, I have a question regarding the startup class with WL6.0. here is theconfig.xml:
=================================================================
<StartupClass
Arguments="connectionFactory=javax.jms.QueueConnectionFactory,queue=com.lass
o.email.emailQueue"
ClassName="com.lasso.service.mail.StartupEmailSender"
FailureIsFatal="true" Name="EmailSender" Targets="localserver"/>
<StartupClass Arguments="" ClassName="com.lasso.util.StartupLoad"
FailureIsFatal="true" Name="StartupLoad1" Targets="localserver"/>
<Security Name="lassov2" PasswordPolicy="wl_default_password_policy"Realm="wl_default_realm"/>
================================================================
Here is what I got after start weblogic server 6.0:
================================================================
<Jul 9, 2001 1:50:35 PM CDT> <Notice> <WebLogicServer> <WebLogic Serverstarted>
>
<Jul 9, 2001 1:50:35 PM CDT> <Notice> <WebLogicServer> <ListenThreadlistening
o
n port 80>
<Jul 9, 2001 1:50:35 PM CDT> <Notice> <WebLogicServer> <SSLListenThreadlistenin
g on port 443>
<Jul 9, 2001 1:50:35 PM CDT> <Error> <Performance Pack> <Unable to loadperforma
nce pack, using Java I/O.
java.lang.ThreadDeath
>
<Jul 9, 2001 1:50:36 PM CDT> <Emergency> <WebLogicServer><ListenThread.run()
fa
iled: java.lang.ThreadDeath>
<Jul 9, 2001 1:50:36 PM CDT> <Emergency> <WebLogicServer> <The WebLogicServer
i
s no longer listening for connections. You should probably restart it.>
<Jul 9, 2001 1:50:36 PM CDT> <Alert> <WebLogicServer> <Server shutdown hasbeen
requested by system>
<Jul 9, 2001 1:50:36 PM CDT> <Alert> <WebLogicServer> <The shutdownsequence has
been initiated.>
<Jul 9, 2001 1:50:58 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
: '0' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
: '1' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
: '2' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
: '3' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
: '4' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
: '5' for queue: 'default'' stopped.>
<Jul 9, 2001 1:51:06 PM CDT> <Critical> <Kernel> <Execute Thread:'ExecuteThread
==============================================================
What can I do to start those StartUp classes successfully?
Thanks.
Alan Zhang

Startup class is not working in oc4j

hi
I have a servlet .In init of that servlet I will create an instance of a startup class .
In web.xml configuration I gave <load-on-startup></load-on-startup> .I created a war and an ear and deployed my application .The startup class is not called.
But when I configured the servlet in the default-web-app the startup class is running.
And furthur when I hot deploy my ear the startup class is running.
But when I restart my application server the startup class is not invoked.
can anybody help
Regards
Gajendran.G

hi
I had put auto-start=true in server.xml .then also it is not working.
when I redeploy my ear,the startup class is invoked,but when i restart the
server it does'nt
gaj

Failed to invoke startup class "MyStartup Class"

Hi,
I configured StartUpClass.java in Weblogic server through Admin Console . Also I set the required jar files in the classpath of the server in WL_HOME\server\bin\startWLS.cmd.
This StartUPClass is written to initialize and create the minimum number of objects in the pool, needed for URLConnection using ObjectPooling API.
I am getting Exceptions while starting the server after deployment of the application. I am pasting the full stack trace.
<Feb 1, 2007 9:49:55 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_12-b03 from Sun Microsystems Inc.>
<Feb 1, 2007 9:50:10 AM IST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<Feb 1, 2007 9:50:10 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Feb 1, 2007 9:50:11 AM IST> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at D:\bea\user_projects\domains\nessdomain\.\config.xml.>
<Feb 1, 2007 9:50:15 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea\user_projects\domains\nessdomain\myserver\myserver.log is opened. All server side log events will be written to this file.>
<Feb 1, 2007 9:50:18 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 1, 2007 9:50:18 AM IST> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server "myserver" for domain "nessdomain">
<Feb 1, 2007 9:50:31 AM IST> <Warning> <HTTP> <BEA-101248> <[Application: 'D:\MSM\Workspace\MSM2.0Jan9', Module: 'MSM31']: Deployment descriptor "web.xml" is malformed. Check against the DTD: org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". (line 96, column 11).>
<Feb 1, 2007 9:50:31 AM IST> <Warning> <HTTP> <BEA-101248> <[Application: 'D:\MSM\Workspace\MSM2.0Jan9', Module: 'MSM31']: Deployment descriptor "weblogic.xml" is malformed. Check against the DTD: org.xml.sax.SAXParseException: The content of element type "weblogic-web-app" must match "(description?,weblogic-version?,security-role-assignment*,run-as-role-assignment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filter?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-match-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-root?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)". (line 23, column 20).>
<Feb 1, 2007 9:50:35 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "MyStartup Class", java.lang.ClassNotFoundException: com.helio.msm.ws.util.StartUpClass
java.lang.ClassNotFoundException: com.helio.msm.ws.util.StartUpClass
     at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:141)
     at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:156)
     at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36)
     at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:121)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:116)
     at weblogic.t3.srvr.PostDeploymentStartupService.resume(PostDeploymentStartupService.java:63)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
     at weblogic.Server.main(Server.java:32)
>
<Feb 1, 2007 9:50:36 AM IST> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that wlntio.dll is in: 'D:\j2sdk1.4.2_12\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\j2sdk1.4.2_12\bin;c:\windows\system32;C:\apache-ant-1.6.5\bin;'
>
<Feb 1, 2007 9:50:36 AM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "myserver" for domain "nessdomain" running in Development Mode>
<Feb 1, 2007 9:50:36 AM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Feb 1, 2007 9:50:36 AM IST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address *.*>
<Feb 1, 2007 9:50:55 AM IST> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
Please help me in resolving this problem. I need it asap
Thanks,
Dharani

I should be more specific and have a bit more to add....
We have our app in an .ear file. I find that when I put the startup
classes in a seperate directory which is in the classpath specified in the
startWeblogic.cmd file they will be run on startup. I don't think I should
have to do this since these files exist in the ear file. I think this is
causing other problems too such as an illegalAccessError I get when an EJB
tries to load a class which was previously accessed by the startup classes.
Thanks,
Steve
Steve Snodgrass wrote:
Hi,
I am beggining to upgrade our app from Weblogic 5.1 to 6.0. So far it
has been progressing nicely and everything works with one exception. I
can not get the start up classes to run. I get the following exception:
<Failed to invoke startup class "MyStartup Class",
java.lang.ClassNotFoundException:
followed by my fully qualified class name. The class is reference
elsewhere in the code and works fine. Is a seperate classpath used for
startup classes? If not why might Weblogic have a hard time finding my
class?
Thanks,
Steve

Problems in startup class (MDB on Weblogic 7.0 / IBM MQ)

Hello friends,
          I am trying to communicate with IBM MQ through Weblogic 7.0 SP2 and
          using MDB.
          This is a bit strange but I had to reinstall Weblogic and I tried to
          deploy the Startup class . However I am getting this error:
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.NoSuchMethodError
          at com.ibm.mq.jms.services.ConfigEnvironment.<clinit>(ConfigEnvironment.java:173)
          at java.lang.Class.forName0(Native Method)
          I am totally at loss to understand this as it was working before I
          reinstalled the Weblogic. (Maybe I am skipping something which I had
          earlier done :-().
          All help appreciated.
          Thanks in advance,
          Milan Doshi


Since your simply running an MQ client in a startup class, you should
          be able to reproduce the issue without WebLogic in the mix. Once
          that is done, contact IBM for support. I continue to suspect
          a command-line problem - IBM is expecting something on
          the java JVM command-line that is missing.
          Tom
          Milan Doshi wrote:
          > Hello Tom,
          >
          > Thanks for the reply. I did ensure that all the relevant IBM jars are
          > in the classpath but I still get that error.Infact the claspath was
          > allready in place.
          >
          > Please give me your suggestions as I am totally at sea.
          >
          >
          > <May 23, 2003 5:31:17 PM EDT> <Emergency> <WebLogicServer> <000342>
          > <Unable to initialize the server: Fatal initialization excepti
          > on
          > Throwable: java.lang.NoSuchMethodError
          > java.lang.NoSuchMethodError
          > at com.ibm.mq.jms.services.ConfigEnvironment.<clinit>(ConfigEnvironment.java:173)
          > at java.lang.Class.forName0(Native Method)
          > at java.lang.Class.forName(Class.java:115)
          > at com.ibm.mq.jms.MQConnection.<clinit>(MQConnection.java:149)
          > at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:142)
          > at com.jpmc.ivr.middle.util.MQJMSStartup.startup(MQJMSStartup.java:112)
          > at weblogic.t3.srvr.StartupClassService.invokeStartup(StartupClassService.java:158)
          > at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:139)
          > at weblogic.t3.srvr.StartupClassService.access$0(StartupClassService.java:130)
          > at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:102)
          > at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
          > at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:97)
          > at weblogic.t3.srvr.StartupClassService.initialize(StartupClassService.java:60)
          > at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
          > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
          > at weblogic.Server.main(Server.java:32)
          >
          > ***************************************************************************
          > The WebLogic Server did not start up properly.
          >
          > Thanks and regards,
          >
          > Milan Doshi
          >
          > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          >
          >>Make sure that your MQ client classes are in
          >>the classpath used to boot the WL JVM. If you
          >>re-installed WL, and are using the installation's
          >>WL boot scripts rather than your own, the JVM
          >>will have a vanilla classpath - which, of course,
          >>won't include IBM classes.
          >>
          >>Tom
          >>
          >>Milan Doshi wrote:
          >>
          >>>Hello friends,
          >>>
          >>>I am trying to communicate with IBM MQ through Weblogic 7.0 SP2 and
          >>>using MDB.
          >>>
          >>>This is a bit strange but I had to reinstall Weblogic and I tried to
          >>>deploy the Startup class . However I am getting this error:
          >>>
          >>>
          >>>The WebLogic Server did not start up properly.
          >>>Exception raised:
          >>>java.lang.NoSuchMethodError
          >>> at com.ibm.mq.jms.services.ConfigEnvironment.<clinit>(ConfigEnvironment.java:173)
          >>> at java.lang.Class.forName0(Native Method)
          >>>
          >>>I am totally at loss to understand this as it was working before I
          >>>reinstalled the Weblogic. (Maybe I am skipping something which I had
          >>>earlier done :-().
          >>>
          >>>All help appreciated.
          >>>
          >>>Thanks in advance,
          >>>
          >>>Milan Doshi
          >>

Class not found exception for the startup class defined.

iam using weblogic server 10 and bea jrockit 1.5.0.12.
i have created a startup class in the admin console for a web project and i have deployed the war file using the console in a user defined domains, user project directory.
when i start the server, iam getting class not found exception for the startup class.
But, the startup class is available in the web archive (war). how should we add the classes and jars in the war to the classpath in setDomainEnv.sh or is there any other setting available in the console to enable this.

Hello Julius,
yes sure, we can move this post to the NW admin forum. I have already posted similar thread on sun forums. I was hoping that someone from SAP SDN already tackled this problem and if not someone specialized in J2EE Engine could troubleshoot me from the class problem I'm getting. I don't know if it's specific from the agent or if this ClassNotFound is a general SAP J2EE Engine error relating to a library not correclty defined.
Kind regards,
Tanguy Mezzano

WLS 10.0 Mp1 - Weblogic startup class to initialize client's SSL channels

Hi,
Is it possible to use Weblogic startup class to initialize client's SSL channels?
Any pointers are appreciated.
Thanks in advance.

Hey
If possible can you explain the issue in detail.
What do you mean by “initialize client's SSL channels”
Regards,
Hussain

Redundancy for startup class.

Hi,
I have a startup class in weblogic server. This class acts as a daemon inside
weblogic server. What happens if this class goes down due to an exception after
a while ? does the weblogic server brings it up again or can we configure it or
is it just lost?
-Kishan-

It it runs in its own thread why don't you just do something like this:
public void run()
............ //initialization
while(!shouldStop)
try
catch(Throwable th)
th.printStackTrace();
and you wouldn't need anything like the functionality you are describing which I do
not believe BEA does.
Regards,
--dejan
Kishan wrote:
Hi,
I have a startup class in weblogic server. This class acts as a daemon inside
weblogic server. What happens if this class goes down due to an exception after
a while ? does the weblogic server brings it up again or can we configure it or
is it just lost?
-Kishan-[dejan_bektchiev.vcf]

A startup class to enable MQ Queues to trigger MDBs in WLS 6.1(sp4)

          Hi,
          I am hoping for references to documentation or opinions on the following method
          allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          with MQs connection factory.
          I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          in a startup class will not allow MDBs to be linked to an MQ queue because startup
          classes are run after MDB deployment during startup. However I found some unused
          in-house code which appeared to do just that and it works.
          Here is the code in abbreviated form:
          public String startup(String str, Hashtable args) throws Exception
               bindMQFactory();
               bindMQQueues();
               return "";
          private void bindMQFactory() throws Exception
               // Create MQ Factory and configure it
               MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
               factory.setChannel(channel );
               factory.setHostName(host);
               factory.setPort(Integer.parseInt(port));
               factory.setQueueManager(qmanager);
               factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
               // bind connection factory into WLS JNDI for later use by clients
               _wlsContext.bind( connectionFactoryJndi, factory );
               // Force mq connection factory to be the one used for mdb's
               _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          private void bindMQQueue() throws Exception
               // create queue and configure it
               MQQueue queue = new MQQueue();
               queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
               queue.setBaseQueueName( mqQueueName );
               // bind queue in WLS JNDI
               _wlsContext.bind( wlsJndi, queue );
          Thanks in advance for any comments or opinions on the above.
          regards
          Martin


Start with the white-paper:
          "Using Foreign JMS Providers with WebLogic Server"
          Note that to get transactional behavior you
          will need to use the WebLogic Messaging Bridge feature.
          Note that integrating MQ is easier in 8.1 - consider
          using WL 8.1 if you can.
          One more comment in-line.
          Martin wrote:
          > Hi,
          >
          > I am hoping for references to documentation or opinions on the following method
          > allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          > the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          > with MQs connection factory.
          Not recommended. Highly not recommended. Do not use the same name
          as the internal factory. Create your own name for a CF, and change the
          weblogic ejb jar to reference your name. The above white-paper
          states how to do this.
          >
          > I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          > in a startup class will not allow MDBs to be linked to an MQ queue because startup
          > classes are run after MDB deployment during startup. However I found some unused
          > in-house code which appeared to do just that and it works.
          >
          > Here is the code in abbreviated form:
          > public String startup(String str, Hashtable args) throws Exception
          > {
          >      bindMQFactory();
          >      bindMQQueues();
          >
          >      return "";
          > }
          >
          > private void bindMQFactory() throws Exception
          > {
          >
          >      // Create MQ Factory and configure it
          >      MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          >      factory.setChannel(channel );
          >      factory.setHostName(host);
          >      factory.setPort(Integer.parseInt(port));
          >      factory.setQueueManager(qmanager);
          >      factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
          >
          >      // bind connection factory into WLS JNDI for later use by clients
          >      _wlsContext.bind( connectionFactoryJndi, factory );
          >
          >      // Force mq connection factory to be the one used for mdb's
          >      _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          > }
          >
          > private void bindMQQueue() throws Exception
          > {
          >      // create queue and configure it
          >      MQQueue queue = new MQQueue();
          >      queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
          >      queue.setBaseQueueName( mqQueueName );
          >
          >      // bind queue in WLS JNDI
          >      _wlsContext.bind( wlsJndi, queue );
          > }
          >
          > Thanks in advance for any comments or opinions on the above.
          >
          > regards
          >
          > Martin

Startup classes arguments

Similar Messages

Maybe you are looking for