WebSphere WebSphere Business Integration Message Service Clients for C/C++ Version 1.2.7 and .NET Version 1.2.6 Operating Systems: AIX, Linux, Solaris, Windows

JNDI Lookup Web service

To access a COS naming directory from XMS, a JNDI Lookup Web service must be deployed on a WebSphere 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 install directory. This can be installed within a WebSphere 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

Setting 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.

C, C++, and .NET applications can all 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.

Related concepts
Supported types of administered object repository
Property mapping for administered objects
InitialContext properties
URI format for XMS initial contexts
Retrieval of administered objects
Related tasks
Creating administered objects
InitialContext objects
Installing Message Service Client for C/C++ using the installation wizard
Installing from the command line
Installing Message Service Client for .NET using the installation wizard
Setting up the messaging server environment
Using the XMS sample applications
Related reference
Required properties for administered ConnectionFactory objects
Required properties for administered Destination objects

Concept topic

Terms of Use | Rate this page

Last updated: 18 Jun 2008

© Copyright IBM Corporation 2005, 2008. All Rights Reserved.