WebMethods Flow: Difference between revisions

Revision as of 13:47, 15 November 2021

Revision as of 19:58, 1 February 2022

Line 27:

The main driver behind flow syntax was to allow the graphical configuration of the mapping logic that forms the major part of Integration projects. Transformation and conversion of data in a text based programming language quickly becomes unwieldy and cluttered. It is also quite difficult to maintain due to the cumbersome nature. Flow code seeks to alleviate this problem by creating a programming language similar to the way you would indicate mapping of data if your source and destination data formats were placed side by side on a white board and lines connecting source to destination.

The other goal of flow was to allow a service based view of the application. Any existing code is a service. Invoking functionality is akin to treating it as a "[[black box]]" requiring certain inputs (which are mapped from your available variables). The results of that operation are then treated as outputs of the "black box". The concept of the "pipeline" is the means by which to pass data to and get results back from invocation of services.<ref name="wmPipelineExplained">[http://www.jroller.com/page/nathan?entry=webmethods_pipeline_variable_passing_and explanation of the webMethods pipeline]</ref>

==Syntax==

There are the following operators in the flow language:<ref name="wmIntroToFlow">[http://www.jroller.com/page/nathan?entry=intro_to_webmethods_flow Nathan's Intro to webMethods Flow]</ref>

* Map

* Invoke