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.
About this task
Perform the following steps to delete the static routing table.
Procedure
- For each member of the cluster, set the ORB_LISTENER_ADDRESS property
0 (zero).
- In the administrative console, click Servers > Application
Servers > 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 0.
- Manually delete the static route table file from the config directory
of the deployment manager 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 deployment manager config directory for the file cluster_name.wsrttbl.
- Synchronize the configuration changes across nodes.
- 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.
Using 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')
- Repeat this process for each node that you want to synchronize.
- Stop the cluster. Follow the instructions specified
either the Stopping clusters or Stopping clusters using
scripting topic.
- Start the cluster again. Follow the instructions specified
either the Starting clusters or Starting clusters using
scripting topic.
- Exit the wsadmin tool.
Results
The cluster members resume using the dynamic routing table to handle
IIOP requests.