Cisco WebEx Social Installation and Upgrade Guide, Release 3.4
Upgrading Cisco WebEx Social
Downloads: This chapterpdf (PDF - 128.0KB) The complete bookPDF (PDF - 1.72MB) | Feedback

Upgrading Cisco WebEx Social

Table Of Contents

Upgrading Cisco WebEx Social

Supported Upgrade Paths

Upgrading to Release 3.4

Upgrading to Release 3.4 SR1

Upgrading to Release 3.4 SR2


Upgrading Cisco WebEx Social


This chapter explains how to upgrade to Cisco WebEx Social 3.4. It includes these topics:

Supported Upgrade Paths

Upgrading to Release 3.4

Upgrading to Release 3.4 SR1

Upgrading to Release 3.4 SR2

Supported Upgrade Paths

You can upgrade to Cisco WebEx Social release 3.4 only from Cisco WebEx Social 3.3 SR1.

You can upgrade to Cisco WebEx Social release 3.4 SR1 only from Cisco WebEx Social 3.4.

You can upgrade to Cisco WebEx Social release 3.4 SR2 only from Cisco WebEx Social 3.4 SR1.

Upgrading to Release 3.4

This section explains how to upgrade to Cisco WebEx Social release 3.4. You can upgrade to this release only from Cisco WebEx Social 3.3 SR1.

The time that the upgrade process takes depends on the amount of data in your database. You can reduce the time that the database upgrade process takes by deploying up to four Worker nodes before you begin the upgrade procedure. These nodes increase the speed of the data migration part of the upgrade process. After the upgrade completes, you can remove the Worker nodes that you do not require.

To Upgrade to Cisco WebEx Social 3.4, perform the following steps.

Before You Begin

Verify the integrity of the installation image file as described in the "Verifying the Integrity of a Cisco WebEx Social .img File" section.

If a new NFS share will be used for Cisco Webex Social:

Copy the cms folder from the old share to the new share to migrate images and documents. For example, use this command:

cp -rp old_nfs_path/cms new_nfs_path/cms

Perform a partial reindex of the Image Gallery before you upgrade to this Cisco WebEx Social release. To do so, sign in to a Cisco WebEx Social App Server as a system administrator, click the down-arrow to the right of your name in the Global Navigation bar, select Server > Server Administration > Partial Re-Indexing, check the Image Gallery box under Media, and then click Execute the bottom of the window.

Procedure


Step 1 Sign in to the Director with your administrator user ID and password.

Step 2 Click System in the menu bar, then select Software from the list on the left of your screen.

Step 3 Take either of these actions:

If you want to use SCP to obtain the .img file:

a. Click the SCP button to display options for using SCP.

b. In the Host Name field, enter the fully qualified domain name or the IP address of the node where you placed the patch .img file.

c. In the File Name field, enter the complete path and file name of the .img file.

d. In the Linux/Unix User Name field, enter the user ID of the node on which the patch .img file has been placed.

e. In the Password field, enter the password for the User ID that you entered.

If you want to enter a URL where the .img file is stored:

a. Click the URL button to display options for entering a URL.

b. In the Upgrade File URL field, enter the URL.

Step 4 Click Fetch Image.

The .img file is copied to the Director node and the software version that you uploaded appears in the Available Upgrade Version field in the Upgrade area of the page.

Step 5 Click Upgrade.

The upgrade process begins.


Note You can monitor the upgrade process by checking the opt/logs/date/node-hostname_messages logs.


Step 6 Allow up to 15 minutes for the Director web service to automatically restart.

Step 7 Sign in to the Director with administrator credentials.

Step 8 Click System in the menu bar, then select Topology from the list on the left of your screen

Step 9 Verify that all the nodes have been upgraded to the desired version by checking the "Version Info" column next to each node.

If "Error" appears for any node, use an SSH client to connect to the node showing the symptom, log in as the admin user, and run the following command to identify the error:

sudo service puppet debug

Step 10 Take these actions in the Director:

a. Click System in the Menu bar and click Topology in the left panel.

b. Click the Refresh all button in the Server List area.

c. Make sure that the Operational Status field for each Cache, App Server, and Worker shows stopped, and that each Operational Status field for the other nodes shows running.

Step 11 Take these actions to migrate the Cisco WebEx Social schema and data to the format that the new release requires:

a. Use an SSH client to access any App Server node, log in as the admin user, and enter these commands:

