Troubleshooting
Problem
Your configured trace logging does not output any tracing, or outputs the incorrect trace subsystems in the trace log.
Cause
In the Content Platform Engine server, trace logging can be configured at various levels such as Domain, Site, Virtual Server, and Server Instance. Although trace logging is most commonly enabled at the Domain level (especially in clustered configurations), the server uses the following order of precedence when determining what subsystems are enabled for tracing: Server Instance > Virtual Server > Site > Domain.
Most often, this problem is due to an unwanted configuration of the tracing at a lower level than the one that you attempted to configure.
Resolving The Problem
Reconfigure your Content Platform Engine trace logging to use the Domain-level configuration:
1. Reset each Virtual Server and Server instance listed in ACCE:
(a) In the ACCE tree view, expand [Domain name] > Global Administration > Sites > [Site name] > Virtual Servers > [Virtual Server name] > Trace Subsystem tab.
Verify that "Configuration source" is set to "[Domain name] (server hierarchy object)". If it is not, set it to that value, and click Save.
(b) In the ACCE tree view, expand [Domain name] > Global Administration > Sites > [Site name] > Virtual Servers > [Virtual Server name] > [Server Instance name] > Trace Subsystem tab.
Verify that "Configuration source" is set to "[Domain name] (server hierarchy object)". If it is not, set it to that value, and click Save.
(c) For each additional Server Instance listed under the Virtual Server Name, repeat both (a) and (b).
(d) For each additional Virtual Server listed under "Virtual Servers" in the tree view, repeat (a)-(c).
2. Reset each Site instance listed in ACCE:
In the ACCE tree view, expand [Domain name] > Global Administration > Sites > [Site name] > Trace Subsystem tab.
Verify that "Configuration source" is set to "[Domain name] (server hierarchy object)". If it is not, set it to that value, and click Save.
For each additional Site listed under "Sites" in the tree view, repeat the above action, and the actions in Step 1.
Once all of the Sites, Virtual Servers, and Server Instances have their "Configuration source" value set to "[Domain name] (server hierarchy object)", then the Domain Trace Subsystem tab will control the trace logging for all servers in the P8 domain.
3. One commonly overlooked requirement that can affect trace logging is that your CPE virtual server names and server instance names must be unique within the topology in which the FileNet P8 domain is configured. If there is more than one CPE JVM instance, verify that all virtual server names and server instance names are unique. If any are not unique, then implement one or both of the JVM arguments mentioned in this documentation article to make them unique:
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNVNV","label":"IBM FileNet Content Manager"},"ARM Category":[{"code":"a8m0z0000001ggCAAQ","label":"ACCE-\u003ETracing"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.1;and future releases"}]
Was this topic helpful?
Document Information
Modified date:
19 February 2026
UID
ibm16827503