HCL Web Content Manager tracing | HCL Digital Experience
Enable the use of WebSphere Application Server trace facilities to create trace information for Web Content Manager. This tracing can be enabled either permanently or for just the current HCL Digital Experience session.
HCL Web Content Manager uses the IBM® WebSphere® Application Server trace facilities to create trace information. If you need detailed trace output of Web Content Manager to debug a problem, follow these steps:
Enable static (extended) tracing
Static tracing is recommended when there is a need to capture data, as it collects data from server startup until problem recreation.
- Log in to the Integrated Solutions Console as the WebSphere® Application Server administrator.
- Select .
- On the Configuration tab, ensure that the Enable Log checkbox is selected. On this same tab, increase the Maximum File Size and Maximum Number of Historical Files as needed to ensure that the tracing of the problem recreation is not overwritten due to the amount of traffic on the system and output of the tracing itself.
- Click Change Log Level Details and enter the trace string based on the table below.
- Click OK and save the changes.
- Restart the WebSphere_Portal application server.
Enable dynamic tracing
Dynamic tracing can be used for situations that do not permit a server restart.
- Log in to the Integrated Solutions Console as the Portal administrator.
- Select . The Enable Tracing portlet appears.
- Type the required trace string into the field Append these trace settings based on the table below.
- Click the Add icon. Enable Tracing updates the field
Current trace settings. Note: Restarting HCL Portal will remove traces that were set by using the Enable Tracing Administration portlet.
Trace strings
The following table is the list of all trace strings available for HCL Digital Experience 8.5 and higher releases.
| Issue | Trace String |
|---|---|
| General Information |
|
| Syndication | |
| Security |
|
| Authoring Portlet |
Note: Client-side trace required. When recreating the issue, it is important to
note any JavaScript exceptions you may see in the browser. Additionally, you
need to collect some browser-side information so we can see the requests being
passed.
There are multiple methods for collecting this information: |
| API |
|
| JSR 286 Web Content Viewer |
|
| Remote Web Content Viewer Portlet | On the remote rendering server:
If the credential vault is in use, add the following the remote
rendering server traces:
On the rendering server:
|
| Caching |
|
| Pre-rendering |
|
| Enterprise Content Management Integration | Document Picker issues:
Personalization Federated Document issues:
Note: Client-side trace required. When recreating the issue, it is
important to note any JavaScript exceptions you may see in the browser.
Additionally, you need to collect some browser-side information so we can see
the requests being passed. There are multiple methods for collecting this
information: |
| Blogs and Wikis |
|
| Java Content Repository (JCR) |
|
| Java Content Repository (JCR) Export/Import of Library |
|
| Web Content Integrator |
|
| Migration |
|
| Seedlist and Search | WCM Seedlist issues:
WCM Search issues:
|
| Personalization | For issues with personalization in HCL Portal (rules, campaigns, application objects):
For issues with personalization and security:
For issues with personalization and Web Content Management (WCM):
For issues with personalization and JCR:
For issues with personalization authoring performance:
For issues with personalization runtime performance:
For issues with personalization publishing:
For configuration issues with personalization authoring
environment (Navigator Portlet, Editor Portlet, and List Portlet):
|
| Java Message Service (JMS) |
|
| Advanced Editor (RTE) | Enable Java Console logging on client system and send
output. Note: Client-side trace required. When recreating the issue, it is
important to note any JavaScript exceptions you may see in the browser.
Additionally, you need to collect some browser-side information so we can see
the requests being passed. There are multiple methods for collecting this
information: |
| Multilingual Solutions | MLS Install Trace location:
[WAS_PROFILE_ROOT]/ConfigEngine/log/ConfigTrace.log Configuration Issues:
Authoring plugin:
Workflow Traces:
|
| Workflow |
|
The resulting traces of Virtual Member Manager are written below:
- AIX® Linux™ Solaris: wp_profile_root/logs/HCL Portal and HCL Web Content Manager/trace.log
- IBM® i: wp_profile_root/logs/HCL Portal and HCL Web Content Manager/trace.log
- Windows™: wp_profile_root\logs\HCL Portal and HCL Web Content Manager\trace.log
- z/OS®: The resulting traces of Virtual Member Manager are written to the output location you specified as ras_trace_outputLocation in the WebSphere® Integrated Solutions Console. Check the Help Center of WebSphere® Application Server for z/OS® for details on what can be specified. For more information, see Setting trace controls.