This blog is the third in the FlexDeploy Loves OIC blog series, stay tuned for subsequent entries in the series.
- FlexDeploy Loves OIC: Series Overview
- FlexDeploy Loves OIC: Manage Integrations with Connections
- FlexDeploy Loves OIC: Manage Connection Property Replacement
- FlexDeploy Loves OIC: Continuous Integration
- FlexDeploy Loves OIC: Automated Testing
- FlexDeploy Loves OIC: Continuous Delivery with Pipelines and Releases
- FlexDeploy Loves OIC: Manage Connections, Lookups and Libraries
Oracle Integration Cloud (OIC) provides the ability to develop an integration in the cloud. The integration can connect cloud and/or on-premise applications; however, these integrations are maintained directly in the cloud and not in any Source Code Management (SCM) system. Consequently, applying the DevOps principle of Continuous Integration with OIC isn’t as straight forward as it is with a SCM system to watch for changes.
Luckily FlexDeploy has a few tricks that can make this process easier which we will walk through here. At a high level these are the steps to perform:
- Create a Cloud Account for OIC Development Environment (if not already done).
- Create an SCM Integration Instance of type OIC
- Configure the Project to use this as a source control system and add a CI trigger
Cloud Account
If you have been following along since the beginning then this would be done already. However, if you are just joining you can review the Cloud Account creation process here.
Create an SCM Integration
In order to make use of FlexDeploy’s built in CI server, we need some SCM Integration instance, lucky for us there is an OIC scm type for just that. Navigate to Topology->Integrations->Source Control and create a new SCM Instance.
Be sure to specify the type as Oracle Integration Cloud and use the Cloud Account created in the previous steps.
Project Configuration
Last but not least we need to update our Project to use this new configuration and add the CI trigger.
Note that after adding this configuration, the Integration Identifier project property will become irrelevant. At this point our project can now make use of all the features of using a Source Control system. Most notably the ability to use CI!
Simply head to the CI tab and add a Poll SCM Trigger and watch the CI beauty.
Validation
I made a change to Process HR Request integration offscreen and below we can see the CI process picking up the change. Note that the CI process for OIC will only check for changes on active integrations.
In addition to Continuous Integration we will also get some basic change log information such as the last person to make a change and what time it occurred.
There you have it. In just a few simple steps we can actually configure OIC with Continuous Integration by making use of common FlexDeploy features.
Previous Post: FlexDeploy Loves OIC: Manage Connection Property Replacement
Next Post: FlexDeploy Loves OIC: Automated Testing
