Through message record and action policies, you select a message based on content and then define the appropriate action. A possible message action is to instruct Event Management to perform an action on a specific (and potentially remote) machine. You can easily define an action such as sending the message to a remote machine or initiating a command on the remote machine. For example, you can identify a network security event or a tape mount event for routing to an alternate machine simply by defining Event Management policies to that effect.
Actions to be performed on remote nodes can be done synchronously or asynchronously. Before proceeding to the next action, action processing waits for the remote action to complete and return a completion code. 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.
|
Copyright © 2010 CA.
All rights reserved.
|
|