Installation

Streaming for Video is installed as a specially-licensed IBM High-Speed Transfer Endpoint (formerly Aspera Point-to-Point Client) with limited GUI capabilities.

Important: If this is a product upgrade, review all prerequisites described in "Before Upgrading or Downgrading" in the IBM Aspera High-Speed Transfer Endpoint Admin Guide.

Download the installer from the Aspera website.
Use the credentials provided to your organization by Aspera to access:
http://downloads.asperasoft.com/en/downloads/60

If you need help determining your firm's access credentials, contact your Aspera account manager.

Install the product.

Run the following command, depending on your operating system.

OS	Command
RedHat, CentOS	`$ rpm -Uvh aspera-scp-p2p-fs-version.rpm` Note: If your Linux OS is a minimal clean system, ensure that all the required dependencies are installed with your Aspera application by installing the product with a yum install: `$ yum --nogpgcheck install /path_to_installer/aspera-scp-p2p-version.rpm`
Debian	`$ dpkg -i aspera-scp-p2p-fs-version.deb`

Install the license.
Create the following file:
```
/opt/aspera/etc/aspera-license
```
Copy and paste your license key string into it, then save and close the file. To verify the license information, run the following command:
```
$ ascp4 -A
```
Prepare your computer as a Streaming for Video sender (client) or receiver (server).
Download or open the IBM Aspera High-Speed Transfer Endpoint Admin Guide for your OS and use it as a reference for the following preparation steps.
If your computer is a Streaming for Video receiver (server):
1. Configure the firewall (see "Configuring Your Firewall").
2. Change and secure the TCP port (see "Securing Your SSH Server").
3. Add a user and configure their access.
  The Streaming for Video sender authenticates to the receiver by using operating system accounts on the receiver. For example, if the sender user, "marketing_mgr" wants to send a stream to the receiver server, add marketing_mgr as a system user on the receiver. To secure your receiver, restrict marketing_mgr's access to only certain directories on the server (set a docroot), set transfer permissions, and set the default shell as aspshell. For instructions, see "Setting Up Users" to set up a user in the GUI, or "Setting Up Transfer Users (Terminal)" to set up a user from the command line.
  Note: Multicast-to-multicast transfers must be authenticated by a transfer user who does not have a docroot configured in aspera.conf. For instructions, see Streaming for Video Command Syntax.
4. Set up the user's public key on the receiver.
  Aspera recommends using SSH key authentication. Have the user on the sender create an SSH private-public key pair and send the public key to the admin of the receiver. Then follow the instructions in "Setting Up a User's Public Key on the Server."
5. If you are sending or receiving a multicast video stream with a macOS server, and do not want to use the default interface (en0), configure the new interface.
  For instructions, see Configuring Mac OS X Server for Multicast Streams.
6. For a complete overview of Aspera-recommended security settings, see "Aspera Ecosystem Security Best Practices".
If your computer is a Streaming for Video sender (client):
1. Configure the firewall (see "Configuring Your Firewall").
2. If you need to authenticate to the receiver with an SSH key, create an SSH key and send the public key to the receiver admin.
  For instructions on creating an SSH key, see "Creating SSH Keys in the GUI" or "Creating SSH Keys (Command Line)."

To uninstall Streaming for Video, follow the instructions in "Uninstalling" in the IBM Aspera High-Speed Transfer Endpoint Admin Guide.