We covered the basics of CI/CD automation for integrations in the past, and now you can leverage the same capabilities with Gen3 versions of Oracle Integration. Gen3 of Oracle Integration introduced features that modified the authentication and discoverability approaches of instances. Version 2501 of Visual Builder Studio added new features to support the changes in the infrastructure, allowing you to continue and integrate the two services – both for CI/CD automation as well as development of Visual Builder apps inside the integration instances.
Here are the basic steps for mapping your Oracle Integration instances in Oracle Visual Builder Studio:
Getting Permissions
VB Studio can now use OCI Resources as the approach for discovering Integration and Visual Builder instances (replacing the older IDCS resources approach). To allow your VB Studio to discover these you'll need to define a security policy in your cloud tenancy.
As a first step find out and copy the OCID identifying your VB Studio instance – you'll use it in the policies you are about to define.
From the Cloud console, navigate to the policies section of the "Identity and Security" section. Here you'll want to either modify the policy defined for your VB Studio instance (search the list of available policies) or create a new one to add three new policies as explained here. Use the OCID you copied in the policies.
Adding Instances to Environments
Now that your VB Studio has the right policies in place, you should be able to discover Integration and Visual Builder instances in your tenancy and add them to environments in your project.
Define or edit an Environment and click the add instance button – VB Studio queries OCI to find out the instance you can access. You'll see separate entries for Integration instances and Visual Builder instances (unlike in the days of OIC gen2 which had them combined). Add to your environment the instances you are interested in integrating with. Into each environment you can add a single integration and an additional single VB instance.
Important note – if the instances that you are after are in a different region or compartment, switch the region being searched by click the pencil icon on the left and picking a different region from the list.
Once added you'll see the status for your instances, and will also be able to directly navigate to their home pages from the environments tab:
Access to Integration Artifacts
Once the Integration instances is mapped in an environment you'll be able define export/import CI/CD steps against the instance.
Note that with Oracle Integration Gen3 the authentication approach for the build jobs will be OAuth. When you first pick up an instance in a build step you might need to click the authorize button to let VB Studio access the integration artifacts (check for popup blockers in your browser if nothing happens).
Once authorization is available, you can use the search option to lookup integration artifacts in your instance:
You can use any of the following build steps to automate migration and activation of artifacts from one environment/instance to another:
For more on defining the build automation for integration see our documentation.