Disable static routing for a cluster

 

+

Search Tips   |   Advanced Search

 

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 the high availability infrastructure is enabled. When you delete the static routing table, cluster members automatically resume using dynamic routing to handle enterprise bean requests.

Perform the following steps to delete the static routing table.

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

   Go to...

   Servers | Server Types | WebSphere application servers | server_name Communications | Ports | ORB_LISTENER_ADDRESS

   

   ..and change the value specified for the Port field to 0.

2. Manually delete the static route table file from the config directory of the dmgr for the cluster.

   The path to this config directory was included in the message that you received when you originally exported this file. If we did not retain this information, we can do a search in the dmgr config directory for the file cluster_name.wsrttbl.

3. Synchronize the configuration changes across nodes.

   1. Clear the configuration repository Epoch. If we do not clear the configuration repository Epoch, the synchronization only updates the files that the configure service component edited, which does not include the file that contains the static routing table.

      Jacl...

      set configRepository [$AdminControl completeObjectName node=node_name,type=ConfigRepository,*]
      $AdminControl invoke $configRepository refreshRepositoryEpoch

      Jython...

      configRepository = AdminControl.completeObjectName('node=node_name, type=ConfigRepository,*') AdminControl.invoke(configRepository, 'refreshRepositoryEpoch')

   2. Repeat this process for each node to synchronize.

4. Stop the cluster.

5. Start the cluster again.

6. Exit wsadmin.

 

Related tasks

Enable static routing for a cluster
Saving configuration changes with wsadmin
Synchronizing nodes with wsadmin
Start wsadmin
Stopping clusters
Stopping clusters using scripting

 

Related information

Starting clusters
Starting clusters using scripting