How massload works | Generate a DTD


Step1: Configure the loading utilities


+

Search Tips   |   Advanced Search

Ensure that you have finished the necessary configuration for running this utility:

  1. Configure the loading utilities.

    Before you can use the loading utilities, you might have to update some of the environment variables used by the utilities. The environment variables are set by the following scripts (for AIX) that are called by the loading utilities and other WebSphere Commerce utilities:

      Setenv script: WC_Install_Dir/bin/setenv.sh
      Setenv.db2 script: WC_Install_Dir/bin/setenv.db2.sh

  2. Configure tracing and logging for the loading utilities.

    In addition to the individual logs for some of the loading utilities, you can configure an additional message log file and a trace file for the loading utilities. You can configure the location of the loading utilities message log and trace files and their contents by editing the WCALoggerConfig.xml file.

    To configure additional tracing and logging for the loading utilities:

    • Open the following in a text editor:

      WC_Install_Dir/xml/loader/WCALoggerConfig.xml

    • Modify the contents of the file as follows:

      • Define the parameters for tracing.
      • Define the parameters for logging.

    • Save your changes.

    • Ensure that the full path to WCALoggerConfig.xml is defined as part of the CLASSPATH environment variable before running any of the loading utilities.

  3. Configure the massload utility.

    • Before using the massload utility you might want to change the following to suit your environment.

      By default, the maximum amount of memory allocated to the JVM heap is 64 MB. If this is not increased, the JVM can eventually run out of memory during the load process. The maximum amount of memory allocated to the Java heap can be varied by using the JVM -mx option in the Java command. If you are loading files that are more than 500 MB, then increase the JVM heap size to 512 MB or 1024 MB.

      To modify the Java Virtual Machine (JVM) heap size used for the massload utility:

      • Open the following massload utility file in a text editor:

        WC_Install_Dir/bin/massload.sh

      • Change the JVM heap size to 1024 MB by specifying the -Xms and -Xmx options of the Java command.

        If the -Xms and -Xmx parameters are already specified in the file, change the values to the heap size that you want. Ensure that you update all occurrences of -Xms and -Xmx.

        If the -Xms and -Xmx parameters are not specified in the file, change all occurrences of %JAVA_HOME%\bin\java in the utility command file to %JAVA_HOME%\bin\java -Xms1024M -Xmx1024M.

      • Save the changes.

    • (Optional) Change the directory for the massload utility error log.

    • (Optional) Configure the MassLoadCustomizer.properties file.

  4. In addition to the trace log and message log for loading utilities, this utility produces the following log file for further problem analysis and determination:

    • (For DB2): WC_Install_Dir/logs/massload.db2.log
    • (For Oracle): WC_Install_Dir/logs/massload.db2.log