You can monitor your 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 Java Management Extensions (JMX) resources. As part of the JMX architecture, the MBeans can have notification events, which you can incorporate into your own system management application to monitor activities, such as the starting up of a messaging engine, across your 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 WebSphere Application Server implementation of the JMX framework, see Java Management Extensions (JMX).
Each WebSphere Application Server MBean is documented in the Mbean interfaces section of the Information Center. You 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".
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. |