A

Access Control

Security. Restricting access based on something other than the identity of the user. See permission, amp, authentication, and Access Control List (ACL). See also Authentication and Access Control in Secure MarkLogic Server.

Access Control List (ACL)

Security. A list of permissions attached to an Object. The ACL specifies who or what can access an object, or what operations are allowed on that object. See Access Control.

access token

OAuth. A bearer token used to authorize a specific user. [New in v11.2.0]

ACID (properties)

Database. Atomicity (a set of changes either takes place as a whole or doesn't take place at all), Consistency (system rules are enforced, such as that no two documents should have the same identifier), Isolation (uncompleted transactions are not otherwise visible), and Durability (once a commit is made it will not be lost).

active data

MarkLogic. Active data is data that requires low-latency queries and updates. The “activeness” of a particular document is typically determined by its recency and thus changes over time. See archived data and historical data.

Admin app server

The app server on a particular static host in a group that grants access to port 8001.

admin interface

The Admin Interface (Administration Interface) is graphic user interface for managing MarkLogic Server and is implemented as a web application that runs in your browser.

administration APIs

The MarkLogic Admin APIs provide a flexible toolkit for creating new and managing existing configurations of MarkLogic Server. The Admin APIs take the following forms:

• XQuery Functions

• Server-side JavaScript Functions

• REST Resources

aggregate

Marklogic. XML content that includes recurring element names and which can be split into multiple documents with the recurring element as the document root. For more information, see Splitting Large XML Files Into Multiple Documents in MarkLogic Content Pump (mlcp).

aggregate function

MarkLogic. Used for tasks like computing a sum or count over an element, attribute, or field range index, or many of these range indexes. Aggregate functions are most useful for analytics that produce a small number of results, such as computing a single numeric value across a set of range index values. MarkLogic predefines many aggregate functions, and you can define your own aggregate UDF. See Introduction to Aggregate Functions in Develop Search Applications.

aggregate UDF

MarkLogic. An aggregate User Defined Function (UDF) is a custom function that analyzes values in lexicons and range indexes. An aggregate function is best used for analyses that produce a small number of results, rather than analyses that produce results in proportion to the number of range index values or the number of documents processed. An aggregate UDF is implemented in C++ and deployed as a native plugin. For more information, see Aggregate User-Defined Functions in Develop Server-Side Applications.

alerts

MarkLogic. An alerting application is used to notify users when new content is available that matches a predefined (and usually stored) query. An alert is based on a reverse query. Alerts are used with Query-Based Flexible Replication (QBFR). See Configuring Alerting With Flexible Replication in Use Flexible Replication.

Amazon Machine Image (AMI)

Cloud. An encrypted machine image that contains all information necessary to boot instances of software. Instances of MarkLogic Server are created from the stock Amazon Linux AMI and have been pre-installed with MarkLogic and the necessary dependencies. A virtual appliance for use with Amazon’s Elastic Compute Cloud (EC2).

Amazon Resource Name (ARN)

Cloud. ARNs are used to identify AWS resources across all of AWS. For details, see Amazon Resource Names (ARN).

Amazon Web Services (AWS)

Cloud. The Amazon Cloud Computing service. For details, see Cloud Computing Services.

amp

MarkLogic. An amp provides a user with the additional authorization to execute a specific function by temporarily giving the user additional roles. For details on amps, see Temporarily Increasing Privileges with Amps in Secure MarkLogic Server.

APIs and communications protocols

MarkLogic supports the following application programming languages:

• XQuery (native, server-side support)

• JavaScript (native, server-side support)

• XSLT (native, server-side support)

• Java

• Node.js

• C#

• SQL (native, server-side support)

• SPARQL (native, server-side support)

• REST interfaces

  In addition, XQuery, JavaScript, XSLT, SQL, and SPARQL are native langauges.

App Server

MarkLogic. A MarkLogic server, that can be one of the specific types of server; HTTP Server, XDBC Server, ODBC Server, or WebDAV Server. The type of server is defined at the group level when you create a new server.

archive

MarkLogic. A compressed MarkLogic Server database archive created using the mlcp export command. You can use an archive to restore or copy database content and metadata with the mlcp import command. For details, see Exporting to an Archive in MarkLogic Content Pump (mlcp).

archived data

MarkLogic. Data that has aged beyond its useful life in the online storage tiers and is typically taken offline. See active data.

asserted triples

Semantics. In a system that does inference, asserted triples are those triples that are in the database before inferencing, as opposed to inferred triples which are the result of the inferencing process. See inference, inferred triples, ontology triples, and triple.

asynchronous

General. Asynchronous I/O, or non-blocking I/O is a form of input/output processing that permits other processing to continue before the transmission has finished. See synchronous.

Asynchronous Replication

Flexible Replication. A configuration in which the Master does not wait for confirmation that the update has been received by the Replica before committing the transaction and proceeding with additional transactions. Flexible Replication and database replication are asynchronous.

Attribute-Based Control (ABAC)

Security. A form of security based on attributes assigned to a role or object. ABAC is a logical access control model that controls access to objects by evaluating rules against the attributes of the entities (subject and object) actions and the environment associated with a request. See MarkLogic Security Model in Secure MarkLogic Server.

authentication

Security. The process of verifying user credentials for a named user, usually based on a username and password. Authentication generally verifies user credentials and associates a session with the authenticated user. It does not grant any access or authority to perform any actions on the system. Authentication can be done internally inside MarkLogic Server, or externally by means of Kerberos.

authorization

Security. The process of allowing a user to perform some action, such as create, read, update, or delete a document or execute a program, based on the user's identity. Authorization defines what an authenticated user is allowed to do on the server. When an App Server is configured for external authentication, authorization can be done either by MarkLogic Server or by LDAP.

authorization code

OAuth. A token used in the OAuth 2.0 authorization code flow to be exchanged for an access token. [New in v11.2.0]

authorization server

OAuth. In the OAuth 2.0 protocol, the Identity Provider (IDP) server responsible for authenticating and authorizing users.

authorization server URI

OAuth. OAuth server endpoint for obtaining authorization codes. [New in v11.2.0]

auxiliary databases

MarkLogic. The default databases that are created during the installation process: Security, Modules, Documents, Schemas, Triggers, and Last-Login.

availability of a partition or forest

MarkLogic. Refers to the online or offline status of a partition or forest.