This page gives an overview about the log files and their configuration options.

Module	Default Log File Location	Log File Configuration	Remarks
Application Server Web Client	`<ServerInstallationRoot>\server\logs\*.log` `<ServerInstallationRoot>\server\wrapper.log`	`<ServerInstallationRoot>\server\configuration\HPM\log4j2.xml`	Application log files (out, error, perf) Windows Service Wrapper log
Desktop Client	`<ClientInstallationRoot>\client\logs\*.log`	`<ClientInstallationRoot>\client\configuration\HPM\log4j2.xml`
Supplier Portal	`<SupplierPortalInstallationRoot>\logs` `<SupplierPortalInstallationRoot>\tomcat\logs`	`<SupplierPortalInstallationRoot>\configuration\logback.xml`	Application Logs Tomcat Logs
Media Manager	`<MediaManagerInstallationRoot>\Informatica Media Manager\IMM_protocols` `<MediaManagerInstallationRoot>\OpasGWebServer\Tomcat\logs<MediaManagerInstallationRoot>\OpasGWebServer\XOBSessionManager\logs`
Web Search	`<WebSearchInstallationRoot>\log\server.log` `<WebSearchInstallationRoot>\<tomcat-server>\logs`	`<WebSearchInstallationRoot>\<tomcat-server>\lib\log4j.xml` `<WebSearchInstallationRoot>\<tomcat-server>\conf\logging.properties`	Application Logs Tomcat Logs
Database Setup	`<DatabaseSetupInstallationRoot>\dbclient\logs\*.log`	`<DatabaseSetupInstallationRoot>\dbclient\configuration\log4j2.xml`

Additional Logging of Dataquality

If you want verbose logging of the execution of a dataquality rule by the rule engine, go to the log4j2.xml file and change the priority of the IDQ category like below:

<Logger name="IDQ" level="DEBUG" />

The log files can also be found in the server log folder <ServerInstallationRoot>\server\logs\. Each rule configuration will be executed in it's own worker thread, so a log file will have following name pattern:

<JobWorkerName>-<RuleConfigurationName>-<StartDate>.log

Additional Logging of Change Summary and Datagraph

To get the insides of datagraphs and change summaries before store them to the database you can enable the following logger. You can define the logger for each subclass of

com.heiler.ppm.std.server.entity.EntityPersistenceManagerImpl

This sample enables the logging for ArticlePersistenceManager.

<Logger name="com.heiler.ppm.article.server.internal.entity.ArticlePersistenceManager" level="TRACE />

Use this logger wisely. The logging output is big.

Additional Logging of Media Asset Processing

If you want to fetch the logging of JMS processing, go to the log4j2.xml file and add the following setting:

<Logger name="PPM.MEDIA_ASSET_NOTIFICATION" level="DEBUG"/>

If you want to fetch the logging of Media Manager connector API methods, go to the log4j2.xml file and add the following setting:

Note: Connector logging via PIM is available since PIM 8.0.01

<Logger name="com.heiler.imm.connector" level="DEBUG" />

For more details information please visit the page Logging for Media Manager Connector within PIM.