CA RiskMinder Windows Installation Guide › Planning the Deployment › Choosing a Deployment Model › Deploying in a High-Availability Environment

Deploying in a High-Availability Environment

In a high-availability deployment, RiskMinder components are installed on more than one server to provide high availability and scalability. This section discusses the component diagrams for deploying in a high-availability environment.

Component Diagrams

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

Decision Points

• When do I add a server instance?

  Typically, when your transaction rate exceeds the permissible threshold (as decided by your organizational policies), then you must add a server instance.

• How many RiskMinder Server, Case Management Server, UDS, and SDK instances can I have?
  • RiskMinder 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 sections help you achieve your deployment decision.

High-Availability Deployment Using Java SDK

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

High-Availability Deployment Using Web Services

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