ICS Best Practices : Before going live and post go-live by Ashish Singh
July 23, 2018 Leave a comment
Integration Cloud Service, Oracle’s flagship iPaaS product, is increasingly being adopted by customers as their strategic integration platform, for implementing various Cloud-to-Cloud as well as Cloud-to-OnPrem integration projects.
With every release of the product more and more features are being added, and there’s plenty of documentation available on using ICS for designing and developing various integration patterns.
In this blog, however, I will talk about ICS from an operational perspective. I will go over some of the best practices that should be followed so that the Development, Code Migration, go-live, and post go-live maintenance goes as smoothe as possible.
These practices may be implemented either via the ICS UI, or the REST APIs; however, using the APIs provides a great degree of automation. I will refer to the specific ICS APIs below as needed.
These APIs can be scripted using any client programming language, although if Python is being used then Christian’s blog here provides a great set of starter scripts.
The best practices are as follows. I have split them in two sections, Pre Go-Live and Post Go-Live considerations.
Pre Go-Live Considerations
- a. Version Control the Integration IARs
- Although ICS integration IARs are binary zip files, it is still a good practice for developers to check in in the IARs periodically, just like checking in any code. They can export the integrations manually from ICS UI and import it to their git repository, or have this task automated by a CI/CD system that uses the ICS export REST API, described here to export the integration, and check it into their Version Control System on a nightly/periodic basis.
Doing so ensures that the code is never lost. It also helps with code migration, as explained below. Read the complete article here.
- Although ICS integration IARs are binary zip files, it is still a good practice for developers to check in in the IARs periodically, just like checking in any code. They can export the integrations manually from ICS UI and import it to their git repository, or have this task automated by a CI/CD system that uses the ICS export REST API, described here to export the integration, and check it into their Version Control System on a nightly/periodic basis.
For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog 
Twitter 
LinkedIn ![image[7][2][2][2]](https://soacommunity.files.wordpress.com/2013/04/image7222.png?w=20&h=20&h=20 "image[7][2][2][2]"){kind=small}
Facebook ![clip_image002[8][4][2][2][2]](https://soacommunity.files.wordpress.com/2013/04/clip_image00284222.jpg?w=26&h=23&h=23 "clip_image002[8][4][2][2][2]"){kind=small}
Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress
About Jürgen Kress
