Redirecting the location of the RSA Identity Governance & Lifecycle aveksaServer.log file from the default location to another directory
Originally Published: 2016-12-15
Article Number
Applies To
RSA Version/Condition: 7.0, 7.1
Issue
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
- The following file and line must be modified for WebSphere:
<WAS_HOME>/AppServer/profiles/<Server_Name>/installedApps/<Node_Name>/aveksa.ear/aveksa.war/WEB-INF/classes
log4j.appender.aveksaServerLog.File=${log.dir}/aveksaServer.log
- Since the application is deployed in an .ear file 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.
Related Articles
Adding trusted realm in RSA Authentication Manager 8.1 SP1 fails with an error: "The trust is not unique. Either the trust… 86Number of Views Setting NTP, date, time and time zone information for Authentication Manager 8.x running on SLES 15 38Number of Views Migrating users from one identity source to another in Authentication Manager 44Number of Views Migrating an RSA Authentication Manager deployment from one environment to another 455Number of Views Import Tokens from Another Deployment 103Number of Views
Don't see what you're looking for?