4-Extending a MDC cluster with a new clone DC
post
                    /oam/services/rest/mdc/master/clone
To be executed on the master data center. Creates the new clone DCs MDC configurations in the master and generates the required cloning artifacts that will need to be applied on the new clone
                Request
Supported Media Types
                - application/json
These input parameters direct the MDC topology, the Data Center that needs to be added and configured as the new MDC clone, and the various credentials/certificates needed for the coupling the data centers
                
                
                
                Root Schema : configureMasterWithNewClone
    
      Type: 
      
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        Show Source
        object- 
            accessClientPassword: 
            string
            Password to be used for the MDC NAP agent of new Clone
- 
            agentKeyPassword: 
            string
            Agent Key Password used to register new clone partner in CERT mode. To be used when the Managed Servers are in CERT Mode
- 
            artifactPassword: 
            string
            Password used for protecting the cloning artifacts
- 
            artifactsZipLocation(optional): 
            string
            Location where cloning artifacts has to be stored. OPTIONAL - To be specified if cloning artifacts has to be stored in any location other than /tmp
- 
            certModeKeystorePassword: 
            string
            KeyStore Password used to protect clientTrustStore.jks and clientKeyStore.jks. To be used when the Managed Servers are in CERT Mode
- 
            cloneAdminUserNamePassword(optional): 
            string
            UserName:Password of Clone DC Administrator. OPTIONAL - To be specified when the Master and Clone Admin Users/Password are different
- 
            cloneMDCAgentID: 
            string
            Mdc Nap Agent Name for New Clone to be added to the setup
- 
            cloneServerPolicyManagerURL: 
            string
            URL of the clone policy manager endpoint or the URL of the reverse proxy front-ending the clone policy manager.
- 
            cloneServerURL: 
            string
            URL of the new clone admin server or the URL of the reverse proxy front-ending the new clone admin server
- 
            keyStorePath(optional): 
            string
            In case of SIMPLE mode, Path to oamclient-keystore.jks file. OPTIONAL - To be speciifed when the oamclient-keystore.jks file is present in any folder other than %DOMAIN_HOME%/output/webgate-ssl-SHA-256. In case of CERT mode, Path to clientKeyStore.jks file. OPTIONAL - To be speciifed when the clientKeyStore.jks file is present in any folder other than %DOMAIN_HOME%/config/fmwconfig/oam-mdc-cert-artifacts
- 
            masterServerPolicyManagerURL: 
            string
            URL of the master policy manager endpoint or the URL of the reverse proxy front-ending the master policy manager.
- 
            trustStorePath(optional): 
            string
            In case of SIMPLE mode, Path to oamclient-truststore.jks file. OPTIONAL - To be speciifed when the oamclient-truststore.jks file is present in any folder other than %DOMAIN_HOME%/output/webgate-ssl-SHA-256. In case of CERT mode, Path to clientTrustStore.jks file. OPTIONAL - To be speciifed when the clientTrustStore.jks file is present in any folder other than %DOMAIN_HOME%/config/fmwconfig/oam-mdc-cert-artifacts
Response
Supported Media Types
                - application/json
200 Response
The required MDC configurations were setup on the master DC, and the required clong artifatcs were generated successfully
                
                
                    400 Response
Error
                
                
                    401 Response
Error
                
                
                    500 Response
Error
                
                
                    504 Response
Error