The following packages handle specific SecureTransport functionality.

The following topics describe the other Transaction Manager rules packages:

Related topics:


Use this package to archive transferred files. This package is enabled by default. The package copies each transferred file to the archive directory specified in the global File Archiving configuration page. Copied files are renamed to a unique file name to avoid duplicates. The file name format is:


For example:


The location of the files is as follows:



  • archive_folder - The archive folder location configured in the global File Archiving configuration page.
  • account_name - Name of the account who performed the transfer. When there's no account (for LDAP users for example), account_name has value of NO_ACCOUNT.
  • login_name - Login name for the user who performed the transfer.
  • relative_path_to_file - Path to the file relative to the account's home folder.

For more information, see Create an Archive Maintenance application and File archiving global configuration .

Axway Sentinel

This package is enabled by default. SecureTransport uses it to send file transfer and processing events to Axway Sentinel and to call the agent used in a Axway Sentinel Link Data Maintenance application. For more information about configuring SecureTransport to send events to Sentinel, see Integrate Axway Sentinel.


Enable this package when you want to create and use a Connect:Direct transfer site. This package is disabled by default. For more information, see Connect:Direct transfer sites.


This package is used to implement transfers initiated by SecureTransport using a file services interface protocol.


This package is used to implement anti-virus or DLP scans initiated by SecureTransport using external ICAP servers. The package is disabled by default and must be enabled if ICAP servers are configured.


This package provides functionality to generate MDN receipts for the transferred files. The package is enabled by default.

Note To generate MDN receipts, create an mdn certificate in addition to enabling the MDNReceipting package. For more information about the mdn certificate, see Certificates to generate during initial setup.

Pesit and PesitTransfer

These packages provide the functionality for PeSIT protocol operations, including authentication, server-initiated transfers, client-initiated transfers, routed transfers, and acknowledgments. They are enabled by default.


This package handles PGP encryption and decryption when Advanced Routing is not used. The package is enabled by default.


This package contains rules for canceling events. It is enabled by default.


Use this package when you want to upload files to a specific site without subscribing an account to an application. This package is disabled by default. This package is used with the Send Files Directly To option. For details, see Subscribe an account to an application.

In order to use SendToSite package, enable it and modify its content. For example, by adding a transfer site name as a value to the Site parameter. For details, refer to Manage rules packages.


This package implements HTML email notification for file transfers. This package is disabled by default. For more information, see Velocity email notification package.


This package implements SNMP notifications for failed transfers. This package is disabled by default.

SecureTransport includes support for Simple Network Management Protocol (SNMP) v2 and v3 to help you monitor failed transfers. SecureTransport works with SNMP managers such as Hewlett-Packard OpenView Network Node Manager. You can send messages when file transfers fail after retrying the transfer the number of times allotted. SecureTransport provides a trap MIB file located at <FILEDRIVEHOME>/conf/Transfer.mib.

  1. Select Operations > Server Configuration.
  2. The Server Configuration page is displayed.
  3. Search for TransactionManager.SNMP.enabled and change the value to true.
  4. Search for TransactionManager.SNMP.ManagerHost and change the value to the IP address of the SNMP manager.
  5. Search for TransactionManager.SNMP.ManagerPort and change the value to the port of the SNMP manager.
  6. Set the other TransactionManager.SNMP.* server configuration parameters as required by your SNMP manager and configuration
  7. Select Setup > TM Settings.
  8. The Rules Packages page is displayed.
  9. Click Enable SNMPTransferNotify.
  10. Select Operations > Server Control.
  11. Restart the TM Server.
  12. Repeat steps 6 through 9 on each server in your cluster.


This package supports the REST web service file transfer API.

Related Links