000023358 - The audit.log is not logging to the proper location defined in the log4j.xml

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

Article Content

Article Number000023358
Applies ToRSA Federated Identity Manager (FIM) 3.1.1
BEA WebLogic 8.1
IBM WebSphere 6.0
All OS'
IssueIn the log4j.xml you can specify where you want the audit.log to go, however it's still going to the same default location
CauseWhen the fimconfig.war is deployed separately from the FIM server, even if the log4j.xml specifies a different location for the audit.log, it still writes to the /rsa-fim-config/log directory.  The problem is log4j is not configured/initialized in fimconfig.war. The intialization of log4j is done in StartupServletContextListener.java.
ResolutionPlease contact RSA Technical Support to obtain hotfix #123.
Legacy Article IDa34518

Attachments

    Outcomes