Oracle Integration Cloud Basics-#OIC,#ICS-Post-1
top of page

Tags

Archive

Oracle Integration Cloud Basics-#OIC,#ICS-Post-1

In this Article , i will cover the basics and the building blocks of OIC . Any one who is new to this tool will get benefited with the same.

OIC is an IPaaS offering from oracle which is a no-code/Low-code tool offers seamless integration options between third party , on-premise systems with out writing any code. In layman terms its a visually rich tool where one can simply and rapidly create easy to complex integrations by dragging and dropping the visual components . If you think something is not achievable with what is available out-of box components, one can always write custom java script libraries or advanced XSLT functions to achieve the intended functionality.

Furthrmore , OIC runs on Oracle cloud infrastructure gen2 which is secure, high performance Infrastructure .This tool provides there offerings i.e Application integration,Process Automation and Visual Builder Application.


Quick Look of Welcome Page:




Home Page:



In this post I will only focus on Integration cloud components.


Components of Oracle Integration Cloud:


Application Integration: you can build integrations rapidly between 3rd party and Oracle systems on both cloud and on-premises . The pre-built adapters makes the integration developer job easy and quick . This is were one can create , test ,manage and track integrations .

Quick look of the integration page:




Process Builder : This tool is a lightweight version of BPEL . Using this tool one can define business process like an approval process and some basic forms to enter the information and initiate an approval process . This can be further used in an integration or an VBCS application as per the requirements.

Quick look of process builder :





Visual Builder (VBCS) : using this tool one can extend the SaaS and On -Premise applications in a drag and drop manner . One can create both web and mobile applications rapidly. Extensions created using this application can be embedded to the SaaS application regions .





Connections: Think this way ,in a traditional way of integrating an application with third party,one have to write a lot of code , The connections components in OIC simplifies this . They let you connect to Cloud and on-premise applications to share the data. Generally Connections are starting point of the application integration and they are based on the adapters.Connections can be two types

1) Inbound which is a trigger connection

2)outbound which is a invoke connection



Adapters: Adapter represents a third party application where one can configure properties like WSDL url and security credentials and so on to communicate with a specific instance of an application.



Lookup's : Lookup comes very handy when mapping data between multiple applications for example , if you are integrating between workday and oracle hcm you need a common column to interface the employee information between these applications ,however the employee numbers are called different in two systems

like for instance workday may call as employee_number where as

oracle hcm call as person_number . in short lookup's are providing the capability to map values across vocabularies or systems. one can define application specific values and use it at the run time to map the values. They are reusable and static in nature .



Packages :

Packages gives the ability to group the similar integrations into packages . for example all hcm integrations can be grouped under one package . similarly with other

module specific integrations can be grouped under one package . This will give the ability to organize the same kind of integrations into a package and further more because of this packaging , the developer will get the option to

deploy the entire package to the target instances . This will bring all the integrations which are part of this package. if not as a package one have to export and import

individual integrations manually.




Agents : Agents are required to connect to on-premise applications . A classic example would be connecting to EBS instance. A separate set of configurations need to be done to set up the agent. Think this way , anything behind a firewall and not publicly exposed to internet would need the agent setup to connect successfully.





Libraries : This contains custom JavaScript functions bundled in a jar file . This component is given to facilitate the custom coding to achieve complex or not possible scenarios using OIC internal components.



Monitoring:

OIC Monitoring is a one stop dashboard to give the integrations statistics which includes , success , failed messages and various debugging options to troubleshoot the

integration runs.


Quick look of the dashboard Page.




Hope This Helps ! Happy Learning.

182 views0 comments

Recent Posts

See All

Other Posts you may Interested 

bottom of page