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
Results of generating monitor models from WebSphere Message Broker applications
After you generate a monitor model based on application monitoring information from WebSphere Message Broker, the monitor model contains elements that correspond to the monitoring templates and inbound events that you selected. The Application element field shows the display name of the event source in the application that is linked to this monitoring context. If any of the elements in the monitoring context were generated from templates, the templates are shown in the table.
The created monitor model contains:
- Inbound events for each event source that you selected in the main message flow. Inbound events for terminal events are defined in an event group that has the name of the node.
- Event parts for each inbound event where possible, based on the XPath queries that you defined in the message flow to add application data to your event.
- A key based on the transaction ID.
- A termination trigger that fires when a transaction end or transaction rollback event is received, if these events are defined.
If a message flow has subflows, the transaction start and end events of input nodes in the subflow appear at the top level in the hierarchy, directly under the monitoring context, the same as the input nodes of the message flow. The names of the subflow events have the parent flow name and the subflow node name as a prefix.
If an event part is not associated with a schema in the WebSphere Message Broker toolkit, the event part is generated with the type xs:string. You can treat it as a string, or define a new type using the XML schema editor in the development toolkit and change the xs:string to the new complex type.
If you need to add new event parts to any of the inbound events, click Add on the Event Type Details box for the inbound event and browse to the schema and event part that you want to add.
Event sources for transaction events
When you have configured event sources for transaction events, you must separately identify the transaction start and transaction end events that are issued following message flow error handling, to differentiate them from the transaction start and transaction end events that are emitted when a message is successfully processed. One way to identify these events is to create an event source on the Failure terminal of the Input node. You can then use this event source to identify the events emitted when the rolled-back message is successfully sent down the Input node failure terminal, as follows:
- Create an event source on the failure terminal of the Input node in the WebSphere Message Broker toolkit.
- In the Business Monitor development toolkit, open the Monitor Model editor.
- In your monitor model, create a metric of type String named, for example, EventType, with a default value of Successful.
- Create triggers for:
- A failure terminal event.
- A transaction rollback event.
- In the EventType metric, create additional metric value expressions that set the metric value to:
- Failure when the failure terminal event trigger is fired.
- Rollback when the transaction rollback event trigger is fired.
- On the dashboard, filter out events that have EventType set to Failure, as follows:
- Select Configure from the Add Widget menu.
- Click Add and set metric to EventType, Operator to in, and Value to Successful, Rollback.
Generate monitor models from WebSphere Message Broker message flows
Related tasks:
Generate monitor models based on application monitoring information from WebSphere Message Broker
Related reference:
Common monitoring templates for WebSphere Message Broker message flows