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

Troubleshooting business monitoring for process applications

You can discover and fix problems that you find when you create, update, or delete monitor models for process applications.

Deployment of updated monitor model fails after changes to data types

Because the database views aggregate data together across model versions, some types of changes 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.

Monitor model fails to deploy from IBM Process Designer or IBM Integration Designer

You are attempting to deploy a monitor model while logged into IBM Process Designer or IBM Integration Designer as a user who does not have authority to deploy monitor models.

The SystemOut file contains the following error message:

CWWMH0271E: Authorization failure. Insufficient authority to create a business-level application. This operation requires "deployer" or "configurator" role on the cell

To resolve this problem...

1. Log in to the administrative console.

2. Click Users and Groups > Administrative User roles or Users and Groups > Administrative Group roles.

3. Select your user or group to open it.
4. Under Roles, select Deployer and click OK.
5. Retry the model deployment.

Global transaction timeout error when tracking definitions are updated

Depending on the memory and processor speed of your computer, you might experience a global transaction timeout error when you click File > Update Tracking Definitions in Process Designer. This occurs most often on slower computers when the model deployment does not complete within the allotted time. The error includes information similar to this example:

org.springframework.transaction. TransactionSystemException:
UOWManager transaction processing failed; nested exception is com.ibm.wsspi.uow.UOWException; javax.transaction.RollbackException:
Global transaction timed out after 300 seconds

If you experience this problem frequently, increase the Maximum transaction timeout parameter to a duration greater than 300 seconds. In the WebSphere Application Server administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container Services > Transaction Service. For more information, refer to the related topic "Configuring transaction properties for an application server" in the WebSphere Application Server Information Center.

Toolkits created in earlier versions of the product cause business monitoring of a process application to fail

If a toolkit that was created in WebSphere Lombardi Editions 7.1 or 7.2 is used in a process application created in IBM Process Designer 7.5, business monitoring of that process application fails at run time when the emitted events are routed to the monitor failed events queue.

Before a toolkit created in WebSphere Lombardi Edition 7.1 or 7.2 can be used in a process application created with IBM Process Designer 7.5, the toolkit must be updated to 7.5.

To update the toolkit...

1. Import the toolkit into IBM Process Designer 7.5.
2. Clone the toolkit.
3. Open the toolkit clone you created in step 2 in Process Designer.
4. Right click System Data toolkit > Change Version of dependency.

5. Click 7.5.
6. Save your changes and take a snapshot of this toolkit.

7. Use the cloned toolkit when you create a new process application in IBM Process Designer 7.5.

Failed events after running a BPD in the Inspector or Process Portal

After a business process definition is run in the Inspector or Process Portal, you might see failed events in the monitor error queue. This problem can occur across three different scenarios:

• This problem occurs when a business process definition process instance is started but no monitor model is deployed to consume the emitted events. When you later deploy a monitor model and subsequently complete the original process instance, the events go to the Failed Events queue with an instance correlation error because the monitor instance creation events were emitted before the monitor model was deployed.
• This problem also occurs if multiple versions of a monitor model are deployed and an active instance from an earlier monitor model version is being worked on or completed. Events from that active instance are delivered to the new model version where the parent instance was not created because the instance was instantiated before the new model version being deployed. Events for this instance are routed to the error queue when they cannot be correlated with the new model version. However, these events will be successfully consumed by the earlier model version.
• Finally, this problem can also occur if updates are made to a BPD and the process application is run without running File> Update tracking definitions, and there are active instances from a previous run. When you changed the BPD and saved it, a new version ID is internally assigned for the BPD. When the earlier instance resumes, it runs in the in the new version. The events for the instance that is already in progress, will not correlate because the events contain a new version ID.

Monitor model version deployment from Process Designer fails with the following errors visible in the Admin Console when you click the Deployment Error link for the monitor model

When you click the monitor model Deployment Error link, the deployment of the model from Process Designer fails. The following error is shown:

CWMAX4204E: The Cognos cubes created (optional) step failed.
CWMLC0113E: Model [bmon_SP1_Main] version [2011-09-07T13:39:40] step [createCognosCubes] failed. Cause: [CWMTC2210E: It was not possible to create the Cognos cube because the following error occurred: com.ibm.wbimonitor.admin.command.cognos.CognosCubeDeployException: CWMTC2215E: A model database schema not available: bmon_SP1_Main 20110907133940].
CWMAX4204E: The Create Schema step failed.
CWMLC0012E: Unexpected exception [com.ibm.wbimonitor.schemagenerator.exceptions.SchemaGenerationException: com.ibm.wbimonitor.schemagenerator.exceptions.ModelValidationException: Monitoring Contexts cannot change in the hierarchy between model versions. A different Monitoring Context ID must be specified for: SubProcess1].
CWMAX4204E: The Enable Dashboards step failed.
CWMLC0113E: Model [bmon_SP1_Main] version [2011-09-07T13:39:40] step [enableDashboards] failed. Cause: [Monitoring Contexts cannot change in the hierarchy between model versions. A different Monitoring Context ID must be specified for: SubProcess1].

Some of the subprocesses or event subProcesses may have moved in a process application BPD. This can cause a monitoring context hierarchy change to the generated monitor model. Hierarchy changes are not supported across model versions.

To correct this error condition:

Undeploy all versions of the monitor model from Process Designer

1. Clear the Enable process monitoring through IBM Business Monitor check box on the process application.

2. Click Save.

3. Click File> Update tracking definitions. All versions of the monitor model are uninstalled.

Deploy the process application

1. Check the Enable process monitoring through IBM Business Monitor check box on the process application

2. Click Save.

3. Click File > Update tracking definitions. The model successfully deploys.

Use business monitoring with process applications

Related concepts:
Use business monitoring with process applications

Related tasks:
Replacing a generated monitor model with a new monitor model
Update a generated monitor model
Configure transaction properties for an application server

Related information:
Cloning toolkits in the Process Center Console