IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Use business monitoring with process applications
Monitor models and active snapshots
A process application (including its tip and any active snapshots) can have a generated monitor model. In addition, its processes can be monitored by one or more custom monitor models (created in IBM Integration Designer),
The following sections provide more details on using custom and generated monitor models with multiple process application snapshots on the Process Center server and a process server. The information assumes that the process application supports IBM Business Monitor process monitoring. The current setting for the Enable process monitoring through IBM Business Monitor option on the Process Apps Settings page persists in each snapshot you take. It determines whether a monitor model is generated and deployed with the snapshot.
Process Center server
When you click File > Update Tracking Definitions, the process application tip and all other active snapshots are examined. A single, cumulative monitor model is generated based on the tip and all active snapshots that have the Enable process monitoring through IBM Business Monitor option set. This cumulative monitor model processes the tracking events from the tip and all active snapshots that have the option enabled, and is deployed as the new active monitor model version for the current process application.
The lifecycle for a custom monitor model is determined by the lifecycle of the process application it is associated with. If the current process application has both a generated and a custom monitor model, both are deployed.
Process server
When you deploy a snapshot on a test or production process server, this snapshot and all other active snapshots are examined as a group. A single, cumulative monitor model is generated based on all active snapshots that have the Enable process monitoring through IBM Business Monitor option set. This cumulative monitor model processes the tracking events from all active snapshots, and is deployed as the new active monitor model version for the current process application.The lifecycle for a custom monitor model is determined by the lifecycle of the process application it is associated with. If the current process application has both a generated and a custom monitor model, both are deployed.
Example: Generated monitor model for multiple active snapshots
In this example, the OrderTracking process application is enabled for process monitoring with IBM Business Monitor and the business programmer has clicked File > Update Tracking Definitions in the Process Center or Process Designer to generate and deploy a monitor model (its ID is bmon_ORDTRK_MAIN and its timestamp is 2011-01-01T12:00:00+0400).
The business programmer plays back the process; the monitor model captures the performance data and sends it to the dashboard.
After some time, the business programmer realizes that the process needs to be updated. He makes the necessary changes. He then clicks File > Update Tracking Definitions, which creates a new version of the generated monitor model. The ID remains the same, but the timestamp is updated (2011-04-021T16:00:00+0400). This new version of the monitor model becomes active. Any in-flight instances are migrated from the original version to accommodate the analogous instance migration of any running BPDs.
Later, the business programmer modifies the tracking groups for the OrderTracking process application. He takes a snapshot (SS1) and deploys it to the production server ProcessServer01. During the deployment process, the server checks to see which snapshots are currently active on the server and finds none. A new monitor model is generated for the snapshot; it has the same ID as the cumulative monitor model on the Process Center server (bmon_ORDTRK_MAIN), but a new timestamp. If that this monitor model is not capturing any performance data from the snapshots on the Process Center Server; those are monitored by the existing cumulative monitor model deployed with the second snapshot.