Configuration considerations and limitations

See also Default configurations. The default configurations can be modified by the Progress Data Cloud Operations Team.

Resource allocations

When configuring forests, consider the amount of storage, CPU, and memory capacity. Generally, this information is communicated during the provisioning process. It is also available on the service card of the appropriate MarkLogic Server Service instance.

MarkLogic Server Service provides and monitors the infrastructure, but healthy operation of everything inside your cluster and how the infrastructure is affected by your application(s) is your responsibility. Each Progress Data Cloud subscription comes with an allotment of professional services hours for working with you to help ensure infrastructure, cluster, and application health over time.

See Forest Sizes Per Data Node Host (MarkLogic Guide Scalability, Availability, and Failover Guide).

Clusters

Database replication requires clusters to be coupled. Contact the Progress Data Cloud Operations Team if this is required.

Additionally, do not enable log encryption. This prevents the Progress Data Cloud Operations Team from monitoring logs and delays troubleshooting.

Groups

If you add a new group to your MarkLogic Server Service cluster, it may be lost on service restart. If you wish to add a new group, contact the Progress Data Cloud Operations Team.

Additionally, Temporary Directory must be left empty.

App servers

To allow Progress Data Cloud users access to your custom app servers, when configuring the app server within MarkLogic Server Service, set these fields:

• Authentication must be saml.

• External Security needs to include ML_CLOUD_TOKEN.

• SSL Certificate Template must be none:

  Progress Data Cloud uses service mesh technology that automatically encrypts traffic to and from all Progress Data Cloud components. This technology is more secure than the standard TLS provided by https.

• Modules must not be filesystem.

Once the app server is created within MarkLogic Server Service, see Expose an app server to make the new app server reachable from outside the Progress Data Cloud cluster.

Forests

Leave the following directories blank or with their default settings:

• Data Directory
• Large Data Directory
• Fast Data Directory

Database and forest backup locations

The Progress Data Cloud Operations Team provides details regarding what Backup Directory should be used for MarkLogic Server Services. You will need to specify a Backup Directory beginning with "azure://".

XQuery commands like these can be used in MarkLogic Server Service Query Console to manage your own backup storage area:

• xdmp:filesystem-directory-create: Creates the directory specified by pathname.

• xdmp:filesystem-directory-delete: Deletes the directory specified by pathname.

• xdmp:filesystem-directory: Performs a directory listing of the given file pathname.

Internal users are NOT Progress Data Cloud users

All transactions must be authenticated by the Progress Data Cloud Interface. Service-level transactions are not exceptions. Internal users of a MarkLogic Server Service instance will never authenticate at the Progress Data Cloud Interface level.

These internal users may be used only as part of MarkLogic Server Service features that require a configured user, for example, scheduled tasks.

Internal roles

Roles can be added to the MarkLogic Server Service configuration. However, roles need to be exposed to the Progress Data Cloud application in order to be assigned to Progress Data Cloud users.

Internal roles may also be used as part of MarkLogic Server Service features that require a configured role, for example, amps, element-level security, and so on.

See Expose an internal role for further steps required to make an internal role assignable to Progress Data Cloud users.