Enable static routing for a cluster

If your high availability infrastructure is disabled and you require IIOP routing capabilities, you can create a static routing table for the members of a cluster to use to handle enterprise bean requests. Because the information contained in this static routing table does not account for server runtime state, you should delete this table and return to using the dynamic routing table as soon as your high availability infrastructure is enabled. Before you create a static route table, ensure that:

• The ORB_LISTENER_ADDRESS port is set to a non-zero value on each of the cluster members. Because the route table you create is static, and the cluster members do not communicate during state changes, if you do not set the ORB_LISTENER_ADDRESS port on each of the cluster members, the cluster members might restart on different ports, and IIOP requests will not be routed correctly. To change the value specified for the ORB_LISTENER_ADDRESS port:

  1. In the administrative console, click Servers > Application Servers > server_name, and then under Communications, click Ports .

  2. Click ORB_LISTENER_ADDRESS in the Port name field.

  3. Change the value specified for the Port field to a value that is greater than 0.

• Each cluster member is started and can use these new non-zero ORB_LISTENER_ADDRESS port values to correctly route IIOP requests.

Overview

You should only create a static route table if your high availability infrastructure is disabled and you require IIOP routing capabilities. To create a static route table:

Procedure

1. Start the wsadmin tool if it is not already running.

2. Identify the cluster managed bean (MBean) for the cluster for which you are creating the route table, and assign that MBean to a variable.

   • Using Jacl:

     cluster = 
     AdminControl.completeObjectName('cell=mycell,type=Cluster,name=managedClusterBean,*')
     print cluster
     

   • Using Jython:

     cluster = 
     AdminControl.completeObjectName('cell=mycell,type=Cluster,name=
     managedClusterBean,*') 
     print cluster

   These commands return the name of the cluster MBean for the specified cluster. For example, for cluster cluster1, the output from these commands will be similar to the following message:

   WebSphere:cell=mycell,name=cluster1,mbeanIdentifier=Cluster,type=Cluster,process=cluster1

3. Export the route table

   • Using Jacl:

     $AdminControl invoke $managedClusterBean exportRouteTable

   • Using Jython:

     AdminControl.invoke(managedClusterBean, ‘exportRouteTable’)

   After the table is created, the name of the route table file, is displayed in a message similar to the following message:

   /home/myInstall/was/server/profiles/dmgrProfile/config/cells/mycell/clusters/cluster1/cluster1.wsrttbl

   As this message illustrates, the file containing the table is placed in the config directory of the deployment manager for that cluster. You should keep a record of this location so that you can delete this file when you are ready to start using dynamic routing again.

4. Save your configuration changes. Follow the instructions specified in the Saving configuration changes with the wsadmin tool topic.

5. Synchronize the configuration changes across nodes. Follow the instructions specified in the Synchronizing nodes with the wsadmin tool topic.

6. Stop the cluster. Follow the instructions specified either the Stopping clusters or Stopping clusters using scripting topic.

7. Exit the wsadmin tool.

8. Use the following Debug flag appended to the startServer command to manually start each member of this cluster.

   -Dcom.ibm.websphere.management.registerServerIORWithLSD=false

   For example, to start server1 on a Windows operating system with static routing enabled, issue the following command from the server profile’s bin directory:

   startServer.bat server1 -Dcom.ibm.websphere.management.registerServerIORWithLSD=false
   

Results

What to do next

Related tasks

Related Reference

Related information