Special considerations for AS packaging

When the packaging of the document is specified as AS, WebSphere Partner Gateway performs some additional processing.

How inbound documents are routed

When an EDI document is received from a community participant:

  1. WebSphere Partner Gateway first checks the AS1 or AS2 header information. Specifically, it checks the sender and receiver information to determine whether it matches IDs for valid community participants.

    If the values in the header fields do not match valid IDs, WebSphere Partner Gateway does not route the document.

  2. WebSphere Partner Gateway then performs the steps described in Overview of EDI routing.

How outbound documents are routed

When an EDI document is received from a back-end system, WebSphere Partner Gateway determines whether an AS BusinessID attribute has been specified for both the source packaging (None) and the target packaging (AS):

Setting both IDs in the participant profile

Because WebSphere Partner Gateway uses both the AS1 or AS2 header information as well as the information derived from the EDI document, the IDs for the same participant could be in different forms. For example, the AS header information for the sender could be 123456789 while the information derived from the EDI document could be AB-12345678.

Make sure that you have listed both IDs in the profile for the community participant. Refer to the Hub Configuration Guide for information.

Copyright IBM Corp. 2003, 2005