WebSphere Message Service Clients for C/C++ and .NET, Version 1.2 Operating Systems: Linux, Windows

JNDI Lookup web service

In order to access a COS naming directory from XMS, a JNDI Lookup web service needs to be deployed on a WebSphere ESB server. This web service translates the Java information from the COS naming service into a form that XMS applications can read.

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, a typical example of a web service endpoint URL is:

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

Setting 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, but the way in which the web service is invoked is different:

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
Creating an InitialContext
Related reference
Required connection factory properties
Required destination properties

Concept topic

Terms of Use | Rate this page

Last updated: 7 Dec 2005

© Copyright IBM Corporation 2005. All Rights Reserved.