Troubleshooting is the process of finding and eliminating the cause of a problem. If you have a problem with your applications or your IBM® software, the troubleshooting process begins as soon as you ask yourself what happened?
Troubleshooting focuses on finding solutions to functional problems.
This set of topics, and other aids for troubleshooting with WebSphere® ESB build on information and other aids for troubleshooting with underlying WebSphere Application Server. Where appropriate, links are made to the WebSphere Application Server information and other aids.
As a general strategy for troubleshooting problems, use the following steps:
Always record the error message that you see. Error messages sometimes contain codes that might make more sense as you investigate your problem further. You might also receive multiple error messages that look similar but have subtle differences. By recording the details of each one, you can learn more about where your problem exists.
If you already have an error message and want to quickly look up its explanation and recommended response, look up the message under Messages.
For example, you can use the Log Analyzer tool of WebSphere Application Server to find and examine messages in general purpose logs, including JVM, process, and IBM service logs. For more information about using the Log Analyzer tool to work with message logs, see Diagnosing problems with message logs.
Depending on the specific problem that you have encountered, it might be useful to troubleshoot based on different issues that are known in installation, configuration, deployment, and administration. Investigate known problems organized according to task areas in Troubleshooting by task.
In addition to the information center, you can examine a range of Web-based resources for researching and resolving problems related to WebSphere ESB. For more information about these resources, see Resources for diagnosing and fixing problems.
A product fix might be available to resolve your problem. You can determine what fixes are available by running a query from the IBM Support Assistant. For more information about getting and applying any fixes, see Getting fixes.
Think back to the steps that led to this problem. Try those steps again to see if you can recreate this problem. It is easier to solve consistent and repeatable errors.
Narrow the scope of your problem by eliminating components that are not causing the problem. Consult the information in this product and other available resources to help you with your elimination process.
The support for logging and common base events is provided by the underlying WebSphere Application Server.
Difficult problems might require the use of tracing, which although conceptually similar to logging, exposes the low-level flow of control and interactions between components. Collecting a trace is often requested by IBM technical support personnel. If you are not familiar with the internal structure of WebSphere Application Server, the trace output might not be meaningful to you.
For general information about using logging and tracing to diagnose problems, see Logging and tracing with Java™ logging.
For more information about using tracing, see Working with trace.
Before deploying an application, assemble and test the application on a test server.
To debug applications that run on WebSphere ESB, you must use your application development tool. For more information, see "Debugging components" in the WebSphere Integration Developer information center or in the online documentation installed with IBM WebSphere Integration Developer.
The IBM Developer Kit and Runtime Environment, Java Version 5 Diagnostics Guide describes debugging techniques and the diagnostic tools that are available to help you solve problems with Java. It also gives guidance on how to submit problems to IBM. You can find the guide at IBM developer kits: Diagnosis documentation Web site.
WebSphere ESB is built on WebSphere Application Server. WebSphere ESB also works with infrastructure and platform services from WebSphere Application Server. For more information about troubleshooting in WebSphere Application Server, select Troubleshooting and support.
If you are not able to resolve a problem by following the steps in this topic, by looking up error messages in the message reference, or looking for related documentation on the online help, contact IBM Technical Support.
To find out how to look up documented problems, common mistakes, product prerequisites, and other problem-determination information on the WebSphere ESB Web site, or to obtain technical support from IBM, see Obtaining help from IBM.