Configure logging for the WebSphere Commerce Test server (Developer environment)

We can configure logging for the WebSphere Commerce Test server through the WebSphere Application Server Administrative console.

Procedure

• Enable tracing through the WebSphere Application Server Administrative Console. These steps are duplicated from theWebSphere Application Server documentation. See the Working with trace group of topics in the WebSphere Application Server documentation.

  1. Open the WebSphere Application Server Administrative Console.

     http://hostname:9060/ibm/console

     or

     https://hostname:9043/ibm/console

  2. Expand Troubleshooting > Logs and Trace. The Logging and Tracing page displays in the workspace on the right.

  3. Click the server for which we want to enable the tracing (such as 'server1'). The window refreshes to display the logging and tracing options for the server.

  4. Click Diagnostic Trace. The Diagnostic Trace Service window displays in the workspace.

  5. Click the Configuration or Runtime tab. Changes made to Configuration are stored on the file system and applied when the server starts. We must restart the server to pick up any changes. This is required for finding issues that originate or occur when the server is initiated. Modifications to Runtime are applied immediately and are lost after the server is restarted.

  6. Optional: Select Change Log Detail Levels to modify tracing configurations for components or packages.

     • For component-based traces, use the component names. For a list of component-based traces, see
       Trace strings.

     • For package-based loggers, find the package or class name and determine the appropriate logger name to use. Consider the following SolrSearchConfigurationRegistry class as an example,

       com.ibm.commerce.foundation.internal.server.services.search.config.solr.SolrSearchConfigurationRegistry

       Set the following trace specification:For class-level tracing, use the exact match to the package and class name. For example,

       com.ibm.commerce.foundation.internal.server.services.search.config.solr.SolrSearchConfigurationRegistry=all

     If we are tracing multiple log detail levels, separate the traces with a colon. For example:

     com.ibm.websphere.commerce.WC_SERVER=all:com.ibm.websphere.commerce.WC_ORDER=all

     Tracking all helps in diagnosing problems so that multiple traces can be avoided. As an alternative to all, classes can also use warning and info traces, where info contains the least trace impact.

  7. Click Apply > OK to apply the changes to your server. If we selected to change the log details levels on the Configuration tab, restart your server.

