Migrate Integration and Process Design-Time Metadata into Oracle Integration
You can export an archive of design-time metadata from an Oracle
Integration Classic instance and import that archive into an Oracle Integration instance. All design-time metadata for Integrations and Processes gets migrated during
import, including security and credential settings, IDCS role mappings, connection endpoints
and password, and other dependencies. Integration and process activations occur
automatically upon import if ImportActivateMode
is set to
ImportActivate
.
Import the Design-Time Metadata into Oracle Integration
After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.
{
"archiveFile": "archive_file_name",
"importActivateMode": "ImportActivate",
// options are "ImportOnly" || "ActivateOnly" || "ImportActivate"
"storageInfo": { // storageUrl points to the storage container
"storageUrl":"https://swiftobjectstorage.us-region-1.oraclecloud.com/v1/paasdevoic/
cloneRepo",
"storageUser":"myemail@company.com",
"storagePassword":"generated_token"
}
}
-
To import the archive, go to the Oracle Integration instance and invoke the REST API. This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.
Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us-region-1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"myemail@company.com", "storagePassword":"generated_token" } }
For example, use apostman
orcurl
(as shown below) command to import the archive of design time objects into Oracle Integration. You can setimportActivateMode
to the following values:-
ImportOnly
: Imports, but does not activate, integrations and process applications. -
ActivateOnly
: Activates previously imported integrations and process applications. This enables you to update connection parameters before activating integrations. -
ImportActivate
: Imports and activates integrations and process applications.
curl -k -v -H "Content-Type: application/json" -X POST -d '{"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us-region-1.oraclecloud.com/v1/paasdevoic/cloneRepo","storageUser" :"myemail@company.com", "storagePassword":"generated_token"}}' -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive
Possible sample output from this command is as follows:{ "jobId":"554", "status":"NOT_STARTED" }
-
Check the Design-Time Metadata Import Status
Verify the design-time metadata import status after completing the import task.
-
Check the status of the import operation using a
postman
orcurl
(as shown below) command:curl -k -v -X GET -u admin:password https://host/ic/api/common/v1/ importServiceInstanceArchive/554
Possible sample output from this command is as follows. Other potential output includesRUNNING
,COMPLETED
, andFAILED
.{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] }
-
Log in to your Oracle Integration instance.
-
Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible. For example, for Integrations, look for integrations, connections, lookups, and more. For Processes, look for process applications and decision models.