Logs Webulator/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 error log is the location that
the WebMaster checks to find any errors that may be occurring within the
If the log file does not exist, it will be created. The log files only
support one member within them. If multiple members exist within the file, only
the first member will be used. Each log file stored within the QSYS file system
will use a multi-field record format.
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
NOTE: Logging from within multiple Webulator/400 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.