Tracking IBM Business Process Manager performance data

To create customized and third-party reports in IBM® BPM, you identify the data to track and send that data to the Performance Data Warehouse.

To track data in a business process definition (BPD), use autotracking, tracking groups, or both.

Autotracking automatically captures data from tracking points at the entry and exit of each item in a BPD (for example, services, activities, and gateways). To enable autotracking, make sure that Enable Autotracking is selected under the Tracking tab of the BPD. (By default, the checkbox is not selected, which is better for performance.) Your system administrator can change this default.
Tracking groups provide more control over tracked data. For example, use tracking groups track a selected group of process variables across multiple BPDs or process applications and to store tracking points for a timing interval. To enable tracking groups, make sure that Enable Tracking is selected under the Overview tab of the BPD. (By default, the checkbox is selected.) Your system administrator can change this default. Note that the Enable Tracking setting does not apply to services with tracking points. Tracking data is always enabled when services contain tracking points.

You can use both tracking methods in one BPD. If you use both autotracking and tracking groups, you can create a timing interval.

After you configure data tracking for your BPD, and each time after that configuration that you update your data-tracking requirements, you must send the tracking definitions to the Performance Data Warehouse. When you send tracking definitions, either directly or as part of deploying a snapshot, the Performance Data Warehouse establishes the structure in its database to hold the data that Process Server generates when you run instances of your processes. In IBM BPM, these tracking requirements are called definitions because they establish the database schema in the Performance Data Warehouse to accommodate the tracked data that Process Server generates.

When you change your tracking requirements in Process Designer, you must send the definitions to the Performance Data Warehouse. Therefore, you are developing process applications on Process Center Server, be sure to send definitions after you change each process application. For process applications that are deployed in runtime environments, create a snapshot of your changes and deploy the new snapshot to ensure that the data you want to collect is available in the runtime environment.

Important:

There are some limitations you must keep in mind if you consider changing your tracking requirements :

It is not possible to rename a tracking group.
It is not possible to rename a tracked field.
It is not possible to have several tracking groups with the same name.
It is not possible to have several tracked fields with the same name but with different types in different tracking groups, either in the same process or in different processes or toolkits.