Listing All Ports Exposed by Routers in a Grid

Use this procedure to see a list of all ports that are exposed, including their type and their address. A suitable port may be selected with the help of this list, but this should be explained better in the documentation of each application.

To list all ports exposed by routers in a grid

  1. Navigate to the Configuration Manager.
  2. Click the Advanced Configuration link.
  3. Click the Defined Ports link.

Reasons the List of Ports May Be Incorrect

The Infor Ion Grid only knows about ports that are part of the grid's configuration and that it manages. Often it is those ports that clients should connect to but not always.

Typical examples:

  • A web server may have been placed between the clients and the grid routers. In this case, clients that normally would have connected to an HTTP(S) port of one of the routers should now connect to the web server instead. Traffic will then be routed from the web server to the routers in a transparent manner unknown to both the grid and the client.

  • Several grid routers may have been configured on different grid hosts and some form of network load balancer has been placed in front of them in order to achieve fault tolerance. In this case, clients should not connect to the ports that the grid is aware of (the router ports). Instead, clients should connect to the ports associated with the network load balancer.

What commonly occurs in these example cases (and there may be others) is that the Infor Ion Grid has no way of knowing of these external ports. Since the grid does not know about them, the grid is not in a position to indicate to clients that the external ports should be used. It is entirely up to the person who installs the client application to know of the existence of the above situations and connect to the correct ports.

Although the Infor Ion Grid may be unaware of the correct ports to use, there is a mechanism in the Infor Ion Grid that you can use to determine how clients connect. This mechanism, however, must be configured manually. Also, the clients have to be coded to make use of this information. For more information, see Working With Context Root Discovery URLs.