Deprecated feature: Configuring tracing and logging for the mass load utilities

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 whether 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. After the trace file size is exceeded, a new trace file is started. The old trace file is backed up with a time stamp 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 is not gathered for that component.

  Loading 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:
  • WC_installdir/logs/trace.txt
  • WC_userdir/instances/instance_name/logs/trace.txt
  • WCDE_installdir/logs/trace.txt

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

  Note: You can use the -DDebug=true parameter to get more traces for the loader utilities that can be helpful in getting more debugging information for problem determination.

  %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.
  Default location:

  • WC_installdir/logs/messages.txt
  • WC_userdir/instances/instance_name/logs/messages.txt
  • WCDE_installdir/logs/messages.txt