Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Balancing workloads > Create clusters

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

Perform the following steps to delete the static routing table.

Procedure

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

   1. In the admin console, click...

          > Server Types > WebSphere application servers > server_name

      and then in the Communications > Ports .

   2. Click ORB_LISTENER_ADDRESS in the Port name field.
   3. 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 you did not retain this information, you 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 you 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
      

      Using 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. Follow the instructions specified either the Stop clusters or Stopping clusters using scripting topic.

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

Results

The cluster members resume using the dynamic routing table to handle IIOP requests.
Enable static routing for a cluster
Saving configuration changes with wsadmin.sh
Synchronize nodes using wsadmin.sh
Start the wsadmin scripting client using wsadmin.sh
Stop clusters
Stop clusters using scripting
Create clusters
Start clusters
Start clusters using scripting

+

Search Tips   |   Advanced Search