Quad Install

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco WebEx Social Installation and Upgrade Guide, Release 3.0Revised September 24, 2012

Text Part Number: OL-27466-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.

Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.

You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:

• Turn the television or radio antenna until the interference stops.

• Move the equipment to one side or the other of the television or radio.

• Move the equipment farther away from the television or radio.

• Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)

Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Cisco WebEx Social Installation and Upgrade Guide, Release 3.0 © 2012 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

OL-27466-01

C O N T E N T S

Preface iii

Overview iii

Organization iii

Related Documentation iii

Obtaining Documentation, Obtaining Support, and Security Guidelines iv

C H A P T E R 1 System Requirements 1-1

Browser Support and Compatibility With Other Components 1-1

Installing Plugin for Cisco Web Communicator 1-1

Overview of Cisco WebEx Social Nodes and Their Roles 1-2

Version Compatibility 1-3

Cisco WebEx Social Compute Platform 1-3

Platform 1-3

Compute 1-3

Storage 1-4

NFS Requirements and Setup 1-4

VMware vSphere Configuration for Cisco WebEx Social 1-6

Resource Protection 1-9

VMWare Sizing Tables 1-9

Disk Growth and Size 1-12

Load Balancer Information 1-13

Planning 1-13

C H A P T E R 2 Installing Cisco WebEx Social 2-1

Before You Begin 2-1

Installing Cisco WebEx Social 3.0 2-1

C H A P T E R 3 Upgrading Cisco WebEx Social 3-1

Supported Upgrade Paths 3-1

Generating Database Passwords 3-1

Upgrading to Release 3.0 3-2

Upgrading to Release 3.0 SR1 3-9

iCisco WebEx Social Installation and Upgrade Guide, Release 3.0

Contents



C H A P T E R 4 Post-Installation and Post-Upgrade Steps 4-1

Provisioning Cisco WebEx Social to Communicate with the Notifier Server 4-1

LDAP Sync 4-3

Search Indexing Step 4-3

Updating the Community Templates 4-4

Updating Your Company Name 4-5

Updating the EULA 4-6

Setting Maximum File Size for User Images 4-7

Changing NFS Settings 4-7

C H A P T E R 5 Additional Installation-Related Information 5-1

Enabling or Disabling Cisco WebEx Social Nodes 5-1

Using Refresh Buttons 5-1

Using the Software Window 5-2

Using the Director 5-3

Checking Installation-Related Log Files 5-3

iiCisco WebEx Social Installation and Upgrade Guide, Release 3.0

OL-27466-01

Preface

OverviewCisco WebEx Social Installation and Upgrade Guide provides information for Cisco WebEx Social system administrators. This guide explains how to install and upgrade Cisco WebEx Social, and provides related information and guidelines.

OrganizationThis manual is organized as follows:

Related Documentation • Cisco WebEx Social Administration Guide, Release 3.0

• Cisco WebEx Social Troubleshooting Guide, Release 3.0

• Cisco WebEx Social API Reference Guide, Release 3.0

• Cisco WebEx Social Server: Getting Started Guide, Release 3.0

• Cisco WebEx Social Compatibility Guide

• Open Source License Notices for Cisco WebEx Social

Chapter 1, “System Requirements,” Provides system requirements for Cisco WebEx Social

Chapter 2, “Installing Cisco WebEx Social,” Provides procedures for installing Cisco WebEx Social

Chapter 3, “Upgrading Cisco WebEx Social” Provides procedures for upgrading to the current version of Cisco WebEx Social

Chapter 4, “Post-Installation and Post-Upgrade Steps”

Provides procedures to perform after an installation or upgrade

Chapter 5, “Additional Installation-Related Information,”

Provides additional information that relates to the installation of Cisco WebEx Social

iiiCisco WebEx Social Installation and Upgrade Guide, Release 3.0

OL-27466-01

Preface

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

ivCisco WebEx Social Installation and Upgrade Guide, Release 3.0

OL-27466-01

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Cisco WebExOL-27466-01

C H A P T E R 1
System Requirements
This section provides system requirements for Cisco WebEx Social and contains the following topics:

• Browser Support and Compatibility With Other Components, page 1-1

• Installing Plugin for Cisco Web Communicator, page 1-1

• Overview of Cisco WebEx Social Nodes and Their Roles, page 1-2

• Version Compatibility, page 1-3

• Cisco WebEx Social Compute Platform, page 1-3

• NFS Requirements and Setup, page 1-4

• VMware vSphere Configuration for Cisco WebEx Social, page 1-6

• Resource Protection, page 1-9

• Disk Growth and Size, page 1-12

• VMWare Sizing Tables, page 1-9

• Load Balancer Information, page 1-13

• Planning, page 1-13

Browser Support and Compatibility With Other ComponentsFor a list of browsers and other components that are compatible with Cisco WebEx Social, see Cisco WebEx Social Compatibility Guide.

Installing Plugin for Cisco Web CommunicatorEach Cisco WebEx Social user must install a plugin to use Cisco Web Communicator.

