000029223 - How to differentiate between multiple environments in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016•Last modified by RSA Customer Support on Jun 8, 2020
Version 5Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000029223
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1, 7.x
 
IssueMany organizations have multiple RSA Identity Governance & Lifecycle installations. For example, Production, UAT, QA, Test, and Development are commonly installed environments. This RSA Knowledge Base Article describes a feature introduced in RSA Identity Governance & Lifecycle 6.9.1 that allows the environment name to be configured. Naming the environment allows you to differentiate between systems when logged in from a browser or when determining from which system a log file or export file came from.
 
ResolutionTo configure an environment name for RSA Identity Governance & Lifecycle:
  1. Navigate to Admin > System > Settings tab > Edit 
  2. Under Environment, add an environment name in the Name field.

In the following example, an environment name for a Production database is configured:

 

User-added image
 


The environment name is displayed in the User Interface, and used to prefix Statistics reports (ASRs) and workflow and metadata exports. For example, note the environment name in the footer of the User Interface screen below:
 


User-added image


  1. Optionally restart RSA Identity Governance & Lifecycle to complete the configuration change. As the oracle user execute the following command on the application server:


acm restart

 

After the application is restarted, the Environment name will also show in the aveksaServer.log and the aveksaServerInfo.log located in the $AVEKSA_HOME/wildfly/standalone/log directory in the format:

 

Environment: <environment name> 



Examples: 

 


$ cat aveksaServerInfo.log | grep Production 
Environment: IGL-Production

$ cat aveksaServer.log | grep Production
06/08/2020 16:24:55.119 INFO  (ServerService Thread Pool -- 90) 
[com.aveksa.migration.jdbctool.CheckDatabase] Environment: IGL-Production



Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. These logs may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)


 
Notes
 

Attachments

    Outcomes