Profile Overview

When processing various healthcare-related data in complex business environments, splitting the processing workflow into multiple smaller subsystems (XEServer profiles) simplifies resource management and allows you to scale subsystems dependently based on your business needs. One of the ways to achieve this is setting up inter-profile communication through AWS SQS queues to send, store, and receive messages at any volume without losing messages or requiring other services to be available.

Another benefit of using SQS is that it allows for decoupling of subsystems, which means that different profiles can communicate with each other without being directly connected or dependent on each other. This helps to improve the reliability and scalability of the overall business environment, making it easier to modify or update individual profiles without affecting others.

This profile is designed to help you test the inter-profile data transfer through the AWS SQS queue. The profile submits data to be processed on a different route and receives the resulting data.

Profile Location

Edifecs Library / Best Practices / Common Tasks / AWS Inter-Profile Data Transfer

Requirements

  • Edifecs XEngine 9.3 or later
  • Edifecs XEServer 9.3 or later
  • Edifecs Application Manager (EAM) 9.3 or later

Prerequisites

  • In Edifecs Application Manager, add the profile AWS Processing Tester and AWS Processing Step Template from the Edifecs Library. For more information, see Edifecs Library Help Center.
  • If you do not have an Amazon AWS account yet, go to https://aws.amazon.com and create one.
  • On the profile's Environment tab, enter your AWS account credentials, inbound/outbound data buckets and queues names. The profiles must be pointing to each others' SQS queues as shown below:
    AWS Processing Tester ProfileAWS Processing Step Template Profile
    OutboundDataBucketInboundDataBucket
    OutboundDataQueueInboundDataQueue
    InboundDataBucketOutboundDataBucket
    InboundDataQueueOutboundDataQueue