Profile Workflow

This profile receives data from another profile through the SQS queue (either a full message or a message with no body but with an identifier pointing to the S3 storage containing the required data), if required, retrieves the data from a dedicated S3 bucket, performs required processing, and sends back the results to the SQS queue of another profile.

The profile contains the following routes:

This route demonstrates a typical approach for receiving data through the SQS. The route picks up a message from the SQS queue and checks if this message contains the message body to determine if retrieving data from an S3 bucket is required. The route then sends the data for processing on the subroute.

Route Structure

270 Request Validation

Route Components

Component Name Component Type Description
Amazon SQS Inbound Amazon SQS Inbound Scans the Amazon SQS queue and reads messages, if any.
Contains Body? Router Checks to see if the incoming message contains a body. If the message body was saved in an intermediate storage before submission to this profile, it will be retrieved from the dedicated S3 storage based on the received unique key-object identifier.
Amazon S3 Inbound Amazon S3 Inbound Retrieves required data from the dedicated S3 bucket based on the received unique key-object identifier.
Processing Subroute Sends data for processing on the subroute Processing.

Use this route template to provide custom logic for data processing. By default, the route is configured to validate the data, generate acknowledgments, and send the results to the subroute that handles sending data back to the other profile.

Note AWS SQS does not support multi-message exchanges.

Route Structure

270 Request Validation

Route Components

Component Name Component Type Description
Inbound Parent Route Input Picks up data from the parent route.
Generate Acks XE Native Validates the incoming data and generates acknowledgments.
Archive acks Aggregation Archives all the incoming acknowledgments.
Outbound Subroute Sends the resulting data for processing on the subroute Outbound.

This route demonstrates a typical approach for sending data through the SQS. First, the route checks the resulting file's size. If the data is too large, the profile saves the message body to an assigned S3 bucket with a unique key-object identifier. The route then transfers either this key or the full file to the SQS queue of the other profile.

Route Structure

270 Request Validation

Route Components

Component Name Component Type Description
Processing Result Parent Route Input Picks up data from the parent route.
File Size? Router Checks to see if the file size exceeds the limit of 200 KB.
Store to Amazon S3 Amazon S3 Outbound Stores file that are larger than 200 KB in a dedicated S3 bucket.
Remove Message Body Groovy Runs a Groovy script to remove the message body for files larger than 200 KB.
Amazon SQS Outbound_1 Amazon SQS Outbound Sends the processing results to the SQS queue of the other profile.