Import the MFT metadata into the MFT MDS store

put

/mftapp/rest/v1/mftapp/rest/v1/applicationMetadata

Supports importing metadata along with optional config plan file which allows to override the attributes in the metadata files.

Request

Supported Media Types
  • multipart/form-data
Query Parameters
previewModeFlag
Type: boolean
Flag to view the preview the import without actually importing metadata.
Body Parameter
A body of type:
Root Schema : /paths/~1mftapp~1rest~1v1~1applicationMetadata/put/parameters/1/schema
  • multipart/form-data

Response

Supported Media Types
  • application/json
200 Response
Body
Root Schema : /paths/~1mftapp~1rest~1v1~1applicationMetadata/put/responses/200/schema
Nested Schema : /paths/~1mftapp~1rest~1v1~1applicationMetadata/put/responses/200/schema/properties/configPlanOverrideResultSummmary
Nested Schema : /paths/~1mftapp~1rest~1v1~1applicationMetadata/put/responses/200/schema/properties/failedTransfers
Type: array
Nested Schema : /paths/~1mftapp~1rest~1v1~1applicationMetadata/put/responses/200/schema/properties/skippedTransfers
Type: array
Nested Schema : /paths/~1mftapp~1rest~1v1~1applicationMetadata/put/responses/200/schema/properties/configPlanOverrideResultSummmary/items
Type: object
500 Response
Body
Root Schema : Error information.
Type: object
Title: Error information.
Example application/json

{
    "errorCode":"MFT-2351",
    "errorKey":"MFT_IMPORT_ERROR",
    "errorMessage":"Error occurred while importing the metadata."
}