iTP Secure WebServer System Administrators Guide (Version 7.5+)

httpd server class cannot have name other than httpd when distributor is used (The distributor
continues to work with the httpd server class that has httpd as the default name). If httpd
is renamed when distributor is used, startup fails with a relevant error.
2. Standard values such as gcache, distributor, httpd are default values for gcache,
distributor, and httpd respectively and must not be used as server class names for server
classes.
3. This directive is to support renaming of server classes. Multiple Server definitions for httpd and
gcache with different ServerClassName value must not be specified in the same configuration
file. The iTP Secure WebServer would start successfully with these conditions, but would not
function normally. For multiple httpds and gcache, use –add feature of httpd.
4. While using restarth, value for ServerClassName must not be changed for httpd
serverclass.
5. If multiple httpds for secure version are configured along with gcache enabled for all configured
httpds using the –add feature of httpd, gcache server class must have different server
class names for different httpds.
6. You cannot rename the Admin serverclasses.
Security security-attribute
specifies the users, in relation to the owner of the server, who can access a server class from a
Pathsend requester.
The security attributes are the same as the Guardian file-security attributes. The values are:
Any local userA
A group member or ownerG
Owner onlyO
Local super ID-
Any local or remote userN
Any member of owner's community (local or remote user having same group ID as owner)C
Any member of owner's user class (local or remote user having same group ID and user ID as owner)U
If you do not specify the Security command for a server, the default is O.
An example of the Security command is:
Security O
This command is optional.
Stdin file-name
specifies the standard input file for the server. The value is an OSS path name. If you do not specify
standard files, the process starts without a standard file environment.
If you specify Stdin, you also must specify Stdout and Stderr. If you specify the Debug directive,
the home terminal becomes the standard input file, regardless of the value you specified for Stdin.
The following example specifies the home terminal as the standard input file and two different log
files as the standard output and error files.
set env(HOMETERM) [exec tty]
eval $DefaultServerAttributes
Stdin $env(HOMETERM)
Stdout /web/xyz/startup/t8997/logs/stdout.log
Stderr /web/xyz/startup/t8997/logs/stderr.log
If the server you are defining is a CGI server class, specifying the home terminal as the standard
input file is useful only for debugging your program outside the iTP Secure WebServer environment.
For a CGI server class in the iTP Secure WebServer environment, specify a value of /dev/null.
Stdout file-name
specifies the standard output file for the server. The value is an OSS path name. If you do not
specify standard files, the process starts without a standard file environment.
Server 251