IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models > Generate monitor models > Generate from applications outside the workspace > WebSphere Message Broker message flows

Generate monitor models based on application monitoring information from WebSphere Message Broker

After exporting the required application monitoring information from WebSphere Message Broker V7.0, you can use the information to generate a monitor model for monitoring the message flow.

You must have exported the application monitoring information from WebSphere Message Broker. For instructions, see Create a monitoring model for use by Business Monitor in the WebSphere Message Broker information center

To generate a monitor model:

Procedure

1. In the Business Monitoring perspective, right-click the Project Explorer view and click Import.

2. In the Import wizard, select Business Monitoring > Application monitoring information .zip file.

3. Click Browse and navigate to the file that was exported from WebSphere Message Broker. Click Next.

4. Select a location for the new monitor model. You can select a project from the list of existing business monitoring projects or type a name to create a new business monitoring project. After you have selected or created a project, type a name for the new monitor model and click Next.

5. Select the elements that you want to monitor. In the tree showing the application to be monitored, click any node to see the template and event information for that element. The Monitoring Templates tab shows the common monitoring templates that are available for the selected element. Choose one or more templates to create the appropriate monitoring constructs in the generated model. (See Common monitoring templates for WebSphere Message Broker message flows for information about the available templates.) The Emitted Events tab shows all of the event sources that are defined for the flow or node that you have selected.
   • Transaction events are shown when you select the flow name.
   • Terminal events are shown when you select the appropriate node.

   To include data from emitted events, click the check box for any of the event sources defined for the flow or node that you want to use in the monitor model. You can either select events individually, or you can right-click in the tree at any level and click Select all events at this level or Select all events at this level and below.

   You cannot remove an event if you have chosen a template that requires that event. The event is shown as selected but unavailable.

   After you have finished selecting events and templates, click Next.

6. Select how the monitored elements will be implemented. In general, accept the default implementations. The tree on this page shows only the elements you have chosen to monitor. Specifically, the tree shows the event sources that you selected events for and the event sources that are ancestors of those event sources. If you did not select any templates or events for the ancestor event sources, the default implementation is None whenever possible. (It is not always possible to specify None because some event sources contain information that is needed by events that are emitted from descendent event sources.) In the second column, select the monitoring implementation that you want for each element. Based on the element, you might have some or all of the following choices:
   • None. The element will not be represented in the generated monitor model. This option is available only if there are no inbound events at the selected or descendant levels that require the selected element to be present. If you click this option, all descendant levels are also set to None.
   • Monitoring context. A monitoring context will be created for the element, complete with keys and a corresponding cube. This option is available only if the selected application element has a lifecycle and an identity that events can use to find it.
   • Event group. An event group will be created for the element. All inbound events at the selected level and all descendant levels will be collected in this new event group (that is, they will all be at the same level in the event group). This option is available only if there are no templates chosen that require a monitoring context at the selected or any descendant levels.

     If you choose this option, all descendants are set to "–" because all of the associated events will be collected into the event group. (See When to choose monitoring contexts versus event groups for more information.)

7. To see a preview of the monitor model that you chose to create, click Next. To make changes and see how they affect your model, click Back to make changes and then click Next.

8. When satisfied with your selections, click Finish. You are asked whether you would like to switch to the Business Monitoring perspective to begin editing the newly created monitor model. To open the new monitor model in the Monitor Model editor, select Yes.

   Important: Confirm that the Build Automatically option on the Project menu is enabled. If it is not, perform a clean build on the monitor model project after it is generated to ensure that the monitor model is validated.

Results

The newly created monitor model contains automatically generated elements that correspond to the common monitoring templates and inbound events that you selected.

With inbound events already created for each of your event sources and event parts defining the structure of each WebSphere Message Broker event, you can go on to create any further metrics, stopwatches, and key performance indicators (KPIs) that you need.

Generate monitor models from WebSphere Message Broker message flows

Related reference:
Common monitoring templates for WebSphere Message Broker message flows
Results of generating monitor models from WebSphere Message Broker applications