Pre-Configuration Steps

Configure Properties

Create application properties on the source and the target environments to send a notification to the orchestrator when import or export completes.

Export Notification Endpoint

Sends a notification to the orchestrator endpoint once the creation and build process completes in the source environment[1].

Request
POST http://<host>:<port>/<context-root>/generic/properties

{
  "name": "ohi.datasetoperations.notification.endpoint.export",
  "value": "http://<host>:<port>/<context-root>/<orchestrator_endpoint>"
}

Content-Type: application/json
Accept: */*
Response

Returns HTTP status codes as mentioned in the Building a Migration Set page. A 201 Created response shows a successful operation.

Import Notification Endpoint

Sends a notification to the orchestrator endpoint once the import process completes[2].

Request
POST http://<host>:<port>/<context-root>/generic/properties

{
  "name": "ohi.datasetoperations.notification.endpoint.import",
  "value": "http://<host>:<port>/<context-root>/<orchestrator_endpoint>"
}

Content-Type: application/json
Accept: */*
Response

Returns HTTP status codes as mentioned in the Building a Migration Set page. A 201 Created response shows a successful operation.

Configure Credentials

Export Notification Credentials

Create credentials for the export property to send notifications to the source environment[1].

Request
http://<host>:<port>/<context-root>/credentials/credential/DataExchangeExportNotificationClient

{
    "username": "<orchestrator_username>",
    "password": "<orchestrator_password>"
}

Content-Type: application/json
Accept: */*
Response

Returns HTTP status codes as mentioned in the Building a Migration Set page. A 204 No Content response shows a successful operation.

Import Notification Credentials

Create credentials for the import property to send notifications to the target environment[2].

Request
http://<host>:<port>/<context-root>/credentials/credential/DataExchangeExportNotificationClient

{
    "username": "<orchestrator_username>",
    "password": "<orchestrator_password>"
}

Content-Type: application/json
Accept: */*
Response

Returns HTTP status codes as mentioned in the Building a Migration Set page. A 204 No Content response shows a successful operation.


1. Export property and credentials must be configured on the source environment
2. Import property and credentials must be configured on the target environment