Skip Headers
Oracle® Process Manager and Notification Server Administrator's Guide
10g Release 3 (10.1.3.1.0)

Part Number B28944-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
Contact Us

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

7 Configuring Oracle HTTP Server

This chapter describes Oracle HTTP Server configuration in the OPMN opmn.xml file.

It features the following topics:


Note:

  • Only one Oracle HTTP Server can be configured for each ORACLE_HOME.

  • Oracle Application Server 10g Release 3 (10.1.3.1.0) comes with Oracle HTTP Server based on Apache 1.3. This version of Oracle Application Server cannot be configured to run Oracle HTTP Server 2 based on Apache 2.

  • To obtain Oracle HTTP Server 2 you must use the Oracle HTTP Server 2 standalone install. The Oracle HTTP Server 2 standalone installation is available on the companion CD. The Oracle HTTP Server 2 installation cannot be configured to run Oracle HTTP Server.


7.1 Oracle HTTP Server Process Module Configuration

The following lines load and identify the Oracle HTTP Server process module. Management of Oracle HTTP Server processes by the process module are identified by the module id.

<module path="ORACLE_HOME/opmn/lib/libopmnohs.so">
   <module-id="OHS"/>
</module>

7.2 Oracle HTTP Server Minimum Configuration

The following lines represent the minimum configuration for Oracle HTTP Server. Default values are assigned to all other configuration elements and attributes for Oracle HTTP Server.

<ias-component id="HTTP_Server">
   <process-type id="HTTP_Server" module-id="OHS">
      <process-set id="HTTP_Server" numprocs="1"/>
   </process-type>
</ias-component>

7.3 Oracle HTTP Server Complete Configuration

The following lines show a complete configuration for Oracle HTTP Server. It contains all possible configuration elements and attributes for Oracle HTTP Server.

<ias-component id="HTTP_Server" status="enabled" id-matching="false">
   <process-type id="HTTP_Server" module-id="OHS">
      <process-set id="HTTP_Server" restart-on-death="true" numprocs=1>
         <module-data>
            <category id="start-parameters">
               <data id="config-file" value="/myconfs/httpd.conf"/>
               <data id="start-mode" value="ssl-disabled"/>
               <data id="command-line" value="-D MyDefine"/>
               <data id="routing-id" value="routing id">
            </category>
            <category id="ping-parameters">
               <data id="ping-url" value="/"/>
            </category>
            <category id="restart-parameters">
               <data id="reverseping-timeout" value="345"/>
               <data id="no-reverseping-failed-ping-limit" value="3"/>
               <data id="reverseping-failed-ping-limit" value="6"/>
            </category>
         </module-data>
            <start timeout="300" retry="3"/>
            <stop timeout="300"/>
            <restart timeout="300"/>
            <ping timeout="30" interval="30"/>
      </process-set>
   </process-type>
</ias-component>

7.4 Oracle HTTP Server Attribute Descriptions

This section describes the attributes that are specific for Oracle HTTP Server.

The Oracle HTTP Server attributes are described with the following format:

id="HTTP_Server"


Required: true
Default: none
Valid values: HTTP_Server
Path: ias-component
Path: ias-component/process-type
Path: ias-component/process-type/process-set

The id attribute is required and cannot be changed. The id must match the targets.xml entry or Application Server Control Console will not work.

module-id="OHS"


Required: true
Default: none
Valid values: OHS
Path: ias-component/process-type

The module-id attribute defines the type of process. It associates the configuration with a process module. The OHS module-id can be configured for managing Apache 1.3.

numprocs=1


Required: true
Default: none
Valid values: 1
Path: ias-component/process-type/process-set

The number of Oracle HTTP Server Instances to start. Only valid value is 1.

The numprocs attribute gives the number of Oracle HTTP Server instances to start. The only valid value is 1.

id="start-parameters"


Required: false
Default: none
Path: ias-component/process-type/process-set/module-data/category

The start-parameters category contains the parameters that are relevant for the startup of Oracle HTTP Server.

id="config-file"


Required: false
Default: ORACLE_HOME/Apache/Apache/conf/httpd.conf
Valid values: any full path to an existing configuration file
Path: ias-component/process-type/process-set/module-data/category/
data

The config-file id is an start command option which specifies the httpd.conf for starting Oracle HTTP Server. The config-file id is not supported on Microsoft Windows

id="start-mode"


Required: false
Default: ssl-disabled
Valid values: ssl-enabled/ssl-disabled
Path: ias-component/process-type/process-set/module-data/
category/data

This option specifies whether Oracle HTTP Server will be started with ssl enabled.

id="command-line"


Required: false
Default: none
Valid values: any valid command line options to Oracle HTTP Server
Path: ias-component/process-type/process-set/module-data/
category/data

This id option specifies extra command lines to append to the Oracle HTTP Server command line.

id="routing-id"


Required: false
Default: none
Parents: category
Attributes: value

The routing-id defines the value for the routing ID module.

You can configure the routing-id element for Oracle HTTP Server in both the opmn.xml file and in the configuration for Oracle HTTP Server. However, if the routing-id element is configured in both locations, OPMN will not start.

value="routing id"


Required: true
Default: none
Valid Values: Any string.

The Routing ID specifies a routing relationship between OC4J and Oracle HTTP Server. In other words, an Oracle HTTP Server routes to every OC4J that it shares a routing ID with. Out of the box, the routing ID is specified as a module data under the ias-instance in the opmn.xml file. The value of the default routing-id is g_rt_id. Because of the hierarchical nature of the opmn.xml file, every component configured in the opmn.xml file inherits the configured routing ID. You can configure a separate routing ID for any Oracle HTTP Server or OC4J by configuring a routing ID at a lower level in the opmn.xml file. As with most entities in the opmn.xml file, like entities configured at a lower level override those configured at a higher level.

id="ping-parameters"


Required: false
Default: none
Path: ias-component/process-type/process-set/module-data/
category

The ping parameters category contains the parameters that configure how OPMN pings Oracle HTTP Server.

id="ping-url"


Required: false
Default: /
Valid values: the path portion of an url; for example: http://127.0.0.1/<path>
Path: ias-component/process-type/process-set/module-data/
category/data

The ping-url id specifies the URL at which OPMN pings Oracle HTTP Server.

id="restart-parameters"


Required: false
Default: none
Path: ias-component/process-type/process-set/module-data/
category

The restart-parameters category is used for defining parameters that will be used in death-detection.

id="reverseping-timeout"


Required: false
Default: 300 seconds
Valid values: Any reasonable timeout value
Path: ias-component/process-type/process-set/module-data/
category/data

The reverseping-timeout value is the maximum allowable time between two notifications arriving from an Oracle HTTP Server process. As part of death-detection, the Oracle HTTP Server module performs forward pings on the Oracle HTTP Server process. In the event that forward pings start failing, the reverse pings are taken into account in death-detection and Oracle HTTP Server processes are restarted.

id="no-reverseping-failed-ping-limit"


Required: false
Default: 1
Valid values: Any reasonable value that reflects the tolerance that OPMN should have for failed forward pings when reverse pings are also failing. This tolerance is used by OPMN to determine when the process should be declared as unresponsive and replaced.
Path: ias-component/process-type/process-set/module-data/category/
data

This id module data element defines the tolerance for failed forward pings in the event that reverse pings are also not being received (within the timeout period specified by the reverseping-timeout data element). After the number of ping failures equals this limit, the process is deemed unresponsive and restarted by OPMN.

id="reverseping-failed-ping-limit"


Required: false
Default: 3
Valid values: Any reasonable value that reflects the tolerance that OPMN should have for failed forward pings when reverse pings are being received. This tolerance is used by OPMN to determine when the process should be declared as unresponsive and replaced.
Path: ias-component/process-type/process-set/module-data/category/
data

This module data element defines the tolerance for failed forward pings when reverse pings are succeeding. After the number of ping failures equals this limit, the process is deemed unresponsive and restarted by OPMN.

7.5 Oracle HTTP Server 2

The Oracle HTTP Server 2 based on Apache 2 (OHS2) module ID is used to manage the version of Apache 2 shipped with Oracle Application Server 10g on the companion CD.

module-id="OHS2"


Required: true
Default: none
Valid values: OHS2
Path: ias-component/process-type

The module-id attribute defines the type of process. It associates the configuration with a process module.

id="mpm"


Required: false
Default: prefork
Valid values: worker/prefork
Path: ias-component/process-type/process-set/module-data/
category/data

This option specifies what threading model OHS2 should use. This option is only valid for OHS2 and is only valid on Linux platforms.

Oracle does not support the perchild MPM. Microsoft Windows uses the mpm_winnt MPM.

7.6 Generic Apache (Linux only)

The Oracle HTTP Server process module can be configured to manage generic Apache processes. Follow these steps to configure the Oracle HTTP Server process module to manage generic Apache:

<ias-component id="HTTP_Server">
   <process-type id="HTTP_Server" module-id="GENERIC_APACHE">
      <module-data>
         <category id="start-parameters">
            <data id="apache-home" value="/private1/apbuild/runapache_1.3.27"/>
         </category>
      </module-data>
      <process-set id="HTTP_Server" numprocs="1"/>
   </process-type>
</ias-component>