Configure

You can activate audit logging for several SuperSTAR components:

SuperADMIN

To activate audit logging for SuperADMIN:

1. Open the SuperADMIN log configuration file (log4j-config.xml) in a text editor. If you installed to the default location, this file is located at C:\ProgramData\STR\SuperADMIN\server\config\log4j-config.xml

2. Locate the following section:

   XML

   <!-- uncomment this line to enable AuditFile
           <appender-ref ref="AuditFile"/>
   -->

3. Remove the comments:

   XML

           <appender-ref ref="AuditFile"/>
   

4. Check the following section, which defines the logging settings:

   XML

       <appender name="AuditFile" class="org.apache.log4j.FileAppender">
           <param name="File" value="C:/AuditLogs/superadmin.log"/>
           <param name="Append" value="false"/>
           <param name="Encoding" value="UTF-8"/>
           <layout class="org.apache.log4j.PatternLayout">
               <param name="ConversionPattern" value="%m%n"/>
           </layout>
       </appender>

   You may wish to change the File setting. This defines the location of the log file. The directory (in this case C:/AuditLogs) will be created automatically if it does not already exist.

   See https://logging.apache.org/log4j/extras/apidocs/org/apache/log4j/rolling/RollingFileAppender.html for help configuring the log4j settings.

5. Save your changes and restart the SuperADMIN server.

SuperSERVER

Activate Audit Logging

SuperSERVER audit logging is enabled by default by the settings in C:\ProgramData\STR\SuperSERVER SA\log4j.scsa.xml, and no changes are required.

SuperWEB2

To activate audit logging for SuperWEB2:

1. Open <tomcat_home>\webapps\webapi\WEB-INF\classes\log4j.xml in a text editor.

2. Locate the following section:

   XML

   <!-- Audit Logging configuration
       <appender name="AuditFile" class="org.apache.log4j.rolling.RollingFileAppender">
           <param name="File" value="C:/AuditLogs/superweb2.log"/>
           <param name="Append" value="true"/>
           <param name="Encoding" value="UTF-8"/>
           <rollingPolicy class="org.apache.log4j.rolling.TimeBasedRollingPolicy">
               <param name="FileNamePattern" value="C:/AuditLogs/%d{yyyy-MM-dd}-superweb2.log"/>
           </rollingPolicy>
           <layout class="org.apache.log4j.PatternLayout">
               <param name="ConversionPattern" value="%m%n"/>
           </layout>
       </appender>
   
       <logger name="au.com.str.webapi.services.common.audit.AuditLogger" additivity="false">
           <level value="INFO" />
           <appender-ref ref="AuditFile"/>
       </logger>
    -->    

3. Remove the comments:

   CODE

       <appender name="AuditFile" class="org.apache.log4j.rolling.RollingFileAppender">
           <param name="File" value="C:/AuditLogs/superweb2.log"/>
           <param name="Append" value="true"/>
           <param name="Encoding" value="UTF-8"/>
           <rollingPolicy class="org.apache.log4j.rolling.TimeBasedRollingPolicy">
               <param name="FileNamePattern" value="C:/AuditLogs/%d{yyyy-MM-dd}-superweb2.log"/>
           </rollingPolicy>
           <layout class="org.apache.log4j.PatternLayout">
               <param name="ConversionPattern" value="%m%n"/>
           </layout>
       </appender>
   
       <logger name="au.com.str.webapi.services.common.audit.AuditLogger" additivity="false">
           <level value="INFO" />
           <appender-ref ref="AuditFile"/>
       </logger>

4. Check the settings in the AuditFile section, and update them accordingly (see the SuperADMIN section above for more details).
5. Save your changes and restart SuperWEB2.

If you want to ensure that SuperWEB2 correctly logs end user IP addresses, rather than the gateway IP address, then you may also need to complete this additional configuration.

Backup and Removal of Log Files

The audit logging service does not provide any mechanism for removing log files, so you will need to implement some process for periodically backing up and removing the files from the server, in order to ensure that there is still enough available disk space on your server.