Content Engine trace logging generates detailed information for tracing server and client activity. Trace logging is for diagnostic purposes only and does not provide security or audit trail information. Customer support and development personnel use the information provided by trace logging to diagnose and solve problems.
You can configure trace logging for the domain and for other objects within the context of a server hierarchy. The server hierarchy consists of the following levels (shown in order from highest to lowest level):
The order of the objects indicates ownership. Specifically, a server belongs to a virtual server, a virtual server belongs to a site, and a site belongs to a domain. An owned object can inherit a configuration from the owner object. Consequently, the configuration that you define at the domain level can optionally cascade down to all levels. Alternatively, you can selectively override inheritance and define the configuration for an owned object. For example, you can define the configuration for site A to be independent of the configuration for the domain while still allowing the configuration for site B to be inherited from the domain. Your configuration for site A can optionally cascade down to all objects that directly or indirectly belong to site A.
Configuring trace logging involves enabling or disabling logging and selecting the subsystems to be logged. Content Engine checks for changes to trace logging configurations every 30 seconds. After you enable trace logging for a subsystem, you can use the log files to troubleshoot any traced problems that occur on either the server or the client.
For instructions, see Enable or disable trace logging. For descriptions of the FileNet P8 subsystems that permit trace logging, see Concepts.