Disabling static routing for a cluster

Because the information contained in a 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. When you delete the static routing table, cluster members automatically resume using dynamic routing to handle enterprise bean requests.

Overview

Perform the following steps to delete the static routing table.

Procedure

1. For each member of the cluster, set the ORB_LISTENER_ADDRESS property 0 (zero).

   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 0.

2. Delete the static route table file from the config directory of the deployment manager for the cluster.

   You have two options for deleting the static route table file. You can:

   1. Manually delete the static route table file. The path to this config directory was included in the message you received when you originally exported this file. If you did not retain this information, you can do a query for the file cluster_name.wsrttbl.

   2. Use the wsadmin tool to delete the static route table file.

   If you decide to use the wsadmin tool to delete the static route table file, perform the following steps:

   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=cluster_name,*')
        print cluster
        

      • Using Jython:

        cluster = 
        AdminControl.completeObjectName('cell=mycell,type=Cluster,name=
        cluster_name,*') 
        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. Remove the static route table file.

      • Using Jacl:

        $AdminControl invoke $cluster removeRouteTable

      • Using Jython:

        AdminControl.invoke(cluster, ‘removeRouteTable')

   If the route table file is successfully removed, the removeRouteTable command will return the value true. If the route table file could not be found, the removeRouteTable command will return the value false. If an unexpected problem occurs, an exception is issued.

3. Synchronize the configuration changes across the nodes to ensure that the static routing table is removed from all of the nodes. Follow the instructions specified in the Synchronizing nodes with the wsadmin tool topic.

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

5. Start the cluster again. Follow the instructions specified either the Starting clusters or Starting clusters using scripting topic.

6. Exit the wsadmin tool.

Results

Related tasks

Related information