Applications Systems

Log DPA user activity

DPA does not have internal auditing of user logins. If you are interested in tracking that activity (for example, to see the deployment success of DPA or for other reasons), complete the following steps to turn on auditing in the backend application server.

First published date

10/22/2018 8:57 AM

Last published date

2/7/2023 4:12 PM

Overview

DPA does not have internal auditing of user logins. If you are interested in tracking that activity (for example, to see the deployment success of DPA or for other reasons), complete the following steps to turn on auditing in the backend application server.

Product section

Database Performance Analyzer

Resolution

  1. Stop DPA's process or service. In a Linux DPA application server this means to run ./shutdown.sh inside DPA_HOME. If you are not sure where DPA is running from or where this is you can run the following to find the process 
    ps -ef | grep dpa
    On a Windows install of DPA this is the service called "Ignite PI Server" 
  2. Navigate to the directory DPA_home/iwc/tomcat/conf where DPA_home is where DPA is installed.
  3. Open the server.xmlfile in a text editor.
  4. Near the end, locate a line similar to:
     
    <host name="localhost" appbase="webapps"/>
  5. Replace this with the following:
    <Host name="localhost" appbase="webapps">
      <Valve className="org.apache.catalina.valves.AccessLogValve"
             directory="logs" prefix="dpa_access_log" suffix=".log"
             pattern="%t %h %{userSession}s %S %r %q" />      
    </Host>
  6. Restart DPA's process or service. On a Linux DPA app server this means run ./startup.sh found in DPA_HOME. On a Widnows DPA app server restart the "Ignite PI Server" service. 

DPA user logins will now be logged to the dpa_access_log.log file in the DPA_home/iwc/tomcat/logs directory.