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.
Vapp 14.5.1 CHF01
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:\
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.