000037558 - How to access the aveksaServer.log and aveksaServerInfo.log files in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 6, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037558
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 6.x, 7.x
IssueThe primary diagnostic artifact that RSA Identity Governance & Lifecycle Support uses is the aveksaServer.log. This log file contains information about all activity associated with the application and is required in almost all cases to trouble-shoot issues. RSA Identity Governance & Lifecycle Support will commonly request this file in conjunction with the aveksaServerInfo.log when a new case is opened.

This knowledge base article explains where to find these two files as well as other commonly known log files that exist in the same location.

 
Tasks
The aveksaServer.log and aveksaServerInfo.log reside in the same directory location. Other log files found in the same location that may be requested by RSA Identity Governance & Lifecycle Support are:


  • patch.log
  • migrate.log
  • reporting-user-synonyms.log
  • server.log
  • stdout.log
  • WorkPoint.log
  • wpqmonitor.log
     

This article is specifically about the aveksaServer.log and aveksaServerInfo.log.
ResolutionThere are several ways to access the aveksaServer.log and aveksaServerInfo.log. How you access these two files depends on whether the application is up and running and the installation platform.
 

From the RSA Identity Governance & Lifecycle User Interface


If the application is up and running, these files may be downloaded from the RSA Identity Governance & Lifecycle User Interface.

  1. Login to the RSA Identity Governance & Lifecycle User Interface as an administrator.
  2. Navigate to Admin > System > Server Nodes.
  3. In the Logs column on the resulting page, click the link for the aveksaServer.log.
  4. Clicking on this link will open a download prompt for the log. Follow the prompts to download a copy of the file.
  5. Repeat steps above to download the aveksaServerInfo.log.
 

From the command line


In the event that the aveksaServer.log cannot be obtained from the user interface, it is possible to acquire from the command line. The file location varies depending on what type of server deployment the environment uses.


  • WildFly (JBoss) Non-cluster



 7.0.x: /home/oracle/wildfly-8.2.0.Final/standalone/log
 7.1.x: /home/oracle/wildfly-10.1.0.Final/standalone/log



  • WildFly (JBoss) Cluster



 7.0.x: /home/oracle/wildfly-8.2.0.Final/domain/log
 7.1.x: /home/oracle/wildfly-10.1.0.Final/domain/log



  • JBoss  (prior to 7.x)



 /home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServer.log



  • WebLogic



NOTE: For WebLogic, the aveksaServer.log file location is dependent on the installation path.  For example, the path will vary based on your WebLogic installation 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



  • WebSphere



NOTE: For WebSphere, the aveksaServer.log file location is dependent on the installation path.  For example, the path will vary based on your WebSphere installation location, as well as your domain, but should follow this pattern:

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/<hostname>Node01Cell/aveksa.ear/log/aveksaServer.log

Attachments

    Outcomes