Each party is identified by a unique party alias, which consists of three distinct elements, a name, qualifier, and value. Each party must have at least one set of party aliases.
| Use this | To do this |
|---|
| Name | If a party uses a mutually agreed EDI value to qualify itself, the Name of the qualifier is EDI. For example, a telephone number is used to identify the party, then the entry in the Name field would be Telephone number. When developing an EDI solution, the Name value is EDI. |
| Qualifier | The entry in the Qualifier field; identifies the entry in the Value field. For example, if you entry EDI in the Qualifier field, you are classifying the entry in the value field as an EDI value. When developing an EDI solution, the Qualifier value must be EDI. |
| Value | The entry in the value field is the actual mutually agreed EDI logical address, or telephone number. For EDI, the value must adhere to the following structure EDI://aaaa:bb:zzzzz |
How the Base EDI adapter uses party aliases
- A party alias is required to determine the recipient for inbound messages.
- The BizTalk Server 2004 Base EDI adapter takes the logical address of sender of message, creates a URI from this logical address, and then finds the Receive Location record with that URI.
- Next, the BizTalk Server 2004 Base EDI adapter takes the logical address of recipient of message, creates a URI from that and using this URI, finds the Party Alias record.
- Finally, the BizTalk Server 2004 Base EDI adapter creates the message context from the Sender URI and Recipient Qualifier & Value, and BizTalk 2004 then routes the message to the recipient.
See Also
Developing EDI Business Processes
To download updated BizTalk Server 2004 Help from www.microsoft.com, go to
http://go.microsoft.com/fwlink/?linkid=20616.
Copyright © 2004 Microsoft Corporation.
All rights reserved.