All Collections
Install and Configure
Configuration
Setting Access Log Valve on Definition Center to Track HTTP Traffic
Setting Access Log Valve on Definition Center to Track HTTP Traffic
This article describes how to enable the access log valve in the Tomcat instance associated with a Definition Center.
Jamie Gutierrez avatar
Written by Jamie Gutierrez
Updated over a week ago

Applies to


 The article applies to the following products and versions:
 
 ​Product: iRise Definition Center
 Versions: all versions

Summary

This article describes how to enable the access log valve in the Tomcat instance associated with a Definition Center and see traffic to and from the Definition Center with addresses of machines requesting information

Instructions

Tomcat provides an access log valve that when enabled will log all traffic to and from the server detailing the addresses of the machines making the request or receiving the data. This information is useful to check and make sure that only authorized users are attempting to access a Definition Center

To make the change follow these steps:

  1. Open the x:\iRise\DefCenter\Tomcat\conf\server.xml file in a text editor

  2. Search for the following block of code in the file:

<!--
     <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"  
      prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
-->
  1. Uncomment the line by removing the opening <!-- and closing --> tags

  2. Stop and start the iRise Definition Center service


 Note the new log created in x:\iRise\DefCenter\Tomcat\logs directory named localhost_access_log.yyyy-mm-dd with the new content.

As with all new log files, check to make sure that the volume of traffic to your Definition Center does not create overly large log files that consume lots of disk space. Monitor the log sizes periodically and consider implementing batch processing to archive or delete older access valve log files after a certain time period

Did this answer your question?