The WebSphere Application Server Administrator's Console handles all logging and tracing configuration.
The following sections cover stand-alone tools only:
- Modifying ECMessage startup options
- Modifying ECTrace startup options
If you are using the lightweight WebSphere Commerce test environment, WebSphere Application Server tracing is not available. However, you can enable WebSphere Commerce tracing for your test environment.
Enabling tracing at server startup
- Open the WebSphere Application Server Administrator's Console.
- In the left navigation tree:
- Expand Troubleshooting > Logs and Trace. The Logging and Tracing page displays in the workspace on the right.
- Click on the server for which you want to enable the tracing (for example, WebSphere Commerce Server or Commerce Payments Server). The window refreshes to display the logging and tracing options for your server.
- Click Diagnostic Trace. The Diagnostic Trace Service window displays in the workspace.
- Click the Configuration tab.
- Select the Enable trace check box to enable tracing, or clear the check box to disable tracing.
- Set the tracing specification to the desired state by entering the proper TraceString. For a list of components you can trace, see the tables in Trace components. An example of a proper TraceString is:
com.ibm.websphere.commerce.WC_SERVER=all=enabled
Note: If you are tracing multiple components you should separate them by a colon. For example:
com.ibm.websphere.commerce.WC_SERVER=all=enabled:com.ibm.websphere.commerce.WC_ORDER=all=enabled
- Select whether to direct trace output to either a file or an in-memory circular buffer.
- Select Advanced from the drop down menu for the desired trace output format for the generated trace.
- Select the desired format for the generated trace.
- Save the changed configuration.
- Start the server.
If you are using the full WebSphere Commerce test environment:
Open WebSphere Studio Application Developer and switch to the Server perspective (that is, select Windows > Open Perspective > Server).
From the Servers window at the bottom, double-click Full WebSphere Commerce Test Environment. The Server Settings window displays.
From the bottom of the Server Settings window, select the Server tab
Expand Tracing.
- Select the Enable trace check box to enable tracing, or clear the check box to disable tracing.
- Set the tracing specification to the desired state by entering the proper TraceString. For a list of components you can trace, see the tables in Trace components. An example of a proper TraceString is:
com.ibm.websphere.commerce.WC_SERVER=all=enabled
Note: If you are tracing multiple components you should separate them by a colon. For example:
com.ibm.websphere.commerce.WC_SERVER=all=enabled:com.ibm.websphere.commerce.WC_ORDER=all=enabled
- In the Trace output file field, type the log file name and path where you want the tracing logged
- Start the server.
If you are using the lightweight WebSphere Commerce test environment, WebSphere Application Server tracing is not available. However, you can enable WebSphere Commerce tracing for your test environment by doing the following:
Open the WCDE_installdir\properties\com\ibm\commerce\litecontainer\Logging.properties file in a text editor.
Set desired logging levels to true. The logging levels apply to all of the components that are enabled.
Uncomment the components you want to trace.
Start the server. Logging information is written to the console.
Enabling tracing on a running server
You can modify the trace service state that determines which components are being actively traced for a running server by using the following procedure.
- Open the WebSphere Application Server Administrator's Console.
- In the left navigation tree:
- Expand Troubleshooting > Logs and Trace. The Logging and Tracing page displays in the workspace on the right. The Logging and Tracing page displays in the right windows.
- Click on the server for which you want to enable the trace (for example, WebSphere Commerce Server or Commerce Payments Server). The window refreshes to display the logging and tracing options for your server.
- Click Diagnostic trace. The Diagnostic Trace Service window displays in the workspace.
- Select the Runtime tab.
- Change the existing trace state by changing the trace specification to the desired state. For a list of components you can trace, see the tables in Trace components. An example of a proper TraceString is: com.ibm.websphere.commerce.WC_SERVER=all=enabled Note: If you are tracing multiple components you should separate them by a colon. For example: com.ibm.websphere.commerce.WC_SERVER=all=enabled:com.ibm.websphere.commerce.WC_ORDER=all=enabled
- (Optional) Configure the trace output if a change from the existing one is desired.
- Click Apply.