ORAService OraDAV Configuration Parameters

9-12 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server

9.4 OraDAV Performance Considerations

This section provides information that can help you optimize the performance of various operations. It contains the following subsections: ■ Section 9.4.1, Using Disk Caching with OraDAV ■ Section 9.4.2, Bypassing Oracle Web Cache for WebDAV Activities

9.4.1 Using Disk Caching with OraDAV

The performance benefit from disk caching is greatest with medium to large-size files approximately 50 KB and larger. With smaller files, the performance benefit is less, and with very small files the performance can be worse with disk caching than without disk caching. For example, if the file myfile.dat is requested and if the file size is only 24 bytes, the time required for copying the file from the server to the local system is very small compared to the time required for accessing the server to check if the file has changed. If disk caching is not used, there is no check of the server to see if the file has changed, and the file is copied in all cases. You can set the following OraDAV parameters to control disk caching for OraDAV operations: ■ ORACacheDirectory ■ ORACacheTotalSize ■ ORACacheMaxResourceSize ■ ORACachePrunePercent If you specify ORACacheDirectory, disk caching for OraDAV operations is enabled. You must also specify a value for ORACacheTotalSize, and you can specify values for ORACacheMaxResourceSize and ORACachePrunePercent parameters. If you do not specify ORACacheDirectory, disk caching for OraDAV operations is not enabled, and other disk cache-related parameters are not relevant.

9.4.2 Bypassing Oracle Web Cache for WebDAV Activities

Oracle Web Cache enhances performance for most Web activity that involves client read-only operations of data on the Web server system. Oracle Web Cache does not cache OraDAV operations for GET, PUT, LOCK and UNLOCK, which are designed for readwrite capability. For better performance, WebDAV clients can connect directly to Oracle HTTP Server. To bypass Oracle Web Cache for WebDAV clients, you can send requests directly to the Oracle HTTP Server listen port, which is set in the httpd.conf file. By doing this, WebDAV clients will connect directly to Oracle HTTP Server, resulting in better performance than if Oracle Web Cache is used.

9.5 Globalization Support Considerations with OraDAV

The DAVOraUseNLSLang directive provides globalization support for access to the local file systems. This directive specifies whether or not the file names in the file system need to go through conversion using the NLS_LANG setting. A value of Off specifies that no conversion is needed. A value of On specifies that the character set for See Also: Oracle Fusion Middleware Administrators Guide for Oracle Web Cache