Visual Builder Cloud Service (aka VBCS), one of the 3 legs of Oracle Integration Cloud (aka OIC), is a low code development environment that is one of the main mechanisms for extending Oracle Fusion SaaS Apps.
In this episode we are connecting VBCS to a SaaS instance, so we can get the different endpoints provided and then use it in the application.
What you need is:
a user with access to OIC instance
same user with access to SaaS instance
Step 1: Create a new VBCS app
Step 2: Configure
The url to provide has the following format: https://instancefqdm/helpPortalApi/otherResources/latest/interfaceCatalogs
where instancefqdm is your SaaS instance such as https://<id>-<env>.fa.<datacenter>.oraclecloud.com
Click on [Test] button
Step 3: Import the catalog
Step 4: Use an endpoint for listing Contacts in a table
Oracle Integration Cloud (OIC) is a platform that allows to orchestrate integrations between different systems in a simple way, using low code paradigms. In this post we will explain how to connect OIC to ERP. For this we need an ERP instance and an OIC instance and execute the following steps.
Create a connection to ERP REST Services
The main thing here is provide the url, which is as follows:
Process: a Business Process Managament and Business Rules environment
Visual Builder: a visual low code development environment
Oracle API Platform Cloud Serviceis a API life cycle management solution. It allows you to plan, specify, implement, deploy, entitle, policy enforcement, publish, grant and observe (analytics) your API’s.
Putting things together
OIC has a setup that allows connecting it to an API Platform instance easily. Let’s have a look:
Create an ICS and an API platform service instances. Grab the fdqn url of the API Platform instance portal
Go to your ICS service instance portal and, in the [Integrations] menu, go to [Configuration] and then [API Platform]
Enter the information of the existing API Platform instance you created before and click on [Save]
Config is ready, and now what else?
Go to the lists of integrations in ICS and select one that is finished and ready to activate and click on the [Activate] button or menu.
As you can see, the connection between ICS and API Platform is working, and we are proposed to choose what to do. We can activate the integration (only in ICS) or activate in ICS and publish to API Platform.
Let’s clink on [Activate and Publish…]
You have two options, create a new API or add to an existing one. Leave unchecked the Deploy and Publish options. Once you have finished entering the values, click [Create]. Integration is activated and a new option appears in the hamburger menu:
Now, go to the API Platform portal instance and notice the new API created:
We haven’t deployed the API to a gateway, therefore it is not yet ready for consumption thought API Platform, that is something we’ll explain in coming post. For the moment let’s keep in mind that the integration implemented in ICS has been deployed to API platform and is ready for start applying several API management best practices, such as applying security, traffic, interface or routing policies.