Cisco Unified MeetingPlace, Release 7.1 -- How to Install Web Conferencing in a Load-Balancing Configuration

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.1

Up one page: Installation


Cisco Unified MeetingPlace Web Conferencing requires Microsoft SQL Server 2000 (Service Pack 4). During the installation, you can choose the local SQL Server option or the remote SQL Server option. If you choose the remote SQL Server option, you can use SQL Server 2005 (Service Pack 2) instead of SQL Server 2000 (Service Pack 4). To use SQL Server 2005, first install the SQL Server 2005 backward compatibility software (the Distributed Management Objects [DMO] component only) on the Web Server.

Note: All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the replication. SQL Servers can be “remote” in that they are installed on separate machines within a local data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.

For more information, see SQL Server Requirements.

Cisco Unified MeetingPlace Web Servers make use of an algorithmic formula to evenly distribute web-conferencing requests within a cluster of Web Servers. For detailed information on the requirements for a load balancing cluster, see Load Balancing Requirements.

Note: SQL Server Clustering is not supported.


Follow the steps in these procedures in this order.


Contents

Installing and Configuring the First Internal Web Server

Before You Begin

Complete the tasks in Preparing the Internal and External Clusters.


Procedure
  1. Install Cisco Unified MeetingPlace Web Conferencing on the first Web Server in your internal cluster.
    • Choose Internal (Full Access) for the Server Location.
    • Choose the applicable option for the Database Location:
      • Local Server if the SQL Server is installed locally.
      • Existing Remote Server if there is a full SQL Server installed elsewhere.
    • Choose to reboot your computer later, then click Finish when you reach the final installer window.
  2. Configure the shared storage for this Web Server by performing the procedure in the "Configuring Shared Storage" module of the Configuration Guide for Cisco Unified MeetingPlace Release 7.1 or the online help in the administrator interface.


What to Do Next



Installing Additional Internal Web Servers

Restriction

When installing two or more Web Servers that share a single SQL Server database and point to the same Cisco Unified MeetingPlace Application Server, you must specify the same Cisco Unified MeetingPlace Server hostname (FQDN) for all Web Servers.

Before You Begin

Complete Installing and Configuring the First Internal Web Server.


Procedure
  1. Copy the GUIDS.reg file from the first internal Web Server to the next Web Server in your internal cluster. See Copying GUIDS from One Web Server to Another Web Server.
  2. Install Cisco Unified MeetingPlace Web Conferencing on an additional Web Server in your internal cluster.
    • Choose Internal (Full Access) for the Server Location.
    • Choose Existing remote server for the Database Location.
    • Specify the SQL Server that you used for the first internal Web Server.
    • Choose to reboot your computer later, then click Finish when you reach the final installer window.
  3. Configure the shared storage for this Web Server by performing the procedure in the "Configuring Shared Storage" module in the Cisco Unified MeetingPlace Release 7.1 Configuration Guide at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.
  4. Repeat this procedure until you have installed all of your internal Web Servers.


What to Do Next

Installing the First External Web Server

Copying GUIDS from One Web Server to Another Web Server

The GUIDS entries for the site and the system must match between the internal and external Web Servers and also between all internal servers. Make sure that you run the GUIDS.reg file on each external Web Server before installing Cisco Unified MeetingPlace Web Conferencing on that server.


Note: You must complete this step before running the Web Conferencing installer on the external Web Server. If you skip this step or complete it incorrectly, presentation mode will not work for internal users in external meetings. To recover from this problem, you must rebuild the SQL Server database.


Procedure
  1. Copy the drive:\Program Files\Cisco Systems\MPWebGUIDS.reg file from the first internal Web Server.
  2. Paste the GUIDS.reg file in the drive:\Temp directory of the first external Web Server.
  3. Double-click the GUIDS.reg file from the first internal Web Server, to install it.
  4. Click OK when prompted to add the information from the GUIDS.reg file to the registry.


What to Do Next

Installing the First External Web Server.

Installing the First External Web Server

