Connection Manager High Availability

Connection Manager supports high availability.

The following figure shows how high availability can be configured:

To configure high availability, you must conform to the following rules:
  • Create two or more CMS instances in the internal network, executing on different computers.
  • Create two or more CMA instances in the DMZ, executing on different computers.
  • Create two or more Internet Server instances in the DMZ, executing on different computers.
    Note: CMA and Internet Server can execute on the same computer or on different computers.
  • CMS1 and CMS2 must be configured to connect to CMA1 and CMA2.
  • CMA1 and CMA2 must be configured to accept connections from CMS1 and CMS2.
  • CMA1 and CMA2 must be configured to accept connection requests from MFTIS1 and MFTIS2.
  • MFTIS1 and MFTIS2 must be configured to connect to CMA1 and CMA2.

Connection Manager operates in an active or passive mode. Requests are sent to the first available component. If the connection to that component fails or is not available, the Connection Manager attempts to send the request to the next component.

The configuration in the figure above works as follows.

Note: MFTIS1 needs to connect to a Platform Server in the internal network.
  1. At startup, CMS1 and CMS2 both attempt to establish connections to CMA1 and CMA2. If any connection requests fail, CMS1 and CMS2 continue to connect to CMA every 30 seconds until the connection request is successful.
  2. MFTIS1 attempts to connect to CMA1 to perform this connection. Assume that CMA1 is not available; MFTIS1 then connects to CMA2.
  3. CMA2 looks for an active control connection from CMS. If CMA has an active control connection with CMS1, it initiates the request to CMS1. Assume no active control connection to CMS1 is available; CMA2 then initiates the request to CMS2 over an active control connection.
  4. After CMA2 makes an active connection to CMS2, CMS2 connects to the target Platform Server.
  5. CMS2 then connects back to CMA2 over the data connection port (48001).
  6. CMA2 then completes the connection with MFTIS1. Data begins to flow over the connection: MFTIS1 > CMA2 > CMS2 > Platform Server.
  7. CMA2 issues heartbeat requests to CMS2 every 45 seconds. If no response is received within 30 seconds, CMA2 breaks the connection and waits for CMS2 to initiate a new connection.
  8. CMS2 waits for heartbeat requests from CMA2. If no heartbeat request is received within 90 seconds, CMS2 closes the connection to CMA2 and attempts to re-establish the connection to CMA2. If this fails, the CMS2 attempts to connect to CMA2 every 30 seconds.