# US 2019/0356760 A1 · Data-centric integration modeling

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

- Number: US 2019/0356760 A1
- Document ID: US20190356760A1
- Status: Published application
- Kind: A1
- Application number: 16/531,766
- Filed: 2019-08-05
- Published: 2019-11-21
- Earliest claimed: 2015-03-23
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Daniel Ritter; Jan Bross
- Web page: https://patentgrep.com/patent/US20190356760A1

## CPC

- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 9/00: Arrangements for program control, e.g. control units (program control for peripheral devices G06F13/10)
- G06Q 10/00: Administration; Management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

The present disclosure describes methods, systems, and computer program products for data-centric integration modeling in an application integration system. One computer-implemented method includes receiving, by operation of an integration system, a logic integration program comprising a plurality of logic integration patterns that are defined in a data-centric logic integration language; generating a logical model graph based on the logic integration program, the logical model graph being runtime-independent; converting the logical model graph into a physical model graph, the physical model graph being runtime-specific; and generating logic integration runtime codes executable by the integration system based on the physical model graph.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving, by operation of an integration system, a logic integration program comprising a plurality of logic integration patterns that are defined in a data-centric logic integration language;
generating a logical model graph based on the logic integration program, the logical model graph being runtime-independent;
converting the logical model graph into a physical model graph, the physical model graph being runtime-specific; and
generating logic integration runtime codes executable by the integration system based on the physical model graph.

### Claim 2 (depends on 1)

The method of claim 1, further comprising defining the logic integration program using the data-centric logic integration language for declarative integration programming.

### Claim 3 (depends on 2)

The method of claim 2, wherein defining a logic integration program comprises:
analyzing integration logic represented by the logical model graph; and
adding integration artifacts.

### Claim 4 (depends on 1)

The method of claim 1, wherein the logical model graph comprises one or more annotations defined by the data-centric logic integration language as one or more nodes of the logical model graph.

### Claim 5 (depends on 1)

The method of claim 1, wherein the logical model graph comprises no cycles.

### Claim 6 (depends on 1)

The method of claim 1, wherein converting the logical model graph into the physical model graph comprises:
detecting patterns on the logical model graph; and
performing a rule-based transformation of the patterns on the logical model graph; and
mapping into implementation-specific messaging channels.

### Claim 7 (depends on 6)

The method of claim 6, further comprising optimizing the logical model graph.

### Claim 8

A non-transitory, computer-readable medium storing computer-readable instructions executable by a computer and configured to:
receive a logic integration program comprising a plurality of logic integration patterns that are defined in a data-centric logic integration language;
generate a logical model graph based on the logic integration program, the logical model graph being runtime-independent;
convert the logical model graph into a physical model graph, the physical model graph being runtime-specific; and
generate logic integration runtime codes executable by an integration system based on the physical model graph.

### Claim 9 (depends on 8)

The medium of claim 8, the instructions further executable by the computer and configured to define the logic integration program using the data-centric logic integration language for declarative integration programming.

### Claim 10 (depends on 9)

The medium of claim 9, wherein defining a logic integration program comprises:
analyzing integration logic represented by the logical model graph; and
adding integration artifacts.

### Claim 11 (depends on 8)

The medium of claim 8, wherein the logical model graph comprises one or more annotations defined by the data-centric logic integration language as one or more nodes of the logical model graph.

### Claim 12 (depends on 8)

The medium of claim 8, wherein the logical model graph comprises no cycles.

### Claim 13 (depends on 8)

The medium of claim 8, wherein converting the logical model graph into the physical model graph comprises:
detecting patterns on the logical model graph; and
performing a rule-based transformation of the patterns on the logical model graph; and mapping into implementation-specific messaging channels.

### Claim 14 (depends on 13)

The medium of claim 13, the instructions further executable by the computer and configured to optimize the logical model graph.

### Claim 15

A system, comprising:
a memory;
at least one hardware processor interoperably coupled with the memory and configured to:
receive a logic integration program comprising a plurality of logic integration patterns that are defined in a data-centric logic integration language;
generate a logical model graph based on the logic integration program, the logical model graph being runtime-independent;
convert the logical model graph into a physical model graph, the physical model graph being runtime-specific; and
generate logic integration runtime codes executable by an integration system based on the physical model graph.

### Claim 16 (depends on 15)

The system of claim 15, the processor further configured to define the logic integration program using the data-centric logic integration language for declarative integration programming.

### Claim 17 (depends on 15)

The system of claim 15, wherein defining a logic integration program comprises:
analyzing integration logic represented by the logical model graph; and
adding integration artifacts.

### Claim 18 (depends on 15)

The system of claim 15, wherein the logical model graph comprises one or more annotations defined by the data-centric logic integration language as one or more nodes of the logical model graph.

### Claim 19 (depends on 15)

The system of claim 15, wherein the logical model graph comprises no cycles.

### Claim 20 (depends on 15)

The system of claim 15, wherein converting the logical model graph into the physical model graph comprises:
detecting patterns on the logical model graph;
optimizing the logical model graph; and
performing a rule-based transformation of the patterns on the logical model graph; and mapping into implementation-specific messaging channels.
