AS2 transfer sites

Although transfers using the AS2 protocol function in a different way than the other supported protocols, you can subscribe accounts with AS2 transfer sites to applications. Among the standard applications, the Site Mailbox and Standard Router applications are appropriate for an AS2 transfer site.

Unlike transfer sites for other transfer protocols, an AS2 transfer site is also used for transfers initiated by the remote AS2 site (considered client-initiated by SecureTransport). Only the fields marked with an asterisk (*) as required are needed to define the partnership to enable these transfers.

For detailed information about AS2 transfers, see AS2 transfers.

The following table describes the AS2 protocol options for defining a transfer site.

Field Description
SecureTransport Server Settings
AS2 Name*

The local partnership name, which the remote AS2 site uses to identify to this SecureTransport Server. Each AS2 transfer site for a user must have a unique AS2 Name.

You cannot enter spaces-only values in this field. For more information, see Spaces in required fields.

Signing Certificate (Optional) The alias that represents the server or partner certificate used to sign a message.
Encryption Certificate (Optional) The alias that represents the server or partner certificate used to encrypt a message.
Email The email address used to receive information from the remote AS2 site. You cannot enter spaces-only values in this field. For more information, see Spaces in required fields.
Remote Site Settings
AS2 Name* The remote partnership name, which the SecureTransport Server uses to identify to the remote AS2 site. You cannot enter spaces-only values in this field. For more information, see Spaces in required fields.
URL The URL used to access the remote site. For example, https://as2.example.com:10443,https://172.23.34.45:10443, or https://[FC00:1234:2345:3456::]:10443. You cannot enter spaces-only values in this field. For more information, see Spaces in required fields.
Network Zone

The network zone that defines the proxies to use for transfers through this site.

  • Select none to connect directly to the partner AS2 server.
  • Select any to allow SecureTransport to select the proxy connection using a network zone that enables an HTTP proxy.
  • Select Default to use the default network zone proxy configuration. If no default is network zone is defined, transfers from this transfer site fail.
  • Select a specific network zone to use the proxy configuration defined for that zone.

For more information, see Specify TM Server communication ports and IP address for protocol servers on SecureTransport Edge.

Enable FIPS Transfer Mode

Restrict AS2 to use only FIPS 140-2 Level 1 certified cryptographic libraries.

The sender and the recipient must use the ciphers and ciphers suites listed in FIPS transfer mode. If the sender and the recipient do not provide the required ciphers and ciphers suites SecureTransport does not complete the transfer.

Signing Certificate (Optional) The alias that represents the user or partner certificate used to sign a message from this site.
Encryption Certificate (Optional) The alias that represents the user or partner certificate used to encrypt a message from this site.
Email The email address used to receive information from SecureTransport Server. You cannot enter spaces-only values in this field. For more information, see Spaces in required fields.
  * Each AS2 transfer site must have a unique combination of SecureTransport Server AS2 Name and Remote Site AS2 Name.

The following table describes the AS2 send and receive properties for a transfer site.

Field Description
Send Options
Send File As Select the check box to specify a file name. You can use the expression language to specify the criteria you want to match. The expression uses the criteria provided to create a new file name from the original file name. When you enter a new file name in this field, the AS2 message header uses the new name as the value for original filename.
Subject The MIME subject to be used for outgoing messages.
Mimetype The MIME type to be used for outgoing messages. For example, application/edi-x12.
Timeout Transfer After x Minutes The number of minutes after which a transfer is timed out if it is not successful.
Sign Using The algorithm to be used to sign messages from this site.
Encrypt Using

The algorithm used to encrypt messages from this site.

The RC2/40, RC2/64 and RC2/128 algorithms are not FIPS compliant.

Compress Select this check box to enable compression.
Enable Chunking Select this check box to enable chunking.
Request receipts for all Transfers Select this check box to request receipts for all transfers.
Require Signed Receipt If you select the Request receipts for all transfers check box, select the check box to require those receipts to be signed.
 Request:
Synchronous
Asynchronous

Specify whether you want receipts to be synchronous or asynchronous. If you select asynchronous receipts, specify whether you want to receive those receipts via HTTP or HTTPS.

If you request receipts via asynchronous HTTP and you specify that an SSL connection in Receive Options, you receive receipts via HTTPS instead of HTTP.

Receive Options
Receive File As

Select the check box to specify a file name. You can use the expression language to specify the criteria you want to match. The expression uses the criteria provided to create a new file name from the original file name when the transfer is received. You can use the SecureTransport-specific variable ${stenv.rawsource} which takes the value from the original filename in the AS2 message header. See Expression Language for information on SecureTransport-specific variables.

Require SSL Connection

Select this check box to require an SSL connection for transfers received.

If you request receipts via asynchronous HTTP and you specify that an SSL connection, you receive receipts via HTTPS instead of HTTP.

Require Signature Select this check box to require transfers received to be signed.
Require Encryption Select this check box to require transfers received to be encrypted.
Note Use a subscription to a Basic application or a Site Mailbox application to process files received by an AS2 transfer site.
When using asynchronous receipts for outgoing AS2 transfers, post-transmission actions execute, even if the AS2 transfer has failed. This occurs because the transfer initially reports success, triggering the post-transmission action. After the post-transmission action is triggered, an asynchronous failure message is returned, causing the transfer to fail.

Related topics:

Related Links