Before You Begin
  • Complete installing and configuring at least one internal Cisco Unified MeetingPlace Web Server.


Note: The GUIDS entries for the site and the system must match between the internal and external Web Servers. Make sure that you run the GUIDS.reg file on each external Web Server before installing Cisco Unified MeetingPlace Web Conferencing.

Procedure
  1. Install Cisco Unified MeetingPlace Web Conferencing on the first Web Server in your external cluster.
    • Choose External (Limited Access) for the Server Location.
    • Choose the applicable option for the Database Location:
      • Local Server if the SQL Server is installed locally.
      • Existing Remote Server if there is a full SQL Server installed elsewhere.
    • Choose to reboot your computer later, then click Finish when you reach the final installer window.
  2. Configure the shared storage for this Web Server by performing the procedure in the "Configuring Shared Storage" module of the Configuration Guide for Cisco Unified MeetingPlace Release 7.1 or the online help in the administrator interface.


What to Do Next



Installing Additional External Web Servers

Before You Begin

Complete the tasks in Installing the First External Web Server.


Restriction

When installing two or more Web Servers that share a single SQL Server database and point to the same Cisco Unified MeetingPlace Application Server, you must specify the same Cisco Unified MeetingPlace Server hostname (FQDN) for all Web Servers.

Procedure
  1. Install Cisco Unified MeetingPlace Web Conferencing on an additional external Web Server.
    • Choose External (Limited Access) for the Server Location.
    • Choose Existing Remote Server for the Database Location.
    • Specify the SQL Server that you used for the first external Web Server.
    • Choose to reboot your computer later, then click Finish when you reach the final installer window.
  2. Configure the shared storage for this Web Server by performing the procedure in the "Configuring Shared Storage" section of the Configuration Guide for Cisco Unified MeetingPlace Release 7.1 or the online help in the administrator interface.
  3. Repeat this procedure until you have installed all the external Web Servers.


What to Do Next

Linking the Internal and External Servers



Linking the Internal and External Servers

External meetings are held on an external Web Server so that users can access their meetings from the Internet. Rather than have all of your users log in to a particular external Web Server, configure automatic redirection of all external meetings from your internal Web Servers to a designated external Web Server.


The internal and external Web Servers (or clusters of Web Servers) each operate as completely separate units until you link them by configuring automatic redirection.


Before You Begin

You must have properly installed Cisco Unified MeetingPlace Web Conferencing on all of your internal and external Web Servers.


Procedure
  1. Sign in to Cisco Unified MeetingPlace Web Conferencing from an internal Web Server.
  2. Click Admin > Web Server.
  3. Enter the name of a new Web Server from a blank Web Server Name field, to represent your designated external Web Server.
  4. For Hostname, enter the fully qualified domain name (FQDN) of your external Web Server (for example, hostname.domain.com). If your Web Server is not in a Domain Name Server (DNS), enter the IP address instead. Note the following considerations:
    • You must be able to resolve this hostname from the internal Web Server.
    • If you plan to use SSL, make sure that the hostname on the SSL certificate resolves to the IP address of the external Web Server.
    • If you plan to use SSL and a segmented DNS, make sure that the DNS name and the SSL certificate name differ.
  5. Click Submit to add this Web Server to the database.
    This Web Server now appears as part of your list of Web Servers on the bottom portion of the page.
  6. Continue with Step 7 if you have more than one internal Web Server.
    Note: If you have only one internal Web Server and one external Web Server, you are finished with this procedure.
  7. Return to the main Admin page.
  8. Click Site.
  9. Click the Site Name that represents your cluster of internal Web Servers. The Site Name should have a default value equal to the NetBIO name of the first Web Server you installed in this cluster.
  10. Choose the external Web Server that you just added for the DMZ Web Server.
    This configures the internal Web Servers in this cluster to point to this external Web Server in the case of external meetings.
  11. Click Submit.
    Tip: The external cluster does not require any additional SQL Server database configurations.

Rating: 0.0/5 (0 votes cast)

Personal tools