WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring the JNDILookup Web Service

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 you begin

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.

Why and when to perform this task

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.

Steps for this task

  1. Install and configure Web Services Client for C++ for use within Message Service Client for C/C++ applications. For information about configuring Web Services Client for C++ after installation, see Configuring after installation.
    Note: This step applies to Message Service Client for C/C++ only. Message Service Client for .NET invokes the web service directly through the Microsoft .NET framework.
  2. Define the JNDILookup Web Service URL within the Message Service Client for C/C++ or Message Service Client for .NET application. To define the web service URL within an application, set the XMSC_IC_URL property of the InitialContext object to the web service endpoint URL. This property can alternatively be specified as an argument on constructing the InitialContext object. For further information, see JNDILookup Web Service.
Related concepts
Administered objects
Related tasks
Installing the JNDILookup Web Service application
Configuring Web Services Client for C++ after installation
Working with administered objects
Starting installation from the Launchpad
Related reference
Administered objects settings
InitialContext (C API)
InitialContext (C++ API)
InitialContext (.NET API)
Problems with accessing the JNDILookup web service

Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_clients_jndiconfig.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)