Restarting AS2 Message Transmission

When the optional AS2 Restart feature is enabled and transmission of an AS2 message is interrupted, the sender is able to restart the transmission from the point at which it failed, instead of starting the entire transmission over again. This is advantageous when large files are transmitted because the possibility of failure due to such occurrences as connection timeouts or loss of network connectivity is greater.

There are two ways to enable AS2 Restart when Module for EDIINT is in the sender role:

Using the enableAS2Restart input parameter of the wm.EDIINT:send service. For more information, see Invoking the Send Service to Restart Message Transmission.

Configuring the AS2RestartEnabled EDIINT property. For more information, see Using EDIINT Properties to Restart Message Transmission.

Note:
The enableAS2Restart input parameter of the wm.EDIINT:send service overrides the global AS2RestartEnabled EDIINT property.

When Module for EDIINT is the receiver, the module temporarily saves restart-enabled messages to its file system in the location defined in the AS2RestartTempFilePath property. As a message comes in, the module continues to append this temporary file and returns to the sender a Content-length header containing the number of bytes that have already been received, as an HTTP HEAD response. If message transmission fails, the sender restarts transmission from the point specified in the Content-length header.

Once the entire payload is received, the module begins processing it.

You can purge the payloads saved in the location specified in the AS2RestartTempFilePath property at any time by invoking the wm.EDIINT:purgeFiles service. For more information, see wm.EDIINT:purgeFiles.