Table Of Contents
Post-Installation and Post-Upgrade Steps
Provisioning Cisco WebEx Social to Communicate with the Notifier Server
LDAP Sync
Search Indexing Step
Updating the Community Templates
Updating Your Company Name
Updating the EULA
Setting Maximum File Size for User Images
Changing NFS Settings
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
•LDAP Sync
•Search Indexing Step
•Updating the Community Templates
•Updating Your Company Name
•Updating the EULA
•Changing NFS Settings
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:
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 Common Configurations in the Server drawer.
Step 3 Select t the Notification Service tab.
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.
b. Enter these commands:
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.
LDAP Sync
This 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:
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 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 Step
This 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 an App Server node as an administrator.
Step 2 Take these actions to access the Server Administration window:
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.
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 Templates
This 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:
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 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.
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 Name
This 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
|
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.
|
Step 4 Click Save in the Advanced Portal Properties area
Updating the EULA
This 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 1 Sign in to Cisco WebEx Social as Administrator.
Step 2 Access the License Agreement (EULA) window:
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 License Agreement (EULA) in the Server drawer.
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 Images
This 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 1 Sign in to Cisco WebEx Social as Administrator.
Step 2 Access the Server Administration window:
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.
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 Settings
If 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.
Disable App Server roles first.
b. Power off all virtual machines except the Director.
Disable App Server roles first.
Step 3 Power off corresponding virtual machines.
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. Click the Enable button for each App Server role
Feedback
