000029223 - How to differentiate between multiple co-located IMG systems

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

Article Content

Article Number000029223
Applies ToNew in Version 6.9.1
IssueMany 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.
TasksAn environment name can be configured via the Admin->System->Settings tab.
User-added image
ResolutionOnce 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

...

 
 
NotesInclusion 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.

Attachments

    Outcomes