Upgrade - Viper or Agent on Linux with Sudo / Root Access

Overview

The vFunction Controller keeps a backup of environmentally-specific files in $BASE_DIRECTORY/vfunction/etc/sysconfig/vfunction/installation/backup/. These backup files are then copied back into the default location during the upgrade process. Because this backup-and-copy process is in place, no manual steps are required to keep backups of files before the upgrade occurs.

Upgrade Steps

  1. Download the vFunction Controller Sudoless package from the vFunction Portal
  2. SCP the Controller TGZ package to the VM to the location where vFunction was previously installed, such as $BASE_DIRECTORY
  3. Change owernship of the Controller TGZ package to match the user who performed the original installation
  • Find-and-replace $INSTALLING_USER with the user who will perform the install
  • Find-and-replace $INSTALLING_GROUP with the group to which the user is assigned
  • Find-and-replace $VERSION with the release version, such as “3.6.1449”
chown $INSTALLING_USER:$INSTALLING_GROUP vfunction-controller-sudo-less-installation.v$VERSION.tgz
  1. Switch the user to the be logged in as the user who originally performed the installation
  2. Move to the location where vFunction was previously installed, such as $BASE_DIRECTORY
  • Find-and-replace $BASE_DIRECTORY with the path to the vFunction installation, such as /home/peter
cd $BASE_DIRECTORY
  1. Unpack the Controller TGZ package
  • Find-and-replace $VERSION with the release version, such as “3.6.1449”
tar -xvzf vfunction-controller-sudo-less-installation.v$VERSION.tgz
  1. Find the vFunction instance running in the environment
ps -ef | grep vf | grep instance
  1. Run the Upgrade Script
  • Find-and-replace $BASE_DIRECTORY with the path to the vFunction installation, such as /home/peter
  • Find-and-replace $INSTANCE_NAME with the name of the vFunction instance, such as “default-java”
bash $BASE_DIRECTORY/vfunction/opt/vfunction/controller-installation/upgrade.sh -i $INSTANCE_NAME
  1. If applicable, restart the Application to ensure that the vFunction Agent that is hooked into the Application is the newly upgraded version
  2. If any issues arise, check the list of Known Issues
  3. If the current issue is a new issue and no solution is available in the Known Issues, follow the General Troubleshooting steps

Updated on 08 Aug 2024