MarkLogic Server runs on a variety of platforms. For a list of support platforms and installation procedures, see the Installation Guide
The start, stop, and restart operations for MarkLogic Server are described in Starting and Stopping MarkLogic Server.
Several types of auxiliary databases are created when you install MarkLogic Server, which are described in Understanding Databases. This section outlines the general procedures for creating a database to store your documents.
An application is executed on an App Server, which is configured with a specific database, port number, and so on. Once you have created a database, you can create an App Server. MarkLogic Server allows you to create three types of App Servers to support different types of applications:
To secure your App Server using SSL, see Configuring SSL on App Servers.
MarkLogic Server provides a rich set of security objects that enable you to control user access to documents and applications, which are described in the Understanding and Using Security Guide and in Security Administration in this guide.
You can load documents into the database using the load document functions, as described in the Loading Content Into MarkLogic Server Guide.
You can also set up a WebDAV server and client, such as Windows Explorer, to load your documents. See Simple Drag-and-Drop Conversion in the Content Processing Framework Guide for information on how to configure a WebDAV server to work with Windows Explorer.
To test your MarkLogic Server configuration, Follow the procedure in Getting Started with MarkLogic Server for Exploring the Use Cases. The procedure uses Query Console to evaluate the W3C XQuery use cases.
For procedures on building a simple XQuery application, see Sample XQuery Application that Runs Directly Against an App Server in Getting Started with MarkLogic Server. For more in-depth information, see the Application Developer's Guide. If you are writing a Java or .NET application that communicates with MarkLogic Server through the XCC API, see the XCC Developer's Guide
You can make backups of a database, as described in Backing Up a Database, which backs up all of the forests in the database. You can also create backups of individual forests used by a database, as described in Making Backups of a Forest.
There are a number of key differences between database-level and forest-level backups. A database-level backup, by default, backs up all of the forests in the database to the specified directory. Each time a database backup is initiated, a new set of backup data is created in that directory. With a forest-level backup, each forest must be backed up to a separate directory. In addition, each incremental backup of a forest is added onto the previous backup data. A forest backup also has additional logic that checks to see if any of its stands have changed before overwriting the backup of the earlier stand. Only the stands that have changed are overwritten.
Along with full backups, you can use incremental backups and journal archiving to create backups that enable you to recover your database to a specific point in time. For details, see Backing Up and Restoring a Database.
You can restore an entire database from a database backup, as described in Restoring a Database without Journal Archiving. You can restore an individual forest from either a database backup, as described in Restoring a Database without Journal Archiving, or from an individual forest backup, as described in Restoring a Forest.
For details on how to tune your applications for maximum performance, see the Query Performance and Tuning Guide.
For example, the Admin Library Module (
admin.xqy) enables you to write scripts that create or modify databases, forests, App Servers, set up SSL security, and so on. The Security Library Module (
security.xqy) provides a set of functions that enable you to create scripts that set up security entities. The
xdmp built-in functions enable you to do forest and database backup/restore operations, as well as other database and forest management operations.
For a general overview of scripting administrative tasks, see Scripting Administrative Tasks in MarkLogic Server in the Scripting Administrative Tasks Guide. All of the available administrative functions are described in the XQuery and XSLT Reference Guide and MarkLogic REST API Reference.
You can schedule administrative scripts to be invoked at specific intervals or times, as described in Scheduling Tasks.
A single instance of MarkLogic Server running on a single machine is called a host. You can configure multiple hosts into a cluster, as described in the Scalability, Availability, and Failover Guide. Within a cluster, you can create groups of similarly configured hosts, as described in Groups. Different configurations of grouped hosts are useful when different groups of hosts perform different tasks or have different system capabilities.
Should a host go down, its duties can be resumed by another host in the cluster. MarkLogic provides support for failover, which allows the forest to automatically mount to a different host in the event of a forest's primary host going offline. For details on configuring forests for failover, see High Availability of Data Nodes With Failover and Configuring Shared-Disk Failover for a Forest in the Scalability, Availability, and Failover Guide.