See the “Installation and Configuration for Cisco Web Communicator” section in Cisco WebEx Social Administration Guide for information on where the plugin can be obtained and how users can install the plugin that they need.

1-1 Social Installation and Upgrade Guide, Release 3.0

Chapter 1 System Requirements Overview of Cisco WebEx Social Nodes and Their Roles

Overview of Cisco WebEx Social Nodes and Their RolesTable 1-1 provides a brief description of the service that each node in the Cisco WebEx Social environment performs. The service a node performs is often referred to as a role in Cisco WebEx Social.

Table 1-1 Cisco WebEx Social Roles

Role Description Requirements

Analytics Store A Mongo database that contains information about user preferences for the purpose of providing suggestions for what communities or other aspects of Cisco WebEx Social may interest a particular user. Also used for the e-mail digest notification and metrics features.

Minimum: 1 node.

Maximum: 2 nodes.

Note 2 nodes are recommended to provide for high availability and redundancy.

App Server The core Cisco WebEx Social web application. Minimum: One node.

Maximum: No limit.

Cache A distributed, high-performance, in-memory key/value store. This node is intended to increase the speed of data access. The system tries to fetch data from this node before accessing the database, and database access is a slower operation.

Minimum: 1 node.

Maximum: No limit.

Director Used to set up your Cisco WebEx Social topology and manage various system settings and configuration options.

1 node.

Index Store An autonomous, special-purpose instance of the Cisco WebEx Social search engine used as a pseudo-cache to offload a class of resource-intensive database queries.

Minimum: 1 node.

Maximum: 1 node.

JSON Store A MongoDB database that stores various Cisco WebEx Social data. Provides for faster access to certain data than using a relational database would allow.

Minimum: 1 node.

Maximum: 2 nodes.

Note 2 nodes are strongly recommended to provide for high availability and redundancy.

Message Queue A message bus that provides reliable, asynchronous database updates.

Minimum: 1 node.

Maximum: 2 nodes.

Notifier XMPP publisher for notification of end-user events, including system alerts, announcements, and activities.

Minimum: 1 node.

Maximum: 1 node.

RDBMS Store Data store for data from the Notifier and App Server.

Minimum: 1 node.

Maximum: 1 node.

1-2Cisco WebEx Social Installation and Upgrade Guide, Release 3.0

OL-27466-01

Chapter 1 System Requirements Version Compatibility

Note You can use a proxy server with your Cisco WebEx Social environment. For more information, see the “Proxy Settings” section in the “Director” chapter in Cisco WebEx Social Administration Guide.

Version CompatibilityCisco WebEx Social works with many other components, such as Show and Share, Notification, and Presence servers. For list of the versions of other components that Cisco WebEx Social supports, see Cisco WebEx Social Compatibility Guide.

Cisco WebEx Social Compute PlatformThis section contains information about what Cisco supports and recommends for the Cisco WebEx Social compute platform:

PlatformCisco recommends Vblock for Cisco WebEx Social. Deploying Cisco WebEx Social on Vblock is optional.

ComputeCisco WebEx Social is supported on Cisco Unified Computing System servers.

Search Store Cisco-provided search engine for Cisco WebEx Social.

There must be a master/slave setup for the Search Store. You need one virtual machine for the Master node and one for each slave node.

Minimum: 1 Search Store master and 1 Search Store slave.

Maximum: 1 Search Store master and 10 Search Store slaves.

Worker Improves system performance and user interaction by handling asynchronous and background processing tasks and interacting with various other roles.

Minimum: 1 node (2 for high availability).

Maximum: No limit.

Table 1-1 Cisco WebEx Social Roles (continued)

Role Description Requirements


OL-27466-01

Chapter 1 System Requirements NFS Requirements and Setup

Intel Xeon CPUs

The following Intel Xeon CPUs are supported:

• X5570 4-Core 2.93 Ghz and greater

• X5670 6-Core 2.93 Ghz and greater

StorageStorage requirements and recommendations are as follows:

• Storage vendor—Cisco WebEx Social supports the latest Cisco UCS Storage Interoperability Matrix. The latest matrix is available at the following URL: http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/ Matrix8.html

• NFSv4 storage required—Cisco WebEx Social requires an NFSv4 export.

• Storage space recommendation—Allow for at least 500MB of usable space per user when designing a system for 10,000 or more users.

• Storage performance recommendation: Allow for at least .1 IOPS per user when designing a system for 10,000 or more users.

NFS Requirements and SetupCisco WebEx Social requires one NFS Version 4 export/share on the server and three NFS Version 4 mounts on the Cisco WebEx Social client. The NFSv4 export/share are for data store, Message Queue, and Director data backup. Table 1-2 describes these exports/shares.

After NFS is configured in the Director, the following auto-NFS mount points are automatically configured on each Cisco WebEx Social VM:

• /mnt/auto/cms (for data store)

• /mnt/auto/jms (for Message Queue)

All of these mount points should come from the same NFS server host.

Note “root_squash” on NFS is recommended for these mount points.

Table 1-2 Export/Share on NFS Server

Export/Share Name Ownership Purpose

cms quad:quad (303:300) For data store

