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, Running event-driven workload automation.

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, MessageLogger actions:
<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>
where:
process_name
Is the name of the process to be monitored. You can insert more that one process name, as follows:
<attributeFilter name="ProcessName" operator="eq">
					<value>agent</value>
					<value>batchman</value>
				</attributeFilter>
TWS_path
Is the directory containing the Symphony file and the bin directory.
workstation_name
Is the workstation on which the event is generated.
sample_interval
Is the interval, expressed in seconds, for monitoring the process status.
object_key
Is a key identifying the object to which the message pertains.
message_severity
Is the severity of the message.
log_message
Is the message to be logged.