Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Getting started with record and replay in WebSphere Message Broker V8

Steve Haskey (haskey@uk.ibm.com), Software Engineer, WebSphere Message Broker UI Development team, IBM
Photo of Steve Haskey
Steve Haskey has worked for IBM for 12 years, both in California and the UK, on a number of WebSphere middleware products. You can contact Steve at haskey@uk.ibm.com.
Peter Masters (pmasters@uk.ibm.com), Software Engineer, WebSphere Message Broker Development team, IBM
Photo of Peter Masters
Peter Masters has worked for IBM for 13 years at the IBM Software Lab in Hursley Park, United Kingdom. His product expertise includes CICS, WebSphere Application Server, and WebSphere Message Broker. You can contact Peter at pmasters@uk.ibm.com.
Anton Piatek (anton.piatek@uk.ibm.com), Software Engineer, WebSphere Message Broker Development and Test team, IBM
Photo of Anton Piatek
Anton Piatek is a Software Engineer on the WebSphere Message Broker Development team at the IBM Software Lab in Hursley Park, United Kingdom. He has worked on many WebSphere Message Broker teams, including Development, Performance, Service, Functional Test, and Regression Test. You can contact Anton at anton.piatek@uk.ibm.com.
Dominic Storey (dstorey@uk.ibm.com), Software Engineer, WebSphere Message Broker Development team, IBM
Photo of Dominic Storey
Dominic Storey is a Software Engineer on the WebSphere Message Broker Development team at the IBM Software Lab in Hursley Park, United Kingdom. He has over 15 years of development experience on WebSphere MQ, WebSphere Message Broker, and related messaging technologies. You can contact Dominic at dstorey@uk.ibm.com.

Summary:  WebSphere Message Broker V8 introduces the new record and replay feature, which lets you record and view messages for audit or problem determination purposes, and replay them after problem resolution or other downtime issues. This tutorial shows you how to use event monitoring to emit a message from a flow, how to configure record and replay, and how to use the new web UI to view messages that you have recorded and replay them to a WebSphere MQ queue.

Date:  05 Dec 2012
Level:  Intermediate PDF:  A4 and Letter (1714 KB)Get Adobe® Reader®

Activity:  396 views
Comments:  

Viewing and replaying messages

  1. Before looking at the web interface, you need to put a message on the INQ queue so that you can see that it has been recorded into the database. The simplest way to do this is to use MQ Explorer and select INQ from the list of queues. Right-click the queue and click Put test message. At the prompt, enter some content data for a message: Put a test message to the INQ queue
  2. You have now recorded your first message to the database. If it is not already open, start up the Web Administration Interface by going to http://localhost:4414: Initial view of web interface
  3. In the left-hand navigator, open the Data section and select DefaultCaptureStore. If it is not visible, check that the egForView property is defined as a valid execution group in the configurable service. You should see that a message has been recorded: A message is visible in the data viewer

    If you do not see a message, verify that the mqsichangeflowmonitoring command has been run, that the DataCaptureSource and DataCaptureStore definitions are correct, and that the database is defined and available in ODBC.

  4. You can customize your data viewer by choosing columns, changing the column names and order by clicking Customize to customize the view on a per-DataCaptureStore basis, regardless of user.
  5. You are now ready to replay a message to a destination, which was defined using the INQ DataDestination configurable service above. When a message is replayed, it will be sent to the defined endpoint (the queue called INQ). Since this queue is the input for the flow, the replayed message will be re-recorded and become visible in the Data Viewer. To replay the message, select the check box to the left of the messages you want to replay and then click Mark for replay, which takes you to the second tab, where you can see your chosen messages and select the destination to play them to.
  6. Click the green arrow next to a message to replay one, or select Replay all at the top of the screen: Select a message to replay it.
  7. Having successfully replayed a message, change from the Replay list tab to the Data viewer tab and click Refresh on the viewer. You will now see another message, which is the replayed message having been re-recorded by the flow.
  8. Replay the message again, but this time, make the target flow (TestFlow) fail the message and create a message on the catch terminal by put-inhibiting the flow's output queue. You can either use MQ Explorer as described above, or run the following command inside runmqsc:
    ALTER QLOCAL(OUTQ) PUT(DISABLED)

    The message failed when replayed
  9. You now have four messages in the Data Viewer. Message 1 is the original recorded message, which you replayed to create Message 2. This message was injected into the original flow, emitted from the out terminal, and recorded as Message 3. But it then failed to be put to OUTQ and therefore went to the catch terminal as Message 4. Now that you have multiple messages in the Data Viewer, you can experiment with message filtering, and look at the captured message payload and exception information. When you have finished, remember to put-enable the OUTQ.

6 of 10 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=850776
TutorialTitle=Getting started with record and replay in WebSphere Message Broker V8
publish-date=12052012
author1-email=haskey@uk.ibm.com
author1-email-cc=
author2-email=pmasters@uk.ibm.com
author2-email-cc=
author3-email=anton.piatek@uk.ibm.com
author3-email-cc=
author4-email=dstorey@uk.ibm.com
author4-email-cc=