jms activemq:quad (301:300) For Message Queue

backup oracle:sysdba (440:201) Topology and cluster metadata from the Director


OL-27466-01

http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.html



Chapter 1 System Requirements NFS Requirements and Setup

Setting up an NFS server requires that you contain the exported NFS file area to a subset of the NFS server file system and prepare for multiple uses of the NFS server. For example, you can contain the area of the file system that is exposed to the outside world through NFS to a top-level directory called /export and subdirectories you create under /export.

Under the /export directory, you can create a webexsocial directory to contain all data for all Cisco WebEx Social instances.

The following procedure shows an example for setting up NFS. This procedure assumes that you are squashing the root.

Note This procedure is for a generic linux system and may not give the exact steps you need to run to achieve the NFS setup described. Refer to the vendor-supplied documentation for your storage system to achieve the same setup described in this section.

Procedure

Step 1 Run this command on the NFS server to create the /export/webexsocial folder on that server:

mkdir -p /export/webexsocial

Step 2 Take these actions on the NFS server:

a. Create subdirectories required by each instance of Cisco WebEx Social under the /export/webexsocial directory:

– cd /export/webexsocial/

– mkdir cms jms backup

b. After these subdirectories are created, or if they preexist, execute the following commands execute the following commands to change their ownership:

– chown -vR 301:300 jms

– chown -vR 303:300 cms

– chown -vR 440:201 backup

Step 3 On the NFS server, create the NFS server configuration file /etc/exports file with this content:

/export/webexsocial *(rw,root_squash,fsid=0,anonuid=99,anongid=99)

Note Only one line is required in the file /etc/exports. This setup will serve one or more Cisco WebEx Social instances.

Step 4 After you have finished writing the /etc/exports file, restart the NFS service by running this command on the NFS server:

service nfs restart

Step 5 (Optional but recommended) Take these actions on the NFS server:

a. Configure /etc/idmapd.conf on NFS to have the same domain name as that of /etc/idmapd.conf on the Director node.

b. After you have finished writing the /etc/idmapd.conf file, restart the RPCIDMAPD service by running the following command on the NFS server:

service rpcidmapd restart


OL-27466-01

Chapter 1 System Requirements VMware vSphere Configuration for Cisco WebEx Social

Step 6 Sign in to the Director with administrative credentials and take these actions:

a. Click Configuration in the left column.

b. In the NFS area, enter the NFS root of the export in the Exported Directory field.

For example, if you created a folder called webexsocial under the export folder, enter /export/webexsocial.

c. Click Save.

VMware vSphere Configuration for Cisco WebEx SocialCisco WebEx Social supports VMware vSphere 4.0 and 5.0.

Cisco recommends VMware vSphere 4.1 or 5.0 for Cisco WebEx Social for the following reasons:

• VMware vSphere 4.1 and 5.0 CPU scheduler performance is significantly better than that of VMware vSphere 4.0 CPU scheduler.

• VMware vSphere 4.1 and 5.0 have reduced latency for VMware Paravirtualized SCSI (PVSCSI) virtual adapter type compared to that of VMware vSphere 4.0. Cisco WebEx Social virtual machines use the PVSCSI adapter exclusively.

• Cisco recommends that you do not run a Cisco WebEx Social node on the same VMware vSphere Hypervisor 4.0 that is running non-Cisco WebEx Social applications. If you need to run these items side-by-side, use VMware vSphere Hypervisor 4.1 or 5.0.

• When running on VMware vSphere 4.1 or 5.0, Cisco WebEx Social can run side-by-side with other WebEx Social virtual machines on the same vSphere Hypervisor if CPU and memory reservations are set. CPU and memory reservations are set automatically during OVA deployment.

Note Virtual machines for Cisco WebEx Social must be layer-2 adjacent. Placing security devices or any other network appliances between Cisco WebEx Social virtual machines is not supported.

Follow these steps to perform VMWare configuration:

Procedure

Step 1 Provision the UCS server/ESX hosts for Cisco WebEx Social in to a VMware vSphere Cluster.

Step 2 Enable VMware High Availability (HA) and VMware Dynamic Resource Scheduler (DRS) on the cluster, as shown in the settings in Figure 1-1.


OL-27466-01


Figure 1-1 VMWare Settings—Enabling HA and DRS

Step 3 For DRS, leave the VMware DRS Fully Automated parameter at its default middle setting.

Step 4 Configure VMware DRS Anti-Affinity Rules to prevent VMware DRS from migrating redundant Cisco WebEx Social Virtual Machines to the same ESX hosts. See Figure 1-2 for where the Anti-Affinity Rules appear in the screen.


OL-27466-01


Figure 1-2 VMWare DRS Rules

Step 5 Configure VMware Enhanced VMotion Compatibility (EVC) (see Figure 1-3) to match the CPU in the UCS blades.


OL-27466-01

Chapter 1 System Requirements Resource Protection

Figure 1-3 VMWare EVC

Resource ProtectionSome guidelines for protecting resources are:

• Monitor the Cisco WebEx Social VMware Cluster to ensure that the average CPU utilization is at 60 percent or less during steady usage and no more than 90 percent during peak usage.

• Monitor the Cisco WebEx Social VMware Cluster to ensure that the Cisco WebEx Social Virtual Machines and ESX hosts do not come under memory pressure.

VMWare Sizing TablesSee the following tables for guidelines based on the number of Cisco WebEx Social users. The tables are based on a 20-percent concurrent connection of Cisco WebEx Social users.

Table 1-3 Virtual Machine Guidelines—0 to 5,000 Users

Service # of VMs vCPUs Per VM RAM (GB) Per VM

Analytics Store 2 2 4

Cache 2 1 16

Director 1 2 8

Index Store 1 2 8


OL-27466-01

Chapter 1 System Requirements VMWare Sizing Tables

JSON Store 2 2 8

Notifier 1 2 16

App Server 2 4 8

Message Queue 2 1 8

Search Store 2 2 8

RDBMS Store 1 2 16

Worker 2 2 8

Table 1-4 Virtual Machine Guidelines—5,000 to 10,000 Users



Cache 2 1 16

Director 1 2 8

Index Store 1 2 8

JSON Store 2 2 8

Notifier 1 2 16

App Server 2 4 8

Message Queue 2 1 8

Search Store 2 2 8

RDBMS Store 1 4 16

Worker 2 2 8




Cache 4 1 8

Director 1 2 8

Index Store 1 4 10

JSON Store 2 2 8

Notifier 1 2 16

App Server 4 4 8

Message Queue 2 1 8

Search Store 2 2 6

RDBMS Store 1 6 32

Worker 2 4 8

Table 1-3 Virtual Machine Guidelines—0 to 5,000 Users (continued)



OL-27466-01

Chapter 1 System Requirements VMWare Sizing Tables




Cache 6 1 16

Director 1 2 8

Index Store 1 4 10

JSON Store 2 3 10

Notifier 1 4 24

App Server 6 4 8

Message Queue 2 1 8

Search Store 2 2 6

RDBMS Store 1 8 32

Worker 2 4 8




Cache 6 1 16

Director 1 2 8

Index Store 1 4 10

JSON Store 2 3 12

Notifier 1 4 24

App Server 10 4 8

Message Queue 2 1 8

Search Store 2 2 6

RDBMS Store 1 8 32

Worker 2 4 8




Cache 6 1 16

Director 1 2 8

Index Store 1 4 10

JSON Store 2 4 16

Notifier 1 8 36


OL-27466-01

Chapter 1 System Requirements Disk Growth and Size

Disk Growth and SizeEach Cisco WebEx Social virtual machine contains two virtual disks. Virtual disk 1 is used for the operating system. Virtual disk 2 internally maps to the /opt directory, which is used to store applications and their data.

All Cisco WebEx Social virtual machines support online growth of the /opt directory. This can be accomplished by either:

• Expanding the existing virtual disk 2.

• Adding a virtual disk. Add new disks to virtual SCSI adapter 0 first. If all ports on virtual adapter 0 are used, add a virtual SCSI adapter of type “VMware Paravirtual.”.

Note Expanding virtual disk 1, which is used for the operating system, is not supported.

A cron job runs within the Cisco WebEx Social virtual machine that calls the lvm-expand.sh script every five minutes. The lvm-expand.sh script scans for new free space and new virtual disks. When either is found, the lvm-expand.sh script extends the LVM volume group, LVM logical volume, and finally the Ext4 partition. This entire process is transparent to the administrator.

App Server 12 4 8

Message Queue 2 1 8

Search Store 2 2 6

RDBMS Store 1 8 64

Worker 2 4 8




Cache 6 1 16

Director 1 2 8

Index Store 1 4 10

JSON Store 2 4 16

Notifier 1 8 36

App Server 14 4 8

Message Queue 2 1 8

Search Store 2 2 6

RDBMS Store 1 8 64

Worker 2 4 8

Table 1-8 Virtual Machine Guidelines—60,000 to 80,000 Users (continued)



OL-27466-01

Chapter 1 System Requirements Load Balancer Information

Load Balancer InformationA load balancer, such as Cisco Application Control Engine, is required with Cisco WebEx Social. Cisco Application Control Engine can be deployed in Routed Mode or in Bridged Mode.

The following list includes requirements and recommendations for load balancers:

• Create a maintenance page for redirecting users. Each Cisco WebEx Social virtual machine supports a maximum of 1500 concurrently connected users.

– Set the maximum connections (max conns) to 1500.

– Set the recover threshold (min conns) to 1400.

• Persistent sessions (sometimes called Source IP Sticky sessions) are required.

• When deploying Cisco WebEx Social with a load balancer, it is recommended that you define a backup server farm for situations when sufficient resources are not available to handle the client load.

• Setting minimum cookie size to 8K or greater is recommended.

• Round Robin predictor is recommended for load balancing.

• For each App Server node in your deployment, configure the load balancer health check (probe) to invoke http://App_Server_IP_Address/monit/status.do. This configuration causes an App Server node to return XML data that includes a status code and status text. For example:

