Enable static routing for a cluster

If the high availability infrastructure is disabled and you require IIOP routing capabilities, we 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 creating a static route table, ensure that:

You should only create a static route table if the high availability infrastructure is disabled and you require IIOP routing capabilities. To create a static route table:

  1. Start wsadmin.sh if it is not already running.

  2. Identify the cluster managed bean (MBean) for the cluster for which we are creating the route table, and assign that MBean to a variable.

    • Jacl:
      set cluster [$AdminControl completeObjectName cell=
         cell_name,type=Cluster,name=cluster_name,*]  puts $cluster

    • Jython:
      cluster = AdminControl.completeObjectName('cell=
      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:


  3. Export the route table.

    • Jacl:

        $AdminControl invoke $cluster exportRouteTable

    • Jython:

    After the table is created, the name of the route table file, is displayed in a message similar to the following message:


    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 we can delete this file when we are ready to start using dynamic routing again.

  4. Synchronize the configuration changes across nodes.

    1. Clear the configuration repository Epoch. If we 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 containing the static routing table.

      Using Jacl:

        set configRepository [$AdminControl completeObjectName node=node,type=ConfigRepository,*] $AdminControl invoke $configRepository refreshRepositoryEpoch

      Using Jython:

        configRepository = AdminControl.completeObjectName('node=node, type=ConfigRepository,*') AdminControl.invoke(configRepository, 'refreshRepositoryEpoch')

    2. Repeat this process for each node to synchronize.

  5. Stop the cluster. Follow the instructions specified either the Stopping clusters or Stopping clusters topic.

  6. Exit wsadmin.sh.

  7. Use the following Debug flag appended to the startServer command to manually start each member of this cluster.


      For example, to start server1 on a Windows operating system with static routing enabled, issue the following command from the server profiles bin directory:

        startServer.bat server1 -Dcom.ibm.websphere.management.registerServerIORWithLSD=false


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

    What to do next

    When the high availability infrastructure is enabled, follow the instructions in the topic Disable static routing for a cluster to disable static routing. When static routing is disabled, the cluster members resume using dynamic routing.

    Related tasks

  8. Disable static routing for a cluster
  9. Saving configuration changes with wsadmin.sh
  10. Synchronize nodes using wsdmin.sh
  11. Start the wsadmin scripting client
  12. Stopping clusters
  13. Stopping clusters
  14. Start clusters
  15. Start clusters

  16. Java virtual machine custom properties