Using EDIINT AS2 with 1SYNC
EDIINT AS2 is an XML document transport protocol that uses HTTP to build a tunnel to the recipient address, establishes the connection, and then sends the information with a signed payload, assuring the sender of receipt.
In nominal operating mode, the EDIINT client can expect to receive two messages from 1SYNC in response to each business document sent:
An MDN (Message Disposition Notification), which indicates the 1SYNC EDIINT hub received the request business document
A 1SYNC Response (which is a TN XML document type), which indicates the 1SYNC application has processed the business document on the back-end.
Note:
An MDN is a receipt document that provides the sender with a guarantee that the intended recipient received the business document. MDNs are not XML but are multipart MIME documents.
Before you can use EDIINT AS2 as a transport protocol, you must first set up EDIINT to interact with 1SYNC. This chapter provides procedures for doing this as well as illustrates the 1SYNC EDIINT workflow. The latter is discussed in the following section.
Important:
If Integration Server is inside a firewall, you must configure this Integration Server as an Enterprise Gateway Server. For information about how to configure Integration Server as an Enterprise Gateway Server, see the webMethods Integration Server Administrator’s Guide for your release.