Configure the massload utility

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

  1. Change the Java Virtual Machine (JVM) heap size used for the massload utility.

    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 JVM heap size for the massload utility:

    1. Open the following massload utility file in a text editor:

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

    3. Save your changes.

  2. (Optional) Change the directory for the massload utility error log. By default, the massload utility writes the error log to the following directory:

    To change the location of the massload utility error log:

    1. Open the following massload utility file in a text editor:

    2. Change error report location setting:

      • If the -Dcom.ibm.wcm.ErrorReporterDir parameter is already specified in the file, change the directory to the new location for the massload utility error log. Ensure that you update all occurrences of -Dcom.ibm.wcm.ErrorReporterDir.

      • If the -Dcom.ibm.wcm.ErrorReporterDir parameter is not specified in the file, change all occurrences of %JAVA_HOME%\bin\java %PM_ARGS% in the utility command file to %JAVA_HOME%\bin\java %PM_ARGS% -Dcom.ibm.wcm.ErrorReporterDir=error_log_directory.

      The directory you specify must exist. The massload utility does not create the directory for you. If the specified directory does not exist, no error log file is produced. Additionally, if you have configured message logging for the massload utility, a DirNotExististException message is logged in the message log

    3. Save your changes.

  3. (Optional) By default, the massload utility uses the Oracle thick JDBC client. To change the massload utility to use the Oracle thin JDBC client:

    1. Extract DbConnectionImplIDProperty.properties from the following file:

      WC_installdir/lib/loader/oracle/dbconnect.zip

    2. Open DbConnectionImplIDProperty.properties in a text editor.

    3. Locate the following text:

      ConnectStringID = jdbc:oracle:oci8:@

    4. Change the text to match the following text:

      ConnectStringID = jdbc:oracle:thin:@

    5. Save your changes.

    6. Add the updated DbConnectionImplIDProperty.properties file to the WC_installdir/lib/loader/oracle/dbconnect.zip file. Overwrite the existing file in the archive.

  4. (Optional) Configure the MassLoadCustomizer.properties file.

Related concepts

Related reference