This guide is targeted for technical staff responsible for the installation and upgrading of Quality Management Suite. Described procedures cover single server deployment. For the upgrading of cluster deployment, please refer to Genesys Tech Support.
Before You Start
- Check your license is valid for the upgrade. For major upgrades request a new license at Genesys Tech Support.
- Check that your Java version and browser are supported (see System Requirements for Web UI).
- Download the ISO file of the version you desire to upgrade to at Genesys Tech Support and verify the ISO file integrity.
- Check that you have root access to the server.
- Check that you have physical or console access (such as integrated Lights-out) to the server – for upgrades that require a server reboot.
Determine Your Upgrade Method
There are several factors that will determine your choice of upgrade method, if you:
- Have a cluster deployment you should contact Genesys Tech Support for help.
- Are upgrading to a minor version (for example 8.1.513 to 8.1.514) you should upgrade manually.
- Are upgrading from any previous supported version (8.1.480 / 8.1.490 / 8.1.500 / 8.1.510) to a major newer version you should use the upgrade script. If you experience a failure of the upgrade script due to the server custom configuration, you should upgrade manually.
- Are upgrading from a version 8.1.470 and older you will need to freshly install the software.
- Are upgrading from a 32bit to a 64bit operating system you will need to freshly install the software.
Required knowledge
- Genesys Quality Management Suite features and functionality
- RedHat Enterprise Linux or CentOS Linux installation and configuration
- Linux system administration
- Network administration
Reduce downtime after upgrade
For a large database dump with a limited downtime window, you can migrate your database later. This way, you can start to record right after you upgrade your system and Genesys Quality Management Suite packages on a newly created database. Later, you can restore your database to a second parallel database on the background. The restore process can take many hours or days. When this process finishes, switch the databases. This takes 15 – 20 minutes of downtime. Afterwards, migrate the calls you have on the new database.