Collect troubleshooting data for snapshot deployment and repository problems in IBM Business Process Manager (BPM)
You are having a snapshot deployment or other snapshot repository related problem with IBM Business Process Manager. You would like to know what documentation you must collect (MustGather) so that the IBM Business Process Manager Support team can diagnose your problem. If you gather this documentation before contacting support it will expedite the troubleshooting process, and save you time.
Diagnosing the problem
Overview of snapshot deployment and repository diagnostic information
Gather the following information and files:
General diagnostic information
- Problem description
- Environment description
- Server log files - All of the files from the following directories:
Process Server app member: <profile_root>/logs
Process Center app member: <profile_root>/logs
- TWX export of the related process application
As needed diagnostic information
- Profile /config directory from the deployment manager
- Snapshot related table exports
Setting the trace string
The general trace string should be set on the involved App cluster members from the Process Center and/or Process Server. Depending on the issue the other trace strings can be included with the general trace. The lightweight trace can be used for deployment, import and export if performance is a concern and only a high level trace is needed. Note, for offline deploy only the Process Server data is needed.
|General trace string||*=info: WLE.*=all: WAS.clientinfopluslogging=all: com.ibm.bpm.fds.*=all: ProcessApplicationLifecycle=all|
|Advanced content deployment issues||See the Advanced Snapshot Deployment Mustgather|
For instructions on setting the trace, see "Enabling trace on a running server". You may also need to increase the trace file size and number if the logs are rolling too fast. 20MB is a good starting point for the file size and you shouldn't increase it over 50MB.
Note: Enabling this trace might slow down your system. This delay can lead to transaction time-outs and errors. Disable this trace after capturing the problem to ensure the trace is not overwritten.
General diagnostic information
Collect the following diagnostic information:
1: Problem and environment description
Provide a detailed description of the problem that you are having. Try to be as detailed about the steps that lead up to the issue and include screen shots whenever possible. Include any error messages that you think are related. For example, include the answers to the following questions.
- Is this a new environment?
- Were there any changes prior to the issue occurring?
- Is the issue intermittent or re-creatable? If intermittent, how often does it occur?
- What type of environment is having the issue? (Test, QA, Production)
- How does the issue impact your business?
- Are there any deadlines that are affected by this issue that we should be aware of?
Profile_root /bin/versionInfo -maintenancePackages
The trace should be enabled on any involved application cluster members. For online deployment this should be both Process Center and Process Server. When providing the logs ensure the full logs directory including all servers and FFDCs on the node are included.
- Set the needed trace string on the related app cluster members.
- Recreate the issue. Take note of the time you trigger the issue and provide this with the logs.
- Turn off each of the enabled trace strings.
- Compress the profile_root/logs directory from each node profile. The directory contains the logs, trace, and ffdc files for each server.
Note: If you have logs/trace going to custom locations then provide those locations in addition.
If your issue is related to a particular application then provide a twx export of the involved snapshot.
In certain situations we will need config information from the profiles if the issue is configuration related. If this is needed provide the
/config directory from the DMgr profile.
For most snapshot related issues it is helpful to have the following 3 snapshot related tables from the BPMDB. Depending on the issue there are various other tables that can provide useful data. When providing DB table data it is important to provide it in a CSV text format. Each row should be on one line of text with each column value separated by a comma or other special character separator.
What to do next
- Review the log files and traces at the time of the problem to try to determine the source of the problem.
- Use IBM Support Assistant to search for known problems in the product documentation, forums, and technotes.
- If you cannot find related problems or cannot solve the problem, send the information you have collected to IBM by following the instructions in Exchanging Information with IBM Technical Support.
BPM product documentation - Installing process apps
BPM product documentation - Troubleshooting app deploy
Password limitations when deploying to offline Process
A simplified Chinese translation is available
|Business Integration||IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server||Application Deployment||Linux Red Hat - xSeries||8.0.1, 8.0|
|Business Integration||IBM Business Process Manager Express||Application Deployment||Linux, Windows||8.5, 8.0.1, 8.0, 7.5.1, 7.5|
|Business Integration||IBM Business Process Manager Standard||Application Deployment||AIX, Linux, Solaris, Windows||8.5, 8.0.1, 8.0, 7.5.1, 7.5|
|Business Integration||IBM Business Process Manager Advanced Pattern on AIX||Application Deployment||AIX||8.0.1|
More support for:
IBM Business Process Manager Advanced
Software version: 7.5, 7.5.1, 8.0, 8.0.1, 8.5
Operating system(s): AIX, Linux, Solaris, Windows
Reference #: 1618716
Modified date: 06 December 2012