WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Troubleshooting the installation and configuration

Use the information in the troubleshooting section to help you assess and correct problems that may occur if the product installation has not been successful.

Before you begin

The installer program logs installation records in multiple ways:
  • Standard output messages

    Standard output messages display directly on the screen of server when you run the installation script zSMPInstall.sh. Standard output messages are also displayed when you run the augment script zWESBConfig.sh. You can choose to redirect these messages to a file by using redirect symbol > and a file name at the end of the command line. For example, adding >run.log to the end of the installation command will redirect the standard output messages to a file called run.log in the present working directory.

  • Log file messages

    Log file messages for the installation process are written to the zSMPInstall.log file in the runtime directory. The default location for this file is /WebSphere/V6R2/AppServer/logs/wbi/zSMPInstall.log.

    Log messages for the configuration process are written to the zWESBConfig.log file in the runtime directory. The default location of this file is /WebSphere/V6R2/AppServer/logs/wbi/zWESBConfig.log.

  • Trace file messages

    Trace messages for the installation process are written to the zSMPInstall.trace file in the runtime directory when you specify the -trace parameter on the command line when running the installation script zSMPInstall.sh. If you do not specify this parameter, the trace messages do not get written to the file. The default location of this file is /WebSphere/V6R2/AppServer/logs/wbi/zSMPInstall.trace.

    Trace messages for the configuration process are written to the zWESBConfig.trace file in the runtime directory. The default location of this file is /WebSphere/V6R2/AppServer/logs/wbi/zWESBConfig.trace.

Make sure that you have installed and configured WebSphere® Application Server for z/OS® successfully. Refer to the installation troubleshooting information in the WebSphere Application Server for z/OS information center if you are having trouble installing and configuring WebSphere Application Server for z/OS.

About this task

For current information available from IBM® Support on known problems and their resolution, see the WebSphere Enterprise Service Bus Support page.
Procedure
  1. Review the messages from Standard Out. There should be no error messages displayed. The standard output messages display on either the screen from which you ran the installation command or in a file that you specified by using the redirect (">") symbol on the command line.
    The following is an example of a successful execution of the installation script with the -install option:
    parsing command arguments...
    parsing arguments complete
    setting up configuration...
    runtimeRootDirName is: /WebSphere/V6R0M0/AppServer
    WAS_HOME is: /WebSphere/V6R0M0/AppServer
    WBI_HOME is: /WebSphere/V6R0M0/AppServer
    set up configuration complete
    creating the symbolic links...
    invokeSymLink
    creation of symbolic links complete
    doing post install file updates...
    post install updates complete
    running Configuration Manager update...
    Configuration Manager update complete
    augmenting profile(s)...
    augmenting profile(s) complete

    Error messages indicate an unsuccessful installation. Some errors as displayed in Standard Out will be self explanatory and can be easily corrected. If the installation completed to the point where the log and trace files were created, continue with the following steps.

  2. Review the zSMPInstall.log (ASCII) file in the runtime directory. For a stand-alone configuration, the standard location for this file is /WebSphere/V6R1M0/AppServer/logs/wbi/zSMPInstall.log. For a deployment manager configuration, the standard location for this file is /WebSphere/V6R1M0/DeploymentManager/logs/wbi/zSMPInstall.log
    If there are error messages, determine which of the following tasks were in progress when the error occurred.
    • Create symbolic links
    • Create post installation file
    • Update codebase permissions
    • Update Configuration Manager

    Knowing the task that was in progress at the time of an error will help you assess the information in the trace file.

  3. Review the zSMPInstall.trace or the zWESBConfig.trace (ASCII) file in the runtime directory. For a stand-alone configuration, the standard location for these files are /WebSphere/V6R1M0/AppServer/logs/wbi/zSMPInstall.trace or /WebSphere/V6R1M0/AppServer/logs/wbi/zWESBConfig.trace For a deployment manager configuration, the standard location of this file is /WebSphere/V6R1M0/DeploymentManager/logs/wbi/zSMPInstall.trace or /WebSphere/V6R1M0/DeploymentManager/logs/wbi/zWESBConfig.trace

    On a successful installation, only informational messages, for example messages that have a suffix of CWPIZ0044I should be listed in the trace file.

    If warning messages (messages with a suffix of W) or error messages (messages with a suffix of E) are listed in the trace, further review is required.

    If the warning or error occurred during the create symbolic links, create post installation file, or update codebase permissions tasks, the trace message should contain information that will help you diagnose and correct the problem.

    If the warning or error occurred in the update Configuration Manager task, proceed to the next step.

    If the warning or error occurred in the augment profile(s) task, proceed to step 5.

  4. Review the actions of the Update Configuration Manager task. These actions are recorded by writing to a log file (ASCII). The log file name is installconfig.log.

    Standard location for this file is in directory /WebSphere/V6R1M0/AppServer/logs/wbi/install.

    Search the Configuration Manager log for >SEVERE< or >WARNING< level messages to determine overall error in processing.

    Each Ant script run from the installation directory writes to its own log (ASCII).

    To determine what Ant file was running at the time of the error, you can look for 'Buildfile' previous.

    The default name for the installation directory that contains the ant scripts is: /WebSphere/V6R1M0/AppServer/properties/version/install.wbi/config/install.

    The resulting ant logs are written to the product log directory. The default name for this directory is /WebSphere/V6R1M0/AppServer/logs/wbi. Review these logs to determine errors in processing.

    If there were no problems a BUILD SUCCESSFUL message displays at the end of the file.

  5. Review the actions of the WebSphere Application Server profile augment task. The augment profile(s) task records its actions by writing to a log file (ASCII). The log file name has the name default_augment.log. Standard location for this file is in the directory /WebSphere/V6R1M0/AppServer/logs/manageprofiles/default_augment.log.

    Search the Profile Augmentation log for >SEVERE< or >WARNING< level messages to determine overall error in processing.

    Individual Ant action logs are located in /WebSphere/V6R1M0/AppServer/profiles/default/logs/manageprofiles/default.

    To determine what Ant file was running at the time of the error, you can look in the log for last instance of 'Buildfile' prior to the message in which you are interested.

What to do next

After troubleshooting the problems that caused the installation errors, and after you have run the installation script successfully, you should perform the following steps:
  1. Start the WebSphere Application Server.
  2. Launch the Administrative Console and verify that the product components have been installed.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tins_zos_trouble.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).