Troubleshooting installation and configuration

You can diagnose problems when the installation and configuration of IBM® Business Automation Workflow is unsuccessful.

Procedure

  1. 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.

  2. If you have successfully created a server profile, use the Quick Start console or the command-line method to start the server.
  3. 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:
    • For UNIX operating systemFor Linux operating system On Linux® and UNIX platforms: profile_root/logs/servername
    • For Windows operating system On Windows platforms: profile_root\logs\servername
  4. Use the Quick Start console or the command-line method to stop the server, if it is running.
  5. If you want to use a Snoop Servlet to verify the ability of the web server to retrieve an application from IBM Business Automation Workflow, see Default Application in the WebSphere® Application Server Network Deployment documentation.
  6. Start the administrative console.

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 Automation Workflow support page.