Appendix A. Managing WebSphere Commerce components 247
Draft Document for Review July 28, 2004 7:33 pm 6320ax04.fm
5. Enter the following at the wsadmin prompt to exit the wsadmin tool:
quit
Tracing with WebSphere Commerce V5.6 Toolkit
Specifying trace levels and components for WebSphere Commerce V5.6 is very
different than in WebSphere Commerce Suite V5.1. Since WebSphere
Commerce V5.5, the WebSphere Application Server tracing facility has been
used for trace output.
In the WebSphere Commerce V5.6 runtime environment, tracing is enabled in
the WebSphere Application Server Administration Console.
In WebSphere Commerce V5.6 Toolkit, the tracing is specified in one of two
ways, depending on whether the Full or the Lightweight WebSphere Test
Environment is used.

Tracing for Lightweight WebSphere Test Environment

The Lightweight WebSphere Test Environment uses a property file to control
which components have tracing enabled.
Tip: The trace strings for the various WebSphere Commerce components
can be found in the WebSphere Commerce InfoCenter at the following
address:
http://publib.boulder.ibm.com/infocenter/wc56he lp/topic/com.ibm.commer
ce.admin.doc/refs/rlslogging.htm
Also, to enable logging for more than one component, separate the trace
strings with a colon, for example:
com.ibm.websphere.commerce.WC_ORDER=all=enabled :com.ibm.websphere.comm
erce.WC_INVENTORY=all=enabled:com.ibm.websphere .commerce.WC_UTF=all=en
abled
This will enable tracing for the components ORDER, INVENTORY and UTF.
Note: The changes to the trace string are not saved in the server
configuration. If the server is restarted, the trace string spec ification will revert
to the value it had before you changed the value from within the wsadmin tool.
To permanently change the trace string for a server, you must use the
WebSphere Commerce Administration Console.