CA AuthMinder UNIX Installation Guide › Planning the Deployment › Choosing a Deployment Model › Deploying on a Single System › Deploying in High-Availability Environment › Component Diagrams

Component Diagrams

The diagrams in this section depict several possible options for which prerequisites and AuthMinder 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 AuthMinder Server, Administration Console, UDS, and SDK instances can I have?
  • AuthMinder 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, 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 AuthMinder using Java SDK.

High-Availability Deployment Using Web Services

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