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

Creating a monitor model for WebSphere Business Monitor V7 or later

To create a monitoring model for WebSphere® Business Monitor V7 or later, export monitoring information from WebSphere Message Broker.

Before you start:

To create a monitoring model, you export your message flow as a .zip file from WebSphere Message Broker, then import it into WebSphere Business Monitor.

  1. Export your message flow from WebSphere Message Broker.
    1. In the WebSphere Message Broker Toolkit, right-click the message flow or Message Broker project, and click Export. The Export wizard starts.
    2. Click Business Monitoring > Application monitoring information, then click Next.
    3. Select the flows from which you want to export monitoring information, and specify a file name.
    4. Optional: Specify that an existing file should be overwritten without warning.
    5. Click Finish.
      A .zip file is created that contains the following monitoring information about the message flow:
      • All monitoring information that is defined in the message flow files
      • The WMBEvent.xsd file, which is the schema for the emitted event
      • All .xsd files in the message sets that are referenced by the selected flows
      A report of the export is written to file flowProjectName_batchgen.report.txt in the log directory of the Message Broker project.
  2. Import the exported .zip file into WebSphere Business Monitor V7 or later.
    1. In the Business Monitoring perspective of WebSphere Business Monitor, right-click the Project Explorer view and click Import.
    2. Complete the instructions in the Generate Monitor Model wizard.
      Select one or more of the following templates, depending on the event sources in your message flow:
      • Average Transaction Duration This template is available if you have created transaction.Start, transaction.End, and transaction.Rollback event sources. If you select this template, a metric and stopwatch are created for you in the monitor model showing the Average Transaction Duration, and a key performance indicator (KPI) is created using the data from this stopwatch.
      • Number of Failed Transactions This template is available if you have created transaction.Rollback event sources. If you select this template, metrics are created for you in the monitor model showing the number of failed transactions and the failed transaction time (this has a default value of 1 January 9999 01:00:00.) A measure and dimension are also created for use in creating multidimensional reports. See Defining Dimensions in the WebSphere Business Monitor information center.
      • Message Flow Correlation This template provides information about the broker (such as broker name, execution group name, parentTransactionID, globalTransactionID). You can display this information in a Business Space Dashboard with other metrics and key performance indicators. Because these metrics are used in the correlation expression for the inbound events defined, select this template only if the events for a specified monitoring context are from the same execution group.
      For detailed instructions for using WebSphere Business Monitor to monitor message flows, see Generating monitor models based on application monitoring information from WebSphere Message Broker in IBM® WebSphere Business Process Management Version 7.0 Information Center.
  3. Install and configure a message-driven bean in WebSphere Business Monitor.

    For WebSphere Business Monitor to monitor events, they must be submitted to the CEI repository by using a message-driven bean. 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.

  4. Ensure that the event topic has a subscription registered against it for the message flow.
  5. Create a WebSphere Business Monitor dashboard.

    For detailed instructions see IBM WebSphere Business Process Management Version 7.0 Information Center. This step is also demonstrated by the sample (Running the WebSphere Business Monitor sample).

  6. In WebSphere Message Broker, configure event sources by using either monitoring properties or a monitoring profile. For more information, see the appropriate topic:
  7. Ensure that the appropriate events are enabled.

    For more information, see Enabling and disabling event sources.

  8. In WebSphere Message Broker, activate monitoring for the deployed message flow.

    For more information, see Activating monitoring.

When you have completed these steps, you can send messages through the deployed message flow and view the events in the WebSphere Business Monitor dashboard.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:28


Task topicTask topic | Version 8.0.0.7 | ac60394_