Performing the App Visibility server upgrade silently
This topic presents upgrade procedures for the App Visibility server from version 10.0 to the current version. You can upgrade App Visibility components using the silent upgrade procedure, as described in this topic, and deploy the silent upgrade to several computers, or you can upgrade using the upgrade wizard.
When you run the silent installation, only the App Visibility component or components that are on the computer are upgraded. After you upgrade components, you can run the silent installation to install components that are not on the computer.
Upgrade from an earlier version
To upgrade from a version earlier than 10.0, first upgrade to version 10.0
.
The App Visibility portal and collector upgrade processes include a database migration, which moves data from the previous App Visibility database, to the current PostgreSQL App Visibility database.
The following topics are presented:
Before you begin
- Download the installation files from the Electronic Product Distribution site to a temporary directory on the App Visibility server computer.
- Ensure that you have completed all tasks described in the Preparing-for-the-App-Visibility-server-installation.
Complete the tasks in Preparing-for-an-App-Visibility-upgrade-and-checking-compatibility topic, ensuring that you back up the database and and customized agent policies.
To upgrade the App Visibility server silently
- In a command line, navigate to the \ADOPServer\Disk1 folder in the installation file structure.
- Open the downloaded options file in a text editor:
- (Windows) adop-silent-option-upgrade.txt
- (Linux) adop-silent-option-upgrade
Enter the encrypted root password for the MySQL Database to remove the database tables.
If the root password was not changed since installation, do not change the entered password.
Enter the PostgreSQL database port number for the db_port parameter.
The port number cannot be the same as the current MySQL database port (default 3301).
The default port number for the PostgreSQL database is 8800.
Determine whether you want to enable the upgrade process to continue if the database migration encounters a warning.
The default value (yes) enables the process to continue.
Change the value to no to stop the process and return to the previous version.
# Database Migration continue on warning
-J db_migration_continue_on_warning=yesIf the database migration encounters an error, the upgrade process stops and returns to the previous version.
- Save and close the upgrade options file.
To run the silent upgrade, enter the following command:
Windows
setup.exe -i silent -DOPTIONS_FILE=<fullFilePath>\adop-silent-option-upgrade.txtLinux
./setup.bin -i silent -DOPTIONS_FILE=<fullFilePath>/adop-silent-option-upgrade
Encrypting the password for silent App Visibility server upgrade
The Maintenance Tool enables you to retrieve an encrypted password, which the App Visibility server upgrade utility requires to access the MySQL database. You must use an encrypted password so that it is not exposed in the upgrade options file.
You can run the Maintenance Tool in a GUI or from the command line interface (CLI):
To adjust the App Visibility portal database size
After you upgrade the App Visibility portal to version 10.1.00, you can adjust the maximum database size (db.max.size). The upgrade utility always sets the default value to 102400 MB (100 GB).
Use the following procedure to reset the maximum database size:
On the computer where the App Visibility portal is installed, open the portal.properties file located in the following directory:
- Windows
installationDirectory\portal\properties
- Linux
installationDirectory/portal/properties
- Windows
- Edit the db.max.size value, in megabytes.
- Save the portal.properties file and restart the portal service.
Where to go from here
After you upgrade the App Visibility server components, do the following:
Related topics
Upgrading-App-Visibility-agents-for-Java
Upgrading-App-Visibility-agents-for-NET
Changing-App-Visibility-collector-settings
Changing-App-Visibility-portal-settings
Changing-App-Visibility-proxy-settings