AS2-Related Actions

AS2 Send File to host Action for executing outbound AS2 send file transactions can be added to Event Rules. (Refer to Sending Files via AS2 Partner without Inbound Access for details of configuring this Action.)

The AS2 Send File to host Action is a synchronous event even if asynchronous MDN receipts are requested. Synchronous means that the Event Rule executes Actions sequentially from top to bottom; when EFT Server encounters an AS2 outbound action, it performs the transfer, and then if MDN is synchronous, EFT Server waits for the result before moving to the next Action (with success/failure set appropriately). If MDN is asynchronous, EFT Server proceeds to the next Action based only on the HTTP result of the SEND operation, NOT the result of the asynchronous MDN receipt.

The AS2 Send File to host Action is available for the following Events:

When triggered, the AS2 Send File to host Action offloads one or more user-defined files and one or more context files. Depending on the AS2 Send File to host Action’s retry configuration, the Action fails if any error occurs when attempting to send the AS2 payload. Those errors may include any connection, authentication, transport, or navigation errors; receipting errors or failures; payload errors, including transfer errors or integrity mismatch errors or failures; server communicated errors; and unknown or undefined errors, such as:

No receipt was provided
The receipt was not signed
The MIC value returned did not match the original file/message MIC
EFT Server was unable to:

verify the receipt signature
establish a connection to the remote host
upload the file to the remote host
send an the receipt asynchronously
send the receipt synchronously