webMethods Flow

webMethods Flow
Paradigm Object-oriented, structured, graphical
Designed by webMethods
First appeared 1990s
OS Cross-platform
License commercial
Website http://www.softwareag.com/
Major implementations
webMethods Integration Server
Influenced by
Java, flow charts

webMethods Flow (known as "flow code" or simply "flow") is a graphical programming language[1] that runs within the webMethods Integration Server. It was designed to simplify tedious, difficult to maintain or error prone aspects of integration/B2B activities.[2]

The Software AG Designer is the IDE in which to write flow code.

History

webMethods developed flow as a technology to increase the ease and speed of development on their B2B/enterprise integration platform. A language that would be a suitable fit with the desire for a service based application server was another driving force.

Philosophy

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.[3]

Syntax

There are the following operators in the flow language:[4]

The operators are stored on disk as XML but this is not generally edited directly, rather the IDE (webMethods Developer) is used.[5]

Advantages

Criticisms

See also

References

  1. webMethods Flow code mapping screenshot
  2. WebMethods Business Integration – Detailed Features
  3. explanation of the webMethods pipeline
  4. Nathan's Intro to webMethods Flow
  5. Vishal KHAPRE on webmethods file structure

External links

This article is issued from Wikipedia - version of the Monday, February 08, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.