Skip Headers

Oracle® HTTP Server Administrator's Guide
10g Release 1 (10.1)

Part Number B12255-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

3
Specifying Server and File Locations

This chapter explains how to set Oracle HTTP Server and server administrator options, and specifies file locations.

Topics discussed are:

Documentation from the Apache Software Foundation is referenced when applicable.


Note:

Readers using this guide in PDF or hard copy formats will be unable to access third-party documentation, which Oracle provides in HTML format only. To access the third-party documentation referenced in this guide, use the HTML version of this guide and click the hyperlinks.


Setting Server and Administrator Functions

The following set basic Oracle HTTP Server and administrator functions. They are located in the "Main Server Configuration" portion of the httpd.conf file.

See Also:

"httpd.conf File Structure"

ServerName

Enables the server to set a hostname that can be used to create redirection URLs, through which you can access directories without having to use a "/" at the end.

See Also:

"ServerName directive" in the Apache Server documentation.

UseCanonicalName

Determines which hostname and port to use when redirecting the URL to the same server.

ServerAdmin

Creates an email address that is included with every default error message that clients encounter. It is useful to create a separate email address for this.

See Also:

"ServerAdmin directive" in the Apache Server documentation.

ServerSignature

Enables the server to recognize which server, among the various proxies, created the returned response, such as an error message.

ServerTokens

Controls server information which is returned to clients, such as in error messages. This information includes a description of the generic operating system-type of the server, and compiled-in modules.

ServerAlias

Sets alternate names for the current virtual host.

See Also:

"ServerAlias directive" in the Apache Server documentation.

Specifying File Locations

The following directives to control the location of various server files. They are located in the "Global Environment" of the httpd.conf file.

See Also:

"httpd.conf File Structure"

CoreDumpDirectory

Specifies the directory in which the server dumps core. The default is the ServerRoot directory. This directive is applicable to UNIX only.

See Also:

"CoreDumpDirectory directive" in the Apache Server documentation.

DocumentRoot

Sets the directory from which httpd serves files. Unless matched by a directive like Alias, the server appends the path from the requested URL to the document root to make the path to the document for static content.

See Also:

"DocumentRoot directive" in the Apache Server documentation.

ErrorLog

Sets the name of the file to which the server notes any errors it encounters. If the name of the file does not begin with a slash (/), then it is assumed to be relative to the ServerRoot. If the name of the file begins with a pipe (|), then it is assumed to be a command to spawn to handle the error log.

See Also:

"ErrorLog directive" in the Apache Server documentation.

LockFile

Sets the path to the lockfile used when Oracle HTTP Server is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or USE_FLOCK_SERIALIZED_ACCEPT. It is recommended that default value be used. The main reason for changing it is if the logs directory is NFS mounted, since the lockfile must be stored on a local disk.

See Also:

"LockFile directive" in the Apache Server documentation.

PidFile

Enables you to set and change the location of the PID file to which the server records the process identification number. If the filename does not begin with a slash (/), then it is assumed to be relative to the ServerRoot.

See Also:

"PidFile directive" in the Apache Server documentation.

ScoreBoardFile

Required in some architectures to set a file that the server uses to communicate between the parent and children processes. To verify if your architecture requires a scoreboard file, run Oracle HTTP Server and see if it creates the file named by the directive. If your architecture requires it then you must ensure that this file is not used at the same time by more than one invocation of the server.

See Also:

"ScoreBoardFile directive" in the Apache Server documentation.

ServerRoot

Specifies the directory that contains the conf and logs subdirectories. If the server is started with the -f option, then you will have to specify ServerRoot.

See Also:

"ServerRoot directive" in the Apache Server documentation.