To deploy Data Service from the Server, go to Data Services tab, click Publish Data Service job and choose a sandbox and .rjob file.

Figure 44.16. Publishing Data Service job

You can choose between Data Service with or without required authentication. In the latter case, the Data Service will run under the specified account.

Figure 44.17. Publishing Data Service job that does not require authentication

You can deploy Data Service directly from a sandbox. To do so, you need the read access to the sandbox and List Data Services and Manage Data Services privileges.

In the Sandboxes section of the Server GUI, select a data service to be published/unpublished. In the top right corner of the overview, there are options for publishing or unpublishing the data service, as well as editing, showing data service in Execution History, downloading/downloading as ZIP and deleting the data service.

CloverDX Server contains a built-in set of Data Service examples. These examples are not deployed by default.

The Data Service examples can be deployed directly from the Data Services tab. If you do not have any Data Service deployed, click the Publish Data service Examples link.

Figure 44.18. Publishing Data Service examples

If there is an existing Data Service, the button to publish examples is in the menu accessible under the three-dot-button.

Figure 44.19. Publishing Data Service examples - II

See Built-in Data Service Examples.

By default, the Data Service requires a client to send the credentials. To create the Data Service that does not require authentication, switch to the Configuration tab in the Data Service Detail pane and change Authentication method to Do not require authentication. The Data service runs with privileges of an existing user; therefore, you should set the Run as field to the suitable user. This user should have permissions necessary to run the Data Service.

Figure 44.20. Configuring Anonymous Data Service

In the list of Data Services, the Data Service that does not require credentials is indicated by unlocked padlock icon.

Figure 44.21. Data Service without authentication

By default, the Data Service runs on HTTP and you can configure it to run on HTTPS.

To run Data Service on HTTPS, create a new HTTPS Connector.

Figure 44.22. Creating a new Data Service Connector

Enter a name, port, keystore path, and keystore and key passwords.

Figure 44.23. Creating a new Data Service Connector II

In Data Services → Endpoints, select the Data Service to be running on HTTPS and switch to the Configuration tab.

Select the HTTPS connector from the combo box and click the Save & Apply button. Now, the Data Service runs on HTTPS.

Figure 44.24. Using the HTTPS Connector in Data Service endpoint

You can have more independent HTTPS contexts running on one Server. There can be multiple Data Services running on the same HTTPS context.

This case extends the case of Running Data Service on HTTPS. Different Cluster nodes have different domain names, but the Java KeyStore has to have one certificate. There are two way to solve the problem with certificates.

To see the activity of Data Service, use the list of Data Services. There you can see the main overview of data services.

The state of a particular Data Service is on the State and History tab.

To test the Data Service, select the Data Service in the list, switch to the Data App tab and click the Run App button. See Data App usage for more information.

To improve performance, do not save job execution records in Execution History. To do so, do not tick Save job execution records in Execution History on Configuration tab.

You can export the Data Service configuration from Data Services → Endpoints tab. Click the three-dot-button and select Export Data Services Configuration from context menu.

Figure 44.25. Data Services - Export

The Data Services configuration will be exported.

You can also export Data Service configuration in Configuration → Export See Server Configuration Export.

You can import the Data Service configuration from Data Services → Endpoints. Click the three-dot-button and select Import Data Services Configuration from the context menu.

Figure 44.26. Data Services - Import

You can also import the Data Service configuration directly in Configuration → Import See Server Configuration Import.

Data Service might prematurely switch to a failing state if the failure indication is set up to switch to a failing state after a given percentage of executions fails in a given time window. E.g. First execution fails.

To avoid this, you can set the minimum number of events necessary to be taken into account when calculating the change of Data Service state. It can be set with the trigger.failure.ratio.min.record.count configuration property. The default value is 3 executions.

It can be set in Configuration → Setup → Configuration File. Add a line containing

trigger.failure.ratio.min.record.count=3

to the configuration file.

You can set it to any reasonable positive integer. This configuration is valid for all Data Services available on the Server.

See also Chapter 17, List of Configuration Properties.

If you have multiple Data Services available, you can search for a specific Data Service:

If you know the endpoint name, you can look it up. Enter the text into the Search endpoints field and click the Refresh button. The Data Services will be filtered.

The entered text will be searched in the title of the Data Service, in the name of the request method, in the name of .rjob file and in the path that the Data Service uses.

If you would like to see invalid endpoints only, click the failing and invalid only icon. The both filters can be combined.

To switch off the filters, click the Show All button.

If the Data Service endpoint is in the failing state and the problem has been fixed, you can reset the endpoint state manually.

To reset the state, open the details of the endpoint, switch to the Alerts and Notification tab and click the Apply and Reset State button.

If the endpoint has an email address set, a notification email will be sent to this address.

CORS (Cross-Origin Resource Sharing) is a mechanism that allows browsers to give a web application running at one origin, access to resources from another origin.

In order to grant an application access to Data Service endpoints, CORS response headers have to be properly configured using dataservice.access.control.* configuration properties. See the list of Data Service configuration properties.

For example, using the following configuration, any web application will be allowed to access Data Service endpoints using GET requests:

dataservice.access.control.allow.origin=*
dataservice.access.control.allow.methods=GET