There is an internal audit requirement to track user login access to AR System server. There is current user login information available in License Review on the AR System Administration Console with User Name, Connect Time and Last Access Time information. Where is this information located?

Legacy ID:KA410061

User access to ARServer is retained in memory cache and is not recorded as data.  The information displayed on the Manage User License form from selecting License Review is retrieved from memory at the time the data is displayed and is not retained as data.  This is point in time information.  The information can be captured and retained, however, in User logging output in either file output or retained as data in a form when selecting the Form rather than File log option. 

Points to consider:
1) if User logging is not turned on, login activity will not be captured
2) the User logging will have to be turned on for every ARServer connecting to a common database
   - all ARServers in a server group environment
   - all ARServers operating as independent ARServers but connecting to the same database
3) there is no option to refine logging output to capture only a single entry for just a login or logout action of a user and a significant volume of information will be generated which will need to be managed
   a) when logging to a file
      1. the size of the file can be managed using the Append option and setting a maximum log file size
      2. the maximum log file size will need to be large enough to allow time to extract the required information before overwrite occurs
      3. the method for extracting the required information will be custom development
      4. the information generated will be discrete to each ARServer log file
   b) when logging to a form
      1. all ARServers connecting to the database will create entries in the same form
      2. the Server Name field on the form is populated when the ARServer is running as a member of a server group
      3. there is a one-to-one correlation between entries in the log file and records added to the log form and the volume of records created will be significant
      4. possible methods for managing the volume of records can be workflow that will delete records that are not of interest
         - a filter that will delete records that are not of interest on submit
         - an escalation that will delete records that are not of interest on a given time interval
      5. it is strongly recommended that there be evaluation of impact from volume of records created and impact from any workflow to manage those records before implementing
      6. it is strongly recommended that monitoring be done on a regular basis after implementing until there is a high level of confidence that there is no negative impact on ARServer or database performance

1. BMC Remedy AR System Server