sudo service puppet debug

sudo service monit stop

sudo service puppet stop

sudo service quad stop

b. Take these actions in the App Server command shell to update the portal-ext.properties file to allow for the schema migration:

1. Enter this command to edit the portal-ext.properties file:

sudo vi /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties

2. Set the upgrade.schema.enabled flag value to true.

3. Set the upgrade.ext.enabled flag value to false.

4. Save the portal-ext.properties file.

c. Enter this command in the App Server command shell:

sudo service quad start

The schema migration starts.

d. Use an SSH client to access the Director and enter the following command to monitor the process of the schema migration, where app_server_hostname is the hostname of the App Server node that you are accessing and date is the current date in yyyy_mm_dd format:

sudo tail -f /opt/logs/date/app_server_hostname_appserver.log

Wait until you see the following line before you continue to the next step:

UpgradeProcessWXS_3_4.doUpgrade(): Schema Upgrade Complete...
 
   

e. Enter this command in the App Server command shell:

sudo service quad stop

f. In the Director, click System in the Menu bar, click Topology in the left panel, then choose Enable from the Action drop-down menu next to each Cache node.

g. In the Director, choose Enable from the Action drop-down menu next to each Worker node.

h. Take these actions in the App Server command shell to update the portal-ext.properties file to allow for the data migration:

1. Enter this command to edit the portal-ext.properties file:

sudo vi /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties

2. Set the upgrade.schema.enabled flag value to false.

3. Set the upgrade.ext.enabled flag value to true.

4. Save the portal-ext.properties file.

i. Enter this command in the App Server command shell:

sudo service quad start

The data migration starts.

j. Use an SSH client to access the Director and enter the following command to monitor the process of the data migration, where app_server_hostname is the hostname of the App Server node that you are accessing and date is the current date in yyyy_mm_dd format:

sudo tail -f /opt/logs/date/app_server_hostname_appserver.log

Wait until you see the following line before you continue to the next step:

UpgradeProcessWXS_3_4.doUpgrade(): Data Migration Complete...
 
   

k. Enter these commands in the App Server command shell:

sudo service puppet start

sudo service monit start

Step 12 In the Director, click System in the Menu bar, click Topology in the left panel, then choose Enable from the Action drop-down menu next to each App Server node.


Upgrading to Release 3.4 SR1

This section explains how to upgrade to Cisco WebEx Social release 3.4 SR1. You can upgrade to this release only from Cisco WebEx Social 3.4.

The time that the upgrade process takes depends on the amount of data in your database. You can reduce the time that the database upgrade process takes by deploying up to four Worker nodes before you begin the upgrade procedure. These nodes increase the speed of the data migration part of the upgrade process. After the upgrade completes, you can remove the Worker nodes that you do not require.

To Upgrade to Cisco WebEx Social 3.4 SR1, perform the following steps.

Before You Begin

Verify the integrity of the installation image file as described in the "Verifying the Integrity of a Cisco WebEx Social .img File" section.

Procedure


Step 1 Sign in to the Director with your administrator user ID and password.

Step 2 Click System in the menu bar, then select Software from the list on the left of your screen.

Step 3 Take either of these actions:

If you want to use SCP to obtain the .img file:

a. Click the SCP button to display options for using SCP.

b. In the Host Name field, enter the fully qualified domain name or the IP address of the node where you placed the patch .img file.

c. In the File Name field, enter the complete path and file name of the .img file.

d. In the Linux/Unix User Name field, enter the user ID of the node on which the patch .img file has been placed.

e. In the Password field, enter the password for the User ID that you entered.

If you want to enter a URL where the .img file is stored:

a. Click the URL button to display options for entering a URL.

b. In the Upgrade File URL field, enter the URL.

Step 4 Click Fetch Image.

The .img file is copied to the Director node and the software version that you uploaded appears in the Available Upgrade Version field in the Upgrade area of the page.

Step 5 Click Upgrade.

The upgrade process begins.


Note You can monitor the upgrade process by checking the opt/logs/date/node-hostname_messages logs.


Step 6 Allow up to 15 minutes for the Director web service to automatically restart.

Step 7 Sign in to the Director with administrator credentials.

Step 8 Click System in the menu bar, then select Topology from the list on the left of your screen

Step 9 Verify that all the nodes have been upgraded to the desired version by checking the "Version Info" column next to each node.

