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

Patent metadata

Field	Value
Publication number	US-10375189-B2
Application number	US-201615174661-A
Country	US
Kind code	B2
Filing date	Jun 6, 2016
Priority date	Jun 4, 2015
Publication date	Aug 6, 2019
Grant date	Aug 6, 2019

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 in a cloud-based integration service for decoupling a source application producing messages and a target application consuming the messages, the system comprising:
a computer comprising one or more microprocessors;
a cloud service, executing on the computer, wherein the cloud service comprises a web interface application for creating one or more integration flows and wherein the cloud service comprises a runtime for executing the one or more integration flows;
a publishing integration flow associated with the source application, the publishing integration flow permitting the source application producing the messages to publish the messages by pushing the messages from the source application via the publishing integration flow;
a subscribing integration flow associated with the target application, the subscribing integration flow permitting the target application consuming the messages to subscribe to receive the messages via the subscribing integration flow, wherein the publishing integration flow and the subscribing integration flow are created in the web interface application, and wherein the publishing integration flow and the subscribing integration flow are activated for execution in the runtime of the cloud service; and
a messaging service in operative communication with the cloud service, the messaging service operating as a medium between the source and target applications to decouple the source and target applications by:
receiving 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
delivering the one or more messages to the target application from the cloud service through the subscribing integration flow,

wherein the publishing and subscribing integration flows synchronize objects between the source and target applications by:
in response to an object being created in the source application, creating a corresponding object in the target application.

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 the subscribing integration flow is configured to permit one or more additional applications 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 in a cloud-based integration service for decoupling a source application producing messages and a target application consuming the messages, the method comprising:
providing a cloud service on a computer including one or more microprocessors, the cloud service comprising a web interface application for creating integration flows and a runtime for executing the integration flows;
designing, in the web interface application, a publishing integration flow associated with the source application, the publishing integration flow permitting the source application producing the messages to publish the messages by pushing the messages from the source application via the publishing integration flow;
designing, in the web interface application, a subscribing integration flow associated with the target application, the subscribing integration flow permitting the target application consuming the messages to subscribe to receive the messages via the subscribing integration flow;
activating the publishing integration flow and the subscribing integration flow for execution in the runtime of the cloud service;
providing a messaging service in operative communication with the cloud service, the messaging service operating as a medium between the source and target applications to decouple the source and target applications by:
receiving 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
delivering the one or more messages to the target application from the cloud service through the publishing integration flow; and

synchronizing objects between the activated source and target applications by the publishing and subscribing integration flows by:
in response to an object being created in the activated source application, creating a corresponding object in the activated target application.

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 the subscribing integration flow is configured to permit one or more additional applications 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 in a cloud-based integration service a source application producing messages and a target application consuming the messages, said set of 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 comprising a web interface application for creating integration flows and a runtime for executing the integration flows;
designing, in the web interface application, a publishing integration flow associated with the source application, the publishing integration flow permitting the source application producing the messages to publish the messages by pushing the messages from the source application via the publishing integration flow;
designing, in the web interface application, a subscribing integration flow associated with target application, the subscribing integration flow permitting the target applica

Assignees

• Oracle Int Corp

Inventors

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

Classifications

• H04L67/26 Primary

  Electricity · mapped topic

• H04L67/55 Primary

  Push-based network services · CPC title