Processors
Below is a list of every processor supported by the flow-server. Select a processor name to learn more about how that processor can be configured. Processor properties are implemented in the following manner:
processorName { propertyName = "value" functionName("value") subBuilderName { propertyName = "value" } }
The descriptions within these pages are also available directly in your IDE. If you are using IntelliJ IDEA, and the "Show quick documentation on hover" setting is checked, you can hover over any processor or property name to see its description. |
Amazon Web Services
Name | Summary |
---|---|
Processor that writes payloads to an AWS S3 bucket. |
|
Processor that looks up an object from an AWS S3 bucket. |
|
Source processor that polls an AWS S3 bucket according to the specified poll configuration. |
Archiving and Resubmission
Name | Summary |
---|---|
Source processor that exposes a REST endpoint specifically for retrieving archived payloads. |
|
Source processor that exposes a REST endpoint specifically for resubmitting archived payloads. |
Arrow
Name | Summary |
---|---|
Processor for writing data in the Arrow format using Arrow Flight RPC protocol. |
Azure
Name | Summary |
---|---|
Processor that writes payloads to an Azure Blob Storage container. |
|
Processor that looks up an object from an Azure Blob Storage container. |
|
Processor that acts as an Event Hubs producer to publish data to a given Azure Event Hubs instance. |
Copying
Name | Summary |
---|---|
Processor that increments the value of a uniquely identified counter set as an exchange property. |
|
Processor that saves a given source to a message exchange property. Value is saved as a string by a given |
|
Processor that sets a given source as the new payload. |
|
Processor that saves the given source to a message exchange scoped storage. Stash can then be accessed later on using the given key. |
|
Processor that deletes the object stored in the current flow’s stash by the given key. |
Cryptography
Name | Summary |
---|---|
Processor for converting incoming payload to binary message digest, using the specified hashing algorithm. Non-binary payloads will be converted to binary before being processed. |
|
Processor for loading a certificate from a secret and set the certificate as the payload. |
|
Processor for generating a digital signature based on asymmetric key cryptography. |
|
Processor for verifying that a message corresponds to a cryptographic signature, ensuring that the message has not been modified in transit. The signing and verification process is based on asymmetric key encryption. |
Files
Name | Summary |
---|---|
Source processor that consumes files over different protocols. |
|
Processor that produces files over different protocols. |
Flat Files
Name | Summary |
---|---|
Processor that parses a flat file input with data columns separated by a delimiter. This processor is highly configurable but will require almost no configuration to process regular CSV files. |
|
Processor that parses an Excel spreadsheet file (i.e., XLSX and XLS files). This processor is highly configurable but will require almost no configuration to process regular Excel files. |
|
Processor that, like the parseCsv processor, parses flat file input with data columns separated by a delimiter. |
Google Cloud
Name | Summary |
---|---|
Processor that consumes messages from a Google Cloud Pub/Sub subscription. |
|
Processor that acts as a Google Cloud Pub/Sub producer to publish messages to a Pub/Sub topic. |
|
Processor that writes payloads to a Google Cloud Storage bucket. |
|
Processor that looks up an object from a Google Cloud Storage bucket. |
Internet
Name | Summary |
---|---|
Source processor for exposing REST endpoints. Can be built from an API specification or exposed as a generic endpoint. |
|
Processor that produces a message from a REST endpoint. |
|
Source processor for exposing SOAP endpoints. Reference to a WSDL specification must be provided. |
|
Processor that acts as a producer of messages to a SOAP endpoint. Reference to a WSDL specification must be provided. |
JMS
Name | Summary |
---|---|
Source processor that consumes messages from a JMS broker. |
|
Processor that acts as a JMS producer to publish data to a given JMS server. |
Kafka
Name | Summary |
---|---|
Processor that acts as a Kafka producer to publish key-value pairs to a given Kafka server. |
|
Source processor that consumes messages published to the specified Kafka cluster and topic. The processor produces payloads by reading the record’s value as binary data. To convert the binary data to e.g. json, use an inboundTransformationStrategy in a downstream processor. |
RabbitMQ
Name | Summary |
---|---|
Source processor that consumes messages from a RabbitMQ queue. |
|
Processor that acts as a RabbitMQ producer to publish data to a given RabbitMQ broker. |
Routing and Scheduling
Name | Summary |
---|---|
Processor that aggregates fragments based on an identifier (correlation ID) and a given number of expected fragments. |
|
Processor that distributes messages to a set of flows. The distribution will not be considered complete until all destinations have confirmed reception of the message. |
|
Processor that determines if message payloads may proceed, provided the expression returns true when evaluated against the message payload. |
|
Source processor that receives messages handed over from other flows. |
|
Source processor that triggers an event message at configurable times. |
|
Source processor that delays the processing of messages handed over from other flows. |
|
Processor that splits the payload into fragments and sends each fragment as a separate message to the given flow. |
|
Processor that suspends processing of a message and waits for a correlated resume message before continuing. |
|
Processor that produces a resume message suitable for forwarding to suspendMessage processors to resume processing of suspended messages. |
|
Source processor that aggregates fragment messages based on a period of time or a number of messages, whichever comes first. |
SCADA
Name | Summary |
---|---|
Receive data from Habitat, which is a SCADA application from GE Vernova that contains real-time data. |
Transformations
Name | Summary |
---|---|
Processor for compressing the incoming payload (i.e., by creating a zip archive). |
|
Processor for decompressing the incoming payload. |
|
Processor that converts a Base64 encoded string to binary. Non-string payloads will be converted to string before being processed. |
|
Processor that groups the data in a list based on a grouping key. |
|
Processor that transforms the payload using a mapping specification. |
|
Processor that converts the incoming payload to a Base64 encoded string. Non-binary payloads will be converted to binary before being processed. |
Validation
Name | Summary |
---|---|
Processor that validates payloads by a given schema. Fails message processing if validation fails. |