Understanding Integration Cloud and how to get the most out of your implementation

Category: Definitive Guides

Longer looks at ICS features and capabilities. Covering things that have been added to ICS since the book was published or couldn’t be fitted in.

Pre-requirements for creating Fusion ERP connection in Oracle Integration Cloud

To be able to successfully create a connection between Oracle Integration Cloud and Oracle Fusion Apps, for example ERP Cloud, there are some pre-requirements to perform. If we want to connect Integration Cloud with Fusion Apps it is in most cases required to import OAuth signing keys from the OCI IAM used by Integration Cloud into Fusion Apps Console. This article provides a step-by-step guide on setting up these pre-requirements.

In our last article, we tackled the process of linking Oracle Integration Cloud with Fusion Apps, like ERP Cloud, through OAuth 2.0. As we navigated the setup, we detailed the creation of two confidential applications in OCI IAM to tap into the Fusion Apps Endpoint URL. But before you dive into the Oracle Integration Cloud configurations, there are essential prerequisites to bear in mind. Neglecting these could lead you to grapple with numerous CASDK-0004 errors when you give the connection in Integration Cloud a test run.

How to create Confidential Applications in OCI IAM for Invoking Fusion Apps Endpoint using OAuth

When seeking a more secure connection method to access Fusion Apps Endpoints (e.g., REST API or Integration Cloud Adapter) beyond basic authentication, OAuth 2.0 is the preferred choice. To implement OAuth 2.0 with Fusion Apps to connect Integration Cloud, you must configure two confidential applications in OCI IAM (formerly known as IDCS – Identity Cloud Service). This article provides a step-by-step guide on setting up these applications for a Fusion Apps Endpoint.

In this introductory blog post, we’ll address how to seamlessly connect Oracle Integration Cloud to Fusion Apps, like ERP Cloud, using OAuth 2.0. Our journey begins with establishing a confidential application in OCI IAM. This crucial step aids in accessing the Fusion Apps Endpoint URL. 

Custom functions to extend ICS transformations – ICS Definitive Guide #4

In the second release of 2017 (17.2.5) ICS will introduce the capability of importing and using custom functions. These functions are created using JavaScript and can be used in transformations, expressions and as a action in Orchestrations. In this definitive guide we will go through all ins and outs of this new capability. 

Custom functions – a new pillar of ICS

In our book we talked about the pillars of ICS; Connections, Integrations, Lookups, Agents, Adapters and Packages. This release introduced Libraries. A library is a set of Javascript functions. Keep in mind that the JavaScript functions are running server-side so some browser/client-side capabilities/APIs are not available. Functions can’t be created within ICS, but can be uploaded as part of a library in both JS and JAR file (collection of JS files) formats.

Applying configuration management and related dev practises – ICS Definitive Guide #3

Good development practises such as  configuration management and naming conventions have been a topic of conversation a number of times recently for us when it comes to ICS. In this post we will look at what configuration management means to ICS and the application of naming standards.

Why Configuration Management?

So why do we need configuration management with a tool such as ICS? The question depends on what stage of the software lifecycle you are, but a few reasons:

  • As a developer there have been occasions where we have tried to optimise something and then decided to reverted back to the last secured state in configuration control.
  • Deleted something and then regretted it, whilst desktops have the concept of paper basket to recover from, not so in ICS.
  • If your providing packages of ICS functionality you may have different released versions – so need to keep master copies of every version available to refer to.
  • Sometimes we get ‘configuration drift’ – and therefore need to have a reference point to compare to. This allows us to determine the drift and if it is appropriate to reset an environment. Whilst this may sound less significant, it is enough of a problem for tools like Puppet to incorporate the ability.
  • Tracking what versions of integrations are running in a development vs production environment.

Scheduling Orchestration Integrations – ICS Definitive Guide #2

This is the second article in the Definitive Guide series. This time we take a look at the ability to Schedule an Orchestration integration within ICS has arrived with release 16.4.5 release of ICS,   To demonstrate this, we are going to reuse our FlightSitRep endpoint from the book’s Chapter 3. If you have not got the book yet – it’s a WSDL one way integration that is connected to Mockable.io.

Creating Scheduled Orchestration

From the Integrations screen we need to click on the New Integration button, and select the Orchestration pattern in the pop-up dialogue. The first thing we will see when creating an integration is the Create New Integration dialog, as shown here:

create new orchestration wizard

As you can see the dialog has a new toggle option which defaults to represent the common approach to Orchestration, that being event triggered through an event or object defined by a connection.

For Each activity for processing batches – ICS Definitive Guide #1

This is the first blog in our ICS Definitive Guide series. In this series we pick one feature that ICS offers and write the most detailed guide on it. This blog introduces the capability of processing batches using the For Each activity in orchestration type integrations.

These blogs follow the same writing style as the book. We sometimes use the same resources as we used in the book, which can be downloaded from the website of Packt. For this blog we are using the same WSDL as we used in chapter 5, Going Social with Twitter and Google, and as in chapter 10, Advanced orchestration with branching and asynchronous flows, but with a little change to one element.

The integration we are going to build simulates a notification send from our Airport Flight Schedules system with a list of persons that are missing / late for their flight. For each flight a list of persons are included in the notification. For each missing person a task is added to a Trello Board, used by the ground personal, to remove the passengers luggage from airplane.

Powered by WordPress & Theme by Anders Norén