Import Server Configuration

Import Server Configuration

Imports/exports the server configuration. The exported file is available as an attachment with MIME type application/zip. To perform an export request, an empty file must be attached to the request. Otherwise, the server tries to import a configuration.

The format of the exported or imported file is same as that of files exported or imported by using the Orchestrator configuration interface. The configuration binary content must be available as multi-part content (see RFC-2387 for details). Details of working with multi-part resources depend on the used client HTTP/REST library. For example, in Spring it will look like:

Sample client code that imports a server configuration:
-----------------------
MultiValueMap parts = new LinkedMultiValueMap ();
parts.add("file", new FileSystemResource("/path/to/vco_config_file.zip"))
;parts.add("password", "secret")
;parts.add("importIdentity", Boolean.FALSE);

getRestTemplate().postForEntity(" https://localhost:8281/vco/api/server-configuration", parts, Void.class);
-----------------------

Request
URI
POST
https://{api_host}/vco/api/server-configuration
COPY
Query Parameters
string
password
Optional

password

boolean
importIdentity
Optional

importIdentity

boolean
isUpgradeBackup
Optional

isUpgradeBackup


Responses
200

The request is successful.

Operation doesn't return any data structure

400

Request is not valid (validation error).

Operation doesn't return any data structure

401

User is not authenticated.

Operation doesn't return any data structure

403

User is not authorized.

Operation doesn't return any data structure