JNDI Lookup web service

To access a COS naming directory from XMS, a JNDI Lookup web service must be deployed on a WebSphere Application Server service integration bus server. This web service translates the Java information from the COS naming service into a form that XMS applications can read.

The web service is provided in the enterprise archive file SIBXJndiLookupEAR.ear, located within the installation directory. For the current release of IBM Message Service Client for .NET, SIBXJndiLookupEAR.ear can be found in the install_dir\java\lib directory. This can be installed within a WebSphere Application Server service integration bus server by using either the administrative console or the wsaadmin scripting tool. Refer to the product documentation for further information on deploying web service applications.

To define the web service within XMS applications, you simply need to set the XMSC_IC_URL property of the InitialContext object to the web service endpoint URL. For example, if the web service is deployed on a server host called MyServer, an example of a web service endpoint URL:

wsvc://MyHost:9080/SIBXJndiLookup/services/JndiLookup

Set the XMSC_IC_URL property allows InitialContext Lookup calls to invoke the web service at the defined endpoint, which in turn looks up the required administered object from the COS naming service.

.NET applications can use the web service. The server-side deployment is the same for XMS C, /C++ and, XMS .NET. XMS .NET invokes the web service directly through the Microsoft .NET Framework.