Integration Flow Renew Checkpoint Interceptors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud integration failures often occur unpredictably during data processing, leading to significant time and effort in rectification, especially when dealing with large volumes of data, as conventional methods require re-processing from the beginning after identifying and correcting errors.

Innovation Solution

The Integration Flow Renew module inserts interceptors into executable code to identify failure points, allowing targeted corrections and re-execution from the point of failure, rather than from the start, thereby reducing the effort and time required to rectify integration issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional integration failure rectification methods are used, then the integration flow can be corrected, but significant time and effort are required to re-process all records from the beginning

Engineering Contradiction:
Improveintegration flow completionVSAvoidtime to rectify and re-process
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by saving executable code and data at multiple checkpoints during integration flow execution. When a failure occurs, these pre-saved states enable the system to resume from the last successful checkpoint rather than restarting from the beginning, significantly reducing rectification time while ensuring reliable completion.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The integration flow is segmented into discrete executable steps with saved states at each checkpoint. This segmentation allows the system to identify exactly where a failure occurred and resume processing from that specific point, rather than treating the entire integration flow as a single unit that must be re-executed in its entirety.

Inventive Principle:
Principle #1Segmentation

2Productivity

If integration flow execution is monitored to identify failure points, then re-processing can start from the point of failure, but additional complexity is introduced through interceptors and checkpoint mechanisms

Engineering Contradiction:
Improverectification speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces intermediary components (interceptors and checkpoint mechanisms) that mediate between the integration flow execution and the failure detection/resume functionality. These intermediaries capture execution states and facilitate seamless resumption without requiring complex manual intervention, thereby improving productivity while managing complexity through structured intermediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11442758B2Integration flow execution renew
Publication Date: 2022.09.13 SAP SE
  • US11442758B2 patent drawing
  • US11442758B2 patent drawing
  • US11442758B2 patent drawing

AI summary

A method and system including receiving a set of integration steps to transfer data between a first application and a second application, wherein the set of integration steps includes execution of at least one component; transmitting the received set of integration steps to a blueprint generator; converting, at the blueprint generator, the received set of integration steps to a binary runtime executable code; inserting at least two input/output interceptors into the binary runtime executable code; receiving the binary runtime executable code at a runtime component; executing the received binary runtime executable code at the runtime component using data, in a case that execution of the at least one component is complete, an output of the executed at least one component is saved; in a case that execution of the at least one component is incomplete: receiving an update to the data; re-generating, at the blueprint generator, the binary runtime executable code for one or more an unexecuted integration steps; and executing the re-generated binary runtime executable code. Numerous other aspects are provided.