Event Management › Automation › Automating Through Rules › Rules Actions

Rules Actions

CA Automation Point provides various action capabilities that can be triggered by rules processing to control the following types of activity:

• Synchronous activity that occurs and must complete in real time with the processing of each message
• Asynchronous activities set up in real time, but which do not restrict ongoing message processing

The action capabilities can be grouped into the following categories:

• Display actions that control ongoing attributes of the CA Automation Point depiction of monitored systems. These include the coloring, highlighting or lowlighting, prefixing, and rewording of received messages and controlling whether the received message is displayed in theCA Automation Point Merged Msg window.
• Logging actions that control the logging and printing of received messages. These actions control whether the message is sent to the CA Automation Point message log file or whether the message is printed on the local printer.
• Notification actions that control the following:
  • Notifying local operators with auditory alarming when a given event occurs
  • Issuing messages to either an operator or the automation log
  • Notifying someone remotely through Notification Manager
  • Forwarding messages, session information, or other user-specified data to the CA NSM Event Console
• Automation actions, which act as triggers and constraints on the execution of rules. In addition to the primary rule types of message pattern matching and time-of-day, you can use actions to do the following:
  • Control time intervals for rule execution
  • Control the maximum number of times a rule may execute absolutely
  • Control the maximum number of times a rule may execute in a fixed time interval

  Note: Conditional rule activity can also be controlled by data comparison.

• System event actions that let you automatically issue commands to:
  • The operating system of monitored systems
  • Applications running on monitored systems
  • The operating system of the CA Automation Point workstation
  • Reply to WTORs on monitored systems
  • Dynamically write and read status variables
  • Run basic command sequences to configure the behavior of monitored systems
  • Run complex procedural activity
  • Write messages or other important data to a Program-to-Program Queue (PPQ) for processing by a REXX program on the same or another workstation