Best practices for monitoring the health of Windows cluster services, Provisioning Directory, and remote endpoints like SAP and Active Directory.

Products

• CA Identity Manager
• CA Identity Suite
• CA Identity Portal

Issue/Introduction

Administrators require a strategy to ensure high availability and operational health for CA Identity Manager. Monitoring requirements include verifying that the Provisioning Directory functions without issues, confirming Windows services remain active, and validating the accessibility of remote endpoints such as SAP and Active Directory from the perspective of the Identity Manager system.

 

Environment

Identity Manager 14.5, v15

Resolution

Implement a multi-layered monitoring strategy to cover all system components:

Centralized Service Monitoring: Use DX Unified Infrastructure Management (UIM) to monitor the status of core Windows services. Ensure CA Identity Manager, Java Connector Server (JCS), C++ Connector Server (CCS), and the Provisioning Server services are operational.

Proactive Endpoint Health Checks: Create scheduled tasks within Identity Manager to perform simple read operations against a test account on endpoints. A failure in these scheduled tasks serves as an early warning for endpoint connectivity or health issues.

Directory Monitoring: Utilize the CA Directory external monitoring API or SNMP for health checks on the Provisioning Directory. Detailed log file monitoring remains a primary method for identifying internal directory issues.

Component Health Verification: Monitor the Provisioning Server and C++ Connector Server health using the specific product documentation paths.