You can use the command line interface to change some of the monitoring properties of the deployed message flow:
mqsireportflowmonitoring MB8BROKER -e WBMonitorEventsExecGroup -f TotalPurchaseOrderFlow -n
The mqsichangeflowmontoring command changes the enable and disable state of a configured event source that is defined in a message flow. Issue the following command to disable the event sources in the two MQOutput nodes:
mqsichangeflowmonitoring MB8BROKER -e WBMonitorEventsExecGroup -f TotalPurchaseOrderFlow -s GoldOrderTotal.terminal.in -i disable
mqsichangeflowmonitoring MB8BROKER -e WBMonitorEventsExecGroup -f TotalPurchaseOrderFlow -s RegularOrderTotal.terminal.in -i disable
This action disables the event source in the GoldOrderTotal and RegularOrderTotal MQOutput nodes.
mqsireportflowmonitoring MB8BROKER -e WBMonitorEventsExecGroup -f TotalPurchaseOrderFlow -x -p <output file name>
The output from this command is found in the TotalPurchaseOrderFlowProfile.xml file in the WBMonitorEventsProject.
By editing this file, using an XML editor, you can change the event source configuration for a node. For example, to remove purchaseOrderID from the Transaction start event remove the following code:
<profile:complexContent> <profile:payloadQuery profile:queryText="$Body/PO:purchaseOrder/PO:purchaseOrderID"> <profile:prefixMapping profile:prefix="PO" profile:URI="http://www.ibm.com/ProcessOrder" /> </profile:payloadQuery> </profile:complexContent>
mqsicreateconfigurableservice MB8BROKER -c MonitoringProfiles -o ComplexContentMonitoringProfile
mqsichangeproperties MB8BROKER -c MonitoringProfiles -o ComplexContentMonitoringProfile -p ComplexContentMonitoringProfile.xml -n profileProperties
mqsichangeflowmonitoring MB8BROKER -e WBMonitorEventsExecGroup -f TotalPurchaseOrderFlow -m ComplexContentMonitoringProfile -c active
A skeletal example of a monitoring profile is also included in the MonitoringProfile.xml file in WBMonitorEventsProject.
The sample contains a monitor model, WMBMonitorEventsModel, which is created by using the Export option in the WebSphere Message Broker Toolkit to export monitoring information about the message flow. This section describes the steps to create the monitor model.
The exported .zip file is created in the location specified. A log folder is created in the Message Broker project. This folder contains a log of the generation of the monitoring information from the message flow.
A monitor model called WBMonitorEventsModel is created. Events Parts are created for each XPath query that is used to add application data to the event in the message flow definition. You can now create metrics and key performance indicators (KPIs) to monitor this application data.
For more information about creating metrics and KPIs in a monitor model
in WebSphere Business Monitor, see
IBM WebSphere Business Process Management Information Center.