If "Error" appears for any node, use an SSH client to connect to the node showing the symptom, log in as the admin user, and run the following command to identify the error:

sudo service puppet debug

Step 10 Take these actions in the Director:

a. Click System in the Menu bar and click Topology in the left panel.

b. Click the Refresh all button in the Server List area.

c. Make sure that the Operational Status field for each Cache, App Server, and Worker shows stopped, and that each Operational Status field for the other nodes shows running.

Step 11 Take these actions to migrate the Cisco WebEx Social schema and data to the format that the new release requires:

a. Use an SSH client to access any App Server node, log in as the admin user, and enter these commands:

sudo service puppet debug

sudo service monit stop

sudo service puppet stop

sudo service quad stop

b. In the Director, choose Enable from the Action drop-down menu next to each Worker node.

c. Take these actions in the App Server command shell to update the portal-ext.properties file to allow for the data migration:

1. Enter this command to edit the portal-ext.properties file:

sudo vi /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties

2. Set the upgrade.schema.enabled flag value to false.

3. Set the upgrade.ext.enabled flag value to true.

4. Save the portal-ext.properties file.

d. Enter this command in the App Server command shell:

sudo service quad start

The data migration starts.

e. Use an SSH client to access the Director and enter the following command to monitor the process of the data migration, where app_server_hostname is the hostname of the App Server node that you are accessing and date is the current date in yyyy_mm_dd format:

sudo tail -f /opt/logs/date/app_server_hostname_appserver.log

Wait until you see the following line before you continue to the next step:

UpgradeProcessWXS_3_4_SR1.doUpgrade(): Data Migration Complete...
 
   

f. Enter this command in the App Server command shell:

sudo service puppet debug

Step 12 In the Director, click System in the Menu bar, click Topology in the left panel, then take these actions:

a. Choose Enable from the Action drop-down menu next to each Cache node.

b. Choose Enable from the Action drop-down menu next to each App Server node.


Upgrading to Release 3.4 SR2

This section explains how to upgrade to Cisco WebEx Social release 3.4 SR2. You can upgrade to this release only from Cisco WebEx Social 3.4 SR1.

To Upgrade to Cisco WebEx Social 3.4 SR2, perform the following steps.

Before You Begin

Verify the integrity of the installation image file as described in the "Verifying the Integrity of a Cisco WebEx Social .img File" section.

Procedure


Step 1 Sign in to the Director with your administrator user ID and password.

Step 2 Click System in the menu bar, then select Software from the list on the left of your screen.

Step 3 Take either of these actions:

If you want to use SCP to obtain the .img file:

a. Click the SCP button to display options for using SCP.

b. In the Host Name field, enter the fully qualified domain name or the IP address of the node where you placed the patch .img file.

c. In the File Name field, enter the complete path and file name of the .img file.

d. In the Linux/Unix User Name field, enter the user ID of the node on which the patch .img file has been placed.

e. In the Password field, enter the password for the User ID that you entered.

If you want to enter a URL where the .img file is stored:

a. Click the URL button to display options for entering a URL.

b. In the Upgrade File URL field, enter the URL.

Step 4 Click Fetch Image.

The .img file is copied to the Director node and the software version that you uploaded appears in the Available Upgrade Version field in the Upgrade area of the page.

Step 5 Click Upgrade.

The upgrade process begins.


Note You can monitor the upgrade process by checking the opt/logs/date/node-hostname_messages logs.


Step 6 Allow up to 15 minutes for the Director web service to automatically restart.

Step 7 Sign in to the Director with administrator credentials.

Step 8 Click System in the menu bar, then select Topology from the list on the left of your screen

Step 9 Verify that all the nodes have been upgraded to the desired version by checking the "Version Info" column next to each node.

If "Error" appears for any node, use an SSH client to connect to the node showing the symptom, log in as the admin user, and run the following command to identify the error:

sudo service puppet debug

Step 10 Take these actions in the Director:

a. Click System in the Menu bar and click Topology in the left panel.

b. Click the Refresh all button in the Server List area.

c. Make sure that the Operational Status field for each Cache, App Server, and Worker shows stopped, and that each Operational Status field for the other nodes shows running.

Step 11 In the Director, click System in the Menu bar, click Topology in the left panel, then take these actions:

a. Choose Enable from the Action drop-down menu next to each Cache node.

b. Choose Enable from the Action drop-down menu next to each Worker node.

c. Choose Enable from the Action drop-down menu next to each App Server node.