Upgrading Aginity Premium consists of logging into the server, downloading the latest update and applying it from the command line.
For clarities sake when we refer to aginity-team-<version#>-amd64.deb we purposely leave version# generic. Each upgrade will have a different number associated with it.
Warning
It is important to take a backup of both your encryption key for the
Aginity Premium catalog and to do a Backing Up or Restoring Premium Catalog before upgrading.
This way if anything goes wrong you will not use your catalog. It is also recommended
to do a manual export of your catalog from time to time.
You can get the encryption key using the command below.
sudo cat /etc/aginity-team/service.conf
Step 1: Logging into Aginity Premium Server
SSH into the Premium server as an administrator.
Note
Typically you will log in as an account other than root
and then you will be using the sudo command
Step 2: Check to see if Premium is Currently Running and then Shut it Down
Issue the command below to check the status of the Aginity Premium service
sudo systemctl status aginity-team
If Aginity Premium is running shut it down by issuing this command
sudo systemctl stop aginity-team
Note
It is always a good idea to run the status check again
to make sure Premium has been shut down.
Step 3: Download the Latest Version of Aginity Premium
Using the wget command you can download the latest version as shown below.
wget http://repository.aginity.com.s3.amazonaws.com/AginityTeam/aginity-team-<version#>-amd64.deb
Step 4: Upgrading the Software
Run the upgrade process by issuing this command.
// on Ubuntu
sudo apt-get install aginity-team-<version#>-amd64.deb
// on RHEL
sudo yum install aginity-team-<version#>-amd64.deb
The package manager will determine if your configuration files are different from ones bringing with the new version of the application being installed and will offer you a few option to proceed with installation
You should always keep your currently-installed version and resolve any conflicts by comparing and merging the difference manually.
Step 5: Restart Aginity Premium
Restart the server by issuing this command.
sudo systemctl start aginity-team