This section contains information about resolving problems related to the IBM Java Object Request Broker (ORB), which handles communication between IBM WebSphere InterChange Server and several of its components. This section provides information on the following topics:
IBM WebSphere InterChange Server requires the IBM Java ORB to communicate with several of its components, including adapters and System Manager. Use of the ORB requires installation of the IBM Java ORB.
The IBM Java ORB is installed as part of the IBM Java Runtime Environment (JRE) software, which the IBM WebSphere InterChange Server Installer installs automatically.
Perform the following steps to customize the Object Request Broker:
As Table 24 shows, the ORB location is specified by special variables in the CWSharedEnv file. You must modify these variables in the CWSharedEnv file to change its location.
Other ORB properties are listed in the ORB_PROPERTY variable of the CWSharedEnv file. In this variable, each IBM ORB property is preceded by the -D command-line option. To add or change an ORB property, you must add or change the appropriate -D option in the ORB_PROPERTY variable of the CWSharedEnv file. Properties you specify in the CWSharedEnv file override any other settings from the configuration file.
For example, to specify the maximum number of threads, you can take any of the following actions:
ORB_PROPERTY=-DORBNamingProvider=CosNaming
-Dorg.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB
-Dorg.omg.CORBA.ORBInitialPort=%ORB_PORT%
-Dorg.omg.CORBA.ORBInitialHost=%ORB_HOST%
-Dcom.ibm.CORBA.Debug.Output=nul
-Dcom.ibm.CORBA.ThreadPool.MaximumSize=100
start_server.....-Dcom.ibm.CORBA.ThreadPool.MaximumSize=100
[CORBA]
OAthreadMax=100
Table 24. IBM Java ORB properties that can be customized
IBM ORB property | Configuration parameter | Description |
---|---|---|
com.ibm.CORBA.ListenerPort | OAport | Port number on which the ORB server (within IBM WebSphere InterChange Server) listens for incoming requests. |
com.ibm.CORBA.LocalHost | OAipAddr | IP address or host name of the machine on which the ORB server (within IBM WebSphere InterChange Server) is running. |
com.ibm.CORBA.ThreadPool. MaximumSize | OAthreadMax | Maximum number of threads that the connection manager can create. The default value (zero) indicates that no size restriction exists. |
com.ibm.CORBA.ThreadPool. InactivityTimeout | OAthreadMaxIdle | The time (in seconds) before an idle thread is destroyed. |
com.ibm.CORBA.RequestTimeout | None | Number of seconds that a CORBA request waits before timing out. By default, there is no timeout; the ORB waits indefinitely for a response. |
com.ibm.CORBA.LocateRequest | None | Timeout value (in seconds) for Locate Requests. |
com.ibm.CORBA.FragmentTimeout | None | Maximum length of time that the ORB waits for second and subsequent message fragments before it times out. Set this property to zero to indicate no timeout. The default value is 30000. |
Perform the following steps to change the location of the Object Request Broker during installation:
Table 25 also shows the variables within the CWSharedEnv
file that specify the ORB location.
Table 25. Location of the IBM Java ORB
ORB location | IBM ORB property | Default value | CWSharedEnv variable |
---|---|---|---|
IP address | org.img.CORBA.ORBInitialHost | Name of the local host | ORB_HOST |
Port number | org.omg.CORBA.ORBInitialPort | 14500 | ORB_PORT |
Perform one of the following steps to change the location of the Object Request Broker after installation:
set ORB_PORT=15002
-Dorg.omg.CORBA.ORBInitialPort=15002
For information on how to change ORB properties, see Steps for customizing the Object Request Broker.
Using IBM Transient Naming Server (tnameserv) provides the naming service for the IBM WebSphere Business Integration system. When a component of the IBM WebSphere Business Integration 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 IBM WebSphere InterChange Server, it obtains the location of IBM WebSphere InterChange Server through the Transient Naming Server.
The IBM WebSphere InterChange Server product provides the CosNameServer_Dump tool to list all valid IBM WebSphere InterChange Server 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.
When a component of the IBM WebSphere Business Integration 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 IBM WebSphere InterChange Server 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:
As part of its startup process, IBM WebSphere InterChange Server 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 IBM WebSphere InterChange Server has not yet started when the adapter starts, the naming repository is updated whenever IBM WebSphere InterChange Server does start.
Perform the following steps to turn off the Persistent Naming Server: