Shared-mode instances on Linux do not need upgrading separately, they update automatically with updates to the instance manager.
ADS can manage instances that are of a similar version, where all parts of the version number are the same except the last. For example ADS version 188.8.131.52 could manage an instance of version 184.108.40.206 or 220.127.116.11, but not of 18.104.22.168.
When you do upgrade instances, do so as the user running AMP (such as
amp on Linux or
AMP on Windows). On Linux, switch to the
amp user by running
sudo su -l amp.
You can run the following command line (on both platforms) to bulk-upgrade all of your AMP instances:
Sometimes you may wish to only update ADS, and then use the web interface to upgrade instances via the right-click context menu:
ampinstmgr upgrade ADS
On Windows, it may be necessary to reboot the system after updating AMP.
It’s not always necessary to upgrade the instance manager with each AMP version (unless using shared instances on Linux). Generally speaking it’s only necessary to do this if the release notes for a given version specifically mention changes to the instance manager tools or the local instance manager (LIM)
On Linux, The AMP instance manager (ampinstmgr) is updated via your distributions package manager:
sudo apt update sudo apt upgrade
This will update all packages on your system. If you want to only update AMP then replace the second command with:
sudo apt upgrade ampinstmgr
sudo yum update
This will update all packages on your system. If you want to only update AMP then run:
sudo yum update ampinstmgr
It is not usually necessary to update the Windows instance manager. We advise against doing this unless there is a particular change that affects you.
- Make sure all instances are fully stopped. You can do this by running
ampinstmgr stopallin the command prompt
- Download a fresh copy of the installer and running the setup as an upgrade.
- Reboot the system