Configuring logging for the HCL Commerce Test server (Developer environment)

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


  • Enable tracing through the WebSphere Application Server Administrative Console. These steps are duplicated from theWebSphere Application Server documentation. For more information, see the Working with trace group of topics in the WebSphere Application Server documentation.
    1. Open the WebSphere Application Server Administrative 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 you 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. You 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,
        Set the following trace specification:
        For class-level tracing, use the exact match to the package and class name. For example,
      If you are tracing multiple log detail levels, separate the traces with a colon. For example:

      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 you selected to change the log details levels on the Configuration tab, restart your server.
  • Trace components.

    Here are a set of HCL Commerce-related trace strings that you can use.

    Component Trace string
    Attribute Dictionary*=all:*=all:*=all:
    Price rules*=all:*=all:*=all
    Catalog filters*=all:*=all:*=all:*=all:
    Management Center*=all*=all
    User registration and login*=all
    Calculation framework (orders)*=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.*=all*=all*=all*=all
    Session Management*=all:
    Search scheduled job for update index*=all*=all
    Search build index
    Search health check
    Search rules
    Search Rules Based Sales Categories
    Access control*=all
    Cross site protection*=all
    Commerce Composer
    Data load
    • Data load framework trace*=all.
    • Catalog data load:*=all
    • Promotion data load*=all
    • Marketing data load*=all
    • Price data load*=all