Expose an app server
- Last Updated: May 12, 2026
- 2 minute read
- Progress Data Cloud
- Documentation
Note:
For users with the MarkLogic Administrator or MarkLogic Developer role.
App servers can be configured using the MarkLogic Server Service Admin Interface or by using gradle tasks. First review the configuration requirements regarding app servers.
After configuring an app server, expose the app server to make it accessible from the Progress Data Cloud Interface. Expose an app server through the Configure HTTP Endpoints or Configure TCP Endpoints option from the MarkLogic Server Service service card
menu.
To expose an app server:
-
On the Services page, find the card for the MarkLogic Server Service instance in which you configured your app server.
-
Click
on the service card. -
Click the appropriate configuration option to access the Configure Endpoints sidebar:
- Configure HTTP/XDBC/WebDAV Endpoints exposes an HTTP, XDBC, or WebDav app server.
- Configure ODBC Endpoints exposes an ODBC app server.
-
Click + at the bottom of the sidebar to display the endpoint configuration form.
-
Configure the integration endpoint as needed.
-
Click Add to finalize your configuration.
-
Click Save Changes to finalize the list of exposed endpoints.
You have successfully exposed your app server.
Connecting to an ODBC endpoint
Progress Data Cloud uses separate traffic routes for HTTP and non-HTTP (TCP) traffic:
- HTTP traffic (REST API, Admin UI, Query Console, XDBC, WebDAV) uses the standard hostname:
<tenantDnsName>.data.progress.cloud - TCP traffic (ODBC only) uses a dedicated hostname:
<tenantDnsName>-tcp.data.progress.cloud
For example, if your tenancy DNS name is myorg, the ODBC connection hostname is myorg-tcp.data.progress.cloud.