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 expected parameters or headers for BusinessConnect Container Edition – Services Plug-in are as follows:
fromTp
: This is a required field for the incoming message.toTp
: If this parameter is missing, it is set to the default host.operationID
: If this parameter is missing, the default is set toBC/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: ThefileName
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 (Configuring Private Processes or Configuring Private Processes) for backward compatibility, but is deprecated starting with the BusinessConnect 6.0 release.
Populating URIs
Note: The AS2 specification does not support custom headers.
Ensure that the following parameters are followed for populating URIs:
- On the outbound side, URI fields have precedence over the headers.
- On the inbound side, if values are specified in headers and URI places, the transport headers take precedence over the request URI values.