What are actions and how to define them


This section describes actions, which are used to alert the user that a condition has become true. This section includes:

The actions the IBM MQ Event Service can take are:

  • Send a Monitor Console alert
  • Execute an external program
  • Send an e-mail message
  • Log a message to a file
  • Log an SQL message to a file
  • Write to the journal (database)
  • Send a message to a IBM MQ queue
  • Send an SQL message to a IBM MQ MQ queue
  • Send a message to the Tivoli Event Console
  • Send a message to HP OpenView
  • Delete a transient topic
  • Use time to delay a message

Actions have one and only one start node and many end nodes. Every input or output terminal on a node must be connected to something. Each action node has two outputs: success and failure. Depending on the outcome of the action node execution flows left (success) or right (failure). Hold the mouse over the terminal so see a tool tip labeling which is success and which is failure. Both flows of execution (success and failure) are terminated.

See Action examples for further details of how an action is created.

In actions that you can insert a script you can send formatted output with your action. See Using formatted inputs and outputs for further information.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*