iTP Secure WebServer System Administrators Guide (Version 7.5+)

NOTE: If the terminal is not in the open state, iTP Secure WebServer does not log any
information and returns error 1020.
logparam1, logparam2 can be STATUS or EVENTFORMAT.
Examples
The following command logs errors and status change messages in a file named MYLOG:
LOG1 MYLOG STATUS
where,
MYLOG is the name of the text file where the status information must be stored.
STATUS sends status change messages and error messages to the file MYLOG.
The following command logs error messages to the primary collector $0, and formats the
messages as event messages:
LOG1 /G/0 EVENTFORMAT
where,
/G/0 is the primary collector.
EVENTFORMAT specifies that messages must be formatted as event messages. If you omit
EVENTFORMAT, text messages are generated.
The following command sends error information to a terminal:
LOG1 /G/$ZTO/#A033H
where,
/G/ZTN0/#PTQUZZB is the terminal name.
PathwayMimeMap
Syntax
PathwayMimeMap mime-type{ pathmon[:serverclassname]][serverclassname}
Description
The PathwayMimeMap directive correlates a previously defined MIME type with the name of the
NonStop TS/MP server class that can handle files of that type.
mime-type
an extension defined by a previous MimeType directive to have a MIME type of
application/x-httpd-guardian.
pathmon
a valid HP name for a PATHMON process in OSS file format (preceded by /G/). The PATHMON
name is optional if the server class is in the same PATHMON environment as the httpd process.
serverclassname
a valid NonStop TS/MP server class name. If you do not specify a server-class name, the server
class is presumed to have the same name as the file, minus the extension. For example, the file
logon.ab_demo would be referred to a server class called logon in the PATHMON environment
indicated by the PATHMON name.
Examples
Here are some examples of the PathwayMimeMap directive. The first example specifies a
server-class name, the second specifies a PATHMON name, and the third specifies both:
230 Configuration Directives