![]() On – indicates that mod_oradav is to use the local file system for content. The DAV keyword is followed by one of the following values: The DAV parameter indicates that a URL location is DAV-enabled. To configure the parameters use Fusion Middleware Control. WebDAV clients assign properties to documents using the PROPPATCH directive and retrieve properties using the PROPFIND directive. Property Management: Associating properties and attributes (for example, author) with documents for ease of lookup and for categorization. Properly designed WebDAV clients use shared or exclusive locks on such resources to coordinate these activities. If the directory is shared, then the client doing restructuring is given sole access to the hierarchy through WebDAV exclusive locks.Įditing: Modifying one or a small subset of resources in a hierarchy. In some cases, this directory hierarchy is owned and managed by one user. Restructuring has the same limitations and complications that one encounters when restructuring a file directory. Restructuring is usually done infrequently by a restricted set of individuals who have write access to the WebDAV content. ![]() Restructuring: Deleting, moving, and copying content. It does allow read-only activity by Web browsers and WebDAV clients. A value of On prevents WebDAV clients from performing write operations while using WebDAV. A value of Off specifies that WebDAV clients function normally. The DAVOraReadOnly directive specifies whether or not WebDAV should be used in a read-only mode by WebDAV clients. Its usage model is typical of a read-only Web site. OraDAV usage can involve any combination of the following activities:īrowsing: Read-only activity which uses WebDAV to access content on the file server. Set-based operations such as COPY, MOVE, DELETE can be done completely by a single call to an OraDAV driver. The OraDAV API supports shared and exclusive locking, retrieving basic DAV properties, and defining and retrieving server-defined properties or client-defined properties. PROPPATCH: Sets the properties for a file. PROPFIND: Gets properties defined for a file. This method is not supported by Oracle Web Cache. LOCK: Locks a file when the file is checked out. HEAD: Gets the header content of a file without retrieving the file. MOVE: Moves files within a Web site folder. The following HTTP methods are supported by the OraDAV API:ĬOPY: Copies files within a Web site folder.ĭELETE: Deletes files within a Web site folder. The OraDAV API capabilities are equivalent to using the mod_oradav module running with a file system. If the request is for content stored in Oracle Portal, the OraDAV API handles the access. If the request is for content stored in the file system, the mod_oradav module handles the access. The content editors need to know how to connect to the server, and upload and retrieve files.ĭescription of "Figure 9-1 OraDAV Architecture"įigure 9-1 shows a WebDAV client, such as Web folders, passing HTTP requests to Oracle HTTP Server. The Web administrator needs to know how to start and stop Oracle HTTP Server, and how to configure Oracle HTTP Server to direct URL traffic to an OraDAV driver. OraDAV interaction requires the following proficiency: ![]() End users interact only indirectly with OraDAV through Web browsers or WebDAV client tools. The primary users of OraDAV are Oracle HTTP Server Web administrators and content editors. OraDAV driver: Stored procedure implementation of the OraDAV driver API that runs in Oracle and manages a repository. Retrieving properties associated with documentsĪssociating properties with specific documents Managing, such as creating, populating, and deleting, hierarchies of information OraDAV API: Stored procedure calls that are used by the OraDAV driver to provide support for the following WebDAV functions over the Internet: For more information about DAV directives, see the article written by Greg Stein ( available at
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |