Technote

(troubleshooting)
MustGather: WebSphere Commerce Loader utilities
Problem(Abstract)
MustGather for problems encountered with the WebSphere Commerce loader utilities. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save time.
Resolving the problem WebSphere Commerce provides utilities for preparing and loading data into a WebSphere Commerce database. These utilities provide various functions that can be strung together in the required sequence to solve particular WebSphere Commerce data management problems. The loading utilities are flexible enough to handle customizations that are made to the WebSphere Commerce schema. The loader utilities consist of the following utilities: txttransformer, xmltransformer, dtdgenerator, idresolver, massloader and massextract.
Gather the following information before you call IBM support:

  1. The software stack or environment that the problem occurs on:

    • Operating system

    • WebSphere Commerce edition, version and fix pack level

    • WAS version and fix pack level

    • Java™ Development Kit version

    • Database type and version

  2. Detailed problem description

  3. Syntax of the loader utilities when run from the command line

  4. The input and the output files that have been used and created during the load process.

  5. Traces and logs

    • For loader utilities run from the command line, gather the following information:

      Enabling command line traces and logs
      Enable debug tracing to obtain more traces. The loader scripts need to be modified by adding –DDebug=true as a parameter when invoking the loader utility. For example, for the massload utility on Windows, the change would be as below in the massload.bat file:

      For WebSphere Commerce, versions 5.6 and 5.6.1:
      %JAVA_HOME%\bin\java -DDebug=true -classpath %CP% %massloader% %* > %log%

      For WebSphere Commerce, version 6.0:
      %JAVA_HOME%\bin\java -DDebug=true %PM_ARGS% -Dwas.repository.root="%CONFIG_ROOT%" -Dserver.root="%WAS_HOME%" -Dwas.root="%WAS_HOME%" -Dwas.install.root="%WAS_HOME%" -Dwas.cellname=%WAS_CELL% -Dwas.nodename=%WAS_NODE% -Dws.ext.dirs="%WAS_EXT_CLSLDR_PATH%;%WAS_USER_DIRS%" -classpath %EXT_CP%;%WAS_CLASSPATH% -Djava.security.policy="config.policy" com.ibm.ws.bootstrap.WSLauncher %massloader% %* > %log%

      Location and file names of logs and traces generated from the command line:Gather the following files:

      messages.txt
      trace.txt
      component.dbtype.log

      where

      component is the loader utility (massload, idresolver, etc.
      dbtype is the database type (db2 or oracle)

      The component.dbtype.log file (for example, massload.db2.log ) is only generated when the debug option is enabled.

      The locations of these files are defined in the WebSphere Commerce Information Center on the Loading utilities log files page.

      For loader utilities run from the server environment, gather the following information:

      Enabling server environment traces and logs

      To enable the debug trace, log on to the WAS console, and perform the following steps:

      For WebSphere Commerce 5.6 and 5.6.1:
      Click Servers > Application Servers > servername > Process definition > Java Virtual Machine and then add –DDebug=true in the Generic JVM Arguments text field.

      For WebSphere Commerce 6.0:
      Click Servers > Application Servers > servername > Server Infrastructure > Java and Process Management > Process definition > Java Virtual Machine and then add –DDebug=true in the Generic JVM Arguments text field.

      Locations and file names of the logs and traces generated from the server environment:

      Gather the following files:
      messages.txt
      trace.txt

      The location of these files are defined in the WebSphere Commerce Information Center on the Loading utilities log files page.

      When run on the server environment, the debug traces are generated in the following files:

      For WebSphere Commerce, versions 5.6 and 5.6.1:
      WAS_installdir/logs/WC_<instance>/SystemOut.log
      WAS_installdir/logs/WC_<instance>/trace.log

      For WebSphere Commerce, versions 6.0:
      WAS_installdir/profiles/instance/logs/server1/SystemOut.log
      WAS_installdir/profiles/instance/logs/server1/trace.log

      For more information on tracing and logging for loader utilities, refer to Configuring tracing and logging for the loading utilities in the WebSphere Commerce Information Center.

      Follow these instructions to send diagnostic information to IBM support.

Related information
Configuring the loading utilities
Loading utilities
Loading utilities log files
Configuring tracing and logging for the loading utiliti
Cross Reference information
Segment Product Component Platform Version Edition
Commerce WebSphere Commerce Enterprise Utilities/Tools AIX, Linux, Solaris, Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
Commerce WebSphere Commerce Business Edition Utilities/Tools AIX, Linux, Solaris, Windows 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3
Commerce WebSphere Commerce - Express Utilities/Tools AIX, Linux, Solaris, Windows 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3, 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
Commerce WebSphere Commerce Developer Enterprise Utilities/Tools AIX, Linux, Solaris, Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
Commerce WebSphere Commerce Developer Business Edition Utilities/Tools AIX, Linux, Solaris, Windows 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3
Commerce WebSphere Commerce Developer Professional Edition Utilities/Tools AIX, Linux, Solaris, Windows 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3, 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
Commerce WebSphere Commerce Developer Express Utilities/Tools AIX, Linux, Solaris, Windows 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
   

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21257742