iTP Secure WebServer System Administrator's Guide (Version 7.0)

Server Log File Formats
iTP Secure WebServer System Administrator’s Guide—523346-012
C-8
Logging through an External ServerClass
Therefore the need for clients to maintain their own log repository in a secured location
arises.
This is achieved through a user-written logging serverclass. You must develop your
own TS/MP serverclass to read, manipulate and, if required, return the log strings
generated by httpd. You must provide the name of the logging serverclass using the
following LoggingServerClass configuration directive:
LoggingServerClass <serverclass name>
For example,
LoggingServerClass LogServ
Figure C-1 shows the functional overview of the LoggingServerClass directive.
Following are the design guidelines for developing the logging serverclass:
1. If a logging serverclass is used, httpd does not initially log any information to
access.log and httpd.log.
2. Log strings are sent to the configured logging serverclass through pathsend.
3. If the Pathsend operation fails, corresponding Pathway error gets logged in the
error log
Figure C-1. Logging Using External Serverclass
VST023.vsd
Sends the request
containing card
information
Sends the
modified log
strings back to
iTP Secure
WebServer
User
HTTPD
User-written
LoggingServerClass
HTTPD generates
log strings
Sends the modified
log strings back to
a separate log
repository
Repository