OraDAV Architecture Introduction to the mod_oradav Module

Configuring mod_oradav 9-5 Finally, you can simply omit PROPFIND from the limits if your Web server is intended as a general, read-only repository of files. This allows anybody to arbitrarily browse the directories and to fetch the files.

9.2 Configuring mod_oradav

Use the Advanced Server Configuration page of Fusion Middleware Control to configure the mod_oradav module. This section includes the following subsections: ■ Section 9.2.1, OraDAV Configuration Parameters ■ Section 9.2.2, Using Fusion Middleware Control to Configure mod_oradav

9.2.1 OraDAV Configuration Parameters

When Oracle Fusion Middleware is installed, all required OraDAV parameters are set to their default values. If the default values do not meet your needs, you can modify the values for required parameters and specify values for optional parameters. The OraDAV parameters in the mod_oradav.conf file start with DAV and DAVParam. The DAV parameter indicates that a URL location is DAV-enabled. The DAV keyword is followed by one of the following values: ■ On – indicates that mod_oradav is to use the local file system for content. ■ Oracle – indicates that mod_oradav is to use OraDAV for all content. The DAVParam parameters are used to specify name-value pairs. The required pairs are those that enable Oracle HTTP Server to connect to an Oracle database. These include the names OraService, OraUser, and OraPassword or OraAltPassword. Each OraDAV driver can use the DAVParam mechanism to create its own driver-specific settings. All DAVParam name-value pairs are passed to the OraDAV driver. In addition to the OraDAV parameters, you should consider whether to specify additional DAV parameters, such as DavMinTimeout. Example 9–1 shows the syntax to configure access to files on the local system. It specifies that the directory dav_portal under the Web server documents directory is to be DAV-enabled, along with all directories under dav_portal in the hierarchy. There must not be any symlinks defined on the dav_portal directory or any of its subdirectories. Example 9–1 Configuring File System Access Location dav_portal DAV On Location The following recommendations should be considered when mapping containers under the root location: Note: To configure the parameters use Fusion Middleware Control. Do not edit the mod_oradav.conf file directly. Doing so may harm your installation. 9-6 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server ■ Do not map the root itself. For example, do not specify Location in the mod_oradav.conf file. ■ Do not map a container as a subelement in the hierarchy to another container. For example, do not specify the containers Location project1 and Location project1project2. It is acceptable to specify Location project1 and Location project2. ■ Do not create any symbolic links to the container or any location under the container in the hierarchy. The OraDAV parameters are described in the following sections: ■ ORAAllowIndexDetails ■ ORAAltPassword ■ ORACacheDirectory ■ ORACacheMaxResourceSize ■ ORACachePrunePercent ■ ORACacheTotalSize ■ ORAConnect ■ ORAConnectSN ■ ORAContainerName ■ ORAException ■ ORAGetSource ■ ORALockExpirationPad ■ ORAPackageName ■ ORAPassword ■ ORARootPrefix ■ ORAService ■ ORATraceEvents ■ ORATraceLevel ■ ORAUser

9.2.1.1 ORAAllowIndexDetails

In an Oracle HTTP Server environment that is not OraDAV-enabled, mod_dav does not respond to HTTP GET requests. Instead, normal Oracle HTTP Server mechanisms are used to respond to GET requests. The ORAAllowIndexDetails parameter controls how OraDAV responds when a GET request is performed on a DAV collection and no index.html file is found in the directory. In a typical Oracle HTTP Server environment, a separate module takes control, automatically generating and returning to the client HTML that represents an index of the resources files in that collection. An OraDAV-enabled Oracle HTTP Server performs similar actions when responding to a GET request on a collection. A description column containing links to more detailed information about each resource is included in the generated index when ORAAllowIndexDetails is set to TRUE.