Upgrading to IVG 5.4.1
IVG 5.4.1 includes upgrades to Call Control Interaction Server (CCIS), CTI Event Consumer (CCIS Event Injector), and VoiceXML Interaction Server (VIS). Since this is an incremental update, no installer is necessary to upgrade from version 5.4.0 to 5.4.1. Follow the instructions in this guide to manually back up and replace artifacts for the affected components to complete the upgrade.
Upgrading to IVG 5.4.1 requires that version 5.4.0 is already installed. See the Installation Guide for instructions.
Initial Steps
Before you begin, you will need to obtain the new artifacts and store them on all IVG servers.
Create a directory to place IVG 5.4.1 artifacts.
Log in to the IVG server. Assuming that the present working directory of the logged in user is /home/{user_name}/ (replace it with appropriate path in further Linux commands)
Create a directory with the name IVG_5.4.1 in /home/{user_name}/ (assuming that the present working directory of the logged in user is /home/{user_name})
This directory will be used to copy IVG 5.4.1 artifacts.
Copy the contents of the VIS, CCIS and CTI Event Consumer release artifacts folders to the new directory.
You can obtain the release artifacts from the Mindful Download Center, and they should be named as follows:
- VIS_7.13.0.390
- CCIS_5.4.1.139
- CTIEventConsumer_5.4.1.61
Upgrading CTI Event Consumer to 5.4.1
Follow the steps below to upgrade the CTI Event Consumer.
Switch to the holly-ivg user:
Stop the ctieventconsumer worker:
Back up the existing CTI Event Consumer artifacts.
Exit from the holly-ivg user and navigate to /export/home/VirtualHold/CTIEventConsumer:
Take a backup of the jar file and lib directory:
Copy the new artifacts.
Copy the ctieventconsumer-5.4.1.jar file and lib directories from the CTI Event Consumer release artifacts directory to the path mentioned below.
Update the existing configuration file and startup script:
Change the permissions of the newly copied artifacts:
Update HVP configuration for CTIEventConsumer:
Verify that the configuration is updated correctly by running the below command as the holly-ivg user:
This will result in output like the following, containing the version number in the name of the jar file.
Start the ctieventconsumer worker.
Switch back to the holly-ivg user and start ctieventconsumer:
Wait for a minute and run the following command to verify the ctieventconsumer worker started successfully:
The output shows list of Holly workers running. In that list, ctieventconsumer should be shown, as in the example below:
If the ctieventconsumer opcode shows "ok", then the worker is running as expected.
Upgrading CCIS to 5.4.1
Follow the steps below to upgrade CCIS.
Stop the Tomcat service:
Back up the existing CCIS.war file.
Navigate to the /export/home/tomcat-ivg/webapps directory.
Run the following command to rename the CCIS.war file and remove the existing CCIS directory:
Copy the new CCIS.war file to /export/home/tomcat-ivg/webapps:
Change the ownership of the new CCIS.war file:
Clean the contents of the /export/home/tomcat-ivg/work directory:
Start the tomcat service:
Check the status of the tomcat service:
Upgrading VIS to 7.13.0.390
Follow the steps below to upgrade VIS.
Stop the tomcat service:
Back up the existing VIS.war file.
Navigate to /export/home/tomcat-ivg/webapps.
Run the following command to rename the VIS.war file and remove the existing VIS directory:
Copy the new VIS.war file to /export/home/tomcat-ivg/webapps:
Change the ownership of new VIS.war file:
Clean the contents of the /export/home/tomcat-ivg/work directory:
Start the tomcat service:
Check the status of the tomcat service:
After upgrading all the above components, run test calls to ensure the system functions as expected.