Trace components

Use the following trace strings and logger information to gather the information that you need to troubleshoot problems.

For information about how to configure logging and tracing, see Configure logging for runtime environments.


MustGather information for catalog-related issues


MustGather information for contract, pricing, and offer-related issues


MustGather information for installation-related issues


MustGather information for Management Center-related issues


MustGather information for marketing-related issues


MustGather information for Member and User-related issues


MustGather information for order-related issues


MustGather information for performance-related issues


MustGather information for promotion-related issues


MustGather information for runtime-related issues


MustGather information for Search-related issues


MustGather information for security-related issues


MustGather information for Sterling integration-related issues


MustGather information for Store-related issues


MustGather information for workspaces-related issues


MustGather information for messaging-related issues


Customization server logging

Use the java.util.logging.Logger for logging on the Customization server. This logger is used by default for any IBM provided samples.

Logging for the custom packages of clients is based on the packages that are created by the client developers and the loggers that they include within their packages.


Performance loggers

The performance logger produces trace information about the response time when WebSphere Commerce calls out to different servers or external systems. The trace can be used by a monitor to measure response times.

The trace is enabled using the following string: com.ibm.commerce.performance=fine. The following sample entry shows a sample performance trace file entry, in JSON format:

The following performance measurement loggers are used by the WebSphere Commerce service servers to trace request and response calls:

Server Service
Transaction Server RestServerLogger, RestClientLogger, UELogger, external service logging
Customization server Use java.util.logging.Loggerservice to log trace.
Search server RestServerLogger, RestClientLogger, SolrLogger, UELogger
Store server ServletRequestLogger, RestClientReadEfficiencyLogger, RestClientLogger

The performance logger, com.ibm.commerce.foundation.logging.service.UELogger, is available to gather performance data to help you identify any performance bottlenecks with our customizations. The UELogger is always-on logger for providing a light-weight trace. The UELogger performs the following functions:

The logging layer does not measure the following metrics:

Note: The result size is measured only for the outbound calls to the external rest services.

The com.ibm.commerce.foundation.logging.service.UELogger is implement by the UEExecuteUtils, UEInvoker, and OrderResponseHandler classes.


JCA connectors

The following are the JCA connectors tracing components in WebSphere Commerce service:

Tracing Component WebSphere JRAS Extensions Trace Logger
JCA Silverpop adapter com.ibm.websphere.commerce.adapters.jcasilverpop
Watson Content Hub integration com.ibm.commerce.wc.messaging.adapters.jcawch.*


Related concepts
Logging services