The Nojndi mechanism

The Nojndi mechanism enables JMS programs, which use JNDI interfaces, to use the same URI as WebSphere® MQ programs, which do not use JNDI.

You can use the WebSphere MQ transport for SOAP to invoke Web services on WebSphere Application Server. WebSphere Application Server SOAP over JMS looks up the JMS resources using JNDI. The Web service client might be running on .NET, or using Axis 1.4, to invoke the Web service and not using JNDI. To use the same URL for the client and server, it must provide the same information whether the environment is using JNDI or not.

The URI passed to the WebSphere MQ transport for SOAP by a Web service client contains a specific WebSphere MQ queue manager and queue names. These names are parsed and used directly by WebSphere MQ SOAP support.

The Nojndi mechanism directs the initialContextFactory used by a JMS program to com.ibm.mq.jms.Nojndi. The com.ibm.mq.jms.Nojndi class is an implementation of the JNDI interface that returns the connectionFactory and destination from the URL as ConnectionFactory and Queue Java objects. If the JMS implementation is WebSphere MQ, MQConnectionFactory and MQQueue inherit from the ConnectionFactory and Queue classes.

By using the Nojndi mechanism, you are able to provide the same connection information to WebSphere Application server and .NET using the same URL.