Creating a monitor model for WebSphere Business Monitor V6.2

In WebSphere Business Monitor V6.2

This section outlines the steps you need to take in WebSphere Business Monitor. See the documentation for WebSphere Business Monitor for full and up-to-date details.

1. In the WebSphere Business Monitor development toolkit, create a Monitor Model.

   Import the WMBEvent.xsd schema and any schemas describing complex data that were exported from IBM Integration Bus, then create a monitor model. You see errors, because the model is currently empty. You also see a key, which you can rename, for example to LocalTransactionID.

2. Create WebSphere Business Monitor inbound events.

   A monitoring context definition is the term used by WebSphere Business Monitor to describe all the data that should be collected about an entity (such as a transaction or business process). Each runtime instance (referred to as a monitoring context instance) collects information from inbound events and stores this information in fields that represent the business measures that a monitoring context collects: metrics, counters, and stopwatches.

   You need to define an inbound event to describe each event source defined in your message flow that contains information that you want to monitor. For example, if your message flow has Transaction start, Transaction end and Transaction rollback event sources, define an inbound event for each of these event sources.

   You typically define inbound events for these three event sources because they contain information that tells WebSphere Business Monitor when the start and end of the monitoring context instance occurs. You also define inbound events to describe any event sources downstream in the flow that contain data that you want to monitor, for example in the In terminal of the MQOutput node.

   Creating inbound events typically involves the following actions:
   1. Define event parts within the inbound event.

      Event parts are XML Schema definition (XSD) types that provide information about the structure of part of an event. For an IBM Integration Bus event, define event parts to describe the different parts of the event that you want to monitor data from. For a description of the event structure, see The monitoring event.

      As a minimum, define an event part for the event described by type wmb:event. To monitor data about the source of the event (information about the message flow name, broker name), also define an event part for the eventPointData section described by type wmb:eventPointData. You might also want to define event parts to describe message payload data from the applicationData section of the event.

   2. Define a correlation expression.

      You typically correlate events on fields from the eventCorrelation section in the IBM Integration Bus event. For example, you could correlate events using the localTransactionId field from the IBM Integration Busevent.

      You must also define whether the event should create a monitoring context; create this for a Transaction start event.

   3. Optional: Define a filter condition.

      Set a filter condition. For example you might want to filter events for a specific broker, integration server, or message flow.

   4. Optional: Define the event sequence path.

      Select a field in the inbound event that can be used to set the order in which the inbound events are processed. For example, you could use creationTime from the IBM Integration Bus event.

   5. Complete the key.

      The key uniquely identifies a monitoring context instance. You can select any value for the key; for an IBM Integration Bus event, a typical value is the localTransactionId field from the IBM Integration Bus event.

3. Define the metrics.

   Having defined inbound events you can now define your metrics. Metrics hold data from the event in a monitoring context.

   You might want to define metrics that hold event source data from the eventPointData section of the IBM Integration Bus event, for example broker name or message flow name. You can also define metrics that hold event sequencing information, for example TimeStarted and TimeEnded metrics, which hold the creationTime for Transaction start and Transaction end or Transaction rollback events.

   In addition, metrics can be defined to hold application data from the IBM Integration Bus event.