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 Configuring 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 performance-related issues
- MustGather information for promotion-related issues
- MustGather information for runtime-related issues
- MustGather information for Solr search-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
- Performance loggers
- JCA connectors
MustGather information for catalog-related issues
MustGather information for contract, pricing, and offer-related issues
MustGather information for installation-related issues
- Collecting MustGather data for initial HCL Commerce deployment issues
- Collecting MustGather data for HCL Commerce Developer installation issues
- Collecting MustGather data for customization deployment issues
- Collecting MustGather data for runtime update issues
- Collecting MustGather data for database update 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
- Collecting MustGather data for dynamic cache issues
- Collecting MustGather data for optimistic locking issues
- Collecting MustGather data for Scheduler issues
- Collecting MustGather data for service provider (subscriptions and recurring orders) issues
- Collecting MustGather data for session management issues
- Collecting MustGather data for Spring framework issues
MustGather information for Solr search-related issues
- Collecting Solr based search-related MustGather data for search build index issues
- Collecting Solr based search-related MustGather data for search cache invalidation issues
- Collecting Solr based search-related MustGather data for search core creation issues
- Collecting Solr based search-related MustGather data for search facets issues
- Collecting Solr based search-related MustGather data for search relevancy issues
- Collecting Solr based search-related MustGather data for search replication issues
- Collecting Solr based search-related MustGather data for search rule issues
- Collecting Solr based search-related MustGather data for search Rules Based Sales Categories issues
- Collecting Solr based search-related MustGather data for search term association and landing page 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 HCL 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 HCL 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 by using the following string: com.ibm.commerce.performance=fine.
{"timestamp": "2012/10/02 23:56:38:265 EDT", "threadID": "0000009c", "source": "External OMS", "service": "getPage-getOrderList", "serviceTime": "6188 ms"},
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 externalized customization performance logger,
com.ibm.commerce.foundation.logging.service.UELogger
, is available to gather
performance data to help you identify any performance bottlenecks with your customizations. The
UELogger is always-on logger for providing a light-weight trace.
- Measures the entire externalized customization extension process.
- Logs the outbound calls to the external REST services when an extension runs.
- Logs the order data persistence when an extension runs.
- If caching is enabled for the operation.
- If the operation result was a cache hit.
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 HCL Commerce service:
Tracing Component | WebSphere JRAS Extensions Trace Logger |
---|---|
JCA Silverpop Adapter | com.ibm.websphere.commerce.adapters.jcasilverpop |