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

Note: 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

Note: 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
Note: 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.