000012287 - How to configure FIM 4.0 to use the DailyRollingFileAppender for log file rotation.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000012287
Applies ToFederated Identity Management Module 4.0
BEA WebLogic 9.0
IssueHow 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.
CauseThis 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.
ResolutionConfigure 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.

WorkaroundLog4j is configured to use the DailyRollingFileAppender.
Legacy Article IDa41515

Attachments

    Outcomes