Event Management › Implementation Process › Message Traps and Actions › How Remote Actions Are Processed

How Remote Actions Are Processed

Through message record and action policies, you select a message based on content and then define the desired action. One of the message action capabilities is to instruct Event Management to perform an action on a specific (and potentially remote) computer. Actions such as sending the message to a remote computer or initiating a command on the remote computer are accomplished easily. For example, you can identify a network security event or a tape mount event for routing to an alternate computer simply by defining Event Management policies to that effect.

Actions that must be performed on remote nodes can be done synchronously. Action processing waits for the remote action to complete and return a completion code before proceeding to the next action. This means that the completion code received from the remote action can be tested as part of a message action and used to control subsequent processing. Remote actions are not attempted if the target node is known to be unreachable.