+

Search Tips   |   Advanced Search

 

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 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 restart on different ports and the deployment manager is not able to route IIOP requests to the cluster members.

 

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. In the console, click Servers > Clusters.

  2. Select the fully-configured cluster for which static routing is required and click Start if it is not already running.

  3. Ensure that the cluster is in a fully available state such that a client can route across the entire cluster.

  4. Click the name of the cluster, and then click Export route table to create a static route table for that cluster. After the table is created, an informational message, similar to the following message, is issued that indicates the name of the file that contains the table and where that file is located: 

    The route table for cluster MyCluster was exported to file
/home/myInstall/was/server/profiles/dmgrProfile/config/cells/MyCell/
     clusters/Myfile.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.

  5. In the console navigation, click System administration > Nodes, select all of the nodes in the cluster, and then click Full Resynchronize. This file is then distributed to all of the nodes in the cell.

  6. In the console navigation, click Servers > Clusters, select the cluster that needs the static route table, and then click Stop to stop the cluster.

  7. Select the cluster again and click Start. The cluster members do not start to use the static route table until you stop and then restart the cluster.

 

Results

The cluster members use the static route table to perform IIOP routes.

 

What to do next

When your high availability infrastructure is enabled, disable static routing so that the cluster members resume using dynamic routing:

  1. Set the ORB_LISTENER_ADDRESS property back to 0 (zero).

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

  3. Force a node synchronize to ensure the file is removed from the nodes.

  4. Stop the cluster and then start the cluster again.

 

Related tasks


Creating clusters

 

Related Reference


Server cluster settings