Getting Started with the Aspera Trapd Service

When HST Server is installed on a virtual machine in the cloud or other object storage, Trapd is the Aspera service that enables it to write to the object storage (including Hadoop Distributed File System (HDFS)). Trapd is supported in HST Server for Linux 64-bit and Windows 64-bit. The HST Server should be in close proximity to the object storage to minimize latency.

Requirements and Set Up

  • Trapd is included with IBM Aspera On Demand applications and HST Server for Linux 64-bit and Windows 64-bit. Trapd is enabled in Aspera on Demand, but is disabled by default in HST Server. Trapd can be enabled by running the following command:
    # /opt/aspera/bin/astrap-config.sh enable
  • HST Server must be configured to access the object storage. For stand-alone servers, this configuration is typically done when setting the docroot in aspera.conf (see Setting Docroots for Object Storage and HDFS). The Aspera client may also specify the object storage path and credentials as part of the transfer command (see Ascp Transfers with Object Storage and HDFS). For multi-tenant use cases, such as the IBM Aspera Transfer Cluster Manager or IBM Aspera on Cloud (including IBM Aspera on Cloud transfer service), configuration is done as part of creating an access key (see the documentation for those products for more information).

Configuration

For information about configuring Trapd, see General Trap Configuration Reference.

Trapd works with many types of storage and comes packaged with templates of configuration files for all supported storage types. For more information, see the topics relevant to your storage type: