Introduction
Thanks for choosing Aspera and welcome to the world of unbelievably fast and secure data transfer.
Get Started with an Aspera Transfer Server
As a server, HSTE is a remote endpoint that accepts authenticated connections from Aspera client applications and that participates as a source or destination for authorized transfers. Your server can also take the role of a client and connect to other Aspera servers to initiate transfers. The following steps describe how to prepare your system as a server.
Get Started as a Transfer Client
Aspera transfer clients connect to a remote Aspera transfer server and request a transfer with that server. Your Aspera application can be used as a client to initiate transfers with Aspera servers, as described in the following steps.
Comparison of Aspera File Delivery and Synchronization Tools
Your Aspera product includes several transfer tools that can be used for automatic file delivery and synchronization.
Installation and Upgrades
Before you install the current release, review the following information about hardware and software requirements, system preparation for upgrades or downgrades, installation instructions, and product security configuration.
Server Set up Methods
Users, groups, and transfers can be configured in several ways, all of which modify the server configuration file aspera.conf .
Set up Users in the GUI
Aspera clients connect to HSTE by authenticating as a system user who is configured in the application. Users can be set up in the HSTE GUI.
Configure HSTE in the GUI
The following references describe the server settings that can be configured in the HSTE GUI. Not all settings are available in the GUI; some must be set by using the command line or directly editing the HSTE configuration file, aspera.conf .
Set up Users and Groups from the Command Line
Aspera clients connect to HSTE by authenticating as a system user who is configured in the application. Users can be set up by running asconfigurator commands or directly editing the configuration file, aspera.conf .
Configure the Server from the Command Line
The following references describe the server settings that can be configured for HSTE by using the command line or directly editing the HSTE configuration file, aspera.conf .
Secrets Management with askmscli
The askmscli tool can be used to securely manage secrets and keys that can pose a security risk when stored on machines in plain-text format.
Transfer Files in the GUI
Use the HSTE pDesktop Client GUI to create connections to Aspera servers, configure transfer settings, set up transfer notifications, and start, stop, pause, and schedule transfers.
ascp: Transferring from the Command Line
Ascp is a scriptable FASP transfer binary that enables you to transfer to and from Aspera transfer servers to which you have authentication credentials. Transfer settings are customizable and can include file manipulation on the source or destination, filtering of the source content, and client-side encryption-at-rest.
ascp4: Transferring from the Command Line
Ascp4 is a FASP transfer binary similar to Ascp but it has different strengths as well as capabilities that are unavailable with Ascp.
Automated Execution of Lua Scripts with Transfer Events
Lua is embedded in Ascp and Ascp4, and HSTE can be configured to execute custom Lua scripts automatically at specific transfer events. In addition, Lua functions that can be used for monitoring and managing transfer sessions are provided by Ascp and Ascp4.
Aspera Watch Service and Watch Folders
Aspera Sync
A complete guide to IBM Aspera Sync .
Set up HSTE for Node API
HSTE must be configured in order to use the Aspera Node API. You can use the asnodeadmin tool to set up the server and manage the Node API. The Node API uses a Redis database, which can be backed up and restored in different ways, depending on what information you need to preserve.
Authentication and Authorization
Asconfigurator Reference
Troubleshooting
Solutions to common problems.
Appendix