Glossary/Terminology
The (English) names and designations that can be found in various places in the IGUASU product and documentation are defined here.
General |
|
Flow |
The definition of an executable, directed graph. This can contain various Processors, connections etc. and can also extend over several Process Groups. A flow can be created via a Process Group |
Diagram |
The left-hand area of the IGUASU user interface in which flows are created. |
Diagram |
|
Modules |
All elements that can be used in diagrams. |
Process Group |
The Process Group is a grouping element that can contain all modules of a diagram (including other Process Groups). |
Processor |
The Processor is the element on which the specific logic takes place. There are various Processor types for different tasks such as filling a database, calling an HTTP endpoint or converting an XML into a JSON. |
Input Port |
Defines an entry point into a Process Group |
Output Port |
Defines an entry point into a Process Group |
Label |
Element via which Notes and frames can be created in the Diagram |
Connection |
A connection between two modules in the Diagram |
Funnel |
The Funnel is used to merge connections. It can also be used as a "dead end" when developing flows, e.g. if you want to execute failure connections without completing the processing at that moment. |
Status History |
Can be selected in the Diagram to obtain graphical histograms of past executions at the Processors and Process Groups. |
Relationship |
The outputs that a Processor can have - in the Diagram these become Connections |
Configuration |
|
Config |
The Config panel shows the configuration of the module selected in the Diagram. The most extensive configurations are in the Processor - these are also different for each Processor. |
Settings |
Settings are below the Config panel. All modules except the Funnels have settings. |
Properties |
Properties are below the Config panel and are only available for Processors. Each Processor type has different properties. |
Dynamic Property |
Some Processors and Services allow the use of dynamically added Processors. |
State |
Is only available for some Processors that hold a state across executions. |
Data |
The Data Panel is only available for Processors. Data (FlowFiles with their attributes and content) from past executions can be displayed in the data panel. Entries can also be made here, which are then used for the local test execution of Processors. |
Data |
|
FlowFile |
The FlowFile refers to the data that flows through the flow. |
FlowFile Attributes |
The attributes - i.e. name/value pairs that act as metadata. Some attributes, such as a UUID, always exist, others can be set by the Processors as required. |
FlowFile Content |
The data attached to a FlowFile, e.g. JSON, CSV, a binary image, etc. |
Other components |
|
Service |
Each Process Group can contain any number of Services. Services are used by Processors to combine common functionality. This could be, for example, a database pool for database Processors or an SSL service for HTTP-based Processors. |
Parameter |
Parameters are recorded centrally in Parameter Contexts and then used from the flows at the properties of the Processors and Services. Generic flows can be parameterized via this. This is also useful for staging. |
Reporting Tasks |
Provide a way to process metrics about the system and the executions or to make them available for other systems. |
Bulletins |
Represent messages from Processors and Services. This is particularly important if there are ERRORs. Whether Bulletins are generated depends on which 'Bulletin Level' has been configured on the component. |
Process execution data |
|
Provenance |
Diagram can be switched on. If you then select a Processor, a table of the associated events is displayed. If you select one of the events, the Data Panel shows which data (FlowFile) was processed here. If activated, in addition to this list, the complete processing of this flow with the modules and connections that have been flowed through is colored blue. |
Event |
Events are generated when Processors are executed. For example, when a remote system is called. When selecting such an event, you can see the data that has flowed in the Data Panel. |
Execution sequence |
The representation of the execution of a flow in the Diagram. All strands that have been run through are displayed. This is done by coloring Processors and connections blue. |