Service integration notification events

Service integration notification events

We can monitor the service integration environment by using notification events.
Each service integration entity, such as a messaging engine or a WebSphere MQ link, is represented by an MBean. MBeans are Java objects that represent JMX resources. As part of the JMX architecture, the MBeans can have notification events, which we can incorporate into our own system management application to monitor activities, such as the starting up of a messaging engine, across the service integration configuration. Events also enable applications acting as agents for other administration networks to monitor reports and create the appropriate alerts.
For more information about the WAS implementation of the JMX framework, see Use wsadmin scripting with JMX.
Each WebSphere Application Server MBean is documented in the Mbean interfaces section of the Information Center. We can navigate to this section by expanding Reference > Programming interfaces in the Information Center navigation, and then clicking Mbean interfaces, or by doing a search for "Mbean interfaces".
The following service integration MBeans have notification events:

SIBGatewayLink

SIBMediationPoint

SIBMessagingEngine

SIBMQLink

SIBMQLinkReceiverChannel

SIBMQLinkSenderChannel

SIBPublicationPoint

SIBQueuePoint

SIBRemotePublicationPoint

SIBRemoteQueuePoint

Format of event notifications

Event notifications contain information about the event and its origin. Typically, these notifications are processed by a system management application program tailored to meet the requirements of the enterprise at which it runs. The service integration events have the following attributes:

Attribute name Attribute description
Message The message that describes the event.
SequenceNumber An identifier for the event instance, unique within a run of the application server.
TimeStamp Timestamp in milliseconds.
Type Identifies the type of event, for example a messaging engine stop event. The type is defined by constants in the app_server_root/web/apidocs/SIBNotificationConstants.html file.
Properties Specific for each event generated. These are key value pairs of strings that describe aspects of the event, such messaging engine name or number of messages on a destination. The key and value strings are defined by constants in the app_server_root/web/apidocs/SIBNotificationConstants.html file.
All service integration events will have properties for the bus name and UUID, and the messaging engine name and UUID.

Related tasks

Enable or disable service integration notification events

Attribute name	Attribute description
Message	The message that describes the event.
SequenceNumber	An identifier for the event instance, unique within a run of the application server.
TimeStamp	Timestamp in milliseconds.
Type	Identifies the type of event, for example a messaging engine stop event. The type is defined by constants in the app_server_root/web/apidocs/SIBNotificationConstants.html file.
Properties	Specific for each event generated. These are key value pairs of strings that describe aspects of the event, such messaging engine name or number of messages on a destination. The key and value strings are defined by constants in the app_server_root/web/apidocs/SIBNotificationConstants.html file. All service integration events will have properties for the bus name and UUID, and the messaging engine name and UUID.