000034560 - Redirecting the location of the RSA Identity Governance and Lifecycle aveksaServer.log file from the default location to another directory

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

Article Content

Article Number000034560
Applies ToRSA Product Set: Identity Management and Governance
RSA Version/Condition:  7.0, 7.1
IssueIt is supported to redirect the location of the aveksaServer.log?
 
Resolution
  • The following file and line must be modified for WildFly:
/home/oracle/wildfly/standalone/configuration/aveksa-log4j.properties
log4j.appender.aveksaServerLog.File=${log.dir}/aveksaServer.log

  • The following file and line must be modified for WebLogic:
/home/oracle/Oracle/Middleware/Oracle_Home/user_projects/domains/aveksaDomain/servers/AdminServer/tmp/.<variable name>_aveksa.ear/aveksa.war/WEB-INF/classes/aveksa-log4j.properties
log4j.appender.aveksaServerLog.File=${log.dir}/aveksaServer.log

  • Since the application is deployed in an .ear now, for both Web Application Servers and WildFly, you must deploy this change in the .ear file (The ear file gets redeployed on every start, so changes are not persistent unless they are deployed in the .ear file).
Please see 000033885  How to add content to the RSA Identity Governance & Lifecycle 7.x application for instructions on how to accomplish this.  Also, the application server needs to be restarted for this change to take effect.

Attachments

    Outcomes