OIC to perform the Integration
Handling integration between Oracle SaaS applications and modules has been something of an evolutionary journey. A couple of years ago if you wanted to intgrate say HCM and ERP you needed to ICS or OIC to perform the integration.
In many
respects, this wasn’t such a terrible thing. Technically as it meant that the
back end database schema development for each app was not going to be slowed by
needing to be mutually dependent with each other. As a result avoiding the
complexities of managing a canonical model and ensuring any changes to that
model are delivered in a manner that aligns across multiple development teams
plans.
Although
you can see from a marketing position it might not have seemed so great, as the
customer incurs more cost and development effort to realize a process of
managing people (HCM) and paying them (ERP) for example.
Things have
moved on, and as long as SaaS apps reside in a Global Single Instance (GSI)
(i.e. same region, account and deployment) then for the major products (e.g.
ERP, CX, HCM, etc) are internally integrated so a person change in HCM will
propagate to ERP as necessary. This certainly reduces the need for integration,
saving effort (and the cost of needing OIC).
The problem now is understanding
which entities in the SaaS apps are integrated out the box if you deploy using
the GSI manner. If you have been working from an integration/technology view
point with ICS and OIC for a while it is very easy to get sucked into thinking
you need to repeat the integration. After all explicitly integrating the apps
is how we started out.
Oracle also
want to make it very easy for non Oracle products to integrate, so OIC
documentation and the many very good blogs from product management and the
engineering team focus on external integration which does (for me atleast) lead
to thinking about the older way of working.
Comments
Post a Comment