Recommended Sizing and Architecture for Broadcom Identity Manager (IM) and Identity Governance (IG) - IM service stopping by itself
search cancel

Recommended Sizing and Architecture for Broadcom Identity Manager (IM) and Identity Governance (IG) - IM service stopping by itself

book

Article ID: 405417

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

This article provides guidance on recommended sizing and architectural best practices for Broadcom Identity Manager (IM) and Identity Governance (IG) based on existing documentation. Adhering to these recommendations can help prevent performance bottlenecks and ensure optimal system stability and high availability.

Identity Manager (IM) and Identity Governance (IG) Sizing and Architecture:

For Broadcom Identity Manager and Identity Governance, particularly with Virtual Appliance (vApp) deployments, it is crucial to meet or exceed the recommended system resources. Running multiple components (Identity Manager, Identity Governance, Provisioning Server, User Store, and Connector Server) on a single VAAP server, especially in a production environment, is not a recommended architecture due to single points of failure and performance bottlenecks. Each of these components has its own resource demands, and cramming them onto one server means they are constantly competing for CPU, memory, and I/O. This significantly limits scalability, impacts reliability, and makes troubleshooting much harder.

Environment

Vapp 14.5.1 CHF01

Cause

The official Broadcom TechDocs for detailed minimum and recommended requirements for VMware deployments of the Virtual Appliance outline the necessary RAM and disk space for various Identity Suite components:\

  • Virtual Appliance VMware Deployment: Refer to the "VMware Deployment" from techdocs section in the Identity Suite 14.5 Virtual Appliance documentation for comprehensive details on setting up and sizing your virtual appliances.
    • Minimum Requirements: For a basic setup, the documentation specifies minimum RAM and disk space for each component. For example:
      • Identity Suite (SO+IP+IG+IM): Minimum 34 GB RAM (10GB for SO, 8GB for IP, 8GB for IG, 8GB for IM) and 50 GB Disk.
    • Recommended Requirements: For production environments and optimal performance, higher resource allocations are recommended:
      • Identity Suite (SO+IP+IG+IM): Recommended 40 GB RAM (16GB for SO, 8GB for IP, 8GB for IG, 8GB for IM) and 200 GB Disk.
  • Java Heap Size: Issues like `Java Heap Size not enough` can occur under heavy load. Increasing JVM heap space can address `OutOfMemoryError` incidents. While specific values may vary, the documentation often advises on adjusting JVM parameters for performance.

Best practice for a production environment would be to distribute these components across multiple dedicated servers for high availability and better performance. This approach minimizes single points of failure, allows for independent scaling of each component, and makes future upgrades and maintenance less disruptive.

Resolution

Following the guidelines and recommendations in the cited Broadcom documentation is essential for maintaining stable and high-performing Identity Manager and Identity Governance environments. Regularly reviewing and adjusting resources based on actual usage and documented best practices will contribute to system health and efficiency.