One of the very first capabilities Oracle ever introduced in its PaaS portfolio was integration. It was clear from the onset of any talk about clouds that facilities to do integration between cloud and on premises as well as between various clouds [from different vendors] would be essential. With its SOA Suite, Oracle had a very strong on premises offering for integration, and it used this foundation for its first steps on the cloud integration path.
The initial approach from Oracle on integration in the cloud was two-fold:
- SOA Suite Cloud Service offered the originally on premises products SOA Suite 12c along with API Manager, B2B and MFT (Managed File Transfer) running on DBaaS and a WebLogic domain provisioned automatically
- ICS (Integration Cloud Service) provided a citizen developer’s user experience for declaratively creating SaaS to SaaS integration flows, using a quickly expanding portfolio of pre-built cloud adapters; ICS made use of the SOA Suite SB engine under the covers
Additionally, a roadmap was outlined for the continued development of the on premises SOA Suite product that was to mimicked by the SOA Suite CS.
This year, the strategy around integration has somewhat changed, in several ways, visualized in this figure:
ICS is positioned to be the premier cloud integration platform – taking over that role from SOA Suite CS. After making all [or at least most] features in SOA Suite available in ICS – and adding new ones at the same time – it will be ICS that handles all complex integration scenarios, including long running integration processes. When that happens [ maybe two years into the future?], SOA CS is likely to gradually disappear. At that time, the parity between cloud and on premises based integration will also vanish – as ICS pulls ahead and SOA Suite falls behind.
ICS can no longer be considered a citizen developer’s instrument, even though it was originally positioned as such. As ICS has kept on acquiring new features, it has become a developer’s tool that requires technical skills beyond what the citizen developer brings to the table. To prove that point: some recently or soon to be added ICS features are asynchronous message patterns, scheduling, orchestration (the BPEL engine from SOA Suite is now included in the ICS runtime):
The Mapper will be further enhanced – to cater for custom XPath function, loading mapping definitions (XSLT and perhaps XQuery) from other platforms, and for a Source View of the mapping definition (that seems to indicate XSLT that can be inspected and perhaps even edited in the browser).
ICS will soon have REST APIs through which management operations (such as deployment, activate and deactivate, configure endpoint, clone and export and delete an integration) can be performed, in an automated fashion or from a completely custom built User Interface.
Very importantly: the set of Cloud Adapters for declarative integrations with a wide range of Oracle and 3rd party SaaS applications keeps on expanding. These adapters are available in ICS and also in SOA CS and on premises SOA Suite. There are 50+ different adapters – for a large number of SaaS applications, from Oracle and third parties, including Oracle Sales Cloud, NetSuite, Oracle E-Business Suite, Service Cloud, Eloqua, JD Edwards, HCM Cloud, Salesforce, Ariba, Concur, SAP and GMail, Twitter, Facebook:
The 220.127.116.11.0 release for on premises SOA Suite was published in June 2016– with enhancements for continuous availability and JET support in BAM as most striking features; 18.104.22.168.0 will be next was next in late October 2016, with dynamic clusters as key feature. The current roadmap also includes the 12.2.2 release in CY 2017.
Do not expect major leaps in functionality: Oracle considers the SOA Suite quite mature and functionally pretty much complete.
The Integration Platform is closely related to the API Platform; many or even most of the services published from SOA CS, ICS and on premises SOA Suite are likely to be accessed through the API Platform CS. A discussion of this service can be read here, in my previous article.
Self Service Automation
For the business user, a new integration product has been announced: Self Service Automation (OSSA). This offering allows users to create straightforward recipes, in the style of the IFTTT (If This Then That) platform, that prescribe how events in one Cloud application should trigger integration actions in other Cloud applications.
This screenshot shows an example set of Cloud Applications that can serve as either the source of a recipe (a trigger of an integration) or as the target of one.
An example of an OSSA recipe is one that is executed for an event registration in EventBrite and creates a new line with registration details in a Google Sheet as well as a new contact entry in Eloqua.
Among the cloud applications that initially will be supported are Oracle’s own SaaS products and popular 3rd party offerings such as Google Apps, Office 365, Mail Chimp, Dropbox, Asana and Slack.
Also of interest to the business user is the Integration Analytics offering that is now available under SOA CS.
It bundles three tools to use analytics to achieve more insight and act on that insight:
- BAM (Business Activity Monitoring) to create dashboards, alerts and actions based on metrics from processes running in SOA Suite – and custom data streams as well
- Real-Time Business Integration Insight – for collecting and presenting real time business metrics across integration flows, allowing live insight in the functional status. “Insight”has declarative integration with Service Bus and SOA Suite and shortly ICS as well. It also offers APIs that make it possible to add metrics for custom application and integration activity wherever they run, as long as they can make a REST call.This next screenshot shows how in Real-Time Business Integration Insight a milestone can be defined; the REST invocation details including a sample message are provided; these are details used by developers who need to add the REST API calls to Real-Time Business Integration Insight in their custom applications.
Real-Time Business Integration Insight is capable of extracting metrics from running processes and integrations – end to end chains that may span across various technologies and platforms – correlating them and analyzing them – one by one and collectively. The results can be reported in dashboards, forwarded to BAM or BI CS/OBI EE for advanced analysis.
Additionally, milestones can be made actionable: when a process instances reaches that milestone, a call can be made to an HTTP service.
Check out this slidedeck for an in depth introduction to Real-Time Business Integration Insight as well as this blog article with an overview, screenshots and a demonstration video.
Note: there is some overlap between this product and the Customer Insights & Engagement Cloud Service (CIECS) – a service for functionally tracking application activity – and Application Performance Monitoring (APM) under the Oracle Management Cloud Service umbrella that does (primarily) non-functional tracking of such activity (health, response times).
- and soon to be added: Stream Analytics (fka Stream Explorer, fka Oracle Event Processor, fka Complex Event Processor, fka WebLogic Event Server) to ingest real time streaming data from sources such as IoT, social media, web site activity and transaction engines plus the Integration Insight agents and analyze them for exceptions, aggregates and complex patterns that require reporting and action;
Stream Analytics has an impressive roadmap which includes integration with GoldenGate and Kafka as source and destination for events and results
allowing free format CQL and supporting complex patterns for example around location-aware events and patterns such as geo fencing.
Note: Stream Analytics is also embedded inside the IoT CS to process messages received from the devices registered in IoT CS. Oracle also announced the DFML (Data Flow Machine Learning) CS which is also targeted at processing streaming data; how Stream Analytics and DFML CS compare is not yet clear [to us at least].
Tight integration from both BAM and Real-Time Business Integration Insight with Process Cloud Service (PCS) is not currently available, but is on the roadmap to be added after the ICS integration.
Messaging Cloud Service
JMS over HTTP is one very quick and concise description of the Messaging Cloud Service. It is one of the foundational services – somewhere deep in the PaaS layer or perhaps even considered part of IaaS. This cloud services allows messages to be sent over HTTP from anywhere to a cloud based lean publish/subscribe platform – very similar to what JMS offers in a Java EE environment. Consumers can subscribe to topics. Messages on these topics are either kept for these consumers [to come and collect them] or can be pushed if the consumer has registered an endpoint at which to receive said messages. Client libraries are available to have the Messaging Cloud appear as JMS to sending applications. The Messaging Cloud Service is integrated with ICS.
Oracle Data Integration Cloud
Additionally, there is also the largely unrelated Oracle Data Integration Cloud – with functionality derived from or offered by products such as GoldenGate (for near real time replication) and Oracle Data Integrator (for ELT/ETL in bulk/batch integration).
Download the AMIS OOW16 Highlights for an overview of announcements at OOW16.