(Each WebDAV server is connected to a database, and each database is in turn connected to a security database in which security objects such as users are stored.)
The server authenticates users with user IDs and passwords stored in the security database for that WebDAV server, and the server controls access to objects in the database with privileges and roles. WebDAV servers follow the MarkLogic Server security model, as do HTTP, ODBC, and XDBC servers. For an example of this configuration, see Example: Setting Up a WebDAV Server to Add/Modify Documents Used By Another Server.
Webdav server for windows code#
Then, you can edit code from the WebDAV server that executes from an HTTP, ODBC, or XDBC server. You can, however, configure a database as the Modules database of an HTTP, ODBC, or XDBC server and you can configure the same database for access from a WebDAV server. Unlike an HTTP server, there is no Modules database for a WebDAV server. When accessing a database via a WebDAV server, you cannot execute XQuery code. When you add a document via a WebDAV client (by dragging and dropping, for example), you are actually loading a document directly into the database. The database is also accessible via WebDAV clients for reading, modifying, deleting, and adding documents. Documents stored in that database are accessible for reading via HTTP. In the Admin Interface, you configure a WebDAV server to access a database. When a document is read or written via WebDAV, all of its associated data, such as properties, metadata, collections, and so on are also transferred with the document. Each WebDAV server provides access to a single database for reading and writing (dependent on the needed security permissions). In MarkLogic Server, WebDAV servers are defined at the group level and apply to all hosts within the group. → Learn how MarkLogic simplifies data integrationĭatabase Documents, graphs, relational dataĪccesses a Database for Read and Write, Not XQuery Execution