It’s a wrap for the Jumpmind Team at Shoptalk Spring and we could not have …
Icon | Name | Use When |
---|---|---|
Readers |
||
|
A file based resource needs to be checked for the existence of a file or set of files |
|
|
Data needs read from a text file |
|
|
An XML file needs to be read and element content of that file sent as individual messages |
|
|
A compressed zip file needs to be extracted in order to process its content |
|
|
Data needs read from a relational database |
|
|
A text constant is needed in message content in the flow |
|
Processors |
||
|
A flow needs to be called from another flow |
|
|
Content within a message needs to be routed to different downstream components in the existing flow |
|
|
A set of model based data needs compared to another set of model based data in order to generate insert/update/delete instructions for a writer component |
|
|
Input model based records must be deduplicated before being sent to downstream components |
|
|
A delay is needed when sending data between components |
|
|
There is a need to execute an operating system command as part of a flow |
|
|
Files need to be renamed, copied, moved or deleted |
|
|
Model based data needs to be formatted into delimited text |
|
|
Model based data needs to be formatted into fixed length text |
|
|
Model based data needs to be formatted into xml text |
|
|
Different instances of model based records need to be merged into a single instance that combines the attributes from all instances. |
|
|
Reference data exists that needs to be looked up / retrieved by a specified key, and another attribute of the the resulting reference data passed to downstream components. |
|
|
Data needs to be mapped from one set of entities/attributes (model structure) to another set of entities/attributes |
|
|
Messages need to be logged to the Metl console and log file |
|
|
Inbound messages need to be multiplied (duplicated n number of times) and the sent to downstream components. |
|
|
A message needs to be passed through to another component without any action being taken on the message |
|
|
An inbound text message in some delimited text format needs to be parsed into a model based message structure |
|
|
An inbound text message in a fixed length text format needs to be parsed into a model based message structure |
|
|
An inbound text message in xml text format needs to be parsed into a model based message structure |
|
|
A custom action should be performed that can be written using Groovy |
|
|
A sequence number needs to be created for a given attribute in a model based record, and the starting value of the sequence can be derived by an sql statement. |
|
|
Data within a model based message needs to be sorted by one of the attributes within the model |
|
|
A piece of text in a text based message needs replaced with alternate text |
|
|
An attribute in a model based message needs transformed in one way or another (trim, substring, constants, etc.) |
|
|
Inbound messages need to be combined into a single message and then sent to downstream components. |
|
|
A web service (either REST or WSDL) needs to be called to perform an action such as retrieving or writing data |
|
|
XSLT needs applied to a set of input data in order to transform it into a given output format |
|
Writers |
||
|
Data needs written to a relational database |
|
|
Data needs written to or deleted from a database using a specific sql statement |
|
|
Data needs written to a text based file |
|
|
Data needs to be put in a compressed file |
|
Controls |
||
|
Flow needs controlled by one input before remaining process continues |
|
|
Flow needs to be held at this point until all inputs complete before continuing |