Skip Headers
Oracle® HTTP Server Administering a Standalone Deployment Based on Apache 1.3
10g Release 2 (10.1.2)
  Go To Documentation Library
Go To Product List
Solution Area
Go To Table Of Contents
Go To Index


B Configuration Files

This appendix lists commonly used Oracle HTTP Server configuration files.

Files discussed are:

B.1 dms.conf

Enables you to monitor performance of site components with Oracle's Dynamic Monitoring Service (DMS).

It is located at:

B.2 httpd.conf

This is a server configuration file which typically contains directives that affect how the server runs, such as user and group IDs it should use, and location of other files. Because the server configuration file is the main file that the server starts with, Oracle HTTP Server does not include any directive that says where to locate it. The location is passed on command line when the server starts.

It is located at:

You should use only this file, and not srm.conf or access.conf because it is much easier to manage a single configuration file.


If you have an Oracle Application Server installation in /home/your_directory/orahome and it is linked to /private/your_directory/orahome, the files in the installation are accessible from either /home/your_directory/orahome or /private/your_directory/orahome.

After installation, the httpd.conf file contains an entry for the dms.conf file that uses the original Oracle home path. For example:

include /home/your_directory/orahome/Apache/Apache/conf/dms.conf

Do not replace the original Oracle home path with the linked Oracle home path.

B.2.1 httpd.conf File Structure

httpd.conf is arranged in the following sections:

B.2.1.1 Global Environment

This is section one of the httpd.conf file. It contains configuration directives dealing with Oracle HTTP Server.

B.2.1.2 Main Server Configuration

This is section two of the httpd.conf file. It contains the directives of the default server.

B.2.1.3 Virtual Hosts Parameters

This is section three of the httpd.conf file. It contains parameters specific to virtual hosts, which override some of the main server configuration defaults.

B.3 iaspt.conf

Configures the port tunneling process. Port tunneling allows all communication between Oracle HTTP Server and OC4J to happen on a single, or a small number of ports.

It is located at:

B.4 mime.types

Controls the Multi Internet media types that are sent to the client for the given file extensions. Sending the correct media type to the client is important so that the client knows how to handle the content of the file. You can add extra types in the mime type file or add an AddType directive in the configuration file.

It is located at:

See Also:


B.5 mod_oc4j.conf

Configures and loads the mod_oc4j module, and is enabled by default. It routes requests from Oracle HTTP Server to OC4J, and therefore contains routing information.

It is located at:

See Also:


B.6 mod_osso.conf

Configures mod_osso, which enables single sign-on for Oracle HTTP Server.

It is located at:

See Also:


B.7 opmn.xml

Describes the processes that Oracle Process Manager and Notification Server (OPMN) manages within an Oracle Application Server installation.

The opmn.xml file is the main configuration file for OPMN. It contains information for the ONS, the PM, and Oracle Application Server component-specific configuration. opmn.xml shows you which Oracle Application Server components OPMN is managing on your system. It contains Oracle Application Server component entries arranged in the following hierarchical structure:


opmn.xml is located at:

B.8 oracle_apache.conf

Stores configuration files of supported modules.

It is located at:


For the Oracle Application Server Infrastructure install type, another configuration file is included by oracle_apache.conf called oracle_ocm.conf. It contains configuration for Oracle Application Server Certificate Authority.

B.9 php.ini

Configures mod_php. This file should not be renamed as PHP looks for this specific file name.

It is located at:

See Also:


B.10 ssl.conf

Includes the SSL definitions and virtual host container. Out of the box, it is disabled by default.

It is located at: