How to configure FIM 4.0 to use the DailyRollingFileAppender for log file rotation.
3 years ago
Originally Published: 2008-08-05
Article Number
000040080
Applies To
Federated Identity Management Module 4.0
BEA WebLogic 9.0

Issue
How to configure FIM 4.0 to use the DailyRollingFileAppender for log file rotation.
Log files are not rotated correctly when FIM is deployed in a clustered deployment.  Even after log file rotation some information is still written to the old log file.
Cause
This may occur if multiple JDK's attempt to log to the same log file name.  This is an operating system restriction and should never, intentionally, be done.
Resolution
Configure each JDK on each cluster to log to it's own log file.  If you wish to view the logs in a unified format use a product such as RSA enVision to consolidate the data.

Modify the log4j.xml file in the FIM properties directory

<appender name="SystemLogFile" class="org.apache.log4j.DailyRollingFileAppender">
                <errorHandler class="com.rsa.fim.util.logger.RSAErrorHandler"/>
                <param name="Threshold" value="WARN"/>
                <param name="File" value="rsa-fim-config/log/System_${weblogic.Name}.log"/>
                <param name="DatePattern" value="'.'yyyy-MM-dd" />
                <layout class="org.apache.log4j.PatternLayout">
                        <param name="ConversionPattern" value="%d (%t) [%p] - %m%n"/>
                </layout>
        </appender>

After modifying the file on a particular server remember to restart the server.


Workaround
Log4j is configured to use the DailyRollingFileAppender.
Don't see what you're looking for?