Agreement Resolution for Incoming AS2 Messages
When BizTalk Server receives an EDIINT/AS2-encoded message over HTTP/HTTPS transport, it attempts to determine the trading partner’s business profile that sent the message. It does so by attempting to do the following (in the order shown):
Make a match between the AS2-From header in the incoming message with the value for AS2-From in the Identifiers page of the one-way AS2 agreement in the Agreement Properties dialog box.
If BizTalk Server cannot determine the agreement, it will attempt to match the AS2-From context property that is set for the incoming message with the name of a trading partner.
Note
Since the AS2-From header can only contain ASCII characters, you must ensure that your trading partner name and the AS2-From alias also contain only ASCII characters. If an exact match does not occur, BizTalk will be unable to determine the agreement based on the incoming message headers.
The AS2 receive pipeline will process the message only if an agreement is determined. Unlike in EDI processing, there are no fallback AS2 properties that BizTalk Server can use if it cannot determine the agreement.
Once the pipeline has determined the agreement, it will check the setting of the Use agreement settings for validation and MDN instead message header property in the Validation page of the one-way AS2 agreement in the Agreement Settings dialog box. If that property is checked, the receive pipeline will use the agreement properties to process the message. If the property is cleared, the receive pipeline will use the values in the AS2 header of the message to process it.
Note
The AS2 agreement that is determined during agreement resolution may not be the same agreement as the EDI payload. There is no requirement that AS2 and EDI must share the same agreement, as the AS2 agreement may represent a clearinghouse that routes EDI documents from multiple parties.
For more details on the receive process, see Processing an Incoming AS2 Message.