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.
You have two options for deleting the static route table file. You can:
If you decide to use the wsadmin tool to delete the static route table file, perform the following steps:
cluster = AdminControl.completeObjectName('cell=mycell,type=Cluster,name=cluster_name,*') print cluster
cluster = AdminControl.completeObjectName('cell=mycell,type=Cluster,name= cluster_name,*') print cluster
These commands return the name of the cluster MBean for the specified cluster. For example, for cluster cluster1, the output from these commands will be similar to the following message:
WebSphere:cell=mycell,name=cluster1,mbeanIdentifier=Cluster,type=Cluster,process=cluster1
$AdminControl invoke $cluster removeRouteTable
AdminControl.invoke(cluster, ‘removeRouteTable')
If the route table file is successfully removed, the removeRouteTable command will return the value true. If the route table file could not be found, the removeRouteTable command will return the value false. If an unexpected problem occurs, an exception is issued.