System and method for importing and exporting an integration flow in a cloud-based integration platform

Patent metadata

Field	Value
Publication number	US-2016357535-A1
Application number	US-201615174658-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 exporting and importing integration flows in a cloud-based integration service. The cloud-based integration service includes a web interface application for creating an integration flow, and a runtime for executing the integration flow. The web interface application can provide an import interface and an import logic component, and an export interface and an export logic component. The export logic component can be configured to export an integration flow and its dependent resources, regardless of their lock states, and with secured information removed from the dependent resources. The import logic component can be configured to import an integration flow and its dependent resources; and perform a plurality of checks and validations for each dependent resource being imported, to determine whether to create the dependent resource in the system, or keep an existing dependent resource in the system.

First claim

What is claimed is:

1 . A system for exporting and importing integration flows in a cloud-based integration service, comprising:
a computer including one or more microprocessors; and a cloud service, executing on the computer, wherein the cloud service includes a web interface application for creating an integration flow between a source application and a target application, and a runtime for executing the integration flow; wherein the web interface application provides an import interface associated with an import logic component and an export interface associated with an export logic component; wherein the import interface is configured to receive a selection for an integration flow to be imported from a source environment, and perform a plurality of checks and validations for each dependent resource being imported, to determine whether to create a new dependent resource in the system, or retain an existing dependent resource in the system; and wherein the export interface is configured to select an integration flow to be exported to a target environment, and to invoke the export logic component to remove secured information from the integration flow.

2 . The system of claim 1 , wherein the integration flow selected for exporting includes one or more dependent connections, and one or more lookups, and wherein the integration flow itself and the dependent connections and lookups are exported in an archive file.

3 . The system of claim 1 , wherein the integration flow and its dependent sources are exported regardless of their lock states.

4 . The system of claim 1 , wherein the export logic component operates to update the status of any dependent connection in the integration selected for exporting, and percentage complete information of the connection.

5 . The system of claim 1 , wherein the source environment and the target environment are a same environment, wherein the web interface application first exports an integration flow to the same environment to use advanced editing features in the same environment, and then imports the edited integration flow back to the web interface application.

6 . The system of claim 1 , wherein the import logic component detects that the integration flow selected for importing exists in the system and is not locked, and prompts a user to choose whether to overwrite the integration flow.

7 . The system of claim 1 , wherein the import logic component determines that a dependent resource being imported does not exist in the system and is incompatible with the system, and aborts the importing operation, and rolls back any changes.

8 . A method for exporting and importing integration flows in a cloud-based integration service, comprising:
providing a cloud service, executing on a computer including a microprocessor, wherein the cloud service includes a web interface application for creating an integration flow between a source application and a target application, and a runtime for executing the integration flow; providing, in the web interface application, an import interface associated with an import logic component and an export interface associated with an export logic component; receiving, at the import interface, a selection for an integration flow for importing from a source environment, wherein the import interface is configured to perform a plurality of checks and validations for each dependent resource being imported, to determine whether to create the dependent resource or keep an existing dependent resource in the integration cloud service; and receiving, via the export interface, a selection for an integration flow for exporting to a target environment, wherein the export interface is configured to invoke the export logic component to remove secured information from the integration flow.

9 . The method of claim 8 , wherein the integration flow selected for exporting includes one or more dependent connections, and one or more lookups, and wherein the integration flow itself and the dependent connections and lookups are exported in an archive file.

10 . The method of claim 8 , wherein the integration flow and its dependent sources are exported regardless of their lock states.

11 . The method of claim 8 , wherein the export logic component operates to update the status of any dependent connection in the integration selected for exporting, and percentage complete information of the connection.

12 . The method of claim 8 , wherein the source environment and the target environment are a same environment, wherein the web interface application first exports an integration flow to the same environment to use advanced editing features in the same environment, and then imports the edited integration flow back to the web interface application.

13 . The method of claim 8 , wherein the import logic component detects that the integration flow selected for importing exists in the system and is not locked, and prompts a user to choose whether to overwrite the integration flow.

14 . The method of claim 8 , wherein the import logic component determines that a dependent resource being imported does not exist in the system and is incompatible with the system, and aborts the importing operation, and rolls back any changes.

15 . A non-transitory computer-readable storage medium storing a set of instructions for exporting and importing an integration flow, said instructions, when executed by one or more processors, causing the one or more processors to perform the steps comprising:
providing a cloud service, executing on a computer including a microprocessor, wherein the cloud service includes a web interface application for creating an integration flow between a source application and a target application, and a runtime for executing the integration flow; providing, in the web interface application, an import interface associated with an import logic component and an export interface associated with an export logic component; receiving, at the import interface, a selection for an integration flow for importing from a source environment, wherein the import interface is configured to perform a plurality of checks and validations for each dependent resource being imported, to determine whether to create the dependent resource or keep an existing dependent resource in the integration cloud service; and receiving, via the export interface, a selection for an integration flow for exporting to a target environment, wherein the export interface is configured to invoke the export logic component to remove secured information from the integration flow.

16 . The non-transitory computer-readable storage medium of claim 15 , wherein the integration flow selected for exporting includes one or more dependent connections, and one or more lookups, and wherein the integration flow itself and the dependent connections and lookups are exported in an archive file.

17 . The non-transitory computer-readable storage medium of claim 15 , wherein the integration flow and its dependent sources are exported regardless of their lock states.

18 . The non-transitory computer-readable storage medium of claim 15 , wherein the export logic component operates to update the status of any dependent connection in the integration selected for exporting, and percentage complete information of the connection.

19 . The non-transitory computer-readable storage medium of claim 15 , wherein the source environment and the target environment are a same environment, wherein the web interface application first exports an integr

Assignees

• Oracle Int Corp

Inventors

• Gravenites Greg
• Modi Rajan
• Rafique Arif
• Palanisamy Muthu

Classifications

• G06F9/45504

  Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators · CPC title

• G06F8/34

  Graphical or visual programming · CPC title

• G06F8/60 Primary

  Software deployment · CPC title

• G06F8/76

  Adapting program code to run in a different environment; Porting · CPC title