000028823 - How to determine the version and patch level of RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Aug 4, 2020
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000028823
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
IssueKnowing the version and patch level of your RSA Identity Governance & Lifecycle installation can be critical to resolving issues in RSA Identity Governance & Lifecycle. This RSA Knowledge Base Article describes multiple methods for ascertaining the RSA Identity Governance & Lifecycle version and patch level. It is a good practice to always provide this information when you open a case with RSA Identity Governance & Lifecycle Support and/or request assistance in the RSA community forums.
 
ResolutionThere are multiple ways of determining the version and patch level of RSA Identity Governance & Lifecycle. The most common ways are:  


User Interface



This method is the simplest and most common method but requires that the application and the database be running.

Any screen in the RSA Identity Governance & Lifecycle user interface has the version and patch level in the bottom left corner.


  • Example with no patches installed:

User-added image


  • Example with a patch installed:

User-added image

 

aveksaServerInfo.log



The advantage of this method is that:


  1. Neither the application nor the database need to be running, and
  2. The aveksaServerInfo.log contains valuable information about your RSA Identity Governance & Lifecycle configuration and environment.  


It is a best practice to attach the aveksaServerInfo.log to every case that you open with RSA Identity Governance & Lifecycle Support.


On a WildFly standalone system, the aveksaServerInfo.log is located in the $AVEKSA_HOME/wildfly/standalone/log directory. Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServerInfo.log 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.)
 

IMPORTANT:
It is important to note that the most current configuration information is appended to the bottom of the aveksaServerInfo.log after every application startup. Therefore, to determine the current version and patch level of the system, go to the bottom of the aveksaServerInfo.log file and then scroll up until you encounter the first occurrence of Startup Date. The current version and patch level will be below this heading. For more information on locating the current version and patch level information, please see RSA Knowledge Base Article 000039397 -- Enhancement to the aveksaServerInfo.log file starting in version 7.2.0 of RSA Identity Governance & Lifecycle.




  • Example with no patches installed (execute the following as the oracle user):


$ cd $AVEKSA_HOME/wildfly/standalone/log
$ cat aveksaServerInfo.log
RSA IDENTITY GOVERNANCE AND LIFECYCLE
Version 7.2.0.176311
****************************************************************************************************

(...)

Hot Fix : (none)

(...)


  • Example with a patch installed:


$ cd $AVEKSA_HOME/wildfly/standalone/log
$ cat aveksaServerInfo.log
RSA IDENTITY GOVERNANCE AND LIFECYCLE
Version 7.2.0.177042 P01
****************************************************************************************************

(...)

Hot Fix : P01

(...)

 

aveksa-version.properties and patch-version.properties



aveksa-version.properties contains the version information and patch-version.properties contains the patch information if there is a patch installed. This method is best used when the application and database are running. Although the aveksa-version.properties file can be found without either the application or database running, to reliably find the correct patch-version.properties file (if there is a patch installed), it is better to have both the application and database running.


  • Example with no patches installed:


$ find $AVEKSA_HOME -iname "*version.properties"
/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempe49cea2f99c3f858/content-
4e831bf4e475b92f/contents/aveksa.war/WEB-INF/classes/aveksa-version.properties
/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempe49cea2f99c3f858/content-
4e831bf4e475b92f/contents/aveksa.war/WEB-INF/database/aveksa-version.properties
/home/oracle/database/aveksa-version.properties



$ cat $AVEKSA_HOME/database/aveksa-version.properties
# RSA Identity Governance and Lifecycle
version=7.2.0
build=176311
(...)


  • Example with a patch installed:

Note that no patch-version.properties file exists until a patch is installed.



$ find $AVEKSA_HOME -iname "*version.properties"
/home/oracle/Aveksa_7.2.0_P01/aveksa.ear/aveksa.war/WEB-INF/classes/patch-version.properties
/home/oracle/Aveksa_7.2.0_P01/aveksa.ear/aveksa.war/WEB-INF/classes/aveksa-version.properties
/home/oracle/Aveksa_7.2.0_P01/aveksa.ear/aveksa.war/WEB-INF/database/aveksa-version.properties
/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/deployment/deploymentff2592f1efd69204/
aveksa.war-dcf15d313217615e/WEB-INF/classes/patch-version.properties
/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/deployment/deploymentff2592f1efd69204/
aveksa.war-dcf15d313217615e/WEB-INF/classes/aveksa-version.properties
/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/deployment/deploymentff2592f1efd69204/
aveksa.war-dcf15d313217615e/WEB-INF/database/aveksa-version.properties
/home/oracle/database/aveksa-version.properties



$ cat /home/oracle/database/aveksa-version.properties
# RSA Identity Governance and Lifecycle
version=7.2.0
build=176311
(...)



$ cat /home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/deployment/deploymentff2592f1efd69204/
aveksa.war-dcf15d313217615e/WEB-INF/classes/patch-version.properties

AveksaVersion=7.2.0
PatchVersion=P01
build=177042
(...)

 

T_SYSTEM_SETTINGS



The advantage of this method is that only the database needs to be running. 

As avuser, connect to SQL*Plus or a SQL interface such as SQL Developer and execute the following SQL statement:



select * from t_system_settings where parameter in
('productVersion', 'Build', 'SchemaCreatedVersion', 'SchemaCreatedBuild',
'HotFixes', 'HotFix_Build')



  • Example with no patches installed:

User-added image

 

  • Example with a patch installed:

User-added image

Attachments

    Outcomes