Oracle Audio Technologies ORACLE9I B10508-01 - Manual (Page 169)

Running the Oracle HTTP Server on OpenVMS
Apache Server Installation/Configuration D-23
OpenVMS Cluster Considerations
An OpenVMS Cluster is a group of OpenVMS systems that work together as one
virtual system
.
The Oracle HTTP Server runs in an OpenVMS Cluster so you can
take advantage of the resource sharing that increases the availability of services and
data
. Keep the following points in mind:
■
The Oracle HTTP Server is supported on OpenVMS Alpha Version 7.1-2 or
higher.
■
The Oracle HTTP Server runs in an Alpha or a mixed-architecture cluster.
Individual System versus Clusterwide Definition
To define clusterwide versus individual configuration files, APACHE$ROOT uses the
following concealed logical names:
■ APACHE$COMMON defines clusterwide files.
■ APACHE$SPECIFIC defines system-specific files.
When reading a file, the server first looks for a system-specific version of the file in
APACHE$SPECIFIC:[directory]
. If it does not find one, then it looks for a
clusterwide file in APACHE$COMMON:[directory].
APACHE$CGI_USE_DCLCOM_FOR_IMAGES If defined, this system logical name forces CGI images to
execute within a DCL process
.
The default is to execute
CGI images directly
.
(Note: Direct execution of CGI
images in not currently supported.)
APACHE$DL_NO_UPPERCASE_FALLBACK If defined to be true (1, T, or Y), this system logical name
disables case-insensitive symbol name lookups whenever
case-sensitive lookups fail
.
See
APACHE$DL_FORCE_UPPERCASE.
APACHE$DL_FORCE_UPPERCASE If defined to be true (1, T, or Y), this system logical name
forces case-sensitive dynamic image activation symbol
lookups
.
By default, symbol lookups are first done in a
case-sensitive manner and then, if failed, a second attempt
is made using case-insensitive symbol lookups
.
This
fallback behavior can be disabled with
APACHE$DL_NO_UPPERCASE_FALLBACK.
Table D–2 Oracle HTTP Server Logical Names and Their Descriptions
Logical Name Description