Cisco Cisco WebEx Social for Mobile

다운로드
페이지 6
 
3
Disabling the Email Functionality in Cisco WebEx Social 3.0.1 SR3, 3.1 SR1, and 3.3
Rev. 03 (04/22/13)
  Removing the Community Email Application from Existing Communities
c.
Navigate to the location where you saved the exported template for the respective community type 
and select it.
d.
Wait for the upload to complete and click Save.
Removing the Community Email Application from Existing 
Communities
After you have prevented users from creating new communities that feature the Community Email 
application you may want to remove the application from existing communities. Running it does not 
prevent community administrators or owners from readding the application; to do this, see 
.
You must have Administrator privileges on App Server nodes to complete this procedure successfully. 
The steps are as follows:
Step 1
Transfer communityEmailPortlet.jsp to an App Server node:
a.
Log in as admin to any App Server node in your topology.
b.
Using your preferred method, transfer the provided communityEmailPortlet.jsp file to the App 
Server node’s filesystem (for example to /home/admin).
c.
Copy the communityEmailPortlet.jsp file to /opt/cisco/quad/tomcat/webapps/ROOT/. For example 
if you stored the file to /home/admin use this command:
sudo cp /home/admin/communityEmailPortlet.jsp /opt/cisco/quad/tomcat/webapps/ROOT
Step 2
Use communityEmailPortlet.jsp to remove the Community Email application from all existing 
communities:
a.
Sign in to Cisco WebEx Social using an account with Administrator privileges.
b.
Keeping the page loaded, open a new tab or window in your Web browser.
c.
In the address bar of the new tab or window enter:
http(s)://<WebEx_Social_URL>/communityEmailPortlet.jsp?action=remove
where WebEx_Social_URL is the base URL that you use to access Cisco WebEx Social.
d.
Press enter to execute the removal request. You see a confirmation message when the operation 
completes.
Later, if you want to undo the removal of the Community Email application, you can do so by 
substituting ?action=add for ?action=remove at the end of the URL.