Contents
Genesys Interaction Recording Migration Guide
The 8.5.211.01 release of the Genesys Interaction Recording solution replaces the Web Services and Applications prerequisite with a new GIR component called Interaction Recording Web Services. If you plan to install this release of GIR, you'll need to complete the steps below to migrate from Web Services and Applications to Interaction Recording Web Services.
Upgrading from standalone to embedded Jetty
Complete the steps below for each Web Services node you need to upgrade to Interaction Recording Web Services.
Start
- Stop Web Services on the node.
- If you installed Jetty as service, disable the service to prevent auto start and potential port conflicts.
- Deploy the new version of Interaction Recording Web Services.
- Copy settings from your existing server-settings.yaml, onpremise-settings.yaml, and cassandra-cluster.yaml configuration files to the serverSettings, onPremiseSettings, and cassandraCluster sections of the application.yaml configuration file. See Configuring Interaction Recording Web Services for more information about this file.
- Copy settings from your existing Jetty configuration files to the jetty section of the application.yaml configuration file.
- Adjust the logging section of the application.yaml configuration file.
- Copy the JMV options from your exiting Jetty initialization script to the JAVA_OPTIONS variable in the /etc/default/gir file.
- Start the new version of Interaction Recording Web Services on the node.
End
Upgrading Cassandra for Interaction Recording Web Services
If you currently have Cassandra 1.2 installed:
- and have not updated to the latest schema (cf-schema-8.5.201.09.txt), please follow the instructions below to upgrade your schema to the latest before migrating to Cassandra 2.2.
- and are already using the latest schema (cf-schema-8.5.201.09.txt), please proceed to upgrade your Cassandra version to 2.2 by following the steps in Installing and Configuring Cassandra.
Complete the steps below on the node where you have installed cassandra-cli (only for Cassandra 1.2):
Start
CHANGED TEXT BEGINS
- Make note of your current Web Services and Applications version.
- Copy the Interaction Recording Web Services install CD/data directory to the Cassandra node.
- In the data directory, notice that there are text files, cf-schema-<version>.txt, for each version of Web
Services and Applications. You'll need to run all the Cassandra upgrade scripts after your currently
installed version of Web Services and Applications until the latest file, which is cf-schema-8.5.201.09.txt.
For example, if your Web Services and Applications version is 8.5.200.96, you'll need the following scripts:
- cf-schema-8.5.200.98.txt
- cf-schema-8.5.200.99.txt
- cf-schema-8.5.201.04.txt
- cf-schema-8.5.201.06.txt
- cf-schema-8.5.201.09.txt
cassandra_install_dir/bin/cassandra-cli -h cassandra_host --file cf-schema-<version>.txt ...where:
cassandra_install_dir is where Cassandra is installed on the node.
cassandra_host is the host name (FQDN) or IP of the Cassandra node.
End
CHANGED TEXT ENDS
Re-importing the Certificate for WebDAV
Complete the steps below if you used a self-signed certificate to configure TLS for the WebDAV server.
Start
- Make sure you have installed Java 8.
- Retrieve your self-signed CA certificate from the WebDAV server. Run the following command to determine the file used as a certificate for WebDAV access: grep SSLCertificateFile /etc/httpd/conf.d/ssl.conf
For example, this might return the following response: /etc/pki/tls/certs/server.crt - Re-import the certificate into the new keystore with the following commands:
cd $JAVA_HOME/jre/lib/security
../../bin/keytool -import -alias webdav -file ~/webdav_certificate -keystore cacerts- webdav_certificate is the file returned in step 2.
- Restart Interaction Recording Web Services.
End
