CA AuthMinder Windows Installation Guide › Planning the Deployment › Choosing a Deployment Model

Choosing a Deployment Model

As a part of AuthMinder deployment, AuthMinder Server is the primary component that you must install as it authenticates users. Your applications that need to use AuthMinder Server can integrate with it by using Java SDKs or Web Services shipped with it.

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

Typically, all AuthMinder components are installed on a single system for development and simple testing. However, in production deployments and staging environments, it is recommended that AuthMinder Server be installed on its own system. The shipped SDKs or Web Services are installed on a different system or systems that contain the application that users log in to.

AuthMinder is also shipped with Sample Application, which can be used to verify if AuthMinder is installed properly and is able to perform user authentication. Sample Application also serves as a code sample for integrating AuthMinder with your existing application(s).

The high-level deployment types supported by AuthMinder are:

• Single-System Deployment - For development or testing

  See "Deploying on a Single System" for more information.

• Distributed-System Deployment - For production or staging environments

  See "Deploying on Distributed Systems" for more information.

• High-Availability Deployment - For high availability and scalability, production, or staging environments

  See "Deploying in High-Availability Environment" for more information.