Skip to content

Update - Datastore Configuration

URL:
https://<root>/data/config/update
Methods:
POST
Version Introduced:
10.1.1

Access requirements

Required privileges

The Sever Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.



Note that administrators assigned a custom role must also have the administrative View all content privilege assigned to them to access the API directory as an administrator.

Tokens

This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Server Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.

Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generateToken operation in the Portal Directory API. For security reasons, all POST requests made to the Server Administrator API must include a token in the request body.


Learn how to generate a token

Description

The update 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.

Request parameters

ParameterDetails

datastoreConfig

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

Example
Use dark colors for code blocksCopy
1
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

The following is a sample POST request for the update operation:

Use dark colors for code blocksCopy
1
2
3
4
5
6
POST /<context>/admin/data/config/update HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []

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

JSON Response example

Use dark colors for code blocksCopy
1
{"status": "success"}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.