• Trace components.

  Here are a set of WebSphere Commerce-related trace strings that we can use.

  Component	Trace string
  Promotion	com.ibm.websphere.commerce.WC_ORDER=all: com.ibm.websphere.commerce.WC_CALCULATION=all: com.ibm.commerce.marketing.promotion.*=all: com.ibm.commerce.promotion.*=all com.ibm.commerce.foundation.logging.*=all
  Marketing	com.ibm.websphere.commerce.WC_MARKETING=all: com.ibm.commerce.marketing.*=all: com.ibm.commerce.foundation.*=all: com.ibm.commerce.content.*=all: com.ibm.commerce.membergroup.*=all: com.ibm.websphere.commerce.WC_USER=all
  	com.ibm.commerce.marketing.cache.*=all com.ibm.commerce.store.marketing.*=all com.ibm.commerce.foundation.logging.*=all
  Orders	com.ibm.websphere.commerce.WC_ORDER=all: com.ibm.websphere.commerce.WC_CALCULATION=all: com.ibm.websphere.commerce.WC_EDP=all: com.ibm.websphere.commerce.WC_PPC=all: com.ibm.websphere.commerce.WC_INVENTORY=all com.ibm.commerce.foundation.logging.*=all
  Catalog	com.ibm.websphere.commerce.WC_CATALOG=all: com.ibm.commerce.foundation.*=all: com.ibm.websphere.commerce.WC_SERVER=all: com.ibm.commerce.foundation.client.lobtools.*=all: com.ibm.commerce.catalog.*=all
  Attribute Dictionary	com.ibm.commerce.tools.*=all: com.ibm.commerce.catalog.*=all: com.ibm.commerce.foundation.*=all: com.ibm.websphere.commerce.WC_SERVER=all
  Price rules	com.ibm.commerce.foundation.*=all: com.ibm.commerce.price.*=all: com.ibm.websphere.commerce.WC_CONTRACT=all: com.ibm.websphere.commerce.WC_ORDER=all: com.ibm.commerce.catalog.*=all
  Catalog filters	com.ibm.commerce.catalog.*=all: com.ibm.commerce.catalogentry.*=all: com.ibm.commerce.contract.*=all: com.ibm.commerce.foundation.*=all: com.ibm.websphere.commerce.WC_CATALOG=all: com.ibm.websphere.commerce.WC_CONTRACT=all
  Management Center	com.ibm.commerce.foundation.client.lobtools.*=all com.ibm.commerce.foundation.logging.*=all
  User registration and login	com.ibm.websphere.commerce.WC_SERVER=all: com.ibm.websphere.commerce.WC_USER=all: com.ibm.websphere.commerce.WC_ACCESSCONTROL=all com.ibm.commerce.foundation.logging.*=all
  Calculation framework (orders)	com.ibm.websphere.commerce.WC_ORDER=all: com.ibm.websphere.commerce.WC_CALCULATION=all: com.ibm.websphere.commerce.WC_MARKETING=all com.ibm.commerce.foundation.logging.*=all
  Dynamic Cache	The following strings are useful for diagnosing cache-related problems on the Transaction Server. The trace strings are listed from the highest-level and most important tracing to the most detailed. Each trace string creates some extra logging and can impact performance. If you need to reduce the performance impact, remove the trace strings beginning from the end of the list, unless a particular string is required for diagnosing the initial issue. com.ibm.commerce.dynacache.commands.*=all com.ibm.commerce.foundation.logging.*=all com.ibm.commerce.datatype.*=all com.ibm.websphere.commerce.WC_CACHE=all com.ibm.ws.cache.*=all
  Session Management	com.ibm.websphere.commerce.WC_SERVER=all: com.ibm.websphere.commerce.WC_BUSINESSCONTEXT=all: com.ibm.websphere.commerce.WC_USER=all: com.ibm.websphere.commerce.WC_SESSIONMANAGEMENT=all: com.ibm.commerce.foundation.*=all:
  Search scheduled job for update index	com.ibm.commerce.foundation.dataimport.*=all com.ibm.commerce.foundation.logging.*=all
  Search build index	*=info:com.ibm.commerce.foundation.*=all: com.ibm.commerce.rest.*=all: com.ibm.commerce.catalog.facade.server.*=finest
  Search health check	*=info:com.ibm.commerce.rest.*=finest
  Search rules	:*=info:com.ibm.commerce.rest.*=all: com.ibm.commerce.marketing.*=all: com.ibm.commerce.foundation.*=all: com.ibm.commerce.catalog.*=finest
  Search Rules Based Sales Categories	*=info:com.ibm.commerce.rest.*=all: com.ibm.commerce.marketing.*=all: com.ibm.commerce.foundation.*=all
  Access control	com.ibm.websphere.commerce.WC_SERVER=all: com.ibm.websphere.commerce.WC_USER=all: com.ibm.websphere.commerce.WC_ACCESSCONTROL=all com.ibm.commerce.foundation.logging.*=all
  Cross site protection	com.ibm.websphere.commerce.WC_SERVER=all com.ibm.commerce.foundation.logging.*=all
  SEO	*=info: com.ibm.commerce.seo.*=all com.ibm.commerce.foundation.logging.*=all
  Commerce Composer	*=info: com.ibm.commerce.foundation.logging.*=all com.ibm.commerce.pagelayout.*=all
  Data load	Data load framework trace com.ibm.commerce.foundation.dataload.*=all. Catalog data load: com.ibm.commerce.catalog.dataload.*=all Promotion data load com.ibm.commerce.promotion.dataload.*=all Marketing data load com.ibm.commerce.marketing.dataload.*=all Price data load com.ibm.commerce.price.dataload.*=all
  Watson Content Hub integration	com.ibm.commerce.security.commands.WCHUserHelper=all com.ibm.commerce.foundation.logging.*=all
  	For troubleshooting connections to Watson Content Hub, such as for completing onboarding tasks, see the alerts that are generated based on the error code. We cannot configure this logging.