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

Post-Installation and Post-Upgrade Steps

Table Of Contents

Post-Installation and Post-Upgrade Steps

Updating Your Company Name

Updating the Cisco WebEx Social for Microsoft Office Plugin Download Location

Setting the Default Logout Page Option

Manually Enabling Synthetic Monitoring

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:

Updating Your Company Name

Updating the Cisco WebEx Social for Microsoft Office Plugin Download Location

Setting the Default Logout Page Option

Manually Enabling Synthetic Monitoring

Changing NFS Settings

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 In the Director, click Application in the Menu bar, then click Portal in the left panel.

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

Email address that appears in the footer of the email message that is sent to the author of a blog when someone comments on the blog.

admin.email.from.name

your_company_support_name

The name that appears in the footer of the email message that is sent to the author of a blog when someone comments on the blog.

company.default.web.id

your_company.com

Default login ID for your company.

outbound.email.from.address

The default value is empty. In this case, the sender email address is noreply@mail_domain, where mail_domain is the value that you defined in the Mail Domain field as described in the "Email Configuration" section in Cisco WebEx Social Administration Guide.

Email address of the outbound email notification sender.

outbound.email.from.name

Cisco WebEx Social

Name of the outbound email notification sender.

report.problem.email.to.address

your_email_support_alias
@your_company.com

Email address or email alias to which an email 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 email 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.

Step 5 Click Apply Config in the left panel.


Updating the Cisco WebEx Social for Microsoft Office Plugin Download Location

This procedure is optional after a fresh installation or an upgrade.

To update the Cisco WebEx Social for Microsoft Office Plugin Download location, follow these steps:


Step 1 Sign in to the Director.

Step 2 In the Director, click Application in the Menu bar, then click Portal in the left panel.

Step 3 In the Advanced Portal Properties area, enter the following value for the com.cisco.social.office.client.updateUrl property:

${web.server.protocol}://${virtual.host}/productivityplugins/

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

Step 4 Click Save in the Advanced Portal Properties area.

Step 5 Click Apply Config in the left panel.


Setting the Default Logout Page Option

This procedure is applicable only after an upgrade if SSO is not enabled in your deployment.

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 Portal

d. Click Settings in the Portal drawer.

Step 3 Select the General tab.

Step 4 Enter a slash (/) in the Default Logout Page field in the Navigation area.

Step 5 Click Save.


Manually Enabling Synthetic Monitoring

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

The synthetic monitor runs periodically to verify basic Cisco WebEx Social features. For more information, see the "Synthetic Monitoring" section in Cisco WebEx Social Administration Guide.

If you want to use the Synthetic Monitoring feature, take these actions:

Procedure


Step 1 Use an SSH client to access the Director server and log in as the admin user.

Step 2 Enter this command:

apicurl -X POST localhost:2103/parameters -d 'nodeid=0&key=
synthetic_monitor_disabled&val=false'; apicurl -X GET localhost:2103/apply_config/role/quad


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 and take these actions:

a. In the Director, click System in the Menu bar, click Topology in the left panel, and take these actions:

b. Click the Disable All button in the Server List area.

Step 2 In the vSphere client, power off the virtual machines for the App Server, Cache, and Worker nodes.

Step 3 Take these actions on each Message Queue to stop ActiveMQ:

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

b. Enter these commands:

sudo monit stop

sudo puppet stop

sudo activemq stop

c. Repeat this step for each Message Queue.

Step 4 In the Director, take these actions:

a. Click System in the Menu bar, then click Configuration in the left panel.

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

c. Click Save in the NFS area.

d. Click Apply Config in the left panel.

Step 5 Reboot the Director node virtual machine.

Step 6 Take these actions on each Message Queue to start ActiveMQ:

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

b. Enter these commands:

sudo monit start

sudo puppet start

sudo activemq start

c. Repeat this step for each Message Queue.

Step 7 Power on the virtual machines that you powered off.

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

a. In the Director, click System in the Menu bar, click Topology in the left panel, and take these actions:

b. Click the Enable All button in the Server List area.