If you are using the administered JMS objects provided by WebSphere ESB with Message Service Clients for C/C++ and .NET, you must configure the JNDILookup Web Service that WebSphere ESB provides to enable non-Java clients to access administered JMS objects from a non-Java environment.
Before starting this task, make sure that the JNDILookup Web Service application has been installed.
Web Services Client for C++ is a prerequisite for using the JNDILookup Web Service with Message Service Client for C/C++. If you are using administered objects with Message Service Client for C/C++ applications, ensure that a compatible version of Web Services Client for C++ has been installed before starting this task. The versions of Message Service Client for C/C++ and Web Services Client for C++ that are packaged within WebSphere ESB are compatible.
Administratively defined ConnectionFactory and Destination objects provide a separation between a JMS implementation and the JMS interfaces, which makes JMS client applications more portable since they are sheltered from the implementation details of a JMS provider. Administered objects enable an administrator to manage the connection settings for client applications from a central repository. For example, the specific queue that an application uses can be altered by changing the administered Destination object that the application obtains via JNDI.
Non-Java clients such as Message Service Clients for C/C++ and .NET can also use administered objects. However, since the administered JMS objects provided by WebSphere ESB are serialized Java objects accessed via JNDI, non-Java clients are not able to interpret them properly without the use of the JNDILookup Web Service. This web service provides a lookup operation that allows Message Service Clients for C/C++ and .NET to request the retrieval of a JNDI object by specifying the name of the object. The properties of the administered object are returned to the application using a Map of name/value pairs.