2-Configure the Clone Data Center for MDC

post

/oam/services/rest/mdc/clone

To be executed only on the clone data center. It contacts the master DC to download the generated cloning artifatcs and then applies the configurations on the clone, thereby making this DC as a MDC clone

Request

Supported Media Types
Body ()
These input parameters enable the clone DC to reach out to the master to download the cloning artifacts
Root Schema : configureCloneParameters
Type: object
Show Source
  • Password used for protecting the cloning artifacts. This should be the same password that was passed during setup of master
  • Location where backup artifacts has to be stored. OPTIONAL - To be specified if backup artifacts has to be stored in any location other than /tmp
  • true|false. OPTIONAL - To OverWrite the Existing MDC Configuration or to recover from Inconsistent State
  • UserName:Password of Master DC Administrator. OPTIONAL - To be specified when the Master and Clone Admin Users/Password are different
  • Location where cloning artifacts are present in Master DC. OPTIONAL - To be specified when artifactsZipLocation was used in input while configuring Master Data Center
  • URL of the master admin server or the URL of the reverse proxy front-ending the master admin server

Response

Supported Media Types

200 Response

The cloning articacts were downloaded and applied on the clone successfully
Body ()
Root Schema : responseConfigureClone
Type: object
Show Source
Nested Schema : responseDetails
Type: object
Show Source

400 Response

Error
Body ()
Root Schema : errorresponse
Type: object
Show Source

401 Response

Error
Body ()
Root Schema : errorresponse
Type: object
Show Source

500 Response

Error
Body ()
Root Schema : errorresponse
Type: object
Show Source

504 Response

Error
Body ()
Root Schema : errorresponse
Type: object
Show Source