Resolution:

When a Message Driven Bean (MDB) deployed in the WAS tries to connect to the EMS server, the connection involves two phases.

1). A JNDI lookup, where the application will try to connect to the EMS server that serves as a JNDI server.

2).  The application gets the information about the actual data EMS server from the factories.conf file of the JNDI EMS server and using that information, connects to the data EMS server.

All the information stored in the jndi.properties (i.e. the JNDI provider URL, security protocols, username, password, SSL certificates and passwords, the J2SE vendor etc.) are used to connect to the JNDI EMS server. Instead of using a physical jndi.properties file, all properties that need to be present in the jndi.properties file for JNDI lookup can also be defined as the “Custom Properties” of an attribute/value pair for the TIBCO JMS provider that is configured in WAS.

Why is the jndi.properties file used when integrating IBM WAS with a TIBCO EMS server? Is there any way to integrate WAS with the EMS server without using the jndi.properties file as it is very difficult to manage a physical file?