Agent for simplifying Integration between Cloud and On-Premises apps

Robert van Molken 3
0 0
Read Time:2 Minute, 4 Second

In the last few months I mentioned that Oracle is developing an Agent. The Agent easily integrates your on-premises application(s) with the Oracle Cloud Services. The Agent is rolling out on all production instances next week. It was publicly announced by Bruce Tierney on the 3rd of January. He is the Director of Product Marketing for Cloud Integration and SOA. You can read his announcement on the Oracle Integration blog.

In this first article about the Agent I will go into the architectural basics,  which components are included and how it will connect Cloud to On-premises applications. The article is based on information I presented about during OpenWorld 2015.

Current / classic integration approach

The current approach for connecting Cloud / Internet hosted applications with On-premises applications is usually through one or more firewalls, and the use of a reverse proxy, Oracle API Gateway or OHS. For this a variety of expertise is needed for example to open up inbound ports in the firewall, expose a private SOAP/REST service and configure the network routing. The SOAP/REST service can for example be implemented with SOA Suite to for example communicate with the CRM to retrieve customer data.

Let look at the current / classic approach in the diagram below:

ICS+SOA CS Scenario
This is going to change a lot when using the Agent. It will simplify above diagram.

Common Cloud to On-Premises Integration Patterns

Currently there are three common patterns for Cloud to On-Premises integrations. They are 1. using messaging, 2. through a proxy and 3. using an agent.

Proxy (Sync or Async) – Hybrid Cloud

  • On-Premises SOA Suite is accessible with a web-Proxy in the DMZ, e.g. API Gateway or OHS.
  • On-Premises SOA Suite hosts the adapter that Cloud application can invoke.
  • Integration Cloud Service sends the messages through the Proxy.

Cloud 2 Ground PatternsMessaging (Async) – Hybrid Cloud

  • On-Premises SOA Suite polls the Messaging Service.
  • On-Premises SOA Suite hosts the adapter where messages can be published to.

Agent (Sync or Async)

  • The agent is started on the customer’s internal network.
  • The agent establishes a communications tunnel with ICS.
  • Integration Cloud send messages through the tunnel to the Agent.
  • The agent hosts the adapter to communicate to the On-Premises application.

In preparation of my upcoming book about “Implementing Oracle Integration Cloud Service” the further content of this blog is redacted. If you like where this blog is going I can recommend reading the book when finished around October 2016.

packt pre-order

 

About Post Author

Robert van Molken

Robert designs and develops application integration solutions both on-premises and in the cloud. Traditionally the solutions where based on the Oracle Middleware Stack, but lately he advises solutions that use a more cloud-native or hybrid approach. Besides application integration development he is an advocate on Blockchain, IoT and Microservices. Robert is heavily involved in the developer community.He is an international speaker at conferences (CodeOne, TeqNation, Open World), author of two books, blogger, and participates in tech related Podcasts. For this effort Robert was awarded Oracle ACE Associate in 2015, Oracle ACE in 2016, and Developer Champion in 2017 (which was renewed from 2018 to Oracle Groundbreaker Ambassador).
Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

3 thoughts on “Agent for simplifying Integration between Cloud and On-Premises apps

  1. Hi Robert,
    if we use agent on communication between cloud and on-premises , no need to open up inbound ports in the firewall in customer side is that right? it’s a dedicated tunnel for oracle cloud?

Comments are closed.

Next Post

Getting started with the Oracle DB as a Service (DBaaS) Cloud Service

In this article I will tell you how to get up and running with the Oracle Database as a Service Cloud offering. How in 30 minutes of your own time – and up to one hour background processing time – you will have an Oracle Database 12c (12.1.0.2) instance running […]
%d bloggers like this: