Any errors encountered during the publishing process are written to the following log and trace files:
- activity.log
- A WebSphere Application Server log. All error messages in WebSphere Commerce are written to activity.log. Check this log first when publish fails. The activity log is in binary format, and you must use the Log Analyzer tool to view it. The
activity.log file is located in the following directory:WAS_installdir/logs
WAS_userdir/Base/WAS_instance_name/logs
WCDE_installdir/workspace_name/.metadata/plugins/com.ibm.etools.server.core/tmp0/logs
where workspace_name is workspace_db2 or workspace_oracle depending on the database you are using.
- SystemOut.log and SystemErr.log
- SystemOut.log is located in the following directory Contains any information written to standard output and standard error during store publish. SystemOut.log and SystemErr.log are located in the following directory:
WAS_installdir/logs/instance_name
WAS_userdir/Base/WAS_instance_name/logs/WC_instance_name
Important: SystemOut.log is not available in the WebSphere Commerce development environment. Information written to standard output or standard error is displayed in the console. By default, the WebSphere test environment does not save log files when stopping and starting application servers. For instructions on how to save log files when stopping and starting application servers in the WebSphere test environment, refer to the WebSphere Studio Application Developer information center.
- messages.txt
- Contains messages from the Loader package part of the publishing process.
Line or column numbers mentioned in these messages refer to the files store-data-assets.xml, which is created after IDResolver is run, and store-data-assets-resolved.xml, which is created after the Loader is run. Line or column numbers mentioned in error messages refer to these input files: store-data-assets.resolved.xml in the case of the loader and store-data-assets.xml in the case of IDResolver.
Contains messages from the Loader package part of the publishing process.
Line or column numbers mentioned in these messages refer to the file store-data-assets-resolved.xml, which is created after the Loader is run. Line or column numbers mentioned in error messages refer to this input file. messages.txt is located in the following directory:WC_installdir/instances/instance_name/logs
WC_userdir/instances/instance_name/logs
WCDE_installdir/Commerce/logs
Note: To configure the messages.txt log file (that is, adjust the log level or other options), edit the following file:
WC_installdir/instances/instance_name/xml/loader/WCALoggerConfig.xml
WC_userdir/instances/instance_name/xml/loader/WCALoggerConfig.xml
WCDE_installdir/Commerce/instances/instance_name/xml/loader/WCALoggerConfig.xml
- trace.txt
- Contains trace information for the Loader package and IDResolver parts of the publishing process. By default, trace.txt is turned off.
trace.txt is located in the following directory:WC_installdir/instances/instance_name/logs
WC_userdir/instances/instance_name/logs
WCDE_installdir/Commerce/instances/instance_name/logs
By default trace.txt is a circular log.
Note: To configure the trace.txt log file (that is, adjust the log level or other options), edit the following file:
WC_installdir/instances/instance_name/xml/loader/WCALoggerConfig.xml
WC_userdir/instances/instance_name/xml/loader/WCALoggerConfig.xml
WCDE_installdir/Commerce/instances/instance_name/xml/loader/WCALoggerConfig.xml
RESWCSID.txt
- Contains messages from the IDResolver part of the publishing process. Line or column numbers mentioned in messages refer to the input files, for example the store-data-assets.xml file. RESWCSID.txt is located in the following directory:
WC_userdir/instances/instance_name/logsNote: To configure the RESWCSID.txt log file (that is, adjust the log level or other options), edit the following file:
WC_userdir/instances/instance_name/xml/loader/WCALoggerConfig.xml
- trace.log
- Part of the WebSphere Application Server trace logs. Contains trace information for the publishing process, if the WC_DEVTOOLS trace component is enabled. trace.log is located in the following directory:
WAS_installdir/logs/instance_name
WAS_userdir/Base/instance_name/logs/WC_instance_name
WCDE_installdir/workspace_name/.metadata/plugins/com.ibm.etools.server.core/tmp0/logs
where workspace_name is workspace_db2 or workspace_oracle depending on the database you are using.