on Jun 14, 2016Article Content
| Article Number | 000029223 |
| Applies To | New in Version 6.9.1 |
| Issue | Many organizations have at least two IMG systems (production and test). It would be very helpful to differentiate which system is being viewed in a browser and from which system a log or export is from. |
| Tasks | An environment name can be configured via the Admin->System->Settings tab. |
| Resolution | Once set, the environment name is displayed in the user interface, workflows, statistics reports, and exported XML data (metadata). Note that the environment name is displayed in the UI footer or header (depending on UI style). The Aveksa Statistics Reports (ASR), metadata and workflow exports are prefixed with the environment name. Server logs (including aveksaServer.log, aveksaServerInfo.log, server.log, and stdout.log) include "Environment: <environment name> following the server version string. ... 02/08/2015 10:59:24.309 INFO (main) [com.aveksa.migration.jdbctool.CheckDatabase] RSA Identity Management and Governance 6.9.1.82195 02/08/2015 10:59:24.312 INFO (main) [com.aveksa.migration.jdbctool.CheckDatabase] Environment: UAT ... |
| Notes | Inclusion of the environment string in the server logs also requires an IMG Application restart. Restarts are done from the Linux command line using either "acm restart" or "service aveksa_server restart" commands as the Linux admin or oracle user. |