Following the instructions below will enable logging in the Aeon Web DLL.
DLL Logging should only be enabled to aid in the diagnosis of a problem because the log files tend to get large quickly.
Beginning with Aeon 4.0, EAD contents are no longer included in log statements. Prior to Aeon 4.0, when the Aeon Web DLL processed finding aid requests, it downloaded the finding aid (EAD) and logged the file contents in their entirety at the debug level. Since EADs can be very large, this would often cause the log files to fill up and roll over very quickly if debug logging is enabled.
To enable logging in the Aeon DLL, you will need to create a new file with the text below. This file needs to be saved as log4d.props on the web server in the same directory where the aeon.dll is running (usually C:\program files\aeon\web). The text of the log4d.props file should be:
#---- begin log4d.props ----
# root priority - valid values are 'DEBUG', 'INFO', 'WARN', 'ERROR', 'FATAL'
# root appender
log4d.appender.ROOT.fileName=C:\Program Files (x86)\Aeon\logs\AeonDLL.log
log4d.appender.ROOT.layout.pattern=%d [%p] %c (%t) - %m%n
#---- end log4d.props ----
The DLL will now log to a file called C:\program files\aeon\logs\AeonDLL.log. This can be edited to another name or location. If you have multiple web folders (shared server or using test web), you can make a different log4d.props file in each web folder that points to another file name for that log. You may need to change the permissions on the c:\program files\aeon directory to allow the Internet Guest Account (IUSR_AEON or similar) to create and write to a file. That file may not allow you to open it while the dll is still running. You may need to stop and restart the web server to open the file.
To disable logging in the Aeon DLL, rename the log4d.props file to something else (i.e. disable-log4d.props). If the DLL cannot find that file, it will not log any actions.