AS2 Outbound (Sender) Parameters

For AS2 outbound (sender) connections for transactions over the HTTP and HTTPS ports, enable AS2 by selecting the AS2 check box on the Site's Connections tab. You can enable or disable AS2 in the Settings Template and/or for the user account, or by selecting AS2 in the New User Creation wizard on the protocol selection page when you create the user. The standard inheritance rules apply. (AS2 has to be enabled and configured for the Site before you can enable it for a Settings Template or user account.)

The parameters in the table below are available in the AS2 Outbound Settings dialog box can be configured manually or using the setup wizard.

  • Click Setup Wizard to Configure AS2 Outbound Partners Using the Wizard.

  • Click Test to Test the connection to the partner.

  • (Optional) Click Headers to add a custom header. The purpose of custom HTTP headers is to pass additional or required information to the recipient's server. The Name and Value fields can each contain up to 255 characters. The Value fields can use context variables.

    • To add the header, click Add, then provide the name and value in the table, as shown in the examples in the dialog box.

  • Click Proxy to launch the Proxy Settings dialog box. You can forward the connection through the DMZ Gateway (as a SOCKS5 proxy) or an HTTP proxy of your choosing.

  • Click Clear All to reset all of the fields to default values. (A confirmation prompt appears.)

Parameter

Required/Optional

Description

Monitored hot folder

Optional

Specifies the monitored folder for added files. If no folder is specified, no folder monitoring occurs. The partner profile can be invoked from the Event Rules. (Can be on a drive or UNC path.)

File include mask

Optional

Used to include files based on their extension for sending to the destination to the partner’s remote AS2 host. For example, include only .txt files. Defaults to asterisk (*) to include all files. Blank also means include all files. Accepts wildcard masks; semicolon or comma delimited.

File exclude mask

Optional

Used to exclude files based on their extension from sending to the destination to the partner’s remote AS2 host. For example, exclude .txt files. Defaults to blank, which means exclude no files. Accepts wildcard masks, semicolon or comma delimited.

Delete source after successful offload (MDN received)

Required

Used to delete sources files after sending them to the destination, after the MDN is received and verified from the remote AS2 host. Selected by default.

Host address

Required

AS2 Outbound host address. Requires protocol prefix in URL (http:// or https://). Specified in AS2 Partner Access wizard.

Port

Required

AS2 Outbound port. Range is 1-65K; defaults to 80 if host address is preceded by http; 443 if host address is preceded by https.

Path

Optional

Relative path to the remote directory, such as, /partnerXYZ, /partners/mailboxes/xyz, or /192.168.20.16/path

Username

Optional

User login name

Password

Optional

Password

Message subject

Optional

AS2 message subject

Content type

Required

AS2 content type. Options include:

  • X12 - Format used by many healthcare, insurance, government, transportation, and finance organizations.

  • EDIFACT - Format adopted by the International Organization for Standardization (ISO) as the ISO standard ISO 9735.

  • XML - File format used for structured documents.

  • EDI Consent - Provides a standard mechanism for "wrapping" the EDI objects but does not specify any details about those objects.

  • Binary (default) - e.g., executables, word processing files, database, spreadsheet, and multimedia files

  • Plaintext - e.g., text and HTML files

  • For information about the various content types, refer to RFC 2046 at http://www.ietf.org/rfc/rfc2046.txt.

Compress message

Required

When selected, specifies that the AS2 message should be compressed when sent. (Cleared by default.)

Encrypt message

Required

When selected, specifies that outbound AS2 messages should be encrypted. (Selected by default.)

Encryption algorithm

Optional

Used to specify the encryption algorithm to use for outbound transactions. AESCBC256 is used by default.

Sign message

Required

When selected, specifies that outbound AS2 messages should be signed. (Selected by default.)

Signature algorithm

Optional

Used to specify the signature algorithm to use for outbound transactions. SHA-256 is used by default.

Your certificate

Required

Displays the AS2 certificate public key path to use for signing, copied from the Site. (Can be on a drive or UNC path.)

Partner certificate

Required

Specifies the AS2 certificate to use for encrypting outbound transactions and for validating signed MDN receipts. (Can be on a drive or UNC path.)

Your AS2 identifier

Required

Used to apply a unique AS2-From ID to outbound messages.

Partner AS2 identifier

Required

Used to apply a unique AS2-To ID to outbound messages.

Receipt policy

Required

Used to request an MDN receipt. Options include:

  • Don’t request a receipt

  • Request a signed receipt (default)

  • Request an unsigned receipt

Receipt delivery

Required

Specifies receipt delivery method

  • Synchronous (default)

  • Asynchronous (see Asynchronous receipt timeout, below)

The following fields are used to determine whether a message send attempt has failed due to a timeout, error, or synchronous MDN receipt failure, or other error, after which EFT will attempt to resend the same message at regular intervals, if specified. Because EFT is sending the same content, it will resend the same message, payload, and AS2 Message ID.

Parameter

Required/ Optional

Description

Message send attempt timeout (seconds)

Optional

Specifies the timeout after which a message send attempt is considered a failure if no response or error is received from the remote server. Range: 1-99999 seconds; 60 by default. A value of 0 is not accepted.

Message send attempt retries

Optional

Number of times to reattempt to send the message. Range: 0 (no retry) to 999, 10 is the default. Retries do not include the initial attempt. That is, 10 retries means 10 in addition to the first attempt (11 total).

Send attempt delay between retries

Optional

Interval between resend attempts. Range: 0 (no wait) to - 600 seconds; 30 seconds is the default

Asynchronous receipt timeout

Optional

Specifies the timeout after which EFT determines whether an asynchronous receipt was received. Range: 0 (no timeout) to 999,999 minutes; 7200 minutes (5 days) is the default. If the MDN is received after the timeout expires, the MDN is discarded, EFT returns an HTTP error code to the sender, and triggers the transaction failure event, if defined.

Transaction FAILED notification email*

Optional

Opens the Edit Mail Template in which you can specify an email notification for failed transaction. (Refer to email Notification Action for details of defining an email notification.)

Transaction SUCCESS notification email*

Optional

Opens the Edit Mail Template in which you can specify an email notification for successful transaction. (Refer to email Notification Action for details of defining an email notification.)

Transaction FAILED run command*

Optional

Opens the Custom Command dialog box in which you can specify a Custom Command to occur upon failed send. (Refer to Creating a Command to create a command and refer to Script: Custom Command Action for details of using a Command.)

Transaction SUCCESS run command*

Optional

Opens the Custom Command dialog box in which you can specify a Custom Command to occur upon successful send. (Refer to Creating a Command to create a command and refer to Script: Custom Command Action for details of using a Command.)

* EFT sends emails and executes commands only after the final transaction status (Failure or Success) is known.