# US 2023/0067833 A1 · Integrating applications using containerized integration flow

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0067833 A1
- Document ID: US20230067833A1
- Status: Published application
- Kind: A1
- Application number: 17/464,277
- Filed: 2021-09-01
- Published: 2023-03-02
- Earliest claimed: 2021-09-01
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Sherwin Varghese
- Web page: https://patentgrep.com/patent/US20230067833A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 3/0486: Drag-and-drop
- G06F 8/34: Graphical or visual programming
- G06F 8/63: {Image based installation; Cloning; Build to order}
- G06F 9/455: Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F 2209/541: Client-server
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques for integrating applications using a container image of an integration flow are disclosed. In some embodiments, a computer system performs operations comprising: providing a low-code no-code (LCNC) development platform to a computing device, the LCNC development platform being configured to enable a user to develop an integration flow; receiving a configuration of the integration flow from the computing device via the LCNC development platform, the integration flow being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system; building a container image of the integration flow based on the configuration of the integration flow, the container image being configured to execute the integration flow; and deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application.

## Claims

### Claim 1

A system of comprising:
at least one hardware processor; and
a non-transitory computer-readable medium storing executable instructions that, when executed, cause the at least one processor to perform operations comprising:
providing a low-code no-code (LCNC) development platform to a computing device, the LCNC development platform being configured to enable a user of the computing device to develop an integration flow by using a graphical user interface (GUI) of the LCNC development platform to drag and drop components of the integration flow;
receiving a configuration of the integration flow from the computing device via the LCNC development platform, the integration flow being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system;
building a container image of the integration flow based on the configuration of the integration flow, the container image being configured to execute the integration flow; and
deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first system has a first data model and the second system has a second data model that is different from the first data model.

### Claim 3 (depends on 1)

The system of claim 1, wherein the building the container image of the integration flow comprises generating a Java Archive (JAR) file.

### Claim 4 (depends on 1)

The system of claim 1, wherein the first application comprises an on-premise application being hosted on an on-premise system and the second application comprises a cloud application being hosted on a cloud system.

### Claim 5 (depends on 1)

The system of claim 1, wherein the first application comprises a first on-premise application being hosted on a first on-premise system and the second application comprises a second on-premise application being hosted on a second on-premise system.

### Claim 6 (depends on 1)

The system of claim 1, wherein the first application comprises a first cloud application being hosted on a first cloud system and the second application comprises a second cloud application being hosted on a second cloud system.

### Claim 7 (depends on 1)

The system of claim 1, wherein the operations further comprise running the container image of the integration flow on the second system.

### Claim 8 (depends on 7)

The system of claim 7, wherein the running the container image of the integration flow comprises:
mapping the on-premise application to the second application;
setting an authorization to enable the second system to obtain a payload of a request from the first application;
converting the payload of the request from a first data format of the first application to a second data format of the second application; and
performing a network call to the second application using the converted payload of the request.

### Claim 9

A computer-implemented method performed by a computer system having a memory and at least one hardware processor, the computer-implemented method comprising:
providing a low-code no-code (LCNC) development platform to a computing device, the LCNC development platform being configured to enable a user of the computing device to develop an integration flow by using a graphical user interface (GUI) of the LCNC development platform to drag and drop components of the integration flow;
receiving a configuration of the integration flow from the computing device via the LCNC development platform, the integration flow being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system;
building a container image of the integration flow based on the configuration of the integration flow, the container image being configured to execute the integration flow; and
deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein the first system has a first data model and the second system has a second data model that is different from the first data model.

### Claim 11 (depends on 9)

The computer-implemented method of claim 9, wherein the building the container image of the integration flow comprises generating a Java Archive (JAR) file.

### Claim 12 (depends on 9)

The computer-implemented method of claim 9, wherein the first application comprises an on-premise application being hosted on an on-premise system and the second application comprises a cloud application being hosted on a cloud system.

### Claim 13 (depends on 9)

The computer-implemented method of claim 9, wherein the first application comprises a first on-premise application being hosted on a first on-premise system and the second application comprises a second on-premise application being hosted on a second on-premise system.

### Claim 14 (depends on 9)

The computer-implemented method of claim 9, wherein the first application comprises a first cloud application being hosted on a first cloud system and the second application comprises a second cloud application being hosted on a second cloud system.

### Claim 15

A non-transitory machine-readable storage medium tangibly embodying a set of instructions that, when executed by at least one hardware processor, causes the at least one processor to perform operations comprising:
providing a low-code no-code (LCNC) development platform to a computing device, the LCNC development platform being configured to enable a user of the computing device to develop an integration flow by using a graphical user interface (GUI) of the LCNC development platform to drag and drop components of the integration flow;
receiving a configuration of the integration flow from the computing device via the LCNC development platform, the integration flow being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system;
building a container image of the integration flow based on the configuration of the integration flow, the container image being configured to execute the integration flow; and
deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application.

### Claim 16 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the first system has a first data model and the second system has a second data model that is different from the first data model.

### Claim 17 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the building the container image of the integration flow comprises generating a Java Archive (JAR) file.

### Claim 18 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the first application comprises an on-premise application being hosted on an on-premise system and the second application comprises a cloud application being hosted on a cloud system.

### Claim 19 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the first application comprises a first on-premise application being hosted on a first on-premise system and the second application comprises a second on-premise application being hosted on a second on-premise system.

### Claim 20 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the first application comprises a first cloud application being hosted on a first cloud system and the second application comprises a second cloud application being hosted on a second cloud system.
