What are the Different Types of Integration Pattern available in Oracle Integration Cloud Services

By -

Once you subscribe to Oracle Integration cloud services, you will have access to different sorts of integration patterns. This Integration pattern enables you to build integration faster in an efficient way, rather than creating an integration application from scratch and building it.   

So let's discuss what are those integration patterns and how to use them


App Driven Orchestration


App Driven Orchestration pattern is a multi-step pattern, allows invoking multiple applications in a single flow, doing a for-each loop, if-else logic, apply complex logic, etc.




Scheduled Orchestration

 Scheduled Orchestration pattern allows you to develop an integration that can run on the pre-defined frequency and can be executed on an ad-hoc basis






File Transfer

File Transfer pattern allows moving files across network seamlessly and securely. This is again a scheduled type of pattern.




















Basic Routing

Basic Routing Integration is created initially with empty Trigger and Invoke connections. This design is adopted with the use case, when we have a requirement of integrating business entity of one system to another, with their mapping data structure for request and Response.

We can create only SINGLE routing expressions in Basic Routing integration. In case we have a requirement for creating multiple routing expressions, we should use the Orchestration Design pattern.




















Publish to OIC

Publish to OIC pattern allows publishing messages to OIC internal messaging queues. For example, an event is subscribed from Oracle Sales Cloud and Publish the same into Oracle Integration Cloud messaging queue.



















Subscribe to OIC
 
Subscribe To OIC pattern subscribe messages from Oracle Integration Cloud messaging queue and sends the same to different applications

















These queues  are managed by OIC itself and you don’t have access to them


Pranay is a versatile Oracle Technical consultant. Adept in Oracle ERP development, SDLC management, design, and architecture. He has 11 years of extensive experience in Oracle Apps implementation engaged in technical development areas of Oracle Applications 11i/R12 E-Business Suite. He possesses sound knowledge in technologies like OAF, ADF, J2EE, MSCA, Oracle PaaS Cloud, Java Cloud services, ADF & XML Publisher. Currently, he is working for BirlaSoft Inc. USA. Being a Consistent solution provider in Oracle Developer Community forums earned him the title of "Technology Master”, Currently he holds 3rd position globally for providing a solution in Oracle Developer Community for the OAF Workspace. He has also authored several articles on ADF Technology, Fusion Financials, OAF & PaaS Cloud. He successfully presented the case study in Oracle Collaborate event forum on "How optimizing the Oracle Mobile App Solution Helped in Boosting the Productivity of a Warehouse."

Comments

Post a Comment

Popular posts from this blog

Sample HZ API's script to Create Contacts and Contact Points in Oracle

By -
1. Below Code will create Contact Point in Oracle . DECLARE    P_CONTACT_POINT_REC   HZ_CONTACT_POINT_V2PUB.CONTACT_POINT_REC_TYPE;    P_PHONE_REC           HZ_CONTACT_POINT_V2PUB.PHONE_REC_TYPE;    P_EDI_REC_TYPE        HZ_CONTACT_POINT_V2PUB.EDI_REC_TYPE;    P_EMAIL_REC_TYPE      HZ_CONTACT_POINT_V2PUB.EMAIL_REC_TYPE;    P_TELEX_REC_TYPE      HZ_CONTACT_POINT_V2PUB.TELEX_REC_TYPE;    P_WEB_REC_TYPE        HZ_CONTACT_POINT_V2PUB.WEB_REC_TYPE;    X_RETURN_STATUS       VARCHAR2 (1000);    X_CONTACT_POINT_ID    NUMBER;    X_MSG_COUNT           NUMBER;    X_MSG_DATA            VARCHAR2 (1000); BEGIN    P_CONTACT_POINT_REC.CONTACT_POINT_TYPE := 'EMAIL';    P_CONTACT_POINT_REC.OWNER_TABLE_NAME := 'HZ_PARTIES';    P_CONTACT_POINT_REC.OWNER_TABLE_ID := 150336; ---L_ORG_PARTY_ID; commented by  pranay tiwari on 05-Jun-2014    P_CONTACT_POINT_REC.CREATED_BY_MODULE := 'TCA_V2_API';    ----email    P_EMAIL_REC_TYPE.EMAIL_FORMAT := 'MAILHTML';  
Read more

REST integration built-in OIC to read Large files with size more than 10MB

By -
Image
Processing large files in any integration requires a lot of effort and complex coding. Every integration platform has a limit size to read a file, similarly, the OIC service provides a limit of 10MB to read the file, if the size exceeds, then the below error will be encountered  Error Reason: Translation Error. Translation Error. Error while translating message to native format. Please make sure that the payload for the outbound interaction conforms to the schema and payload size does not exceed threshold. Error occured as File size exceeds maximum threshold size of 10 MB : Application Error Error Summary: ICS runtime execution error  In this article, we will learn how to read the big-size file in OIC.  Note only XML and CSV formats are supported for larger file read operations.  Here we will build an integration with a source FTP connector to read files containing sizes more than 10 MB  &  read them through the "Read File in Chunks" features and create multiple files  at
Read more