components

Components

The following table shows a list of available components.

Icon	Name	Use When
Readers
	File Poller	A file based resource needs to be checked for the existence of a file or set of files
	[text-file-reader]	Data needs read from a text file
	[xml-reader]	An XML file needs to be read and element content of that file sent as individual messages
	[unzip]	A compressed zip file needs to be extracted in order to process its content
	[rdbms-reader]	Data needs read from a relational database
	[text-constant]	A text constant is needed in message content in the flow
Processors
	[call-flow]	A flow needs to be called from another flow
	[content-router]	Content within a message needs to be routed to different downstream components in the existing flow
	[data-diff]	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
	[deduper]	Input model based records must be deduplicated before being sent to downstream components
	[delay]	A delay is needed when sending data between components
	[execute]	There is a need to execute an operating system command as part of a flow
	[file-util]	Files need to be renamed, copied, moved or deleted
	[format-delimited]	Model based data needs to be formatted into delimited text
	[format-fixed]	Model based data needs to be formatted into fixed length text
	[format-xml]	Model based data needs to be formatted into xml text
	[merger]	Different instances of model based records need to be merged into a single instance that combines the attributes from all instances.
	[lookup]	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.
	[mapping]	Data needs to be mapped from one set of entities/attributes (model structure) to another set of entities/attributes
	[message-logger]	Messages need to be logged to the Metl console and log file
	[multiplier]	Inbound messages need to be multiplied (duplicated n number of times) and the sent to downstream components.
	[no-op]	A message needs to be passed through to another component without any action being taken on the message
	[parse-delimited]	An inbound text message in some delimited text format needs to be parsed into a model based message structure
	[parse-fixed]	An inbound text message in a fixed length text format needs to be parsed into a model based message structure
	[parse-xml]	An inbound text message in xml text format needs to be parsed into a model based message structure
	[script]	A custom action should be performed that can be written using Groovy
	[sequence]	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.
	[sorter]	Data within a model based message needs to be sorted by one of the attributes within the model
	[text-replace]	A piece of text in a text based message needs replaced with alternate text
	[transformer]	An attribute in a model based message needs transformed in one way or another (trim, substring, constants, etc.)
	[union]	Inbound messages need to be combined into a single message and then sent to downstream components.
	[web]	A web service (either REST or WSDL) needs to be called to perform an action such as retrieving or writing data
	[xslt-processor]	XSLT needs applied to a set of input data in order to transform it into a given output format
Writers
	[rdbms-writer]	Data needs written to a relational database
	[sql-executor]	Data needs written to or deleted from a database using a specific sql statement
	[text-file-writer]	Data needs written to a text based file
	[zip]	Data needs to be put in a compressed file
Controls
	[gate]	Flow needs controlled by one input before remaining process continues
	[last-unit-of-work]	Flow needs to be held at this point until all inputs complete before continuing