Showing posts with label PaaS. Show all posts
Showing posts with label PaaS. Show all posts

23 October 2017

Installation Steps for Oracle Integration Cloud Service Connectivity Agent

Oracle Integration Cloud Service (ICS) is one of the major Cloud Integration platforms which enables Line of Business (LOB) users to easily build SaaS to SaaS and SaaS to On-Premises integrations in just few clicks.

ICS provides an agent framework that enables you to create integrations and exchange messages between on-premises applications and Oracle Integration Cloud Service.  This type of agent is known as Connectivity Agent. 

The Connectivity Agent is installed and runs in an on-premises environment on the same network as internal systems such as Oracle Database, Oracle Siebel, Oracle E-Business Suite and others.

20 October 2017

Create Database Cloud Service (DBCS) using Oracle Cloud Infrastructure Classic

Most of the applications do require a Relational Database to store and retrieve data.  With the introduction of Cloud based database by various Cloud vendors enable organisations to pay a subscription fee to own a database which would be fully managed by the Cloud provider.

All the major software vendors such as Oracle, Amazon, Google and Microsoft do have options to subscribe to a Database Cloud Service.

This blog post shows how quickly and easily an Oracle Database can be provisioned in the Oracle Cloud Infrastructure Classic (OCI Classic) environment.  Please note that OCI Classic was previously known as Oracle Public Cloud (OPC).

3 October 2017

Oracle ICS Stage File Action To Combine Results Inside a Loop

With Oracle Integration Cloud Service (ICS), Enterprise grade Cloud Integrations can be developed in less time compared to the usage of traditional middleware tools.

This blog post addresses on how to combine the results of multiple calls to return the result set through ICS.

Use Case

Requirement is to invoke a service hosted at a SaaS application and return the result set.  But each record in the result set from the SaaS service contains Ids. Due to this, the result set has to be iterated through to make further calls to SaaS services based on Ids to retrieve the relevant details and each record is populated with the results from multiple calls.