Consultant at a tech services company with 10,001+ employees
Real User
Nov 8, 2019
ODI – The difference I see is it is used for data integration to load huge data from across different databases and within the same databases like PLM to BI, EBS to BI, etc.
OCI – It is for integrations between systems like SOAP services etc.
EPM/BI certified Consultant, Oracle ACE and TeraCorp Consulting CEO at TeraCorp Consulting
Consultant
Top 20
Nov 7, 2019
I would say the biggest difference is that ODI is a corporate class tool that can do anything no just in a matter of ETL but a process controls since you can have ODI managing your entire environment using java code to start processes, or calling web services and more. OIC would be a more focused application create as a workflow to load and extract data of your cloud apps.
If you intend just to automate your cloud env, and you will have everything on the cloud, OIC is enough for you. If you already have a big on-premises environment and want to extend that to the cloud and wand to seamlessly integrate them, I would stay with ODI.
ODI is typically used for batch/micro batched based processes. Its origins are with ETL (Extract Transform Load) or as Oracle describes it ELT (putting the work for transform into the DB rather than the transfer component). That said it does have a lot of adaptors for no DB centered sources.
OIC is event focused - although an event could be a DB trigger. Therefore the payloads are typically smaller. If you had a data extract, then you'd expect to iterate over the extract processing a row at a time rather than a bulk transaction. As a result, it is better for choreographing multiple system changes e.g. sales order --> update manufacturing, book shipping, invoice customer, etc. OIC also has increasingly more powerful integrations with Oracle SaaS, for example, can be aware of events flowing within ERP, HCM to trigger other tasks. ODI does have or need this.
OIC has a richer toolset, for the EE edition you get the use of Process Cloud which is best for very long-running processes (days and weeks not minutes and hours) and human workflow. The visual Builder is also incorporated, providing the means to build apps, and particularly good at building and integrating extensions to core Oracle SaaS.
In a Hybrid context, where ODI is located can create some connectivity challenges - host in the cloud, you could be confronted with issues of getting connected to an on-prem DB. Whereas OIC has a connection/execution engine which can gather and push data to the cloud OIC for onward processing (outbound data flows are more acceptable security-wise)
ODI – The difference I see is it is used for data integration to load huge data from across different databases and within the same databases like PLM to BI, EBS to BI, etc.
OCI – It is for integrations between systems like SOAP services etc.
I would say the biggest difference is that ODI is a corporate class tool that can do anything no just in a matter of ETL but a process controls since you can have ODI managing your entire environment using java code to start processes, or calling web services and more. OIC would be a more focused application create as a workflow to load and extract data of your cloud apps.
If you intend just to automate your cloud env, and you will have everything on the cloud, OIC is enough for you. If you already have a big on-premises environment and want to extend that to the cloud and wand to seamlessly integrate them, I would stay with ODI.
You can take a look at this article that I wrote some time ago to give you a better idea of what I'm talking about:
www.oracle.com/technical-resources/articles/middleware/radtke-giampaoli-odi-cloud.html
In the end, if you want to have a very very flexible tool that can do anything, ODI it is. If you want just to integrate your cloud apps, OIC it is.
ODI is typically used for batch/micro batched based processes. Its origins are with ETL (Extract Transform Load) or as Oracle describes it ELT (putting the work for transform into the DB rather than the transfer component). That said it does have a lot of adaptors for no DB centered sources.
OIC is event focused - although an event could be a DB trigger. Therefore the payloads are typically smaller. If you had a data extract, then you'd expect to iterate over the extract processing a row at a time rather than a bulk transaction. As a result, it is better for choreographing multiple system changes e.g. sales order --> update manufacturing, book shipping, invoice customer, etc. OIC also has increasingly more powerful integrations with Oracle SaaS, for example, can be aware of events flowing within ERP, HCM to trigger other tasks. ODI does have or need this.
OIC has a richer toolset, for the EE edition you get the use of Process Cloud which is best for very long-running processes (days and weeks not minutes and hours) and human workflow. The visual Builder is also incorporated, providing the means to build apps, and particularly good at building and integrating extensions to core Oracle SaaS.
In a Hybrid context, where ODI is located can create some connectivity challenges - host in the cloud, you could be confronted with issues of getting connected to an on-prem DB. Whereas OIC has a connection/execution engine which can gather and push data to the cloud OIC for onward processing (outbound data flows are more acceptable security-wise)
ODI is the tool to build ETL processes. But I don't know the Oracle Integration Cloud Service solution.