Generated monitor model lifecycle

IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Use business monitoring with process applications
Generated monitor model lifecycle

The lifecycle of a generated monitor model is dictated by the actions you perform on its associated process application tip or snapshot.

Remember: A generated monitor model is created from the default and custom tracking definitions of a process application. It is cumulative, which means that it contains a union of all the information from the tip (if applicable) and every active snapshot.
The lifecycle for a custom monitor model (one created in IBM Integration Designer) is managed by the user and does not necessarily follow the lifecycle of a generated monitor model. It is not covered in this topic.

Playback scenarios

Table 1 describes what happens on the Process Center server when a Process Center user clicks File > Update Tracking Definitions. The resulting action depends on the setting of the Enable process monitoring through IBM Business Monitor option and whether there is an existing version of the generated monitor model.

Actions that affect monitor model lifecycle during playback
Actions taken by user Status of "Enable process monitoring through IBM Business Monitor" option Result
Click File > Update Tracking Definitions.
You must have either a snapshot or the tip open in Process Designer or the Inspector perspective in Process Designer before clicking this menu item. Otherwise, no monitor model is generated.
Enabled Send tracking definitions to Performance Data Warehouse.
Generate and deploy a cumulative monitor model for the tip and all active snapshots that have the Enable process monitoring through IBM Business Monitor option selected.
If a cumulative monitor model has already been generated and deployed, this new version (with the same ID but a different timestamp) replaces it. In-flight instances are then migrated to the new version.
When you run any process defined in the tip or an active snapshot in the Inspector view, performance data is monitored and sent to the dashboard.
Disabled If none of the activated snapshots has the Enable process monitoring through IBM Business Monitor option enabled, undeploy the cumulative monitor model from the server and purge its data.
Otherwise, generate and deploy an updated cumulative monitor model for all active snapshots that have the option enabled. The tip is excluded, because the current setting is disabled.

Test and production scenarios

Table 2 describes what happens on the test or production process server when the user deploys or undeploys a snapshot.
If the additional actions you must take in the following scenarios:

When you deploy a snapshot to a test or production server that has monitoring enabled, you must perform the following steps:

On the test or production server, authorize the users or groups to the monitor model. See the "Configuring data security" topic.
Share the generated dashboard with the users who are authorized to the model.

When you deploy a snapshot that has a custom monitor model, you must authorize the users or groups to the monitor model. See the "Configuring data security" topic.

Actions that affect monitor model lifecycle on a process server
Action taken by user Status of "Enable process monitoring through IBM Business Monitor" option when snapshot was taken Result
Deploy a snapshot to the target process server Enabled Generate and deploy a monitor model.
If there are other active snapshots with monitoring enabled, generate an updated, cumulative monitor model; it includes definitions for the union of the processes, tracking groups, and autotracked fields in the new snapshot and all other active snapshots that have process monitoring enabled. The updated cumulative model is deployed with the snapshot and in-flight instances are migrated. The previous version of the monitor model is removed, but data is not purged.
Disabled No action is taken.
The existing version of the cumulative monitor model remains active.
Deploy a new version of a snapshot to a production or test server Enabled If there are active process instances for a previous version of a snapshot, you are prompted to either leave, delete, or migrate those instances to the latest snapshot.

If you delete the instances at this point, the corresponding Monitor instances in the Business Space dashboard are not deleted.
Migrating of instances is not advised.
If you do migrate the instances forward and then complete the instances, Monitor will not know about the completion. The associated emitted events will be routed to the Monitor Failed Events queue.

Remove a snapshot from the process server Enabled or disabled No action is taken.
If there are other active snapshots on the server with process monitoring enabled, the cumulative monitor model continues to capture performance data for those snapshots.
To remove a monitor model, use the WebSphere Application Server administrative console.

Considerations when disabling monitoring

To help prevent problems, consider the following points before you disable monitoring support for a process application that previously supported it.

( Process server only) If you deploy one or more snapshots that have monitoring enabled, and then deploy a snapshot that does not have monitoring enabled, carefully consider whether you want to migrate in-flight instances to the new snapshot. Because no monitor model is generated for the new snapshot, any tracking definitions in that snapshot are not covered, and migrated business process definition instances might not be monitored appropriately during execution.
( Process Center server only) Use caution when disabling monitoring support while there are active business process definition instances.
If you disable monitoring support and click File > Update Tracking Definitions, an updated cumulative monitor model is still generated for any active snapshots that have monitoring support enabled; however, that monitor model does not necessarily include all tracking definitions in the tip. Therefore, any business process definition instances migrated to the new tip might not be monitored appropriately during execution.

Use business monitoring with process applications

Related tasks:
Generate and using a default monitor model

Related information:
Remove monitor models and data

Actions taken by user	Status of "Enable process monitoring through IBM Business Monitor" option	Result
Click File > Update Tracking Definitions. You must have either a snapshot or the tip open in Process Designer or the Inspector perspective in Process Designer before clicking this menu item. Otherwise, no monitor model is generated.	Enabled	Send tracking definitions to Performance Data Warehouse. Generate and deploy a cumulative monitor model for the tip and all active snapshots that have the Enable process monitoring through IBM Business Monitor option selected. If a cumulative monitor model has already been generated and deployed, this new version (with the same ID but a different timestamp) replaces it. In-flight instances are then migrated to the new version. When you run any process defined in the tip or an active snapshot in the Inspector view, performance data is monitored and sent to the dashboard.
Disabled	If none of the activated snapshots has the Enable process monitoring through IBM Business Monitor option enabled, undeploy the cumulative monitor model from the server and purge its data. Otherwise, generate and deploy an updated cumulative monitor model for all active snapshots that have the option enabled. The tip is excluded, because the current setting is disabled.

Action taken by user	Status of "Enable process monitoring through IBM Business Monitor" option when snapshot was taken	Result
Deploy a snapshot to the target process server	Enabled	Generate and deploy a monitor model. If there are other active snapshots with monitoring enabled, generate an updated, cumulative monitor model; it includes definitions for the union of the processes, tracking groups, and autotracked fields in the new snapshot and all other active snapshots that have process monitoring enabled. The updated cumulative model is deployed with the snapshot and in-flight instances are migrated. The previous version of the monitor model is removed, but data is not purged.
Disabled	No action is taken. The existing version of the cumulative monitor model remains active.
Deploy a new version of a snapshot to a production or test server	Enabled	If there are active process instances for a previous version of a snapshot, you are prompted to either leave, delete, or migrate those instances to the latest snapshot. If you delete the instances at this point, the corresponding Monitor instances in the Business Space dashboard are not deleted. Migrating of instances is not advised. If you do migrate the instances forward and then complete the instances, Monitor will not know about the completion. The associated emitted events will be routed to the Monitor Failed Events queue.
Remove a snapshot from the process server	Enabled or disabled	No action is taken. If there are other active snapshots on the server with process monitoring enabled, the cumulative monitor model continues to capture performance data for those snapshots. To remove a monitor model, use the WebSphere Application Server administrative console.