Profile Workflow

The profile is designed to pick up data from a file system folder and send it to the AWS SQS queue of the other profile for processing. If the data is too large, the profile saves the message body to an assigned bucket with a unique key-object identifier. This key is then transferred within the properties to the SQS queue reserved for processing incoming data. The route that handles processing checks to see if the incoming data contains a message body. If not, the route picks up the required data from the S3 bucket. This data is then stored in a file system folder for further processing based on your business needs.

This key will then be transferred within the properties to the queue.

The profile contains the following routes:

This route demonstrates the mechanism of obtaining data that will later be sent for processing on the AWS Processing Step Template profile via the AWS SQS queue. By default, the route picks up data from a file system folder.

Route Structure

270 Request Validation

Route Components

Component Name Component Type Description
FS Intake File System Inbound Picks up data that needs to be transferred to a different profile from a file system folder. Replace the intake component based on the type of storage that contains the required data.
Outbound Subroute Sends the data for processing on the subroute Outbound. This subroute checks the data size and, if it exceeds the limit of 200 KB, saves the message body to an assigned S3 bucket with a unique key-object identifier. This key is then transferred within the properties to the SQS queue of the other profile. The data not exceeding the size limit is sent directly to the SQS queue.

This route shows typical approach for receiving data after processing on the other profile. 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 that save the data to a file system folder.

Route Structure

270 Request Validation

Route Components

Component Name Component Type Description
Processing Results 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.
2) Receive Results Subroute Sends data for processing on the subroute 2) Receive Results that saves the incoming data to a file system folder.