IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Use business monitoring with process applications > Generated monitor models
Update a generated monitor model
If you make changes to your process application that might affect the current monitor model (adding, changing, or removing auto-tracked fields or tracking group definitions, or adding new processes), any existing generated monitor model should also be updated to capture those changes and deliver complete performance data to the monitoring dashboard. An updated monitor model version has the same ID but a unique timestamp.
Before you can update the business monitor model for a process application, verify that there is an active monitor model already deployed.
Important: Some types of changes to a process application are not supported. If you change the data type of an existing auto-tracked field or tracking group, any subsequent deployment of the generated monitor model fails. In order to make changes to data types, you must remove the existing monitor model and create a new one that has a different ID. See Replacing a generated monitor model with a new monitor model.
If you are updating your process and want to regenerate your monitor model to capture those changes...
Procedure
- Log in to IBM Process Designer.
- Open the process application and make the necessary updates. Save your changes.
- Do one of the following, depending on whether you want to run the monitor model on the Process Center server or deploy it on a process server.
Option Description Process Center server
- Click File > Update Tracking Definitions to generate a new version of the monitor model with the same ID but a new time stamp. This version is considered the active version and is deployed on the server.
- Open the Inspector and run the process. Monitoring data is captured and sent to the dashboard.
Process server
- Create a snapshot of the process application.
- Deploy the snapshot on the target process server. A new version of the monitor model is generated and deployed; monitoring data is captured and sent to the dashboard.
What to do next
Once you have deployed multiple monitor model versions, you can use dashboard views for a specific version of the monitor model or for a cross-version view of the monitor model. The cross-version view will display a "union" of the objects from each version.
For example, if an auto-tracked field is removed and another is added and, as a result, the second version of the monitoring context removed one metric and added another, both metrics can be seen in the cross-version Instance View. Process instances from both versions are displayed.
Null values are displayed for any metrics that were removed for all instances that started after the change, and for the metrics that were added for instances that completed before the change was made. In the case of instances that were active when the change was made, the information on the Instance View depends on whether there was a reported value for the new or removed metric.
For example, if a value was reported for a metric before it was removed, or if a value was reported for a new metric after the process application was updated, both values are displayed.
Related concepts:
Troubleshooting business monitoring for process applications
Related information:
Monitoring from dashboard spaces