1.6 Deployment Options for Identity Manager

Consult the following table to plan the physical environment for your Identity Management solution. These deployment use cases provide an overview of the Identity Management physical architecture and how the component products are connected and communicate with each other and other products. For an introductory overview of the Identity Management functional architecture and the components, see Functional Architecture.

Deployment Option	Summary
Single-server configuration on one computer	The most basic deployment configuration includes Identity Manager server and other required applications on one computer. You must ensure that the computer has the required memory, speed, and available disk space to meet the workload. This is a basic deployment use case and mostly suited for Proof-of-Concept (POC) and demonstration purposes only. It might not be appropriate for a production environment.
Distributed server configuration	This deployment has Identity Manager server on one computer and all other required applications on one or more additional computers. For example, components such as identity applications, iManager, OSP, and SSPR can run on a separate computer. You can include an additional computer to host the components for reporting service to suffice the system requirements for running the Sentinel Log Management for IGA component.
High-availability deployment	High availability is a redundancy operation that automatically switches to a standby server if the primary server fails or is temporarily shut down for maintenance. Identity Manager supports installing the following components in a high-availability environment: Identity Vault Identity Manager engine Remote Loader Identity applications, except Identity Reporting A typical cluster configuration contains Tomcat Application Server nodes hosting the Identity Applications for load balancing and fault tolerance. All the communication is routed through the load balancer. All nodes communicate to the same instance of the Identity Vault and the Identity Applications database. This configuration is scalable. You can easily increase the number of nodes to handle the load.

Deployment Option

Summary

Single-server configuration on one computer

The most basic deployment configuration includes Identity Manager server and other required applications on one computer. You must ensure that the computer has the required memory, speed, and available disk space to meet the workload. This is a basic deployment use case and mostly suited for Proof-of-Concept (POC) and demonstration purposes only. It might not be appropriate for a production environment.

Distributed server configuration

This deployment has Identity Manager server on one computer and all other required applications on one or more additional computers. For example, components such as identity applications, iManager, OSP, and SSPR can run on a separate computer. You can include an additional computer to host the components for reporting service to suffice the system requirements for running the Sentinel Log Management for IGA component.

High-availability deployment

High availability is a redundancy operation that automatically switches to a standby server if the primary server fails or is temporarily shut down for maintenance. Identity Manager supports installing the following components in a high-availability environment:

Identity Vault
Identity Manager engine
Remote Loader
Identity applications, except Identity Reporting

A typical cluster configuration contains Tomcat Application Server nodes hosting the Identity Applications for load balancing and fault tolerance. All the communication is routed through the load balancer. All nodes communicate to the same instance of the Identity Vault and the Identity Applications database. This configuration is scalable. You can easily increase the number of nodes to handle the load.