CA RiskMinder UNIX Installation Guide › Planning the Deployment › Choosing a Deployment Model

Choosing a Deployment Model

RiskMinder Server is the primary component of the RiskMinder deployment because it provides the risk evaluation service. You integrate your application with the RiskMinder Server by using the Java SDKs or web services that are shipped with the RiskMinder Server.

RiskMinder also requires an SQL database for storing server configuration data, user-specific preferences, and usage data.

Typically, all RiskMinder components are installed on a single system for development and simple testing. However, in production deployments and staging environments, RiskMinder Server should be installed on its own system. The Java SDKs or web services are installed on the system or systems on which your application is installed.

RiskMinder is also shipped with a Sample Application, which can be used to verify that RiskMinder was installed properly and to perform risk evaluation. Sample Application also serves as a code sample for integrating RiskMinder with your existing application.

The following high-level deployment types are supported by RiskMinder:

• Single-System Deployment - For development or testing
• Distributed-System Deployment - For production or staging environments
• High-Availability Deployment - For high availability and scalability, production, or staging environments