CA AuthMinder UNIX Installation Guide › How to Plan the Deployment › Choosing a Deployment Model › Single System Deployment › High-Availability Deployment

High-Availability Deployment

In a high-availability deployment, Strong Authentication components are installed on more than one server to provide high availability and scalability.

The diagrams in this section depict several possible options for which prerequisites and Strong Authentication components can be installed on multiple systems for a high-availability deployment.

• When do I add a new server instance?

  Typically, when your transaction rate exceeds the allowable threshold (as decided by your organizational policies), then you need to add a new server instance.

• How many servers, Administration Console, UDS, and SDK instances can I have?
  • Strong Authentication Servers: Multiple instances are supported. The number depends on the transaction rate you want to achieve.
  • Administration Consoles: Multiple instances are supported. The number depends on the number of administrators in the system who log in to the Console at the same time.
  • UDS Servers: Currently, only one is supported. But if you need multiple instances of UDS, put them behind a Load Balancer. However, UDS failover is not supported.
  • SDKs: Multiple instances are supported. This number depends on the number of your application instances that you plan to support.

The following figure illustrates multiple-instance deployment of Strong Authentication using Java SDK.

The following figure illustrates multiple-instance deployment of Strong Authentication using Web Services.