great place to work

A Guide to Create Seamless and Easy Oracle Integration Cloud Backups

Share

 

When you’re working on a Cloud PaaS solution, you might think that keeping backups of your work is not an arduous task at all. This is somewhat true and the same assumption is applied to when working in Oracle Integration Cloud. It is an Oracle-managed PaaS environment hence, everything is in the safe hands of Oracle. But sometimes having a backup is handy and also, necessary sometimes for your integrations. You might be performing back-to-back updates or fixes on complex integrations and having a well-documented repository of older versions is essential. Or you might be working as a part of the team working on and sharing several OIC instances and integrations. You can create backups manually – click export in the options of the resource ( packages, integrations, libraries, etc.) and add it to your repository or backup system. But you can make it much more convenient for you in the long run if you spend some time in the beginning. It’ll also provide flexibility of scheduling. 

 

This blog is created to share a bash script to help you get some knowledge regarding the backup process of the integration package and then, how to add the backup to your GitHub repository.

Script for Backup

Now, let’s focus on the script to export a package. The steps in this bash script are as follows,

 

  • Gets the commit message from the command line.
  • Switches to the location where the exported file is to be saved.
  • Exports the integration package as a .par file and saves it in the directory.
  • Switches to the root directory of the local git repository.
  • Stages the changes.
  • Commits the changes. If the commit message received from the command line is empty, pick the current date and time as the commit message (Useful for scheduling).
  • Pushes the changes to the branch.

Here is the bash script,

Implementing Use Cases for OIC Backup using REST API’s

 

You are using the REST APIs for Oracle Integration to implement this. The APIs provide a range of options, but the below code focuses on only one endpoint – export a package. But consider this as only a starting point. From this base script, you can customize by incorporating additional end-points and logic to handle specific use cases. Here are some of the useful backup use cases and the endpoints to implement them,

Conclusion

To summarize, having a well-documented bac-kup of your work – even if the work is on a Cloud PaaS solution – has its advantages and importance. By using the REST API for Oracle Integration, you can develop a script to automate the process or run it ad hoc. Here, we used Github to store the backups and bash to script the flow. But you can use other hosting solutions or languages ideal for your use cases. 

 

Feel free to explore.

By,

Dipin Manmadhan

Senior Software Engineer, RapidValue

Please Share Your Thoughts & Comments Below.

How can we help you?