Trading Networks 10.3 | Administering and Monitoring B2B Transactions | webMethods Module for EDIINT | Before You Can Transport Documents Using EDIINT | Including EDIINT Information in Profiles | External IDs Tab of the Profile | Behavior of External ID Matching | Updating Existing Profiles to Use EDIINT AS1, EDIINT AS2, and EDIINT AS3
 
Updating Existing Profiles to Use EDIINT AS1, EDIINT AS2, and EDIINT AS3
Prior to version 6.5.2, Module for EDIINT only looked at the external ID value to find a matching profile when sending or receiving documents; it ignored the external ID type. Thus, each external ID value was required to be unique; a value could not be duplicated within a single profile or in any other profile.
With version 8.0 and higher, Module for EDIINT looks at both the external ID value and the external ID type in order to find a matching profile. This means you may assign the same external ID value for multiple external ID types within the same profile or in any other profile (or the values may be unique).
By default, when you send an EDIINT document the wm.EDIINT:send service tries to match the document's "To" header (for example, AS2-To: 987654321) with the external ID type and value defined in a partner profile (for example, EDIINT AS2 and 987654321).
Similarly, when you receive an EDIINT document the wm.EDIINT:receive service tries to match the value of its sender ID input parameter (which specifies both type and value) with a partner profile's external ID type and value.
Important:
If you use the EDIINT AS1, EDIINT AS2, or EDIINT AS3 types in your profiles, make sure the EDIINT ID Match option is selected (this is the default). If you turn off this option, you may get unpredictable results when trying to match external IDs. For details, see Using the EDIINT ID Match Option.