Jump to: navigation, search

Upgrading Components

This section defines the order of the steps necessary to upgrade software. You might also consider upgrading the database schema and/or reloading the locale, if necessary, as part of the software upgrade procedure. See the following sections for details of database-related activities.

Important
You do not have to update both the software and the database schema at the same time, unless you want particular new features to work with new software.

Interoperability

There are several items to consider regarding interoperability:

  • When upgrading a configuration environment running in Distributed mode, first upgrade Configuration Server to the newer version, then upgrade all Configuration Server Proxies as soon as possible. Genesys does not support running different versions of Configuration Server components, except during the migration from one version to another. During this phase, different versions of Configuration Server can co-exist in the same environment to ensure minimal downtime; however, do not attempt to enable any new features until you remove older versions of Configuration Server from the environment.
  • When upgrading Configuration Server in Disaster Recovery/Business Continuity mode, make sure you upgrade dormant copies of master Configuration Servers. If the Configuration Database was also upgraded, be sure to replicate the upgraded database before you start any of the dormant instances.
  • License Reporting Manager (LRM) 8.5 is no longer integrated with Configuration Server. If you are upgrading from a configuration environment using LRM 8.5, you must uninstall it. Refer to the LRM Technical Advisory for more information.

Upgrading Local Control Agent

Use the following procedure to upgrade Local Control Agent (LCA).

[+] Show procedure

This page was last edited on June 5, 2017, at 17:52.
Comments or questions about this documentation? Contact us for support!