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:  

Setting up the Web UI

To start the Web UI, you must create a broker to host it, and then apply some configuration properties against that broker.

Creating a broker

If you've already created a broker, you can skip this step. A quick way to create a broker is via the Default Configuration Wizard in the WebSphere Message Broker Toolkit:

  1. Start the Default Configuration Wizard from the WebSphere Message Broker Toolkit Welcome page, which is displayed the first time you start the WebSphere Message Broker Toolkit. If the Welcome page is not displayed, open it in the WebSphere Message Broker Toolkit by clicking Help => Welcome.
  2. Click Get Started on the Welcome page, then click Create the Default Configuration.
  3. Click Start the Default Configuration Wizard.
  4. The welcome page of the Wizard describes what is about to happen. Click Next to continue. The Wizard checks whether the default configuration has already been created.
  5. After the Wizard runs successfully, click Next and then Finish. The wizard creates default broker named MB8BROKER.

Configuration properties

You can configure the Web UI to use either HTTP or HTTPS on any port. This tutorial assumes that the default broker's name is MB8BROKER and that you want to use HTTP on Port 4414, which is set by default. If you have another broker, then you may need to set the port manually. If you want the Web UI to use a another port, then change the commands accordingly.

  1. Set the HTTP port by running the mqsichangeproperties command in the command console:
    mqsichangeproperties MB8BROKER -b webadmin -o HTTPConnector -n port -v 4414

  2. To confirm that the properties have been set correctly, run the mqsireportproperties command, as shown below:
    mqsireportproperties MB8BROKER -b webadmin -o HTTPConnector -a

    This command produces a response similar to this truncated example:

    HTTPConnector
    uuid='HTTPConnector'
    address=''
    port='4414'
    allowTrace=''
    . . . 

  3. By default, the Web Administration Interface is enabled for new brokers. For migrated brokers you must enable the Web Administration Interface yourself. To do so, run the mqsichangeproperties command in the command console:
    mqsichangeproperties MB8BROKER -b webadmin -o server -n enabled,enableSSL 
        -v true,false

  4. To confirm that the properties have been set correctly, run the mqsireportproperties command, as shown below:
    mqsireportproperties MB8BROKER -b webadmin -o server -a

    This command produces a response similar to this example:

    server=''
    uuid='server'
    enabled='true'
    enableSSL='false'

  5. To ensure that the changes take effect, restart the broker by running the following commands in the command console:
    mqsistop MB8BROKER
    mqsistart MB8BROKER

Connecting to the web UI

After a few seconds, the Web UI should be up and running. Using either Mozilla Firefox V3.6 or later, or Microsoft® Internet Explorer V8 or later, you can open the Web UI using the URL http://serverAddress:4414/. For example, if your broker is running on your local host, the URL would be 100%">http://localhost:4414: Web UI

2 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=