Product Setup

Important: If this is a product upgrade, review all prerequisites described in Before Upgrading or Downgrading.

To install Enterprise Server, log into your computer with root permissions, and follow the steps below.

Download the IBM Aspera product installer.
Use the credentials provided to your organization by Aspera (not your personal Aspera ID) to access:
http://downloads.asperasoft.com/en/downloads/1

If you need help determining your firm's access credentials, contact your Aspera account manager.
For product upgrades, ensure you have prepared your machine to upgrade to a newer version.
Although the installer performs your upgrade automatically, Aspera highly recommends completing the tasks described in Before Upgrading or Downgrading. If you do not follow these steps, you risk installation errors or losing your configuration settings.

Run the installer

To run the installer, run the following commands with the proper administrative permissions. Replace the product version accordingly.

OS	Commands
RedHat, zLinux, CentOS	$ rpm -Uvh aspera-`entsrv`-`version`.rpm
Debian	$ dpkg -i aspera-`entsrv`-`version`.deb

Install the license.
The license can be installed using the GUI or from the command line.
- GUI: Launch the application by running the following command as root:
```
# asperascp
```
  If this is a fresh install, an Enter License window appears. Either click Import License File and select the license file, or click Paste License Text to copy-and-paste the license file's content. The license information will appear in the window. Verify that it is correct and click Close.
- Terminal: 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:
```
$ ascp -A
```
If you are updating your product license after the installation, see Updating the Product License.
Review or update OpenSSH authentication methods.
Open your SSH Server configuration file from /etc/ssh/sshd_config with a text editor.
To allow public key authentication, set PubkeyAuthentication to yes. To allow password authentication, set PasswordAuthentication to yes, for example:
```
...
PubkeyAuthentication yes
PasswordAuthentication yes
...
```
Save the file then run the following to reload SSH:

RedHat
```
$ sudo service sshd restart
```
Debian
```
$ sudo /etc/init.d/ssh restart
```
To further secure your SSH Server, see Securing Your SSH Server.
Troubleshooting
If the installer freezes during installation, another Aspera product might be running on your computer. To stop all FASP transfer-related applications and connections, see Before Upgrading or Downgrading.

Upgrade Follow up

If not using, disable the Aspera Watch Service.
On an upgrade, the Aspera Watch Service is automatically enabled and a Watchfolder instance is automatically started as the default user (root). If you do not plan to use these services, you can disable them by running the following commands to retrieve the service ids and disable them. This stops Watch Service logging that otherwise continues in the backgournd.
```
# /opt/aspera/bin/asrun send -g
```
The output will look similar to the following:
```
[asrun send] code=0, body={"services":[{"id":"52ca847a-6981-47e1-9f9b-b661cf298af1","configuration":{"enabled":true,"run_as":{"user":"root"},"type":"WATCHD"},"state":"RUNNING","state_changed_at":"2016-10-20T19:14:34Z"},{"id":"root","configuration":{"enabled":true,"run_as":{"user":"root"},"type":"WATCHFOLDERD"},"state":"RUNNING","state_changed_at":"2016-10-20T00:11:19Z"}
```
In the resulting output, find the IDs for the Watch Service and Watchfolder instances. You can identify the asperawatchd service by searching for the string "type":"WATCHD" and, before this entry in the output, locate the string following "id". You can identify the asperawatchfolderd service by searching for the string: "type":"WATCHFOLDERD". The ID for the asperawatchfolderd service is generally the name of the user running the service.

To disable the services, run the following command for both the asperawatchd service id and the asperawatchfolderd service id:
```
# /opt/aspera/bin/asrun send --disable watch_service_id
```
For example, using the output shown above:
```
# /opt/aspera/bin/asrun send --disable 52ca847a-6981-47e1-9f9b-b661cf298af1
# /opt/aspera/bin/asrun send --disable root
```
The first command disables the Watch Service instance and the second disables the Watchfolder instance.
If you are updating a Files node, restore the Files data to the Redis database.
1. Stop the Aspera NodeD service.
  Stop the Aspera NodeD service by running the following command:
```
# /etc/init.d/asperanoded stop
```
2. Flush existing data from the Redis database on the new node.
```
#/opt/aspera/bin/asredis -p 31415 FLUSHALL
```
3. Load the backup database file into the new node database.
```
# cat appendonly.aof | /opt/aspera/bin/asredis --pipe -p 31415
```
4. Restart the Aspera NodeD service.
  Start the Aspera NodeD service by running the following command:
```
# /etc/init.d/asperanoded start
```
If the Redis database is run on another system: Update the KV store keys to the latest format.
The local Redis database schema is automatically updated by the installer, but non-local Redis databases must be manually updated by running the following command as root:
```
# /opt/aspera/bin/asnodeadmin --db-update
```
For all upgrades: Validate aspera.conf.
The aspera.conf file is not overwritten during an upgrade and your configurations are preserved. However, the XML formatting, parameters, and acceptable values may have changed between your old version and new version. Run the following command to check aspera.conf for XML form and valid configuration settings:
```
# /opt/aspera/bin/asuserdata -v
```

Parent topic: Installation and Upgrades