Copyright © TIBCO Software Inc. All Rights Reserved

> 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, Business Connect 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.

> | 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.
> Email Transport
> The URI format is mailto://username@domain, such as mailto://john@acme.com
> When using Email transport, you have the option of specifying the mail subject. If the subject contains the string operationID=”category/version_number/operation_name” then OperationID is taken as the operation ID for that transaction.
> If the operation ID is not specified in the subject, then the value is what is sent by the private process.
> File Transport
> The URI format is file://BaseDir/*.*
> This causes all directories under BaseDir to be checked for files. In order for the file to be handled by the Services Plug-in, the document must appear as follows:

> • | Default behavior, such as for the operation BC/version/Notify:

> BaseDir/EZComm/TpName

> • | Non-default behavior, for other operations:

> BaseDir/EZComm/TpName/Category_version_OperationID
> where BaseDir is a user selected base directory, TpName is the name of the trading partner, Category is the operation category, version is the operation version, and OperationID is the operation ID.
> If OperationID is not provided, then it defaults to BC/version/Notify.

> | A file name can be specified in the file mask field. See TIBCO BusinessConnect Trading Partner Administration Guide, Table 41, Outbound File Transport for information about how to specify the file mask field in File transport.

> You should provide a file mask *.* for a file. Otherwise, the file is not picked up by the File transport.
> FTP Transport
> URI format ftp://server:port/dir. dir can be anything or absent.

> | A file name can be specified in the file mask field. See TIBCO BusinessConnect Trading Partner Administration Guide for information about how to specify the file mask field in FTP transport. With the Services Plug-in, FTP inbound transactions always defaults to the BC/version/Notify operation.

> You should provide a file mask *.* for a file. Otherwise, the file is not picked up by the FTP transport.
> HTTP/S Transport
> URI for the HTTP Transport
> URI format: http://server:port/dmz/EZComm
> Example: http://www.gizmo.com:555/dmz/EZComm
> For HTTP transport, the partner name, host name, and operation ID can be specified as parameters in the request URI or as transport headers.
> The parameters or headers that the Services Plug-in expects are as follows:

> • | fromTp This is a required field for the incoming message.

> • | toTp If this parameter is missing, it defaults to the default host.

> • | operationID If this parameter is missing, it defaults to BC/version_number/Notify.

> • | fileName If you specify the parameters in the URI, the format is:

> http://host:port/dmz/EZComm?fromTp=fromTP&toTp=toTP&operationID=opID&fileName=fileName

> | The fileName feature is not supported for the AS2-HTTP transport.

> URI for the HTTPS Transport
> URI format: https://server:port/dmz/EZComm
> Example: https://www.gizmo.com:555/dmz/EZComm

> | BusinessConnect 6.x still supports the older BusinessConnect 5.x URI format http://server:port/EZComm (or https://server:port/EZComm) for backward compatibility, but is deprecated starting with the BusinessConnect 6.0 release.

> Populating URIs

> | The AS2 specification does not support custom headers.

> URIs are populated as follows:

> • | On the outbound side, URI fields have precedence over the headers.

> • | On the inbound side, if values are specified in headers as well as URI places, the transport headers take precedence over the request URI values.

Copyright © TIBCO Software Inc. All Rights Reserved