Options for Configuring Primary and Secondary CyberMgr

There are two options for configuring the Primary and Secondary CyberMgr:

  1. Configure a Direct Connection to the Primary and Secondary CyberMgr

    Define the config.txt parameters to point directly to the CyberMgr instances.

    HACyberMgrPrimary:      primary.cybermgr.acme.com:46678
    HACyberMgrSecondary:    secondary.cybermgr.acme.com:46678

    In this case, Platform Server would always connect to the Primary CyberMgr. If connections to the Primary CyberMgr fail, Platform Server attempts to connect to the Secondary CyberMgr.

    This option requires network connectivity to the Primary and Secondary CyberMgr.

    The only disadvantage to this approach is that if the Primary CyberMgr is down, connections to the Primary CyberMgr may take a few seconds to timeout, thus causing transfers to take longer.

  2. Configure the Connection to the Primary and Secondary CyberMgr to run through a load balancer in Active/Passive mode

    Define the config.txt parameters to point directly to the load balancer.

    HACyberMgrPrimary:      loadbalancer.cybermgr.acme.com:46678
    HACyberMgrSecondary:    loadbalancer.cybermgr.acme.com:46678

    In this case, Platform Server would always connect to the Primary CyberMgr which in this case is a load balancer.

    The load balancer must be configured to connect to the Primary and Secondary CyberMgr in Active/Passive Mode.

    The load balancer keeps track of which CyberMgr is active and routes the request to the Primary CyberMgr when active. It only routes the request to the Secondary CyberMgr if the Primary CyberMgr is unreachable.

    The advantage to this approach is that when the Primary CyberMgr is down, the load balancer automatically routes requests to the Secondary CyberMgr without a delay.

    This option requires network connectivity from the Platform Servers to the load balancer. The load balancer must have connectivity to the Primary and Secondary CyberMgr instances.

Note: When using a load balancer to connect to CyberMgr, the load balancer must be configured to work in Active/Passive mode. Otherwise, duplicate transaction numbers and possible corrupted Log.txt (audit) files are generated.