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

From DocWiki

Revision as of 15:23, 4 April 2011 by MeetingPlace Moderator (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.1

Up one page: Installation



Contents

Reviewing System Requirements

Before installing the Cisco Unified MeetingPlace Web Conferencing in a load-balancing configuration, read the following:


Gathering Installation Values

Gather and record the information in Gathering Installation Values to prepare for your installation of Cisco Unified MeetingPlace Web Conferencing. See Installing the Cisco Unified MeetingPlace Web Conferencing Server for basic information about installing Cisco Unified MeetingPlace Web Conferencing.


Preparing the Internal and External Clusters

Perform this procedure twice: once for the internal cluster and a second time for the external cluster.


Restrictions
  • We do not support Microsoft Network Load Balancing.
  • We do not support third-party web server load balancing.
  • Cisco Unified MeetingPlace Web Conferencing requires Microsoft SQL Server 2000 (Service Pack 4). If you choose the remote SQL Server option, then SQL Server 2005 (Service Pack 2) is also supported. 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. See SQL Server Requirements.
  • SQL Server clustering is not supported.
Procedure
  1. Determine and create a common domain Windows administration account.
    All of the Web Servers in this cluster use this account. It starts Web Conferencing services and allows all Web Servers in this cluster to access the shared storage location by using a Universal Naming Convention (UNC) path, for example, \\servername\shared folder\Resource.
    After creating the account, write down the value, which you will need later.
    Note: Enter different values for your internal and external clusters.
  2. Determine and create a shared storage location.
    You can create this folder on the same system as your first internal Web Server (for the internal cluster) on the same system as your first external Web Server (for the external cluster), or on a separate system. Keep in mind that this shared storage location is where attachments are stored and, therefore, where all Web Servers in this cluster go to find attachments.
    After creating the location, write down the value as a UNC path, for example, \\servername\shared folder\MPWeb.
  3. Decide on a shared storage configuration for the cluster:
    • Backup-only storage-Content is copied to the primary external storage device and pulled to the local content folder on each Web Server in the cluster as needed. This configuration frees resources on the local server which is especially helpful in a large cluster.
    • Fully-mirrored storage-Content is copied to the primary external storage device as well as to all other Web Servers in the cluster. We recommend this configuration for small clusters unless you have a large amount of content that is randomly accessed.

Rating: 0.0/5 (0 votes cast)

Personal tools