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.
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
Upgrading Management Layer Server Components
- When upgrading a Management Layer server component, you must stop it using the Management Layer (using Genesys Administrator), to prevent it from being restarted during the upgrade process.
- Use the Management Layer to prevent them from being restarted during the upgrade process to start the components, except when a single Solution Control Server (SCS) (not part of an HA pair) is being upgraded. In this case, start SCS using the appropriate operating system commands on its host, and then confirm that Genesys Administrator can reconnect to this SCS.
Use the following procedure to upgrade Management Layer Server Components.[+] Show procedure
Upgrading Configuration Server
- Do not enable any new features of Configuration Server until you finish upgrading all Configuration Server Proxies to the version that supports the new features.
- Both Configuration Servers configured as an HA pair must be running the same version when migration is complete. If there are requirements for related components (such as DB Server), upgrade those components first.
Preserve the legacy Configuration Database for some period of time to ensure rollback is possible, if needed. Rollback can be carried out using the same sequence of steps if the legacy Configuration Server was 8.5; for older servers, it is required to shut down both currently running servers in the master Configuration Server pair before starting any previous version.
- Client sessions are not preserved between older and newer versions of servers when upgrading the database. There might be other cases when session restoration will not work during upgrade – refer to the Release Notes of the particular version.
- During the upgrade procedure, the Configuration Server environment remains read-only and the master Configuration Server is not redundant until the new server is fully initialized.
- During upgrade, SCS might not be able to switch over applications as long as it is configured to accommodate the startup of new Configuration Servers, or it might not be able to control applications on the host of the newly installed Configuration Server if LCA was shut down using the previous steps.
- All new Installation Packages have been delivered to the relevant hosts and are ready to be installed.
- The latest version of LCA is installed on the Сonfiguration Server hosts.
- The latest version of SCS is deployed in the environment.
Upgrading a Standalone Configuration Server
Use the following procedure to upgrade a standalone Configuration Server.[+] Show procedure
Upgrading an HA Pair of Configuration Servers
If you want to upgrade to 8.5.101 an HA pair of Configuration Servers running version 8.1.3 against a Configuration Database with an 8.1.1 schema, you can upgrade the two servers without losing or interfering with any of the backup functionality. Use the following procedure:[+] Show procedure
If you just want to upgrade the HA pair to an 8.5 Configuration Server from an 8.1 version or an earlier 8.5 version, regardless of whether they are using the same Configuration Database schema, use the following procedure:[+] Show procedure
Upgrading a Configuration Server Proxy
To upgrade Configuration Server Proxies, if any, use the previous procedures, depending on how they are configured—as standalone Configuration Server Proxies or in HA pairs. In either case, note the following exceptions to the referenced procedures:
- If the master Configuration Server 8.1.3 is using the Configuration Database in single-language mode, both primary and backup instances of Configuration Server Proxy 8.5 can, during migration, start and operate against Configuration Server 8.1.3. In all other cases, you must upgrade the master Configuration Server before any of its associated Configuration Server Proxies.
- You do not need to put the configuration environment into read-only mode, but Genesys strongly recommends that you ensure no updates are pending and/or scheduled.
- You do not need to copy any *.conf files from one folder to another when preparing new instances.
- You might want to back up configuration options of individual Configuration Server objects using Genesys Administrator, by selecting the Application object’s options and exporting them into XML.
- When installing the new Configuration Server Proxy instance for upgrade purposes, you must specify the same Application object name as that of the instance being replaced, and perform all configuration (using the master Configuration Server) using the options of that Application object.
Rolling Back Configuration Server
If you need to return to a previously stable version of Configuration Server, an installed but inactive old instance should be used to boot up the stable version. If rollback of both the master and Configuration Server Proxy are required, the rollback order depends on the operational state of the master, as follows: