CA Strong Authentication UNIX Installation Guide › How to Plan the Deployment › Choosing a Deployment Model › High-Availability Deployment › Component Diagrams <C3_HA_CD>

Component Diagrams <C3_HA_CD>

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

Decision Points

• 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 CA Strong Authentication server, CA Advanced Authentication, UDS, and SDK instances can I have?
  • CA Strong Authentication Servers: Multiple instances are supported. The number depends on the transaction rate you want to achieve.
  • CA Advanced Authentication: Multiple instances are supported. The number depends on the number of administrators in the system who log in to the Console simultaneously.
  • UDS Servers: Currently, only one is supported. But if you need multiple instances of UDS, then you need to 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 sections will help you to achieve your deployment decision.

• High-Availability Deployment Using Java SDK
• High-Availability Deployment Using Web Services

High-Availability Deployment Using Java SDK

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

High-Availability Deployment Using Web Services

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