Integration flow execution renew

A system comprising:

• a source system and a target system;
• an integration flow renew module;
• a computer memory storing processor-executable process steps;
• and
• an integration flow renew computer processor coupled to the computer memory, and in communication with the integration flow renew module and operative to execute the processor-executable process steps to cause the system to:
• receive a set of integration steps to transfer data between a first application of the source system and a second application of the target system, wherein the set of integration steps includes execution of at least one component;
• transmit the received set of integration steps to a blueprint generator;
• convert, at the blueprint generator, the received set of integration steps to a binary runtime executable code;
• insert at least two input/output interceptors into the binary runtime executable code;
• receive the binary runtime executable code at a runtime component;
• execute 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:
• receive an update to the data;
• re-generate, at the blueprint generator, the binary runtime executable code for one or more an unexecuted integration steps, wherein re-generation is executed from a point when the at least one incomplete component receives the input update;
• and
• execute the re-generated binary runtime executable code.

A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause the computer system to:

• receive 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;
• transmit the received set of integration steps to a blueprint generator;
• convert, at the blueprint generator, the received set of integration steps to a binary runtime executable code;
• insert at least two input/output interceptors into the binary runtime executable code;
• receive the binary runtime executable code at a runtime component;
• execute 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:
• receive an update to the data;
• re-generate, at the blueprint generator, the binary runtime executable code for one or more an unexecuted integration steps, wherein re-generation is executed from a point when the at least one incomplete component receives the input update;
• and
• execute the re-generated binary runtime executable code.