Integration, Process and Visual Builder by Jin Park

OIC makes integration easy with ODI

We know OIC (Oracle Integration Cloud) is capable of file based integration for ERP over API.
And we do know that ODI (Oracle Database Integrator from Data Integration Platform Cloud) is capable of ingesting large file and processing it for ERP through the database layer aka ETL / ELT.

Okay, what if those cloud services work together and give you a simple pattern which can be applied to typical use case such as large number of big files integration with ERP through the database layer.

Following scenarios would be typical integration use case scenarios;

Financial transaction records from branches / retail merchants come in large number of big files
Files have to be ETL / ELT before cut-off time
Business / IT want to know what’s happened for last batch job processing or current job happening
Financial transaction records have to be kept for certain periods for internal audit and legislative requirements

Now let me show how those integration use cases are implemented by OIC and ODI.

Firstly ODI (Oracle Database Integrator) will do take heavy workloads such as ingesting large files, transforming raw transaction records and load them to target database. Luckily OdiInvokeWebService Tool is available for ODI as an API and Integration (from OIC) will invoke this API. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress