Preface

This guide describes how to administer the Oracle HTTP Server.

This preface contains these topics:

Intended Audience
Documentation Accessibility
Organization
< a href="preface.htm#970681">Related Documentation
Conventions

Intended Audience

The Oracle HTTP Server Administrator's Guide is intended for data base administrators and security managers.

Docume ntation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facili tate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market- leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For ad ditional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle n either evaluates nor makes any representations regarding the accessibility of these Web sites.

Organization

This document contains:

Chapter 1, "O racle HTTP Server Overview"

This chapter describes the Oracle HTTP Server, highl ighting the differences between the Oracle distribution and the open source Apache product on which it is based. It also explains how to start, stop and restart the server.

Chapter 2, "Oracle HTTP Server Concepts"

This chapte r introduces you to the Oracle HTTP Server directory structure, and configuration files, configuration file syntax, modules, and dire ctives.

Chapter&nb sp;3, "Specifying Server and File Locations"

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

Chapter 4, "Managing Server Processes"

This chapter provides an overview of the Oracle HTTP Server processes, and provides information on how to regulate, and monitor these processes.

Chapter 5, "Managing the Network Connection"

This cha pter provides information about specifying IP addresses and ports, and managing server interaction, and network connection persistenc e.

Chapter 6, "Configuring and Using Server Logs"

This chapter discusses Oracle Diagnostic Lo gging, log formats, and describes various log files and their locations.

Chapter 7, "Oracle HTTP Server Modules"

This chapter describes the modules (mods) included in the Oracle HTTP Server. The modules extend the basic funct ionality of the Web server, and support integration between Oracle HTTP Server and other Oracle Database components.

Chapter 8, "Managing Security"

This chapter provides an overview of Oracle HTTP Server security features and c onfiguration information for setting up a secure Web site using them.

Chapter 9, "Frequently Asked Questions"

< p class="BP">This chapter provides answers to frequently asked questions about Oracle HTTP Server.

Chapter A, "Oracle HTTP Server Configuration Fi les"

This appendix lists commonly used Oracle HTTP Server configuration files.

Chapter B, "Thi rd Party Licenses"

This appendix includes the Third Party License for all the th ird party products included with Oracle Database.

Glossary

The glossary defines terminology used throughout this guide a nd the Oracle Database documentation set.

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conve ntions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle9i Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
`UPPERCASE monospace (fixed-width) font`	Uppercase monospace typeface indicates elements supplied by the system. Such elements in clude parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	< /a> You can specify this clause only for a `NUMBER` column. You can back up the database by using the `BACKUP` command. Query the `TABLE_NAME column in the USER_TABLES data dictionary view.` `Use the DBMS_STATS.GENERATE_STATS procedure.`
`lowercase monospace (fixed-width) font`	Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. S uch elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objec ts and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter th ese elements as shown.	Enter `sqlplus` to open SQL*Plus . The password is specified in the `orapwd` file. Back up the datafiles and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_id` columns are in the `hr.department s` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user. The JRepUtil class implements these methods.
`lowercase italic monospace (fixed-width) font`	Lowercase italic monospace font represents placeholders or variables.	You can specify the `parallel_clause`. Run `U``old_release``.SQL` where `old_release` refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal t ext as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code exa mples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	DECIMAL (digits [ , precision ])
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	{ENABLE \| DISABLE}
\|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the ve rtical bar.	{ENABLE \| DISABLE} [COMPRESS \| NOCOMPRESS]
...	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln< /em> FROM employees;
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.	SQL> SELECT NAME FROM V$DATAFILE; NAME ------------------------------------ /fsl/dbs/tbs_01.dbf /fs1/dbs/tbs_02.dbf . . . /fsl/dbs/tbs_09.dbf 9 rows selec ted.
Other notation	You must enter symbols other than brackets, braces, vert ical bars, and ellipsis points as shown.	acctbal NUMBER(11,2); < a name="971230">acct CONSTANT NUMBER(4) := 3;
Italics	Italicized text indicates placeholders or variables for which you must supply particular values.	CONNECT SYSTEM/system_password DB_NAME = database_name
UPPERCASE	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unles s terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees;
lowercase	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: S ome programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9;

Conventions for Windows Operating Systems

The foll owing table describes conventions for Windows operating systems and provides examples of their use.

Convention	Meaning	Example
Choose Sta rt >	How to start a program.	To start the Database Configuration Assistant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant.
File and directory names	File and directory names are not case sensitive. The following special characters are n ot allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (\|), and da sh (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the file name begi ns with \\, then Windows assumes it uses the Universal Naming Convention.	c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32
`C:\>`	Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in thi s manual.	C:\oracle\oradata>
Special characters	The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not requi re an escape character. Refer to your Windows operating system documentation for more information on escape and special characters.	C:\>exp scott/tiger TABLES=emp QUERY=\"WHERE job='SALESMAN' a nd sal<1600\" C:\>imp SYSTEM/password FROMUSER=scott TABLES=(emp, dept) < /td>
HOME_NAME	Represents the Oracle home name. The home n ame can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore.	C:\> net start OracleHOME_NAMETNSListener
`ORACLE_HOME< /code>` `and ORACLE_BASE`	In releases prio r to Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a to p level `ORACLE_HOME` directory. For Windows NT, the default location was `C:\orant`. This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level `ORACLE_HOME` directory. There is a top level directory called `ORACLE_BASE` that by default is `C:\oracle`. If you install the latest Oracle release on a computer with no other Oracle software installed, then the default setting for the first Oracle home directory is `C:\oracle\ora``nn`, where `nn` is the latest release number. The Oracle home directory is located directly under `ORACLE_BASE`. < a name="971307"> All directory path examples in this guide follow OFA conventions. Refer to Oracle9i Database Getting Starting for Windows for additional information about OFA comp liances and for information about installing Oracle products in non-OFA compliant directories.	Go to the `ORACLE_BASE``\``ORACLE_HOME``\rdbms\a dmin` directory.