Process Data Mapping (JSON)

Submits a request to initiate a new Data Mapping operation.

As content the request takes one of either:

  • a JSON Identifier of the data file’s Managed File ID, or
  • a JSON Identifier (Named) of the data file’s Managed File Name

On success, it returns a response containing additional headers that specify the ID of the new operation as well as link URLs that can be used to retrieve further information/cancel the operation.

Type: POST
URI: /rest/serverengine/workflow/datamining/{configId}
Parameters:

Path:

  • configId – the Managed File ID (or Name) of the Data Mapping configuration in File Store
Request:
Add. Headers: auth_token – Authorization Token (if server security settings enabled)
Content: JSON Identifier specifying Managed File ID or JSON Identifier (Named) specifying Managed File Name in File Store
Content Type: application/json
Response:
Add. Headers:
  • operationId – Operation ID of new Data Mapping operation
  • Link – Contains multiple link URLs that can be used to retrieve further information/cancel the operation.
Content: -
Content Type: -
Status:
  • 202 Accepted – Creation of new operation successful
  • 400 Bad Request – Data file or Data Mapping Configuration not found in File Store
  • 401 Unauthorized – Server authentication required
  • 403 Forbidden – Server authentication has failed or expired
  • 500 Internal Server Error – JSON Identifier bad or missing