IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Record and replay

For audit or problem determination purposes, you can record data to a database, then view it, and replay it.

If you need an audit record of messages that pass through the broker, you can record those messages. You might also want to record messages if you need to keep a history of messages for development and test purposes, or to help in problem determination.

To determine which data is recorded, you must configure monitoring on the message flow. Data is stored in a database, which can be an Oracle, Microsoft SQL Server, or DB2® database. You must create a data source, then use a configurable service to define the data source name to use when recording data.

After you have recorded data, you can view it in several ways. By using the web interface, you can view a list of recorded messages, or you can view details of a specific message. You can also view recorded data by using the IBM® Integration API or the IBM Integration Bus Representational State Transfer (REST) API.

You can replay a message to a WebSphere® MQ queue by using the web interface or IBM Integration API. You can also replay the message to another message flow for testing or problem determination.

Recording events from WebSphere Application Server

You can record events emitted by WebSphere Application Server when it is in a service mapping configuration. The WebSphere Application Server administrator must take the following actions:
  1. Supply the topic for the DataCaptureSource; otherwise configuration in IBM Integration Bus is exactly the same as for other events.
  2. Configure a JMS connection to the queue manager.
See WebSphere Application Server documentation for more information.

bj23550_.htm | Last updated Friday, 21 July 2017