How to Configure and Monitor the Client Automation Infrastructure Health › Understand HM Architecture and Basics › Health Monitoring Components

Health Monitoring Components

The HM feature introduces the following components:

HM Agent:

A persistent module that is installed with the common agent and resides on all the tiers of the Client Automation infrastructure.

• Interprets the alert configuration on the agents, periodically monitors the occurrence of the alert conditions, and notifies the administrator on detecting the health conditions.

  Note: Alert monitoring is disabled by default. To enable health monitoring, apply a configuration policy.

• Provides the following command-line options for interaction:

  hmagent start 
  

  Starts the HM agent.

  hmagent stop 
  

  Stops the HM agent.

  hmagent status 
  

  Displays whether the agent is running and health monitoring is enabled.

• The HM agent is a service on Windows platforms and a daemon on Linux and UNIX platforms.

Alert Collector:

Alert Collector comprises the following modules:

Web Module

Receives the alerts from the HM agent and copies them to a configured folder.

Persistent Module

Monitors the configured folder and processes new alerts according to the configured alert collector role. For more information, see Configure Alert Collector.

The alert collector has the following requirements:

• The alert collector is only supported on Windows.
• IIS installation is a prerequisite.
• Ensure that the ISAPI extensions and ISAPI filters available under the Application Development option are installed.
• Depending on the DB type to which the alert collector persists the alerts, 32-bit SQL or the Oracle client must be installed.

The web module application hosts HM web services on IIS. This web service is independent of the existing Client Automation web services functionality and runs in a separate application pool.

The administrator can start, stop, and query the status of the alert collector process from the supported command line. Alert Collector supports the command line options similar to the HM agent.

Note: Whenever the FIPS mode is changed, verify the associated Change Action parameter value. If the parameter value is other than Reboot the machine, after the CAF restart you must also restart the following ones to switch the FIPS mode successfully for all the Client Automation components:

On a Manager or standalone Alert Collector computer:

• Alert collector
• Health Monitoring Agent

On a scalability server or agent computer:

• Health Monitoring Agent

Alerts on WAC:

DSM Explorer displays a notification when new alerts are raised. The notification contains a hyperlink that launches WAC and navigates to the Alerts page when the unified login is enabled for WAC. If the unified login is not enabled, enter the appropriate user credentials to navigate to the alerts page.