Steps to enable Logging in Non-prod envs or Lower Environments of HCL Servers for debugging Issues.
1. Access the WebSphere Application Server Administrative Console.
http://hostname:9060/ibm/consoleor
https://hostname:9043/ibm/console2. Expand . The Logging and Tracing page displays in the workspace on the right.4. Click Diagnostic Trace. The Diagnostic Trace Service window displays in the workspace.
- 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
SolrSearchConfigurationRegistryclass as an example,
com.ibm.commerce.foundation.internal.server.services.search.config.solr.SolrSearchConfigurationRegistrySet the following trace specification:
com.ibm.commerce.foundation.internal.server.services.search.config.solr.SolrSearchConfigurationRegistry=allIf you 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=allTracking 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 to apply the changes to your server. If you selected to change the log details levels on the Configuration tab, restart your server.
8. you should now be able to see traces in the console or log files..
Below are some of the components and their trace strings please refer.
| Component | Trace string |
|---|---|
| Promotion | |
| Marketing | |
| |
| Orders | |
| Catalog | |
| Attribute Dictionary | |
| Price rules | |
| Catalog filters | |
| Management Center | |
| User registration and login | |
| Calculation framework (orders) | |
| 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. |
| Session Management | |
| Search scheduled job for update index | |
| Search build index | |
| Search health check | |
| Search rules | |
| Search Rules Based Sales Categories | |
| Access control | |
| Cross site protection | |
| SEO | |
| Commerce Composer | |
| Data load |
|
Reference Links:
https://help.hcltechsw.com/commerce/9.0.0/admin/tasks/tlslogging_txn_dev.html