IBM BPM, V8.0.1, All platforms >

Troubleshooting and support for IBM BPM

Troubleshooting and support information for IBM BPM helps you understand, isolate, and resolve problems.

Troubleshooting and support information contains instructions for using the problem-determination resources that are provided with your IBM products.

To resolve a problem on your own, you can find out how to identify the source of a problem, how to gather diagnostic information, where to get fixes, and which knowledge bases to search. If you need to contact IBM Support, you can find out what diagnostic information the service technicians need to help you address a problem.

Resources for troubleshooting IBM BPM include a strategy for troubleshooting and diagnosing problems, a list of error messages, specific troubleshooting documentation organized by the tasks you are performing in IBM BPM, documentation about tools that help you track and monitor errors in your deployed applications, and links to technical support web sites.

Another troubleshooting resource is the IBM BPM forum on developerWorks. Use the forum to read or participate in technical discussions about the product with other customers.

IBM Redpapers publication: WebSphere for z/OS Problem Determination Means and Tools

• Overview of troubleshooting
  Troubleshooting is a systematic approach to solving a problem. The goal is to determine why something does not work as expected and how to resolve the problem.
• Troubleshooting checklist for IBM BPM
  Asking questions about hardware and software requirements, product fixes, specific problems, error messages, and diagnostic data can help you troubleshoot IBM BPM.
• Messages overview
  When you receive a message from IBM BPM, you can often resolve the problem by reading the entire message text and the recovery actions that are associated with the message.
• IBM BPM log files
  IBM BPM offers a comprehensive set of log files to help you identify and resolve problems during installation, configuration, and run time.
• Transaction log file
  The transaction (tranlog) log file stores critical transactional data that is written to databases. It is an internal file that WebSphere Application Server uses to manage in-flight transactions and attempt to recover them if the server locks up.
• Troubleshooting installation and configuration
  

  You can diagnose problems when the installation and configuration of IBM BPM is unsuccessful.

• Troubleshooting the z/OS installation and configuration
  Use this information to help you assess and correct problems that can occur if the product installation or configuration has not been successful.
• 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.
• Troubleshooting migration
  

  If you encounter problems during migration, the information described here could help.

• Troubleshooting memory issues for BPM servers
  

  If you are using IBM BPM with a 32-bit operating system or Java Virtual Machine (JVM), you might notice issues with server performance and availability, including OutOfMemory exceptions. These happen when the operating system or JVM does not have enough accessible memory to support all the running processes.

• Troubleshooting service module deployment failures
  This topic describes the steps to take to determine the cause of a problem when deploying a service module. It also presents some possible solutions.
• Failed to log in to Process Center
  In the Process Center perspective in IBM Integration Designer, when you provide the URL to connect to the Process Center, you might receive an HTTP 404 error stating that the JSP cannot be found.
• Failed to log in to Process Designer because URL should be qualified
  When you log in to Process Designer, you might receive an error stating that the Process Center is not running or the authentication of the username and password failed.
• Failed to log in to Process Designer because cache should be cleared
  When you log in to IBM Process Designer you may receive an error message that says that a call failed on the server. The error results if the browser is unable to open the URL that is passed to it.
• Resolving browser display problems in Process Designer
  After you log in to Process Designer, the Process Designer window might be blank. This issue typically occurs if additional security configuration is required in Internet Explorer V8 or V9.
• Troubleshooting administration tasks and tools
  Use the information in this group of topics to identify and resolve problems that can occur while you are administering the runtime environment.
• Troubleshooting WebSphere Application Server
  Because IBM BPM is built on IBM WebSphere Application Server, the function that you are having problems with might be provided by the underlying WebSphere Application Server. You might want to consult troubleshooting information in the WebSphere Application Server documentation.
• Tools for troubleshooting your applications
  IBM BPM and Integration Designer include several tools you can use to troubleshoot your applications that you develop and deploy on the server.
• Recovering from a failure
  Recovering from a failure requires an understanding of standard system processing in the event of a failure, as well as an understanding of how to analyze problems that may be the cause of a failure.
• Disaster recovery
  Disaster recovery consists of the policies and procedures that describe how to recover or continue the technology infrastructure critical to an organization after a natural or human-induced disaster.
• Search knowledge bases
  

  You can often find solutions to problems by searching IBM knowledge bases. Optimize your results by using available resources, support tools, and search methods.

• Getting fixes
  A product fix might be available to resolve your problem.
• Contacting IBM Software Support
  IBM Software Support provides assistance with product defects.