Previous Topic: How Remote Actions Are Processed

Next Topic: Message Action Definitions

Message Routing to Remote Hosts

Routing messages to a remote computer through message record and action policies is most easily achieved by creating a message record that traps those events and a message action that uses the FORWARD action keyword and specifies the remote node to which you want the messages sent.

Because one message can have many message actions, you can send messages to multiple computers. You can specify the name of any computer that is currently defined for CAICCI remote communication.

Note: For more information about CAICCI configuration, see Common Communications Interface.

On z/OS UNIX platforms, one source of event messages is the Berkeley syslog daemon, which can route messages to a CA Common Services for z/OS server for processing, even those originating from servers not running CA Common Services for z/OS.

Event Management takes advantage of the powerful messaging facilities provided by the syslog daemon to:

Note: For more information about configuring the Berkeley syslog daemon, see the Post-Installation Tasks for Event Management in the Installation Guide.

Note: If you use both the Berkeley syslog daemon and specific message action policies to reroute the same messages to the same remote computers, those messages will display twice on those remote computers because they were sent there twice, once by the Berkeley syslog daemon and again by Event Management.