Starting in RSA Identity Governance & Lifecycle 7.2.0, there has been an enhancement to the aveksaServerInfo.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServerInfo.log) . The purpose of this RSA Knowledge Base Article is to describe the product enhancement made to this log file.
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycleto find the location of the aveksaServerInfo.log file for your specific deployment, if you are on a WildFly cluster or a non-WildFly platform. The aveksaServerInfo.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
The aveksaserverinfo.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServerInfo.log) is a log file that shows detailed configuration information about the current RSA Identity Governance & Lifecycle installation. Prior to RSA Identity Governance & Lifecycle 7.2.0, the aveksaServerInfo.log would show the current configuration information only. Starting in 7.2.0, the log file has been enhanced to append the current configuration information to the file after each application startup. That way there is a history of configuration changes including version and patch information. It is important to note that with this change, the most current information is at the bottom of the log file rather than the top as it was originally when only the current information was logged.
Below is an example of an aveksaServerInfo.log file where the system has been patched twice and restarted six times. To determine the latest configuration information including the current version and patch level of this system, go to the bottom of the file and then scroll up until you encounter the first occurrence of Startup Date.
In this case the first occurrence of Startup Date when scrolling backwards from the bottom of the file is: 2020/07/31 18:20:47 making the following the current configuration information for this system: