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

Upgrading Cisco WebEx Social

Table Of Contents

Upgrading Cisco WebEx Social

Supported Upgrade Paths

Generating Database Passwords

Upgrading to Release 3.0

Upgrading to Release 3.0 SR1

Upgrading to Release 3.0 SR2

Upgrading to Release 3.0 SR3


Upgrading Cisco WebEx Social


This chapter describes how to upgrade Cisco WebEx Social to release 3.0. It includes these topics:

Supported Upgrade Paths

Generating Database Passwords

Upgrading to Release 3.0

Upgrading to Release 3.0 SR1

Upgrading to Release 3.0 SR2

Upgrading to Release 3.0 SR3

Supported Upgrade Paths

You can upgrade to Cisco WebEx Social release 3.0 from Cisco Quad release 2.5.2 SR5

You can upgrade to Cisco WebEx Social release 3.0 SR1 from Cisco WebEx Social release 3.0

You can upgrade to Cisco WebEx Social release 3.0 SR2 from Cisco WebEx Social release 3.0 SR1

You can upgrade to Cisco WebEx Social release 3.0 SR3 from Cisco WebEx Social release 3.0 SR2

Generating Database Passwords

The upgrade procedure requires you to enter two database passwords. Perform the following steps to generate the passwords that you need.

Procedure


Step 1 Log in to Unix account on the Quad Director as the admin user.

Step 2 Enter this command:

# sudo source /opt/cisco/bin/inc.functions.sh

Step 3 Enter this command, where RDBMS_fqdn is the fully qualified domain name of the RDBMS Store VM:

# sudo /opt/cisco/sbin/external-nodes.py RDBMS_fqdn | grep pass

Step 4 In the output that appears, find the output lines the that following table shows and make a note of the hash value of each line:

Output Line
Corresponding Username

quadbpass

quaddb

openfiredbpass

xmppdb


Step 5 Use the following command to decrypt each hash value that you noted in Step 4 and make a note of each decrypted value. Run this command four times, each time replacing hash_value with one of the hash values that you noted in Step 4.

# sudo CCMDecrypt hash_value


Upgrading to Release 3.0

To Upgrade to Cisco WebEx Social 3.0, perform the following steps. The upgrade process can take up to 20 minutes per node, depending 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 for normal operation.

Before You Begin

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, from the Control Panel in Quad, select Server Administration > Partial Re-indexing > Media > Image Gallery.

Procedure


Step 1 Take these actions in the Director to disable Quad Web node:

a. Click Topology in the left panel.

b. Click Disable in the Operational Status column for each Quad Web role.

c. Click Portal in the left panel.

d. In the Email Digest area, uncheck the Enable Inbound Mail box and click Save.

e. In Advanced Portal Properties area:

Find the outbound.enabled property and change its value to false.

Find the worker.digestscheduler.isActive property and change its value to false.

Click Save.

Step 2 Take these actions to back up the existing JSON database:

a. Use an SSH client to access the primary or secondary JSON node and log in as the root user.

b. Enter these commands:

# /usr/bin/mongodump -h 127.0.0.1:27000 -o /opt/mongo_backup/ --oplog

# tar czf json_store.tgz mongo_backup/

c. Copy the json_store.tgz file to a network storage location.

Step 3 Take these actions to back up the existing Analytics database:

a. Use an SSH client to access the Analytics node and log in as the root user.

b. Enter these commands:

# /usr/bin/mongodump -h 127.0.0.1:27001 -o /opt/mongo_backup/ --oplog

# tar czf analytics_store.tgz mongo_backup/

c. Copy the analytics_store.tgz file to a network storage location.

Step 4 Take these actions to back up the existing Search master data:

a. Use an SSH client to access the master Search node and log in as the root user.

b. Enter these commands:

# cd /opt/cisco/search/

# tar czf search_master.tgz data --exclude conf --exclude '*.lock'

c. Copy the search_master.tgz file to a network storage location.

Step 5 Take these actions to back up the existing Search slave data:

a. Use an SSH client to access the slave Search node and log in as the root user.

b. Enter these commands:

# cd /opt/cisco/search/

# tar czf search_slave.tgz data --exclude conf --exclude '*.lock'

c. Copy the search_slave.tgz file to a safe network storage location.

Step 6 Take these actions to back up the existing Index Store data:

a. Use an SSH client to access the Index Store and log in as the root user.

b. Enter these commands:

# cd /opt/cisco/searchcache

# tar czf search_cache.tgz multicore --exclude conf --exclude '*.lock' --exclude solr.xml

c. Copy the search_cache.tgz file to a network storage location.

Step 7 Take these actions to back up the existing RDBMS database:

a. Use an SSH client to access the RDBMS node and log in as the root user.

b. Enter the following commands. Replace quaddb_password with the password of the existing Quad database, and replace xmppdb_password with the user password of the existing XMPP database. (You obtained these passwords as described in the "Generating Database Passwords" section.)

# su - oracle

# cd /opt/oracle

# exp userid=quaddb/quaddb_password buffer=1024000 file=2.5.2_quaddb.dmp log=2.5.2_quaddb.log owner=quaddb consistent=Y rows=Y RESUMABLE=y RESUMABLE_NAME=quaddb_export RESUMABLE_TIMEOUT=10000 feedback=100000

# exp userid=xmppdb/xmppdb_ password buffer=1024000 file=2.5.2_xmppdb.dmp log=2.5.2_xmppdb.log owner=xmppdb consistent=Y rows=Y RESUMABLE=y RESUMABLE_NAME=xmppdb_export RESUMABLE_TIMEOUT=10000 feedback=100000

Step 8 Take these actions to set up the virtual machines for all Cisco WebEx Social roles:

a. Obtain the installation image (of the form quad-3.x.x.xxxxx.xxx-xx.ova) from Cisco.

b. Copy the .ova image to a local disk on a Windows machine where VMware vSphere client is installed.


Note For faster deployment, run VMware vSphere client from a machine that is on the same network as VMware vSphere server.


c. Run the VMware client.

d. From the menu options, select File > Deploy OVF Template.

e. Using the Browse button, navigate to the path where the .ova file resides and select this file, then, click Next.

f. Review the template details and if they are correct, click Next.

g. Accept the license agreement and click Next.

h. Specify a VM name and location for the deployed template, then click Next.

A Configuration drop-down list appears.

i. Select the role that you are creating, then click Next.


Note You must create the Director VM first and the App Server VMs last. The order in which you create VMs for the other nodes does not matter.


j. Select the Host/Cluster that will be running the virtual machine, then click Next.

k. Select the Resource Pool, if any, then click Next.

l. Select the Data Store where the image will be stored, then click Next.

m. Select a format in which to store the virtual machine virtual disks, then click Next.

The Deployment Settings window opens.

n. Select network, then click Next.

o. Check to make sure the settings are correct, then click Finish.

The creation of the new virtual machine, depending on its speed and capability, may take as long as 30 minutes. When this process completes, a window appears telling you the process has completed.

p. Right-click on each virtual-machine icon and select Edit Settings. Make sure that Memory and CPU are adjusted based on the capability of the physical machine to which the virtual machine belongs.

q. Repeat steps i through p for all roles in your Cisco WebEx Social environment. (For a list of roles, see Table 1-1.)

Step 9 Take these actions to install the Director node virtual machine:

a. Power on the virtual machine that you have created for the Director.

b. Log in as admin in the VM console.

c. Select Network Settings.

d. Select Configure eth0 Interface.

e. Configure values in the IP Address field, Subnet Mask field, and Gateway field, then press Enter to save your changes.

f. In the Network Settings screen, configure values in the Primary Nameserver field, Hostname field, and Director field, then press Enter to save your changes.

The values in the Hostname and Director fields must by fully-qualified domain names.

g. Select Apply Configuration.

Step 10 Take these actions to access the Director and create a Unified Access password:

a. Access the Director web console by entering the following URL in a supported web browser, where virtual machine IP is the IP address of the virtual machine that contains the Director:

http://virtual_machine_ip

The Director window opens.

b. Sign in with the following default administrative user credentials:

User Name—admin

Password—cisco

c. When you are prompted for a Unified Access password, enter a password and designate the Cisco WebEx Social components that the password should apply to, then click Save.

Step 11 In the Director, click Configuration in the left panel, enter appropriate values for your deployment in the Unified Access , NFS, and NTP, and NFS areas, and click Save.

For detailed descriptions of fields in the Director, see the "Director" chapter in Cisco WebEx Social Administration Guide.

Step 12 Take these actions in the Director:

a. Click Topology in the left panel.

b. Choose RDBMS Store from the Role drop-down list.

c. In the FQDN field, enter the fully qualified domain name of the RDBMS role (for example, abc-rdbms.cisco.com)

d. Click the Add button.

Step 13 In the Director, click Configuration in the left panel, enter appropriate values for your deployment in the areas that you did not configure in Step 11, and click Save.

Step 14 Deploy the RDBMS Store node using the latest OVA template, then power on this node and take these actions to configure the VM:

a. Log in as admin in the VM console.

b. Select Network Settings.

c. Select the NIC to configure.

d. Configure values in the IP Address field, Subnet Mask field, and Gateway field, then press Enter to save your changes.

e. In the Network Settings screen, configure values in the Primary Nameserver field, Hostname field, and Director field, then press Enter to save your changes.

The values in the Hostname and Director fields must by fully-qualified domain names.

f. Select Apply Configuration.

Step 15 Use SSH to access the RDBMS node, log in as the admin user, and take these actions:

a. Check the following log files to monitor the progress of the RDBMS Store deployment:

On the RDBMS node: /tmp/cr_ECP_DB_quad-*.LOG

On the Director node: /opt/logs/date/director_hostname-messages


Note It can take up to 30 minutes for the RDBMS node to deploy.


b. Make sure that the RDBMS node is up and running by entering this command:

service dbora status


Note Do not continue with this procedure until this node is up and running.


Step 16 Take these actions to restore the RDBMS database:

a. Use an SSH client to access the RDBMS node and log in as the admin user.

b. Copy the RDBMS dump files that you created in Step 7 to the /opt/oracle folder on the RDBMS node (precede the copy command that you use with sudo).

c. Enter this command to restore the quaddb.dmp file:

# sudo /opt/oracle/utils/restore_db.sh --db-name quaddb --db-dump-file / opt/oracle/2.5.2_quaddb.dmp

d. If your Cisco WebEx Social 3.0 deployment is using the same Notifier node hostname that was used in the Quad deployment that you are upgrading from, enter the following command to restore the xmppdb.dmp file.

Do not restore your database by using this command if you changed the Notifier node hostname.

# sudo /opt/oracle/utils/restore_db.sh --db-name xmppdb --db-dump-file / opt/oracle/c2.5.2_xmppdb.dmp

Step 17 Take these actions to install all other roles in your Cisco WebEx Social environment (you must repeat these substeps for each node you are deploying):

a. Power on the virtual machine that you created for each role.

b. Log in as admin in the VM console.

c. Select Network Settings.

d. Select the NIC to configure.

e. Configure values in the IP Address field, Subnet Mask field, and Gateway field, then press Enter to save your changes.

f. In the Network Settings screen, configure values in the Primary Nameserver field, Hostname field, and Director field, then press Enter to save your changes.

The values in the Hostname and Director fields must by fully-qualified domain names.

g. Select Apply Configuration.

Installation of nodes usually takes a few minutes, and you will receive a message when it is complete.

Step 18 Take these actions to restore the JSON Store database:

a. Use an SSH client to access the JSON Store primary node and log in as the admin user.

b. Copy the json_store.tgz file that you backed up in Step 2 to the /opt folder on the JSON Store primary node.

c. Enter these commands:

# sudo tar xzf /opt/json_store.tgz

# sudo mongorestore --port 27000 -d quad --drop /opt/mongo_backup/quad/

Step 19 Take these actions to restore the Analytics Store database:``

a. Use an SSH client to access the Analytics node and log as the admin user.

b. Copy the analytics_store.tgz file that you backed up in Step 3 to the /opt folder on the Analytics node node.

c. Enter these commands:

# sudo tar xzf /opt/analytics_store.tgz

# sudo mongorestore --port 27001 --drop -d recommendation /opt/mongo_backup/
recommendation/

Step 20 Take these actions to import Search Store index data:

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

sudo service puppet stop

sudo service monit stop

sudo service search stop

b. Copy the search_master.tgz file that you backed up in Step 4 to the /opt/cisco/search folder on the Search master node.

c. Enter this command:

cd /opt/cisco/search/

sudo tar xzf search_master.tgz

d. Enter these commands:

sudo service search start

sudo service monit start

sudo service puppet start

e. Use an SSH client to access the Search slave node, log in as the admin user, and enter these commands:

sudo service puppet stop

sudo service monit stop

sudo service search stop

f. Copy the search_slave.tgz file that you backed up in Step 5 to the /opt/cisco/search folder on the Search slave node.

g. Enter this command:

cd /opt/cisco/search/

sudo tar xzf search_slave.tgz

h. Enter these commands:

sudo service search start

sudo service monit start

sudo service puppet start

i. Use an SSH client to access the Index Store node, log in as the admin user, and enter these commands:

sudo service puppet stop

sudo service monit stop

sudo service searchcache stop

j. Copy the search_cache.tgz file that you backed up in Step 6 to the /opt/cisco/searchcache folder on the Search slave node.

k. Enter this command:

cd /opt/cisco/searchcache/

sudo tar xzf search_cache.tgz

l. Enter these commands:

sudo service searchcache start

sudo service monit start

sudo service puppet start

Step 21 In the Director click Topology in the left panel and make sure that all roles except App Server, Cache, and Worker are running.

Step 22 Take these actions to migrate Cisco WebEx Social data and schema 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 monit stop

sudo service puppet stop

b. Take these actions:

1. Use a text editor to edit this file:

/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:

sudo service quad start

d. Enter the following command to monitor the process of the schema update, 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:

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

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

UpgradeProcessSprint20.doUpgrade():Complete...
 
   

e. Enter this command:

sudo service quad stop

f. Take these actions:

1. Use a text editor to edit this file:

/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.

g. Take these actions in the Director to enable the Cache node and the newly added Worker nodes:

1. Click Topology in the left panel.

2. Click Enable in the Operational Status column for the Cache role.

3. Click Enable in the Operational Status column for each Worker role.

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

sudo service quad start

i. 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:

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

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

ActiMigMonitorThrd() Activity collections indexing ends
 
   

j. After data is migrated successfully, enter these commands:

sudo service monit start

sudo service puppet start

Step 23 In the Director, click Enable in the Operational Status column for each App Server role.

Step 24 Sign in to a non-Director Cisco WebEx Social node as system administrator and take these actions:

a. Click the down-arrow to the right of your name in the Global Navigation bar.

b. Select Account Settings from the drop-down menu.

c. Click the right-arrow next to Server.

d. Click Server Administration in the Server drawer.

e. In the Server Administration window, click the Log Properties tab, and, for the Search log group, choose INFO from the drop-down list for this group in the Level field.

f. In the Server Administration window, click the Partial Re-Indexing tab.

g. Check the Contacts, Follower, and People check boxes under People near the bottom of the window.

h. Check the Use Faster Multi-Threaded approach check box.

i. Click Execute.


Upgrading to Release 3.0 SR1

You can upgrade to Cisco WebEx Social release 3.0 SR1 only from Cisco WebEx Social release 3.0. To perform this upgrade, follow these steps:

Procedure


Step 1 Use SSH to access the RDBMS Store node, log in as the admin user, and take these actions:

a. Enter these commands to delete trace and dump files that are older than 1 day (you can ignore the "no such file or directory" message):

sudo /usr/bin/find /opt/oracle/app/oracle/diag/rdbms/quad/quad/trace -type f -name "*.tr[c,m]" -mtime +1 -exec /bin/rm -f {} \;

sudo /usr/bin/find /opt/oracle/app/oracle/admin/quad/adump/* -maxdepth 1 -mtime +1 -exec /bin/rm -f {} \;

sudo /usr/bin/find /opt/oracle/app/oracle/diag/rdbms/quad/quad/cdump/* -maxdepth 1 -mtime +1 -exec /bin/rm -rf {} \;

sudo /usr/bin/find /opt/oracle/app/oracle/diag/rdbms/rdfprod/rdfprod/trace -type f -name "*.tr[c,m]" -mtime +1 -exec /bin/rm -f {} \;

sudo /usr/bin/find /opt/oracle/app/oracle/admin/rdfprod/adump/* -maxdepth 1 -mtime +1 -exec /bin/rm -f {} \;

sudo /usr/bin/find /opt/oracle/app/oracle/diag/rdbms/rdfprod/rdfprod/cdump/* -maxdepth 1 -mtime +1 -exec /bin/rm -rf {} \;

b. Enter these commands:

sudo rm -f /var/lib/logrotate.status

sudo killall logrotate

c. Enter this command to verify that the crond daemon is running:

service crond status

If this daemon is not running, enter service crond start to start it.

Step 2 Upgrade the Cisco WebEx software by using the provided .img file and the Software Maintenance window under Deployment on the Quad Director node, but do not reenable the Cache, App Server, and Worker nodes.

For instructions, see the "Using the Software Window" section.

Step 3 Take these actions:

a. Use SSH to access the App Server node on which you will migrate the Cisco WebEx Social data and schema to the format that the new SR1 requires and log in as the admin user.

b. Enter this command:

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

c. Ensure that the upgrade.ext.processes property has this value:

com.liferay.portal.upgrade.UpgradeProcessSprint20,com.liferay.portal.upgrade.
UpgradeProcessSprint20SR1

d. If the liferay.portal.upgrade.UpgradeProcessSprint20SR1 value is missing, enter the following command, then repeat Steps 2 and 3:

sudo service puppet debug

Step 4 Use SSH to access any App Server node, log in as the admin user and take these actions to migrate Cisco WebEx Social data and schema to the format that the new SR1 requires:

a. Enter these commands:

sudo service monit stop

sudo service puppet stop

b. Take these actions:

1. Use a text editor to edit this file:

/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:

sudo service quad start

d. Enter the following command to monitor the process of the schema update, 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:

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

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

UpgradeProcessSprint20SR1.doUpgrade():Complete...
 
   

e. Enter this command:

sudo service quad stop

f. Take these actions:

1. Use a text editor to edit this file:

/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.

g. Take these actions in the Director to enable the Cache node and the Worker nodes:

1. Click Topology in the left panel.

2. Click Enable in the Operational Status column for the Cache role.

3. Click Enable in the Operational Status column for each Worker role.

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

sudo service quad start

i. 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:

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

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

ActiMigMonitorThrd() Activity collections indexing ends
 
   

j. After data is migrated successfully, enter these commands:

sudo service monit start

sudo service puppet start

k. Take these actions in the Director to enable the App Server nodes:

1. Click Topology in the left panel.

2. Click Enable in the Operational Status column for each App Server role.

Step 5 Log in to the Cisco WebEx Social as an administrator and these actions:

a. Click the down-arrow to the right of your name in the Global Navigation bar.

b. Select Account Settings from the drop-down menu.

c. Click the right-arrow next to Server

d. Click Server Administration in the Server drawer.

e. Select the Metrics Initialization tab.

f. Click the Initialize Metrics button.


Upgrading to Release 3.0 SR2

You can upgrade to Cisco WebEx Social release 3.0 SR2 only from Cisco WebEx Social release 3.0 SR1. To perform this upgrade, follow these steps:

Procedure


Step 1 Upgrade the Cisco WebEx software by using the provided .img file and the Software Maintenance window under Deployment on the Quad Director nodes.

For instructions, see the "Using the Software Window" section.

Step 2 After the upgrade completes, log in to Cisco WebEx Social as an administrator and take these actions:

a. Click the down-arrow to the right of your name in the Global Navigation bar.

b. Select Account Settings from the drop-down menu.

c. Click the right-arrow next to Server

d. Click Server Administration in the Server drawer.

e. In the Resources tab, click the Execute button next to Index JSON and Analytics Stores.


Upgrading to Release 3.0 SR3

You can upgrade to Cisco WebEx Social release 3.0 SR3 only from Cisco WebEx Social release 3.0 SR2.

To perform this upgrade, use the provided .img file and the Software Maintenance window under Deployment on the Quad Director node.

For instructions, see the "Using the Software Window" section.