Get Started As A Transfer Client - IBM Aspera HST Admin Manual

b) If you prefer to have your users authenticate to the server using SSH keys rather than with passwords, gather
their public keys and install them on the server. For instructions, see
Server on page 38.
5. Configure transfer settings and control bandwidth usage.
Aspera FASP transfers can be configured globally, by group, or by user. You can set bandwidth caps and limit
the total number of transfers. For more information on user-specific settings, see
Configuration on page 69.
You can also set "virtual" bandwidth caps that can be assigned to incoming or outgoing transfers by group or
by user. For more information, see
58.
6. Set up file validation and processing, if needed.
You can protect your server against malicious software in uploaded files by using out-of-line file validation or
inline file validation. For more information, see
Validation on page 83.
You can configure your server to run other customized scripts when an individual file transfer starts or stops, or
when a transfer session starts or stops. For more information, see
90.
7. Test that a remote client can access and transfer with your server.
For instructions, see
topics in Troubleshooting
Once you confirm that remote clients can access your server, your basic server set up is complete.
• If you want to automatically distribute files and folders to clients when they are added to a specific folder on the
server, see Introduction to Watch Folders and the Aspera Watch Service
• If you want to enable server-based clients to synchronize files with your server, with the ability to synchronize
bidirectionally, see

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.
1. Test a locally-initiated transfer to the Aspera demonstration server to confirm your installation and firewall
configuration are operational.
For instructions, see
how to set up a connection with a server and transfer.
2. If you need to authenticate to the remote server with an SSH key, create an SSH key and send the public key to the
server admin.
For instructions on creating an SSH key, see
3. To run transfers from the command line, review the instructions for the Aspera command line client.
Your Aspera product comes with two command line clients: ascp and A4. They are similar but have different
capabilities. For a comparison, see
• For more information about ascp, see
on page 114.
• For more information about A4, see
page 153.
Once you confirm that you can transfer with your server, your basic set up is complete.
• If you want to automatically distribute files and folders to clients when they are added to a specific folder on the
server, see Introduction to Watch Folders and the Aspera Watch Service
Controlling Bandwidth Usage with Virtual Links (Command Line)
Testing a User-Initiated Remote Transfer
on page 329.
Aspera Sync on page 218.
Testing a Locally Initiated Transfer
Creating SSH Keys
Comparison of Ascp and Ascp 4 Options
Ascp Command Reference
Ascp 4 Command Reference
Setting Up a User's Public Key on the
Out-of-Transfer File Validation
File Pre- and Post-Processing (Prepost)
on page 39. If you have problems, review the
on page 159.
on page 20. This provides a simple walk through of
on page 133.
on page 99 and
on page 144 and
on page 159.
| Get Started as a Transfer Client | 10
aspera.conf - Transfer Server
on page
on page 80 and Inline File
on page 138.
Ascp General Examples
Ascp 4 Examples
on page
on