Enabling 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 begin
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:
- In the administrative console, click server_name, and then under Communications, click Ports .
- Click ORB_LISTENER_ADDRESS in the Port name field.
- 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.
About this task
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: