Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport >

Configuring the JMS Transport

The JMS Transport is built using the Java Business Service and therefore inherits all the requirements of that business service. This includes the independent installation of a Java virtual machine (JVM) and the configuration of the Siebel application to identify and create the VM. Configuration of the Siebel application requires creating a named subsystem of type JVMSubSys with the necessary properties. Refer to the Java Business Service documentation for instructions on how to configure the JVM named subsystem.

The JMS Transport requires that the CLASSPATH property of the JVM subsystem include the following packages or classes:

• Siebel.jar
• SiebelJI_lang.jar (where lang corresponds to the default language for your installation)
• A directory containing the location of the jndi.properties file

  The jndi.properties file contains the necessary name value pairs required to perform a JNDI lookup and bind to the remote queue.

• Necessary classes and JAR files as required by the JMS provider.

NOTE:  You can have only one JVM loaded in a process, and therefore only one JVM subsystem in a process. If you try to load more than one JVM subsystem into a process, an error will occur.

If you want multiple JVM subsystems, then you must configure additional components. For example, you can have EAIObjMgr_WL pointing to a JVM subsystem called JAVA_WL and EAIObjMgr_ORACLE pointing to a JVM subsystem called JAVA_ORACLE.

To verify that the CLASSPATH and jndi.properties are properly configured, refer to Troubleshooting for the JMS Transport.

The following JMS Transport configuration topics are also discussed here:

• About the JMSSubsys Named Subsystem
• About the JMS Receiver
• Creating a JMS Subsystem by Using the Siebel Web Client
• Sending and Receiving Messages with the JMS Transport