Introduction
Digipass S3 Software provides 4 primary diagnostic logs using the Log4j2 package. These are invaluable tools for confirming operations, troubleshooting issues, and monitoring your deployment.
Component | Log File Directory | Log File | Configuration File |
|---|---|---|---|
Authentication Server | <TOMCAT_HOME>/logs | nnl.log, nnl_hist_data_failure.log | <TOMCAT_HOME>/conf/nnl/log4j2-nnl.xml |
API Server | <TOMCAT_HOME>/logs | nnlgateway.log | <TOMCAT_HOME>/webapps/nnlgateway/WEB-INF/classes/log4j2.xml |
Admin Console | <TOMCAT_HOME>/logs | nnl-admin.log | <TOMCAT_HOME>/webapps/nnladmin/WEB-INF/classes/log4j2.xml |
Command Line Interface | <MFAS_HOME>/admin/logs | nnl-mgmt.log | <MFAS_HOME>/admin/conf/log4j2.xml |
Where <TOMCAT_HOME> is the full path of the Tomcat installation used when installing the Digipass S3 Server. <MFAS_HOME>is the full path of the Authentication Server.
Depending on the logging level, these logs can quickly grow in size, consuming system resources. This section covers the most commonly performed configuration tasks which include changing the following:
log4j2-nnl.xml configures several logs generated by the Authentication Server, including nnl.log, nnl_hist_data_failure.log, and tenant-specific audit files. As a result, it is important to follow the instructions below to verify that you are editing the correct section in log4j2-nnl.xml. To give you context for where you can make edits, refer to Example log4j2-nnl.xml.
To modify other logging configurations, refer to the Log4j documentation.
Log4j 2 picks up changes to the configuration file every 2 minutes. You can either wait or restart the Tomcat service to apply your changes.