Using the IBM Transient Name Server

Using IBM Transient Naming Server (tnameserv) provides the naming service for the WebSphere Business Integration Express system. When a component of the WebSphere Business Integration Express system starts, it registers itself with the IBM Transient Naming Server. When the component needs access to another business-integration-system component, it uses the naming service to determine the information it needs to locate and start interacting with that component. For example, when an adapter needs to communicate with InterChange Server Express, it obtains the location of InterChange Server Express through the Transient Naming Server.

Note:
The IBM Transient Naming Server is part of the IBM Java ORB. Therefore, it is installed automatically on the InterChange Server Express machine as part of the WebSphere InterChange Server Express installation process.

Identification of registered components

The WebSphere InterChange Server Express product provides the CosNameServer_Dump tool to list all valid InterChange Server Express ORB objects currently registered with the IBM Transient Naming Server. This tool is located in the bin subdirectory of the product directory. You invoke it with the following command: CosNameServer_Dump.bat.

Steps for using the Persistent Naming Server

When a component of the WebSphere Business Integration Express system starts, it registers itself with the IBM Transient Naming Server and its CORBA object is stored in the memory of the Transient Naming Server. However, if the Transient Naming Server fails, its memory contents are lost. As a result, all components that had been registered with it must be rebooted so they can reregister with the naming service.

The Persistent Naming Server extends the capability of the IBM ORB Transient Naming Server so that the collection of CORBA objects that are registered with the Transient Naming Server are stored in a naming repository. The existence of the naming repository means that these CORBA references, rather than being only in the Transient Naming Server memory, are persistent; that is, they are available to other processes and InterChange Server Express components in the event that the Transient Naming Server fails. Other components do not need to shut down and restart in order to reregister with the naming service.

The default location of the naming repository is the following local file: ProductDir\CxCosNameRepos.ior.

Perform the following steps to change the location of the naming repository:

  1. Edit the InterChange Server Express configuration file (InterchangeSystem.cfg).
  2. Set the CosNamingPersistencyFile configuration parameter in the CORBA section. By default, the Persistent Naming Server is enabled; that is, references to CORBA objects are maintained in the naming repository.
  3. For the naming server to run, you must explicitly start it with the PersistentNameServer startup file, located in the bin subdirectory of the product directory. This startup file takes the following steps:

    As part of its startup process, InterChange Server Express updates the naming repository by copying the CORBA objects currently registered with the Transient Naming Server into the naming-repository file. When each adapter starts, it updates the naming repository with its information. If InterChange Server Express has not yet started when the adapter starts, the naming repository is updated whenever InterChange Server Express does start.

    Note:
    If the Persistent Naming Server fails, you can restart it with the PersistentNameServer startup script. However, you do not need to restart InterChange Server Express or any started adapters.

Perform the following steps to turn off the Persistent Naming Server:

  1. Edit the InterChange Server Express configuration file (InterchangeSystem.cfg).
  2. Set the CosNamingPersistency configuration parameter (located in the CORBA section) to false.

Copyright IBM Corp. 2004