# Genesys Quality Management Suite 8.1.520 : Post Upgrade Tasks

When you successfully finish the upgrade script, access the Call Recording Web GUI at the same URL, with the same user accounts and passwords.

Perform the following tasks before you go live with the installation.

- Ensure correct Call Recording and Quality Manager licenses are uploaded via their respective Web GUIs.
- Re-enter the Maintenance Tool settings in the Web GUI (Settings > Configuration > Maintenance) if you haven't upgraded the configuration files and used the callrec setup to configure them. The callrec-setup script doesn't cover them.
- Ensure that the roles and permissions are set up correctly on the upgraded version (rights are on existing installations during the upgrade). Assign any new roles or permissions included in the newer Genesys Quality Management Suite version to the upgraded Call Recording and Quality Manager applications.
- Restore the saved JavaCIL.jar file from the backup directory to the Call Recording installation:

    mv /home/backup/callrec-backup/ipcc/JavaCIL.jar /opt/callrec/ipcc/
    /opt/callrec/bin/rc.callrec_ipcc restart

## Check that the upgrade is successful

1. Check whether the modules start correctly.
2. Check whether the Web UI is accessible.
3. Check whether calls record.
4. Check whether the tools and other modules are configured correctly and run.
5. Check whether the cron script /var/log/cron runs.
6. Test whether all the Call Recording features work correctly.

## Cluster Upgrade Follow Ups

In case of cluster upgrades perform the following steps:

- Check the status of the CORE service and ensure that it sees all recorder services and decoder services

- Ensure that `--connectionString` parameter of your recorder service is pointing to the proper AMQP server. Open the file /opt/callrec/etc/callrec.derived on the server where your SPANless recorder is running and search for SLR_PARAMS (for Active Recording) and/or RS_PARAMS (for Passive Recording) according to your solution. It should look like the following:

      SLR_PARAMS[1]="--connectionString amqp://192.168.110.35 -t 120 -m 40 -A 0 -A 8 -A 9 -A 18 -A 13 -A 19 -l /etc/callrec/slr.log4cxx.xml"
      RS_PARAMS="--connectionString amqp://192.168.110.35 -t 120 -m 40 -A 0 -A 8 -A 9 -A 18 -A 13 -A 19"

  Where 192.168.110.35 must be replaced by the IP address of your AMQP server

- Check the Recorder Status tab and ensure that you see all your Recorder services there:

  Icon

  More info about usage of status page can be found here - Call Recording Status Overview

## Long-running script to migrate from Genesys Quality Management Suite 8.1.49x to 8.1.50x

After the database upgrades from 8.1.49x to 8.1.50x, run an extra script to convert the required data from the database records. This process is slow. Therefore, plan it properly. Use this script to copy agent identification and couple direction from the fixed external data to the couples table.

This can take a long time, maybe two days, based on the database size. Use the script only if this update is required. We recommend that you run it over the weekend.

We recommend that you drop updated column indexes before you run the script. Re-create them afterwards.

### PostgreSQL

Go to the script directory:

    cd /opt/callrec/dbscripts/postgres/updates/5.0/long_running/

Drop the indices:

    psql -U postgres -d callrec -h localhost -f update_49_update_couples_data_index_drop.sql

Where:

- U specifies the database user name under which you run the script.
- d is the database name.
- h is the host where database is located.
  f defines the file with the update script to execute.

Execute the long-running script in a screen:

    psql -U postgres -d callrec -h localhost -f update_49_update_couples_data.sql

Recreate the indexes:

    psql -U postgres -d callrec -h localhost -f update_49_update_couples_data_index_create.sql

### Oracle

Go to the script directory:

    cd /opt/callrec/dbscripts/oracle/update/5.0/long_running/

Drop the indexes:

    sqlplus system_user/system_passwd@database @update_49_update_couples_data_index_drop.sql

Where:

- system_user is the user with rights to the GQM database.

- system_passwd is this user's password.

- database is the name of database (mostly Call Recording) to modify.

Execute the long-running script in a screen:

    sqlplus system_user/system_passwd@database @update_49_update_couples_data.sql

Recreate the indexes:

    sqlplus system_user/system_passwd@database @update_49_update_couples_data_index_create.sql