Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Process of Installing Required Files for JMS Messaging >

Creating the jndi.properties File

The jndi.properties file provides the JMS subsystem on the Siebel Server with a connection point (RMIInitialContextFactory) that it can use to look up queues and their connection factories dynamically. The jndi.properties file is created on the computer where the Siebel Server is installed, for example, in the D:\JMS directory. This is a step in Process of Installing Required Files for JMS Messaging.

NOTE:  The full path of the jndi.properties file must be included in the CLASSPATH in Creating the JVM Subsystem.

To create the jndi.properties file

• Use a text editor to create the jndi.properties file (for example, in the D:\JMS directory) as follows:

  java.naming.factory.initial=oracle.j2ee.rmi.RMIInitialContextFactory

  java.naming.provider.url=opmn:ormi://Oracle_Fusion_Middleware_server:port/OC4J_instance

  java.naming.security.principal=username

  java.naming.security.credentials=password

The following is an example of a jndi.properties file:

java.naming.factory.initial=oracle.j2ee.rmi.RMIInitialContextFactory

java.naming.provider.url=opmn:ormi://SOAserver.mycompany.com:6003/oc4j_soa

java.naming.security.principal=oc4jadmin

java.naming.security.credentials=welcome1

NOTE:  When creating the jndi.properties file, make sure that the port is set correctly in the java.naming.provider.url parameter. The previous example shows 6003, but it might be a different value. Contact your Oracle Fusion Middleware administrator for help with determining the correct port.