Contents
Upgrading Web Services and Applications
This article provides instructions on how to upgrade Web Services and Applications from a specific version up to the currently available version and describes the steps to perform on each node where Web Services and Applications are run. The order in which you upgrade Web Services and Applications nodes doesn’t matter; you can upgrade all nodes simultaneously or one at a time.
During a migration, we strongly recommend to avoid changing the configuration files if the changes are not required for the migration procedure. Configuration changes can cause the migration to fail. In the event of a failure, you will need to rollback to previous version instead of rolling back only the changed options. Thus, you should only change configuration after verification that the migration to new version completed successfully.
- After version 8.5.201.29, support for Genesys Interaction Recording (GIR) API was discontinued by Web Services and Applications. Thus if you are migrating to an 8.5.201.29+ version, you need to install separate GIR nodes according to the instructions in Genesys Interaction Recording Migration Guide.
- Version 8.5.201.41 introduced support for the Cassandra 2.2 database. You have the option to migrate to new Cassandra according to steps are described in Upgrading Cassandra to 2.2. This is not a mandatory step, so you can maintain the Cassandra 1.2 cluster with latest version of Web Services and Applications. If you decide to upgrade the Cassandra cluster, we recommend that you perform this operation separately from the Web Services and Applications migration; not at the same time.
Choose one of the following procedures:
Migrating from 8.5.200.09 to 8.5.201.61
- Stop Web Services and Applications on the node.
- Backup your old installation and configuration files. You might need the files if you need to rollback your upgrade at a later date.
- Install Java 8 on the node according to Migrating from Java 7 to Java 8.
- Deploy the new version of Web Services and Applications.
- Migrate from standalone to embedded Jetty.
- Start Web Services according to Starting and testing.
Migrating from 8.5.200.18 to 8.5.201.61
'
- Stop Web Services and Applications on the node.
- Install Java 8 on the node according to Migrating from Java 7 to Java 8.
- Perform the steps in Migrating from 8.5.201.29+ to 8.5.201.61
Migrating from 8.5.201.29+ to 8.5.201.61
Start
- Stop Web Services and Applications on the node.
- Backup your old installation and configuration files.
- You might need the files if you need to rollback your upgrade at a later date. Make sure to back up the following files if you configured the previous version as a service:
- /etc/init.d/gws
- /etc/default/gws
- Remove the following service initialization scripts from the host:
- /etc/init.d/gws
- /etc/default/gws
- Deploy the new version of Web Services and Applications.
- Copy the following configuration files from the configuration folder in your previous installation into the config folder in the home directory of the new installation:
- application.yaml
- elasticsearch.yml
- hystrix.properties
- logback.xml
- statistics.yaml
- Open the /etc/default/gws file and update the following environment variables to values appropriate for your Web Services node:
- GWS_HOST: This value must match the host value defined in jetty section of the application.yaml file.
- GWS_PORT: This value must match port value that you will define later in jetty section of the application.yaml file.
- Update the application.yaml file with the new path to the logback.xml file.
- Start Web Services according to Starting and testing.
End