Installing Console
About this task
Warning: Due to incompatible common components, IBM Aspera Console and IBM Aspera
Faspex cannot be installed on the same machine. IBM Aspera does not support this
combination.
Perform the following steps as an Administrator (or Domain Administrator if in an Active Directory environment).
Procedure
-
Upgrade to Windows Installer 4 and later.
The Console installer requires Windows Installer 4+ for a successful configuration. You may download the latest version of Windows Installer from the Microsoft website: www.microsoft.com/en-us/download/details.aspx?id=8483
- Download Console installation components. Use the credentials provided by Aspera to download the installer.
-
Run the downloaded installation components.
Double-click the Console installer to start the installation.
Note: If you are running Windows Server with User Account Control (UAC) enabled, run the installation as an administrator. Right-click the installer and click Run as administrator. -
Choose the setup type.
After the Console's End-User License Agreement screen, you should see "Choose Setup Type" with the following two options:
Option Description Typical Install all components required by Console, including the Console application, Ruby, MySQL common files, and Console's MySQL database. Custom Select the components to install. You can use your existing installation of Ruby, MySQL or Console's MySQL database for the new installation. If you select custom install, you can choose components to install in the following screen.

-
Enter the user name and password of the system account used as the Aspera service account.
This account can be either a local account or an Active Directory account. If the Aspera service account is an existing user, enter the user's password. Otherwise, create a new user name and password. By default, the user name is svcAspera.

-
Run the asctl setup command.
Once installation is complete, click Finish. By default, the installer automatically runs the asctlsetup command. If you do not want to run the setup command automatically, clear Launch asctl to continue the Console setup and click Finish.
Note: If Console doesn't automatically run the setup command or an error halts the process, then you can run the command manually, as shown below.> asctl console:setup - Run the post database migration script:
asctl console:rake aspera:db:post_db_migrate - Run the assets precompile:
cd "C:\Program Files (x86)\Aspera\Management Console" "C:\Program Files (x86)\Common Files\Aspera\Common\ruby\bin\ruby.exe" "C:\Program Files (x86)\Aspera\Management Console\bin\rails" assets:precompile RAILS_ENV=production -
When prompted, enter the IP addresses and host names (separated by commas) that
are allowed to access Console.
You can only access the Console web application from an accepted IP address or host name. If you do not include the current IP address, you cannot log into Console.Note: After installation, you can edit the list of accepted IP addresses and host names by modifying AcceptedHosts in the console.rb.yml (C:\Program Files (x86)\Aspera\Management Console\config\console.yml) configuration file. For more information, see Allowing access to Console at defined hostnames.
-
Update the Aspera license from the command line.
Important: For purchasers of Aspera Enterprise, a license enabling Console as part of Enterprise can be downloaded from IBM Fix Central.Console administrators can update the license in the Console web UI, see Logging Into Console for the first time. However, if you are automating Console installation, you can use a rake command to set the license without logging into the web UI.
- Set the license text as an environment
variable.
> set LICENSE_TEXT='<ASPERA_LICENSE> <DETAILS expiration_date=... </KEY> </ASPERA_LICENSE>'In this example, only part of the license text is shown. You must paste the entire license text for the license to be valid.
- Update the Aspera
license:
> asctl console:rake aspera:update_license
- Set the license text as an environment
variable.