<?xml version="1.0" encoding="UTF-8" ?><state-manager> <quad> <code>200</code> <status>OK</status> </quad></state-manager>

PlanningFor planning purposes, it is recommended that you write down the values of the following items for each node because you will be prompted to enter these values when you install each node:

• Fully qualified domain name (of each node and of the Director)

• IP address

• IP netmask

• IP default gateway

• Default DNS domain

• Primary name server

• Any additional name servers

• Administrator password

Note DNS is required for the Cisco WebEx Social network.


OL-27466-01

Chapter 1 System Requirements Planning


OL-27466-01


C H A P T E R 2
Installing Cisco WebEx Social
This chapter describes how to install Cisco WebEx Social.

This chapter includes these topics:

• Before You Begin, page 2-1

• Installing Cisco WebEx Social 3.0, page 2-1

Before You BeginBefore you begin installation, review the following guidelines and requirements:

• Verify that your current hardware meets the requirements listed in Chapter 1, “System Requirements.”

• Set up the NFS server as described in the “NFS Requirements and Setup” section on page 1-4.

• Planned your network by referring to the “Planning” section on page 1-13.

• This document makes many references to .ova files. These references are generic, but the information below describes how to know which .ova file pertains to which release:

WebExSocial-<major#>.<minor#>.<update#>.<release#>.<build#>.ova

• All operating system-level administrative and root passwords must be at least six characters long, and must contain at least one uppercase letter and one numeric character.

Installing Cisco WebEx Social 3.0This section describes how to install Cisco WebEx Social release 3.0.

To install Cisco WebEx Social, follow these steps:

Procedure

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

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

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


Chapter 2 Installing Cisco WebEx Social Installing Cisco WebEx Social 3.0

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. When the Properties window for the OVF template appears, click Next without entering information in any field in this window.

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

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

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

Step 2 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.


OL-27466-01


f. In the Network Settings screen, configure values in the Primary Nameserver field and Hostname 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 3 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. Default credentials work for a fresh installation.

– 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 4 In the Director, click Configuration in the left panel and in each area of the Configuration window, enter appropriate values for your deployment and click Save.

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

Step 5 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 6 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.


f. Select Apply Configuration.

Step 7 Take these actions:

a. Use SSH to access the Director node and check the following log files to monitor the progress of the RDBMS Store deployment:

– On the RDBMS node: /opt/logs/date/RDBMS_hostname_messages

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


OL-27466-01


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

b. Use SSH to access the RDBMS node and make sure that this node is up and running by entering this command:

service dbora status

Step 8 In the Director, click Configuration in the left panel and in the Notifier area, configure items as appropriate for your deployment and click Save.



Caution Do not enable any roles at this time.

b. From the Role drop-down list, select a node to add.

c. In the FQDN field, enter the fully qualified domain name of the node you are adding. (Do not enter a host name or an IP address in this field.)

d. Click Add.

e. Repeat steps a through d for each node in your Cisco WebEx Social environment. (For descriptions and requirement for Cisco WebEx Social roles, see Table 1-1 on page 1-2).

Step 10 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 the node.



d. Select the NIC to configure.


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.



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



b. Click the Enable button next to each Cache role.

c. Click the Enable button next to one App Server node and wait for the Cisco WebEx Social Welcome page to come up on that node

d. Monitor the /opt/cisco/quad/deploy folder on the App Server node that you enabled for all .war files to be consumed. When these files are consumed, continue with this procedure.

e. Log in to the App Server that you enabled with the user name test@your_company.com and the password test.


OL-27466-01


f. After you successfully log in to the App Server node, click the Enable button next to each App Server role that you have not yet enabled.

g. Click the Enable button next to each Worker role.

Step 12 Perform the post-installation steps that the following sections describe:

a. Provisioning Cisco WebEx Social to Communicate with the Notifier Server, page 4-1

b. Search Indexing Step, page 4-3


OL-27466-01



OL-27466-01


C H A P T E R 3
Upgrading Cisco WebEx Social
This chapter describes how to upgrade Cisco WebEx Social to release 3.0. It includes these topics:

• Supported Upgrade Paths, page 3-1

• Generating Database Passwords, page 3-1

• Upgrading to Release 3.0, page 3-2

• Upgrading to Release 3.0 SR1, page 3-9



Supported Upgrade PathsYou 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 PasswordsThe 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:


Chapter 3 Upgrading Cisco WebEx Social Upgrading to Release 3.0

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.0To 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:


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:

Output Line Corresponding Username

quadbpass quaddb

openfiredbpass xmppdb


OL-27466-01


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


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


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


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


# 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 on page 3-1.)

# 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


OL-27466-01


# 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 on page 1-2.)

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.




OL-27466-01


d. Select Configure eth0 Interface.





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.



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.


f. Select Apply Configuration.


OL-27466-01


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.



d. Select the NIC to configure.





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.


OL-27466-01


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


OL-27466-01


h. Enter these commands:

sudo service search start



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



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



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:



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.


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


OL-27466-01

Chapter 3 Upgrading Cisco WebEx Social Upgrading to Release 3.0 SR1

e. Enter this command:

sudo service quad stop

