Copy to Object Store (v1)

Use the Copy to Object Store (v1) REST API to copy a file or a backup snapshot from the current cloud environment (the source) to the Oracle Object Storage Cloud (the target). You can copy any file or snapshot available in the Oracle Fusion Cloud Enterprise Performance Management. For example, if you export data to a file, the exported file is stored in the Outbox. You can then use this API to copy the file directly to Oracle Object Storage, assuming you have an account.

This topic describes the v1 version of this REST API. You can also use the simplified v2 version of the REST API. The v2 version contains all parameters in the payload and does not require URL encoding while calling the REST APIs. This makes the v2 API easier to use. The v2 version is backwards compatible.

Note:

The Object Storage requires an Other Web Services Provider type. Ensure that you have access to the Web service you are connecting. You must also have URLs for the Web service and an login details if required. For information see, Connecting to External Web Services in Administering Planning.

Required Roles

Service Administrator

REST Resource

POST /interop/rest/v1/services/copytoobjectstore

Table 9-77 Tasks for Copy to Object Store

Task	Request	REST Resource
Trigger `copytoobjectstore`	POST	`/interop/rest/v1/services/copytoobjectstore`
Retrieve `copytoobjectstore` status	GET	`/interop/rest/v1/services/jobs/777`

Request

Supported Media Types: application/x-www-form-urlencoded

Table 9-78 Parameters

Name	Description	Type	Required	Default
`url`	Oracle Object Storage Cloud bucket with an optional object name appended. The URL format without object name: `https://swiftobjectstorage.region_identifier.oraclecloud.com/v1/namespace/bucket_name` The URL format with object name: `https://swiftobjectstorage.region_identifier.oraclecloud.com/v1/namespace/bucket_name/object_name` Components of this URL: region_identifier is an Oracle Cloud Infrastructure hosting region. namespace is the top-level container for all buckets and objects. Each Oracle Cloud Infrastructure tenant is assigned a unique system-generated and immutable Object Storage namespace name at account creation time. Your tenancy's namespace name, for example, axaxnpcrorw5, is effective across all regions. bucket_name is the name of a logical container where you store your data and files. Buckets are organized and maintained under compartments. A system generated bucket name, for example, bucket-20210301-1359 reflects the current year, month, day, and time. object_name, optionally, is name that you want to use for the file on Oracle Object Storage Cloud. If an object name is not specified, the file will be copied with its original name. For more information, see these topics in Oracle Cloud Infrastructure Documentation: Regions and Availability Domains Understanding Object Storage Namespaces Managing Buckets	Form	Yes	None
`username`	The ID of a user who has the required access rights to write to Oracle Object Storage Cloud. For users created in a federated identity provider, specify the fully-qualified name of the user (for example, `exampleIdP/jdoe` or `exampleIdP/john.doe@example.com`, where `exampleIdP` is the name of the federated identity provider). For other users, provide the User ID.	Form	Yes	None
`password`	The Swift password or auth token associated with the user. This password is not the same as the password that you use to sign into the Object Storage Console. Auth token is an Oracle-generated token that you use to authenticate with third-party APIs, for example to authenticate with a Swift client. For instructions to create this token, see To create an auth token in Oracle Cloud Infrastructure Documentation .	Form	Yes	None
`filepath`	Name of the file (with path) to be copied to the Store. If you are copying a snapshot, do not specify the ZIP extension. Examples: Artifact Snapshot, inbox/File.txt	Form	Yes	None

Sample Request Payload

{
  "url": "OBJECT_STORAGE_URL",
  "username": "USER_NAME",
  "password": "PASSWORD",
  "filepath": "<FILEPATH>"
}

Response

Supported Media Types: application/json

Table 9-79 Parameters

Name	Description
`details`	In the case of errors, details are published with the error string
`status`	See Migration Status Codes
`links`	Detailed information about the link
`href`	Links to API call or status API
`action`	The HTTP call type
`rel`	Possible values: `self` or `Job Status`. If the value is set to `Job Status`, you can use the href to get the status
`data`	Parameters as key value pairs passed in the request

Example of Response Body

{
  "details": null,
  "status": -1,
  "items": null,
  "links": [
    {
      "href": "https://<BASE-URL>/interop/rest/v1/services/copytoobjectstore",
      "action": "POST",
      "rel": "self",
      "data": null
    },
    {
      "href": "https://<BASE-URL>/interop/rest/v1/services/jobs/<JOB_ID>",
      "action": "GET",
      "rel": "Job' 'Status",
      "data": null
    }
  ]
}

Sample cURL Command

curl -s -u <USERNAME>:<PASSWORD> -H 'Content-Type: application/x-www-form-urlencoded' --request POST https://<BASE-URL>/interop/rest/v1/services/copytoobjectstore -d 'url=<OBJECT-STORAGE-URL>/<OBJECT-NAME>&username=<OBJECT-STORAGE-USERNAME>&password==<OBJECT-STORAGE-PASSWORD>&filepath=<FILEPATH>’