WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Monitoring scenarios
Events can be used to support transaction monitoring, transaction auditing and business process monitoring.
Transaction monitoring and auditing
The events published by WebSphere® Message Broker can be written to a transaction repository, creating an audit trail of the transactions that are processed by a broker. A transaction repository can be used for monitoring, auditing and replay of transactions. Bitstream data can be included so that failed transactions can be resubmitted. You can perform the following tasks to set up transaction monitoring and auditing.- Configure events for your transactions
- In most cases bitstream information is not sufficient to allow querying of the logged transactions. Key fields and other correlation data can be extracted from the message payload and placed into the wmb:applicationData/wmb:simpleContent or wmb:applicationData/wmb:complexContent element of the event. The logging application or message flow can extract these fields and log them with the message bit stream.
- Subscribe to the event topic and write events to a repository
- You can create a message flow, or any WebSphere MQ application, that subscribes to the event topic and writes events to a relational database. The details of the database schema depend on the requirements of your organization, for example the number of key fields and transaction IDs.
Business process monitoring
The events published by a broker can be monitored by WebSphere Business Monitor. Important fields in the message payload can be added to the events emitted by your message flows, allowing them to be monitored. You can use the following items to help you use WebSphere Business Monitor to monitor your message flows:- Message-driven bean
- The events must be submitted to the CEI repository for WebSphere Business
Monitor to monitor them. A message-driven
bean is supplied for this purpose. The message-driven bean, which
runs in WebSphere Application
Server, subscribes
to the event topic and writes events that match its subscription to
the CEI repository as Common Base Event events.
A message-driven bean is supplied with the WebSphere Business Monitor sample. For instructions about how to install and configure the sample message-driven bean, see Running the WebSphere Business Monitor sample.
- WebSphere Business Monitor Model
- WebSphere Message
Broker includes an example
monitor model for use with WebSphere Business
Monitor.
This model demonstrates how to monitor transaction events and terminal
events, including events that capture data from the input message
and output message. Modify the model to match your actual events and
message formats.
A WebSphere Business Monitor Model is supplied with the WebSphere Business Monitor sample. For instructions about how to install and configure the sample WebSphere Business Monitor Model , see Running the WebSphere Business Monitor sample.