Record and Replay framework with WMBEvent Monitoring

Record and Replay framework with WMB Event Monitoring

This framework can be used to Record/log the messages and Replay the messages/files using Event monitoring in Websphere message broker.

How it differs from existing common logging and Replay frameworks?

Existing common logging frameworks logs the messages for each message that gets processed by a message flow. Similarly, based on some replay flag set, the messages are replayed at the time of error handling in existing error handling frameworks.

“Record and Replay framework with WMB Event Monitoring” can do additional tasks below

 Can decide when and where logging should happen at runtime

 Can decide whether should log all messages or can choose specific messages for logging for a message
flow at runtime

 Can decide what messages should be replayed instead of replaying all the messages failed for a message
flow at runtime

How it gives advantage over WMB 8 version Record and Replay concept?

WMB 8 version also has this Record and Replay by creating the configurable services and corresponding database. It is GUI window to see the logging and can select the messages failed to replay from GUI.
Here with Record and Replay framework using Event Monitoring allows to choose the logging instead of logging all the transactions for each of the message flow/service at runtime and similarly can choose Replay also.

Technology stack required:

 This framework has a package of two WMB message flows, one for logging and another for Replay.

 A database that is compatible with Websphere Message Broker can be used
o To define rules for logging and replay which allows us to choose the logging and replay for each of
our service.
o To log the messages

 MQ for creating subscription queues for Event monitoring

How this framework works?

 Record Message Flow

It does success logging and failure logging to database using the Event monitoring message for each service based on rules defined in database/cache. Caching mechanism is used to load the rules in cache and can be refreshed when required from web browser.

 Replay Message Flow

It is triggered from web browser with Service name or Application/Message flow name to replay failures only for specific service based on rules defined in database. Caching mechanism to load the rules in cache and can be refreshed when required from web browser.

Replay is limited to no of messages as per REPLAYLIMIT in database and also based on UDP flag.