ebXML Host: HTTP Tab

Indicates whether you use SSL or not for outbound file transfers.

HTTP: Do not require use SSL

HTTP/s: Require SSL for outbound file transfers.; If you select HTTP/s, you can select Check certificate server name

Require your trading partner to use Secure Socket Layer (SSL) for inbound file transfers.

In most cases the CONNECT command is not used and should be left blank. In rare instances, CONNECT is required by the remote server to identify the client, particularly if SSL has not been used.

The only valid Method for AS2 commands is PUT ("POST").

The server Path for the PUT command.

If the remote server is also using the VersaLex application, the path is /ebMS. The resource path must be properly specified in order for your trading partner’s ebMS installation to process messages from you. Given the URL provided by your remote trading partner in the form:

http(s)://remote-host:port/resource-path?optional-parameters

Enter the bolded portion in this field (if it was supplied).

By default, no Parameters are specified for sending ebMS messages. If parameters are required, they must be obtained from your trading partner when the trading relationship is established. Given the URL provided by your remote trading partner in the form:

http(s)://remote-host:port/resource-path?optional-parameters

Enter the bolded portion in this field if it was supplied.

These header fields are filled in at the Mailbox and/or Action level and specify the values set in the HTTP headers that precede the body of the message sent.

At a minimum, the only Header required is the SOAPAction: "ebXML" header. Content-Type: is optional and can be specified at the mailbox and/or action level.

Note: Entering a value for the Content-Type header is optional. If Content-Type is not specified or if multiple payloads are attached in the message, the Content-Type is detected based first on file content and then the file extension. Detectable types include application/edifact, application/edi-x12, application/edi-tradacoms, application/xml (text/xml), application/pdf, application/msword, application/x-msexcel, application/rtf, application/zip, image/bmp, image/gif, image/tiff, image/jpeg, text/plain, text/html, and video/mpg.

These header fields are filled in at the Mailbox and/or Action level and specify the values set in the HTTP headers that precede the body of the message sent.