f. Take these actions:


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


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:


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:



ActiMigMonitorThrd() Activity collections indexing ends

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



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

Upgrading to Release 3.0 SR1You 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 {} \;


OL-27466-01


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 {} \;


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 on page 5-2.

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:



b. Take these actions:



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

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


OL-27466-01





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:



UpgradeProcessSprint20SR1.doUpgrade():Complete...

e. Enter this command:

sudo service quad stop

f. Take these actions:



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

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


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


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:


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:



ActiMigMonitorThrd() Activity collections indexing ends

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



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


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.


OL-27466-01


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


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





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

Upgrading to Release 3.0 SR3You 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.



OL-27466-01


C H A P T E R 4
Post-Installation and Post-Upgrade Steps
This section contains procedures that should be performed after an installation or an upgrade. Perform procedures in this section only if you were directed to do so from either the installation chapter or the upgrade chapter.

This section contains the following topics:

• Provisioning Cisco WebEx Social to Communicate with the Notifier Server, page 4-1

• LDAP Sync, page 4-3

• Search Indexing Step, page 4-3

• Updating the Community Templates, page 4-4

• Updating Your Company Name, page 4-5

• Updating the EULA, page 4-6

• Changing NFS Settings, page 4-7

Provisioning Cisco WebEx Social to Communicate with the Notifier Server

This procedure is applicable after either a fresh installation or an upgrade.

Before you perform this procedure, you must configure Notifier settings and then add a Notification Node in the Director. For more information, see Cisco WebEx Social Administration Guide.

To provision Cisco WebEx Social to Communicate with the Notifier Server, follow these steps:

Procedure

Step 1 Sign in to Cisco WebEx Social as an administrator.

Step 2 Take these actions to access the Common Configurations window:




d. Click Common Configurations in the Server drawer.

Step 3 Select t the Notification Service tab.


Chapter 4 Post-Installation and Post-Upgrade Steps Provisioning Cisco WebEx Social to Communicate with the Notifier Server

Step 4 Verify that at least one Message Queue node is running. If it is not, enable the Message Queue nodes, verify they are running, then restart the quad service on all App Server nodes.

Step 5 In the Notification Service tab, click Start Synchronization.

The system displays a message that informs you when the synchronization process completes.

Step 6 If the Cisco WebEx Social node that is running the synchronization operation is restarted in the middle of this operation, click Reset Sync Flag, then click Start Synchronization again.

Step 7 If you received a synchronization-error notification, you can resume the synchronization where it was stopped by clicking the Resume Synchronization button, or you can start the synchronization from the beginning by clicking the Start Synchronization button.

Step 8 To receive XMPP updates:

a. Sign out of Cisco WebEx Social.

b. Sign in to Cisco WebEx Social as a regular user.

Additional Steps

To access the Notifier administration user console, follow these steps:

Procedure

Step 1 Enable ports 9095 and 9096 in the firewall by performing the following substeps:

Note For security reasons, ports 9095 (for http) and 9096 (for https), which are used by the Notifier administration console, are blocked by the firewall by default.

a. Use an SSH client to access the Notifier server and log in as the admin user.


sudo iptables -A INPUT -p tcp --dport 9095 -j ACCEPT

sudo iptables -A INPUT -p tcp --dport 9096 -j ACCEPT

Step 2 Sign in to the console as follows, where Notifier_server_host is the fully qualified domain name or IP address of the Notifier node:

http://Notifier_server_host:9095\

Use the username admin and use the Unified Access password that you set when you performed the Cisco WebEx Social installation or upgrade procedure.

Step 3 To close the ports, enter the following command:

sudo /sbin/service firewall restart

For more information about the Notification Service window, see Cisco WebEx Social Administration Guide.


OL-27466-01

Chapter 4 Post-Installation and Post-Upgrade Steps LDAP Sync

LDAP SyncThis procedure is applicable only after an upgrade from Cisco Quad 2.5.2.

To enable synchronization with the LDAP server, follow these steps:

Procedure

Step 1 Sign into a App Server node with administrative credentials.

Step 2 Take these actions to access the Settings window:



c. Click the right-arrow next to Portal

d. Click Password Policies in the Portal drawer.

Step 3 Select Authentication in the right pane of the window.

Step 4 Select the LDAP Directory Sync tab.

Step 5 Check the Enable Synchronizing from LDAP Server box.

Step 6 From the Which node to run sync on drop-down list, select the Cisco WebEx Social server that you want to synchronize to the LDAP server. This server cannot be the Director node. If this node is changed later, both the new and old nodes must be restarted.

Step 7 Click Save in the right panel of the window.

Step 8 Under the Agreements portion of the window, click Add, and fill out all the fields and information about when and how often you want synchronization to occur.

For a detailed descriptions of these options, see the “LDAP Directory Sync” section in Cisco WebEx Social Administration Guide.

Step 9 Click Save.

Step 10 (Optional) If you want to modify an agreement, click on its link and make any changes you want, and save your changes.

Step 11 Check the box next to the agreement you want.

Step 12 Click Save.

