Architecture of EDI Accelerator

The architecture of EDI Accelerator is given below:

The EDI Accelerator supports direct exchange of data using File and FTP protocols. In case, where the trading partner is using a protocol other than File or FTP, third-party software, namely Managed File Transfer (MFT) is used. This host will receive the data from the partner's protocol and send it to EDI Accelerator on a local file system or FTP location.

For inbound processing, MFT receives data from any trading partner and download it into its configured mailbox. The EDI Accelerator picks the data file from the inbox folder of MFT and starts its inbound processing. It splits the file into transaction sets and insert them into the EDI database. It now processes each transaction set one by one. Once this EDI translation is done, the translated data is placed in the File System. This data can now be sent to the back-end application using a process flow. 

For outbound processing, EDI Accelerator picks the data from the File System (sent by the backend application using a process flow) and starts its outbound processing. It translates the data and splits it into different records, based on the Application ID (used to identify the Trading Partner for the specific data). Once it translates the outbound data, it puts it in the Outbound Queue. Transactions in this queue are processed when a batch schedule is run. Then, the EDI Accelerator picks these transactions, creates GS and ISA Envelopes for them, and send them to Partner using File or FTP protocol of Adeptia Suite. If MFT is being used, then they are sent to the outbox folder in MFT mail box, from where they are sent to the Partner.

Key Terms used in EDI Accelator

The key terms used in the EDI Accelerator are as follows: