IBM BPM, V8.0.1, All platforms > Troubleshooting and support

Troubleshooting your deployment environment

When processing appears sluggish or requests fail, use a focused approach to determine the source of the problem in the environment. The approach described is for non-standalone server environments.

You must be logged into the administrative console of the dmgr to perform this task.

When security and role-based authorization are enabled, you must log in to the administrative console as an administrator or configurator to perform this task.

Investigate the state of your deployment environment if you notice any of the following symptoms:

• Unavailable applications
• Sluggish applications
• Stopped applications
• Decreased throughput
• Sluggish performance

Procedure

1. Display the topology layout that describes this deployment environment to determine the status of the topology.
2. Display the topology to determine the state of the various roles in the topology. If the roles with unexpected states or warning for further investigation.
3. Locate the nodes that are causing the error state for each role.
4. Make sure all nodes are synchronized.

   On the Nodes page in the administrative console select any unsynchronized nodes and click Synchronize.

5. Make sure that the messaging engines associated with all the buses are running.

   If they are not running, stop and start the messaging engines.

6. Locate the logs associated with the nodes in error and view the logs for error messages.
7. Take any actions prescribed by the error messages to affect the correction.
8. Correct any errors and restart the affected nodes.

Results

The nodes previously in error start and the status of the topology becomes "running."

What to do next

Restart any affected applications

• AIS does not refresh automatically in the Inspector view
  When you run a Business Process Diagram (BPD) in IBM BPM Advanced, the process status does not automatically update in the Inspector view. An Advanced Integration Service (AIS) can take some time to run, depending on the service implementation.
• AIS does not participate in the same transaction as business process
  In IBM BPM Advanced, process navigation of business process definitions (BPDs) does not participate in the same transaction context as an advanced integration service (AIS). Therefore, a runtime failure in the BPD navigation that causes the BPD transaction to roll back does not roll back the transaction under which the currently executing AIS might be running. As a result, the AIS might be executed a second time.
• Authors cannot drill down in a report
  When a report is present in Coach technology and you run it in playback mode using IBM Process Center for IBM BPM Advanced, you might not be able to drill down in the report.
• Limitations for importing processes from IBM Blueworks Live
  There are known issues pertaining to importing processes from IBM Blueworks Live into IBM BPM.
• Error occurs when importing process applications
  When you try to import process applications and toolkits into IBM Process Center for IBM BPM Advanced, the import process might fail if you do not have proper rights in your operating system.
• Process Portal does not support automatic session rollover
  Process Portal does not support automatic session rollover if one of the nodes in a cluster becomes unavailable.

Troubleshooting and support for IBM BPM

Related information:

Log files
Deployment environment status information
Aggregated status information
Topology status information