The Role of the Party in AS2 Processing
A party is an entity outside of BizTalk Server that interacts with BizTalk Server. An organization uses BizTalk Server to receive AS2 messages from, and send AS2 messages to, one or more trading partners, each of which is a party.
You set AS2 party properties in the Partner Agreement Manager (PAM) user interface. The PAM screens are in the Parties node of the BizTalk Server 2006 Administration Console.
For more information about parties in general, and how a party affects the home organization, see The Role of the Party in EDI Processing.
Any time the home organization receives an AS2 message from, or sends an AS2 message to, that party, the BizTalk Server AS2 receive pipeline or AS2 send pipeline will process the message according to the AS2 party properties. At the home organization, you define a party for the trading partner in the BizTalk Server 2006 Administration Console. You can define the following sets of properties for a party for AS2 communications.
Party properties that define general aspects of the party, such as name and aliases, send ports, and signing certificate
AS2 properties that define how BizTalk Server will perform AS2 communications, both incoming and outgoing.
Note Unlike in EDI processing, there are no global AS2 properties that BizTalk Server can use if it cannot determine the party. The AS2 receive or send pipeline will process the message only if a party is determined.
You can use HTTP/HTTPS transport for either EDIINT/AS2-encoded messages or non-EDI over AS2-encoded messages. If you transmit EDIINT/AS2-encoded messages over HTTP/HTTPS transport, the EDI properties for the party will apply.
The signing certificate for the home organization is defined in the Certificate page of the BizTalk Group - Group Properties dialog box. Additionally, you can define a different certificate to sign outgoing messages for a specific party. To define a different certificate for a specific party, use the Certificate page of the AS2 Properties dialog box for the party. For instructions on overriding default certificate for signing outgoing messages, see Configuring the Certificate.
|The option to override the default signing certificate and have a different certificate for a specific party is available only if you have BizTalk Server 2006 R2 SP1 installed.|
Many properties have defaults that are used if you do not define them explicitly. If you have changed any AS2 party property, the row for the party in the Parties pane of the BizTalk Server Administration Console will indicate Modified for AS2, rather than Default.
When BizTalk Server receives an AS2-encoded message, it attempts to determine the party that sent the message by matching the AS2-From header to the AS2-From party property. When BizTalk Server sends an AS2-encoded message, it attempts to determine the party that will receive the message by matching the AS2-To header to the AS2-To party property. For more information, see Party Resolution for Incoming AS2 Messages or Party Resolution for Outgoing AS2 Messages.
The "Override inbound message properties" property enables you to override the AS2 properties contained in the AS2 headers of an incoming AS2 message. These properties included those enabling signing, compression, and encryption. They also included those enabling MDN generation, and those determining whether the MDN should be signed and transmitted asynchronously or synchronously.