Interacting with External Event Systems › Using the CA NSM Interface › Communication Between Event Traffic Controller and Event Manager › Receiving Events From Event Manager › Types of Sessions

Types of Sessions

During the configuration of the Event Traffic Controller, rules are automatically generated for the sessions that are associated with the selected event types. The session definitions for the special Event Traffic Controller sessions are automatically defined in the session definition set. Each of the message streams described in the previous section are funneled into one of the following sessions:

• UNI_MSGS—User-filtered messages are sent to this session. The only generated rule associated with this session logs the message. You can add rules that match messages in this session, enabling CA Automation Point to take action upon any event that is captured by CA NSM Event Manager.
• NM_REQUESTS—Notification messages are sent to this session. The generated rules associated with this session log the message and launch an appropriate NMFIND command based on the fields that are contained in the message. In this manner, CA NSM Event Manager can indirectly issue pages, voice, and e-mail notifications. You can use this method to issue notifications on behalf of other CA NSM options that have the ability to write messages to CA NSM Event Manager, such as CA Service Desk.

  Note: For information about the CA Service Desk interface with CA NSM Event Manager, see the CA Service Desk documentation.

  This session is also used for NMFIND requests that originate from CA OPS/MVS.

• SNMP_TRAPS—SNMP messages are sent to this session. The only generated rule associated with this session logs the message. You can add rules that match the messages in this session, enabling CA Automation Point to take action upon any SNMP event that is captured by CA NSM Event Manager.
• HOST_COMMANDS—SESSCMD messages are sent to this session. The generated rules associated with this session log the message and execute the supplied command in a specified CA Automation Point session. In this manner, CA NSM Event Manager can indirectly issue z/OS commands.
• WIN_EVENTS—Messages from a Windows event log are sent to this session. The only generated rule associated with this session logs the message. You can add rules that match the messages in this session, enabling CA Automation Point to take action upon any Windows event.

  Note: These session names are the default names, and should normally not be changed.