Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Process of Configuring JMS Messaging on the Siebel Server >

Creating the JVM Subsystem

You can create the JVM subsystem using either the Siebel client or the command-line interface with the Siebel Server Manager (srvrmgr) utility. This is a step in Process of Configuring JMS Messaging on the Siebel Server.

Creating the JVM Subsystem Using the Siebel Client

The following procedure shows how to use the Siebel client to create the JVM subsystem.

To create the JVM subsystem using the Siebel client

1. In the Siebel application, navigate to the Administration - Server Configuration screen, Enterprises view.
2. In the top list applet, select the Enterprise Server that you want to configure.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile.
5. Set the following parameters:

   Name	Value
   Profile	JAVA
   Alias	JAVA
   Subsystem Type	JVMSubsys

6. In the Profile Parameters list applet (the bottom applet), set the following parameters:

   Name	Alias	Data Type	Value
   JVM Classpath	CLASSPATH	String	Must contain the following: JMS provider JAR files Siebel.jar and SiebelJI_lang.jar Folder that contains jndi.properties CAUTION:  Do not include oc4j-internal.jar in the CLASSPATH. Doing so will cause a Java exception, and the JMS implementation will not work. On Windows, the files in the CLASSPATH must be separated by semicolons (;) and end with a semicolon and period (;.), for example: D:\JMS;D:\JMS\Siebel.jar;D:\JMS\SiebelJI_enu.jar;D:\JMS\j2ee\home\lib\adminclient.jar; D:\JMS\j2ee\home\lib\jndi.jar;D:\JMS\j2ee\ home\lib\jta.jar;D:\JMS\j2ee\home\oc4jclient.jar;D:\JMS\j2ee\home\lib\bcel.jar;D:\JMS\j2ee\home\lib\jms.jar;D:\JMS\j2ee\home\lib\ javax77.jar;D:\JMS\jdbc\lib\ojdbc14dms.jar; D:\JMS\lib\dms.jar;D:\JMS\opmn\lib\optic.jar;D:\JMS\j2ee\home\lib\ejb.jar;D:\JMS\j2ee\home\lib\mail.jar;D:\JMS\j2ee\home\lib\pcl.jar;. On UNIX, the files in the CLASSPATH must be separated by colons (:) and end with a colon and period (:.), for example: /usr/jms:/usr/jms/Siebel.jar:/usr/jms/SiebelJI_enu.jar:/usr/jms/j2ee/home/lib/adminclient.jar:/usr/jms/j2ee/home/lib/jndi.jar:/usr/jms/j2ee/home/lib/jta.jar:/usr/jms/j2ee/home/oc4jclient.jar:/usr/jms/j2ee/home/lib/bcel.jar:/usr/jms/j2ee/home/lib/jms.jar:/usr/jms/j2ee/home/lib/javax77.jar:/usr/jms/jdbc/lib/ojdbc14dms.jar:/usr/jms/lib/dms.jar:/usr/jms/opmn/lib/optic.jar:/usr/jms/j2ee/home/lib/ejb.jar:/usr/jms/j2ee/home/lib/mail.jar:/usr/jms/j2ee/home/lib/pcl.jar:. NOTE:  The length of the CLASSPATH is limited to 1024 characters.
   JVM DLL Name	DLL	String	The path to the JVM library file, for example: C:\PROGRA~1\Java\JDK15~1.0_0\jre\bin\server\ jvm.dll
   JVM Options	VMOPTIONS	String	JVM-specific options for the log file, for example: Windows: -Djms.log=D:\JMS\log\jms.log Solaris: -Xusealtsigs -Xrs -Djms.log=/usr/jms/log/jms.log

7. Restart the Siebel Server.

Creating the JVM Subsystem Using Siebel Server Manager

The following procedure shows how to use Siebel Server Manager (srvrmgr) to create the JVM subsystem.

CAUTION:  Do not include oc4j-internal.jar in the CLASSPATH. Doing so will cause a Java exception, and the JMS implementation will not work.

To create the JVM subsystem using Siebel Server Manager

1. In the srvrmgr utility, type the following command, for example:
   • Windows:

   create named subsystem JAVA for subsystem JVMSubSys with DLL=C:\Sun\SDK\jdk\jre\bin\server\jvm.dll, CLASSPATH = D:\JMS;D:\JMS\Siebel.jar;D:\JMS\SiebelJI_enu.jar;
   D:\JMS\j2ee\home\lib\adminclient.jar;D:\JMS\j2ee\home\lib\jndi.jar;
   D:\JMS\j2ee\home\lib\jta.jar;D:\JMS\j2ee\home\oc4jclient.jar;
   D:\JMS\j2ee\home\lib\bcel.jar;D:\JMS\j2ee\home\lib\jms.jar;
   D:\JMS\j2ee\home\lib\javax77.jar;D:\JMS\jdbc\lib\ojdbc14dms.jar;
   D:\JMS\lib\dms.jar;D:\JMS\opmn\lib\optic.jar;D:\JMS\j2ee\home\lib\ejb.jar;
   D:\JMS\j2ee\home\lib\mail.jar;D:\JMS\j2ee\home\lib\pcl.jar;.,
   VMOPTIONS="-Djms.log=D:\JMS\log\jms.log"

   • UNIX:

   create named subsystem JAVA for subsystem JVMSubSys with DLL= /usr/jdk1.5.0_06/jre/lib/sparc/client/libjvm.so, CLASSPATH = /usr/jms:/usr/jms/Siebel.jar:/usr/jms/SiebelJI_enu.jar:/usr/jms/j2ee/home/lib/adminclient.jar:/usr/jms/j2ee/home/lib/jndi.jar:/usr/jms/j2ee/home/lib/jta.jar:/usr/jms/j2ee/home/oc4jclient.jar:/usr/jms/j2ee/home/lib/bcel.jar:/usr/jms/j2ee/home/lib/jms.jar:/usr/jms/j2ee/home/lib/javax77.jar:/usr/jms/jdbc/lib/ojdbc14dms.jar:/usr/jms/lib/dms.jar:/usr/jms/opmn/lib/optic.jar:/usr/jms/j2ee/home/lib/ejb.jar:/usr/jms/j2ee/home/lib/mail.jar:/usr/jms/j2ee/home/lib/pcl.jar:.,
   VMOPTIONS="-Xusealtsigs -Xrs -Djms.log=/usr/jms/log/jms.log"

2. Restart the Siebel Server.