We would like to monitor and tune our environment to ensure we are getting the most from the product and to avoid outages. Where can we find details?
Release : 14.4, 14.5
Component :
The following is a basis for tuning. There is no one right answer, and two clients with similar deployments may require vastly different configurations for optimal performance.
For details on overall system health please review
KB: 233003
https://knowledge.broadcom.com/external/article/233003
This is our In Progress document and is a good starting point for reviewing and maintaining the overall health of your environment as a healthy Task Persistence database is vital for overall IDM performance.
KB 46523
https://knowledge.broadcom.com/external/article?articleId=46523
This doc discusses overall performance tuning;
KB 240023 Discusses Database pools tuning:
https://knowledge.broadcom.com/external/article/240023
Discusses tuning your database connection pools which can have a significant impact on overall performance.
Task Persistence Cleanup -
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/configuring/task-persistence/monitor-health-of-the-task-persistence-database.html
This is touched on in almost every document around overall performance and specifically called out here as keeping the Task Persistence Runtime database optimized will eliminate many performance-related issues.
The product documentation:
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/reference/performance-tuning.html
This link has information around tuning your application server, Provisioning and the ehcache - which can greatly help if there are a huge number of provisioning roles (thousands)
Documentation on tuning your Roles and tasks, User Store and other general usage suggestions:
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/getting-started/performance-and-optimization.html
Clients have reported better overall performance after migrating to the latest supported Jboss (7.4) and Wildfly (23) versions.
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/Release-Notes/support-for-jboss-eap-74-and-wildfly-23.html
There is a memory leak in the out-of-the-box netty jar files provided with Jboss 7.2 and Wildfly 15, see KB 266967
https://knowledge.broadcom.com/external/article/266967 for details.