Jump to: navigation, search
(→‎Migrating from 8.5.200.18 or later to the current version)
 
(104 intermediate revisions by 9 users not shown)
Line 1: Line 1:
−
= Migrating your Installation Package (IP)=
+
= Upgrading Web Services and Applications=
  
−
If you have [[MigPreparation|prepared for your migration]], you can now migrate the Web Services and Application IP. Use the instructions that are specific to the version from which you migrating:
+
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.
  
−
* [[MigMigrateIPProc#Mig_09|Migrating from 8.5.200.09 to the current version]]
+
During a migration, we strongly recommend to avoid changing the configuration files if the changes are not required by 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. You should only change configuration after verification that the migration to new version completed successfully.
−
* [[MigMigrateIPProc#Mig_18_29_41|Migrating from 8.5.200.18 or later to the current version]]
 
  
 +
Choose one of the following procedures:
 +
* [[Documentation:HTCC:MIG:UpgradeFrom87|Upgrading from 8.5.202.87 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom86|Upgrading from 8.5.202.86 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom81|Upgrading from 8.5.202.81 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom77|Upgrading from 8.5.202.77 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom71|Upgrading from 8.5.202.71 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom69|Upgrading from 8.5.202.69 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom54|Upgrading from 8.5.202.54 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom50|Upgrading from 8.5.202.50 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom40|Upgrading from 8.5.202.40 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom34|Upgrading from 8.5.202.34 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom23|Upgrading from 8.5.202.23 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom04|Upgrading from 8.5.202.04 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom92|Upgrading from 8.5.201.92 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom84|Upgrading from 8.5.201.84 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom68or76|Upgrading from 8.5.201.68 or 8.5.201.76 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom61|Upgrading from 8.5.201.61 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom41or50|Upgrading from 8.5.201.41 or 8.5.201.50 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom29plus|Upgrading from 8.5.201.29 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom18|Upgrading from 8.5.201.18 to 8.5.203.03]]
 +
* [[Documentation:HTCC:MIG:UpgradeFrom09|Upgrading from 8.5.201.09 to 8.5.203.03]]
  
−
{{AnchorDiv|Mig_09}}
+
{{NoteFormat|
−
==Migrating from 8.5.200.09 to the current version==
+
* If you are a  Genesys Interaction Recording (GIR) customer and you are migrating Web Services and Applications 8.5.201.09 or 8.5.201.18, refer to [[Documentation:CR:Migration:Welcome|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 [[Documentation:HTCC:Dep:UpgradingCassandraTo2x|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.
−
Migrating from 8.5.200.09 has special considerations, because it includes a transition from standalone Jetty to embedded Jetty.
 
−
 
 
−
'''Start'''
 
−
<ol>
 
−
<li>Stop Jetty on all the Web Services nodes.</li>
 
−
<li>[[MigThirdParty#MigrateCassandra|Migrate Cassandra]].
 
−
<li>For each Web Services node, complete the following steps:
 
−
<ol type="a">
 
−
<li>Complete the [[MigThirdParty#EmbeddedJetty|How do upgrade from standalone to embedded Jetty?]] procedure.</li>
 
−
{{NoteFormat|Make a backup of your configuration folder ('''$JETTY_HOME/genconfig''') to use as a reference for setting configuration options.|2}}
 
−
<li>Review [[Documentation:HTCC:Dep:ConfigurationPremise|Configuring Web Services]] and its sub-topics.</li>
 
−
<li>Set the options required for your deployment.
 
−
<br/>
 
−
The following configuration options have been modified in the '''$JETTY_HOME/genconfig/server-settings.yaml''' file in 8.5.200.50:
 
−
 
 
−
{|
 
−
! '''Option'''
 
−
! '''Type of Change'''
 
−
|-
 
−
| activationTimeout
 
−
| The default value changed from <tt>1000</tt> to <tt>12000</tt>.
 
−
|-
 
−
| connectionTimeout
 
−
| The default value changed from <tt>400</tt> to <tt>4000</tt>.
 
−
|-
 
−
| cmeAuthenticationEnabled
 
−
| Removed
 
−
|}
 
−
</li>
 
−
<!--<li>If you have a custom <tt>feature-definitions.json</tt> file, review the [[FeatureConfiguration|Feature Configuration]] and add the new features for 8.5.1:
 
−
 
 
−
{|
 
−
! '''id'''
 
−
! '''displayName'''
 
−
! '''description'''
 
−
! '''autoAssignOnContactCenterCreate'''
 
−
|-
 
−
| api-voice-recording
 
−
| Voice API Recording
 
−
| API for Voice Recording
 
−
| false
 
−
|-
 
−
| api-supervisor-agent-control
 
−
| API Supervisor Agent Control
 
−
| API For Supervisors to Control Agent State
 
−
| false
 
−
|-
 
−
| api-supervisor-monitoring
 
−
| API Supervisor Monitoring
 
−
| API For Supervisors to Monitor Agents
 
−
| false
 
−
|-
 
−
| api-mobile-push-notifications
 
−
| Mobile Push Notifications API
 
−
| API for Mobile push notification support
 
−
| false
 
−
|-
 
−
| ui-supervisor-add-user
 
−
| UI Supervisor Add User
 
−
| UI For Supervisors to Create Users
 
−
| false
 
−
|-
 
−
| ui-supervisor-edit-user
 
−
| UI Supervisor Edit User
 
−
| UI For Supervisors to Edit Users
 
−
| true
 
−
|}
 
−
{{NoteFormat|These new features must be added to the <tt>feature-definitions.json</tt> file in order for Web Services to work correctly.}}-->
 
−
</li>
 
−
<li>Complete the [[Documentation:HTCC:Dep:StartHTCC|Starting and Testing]] procedure.
 
−
</ol>
 
−
</li>
 
−
</ol>
 
−
'''End'''
 
−
 
 
−
{{AnchorDiv|Mig_18_29_41}}
 
−
==Migrating from 8.5.200.18 or later to the current version==
 
−
 
 
−
Use this procedure to migrate from 8.5.200.18 or later to the current version.  
 
−
 
 
−
{{NoteFormat|If you are currently using 8.5.200.09, you need to follow the [[MigMigrateIPProc#Mig_09|Migrating from 8.5.200.09]] procedure because the migration includes a transition from standalone Jetty to embedded Jetty.  
 
 
}}
 
}}
−
 
−
'''Start'''
 
−
 
−
# {{Editgrn_open}}Stop GWS on all nodes.{{Editgrn_close}}
 
−
# [[MigThirdParty#MigrateCassandra|Migrate Cassandra]].
 
−
# Update the contents of the GWS package, see [[Documentation:HTCC:Dep:DeployWebApp|Deploy the new version of Web Services]].
 
−
# {{Editgrn_open}}Start GWS on all nodes.{{Editgrn_close}}
 
−
 
−
'''End'''
 
−
 
  
 
[[Category:V:HTCC:8.5.2DRAFT]]
 
[[Category:V:HTCC:8.5.2DRAFT]]

Latest revision as of 06:20, July 4, 2023

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 by 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. You should only change configuration after verification that the migration to new version completed successfully.

Choose one of the following procedures:

Important
  • If you are a Genesys Interaction Recording (GIR) customer and you are migrating Web Services and Applications 8.5.201.09 or 8.5.201.18, refer to 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.
This page was last edited on July 4, 2023, at 06:20.
Comments or questions about this documentation? Contact us for support!