AS2 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

HTTP/s only: 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 either /as2 for newer installations or / for older installations. The resource path must be properly specified in order for your trading partner’s AS2 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 AS2 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).

At a minimum, the following Headers must always be specified in order to properly send AS2 messages:

AS2-From - the alias of the sender of the AS2 message.
AS2-To - the alias of the receiver of the AS2 message.
Note: The AS2-From / AS2-To fields are determined and agreed upon as part of the initial setup of the trading relationship. These fields could be company-specific, such as DUNS number, or could simply be an agreed-upon identification string. The AS2-From / AS2-To combination is case-sensitive and must be unique across all hosts defined in your system, since this combination is used to determine into which Inbox messages are stored when received from remote hosts.
Subject - identifies the message and is returned in the human-readable section of an MDN, if requested.
Content-Type - specifies the format of the message being sent and is used by the sending and receiving applications to properly assemble and parse the message. Currently supported content types (in the pull-down menu) are:
- EDIFACT
- X12
- XML
- Binary
- Plain Text
- EDI Consent
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 or Action level and specify values to be set in the HTTP headers that precede the body (actual content) of the message to be sent.