Configuration Guide

10.3

Back Next

Configuring Application Server Logs

You must set the application server settings for debugging.

Application Server logs are maintained at the application server level. The log entries in an application server log file are not ORS-specific, but specific to the application server. The

Hub Server

log file writes to the

cmxserver.log

file that is specific to the application server. If you use multiple application servers, then each application server has its own configuration and log files. Similarly, the

Process Server

installed on WebSphere and WebLogic write to the log files on their respective application servers. In the case of

MDM Hub

installations on JBoss, the

Hub Server

and

Process Servers

are on the same JBoss instance and write to the same shared application server log file.

Before you can choose servers or databases to view, you must start Enterprise Manager. To configure application server logs, perform the following steps:

Open the

log4j.xml

file for editing.

The

log4j.xml

file is in

<infamdm_install_dir>

\hub\server\conf.

Edit the

log4j.xml

file.

Change default value to DEBUG.

Set the logging category names in the

log4j.xml

file to

com.siperian

com.informatica

, and

com.delos

Set the logging category

siperian.performance

to "OFF". You must set this logging category to "ON" only when Informatica requires it of you.

The following sample shows the settings for the

log4j.xml

file:

   <category name="com.delos">
      <priority value="DEBUG"/>
   </category>

   <category name="com.siperian">
      <priority value="DEBUG"/>
   </category>

   <category name="com.informatica">
      <priority value="DEBUG"/>
   </category>

   <category name="siperian.performance" additivity="false">
      <priority value="OFF"/>
      <appender-ref ref="FILE"/>
   </category>

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Configuring Application Server Logs

Configuring Application Server Logs