Relational Data Store Type | ArcGIS REST APIs

URL:: https://<root>/data/relationalDatastoreTypes/<relationalDatastoreTypeID>
Methods:: GET
Operations:: Edit Relational Data Store Type, Unregister Relational Data Store Type
Version Introduced:: 10.5

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.

Register data stores Feature layer Update Delete Security and infrastructure Servers Organization webhooks Geoprocessing Publisher role

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. Additonally, any custom roles that include a webhook-related privilege must also include the general Publish server-based layers content privilege.

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 resource for an individual relational data store type lists its properties. The properties returned are those that client applications must provide when creating a Relational Database Connection portal item.

Request parameters

Parameter	Details
`f`	The response format. The default response format is `html`. Values: `html` \| `json` \| `pjson`

Example usage

The following is a sample request URL used to access an individual relational data store type resource:

Use dark colors for code blocksCopy
https://organization.example.com/<context>/admin/data/relationalDatastoreTypes/esri.teradata?f=pjson

JSON Response syntax

Use dark colors for code blocksCopy
{
  "name": "",  //user-friendly name
  "id": "",  //identifier
  "userDefinedProperties": [],  //properties specified when creating a relational catalog service
  "dependentServices": []  //comma-separated array of existing relational catalog services using this type
}

JSON Response example

Use dark colors for code blocksCopy
{
  "name": "Teradata",
  "id": "esri.teradata",
  "userDefinedProperties": [
    {
      "name": "username",
      "alias": "User Name",
      "defaultValue": "",
      "type": "string",
      "required": true
    },
    {
      "name": "password",
      "alias": "Password",
      "defaultValue": "",
      "type": "string",
      "required": true
    },
    {
      "name": "serverName",
      "alias": "Server Name",
      "defaultValue": "",
      "type": "string",
      "required": true
    },
    {
      "name": "DATABASE",
      "alias": "Database Name",
      "defaultValue": "",
      "type": "string",
      "required": true
    },
    {
      "name": "DBS_PORT",
      "alias": "Port Number",
      "defaultValue": "",
      "type": "int",
      "required": false
    }
  ],
  "dependentServices": [
    "QA1.RelationalCatalogServer"
  ]
}