Thursday, April 23 2026

News :  πŸ˜‡

This post published in February 2021 Edition of Oracle PaaS Partner Community Newsletter


In this article we will see the steps to invoke a BI Report in an Integration and then the steps to read its base64 encoded output.

we will do the development by breaking it into 2 parts :

PART 1 : Steps to invoke a BI Report
PART 2 : Steps to read the base64 encoded report output. (access link)

– Advertisement –




News :  πŸ˜‡

This post published in February 2021 Edition of Oracle PaaS Partner Community Newsletter



In the previous post we have seen the PART 1 of BI Report Invocation. If you don’t have seen that requesting you to first check that out by clicking here.

In this article we will develop the left part (PART 2) i.e. convert the base64 encoded run report operation response  and then read it in proper XML format using stage activity.


– Advertisement –





Integration Properties are user defined properties available for usage by activities (e.g. Notification , Log) as read-only data with in the flow. Read only data πŸ‘‰ because the integration property value can’t be updated within the integration. For example, you cannot update the integration property in an assign action. You can update integration properties value

In this article I have tried to explain how we can use Global Variable and Data Stitch Action in an Integration. About Global Variable : You can create complex and simple type global variables that are available for usage throughout an orchestrated integration (for example, when building an expression in the Expression Builder of an assign

In this blog I have described the steps to configure the OTM connection in Oracle Integration Cloud Instance. STEPS OVERVIEW : – Step 1 : Configure OTM Connection using Logistics adapter. Step 2 : Upload OTM SSL Certificates. Prerequisite : Requesting you to follow this blog & download the OTM SSL certificates files. We need it in

In this post I have explained how to send Attachments along with notification’s body in OIC Notification action. Knowledge :πŸ‘€ The total size limit on a notification email is 1 MB for Oracle Integration and 2 MB for Oracle Integration Generation 2. Steps overview to send attachment in OIC notification action  : Open the Notification action and click

  News :  πŸ˜‡ This article published in October 2020 Edition of Oracle PaaS Partner Community Newsletter New update in OIC allow us to replace any connection used in an integration with another connection of same Type and Role. Earlier if you want to replace any existing connection of an integration for that you had to delete



In this blog we will test the Integration which we have developed in previous blog
Prerequisite : SoapUI Tool
Lets see the testing steps in detail :
  • Activate the Integration and open the URL which get generated after integration activation.
  • Copy the Endpoint URL 

– Advertisement –




News :  πŸ˜‡

This post featured in June 2020 Edition of Oracle PaaS Partner Community Newsletter



Oracle Integration Cloud Service provides “Global Fault Handler” to catch errors/faults in orchestrated integration and perform actions. In an event of a fault in an integration it goes to “Global Fault Handler” to perform some user define actions like notifying about error by sending email notification etc. and then stops the flow of integration abruptly with an error state i.e. integration will stop and not move to next logical step. We can add fault handling to any integration type (for example: app driven orchestration, scheduled integration etc.). 

Now suppose πŸ‘€ β†’when you have to iterate through multiple conditions and need to continue even if one condition fails i.e. you don’t want your integration flow to stop but move on to the next logical step. To achieve this we have to configure “Default Fault Handler” (at Scope Level).
Scope can catch the error and move ahead to the next logical step in the integration.This does not stop the integration abruptly but rather moves to the next logical step(ex. if there is any Loop, loop will continue to execute).



USE CASE I: [BASIC TYPE] Schedule the integration for every 10 minutes. For this type there is minimum frequency limit of 10 minutes. If you try to define a schedule frequency of under 10 minutes, a validation error occurs. Use iCal to schedule the integration below 10 minutes.
USE CASE II: [ADVANCE TYPE] Schedule the frequency for every 5 minutes using iCal expression. 

– Advertisement –




1 5 6 7 8 9