System and method for decoupling a source application from a target application in an integration cloud service

Patent metadata

Field	Value
Publication number	US-2016359964-A1
Application number	US-201615174661-A
Country	US
Kind code	A1
Filing date	Jun 6, 2016
Priority date	Jun 4, 2015
Publication date	Dec 8, 2016
Grant date	—

Abstract

In accordance with an embodiment, described herein is a system and method for decoupling a source application and a target application using a messaging service associated with a cloud-based integration service. A first integration flow can be provided to enable the source application or producer to publish messages to the messaging service. A second integration flow can be provided to enable the target application or consumer to subscribe to the messaging service to receive messages. The source application and the target application can be agnostic of each other's implementation details, and those of the messaging service, which effectively decouples the source and target applications. The system enables objects between the source and target applications to be sychronized, multiple applications to subscribe to the integration cloud service and register for updates, and one or more applications to be added or removed as subscribers without affecting other subscribers or producers.

First claim

What is claimed is:

1 . A system for decoupling a source application and a target application in a cloud-based integration service, comprising:
a computer including one or more microprocessors; a cloud service, executing on the computer, wherein the cloud service includes a web interface application for creating integration flows and a runtime for executing the integration flows, and is configured to communicate with a messaging service; a publishing integration flow associated with a source application, and a subscribing integration flow associated with a target application, wherein the publishing integration flow and the subscribing integration flow are created in the web interface application, and activated for execution in the runtime of the cloud service; wherein the messaging service operates to
receive one or more messages asynchronously pushed from the source application to the cloud service through the publishing integration flow,
map fields of each of the one or more messages to a data format of the target application, and
asynchronously push the one or more messages to the target application from the cloud service through the subscribing integration flow.

2 . The system of claim 1 , wherein the publishing integration flow publishes the one or more messages from the source application to the cloud service through the messaging service using representational state transfer (REST) or simple object access (SOAP) protocols.

3 . The system of claim 1 , wherein the subscribing integration flow subscribes to the cloud service through the messaging service using representational state transfer (REST) or simple object access (SOAP) protocols.

4 . The system of claim 1 , wherein an object created in the source application causes a creation of a corresponding object in the target application.

5 . The system of claim 1 , wherein the source application and the target application are agnostic of each other's implementation details, and those of the messaging service.

6 . The system of claim 1 , wherein one or more additional applications are configured to subscribe to the cloud service through the messaging service to receive the one or more messages published by the source application.

7 . The system of claim 1 , wherein one or more applications are configured to be added or removed as subscribers without impacting other subscribers or producers.

8 . A method for decoupling a source application and a target application in a cloud-based integration service, comprising:
providing a cloud service on a computer including one or more microprocessors, the cloud service including a web interface application for creating integration flows and a runtime for executing the integration flows, and configured to communicate with a messaging service; designing, in the web interface application, a publishing integration flow associated with a source application, and a subscribing integration flow associated with a target application; activating the publishing integration flow and the subscribing integration flow for execution in the runtime of the cloud service; receiving, via the messaging service, one or more messages asynchronously pushed from the source application to the cloud service through the publishing integration flow; mapping fields of each of the one or more messages to a data format of the target application; and asynchronously pushing the one or more messages to the target application from the cloud service through the publishing integration flow.

9 . The method of claim 8 , wherein the publishing integration flow publishes the one or more messages from the source application to the cloud service through the messaging service using representational state transfer (REST) or simple object access (SOAP) protocols.

10 . The method of claim 8 , wherein the subscribing integration flow subscribes to the cloud service through the messaging service using representational state transfer (REST) or simple object access (SOAP) protocols.

11 . The method of claim 8 , wherein an object created in the source application causes a creation of a corresponding object in the target application.

12 . The method of claim 8 , wherein the source application and the target application are agnostic of each other's implementation details, and those of the messaging service.

13 . The method of claim 8 , wherein one or more additional applications are configured to subscribe to the cloud service through the messaging service to receive the one or more messages published by the source application.

14 . The method of claim 8 , wherein one or more applications are configured to be added or removed as subscribers without impacting other subscribers or producers.

15 . A non-transitory computer-readable storage medium storing a set of instructions for decoupling a source application and a target application in a cloud-based integration service, said instructions, when executed by one or more processors, causing the one or more processors to perform the steps comprising:
providing a cloud service on a computer including one or more microprocessors, the cloud service including a web interface application for creating integration flows and a runtime for executing the integration flows, and configured to communicate with a messaging service; designing, in the web interface application, a publishing integration flow associated with a source application, and a subscribing integration flow associated with a target application; activating the publishing integration flow and the subscribing integration flow for execution in the runtime of the cloud service; receiving, via the messaging service, one or more messages asynchronously pushed from the source application to the cloud service through the publishing integration flow; mapping fields of each of the one or more messages to a data format of the target application; and asynchronously pushing the one or more messages to the target application from the cloud service through the publishing integration flow.

16 . The non-transitory computer-readable storage medium of claim 15 , wherein the publishing integration flow publishes the one or more messages from the source application to the integration cloud service through the messaging service using representational state transfer (REST) or simple object access (SOAP) protocols.

17 . The non-transitory computer-readable storage medium of claim 15 , wherein the subscribing integration flow subscribes to the integration cloud service through the messaging service using representational state transfer (REST) or simple object access (SOAP) protocols.

18 . The non-transitory computer-readable storage medium of claim 15 , wherein an object created in the source application causes a creation of a corresponding object in the target application.

19 . The non-transitory computer-readable storage medium of claim 15 , wherein the source application and the target application are agnostic of each other's implementation details, and those of the messaging service.

20 . The non-transitory computer-readable storage medium of claim 15 , wherein one or more additional applications are configured to subscribe to the integration cloud service through the messaging service to receive the one or more messages published by the source application.

Assignees

• Oracle Int Corp

Inventors

• Modi Rajan
• Raheja Rajesh
• Gravenites Greg
• Stiel Herb

Classifications

• H04L67/1042 Primary

  using topology management mechanisms · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/55 Primary

  Push-based network services · CPC title