Message Routing
When an EDI document is received from a trading partner by the Gateway protocol through the various supported inbound transports Gateway handles all the activities in acknowledging your trading partner at the transport level.
Transport level acknowledgment includes message decryption and authentication as well as composing the receipt synchronously or asynchronously. Gateway then inspects the message and identifies the document type in preparation for protocol standard-specific processing. Protocol standard-specific processing includes splitting the incoming EDI document into multiple interchange envelopes if necessary and redirecting each interchange envelope for EDI message validation and XML conversion.
After this splitting, the EDI message validation and XML conversion is handled by protocol standard-specific processing such as the X12 standard. The corresponding protocol standard level acknowledgment, such as X12 997, is generated accordingly.
The Gateway protocol also provides an option for bypassing the protocol standard specific message validation and XML conversion based on the detected document type. This option is available through the Operations Editor for the corresponding document type. By disabling the protocol standards specific processing, Gateway can simply serves as the inbound transport gateway for receiving and routing inbound EDI documents to your back-end systems or legacy applications which are already capable of processing a well-formed EDI documents.