Exchanging URIs

Trading partners must exchange Uniform Resource Identifiers (URIs) as part of the business agreement before they can transact e-commerce.

For the Services Plug-in, the URI, the subject, and the headers can encode information about the from trading partner, to trading partner, and the operation ID of the transaction. For an outgoing HTTP message, BusinessConnect Container Edition always populates these values in an HTTP URL. However, for an incoming HTTP message it can interpret these values from an HTTP header or an HTTP URL, in that order.

Note: The Services Plug-in populates trading partner and operation information in the outgoing URI only if the URI ends with /EZComm.

Additional information in the URI, such as toTP and fromTP, is available only for transports other than AS1, AS2, or EMAIL, since the same information is derived from the internet headers such as AS2 TO/FROM ID and the EMAIL FROM/TO address. Such information becomes redundant and ambiguous if provided in the URI.

Available transports and their URI formats are listed in this section.