Search Indexing StepThis procedure is applicable after either a fresh installation or major upgrade. It may be applicable after a minor upgrade.

To make sure that Search works properly, follow these steps:

Procedure

Step 1 Sign in to a non-Director Cisco WebEx Social node as system administrator.


OL-27466-01

Chapter 4 Post-Installation and Post-Upgrade Steps Updating the Community Templates

Step 2 Take these actions to access the Server Administration window:



c. Click the right-arrow next to Server.


Step 3 In the Resources tab, click the Execute button that appears next to the Synchronize Recommendation action.

Step 4 In the Resources tab, click the Execute button that appears next to the Reindex all search indexes action.

Updating the Community TemplatesThis procedure is applicable only after an upgrade from Cisco Quad 2.5.2.

If you have not customized your community templates, perform the following procedure to apply functionality updates to the community templates. (Do not perform this procedure if you have created customized community templates.)

Procedure

Step 1 Download the following files from the /opt/cisco/quad/deploy folder on any Quad node to your local system:

• Community_template_open.lar

• Community_template_restricted.lar

• Community_template_private.lar

Step 2 Sign in to Cisco WebEx Social as Administrator.

Step 3 Access the Templates tab in the Community Manager window:



c. Click the right-arrow next to Portal

d. Click Community Manager in the Portal drawer.

e. Select the Templates tab.

Step 4 Take these actions to update the hidden community template:

a. Click Standard Hidden Community Template.

b. Click Browse next to the Upload Template (.lar) file field, then navigate to and select the Community_template_private.lar file that you downloaded.

c. Click Save.


OL-27466-01

Chapter 4 Post-Installation and Post-Upgrade Steps Updating Your Company Name

Step 5 Take these actions to update the restricted community template:

a. Click Standard Restricted Community Template.

b. Click Browse next to the Upload Template (.lar) file field, then navigate to and select the Community_template_restricted.lar file that you downloaded.

c. Click Save.

Step 6 Take these actions to update the open community template:

a. Click Standard Open Community Template.

b. Click Browse next to the Upload Template (.lar) file field, then navigate to and select the Community_template_open.lar file that you downloaded.

c. Click Save.

Updating Your Company NameThis procedure is applicable only after fresh installation.

To update the Cisco WebEx Social to properly use your company name, follow these steps:

Step 1 Sign in to the Director.

Step 2 Click Portal under Application.

Step 3 In the Advanced Portal Properties area, change the default values for the properties that the following table describes to values that are appropriate for your company.

For example, change your_company.com to the name of your company.

To quickly locate a property, enter its name in the Search field in the Advanced Portal Properties area.

Property Default Value Description

admin.email.from.address your_email_support_alias @your_company.com

E-mail address that appears in the footer of the e-mail message that is sent to author of a blog when someone comments on the blog

admin.email.from.name your_company_support_name Name that appears in the footer of the e-mail message that is sent to author of a blog when someone comments on the blog

announcements.email.from.address your_email_support_alias @your_company.com

E-mail address from which the message is sent from the announcement portlet

announcements.email.from.name your_company_support_name “From” name or alias for messages from the announcement portlet

calendar.email.from.address your_email_support_alias @your_company.com

“From” address for Community Calendar portlet e-mail event reminders

calendar.email.from.name your_company_support_name “From” name for Community Calendar portlet e-mail event reminders


OL-27466-01

Chapter 4 Post-Installation and Post-Upgrade Steps Updating the EULA

Step 4 Click Save in the Advanced Portal Properties area

Updating the EULAThis procedure is applicable only after an upgrade from Cisco Quad 2.5.2.

To update the Cisco WebEx Social end-user license agreement (EULA), follow these steps:

Procedure


Step 2 Access the License Agreement (EULA) window:



c. Click the right-arrow next to Server.

d. Click License Agreement (EULA) in the Server drawer.

com.cisco.ecp.portlet.moderator.email. from.address

your_company-compliance-officer @your_company.com'

E-mail address of the compliance officer that is included in e-mail messages that are sent to authors of offending content

communities.email.from.address your_email_support_alias @your_company.com

“From” address for e-mail messages that are sent when a membership request is approved or denied

communities.email.from.name your_company_support_name' “From” name for e-mail messages that are sent when a membership request is approved or denied

company.default.web.id your_company.com Default login ID for your company

journal.email.from.address your_email_support_alias @your_company.com

“From” address for Content Publisher portlet e-mail notification messages

journal.email.from.name your_company_support_name “From” name for Content Publisher portlet e-mail notification messages

message.boards.email.from.address your_email_support_alias @your_company.com

“From” address that is sent in an e-mail when a new email thread or category is created in a message board

postfix.mail.domain your_company.com SMTP domain of Cisco WebEx Social

report.problem.email.to.address your_email_support_alias @your_company.com

E-mail address or e-mail alias to which an e-mail message is sent when users use the Report a Problem link in the Help Window

report.problem.email.to.name your_email_support_name Name to which an e-mail message is sent when users use the Report a Problem link in the Help Window.

Property Default Value Description


OL-27466-01

Chapter 4 Post-Installation and Post-Upgrade Steps Setting Maximum File Size for User Images

