Contents
Upgrading your Installation Package (IP)
This article provides instructions on how to upgrade Web Services from a specific version up to currently available version and describes the steps that should be performed on each node where Web Services are run. The order in which you upgrade Web Services nodes doesn’t matter; you can upgrade all nodes simultaneously or one at a time.
During a migration, we strongly recommend to avoid changes in configuration files if the changes are not required for the migration procedure. Configuration changes can be a cause of failure. In the event of a failure, you will need to rollback to previous version instead of rolling back only the changed options. Thus, changing of customizations should only be performed after verification that the migration to new version completed successfully.
- Since version 8.5.201.29, the Genesys Interaction Recording (GIR) API was discontinued by Web Services and Applications. Thus if you are about migrating to an 8.5.201.29+ version, you have to install separate GIR nodes according to the Genesys Interaction Recording Migration Guide.
- Version 8.5.201.41 supports Cassandra 2.2 database; thus, 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 Cassandra cluster, we recommend to perform this operation separately from the Web Services and Applications migration; not at the same time.
Migrating from 8.5.200.09 to 8.5.201.50
Start
- Install Java 8 on the note according to Migrating from Java 7 to Java 8.
- Migrate from standalone to embedded Jetty.
- Deploy the new version of Web Services.
End
Migrating from 8.5.200.18 to 8.5.201.50
Start
- Install Java 8 on the note according to Migrating from Java 7 to Java 8.
- Deploy the new version of Web Services.
End
Migrating from 8.5.201.29+ to 8.5.201.50
Start
End