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

Patent metadata

Field	Value
Publication number	US-10324697-B2
Application number	US-201615174658-A
Country	US
Kind code	B2
Filing date	Jun 6, 2016
Priority date	Jun 4, 2015
Publication date	Jun 18, 2019
Grant date	Jun 18, 2019

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;
invoke the import logic component to perform a plurality of checks and validations for a dependent resource of the integration flow to be imported, to determine based on a presence of the dependent resource of the integration flow to be imported as an existing resource in the system whether to create the dependent resource of the integration flow to be imported as a new dependent resource in the system, or retain an existing dependent resource in the system; and
invoke the import logic component to selectively create the new dependent resource in the system or retain the existing resource in the system,

wherein the export interface is configured to:
select an integration flow to be exported to a target environment;
invoke the export logic component to write the selected integration flow to an archive file;
invoke the export logic component to determine whether the selected integration flow to be exported comprises a dependent connection or a dependent lookup;
invoke the export logic component to selectively write the dependent connection to the archive file based on the export logic component determining selected integration flow to be exported comprises the dependent connection;
invoke the export logic component to selectively write the dependent lookup to the archive file based on the export logic component determining selected integration flow to be exported comprises the dependent lookup; and
invoke an export updater of the export logic component to selectively update a status of the dependent connection based on the export logic component determining selected integration flow to be exported comprises the dependent connection.

2. The system of claim 1 , wherein the export interface is configured to:
invoke the export logic component to:
select to be exported to the target environment an integration flow comprising one or more dependent connections, and one or more lookups; and
export the selected integration flow together with the dependent connections and the lookups to the archive file.

3. The system of claim 1 , wherein the export interface is configured to:
invoke the export logic component to:
export the integration flow to be exported and its dependent sources regardless of lock states of the dependent resources.

4. The system of claim 1 , wherein the export interface is configured to:
invoke the export logic component to update a status of any dependent connection in the integration flow to be exported; and
invoke the export updater to update the status of the dependent connection as percentage complete information of the dependent connection.

5. The system of claim 1 , wherein:
the source environment and the target environment are a same environment;
the export interface of the web interface application is configured to invoke the export logic to export an integration flow to be edited to the same environment to use advanced editing features on the integration flow to be edited in the same environment as an edited integration flow; and
the import interface of the web interface application is configured to invoke the import logic component to import the edited integration flow back to the web interface application.

6. The system of claim 1 , wherein the import interface of the web interface application is configured to invoke the import logic component to detect that the integration flow selected for importing exists in the system and is not locked, and prompt a user to choose whether to overwrite the integration flow.

7. The system of claim 1 , wherein the import interface of the web interface application is configured to invoke the import logic component to:
determine that a dependent resource being imported is incompatible with the system;
abort importing the integration flow to be imported based on the dependent resource being incompatible with the system; and
roll back any changes made in the system relative to the dependent resource being imported based on the dependent resource being incompatible with the system.

8. A method for exporting and importing integration flows in a cloud-based integration service, the method comprising:
providing a cloud service, executing on a computer comprising a microprocessor, wherein the cloud service comprises 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 to be imported from a source environment;
invoking the import logic to perform a plurality of checks and validations for a dependent resource of the integration flow to be imported, to determine based on a presence of the dependent resource of the integration flow to be imported as an existing resource in the system whether to create the dependent resource of the integration flow to be imported as a new 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 write the selected integration flow to an archive file;
invoke the export logic component to determine whether the selected integration flow to be exported comprises a dependent connection or a dependent lookup;
invoke the export logic component to selectively write the dependent connection to the archive file based on the export logic component determining selected integration flow to be exported comprises the dependent connection;
invoke the export logic component to selectively write the dependent lookup to the archive file based on the export logic component determining selected integration flow to be exported comprises the dependent lookup; and
invoke an export updater of the export logic component to selectively update a status of the dependent connection based on the export logic component determining selected integration flow to be exported comprises the dependent connection.

9. The method of claim 8 , wherein the export interface is configured to:
invoke the export logic component to:
select to be exported to the target environment an integration flow comprising one or more dependent connections, and one or more lookups; and
export the selected integration flow together with the dependent connections and the lookups to the archive file.

10. The method of claim 8 , wherein the export interface is configured to:
invoke the export logic component to:
export the integration flow to be exported and its dependent sources regardless of lock states of the dependent resources.

11. The method of claim 8 , wherein the export interface is configured to:
invoke the

Assignees

• Oracle Int Corp

Inventors

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

Classifications

• G06F8/60 Primary

  Software deployment · CPC title

• G06F8/34

  Graphical or visual programming · CPC title

• G06F9/45504

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