CA Risk Authentication Windows Installation Guide › How to perform a Fresh Installation › Select a Deployment Model › Deploy on a High Availability Environment

Deploy on a High Availability Environment

In a high-availability deployment, CA Risk Authentication components are installed on more than one server to provide high availability and scalability. The diagrams illustrate several possible options for which prerequisites and CA Risk Authentication components is installed on multiple systems.

Add a server instance when your transaction rate exceeds the permissible threshold (as decided by your organizational policies), then you must add a server instance. The following CA Risk Authentication components allow mostly multiple instances to function:

• CA Risk Authentication Servers: Multiple instances are supported. The number depends on the transaction rate you want to achieve.
• Case Management Queuing 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 simultaneously.
• UDS Servers: Currently, only one is supported.
• SDKs: Multiple instances are supported. This number depends on the number of your application instances that you plan to support.

The following illustrations show you how to achieve your deployment decision:

High Availability Deployment Using Java SDK

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

High Availability Deployment Using Web Services

The following figure illustrates multiple-instance deployment using Web services.