In 2015, Oracle made available their latest tool within their integration cloud strategy, Integration Cloud Service (ICS). With the number of SaaS applications growing, the need to integrate is becoming more important, making ICS even more relevant.
Skip to 2020 Update: Why the new Oracle Integration Cloud may not be right for you.
The intended usage of ICS are implementations of simple, light weight integrations between SaaS applications. It resides within the cloud, is built off the Oracle Service Bus, and is available on a monthly subscription basis.
Pre-built solutions will be available in the marketplace (think app store), allowing for reusable integrations to be purchased, implemented in an accelerated manner. This will provide the option to reuse existing integrations as-is, or build on top of the existing, customizing for your business integration needs. If the pre-built solutions don’t meet your integration needs, the capability to develop your own from scratch is always on option. Either way, the development of an integration within ICS can be done using the capabilities detailed in this article.
Within ICS, there are 4 aspects: Integrations, Connections, Lookups, and Packages. Each of these will be discussed in further detail.
Developing integrations between SaaS applications is done in ICS via a web based tool. Using drag and drop capabilities, an integration can easily be defined. Since the tool is built on top of OSB, the functions defined within the VETO (validate, enrich, transform, and operation) integration design pattern are available for implementation:
The same XSLT mapping tool available within the SOA Suite 12c is also available within ICS. ICS provides the ability to create the maps within the web based designer (see example below), but also has the ability to import maps developed in JDeveloper, allowing for reuse between cloud and on premise SOA implementations.
Of note is the ability to define complex mappings, using functions, operators and XSL elements. Glad to see this functionality included, since these are necessary in so many transformations used within an integration:
Through the use of the message cloud service adapter, the publish/subscribe integration pattern can be implemented. Along with this, ICS can listen to events generated by an application, providing the ability to then publish to whatever system is interested. If application generates an event, ICS can listen to it.
The dashboard within ICS gives visibility into what is happening within the integrations. Like auditing in SOA Suite, messages can be introspected for purposes of troubleshooting and debugging.
As shown below, the dashboard in ICS provides a snapshot of the health of the integrations:
The connections can be configured for notification of issues, ensuring that any issues do not go unnoticed:
Oracle SOA Suite has the ability to set sensors within an integration implementation, providing easy search capability for data defined within the sensor. The same capability in ICS is contained within ‘Business Identifiers for Tracking’. These defined fields are then searchable within the ICS dashboard, allowing for easy lookup of instances that contain the defined fields.
A connection is defined for any endpoint (source or target) that is implemented within an integration. These connections are based off of defined adapters. Adapters allow for easy connectivity to applications, insulating the developer from complexities that can occur when interacting with an application (i.e. token management). Currently, there are a handful of adapters available, with many more planned within the roadmap.
A new adapter framework is available for adapter development. The cool thing about these adapters are that they can used either in the cloud or within the on premise SOA Suite, provide greater reuse.
Domain Value Maps (DVM) have been a part of the Oracle SOA Suite for a while now. They provide a way to implement a lookup table (i.e. state abbreviation to state name) easily within the toolset. ICS has the same capability, allowing for cross reference lookup of data within mappings. Just like DVMs, the tables are reusable across multiple integrations. Along with this, the Lookup maps can be imported and exported to CSV format, again allowing for reuse across cloud to on premise implementations.
Packages allow for grouping of integrations, providing the ability to import and export packages between environments. The action of exporting a package creates a .jar file, which can then be imported into another environment. When a package is imported from a .jar file, all artifacts (integration, connection, lookup, etc.) are created/updated.
One thing to note about this functionality is the impact on connections. When a connection is imported, it is created with an empty configuration the first time, eliminating the need for a config plan. Instead, the configuration can be updated within the environment where it’s been deployed.
But Oracle ICS May Not Be Your Best Option
While the concept of Oracle’s system integration platforms may have been revolutionary at the time, as more software and applications have become available and business has become more sophisticated, Oracle integration no longer offers the same benefits it once did.
In fact, in a May 2020 IT Central Station survey, MuleSoft integration products were rated far above Oracle ICS by IT professionals.
It’s faster, easier, has a lower cost, and aids organizational innovation.
One IT professional surveyed in the report commented: “The API-led approach of MuleSoft offers a very cost-efficient model and re-use for implementation and support of microservices, APIs and (generic) services when followed correctly, and is fully supported and enabled by the web engagement tools of the platform (Anypoint Exchange, Anypoint Portals, and Anypoint Design Center). The approach results in a decrease of maintenance costs and time for internal IT departments and external IT vendors and frees up time in an organization for innovation.”
And, “An iPaaS and/or API management offers more advantages, such as shorter time-to-market, less staff required for development and maintenance, fewer incidents on support, etc. MuleSoft has a pure and dedicated vertical focus on product development for integration with their API management and iPaaS offerings, which can be considered a plus.”
And, with a simple approach to implementation, you don’t have to be a developer to get MuleSoft up and running.
A Forrester Total Economic Impact report found that:
- $4.2 million increase in API reuse value through Anypoint Platform, which includes increased reuse rate and time savings from project efficiencies.
- More than $1 million in time savings toward building new APIs.
- At least $740,000 incremental revenue from the platform’s contributions to various top-line projects.
- 90% less time spent on maintaining APIs and integrations, allowing time to be reinvested in innovation.
And MuleSoft API is more efficient than point-to-point connections.
With these and many other benefits such as, when you’re looking at integration products, Mulesoft is clearly the better choice for integration cloud services than Oracle ICS.
If you’re working with Oracle, wouldn’t you be better served with a solution that’s more efficient, quicker and easier to implement, and that provides you with better support? If yes, MuleSoft is the solution you’re looking for.
Implement MuleSoft integrations into your organization! Get in touch with us at AVIO today.
While ICS is certainly an option within the SaaS application integration space, among application integration products, MuleSoft provides the superior experience.