Replacing missing routers and connection dispatchers

The host that you previously removed may or may not have contained one or more routers in addition to the administrative router that most likely was on the removed host. When you used LifeCycle Manager to move the registry, the administrative router was also moved so that one is already taken care of.

However, if there were other routers on the removed host, you have to consider how to replace them. One important thing to remember is that clients may connect to any router in a grid as long as that router is exposing the right kind of port. So, if you have lost a router that exposes an HTTP port but there is another existing router that exposes an HTTP port, you are not required to start any new routers. In this case, you simply must reconfigure the clients to connect to the other (existing) router instead of the old lost one.

This shows that the goal here is actually not to replace routers, but to replace lost ports. If the lost ports exist in other routers, you do not have to replace them. You just need to reconfigure clients to connect to the existing alternative ports. Whenever you are in doubt about what to replace or not replace, the recommendation is the following procedure:

  1. Add a new router as described in Routers. Give it a name, port, HTTP port, and HTTPS port as well as an external address.
  2. Configure certificates related to the HTTPS port as described in "Generating Client Certificates from LifeCycle Manager" and "HTTPS and SSL Certificates" in the Infor ION Grid Security Administration Guide.
  3. In order to find lost connection dispatchers, start by navigating to the Configuration Manager.
  4. Click the Applications link
  5. For each application in the list, do the following
    1. Click on the application name link in the list.
    2. If, at the top of the page, a suggested action to perform is displayed saying that a connection dispatcher is missing, click on the Fix this problem link next to the suggested action. Using the displayed dialog box, add the connection dispatcher to the new router and give it a port number. Consult the documentation for each application for details.
    3. Return to the list of applications and repeat the previous steps until all applications have been dealt with.
  6. Save the new configuration if changes have been made.

At this point you have in one way or the other replaced all missing ports. Still, clients need to be reconfigured in order to find the new ports. Even if you gave the ports exactly the same port numbers, they are still on a new IP address, so clients need to be reconfigured. Consult the documentation for each client application that is affected.

Note: The word "clients" here refers to clients to the grid. These clients may still be server side products. For example, if a web server is placed between the actual clients and the grid, it is the web server that needs to be reconfigured and not the actual clients. Likewise, if some form of network load balancing is put in front of routers, it is the network load balancer that needs to be reconfigured, not the clients.