You can diagnose problems when the installation and configuration
of IBM® Business Process Manager is unsuccessful.
Procedure
- Read any error messages from the installation process.
See the following topic for an explanation: Messages and known issues during installation and profile creation. If the message corresponds to any
of those described, correct the problem, clean up any installed portions,
and try to reinstall.
- If the installation of WebSphere® Application Server Network Deployment
was not successful, check Troubleshooting installation in the WebSphere Application Server
Network Deployment documentation and use the information found there
to correct the problem before attempting to reinstall IBM Business Process Manager.
- If the installation of WebSphere Application Server Feature Pack for Service Component
Architecture (SCA) with the Service Data Objects (SDO) feature not
successful, check Troubleshooting installation in the WebSphere Application Server
Network Deployment documentation and use the information found there
to correct the problem before attempting to reinstall IBM Business Process Manager.
- If the installation of WebSphere Feature Pack for Web Services
was not successful (and installation of WebSphere Application Server Network Deployment
was), check Troubleshooting web server plug-ins installation
and removal in the WebSphere Application Server Network Deployment documentation and use the
information found there to correct the problem before attempting to
reinstall IBM Business Process Manager.
Tip: If a problem occurs during
an installation of WebSphere Feature Pack for Web Services as part of the IBM Business Process Manager installation,
the installation process will not continue and an error message will
be displayed.
- If the installation of IBM Business Process Manager was
not successful (and installation of WebSphere Application Server Network Deployment
and WebSphere Feature
Pack for Web Services were), check other IBM Business Process Manager installation
log files. For information about the names, locations,
and descriptions of these log files, see Installation and profile creation log files.
- If you have successfully created a server profile, use
the Quick Start console or the command-line method to start the server.
- Verify that the server starts and loads properly by looking
for a running Java™ process and
the Open for e-business message in the SystemOut.log and SystemErr.log files.
If no Java process exists or if the message
is not displayed, examine the same logs for any miscellaneous errors.
Correct any errors and try again.
You can find the
SystemOut.log and
SystemErr.log files
in the following platform-specific directories:
On Linux and UNIX platforms: profile_root/logs/servername 
On Windows platforms: profile_root\logs\servername
- Use the Quick Start console or the command-line method
to stop the server, if it is running.
- If
you want to use a Snoop Servlet to verify the ability of the web server
to retrieve an application from IBM Business Process Manager, see
the step "Start the Snoop servlet to verify the ability of the web
server to retrieve an application from the Application Server" in Troubleshooting installation in the WebSphere Application Server
Network Deployment documentation.
- Start the administrative console.
- To
resolve any IP address caching problems, see the step about resolving
any IP address caching problems in Troubleshooting installation in the WebSphere Application Server
Network Deployment documentation.
What to do next
On the product support web site, you can review current
information about resolutions to known problems, and you can read
documents that can save you time gathering the information that you
need to resolve a problem. Before opening a PMR, see the IBM Business Process Manager support page.