System and method for automated generation of integration elements modeling process flow for an integration process with a swagger API
An information handling system a processor receiving an open-standard format file describing code instructions of a Swagger custom API, the processor parsing the file to identify a first Swagger parameter object whose location is defined by a first Swagger path object, a memory for storing a first Swagger operation object and for storing a customized software integration application enabling electronic data exchange comprising a plurality of connector code sets, each of the connector code sets being associated with an integration modeling element selected to generate a customized integration flow model of the specific integration process, wherein the integration modeling element selected is a custom connector integration element associated with a custom connector code sets including the first Swagger operation object acting on the first Swagger parameter object, and the processor transmitting an executable run-time engine and the custom connector code set for execution at an execution location.
1. An information handling system operating a swagger connector integration element generation system comprising:
a processor executing code instructions of a customized data integration software application creation system for visually modelling and generating code for a visually modelled business integration process to conduct bi-directional exchange of data between internal applications of an enterprise, between internal enterprise applications and external trading partners, or between internal enterprise applications and applications running external to the enterprise;
the processor receiving instructions from a user via a graphical user interface for inserting a custom Swagger connector visual element into the visually modelled business integration process;
the processor receiving an open-standard format file for human-readable, machine-executable code instructions of a Swagger custom application platform interface (API) adhering to a Swagger API open source specification;
the processor parsing the open-standard format file to identify a plurality of Swagger parameter objects and a plurality of Swagger path objects, based on syntax schemes defined by the Swagger API open source specification;
the processor receiving a user-selected first Swagger path object from the plurality of Swagger path objects, a user-selected first Swagger parameter object from the plurality of Swagger path objects, and a user-selected first Swagger operation object from a stored plurality of Swagger operation objects;
the processor generating a custom connector code set associated with the custom Swagger connector visual element, the custom connector code set instructing the Swagger custom API to perform an action defined by the user-selected first Swagger operation object on the user-selected first Swagger parameter object within the visually modelled business integration process;
wherein performing the action includes adding the custom connector code into the integration process flow diagram and prompting the user to keep or change the user selected first Swagger operation object or the user-selected first Swagger parameter object; and
the processor transmitting an executable run-time engine and the custom connector code set for execution of the visually modelled business integration process at an execution location.
2. The information handling system of claim 1 , wherein a location of each of the plurality of Swagger parameter objects is defined by one of the plurality of Swagger path objects further comprising: the processor generating a connector import wizard user-interface allowing a user to choose the user-selected first Swagger path object from the plurality of Swagger path objects.
3. The information handling system of claim 2 , wherein the connector import wizard user-interface allows a user to choose the user-selected first Swagger parameter object from the plurality of Swagger parameter objects.
4. The information handling system of claim 1 further comprising: the processor generating a connector import wizard user-interface allowing a user to choose the user-selected first Swagger operation object from the stored plurality of Swagger operation objects.
5. The information handling system of claim 1 , wherein the open-standard format file adheres to the Extended Markup Language (XML) open-standard format.
6. The information handling system of claim 1 , wherein the syntax scheme defines a format for identifying each of the plurality of Swagger path objects.
7. The information handling system of claim 1 , wherein the user-selected first Swagger parameter object is a Swagger path-parameter object.
8. A method of executing a customized software integration application comprising:
executing code instructions of a customized data integration software application creation system, via a processor, for visually modelling and generating code for a visually modelled business integration process to conduct bi-directional exchange of data between internal applications of an enterprise, between internal enterprise applications and external trading partners, or between internal enterprise applications and applications running external to the enterprise;
receiving instructions from a user, via a graphical user interface, for inserting a custom Swagger connector visual element into the visually modelled business integration process;
receiving via a processor an open-standard format file for human-readable, machine-executable code instructions of a Swagger custom application platform interface (API) adhering to a Swagger API open source specification to be associated with the custom Swagger connector visual element;
parsing via a processor the open-standard format file to identify a plurality of Swagger parameter objects and a plurality of Swagger path objects, based on syntax schemes defined by the Swagger API open source specification;
generating a connector import wizard user-interlace for customizing the custom Swagger connector visual element allowing the user to select a user-selected first Swagger parameter object from the plurality of Swagger parameter objects, and for the user to select a user-selected first Swagger operation object from a stored plurality of Swagger operation objects;
generating, a custom connector code set associated with the custom Swagger connector visual element, the custom connector code set instructing the Swagger custom API to perform an action defined by the user-selected first Swagger operation object on the user-selected first Swagger parameter object within the visually modelled business integration process;
wherein performing the action includes adding the custom connector code into the integration process flow diagram and prompting the user to keep or change the user-selected first Swagger operation object or the user-selected first Swagger parameter object; and
transmitting an executable run-time engine, and the custom connector code set for execution of the visually modelled business integration process at an execution location.
9. The method of claim 8 , wherein a location of each of the plurality of Swagger parameter objects is defined by one of the plurality of Swagger path objects, and the connector import wizard user-interface allows the user to choose a user-selected Swagger path object from the plurality of Swagger path objects, further comprising: transmitting the user-selected Swagger path object for execution.
10. The method of claim 8 , wherein the open-standard format file adheres to the JavaScript Object Notation (JSON) open-standard format.
11. The method of claim 8 , wherein the user-selected Swagger parameter object is a Swagger header parameter object.
12. The method of claim 8 , wherein the user-selected Swagger parameter object is a Swagger body parameter object.
13. The method of claim 8 , wherein the user-selected Swagger parameter object is a Swagger form parameter object.
14. The method of claim 8 , wherein the user-selected Swagger parameter object is a Swagger path-parameter object.
15. An information handling system operating a Swagger connector integration element generation system comprising:
a processor executing code instructions of a customized data integration software application creation system for visually modelling and generating code for a visually modelled business integration process to conduct bi-directional exchange of data between internal applications of an enterprise, between internal enterprise applications and external trading partners, or between internal enterprise applications and applications running external to the enterprise;
the processor receiving instructions from a user via a graphical user interface for inserting a custom Swagger connector visual element into the visually modelled business integration process;
the processor receiving a JavaScript object notification format (JSON) file including executable code instructions of a Swagger custom application platform interface (API) adhering to a Swagger API open source specification to be associated with the custom Swagger connector visual element;
the processor parsing the JSON file to identify a plurality of Swagger parameter objects and a plurality of Swagger path objects, based on syntax schemes defined by the Swagger API open source specification;
the processor generating a connector import wizard user-interface for customizing the custom Swagger connector visual element allowing the user to select a user-selected first Swagger parameter object from the plurality of Swagger parameter objects, and for the user to select a user-selected first Swagger operation object from a stored plurality of Swagger operation objects;
the processor generating a custom connector code set associated with the custom Swagger connector visual element, the custom connector code set instructing the Swagger custom API to perform an action defined by the user-selected first Swagger operation object on the user-selected first Swagger parameter object within the visually modelled business integration process;
wherein performing the action includes adding the custom connector code into the integration process flow diagram and prompting the user to keep or change the user-selected first Swagger operation object or the user-selected first Swagger parameter object; and
the processor transmitting an executable run-time engine, and the custom connector code set for execution of the visually modelled business integration process at an execution location.
16. The information handling system of claim 15 , wherein the user-selected Swagger operation object is a Swagger patch operation object.
17. The information handling system of claim 15 , wherein the user-selected Swagger operation object is a Swagger head operation object.
18. The information handling system of claim 15 , wherein the user-selected Swagger operation object is a Swagger options operation object.
19. The information handling system of claim 15 , wherein the user-selected Swagger operation object is a Swagger post operation object.
20. The information handling system of claim 15 , wherein the user-selected Swagger operation object is a Swagger post operation object.