MarkLogic

Access MarkLogic

To access MarkLogic:

On the Your Apps page, on the MarkLogic card, click the Admin UI, Query Console or Monitoring button to access the related service.

API endpoints

By default, each MarkLogic Server Service has these three links or endpoints, which users assigned the specified roles can access. These endpoints are described in this section.

Admin UI

Roles: MarkLogic Administrator

The MarkLogic Server Service Admin Interface is a graphical user interface where users can manage roles, app servers, external security, and use other functionality.

Query Console

Roles: MarkLogic Administrator and MarkLogic Security Administrator

The Query Console is an interactive web-based query development tool for writing and executing ad-hoc queries in popular languages.

Monitoring

Roles: MarkLogic Administrator, MarkLogic Security Administrator, MarkLogic Developer, and MarkLogic Monitor

The MarkLogic Server Service Monitoring Dashboard is a graphical user interface displaying information about query execution, rates and loads, disk space, and history.

MarkLogic Server Service app servers may be exposed through endpoints as needed. Access to these endpoints depends on the configured security settings at the MarkLogic Server Service level.

ml-gradle

To deploy your configured ml-gradle projects, see ml-gradle integration.

Expose additional app servers

To expose additional app servers, see Expose an app server.

ODBC access

To connect to your MarkLogic Server Service databases using ODBC, see Configure ODBC access.

Roles

MarkLogic Server Service has its own concept of users and roles. These service-level users and roles may be used within the MarkLogic Server Service cluster as part of features like scheduled tasks, content processing framework, and others. However, these credentials will not work through the Progress Data Cloud Interface.

To expose MarkLogic Server Service roles, see Expose an internal role.

Backups

Your MarkLogic Server Service subscription includes dedicated backup space for storing your data backups. It is your responsibility as a tenant to use this space to regularly back up your data at a cadence that meets your organization's requirements.

Scheduling backups

When configuring scheduled backups, use the azure:// directory format for the backup directory path:

azure://<mycontainer>/<mydirectory>/

Scheduling methods

You can schedule backups using one of these methods:

API (recommended)

Use the last example on the API page to schedule backups. When using the API, you can target containers that do not yet exist — they are created automatically.

Admin UI

See Scheduling a database backup. When scheduling backups through the Admin UI, you can only target containers that already exist in the storage account.

For more information on configuring and managing MarkLogic Server Service backups, see the MarkLogic Server Service documentation.

Documentation

The MarkLogic Server Service documentation further describes concepts, features, tools, and best practices regarding MarkLogic Server Service.

Service

Your MarkLogic Server Service is configured into an appropriately sized cluster determined during the presales process and is monitored by the Progress Data Cloud Operations Team. Your MarkLogic Server Service subscription also comes with an allotment of professional service hours to help you to ensure infrastructure, cluster, and application health over time. It is your responsibility to make wise use of these hours to ensure that this cluster and the applications installed onto it continue to operate in an expected manner.