Process Data Mapping
Submits a request to initiate a new Data Mapping operation.
Request takes no content, and on success 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}/{dataFileId}
|
| Parameters: |
Path:
- configId – the Managed File ID (or Name) of the Data Mapping configuration in File Store
- dataFileId – the Managed File ID (or Name) of the data file in File Store
Query:
- validate – Only validate the Data Mapping operation to check for mapping errors (Default Value: false)
|
| Request: |
| Add. Headers: |
auth_token – Authorization Token (if server security settings enabled)
|
| Content: |
– |
| Content Type: |
– |
|
| 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
|
|
| Response (Validate): |
| 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
- 401 Unauthorized – Server authentication required
- 403 Forbidden – Server authentication has failed or expired
- 500 Internal Server Error – Data file or Data Mapping Configuration not found in File Store
|
|