Product Setup

To install Enterprise Server, log into your computer with root permissions.

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

Download the IBM Aspera product installer.
Use the credentials provided to your organization by Aspera (not your personal Aspera ID) to access:
https://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 /path_to_installer/aspera-entsrv-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-entsrv-version.rpm`
Debian	`$ dpkg -i /path_to_installer/aspera-entsrv-version.deb`

Installation 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.
Install the license or set up your entitlement, depending on your account type (you only do one).
To Install a License:
The license can be installed by 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
```
To update your product license after the installation, see Updating the Product License.
To Set Up an Entitlement:
Run the following commands to start the ALEE service, restart the Aspera NodeD service, and register your entitlement:
```
# /opt/aspera/bin/asalee-config.sh enable
# systemctl restart asperanoded
# /opt/aspera/bin/alee-admin register customer_ID entitlement_ID
```
The output returns the Customer ID and License ID, what type of license is enabled, the license status, and when the license server was last reached.
If you plan to use Watch Folders, enable the services that allow the Aspera RunD service (the service that manages Watch Folders) to automatically start after a reboot.
For Debian OS, run the following commands:
```
# systemctl enable systemd-networkd
# systemctl enable systemd-networkd-wait-online.service
```
For RedHat, zLinux, and CentOS, run the following commands:
```
# systemctl enable NetworkManager
# systemctl enable NetworkManager-wait-online.service
```
Edit OpenSSH authentication methods.
1. Open your SSH Server configuration file from /etc/ssh/sshd_config with a text editor.
2. To allow public key authentication, set PubkeyAuthentication to yes. To allow password authentication, set PasswordAuthentication to yes.
  For example,
```
...
PubkeyAuthentication yes
PasswordAuthentication yes
...
```
3. Save the file then reload the SSH service.
```
$ sudo systemctl restart sshd.service
```
  or for Linux systems that use init.d:
```
$ sudo service sshd restart
```
4. To further secure your SSH Server, see Securing Your SSH Server.
Secure your server or update your existing configuration.

Upgrade Follow up

If you were using the Aspera Watch Service or Watch Folders in version 3.6.1 or earlier, manually migrate any services that are run by a user other than root.
The installer does not automatically migrate Watch or Watch Folder services for users other than root, and you must manually start their services after upgrade:
1. Confirm that the user has a docroot set in aspera.conf.
  To view the user's settings, run:
```
# /opt/aspera/bin/asuserdata -u user
```
  If a value is not set for absolute in the docroot option set section, set a docroot by running the following command:
```
# /opt/aspera/bin/asconfigurator -x "set_user_data;user_name,username;absolute,docroot"
```
2. Confirm that the user has permissions to write to the log directory.
  To view the log directory settings, run:
```
# /opt/aspera/bin/asuserdata -a
```
  Look for the values for rund_log_dir and watch_log_dir. If they are set to "AS_NULL", then the logs write to the default directory (/var/log/messages).
3. Start Watch and Watch Folder services for the user by running the following commands:
```
# /opt/aspera/sbin/asperawatchd --user username
# /opt/aspera/sbin/asperawatchfolderd --user username
```
If you are updating a Files node, restore the Files data to the Redis database.
1. Stop the Aspera NodeD service.
```
# systemctl stop asperanoded
```
  or for Linux systems that use init.d:
```
# service 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 /opt/aspera/bin/appendonly.aof | asredis --pipe -p 31415
```
4. Restart the Aspera NodeD service.
```
# systemctl start asperanoded
```
  or for Linux systems that use init.d:
```
# service 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
```
If you have a backup of modified daemon start up scripts for Aspera Central and Aspera NodeD services, copy your modifications into the new versions of these scripts. Restart the services to activate your changes.
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
```