Step 3 Select English (United States) from the Language drop-down list.

Step 4 Click the Modify button.

Step 5 Select Software License Agreement and click Delete.

Step 6 Click Save.

Setting Maximum File Size for User ImagesThis procedure is applicable only after an upgrade from Cisco Quad 2.5.2.

To update the Cisco WebEx Social end-user license agreement (EULA), follow these steps:

Procedure


Step 2 Access the Server Administration window:





Step 3 Select the File Uploads tab.

Step 4 In the Maximum File Size field under User Images, enter 0 .

Step 5 Click Save.

Changing NFS SettingsIf you need to change any of your NFS Settings in the Director after a fresh installation or an upgrade, follow these steps:

Procedure

Step 1 Log in to the Director with administrative credentials.

Step 2 In the Director, click Topology in the left panel and take these actions:

a. For each role in the Server List area that has an associated Disable button, click that Disable button.

b. Power off nodes that do not have an associated Disable button.

Disable App Server roles first.

Step 3 Power off corresponding virtual machines.


OL-27466-01

Chapter 4 Post-Installation and Post-Upgrade Steps Changing NFS Settings

Step 4 In the Director, take these actions:

a. Click Configuration in the left panel.

b. Enter your new NFS settings in the NFS area.

c. Click Save in the NFS area.

Step 5 Reboot the Director node virtual machine.

Step 6 Power on all virtual machines.

Step 7 Log in to the Director with administrative credentials and take these actions:

a. In the Director, click Topology in the left panel.

b. Enable all roles by clicking the Enable button next to each role in the Server List area in this sequence:

1. For each role in the Server List area that has an associated Enable button, except App Server roles, click that Enable button.

2. Power on nodes that do not have an associated Enable button, except App Server roles.

3. Click the Enable button for each App Server role


OL-27466-01


C H A P T E R 5
Additional Installation-Related Information
This section contains the following topics:

• Enabling or Disabling Cisco WebEx Social Nodes, page 5-1

• Using Refresh Buttons, page 5-1

• Using the Software Window, page 5-2

• Using the Director, page 5-3

• Checking Installation-Related Log Files, page 5-3

Enabling or Disabling Cisco WebEx Social NodesYou use the Topology window in the Director to enable and disable App Server, Cache, and Worker nodes in your Cisco WebEx Social cluster.

Some requirements exist regarding the order in which you must enable or disable nodes:

• When enabling nodes, App Server roles must be enabled after all other roles are enabled. The order of other roles does not matter.

• When disabling nodes, all App Server roles must be disabled first. After that, the order does not matter.

To enable or disable nodes in your Cisco WebEx Social cluster, follow these steps:

Procedure

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

Step 2 Select Topology under Deployment.

Step 3 Use the Enable and Disable buttons to start or stop a node (role).

Using Refresh ButtonsThe Server List area in the Deployment Topology window in the Director contains Refresh buttons. Use these buttons to fetch version information and to display current operational status of a node. Possible states that the Status column shows are:


Chapter 5 Additional Installation-Related Information Using the Software Window

• Running

• Stopped

• Not Installed

• Unreachable Host

• Connection Failed

Using the Software WindowYou can use the Software window in the Director window for upgrades provided that you have received a patch in the form of an .img file. To upgrade to the latest version of Cisco WebEx Social using the provided .img file, perform the following steps:

Procedure

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

Step 2 Select Software Maintenance under Deployment.

Step 3 In the Host Name field, enter the fully qualified domain name or the IP address of the Linux/Unix node where you placed the patch .img file.

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

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

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

Step 7 Click Upload.

The software version that you uploaded appears in the Available Upgrade Version field in the Upgrade area of the window.

Step 8 Click Upgrade.

The software on each node in your Cisco WebEx Social cluster is upgraded.

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

Step 9 Allow up to 15 minutes for the Director to automatically restart.

Step 10 Sign in to the Director with administrator credentials.

Step 11 Click the Topology tab.

Step 12 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


OL-27466-01

Chapter 5 Additional Installation-Related Information Using the Director

Step 13 Because the Cache, App Server, and Worker nodes will be in the Disabled state after a successful upgrade, do the following from the Topology tab of the Deployment window:

a. Enable Cache nodes.

b. Enable App Server nodes.

c. Enable Worker nodes.

Step 14 Allow up to 15 minutes for the App Server nodes to become enabled.

Monitor the /opt/cisco/quad/deploy folder on App Server nodes for all .war files to be consumed. When these files are consumed, Cisco WebEx Social should be ready for use.

Using the DirectorThe Director is used for setting values of specific properties to complete configuration for some Cisco WebEx Social features. See Cisco WebEx Social Administration Guide for information about when to set properties.

Checking Installation-Related Log FilesYou can check the progress of the upgrade process for a node by opening the following log files on the Director or by running a service puppet debug:

/opt/logs/date/hostname_messages


OL-27466-01

Chapter 5 Additional Installation-Related Information Checking Installation-Related Log Files


OL-27466-01

Quad Install

Documents

Transcript of Quad Install