Event Management › Implementation Process › Message Traps and Actions › Message Routing to Remote Hosts

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 send the messages to.

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 defined for CAICCI remote communication.

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

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

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

• Select from several priorities, levels, and facilities of messages.
• Route messages by level or priority to different devices.
• Route messages by level or priority to different hosts.
• Receive messages from other hosts for local display.

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 display twice on those remote computers. This is because they were sent there twice, once by the Berkeley syslog daemon and again by Event Management.