Administer > Transforming, loading, and extracting data > Overview of the mass load utilities > Configure the loading utilities


Configure tracing and logging for the loading utilities

Overview

In addition to the individual logs for some of the loading utilities, you can configure an additional message log file, messages.txt, and a trace file, traces.txt, for the loading utilities. This can be helpful in getting more information to help determine any problems you may encounter. You can configure the contents and location of these files by editing WCALoggerConfig.xml.


Procedure

  1. Open the following in a text editor:

    There are two locations of WCALoggerConfig.xml.

    • WC_EAR/xml/loader/WCALoggerConfig.xml

      Used by the loader utilities when run from the command line

    • WC_INSTALL/instances/ instance/xml/loader/WCALoggerConfig.xml

      Used by the loader utilities in the server context, for example during the store publish process.

  2. Modify the contents of the file...

    1. Define the parameters for tracing:

      The trace tag defines the following information about the loading utilities trace file:

      • The traceFile attribute defines the full path (including the trace file name) to the trace file.

      • The enable attribute indicates if tracing is enabled (enable="true") or disabled (enable="false").

      • The fileSize attribute specifies the maximum size of the trace file, in megabytes (MB). The default value is 1024. Once the trace file size is exceeded a new trace file is started. The old trace file is backed up with a time stamp value added to the trace file name.

      • The component tags define the components for which trace is enabled. If a component is not listed or a component tag is commented out in the file, trace information will not be gathered for that component. The following table lists components for each loading utilities utility:

        Load utilities utility Trace component name
        dtdgen COMPONENT_DTDGEN
        fileloader COMPONENT_ATTACHMENT
        idresgen COMPONENT_IDRESGEN
        massextract COMPONENT_MASSEXTRACT
        massload COMPONENT_MASSLOAD
        xmltransform COMPONENT_XMLTRANS

        The default location for the trace file is:

    2. Define the parameters for logging:

      The messageLog tag defines the following information about the loading utilities log file:

      • The messageFile attribute defines the full path (including log file name) to the log file.

      • The enable attribute indicates if logging is enabled (enable="true") or disabled (enable="false").

      • The fileSize attribute specifies the maximum size of the log file, in megabytes. The default value is 1024. Once the log file size is exceeded, the log file is overwritten from the start of the trace file.

      • The logSeverity tags define the types of messages to write to the log file. If a message type is not listed or a logServerity tag is commented out, those message types are not recorded in the log file. The following table lists message types that can be logged:

        logSeverity type Description
        INFO Information messages follow events that occur while the loading utilities run. Information messages are related to events that trigger changes in the system state.
        WARNING Warning messages reveal a potential problem.
        ERROR Error messages expose an error condition that can lead to system malfunction.

        You can use the -DDebug=true parameter to get additional traces for the loader utilities that can be helpful in getting more debugging information for problem determination. For example, for a massload utility on Windows, the following change would be added to the massload.bat file: 

        %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%

        By default, only error messages are written to the message log file.

        The default location for the message log file is:

  3. Save the changes.

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


Previous topic: Configure the environment variable setting scripts


Next topic: Configure the idresgen utility


Related concepts

Overview of the mass load utilities


Related tasks

Configure the environment variable setting scripts

Configure the massload utility

Related reference

Example: WCALoggerConfig.xml

dtdgen utility

fileloader utility

idresgen utility

massextract utility

massload utility (Server environment)

txttransform utility

xmltransform utility


+

Search Tips   |   Advanced Search