Article Content
Article Number | 000029223 |
Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 6.9.1, 7.x |
Issue | Many 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. |
Resolution | To configure an environment name for RSA Identity Governance & Lifecycle:
In the following example, an environment name for a Production database is configured: 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:
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:
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 |