WebSphere Commerce installation logs

Reviewing log files after the installation of WebSphere Commerce completes is a recommended step. The log files show any problems that might have been encountered during the installation.

Procedure

Complete the following steps:
  1. Review these log files to ensure that all components of WebSphere Commerce are installed successfully:
    • SolarisLinuxAIXWindowsWC_installdir/logs/install.log

      Check for the message: WebSphere Commerce installation complete.

      For multiple installation attempts, the log will be appended in the existing install.log file.

    • SolarisLinuxAIXWindowsWC_installdir/logs/wctrace_date_time.log

      This log file is intended for use by IBM support. Examining this file might not provide you with any useful information. The installation wizard creates this log file for every install or uninstall action.

    • For IBM i OS operating systemSolarisLinuxAIXWindowsWC_installdir/logs/wcinstall.log
      The installation wizard will create the wcinstall.log file only if errors or warnings are encountered during the installation process.
      AIXNote: You might receive a number of warnings relating to the invalid size of file entries in the wcinstall.log. These warnings can be safely ignored. For example:
      • Setup.product.install, com.ibm.wizard.platform.aix.AixProductServiceImpl,
        wrn, - WARNING: Got invalid size of 0 for file: /usr/IBM/WebSphere
        /CommerceServer70/schema/xml/wcs.bootstrap_adv_base.xml
      • Setup.product.install, com.installshield.wizard.StandardWizardListener, err, could not initialize interface swing
    • SolarisLinuxAIXWC_installdir/logs/wcnonroot.log
    • For IBM i OS operating system
      The following log files contain messages generated by the WebSphere Commerce installation wizard.
      Installation type Default log file location
      GUI based remote installation
      • /InstallLogs/install.log
      • /WC_installdir/logs/wcinstall.log
      • /WC_installdir/logs/wctrace_timestamp.log
      Remote silent installation
      • /InstallLogs/install.log
      • /tmp/InstallShield/wcinstall.log
      • /tmp/InstallShield/wctrace_timestamp.log
      Local silent installation
      • /tmp/InstallShield/install.log
      • /tmp/InstallShield/wcinstall.log
      • /tmp/InstallShield/wctrace_timestamp.log
      For multiple installation attempts, the log will be appended in the existing install.log file.

      Depending on the components of WebSphere Commerce that are installed, the following messages may appear at the end of the install.log file:

      CMN7704S: IBM WebSphere Commerce Installer has successfully copied file 
      from /QIBM/ProdData/CommerceServer70/bin/config_env.sh to 
      /QIBM/ProdData/CommerceServer70/bin/config_env.db2.sh
      
      CMN7720S: IBM WebSphere Commerce Installer internal Generic Catch Warning caught: 
      Command ended normally with exit status 0. 
      /QIBM/ProdData/CommerceServer70/bin/iSeriesFileAuth.sh
      
      CWXAI7779S: IBM WebSphere Commerce Installer has successfully modified the 
      Configuration Manager user password.
      
      CMN7753S: WebSphere Commerce installation complete. 
      
  2. If the installation of WebSphere Commerce fails, review the following information:
    • SolarisLinuxAIXSearch for log files in the /tmp directory.
    • WindowsSearch for log files in the directory defined by the %tmp% environment variable. The default value for the %tmp% environment variable is drive:Documents and Settings\user_ID\Local Settings\Temp\. This directory is hidden by default. You might need to change your folder options to see this directory.
    • For IBM i OS operating systemThe file wcinstall.log is created if an error occurs during installation. Error messages can also be reviewed in the file wctrace_timestamp.log, however this file is more commonly used when troubleshooting with product support.