If you encounter a problem while deploying applications or modules
into WebSphere ESB,
you can use a range of activities and tools to troubleshoot and resolve the
problem.
Before you begin
This topic assumes the following things:
- You have a basic understanding of debugging a module.
- Logging and tracing is active while the module is being deployed.
Why and when to perform this task
The task of troubleshooting a deployment begins after you receive
notification of an error. There are various symptoms of a failed deployment
that you have to inspect before taking action.
Steps for this task
- Determine if the application installation failed.
Examine
the
system.out file for messages that specify the cause
of failure. Some of the reasons an application might not install include the
following:
- You are attempting to install an application on multiple servers in the
same Network Deployment cell.
- An application has the same name as an existing module on the Network
Deployment cell to which you are installing the application.
- You are attempting to deploy J2EE modules within an EAR file to different
target servers.
Important: If the installation has failed and the application
contains services, you must remove any SIBus destinations or J2C activation
specifications created prior to the failure before attempting to reinstall
the application. The simplest way to remove these artifacts is to click after
the failure. If you inadvertently save the changes, you must manually remove
the bus destinations and J2C activation specifications (see
Deleting bus destinations and
Deleting J2C activation specifications).
- If the application is installed correctly, examine it to determine
if it started.
If the application is not running, the failure
occurred when the server attempted to initiate the resources for the application.
- Examine the system.out file for messages
that will direct you on how to proceed.
- Determine if the resources are
started.
Resources that are not started prevent an application
from running to protect against lost information. The reasons for a resource
not starting include:
- Bindings are specified incorrectly
- Resources are not configured correctly
- Resources are not included in the resource archive (RAR) file
- Web resources not included in the Web services archive (WAR) file
- Determine if any components are missing.
The reason for missing a component is an incorrectly built enterprise
archive (EAR) file. Make sure that the all of the components required
by the module are in the correct folders on the test system on which
you built the Java archive (JAR) file.
- Examine the application to see if there is information flowing
through it.
Even a running application can fail to process information.
Reasons for this are similar to those mentioned in step 2.b.
- Determine if the applications uses any services contained in
another application. Make sure that the other application is installed
and running.
- Determine if the import and export bindings for all services
contained in other applications the failing application uses are configured
correctly. Use the administrative console to examine and correct
the bindings.
- Correct the problem and restart the application.
- If the preceding steps do not help, review the troubleshooting
deployment information for WebSphere ESB.
Because WebSphere ESB is
built on WebSphere Application Server Network Deployment,
you might want to consult troubleshooting information for WebSphere Application Server.