[Version 6.0.2]
WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Service integration notification events

You can monitor your service integration environment 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 a .html file that is installed in the install_root/web/mbeanDocs directory, where install_root is the root directory for the installation of IBM WebSphere Application Server. The .html files for service integration MBeans have names that begin with ‘SIB’. For example:
install_root/web/mbeanDocs/SIBMessagingEngine.html
The following service integration MBeans have notification events:

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 install_root/web/apidocs/SIBNotificationConstants.html file.
Properties Specific for each event generated. These are key value pairs of strings which 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 install_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
[Version 6.0.2] Enabling or disabling service integration notification events

Concept topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cji_si_events.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)