1. REST API for Oracle Enterprise Communications Broker, Release 4.2.0
  2. Tasks
  3. configuration management

Back up or activate a configuration

post

/rest/{version}/configuration/management

Executes configuration management action to either back up a configuration to the specified filename in the /code/bkups directory, or to activate the saved configuration. The client making the request must already possess the configuration lock or the request fail. This is an asynchronous request, that can take long enough the client must poll the system for the final result. If the request is received successfully, the immediate response to the client (202) simply indicates that the request was received and is being processed. The links section of the response includes the REST resource the client should use to poll for the final result.

Request

Path Parameters
Query Parameters
  • Specifies which action to take with the configuration. Action can be to back up a configuration to a file from a particular configuration source, or activate the saved configuration.
    Available values: backup, activate
  • Only valid when action is "backup". Specifies the source of the configuration to be backed up. When the action is "backup", both the "backupSource" parameter and "filename" parameter are required. The backupSource will specify which configuration is written to the backup file.
    Available values: running, saved, editing
  • Only valid when action is "backup". Specifies the file name of the backup file. When the action is "backup", both the "backupSource" parameter and "filename" parameter are required. The filename parameter must be included and specify a valid backup filename that is not already present in the file system in the /code/bkups directory. Specifying an already existing filename will result in a failure.
Header Parameters
  • The value in the Authorization header must be the string "Bearer {access token}", where {access token} is a valid, unexpired token received in response to a prior /rest/{version}/auth/token request.
Back to Top

Response

202 Response

The configuration management request was received successfully and is being processed.

400 Response

The request is malformed in some way or is missing required information and therefore cannot be processed.

401 Response

Unauthorized - Request lacks valid authentication credentials.

403 Response

This request requires the client credentials to have administrator privileges.

404 Response

Resource not found

423 Response

The request requires the configuration lock and failed because the client does not currently own the lock. If another client or user currently owns the configuration lock, the error message is "Resource locked by another user". If no client or user owns the configuration lock, the error message is "User does not have the lock".
Back to Top

Examples

Example of Accessing the API with cURL

The following example shows how to back up or activate a configuration by submitting a POST request on the REST resource using cURL. For more information about cURL, see Use cURL. 

curl -X POST \
    --header "Accept: application/xml" \
    --header "Authorization: Bearer $TOKEN" \
    "https://${HOSTNAME}/rest/v1.1/configuration/management?action=backup&backupSource=running&filename=backupRunningConfig.gz"

Example of Accessing the API with Python

The following example shows how to back up or activate a configuration by submitting a POST request on the REST resource using Python. This example assumes you have a valid token stored in the token variable. For an example of authenticating with Python, see Authenticate. 

import requests
headers = { "Accept":"application/xml", "Authorization":"Bearer " + token }
url  = "https://" + hostname + "/rest/v1.1/configuration/management?action=backup&backupSource=running&filename=backupRunningConfig.gz"
resp = requests.post(url, headers=headers)

Example of the Response Body

The following example shows the contents of the response body in XML format.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response>
  <data/>
  <messages/>
  <links>
    <link>https://${HOSTNAME}/rest/v1.1/admin/asyncstatus</link>
  </links>
</response>

After receiving that response, check the status of the asynchronus action by making a GET request to the /rest/v1.1/admin/asyncstatus endpoint.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response>
  <data>
    <operationState>
      <operation>backup</operation>
      <status>success</status>
    </operationState>
  </data>
  <messages/>
  <links/>
</response>
Back to Top