|Applies To||RSA Product Set: Identity Management and Governance|
|Issue||RSA customer support has requested a copy of the aveksaServer.log for diagnosis of a support issue. The aveksaServer.log is a very common diagnostic artifact that RSA support will request in most support cases.|
Important note: This file is separate from both the server.log or the stdout.log files.
|Resolution||There are several ways to access this file.|
From the user interface
In the event that the aveksaServer.log cannot be downloaded from the UI, it is possible to acquire from the command line. The file location varies depending on what type of server deployment the environment uses.
The aveksaServer.log is located in /home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServer.log.
The path will vary based on your WebLogic install location, as well as your domain, but should follow a pattern similar to: $WEBLOGIC_HOME/user_projects/domains/aveksaDomain/servers/AdminServer/tmp/_WL_user/aveksa/ldedze/aveksa.war/log/aveksaServer.log.
The path will vary based on your WebSphere install location, as well as your domain, but should follow this pattern: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/hostnameNode01Cell/aveksa.ear/log/aveksaServer.log.
The path to the file is /home/oracle/wildfly-8.2.0.Final/standalone/log.
|Legacy Article ID||a66683|