System and method of suppressing inbound payload to an integration flow of an orchestration based application integration

Patent metadata

Field	Value
Publication number	US-11595299-B2
Application number	US-202016942425-A
Country	US
Kind code	B2
Filing date	Jul 29, 2020
Priority date	Jul 29, 2020
Publication date	Feb 28, 2023
Grant date	Feb 28, 2023

Abstract

Described herein are systems and methods for suppressing inbound payload to an integration flow of an orchestration based application integration. The systems and methods described herein can, based upon a scan of an integration, identify and exclude from memory certain portions of one or more payloads that are received at the integration flow.

First claim

What is claimed is:

1. A system for suppressing inbound payload to an integration flow of an orchestration based application integration, comprising:
a computer including one or more microprocessors;
an integration platform running on the computer; and
a development canvas at the integration platform, wherein the development canvas is utilized, based upon received instructions, to design an integration flow at the integration platform, the integration flow comprising a plurality of connectors in an ordered arrangement, the plurality of connectors being connected within the development canvas with a plurality of mappers, wherein at least one of the plurality of connectors is associated with a property file, wherein each of the plurality of connectors provides a connection to an application, of a plurality of applications, external to the integration flow;
wherein during the design of the integration flow, the integration flow is scanned;
wherein a list of payload elements used within the integration flow is generated as a result of the scan;
wherein a property file of the at least one of the plurality of connectors is updated to reflect the list of payload elements used within the integration flow;
wherein updating the property file comprises writing to the property file one of a list of included payload elements or excluded payload elements;
wherein upon a payload being received at the integration flow, selected portions of the payload are stored in memory associated with the integration platform based upon the updated property file;
wherein the payload is received from an external application of the plurality of external applications;
wherein the scan of the integration flow determines a plurality of elements of the payload received in the integration flow from a call to the external application of the plurality of external applications;
wherein a set of the plurality of elements of the payload are determined not to be used within the integration flow;
wherein the property file comprises a list of excluded payload elements;
wherein the list of excluded payload elements comprises the set of the plurality of elements of the payload from the external application; and
wherein each of the set of the plurality of elements of the payload from the external application are overwritten prior to the payload being used in the integration flow.

2. The system of claim 1 , wherein the payload comprises an Extensible Markup Language (XML) payload.

3. The system of claim 2 , wherein XML Path Language (XPath) elements in the XML payload are evaluated using a document object model.

4. The system of claim 3 , wherein the list of excluded payload elements comprises a list of excluded XPath elements.

5. A method for suppressing inbound payload to an integration flow of an orchestration based application integration, comprising:
providing a computer including one or more microprocessors;
providing an integration platform running on the computer;
providing a development canvas at the integration platform, wherein the development canvas is utilized, based upon received instructions, to design an integration flow at the integration platform, the integration flow comprising a plurality of connectors in an ordered arrangement, the plurality of connectors being connected within the development canvas with a plurality of mappers, wherein at least one of the plurality of connectors is associated with a property file, wherein each of the plurality of connectors provides a connection to an application, of a plurality of applications, external to the integration flow;
during the design of the integration flow, scanning the integration flow;
generating a list of payload elements used within the integration flow as a result of the scan;
updating a property file of the at least one of the plurality of connectors to reflect the list of payload elements used within the integration flow, wherein updating the property file comprises writing to the property file one of a list of included payload elements or excluded payload elements; and
upon a payload being received at the integration flow, selectively storing portions of the payload in memory associated with the integration platform based upon the updated property file;
wherein the payload is received from an external application of the plurality of external applications;
wherein the scan of the integration flow determines a plurality of elements of a payload received in the integration flow from a call to the external application of the plurality of external applications;
wherein a set of the plurality of elements of a payload are determined not to be used within the integration flow;
wherein the property file comprises a list of excluded payload elements;
wherein the list of excluded payload elements comprises the set of the plurality of elements of the payload from the external application; and
wherein each of the set of the plurality of elements of the payload from the external application are overwritten prior to the payload being used in the integration flow.

6. The method of claim 5 , wherein the payload comprises an Extensible Markup Language (XML) payload.

7. The method of claim 6 , wherein XML Path Language (XPath) elements in the XML payload are evaluated using a document object model.

8. The method of claim 7 , wherein the list of excluded payload elements comprises a list of excluded XPath elements.

9. A non-transitory computer readable storage medium, having instructions thereon for suppressing inbound payload to an integration flow of an orchestration based application integration, which when read an executed cause a computer to perform steps comprising:
providing a computer including one or more microprocessors;
providing an integration platform running on the computer;
providing a development canvas at the integration platform, wherein the development canvas is utilized, based upon received instructions, to design an integration flow at the integration platform, the integration flow comprising a plurality of connectors in an ordered arrangement, the plurality of connectors being connected within the development canvas with a plurality of mappers, wherein at least one of the plurality of connectors is associated with a property file, wherein each of the plurality of connectors provides a connection to an application, of a plurality of applications, external to the integration flow;
during the design of the integration flow, scanning the integration flow;
generating a list of payload elements used within the integration flow as a result of the scan;
updating a property file of the at least one of the plurality of connectors to reflect the list of payload elements used within the integration flow, wherein updating the property file comprises writing to the property file one of a list of included payload elements or excluded payload elements; and
upon a payload being received at the integration flow, selectively storing portions of the payload in memory associated with the integration platform based upon the updated property file;
wherein the payload is received from an external application of the plurality of external applications;
wherein the scan of the integration flow determines a plurality of elements of a payload received in the integration flow from a call to the external application of the plurality of external applications;
wherein a set of the plurality of elements of a payload are determined not to be used within the integration flow;
wherein the property file comprises a list of excluded payload elements;
wherein the list of excluded payload elements comprises the set of the plurality of elements of the payload from the external application; and
wherein e

Assignees

• Oracle Int Corp

Inventors

• Devta Prakash Kumar
• Deshpande Sandeep
• Misra Srimant

Classifications

• H04L45/38 Primary

  Flow based routing · CPC title

• H04L47/30

  in combination with information about buffer occupancy at either end or at transit nodes · CPC title

• H04L45/745

  Address table lookup; Address filtering · CPC title

• G06F9/541

  via adapters, e.g. between incompatible applications · CPC title

• G06F8/36

  Software reuse · CPC title