HCL Workload Automation, Version 9.4

Monitoring the HCL Workload Automation processes

You can use event-driven workload automation (EDWA) to monitor the status of network processes and to start a predefined set of actions when one or more specific events take place. For more information about event-driven workload automation, refer to HCL Workload Automation: User's Guide and Reference.

You can monitor the following processes:
  • agent
  • appservman
  • batchman
  • jobman
  • mailman
  • monman
  • netman
The .XML file contains the definition of a sample event rule to monitor the status of the specified processes on the specified workstation. This event rule calls the MessageLogger action provider to write a message in a log file in an internal auditing database. If the condition described in the rule is already existing when you deploy the rule, the related event is not generated. For more information about the MessageLogger action provider, refer to User's Guide and Reference:
<eventRule name="PROCESSES" ruleType="filter" isDraft="no">
	<eventCondition name="twsProcMonEvt1" eventProvider="TWSApplicationMonitor"
eventType="TWSProcessMonitor"> <scope> AGENT, BATCHMAN DOWN </scope> <filteringPredicate> <attributeFilter name="ProcessName" operator="eq"> <value>process_name1</value> </attributeFilter> <attributeFilter name="TWSPath" operator="eq"> <value>TWS_path</value> </attributeFilter> <attributeFilter name="Workstation" operator="eq"> <value>workstation_name</value> </attributeFilter> <attributeFilter name="SampleInterval" operator="eq"> <value>sample_interval</value> </attributeFilter> </filteringPredicate> </eventCondition> <action actionProvider="MessageLogger" actionType="MSGLOG" responseType="onDetection"> <scope> OBJECT=AAAAAAA MESSAGE=TWS PROCESS DOWN: %{TWSPROCMONEVT1.PROCESSNAME}
ON %{TWSPROCMONEVT1.TWSPATH} </scope> <parameter name="ObjectKey"> <value>object_key</value> </parameter> <parameter name="Severity"> <value>message_severity</value> </parameter> <parameter name="Message"> <value>log_message</value> </parameter> </action> </eventRule> </eventRuleSet>
Is the name of the process to be monitored. You can insert more that one process name, as follows:
<attributeFilter name="ProcessName" operator="eq">
Is the directory containing the Symphony file and the bin directory.
Is the workstation on which the event is generated.
Is the interval, expressed in seconds, for monitoring the process status.
Is a key identifying the object to which the message pertains.
Is the severity of the message.
Is the message to be logged.