BizTalk Server verifies the values of the authorization and security fields set for agreement with the fields in the message. In case of non-compliance, BizTalk Server suspends the exchange. For EDIFACT coded messages, these fields are the recipient`s reference word (UNB6.1 and UNB6.2). For X12 coded messages, these fields are qualifiers and authorization information (ISA1-2) and security qualifiers (ISA3-4). The EDI emission pipeline conducts the search for an agreement by conducting a series of steps to determine if there is a match between the outgoing exchange and the characteristics of an agreement. Once the agreement has been established by BizTalk Server, it determines the document scheme applicable to the exchange (see below). It uses the properties associated with the comparison agreement and the appropriate scheme to generate and verify the outgoing message. Click OK. The newly added agreement is mentioned in the „Agreements“ section of the „Parties and Business Profiles“ section. The newly added agreement is enabled by default. If Stage 2 is inconclusive, the agreement is broken by comparing the party name in the features of the information with the DestinationPartyName property, which is set in the Agreement Property Identification tab as an additional agreement regulation.
If one of the above context properties sets is reclassified and BizTalk Server fails to reach an agreement associated with these contextual properties, BizTalk Server suspends the message. On the Local Host Settings page in the An Impractable Agreement tab in the Convention Properties Dialog, you can set up a value grid to set a custom name space. If no match is found in this grid, the EDI disassembler uses the default name space in the destination name area that is selected for the default line. Resolve the agreement by comparing the sender qualifier and qualifier as well as the qualifier and receiver qualifier in the interchange with those of the characteristics of an agreement. You`ll notice that two new tabs are added to the General tab. Each tab is used to set up a one-sided agreement, and each one-sided agreement is a complete message transaction (including message transmission and confirmation transmission). [! NOTE] If you select the local BizTalk Process quince box for messages supported by the party or supported by the party that supports sending messages from that party, you can specify that the party to be created is for the same organization that is also hosting [! INCLUDEbtsBizTalkServerNoVersion]. On this basis, some properties are turned on or off when you create a deal.
For this exemplary method, however, you can leave this box enabled. If the four contextual properties have been set for a message and no match is found between these context properties and the properties, the message is stopped. The agreement will only be terminated using the broadcast port associated with an agreement if the four context characteristics have not been defined. When BizTalk Server receives a message, it tries to cross-reference the sender`s information for an agreement with the sender`s information in the message. The sender`s information contains the ISA5 and ISA6 data elements for the X12 message and the UNB2.1 and UNB 2.2 data elements for EDIFACT. The convention information can be found in the Tab`s Identify a Deal in the Contract Properties dialog box. If BizTalk Server doesn`t detect the agreement, BizTalk Server uses the features of the case agreement to determine the name space, process the message and send all confirmations. Since the AS2-From header can only contain ASCII characters, you need to make sure that your business partner name and the as2-From alias contain only ASCII characters. If there is no exact match, BizTalk cannot determine the agreement on the basis of inbound flows. The emission pipeline attempts to compare the AS2From and AS2To contextual properties with the AS2From and AS2To values, which are part of the features of the agreement.