Logs

Web Server/400 includes a logging facility which helps the WebMaster maintain the server. The access log reports all attempts to access documents on the server within either a text file using an industry defacto standard format, or within a Data Base file which provides a superset of the text file information. The statistics logs keep track of the Web Server/400's statistics including performance measurements, the cumulative amount of data, and number of requests handled. There are two types of statistics log files. The first type provides a formatted version of calculated data within either a text file or within a Physical File using multiple single field records to hold the formatted text. The second type of statistics log provided is stored within a multi-field Data Base file containing the raw data which was used to calculate the text version of the statistics log. The error log is the location that the WebMaster checks to find any errors that may be occurring within the server.

Included within the logging facility is the ability to cycle the log files. The log file cycling capability gives the WebMaster the ability to set up a schedule when the error or access log files should be rotated or in the case of the statistics logs, an information snapshot appended to the file(s).

NOTE: Logging from within multiple Web Servers to the same log file is prohibited. If the log file is locked when the server attempts to cycle it, the cycling will be suspended until the file is unlocked. If a tool or another instance of the Web Server has the file open this will lock the file, suspending the log file cycling until the file is closed (unlocking the file).

Server User Profile Authority Considerations

The Server User Profile requires Read, Write and eXecute authorities for all directories containing any of the logs. Note that the authorities assigned to all log files created, including cycled log files will only include the *PUBLIC authorities and the authorities of the server user profile. The *PUBLIC authority will be assigned the same as the library or directory where the log file exists. Any special authorities granted or denied to other users will not be carried forward from the library or directory. This limitation exists because the server user profile should, in most cases, have limited authorities for security reasons.

Migration Notes for Version 1.0 Customers Logging to Log Files within QSYS

Note: Logging within the QSYS file system has changed from Web Server/400 version 1.0. In version 1.0 the WebMaster was required to create the single field log file prior to starting the server. Beginning with version 1.1 this requirement has been removed. If the log file does not exist, it will be created. The file formats have changed, and the log files only support one member within them. If multiple members exist within the file, only the first member will be used. With the exception of the statistics text log file, each log file stored within the QSYS file system will use a multi-field record format. Migration from version 1.0 to a later version will require that the WebMaster ensure that any log files currently being logged to the QSYS file system either be changed to a new filename, or that the current file be deleted. The reason behind the migration requirements is that the newer versions require a new record format. If you are running version 1.1 or greater of Web Server/400, the new log file will be created with the appropriate record format.