Skip To Content

Update Datastore Configuration

Description

This operation allows you to update the data store configuration. You can use this to allow or block the automatic copying of data to the server at publish time. This operation overwrites all existing configuraitons.

Note:

If you specify the property as true, users will not be able to publish geoprocessing services and geocode services from composite locators. These service types require data to be copied to the server. As a workaround, you can temporarily set the property to false, publish the service, and then set the property back to true.

Request parameters

ParameterDetails
datastoreConfig

The JSON object containing the data configuration. For more information, see the configuration properties table below.

Example

datastoreConfig={"blockDataCopy": true}
f

The response format. The default response format is html.

Values: html | json| pjson

Configuration properties

ParameterDetails
blockDataCopy

A Boolean property. When this property is set to false, or not set at all, copying data to the site when publishing services from a client application is allowed. This is the default behavior. When this property is true, the client application is not allowed to copy data to the site when publishing. Rather, the publisher is required to register data items through which the service being published can reference data.

When this property is set to true, users will not be able to publish geoprocessing and geocoding services from composite locators, as these services require data to be copied to the server. As a workaround, you can temporarily set the blockDataCopy to false, publish the service, and then set the property back to true once the service has been published.

Values: true | false

Example usage

Below is a sample POST request for update:


POST /webadaptor/admin/data/config/update HTTP/1.1
Host: machine.domain.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []

datastoreConfig={"blockDataCopy": true}&f=json

JSON Response example

{"status": "success"}