Table Of Contents
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3
About the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
About SQL Server Integration
MSDE Database Size
MSDE Database Scalability
About SQL Server Installation Options
About Sun Java Runtime Environment
Preinstallation Tasks: Cisco Unified MeetingPlace Web Conferencing Release 5.3
Installing Cisco Unified MeetingPlace Audio Server Release 5.3
Installing SQL Server on a Remote Server
Creating a Least Privileged SQL Account
Assigning Installation and Ongoing Rights
Assigning Server and Database Roles
Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values
Installation Tasks: Cisco Unified MeetingPlace Web Conferencing Release 5.3
Installing the Operating System on the Cisco MCS Server
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3
How to Test the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
Defining the Cisco Unified MeetingPlace Web Conferencing Server
Testing the Web Server Over an HTTP Connection
Testing the Web Server Over an HTTPS Connection
Testing the Meeting Console Connection
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3
This chapter describes how to complete a new installation of Cisco Unified MeetingPlace Web Conferencing Release 5.3. It does not describe upgrades. For information about upgrading, see "Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3."
Topics in this section include:
•
About the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
•Preinstallation Tasks: Cisco Unified MeetingPlace Web Conferencing Release 5.3
•Installation Tasks: Cisco Unified MeetingPlace Web Conferencing Release 5.3
•Defining the Cisco Unified MeetingPlace Web Conferencing Server
•How to Test the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
Note Before reviewing this chapter, make sure that you read the Release Notes for Cisco Unified MeetingPlace Web Conferencing Release 5.3 for updated system requirements. New installations of Release 5.3 require a Cisco MCS.
About the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
Before you begin installing Cisco Unified MeetingPlace Web Conferencing, make sure that you understand the following concepts:
•About SQL Server Integration
•About SQL Server Installation Options
•About Sun Java Runtime Environment
About SQL Server Integration
Cisco Unified MeetingPlace Web Conferencing is closely integrated with Microsoft SQL Server. It uses Microsoft SQL Server for its databases: MPWEB and MPWEB-Slave-######.
All new servers being deployed must be either Cisco MCS or, for MeetingPlace customers with a legacy system, Cisco MCS-equivalent servers.
Cisco Unified MeetingPlace Web Conferencing comes with a distributable version of SQL Server called MSDE 2000. Although MSDE 2000 and SQL Server 2000 are based on the same technology, MSDE 2000 does not scale as well as SQL Server 2000. Because of this by-design limitation, Cisco Unified MeetingPlace Web Conferencing customers running MSDE 2000 can encounter performance and scalability-related problems when their usage of Cisco Unified MeetingPlace Web Conferencing grows.
The following sections provide information about how to anticipate and diagnose performance and scalability limitations related to MSDE:
•MSDE Database Size
•MSDE Database Scalability
MSDE Database Size
MSDE limits the database size to 2 GB. If either the MPWEB or the MPWEB-Slave database reaches 2 GB, the Cisco Unified MeetingPlace Web Conferencing application can fail. Therefore, you must monitor the growth of the MPWEB databases and take one of the following actions before either database reaches 2 GB:
•Set a more aggressive value for the Purge meetings held before (Days) parameter. For more information, see the "About the MeetingNotes Purge Parameter" section in Chapter 3 of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.
•Upgrade to a full version of SQL Server with a per processor license, as this does not have a database size limitation.
MSDE Database Scalability
MSDE implements a concurrent workload throttle mechanism to limit scalability under heavy load. Currently, this mechanism activates when more than eight SQL queries execute concurrently. However, there is no direct mapping between the number of active web-conferencing users and the exceeding of this limit.
Rather, the exceeding of this limit depends on the following:
•Number of active users
•Features that are used at any given time and how these features interact with the database
•Current size of the database
•Power of the server (CPU, disks, and so on)
Although Microsoft does not give information about the specific algorithm that is used to implement this concurrent workload throttle mechanism, our tests show that the slowdown is based on the number of SQL queries that exceed the limit of eight queries. For example, if 10 concurrent queries execute, the slowdown is minimal. If 20 concurrent queries execute, the slowdown is more noticeable. If 40 or more concurrent queries execute, the slowdown can become so significant that users find Cisco Unified MeetingPlace Web Conferencing as unresponsive or non-functional.
Related Topics
•See the "How to Assess Performance Degradation Due to the Database Scalability Limitation of MSDE" section in the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.
About SQL Server Installation Options
To ease installation, Cisco Unified MeetingPlace Web Conferencing is bundled with both Microsoft SQL Server and Microsoft SQL Desktop Engine (MSDE). You can choose to install SQL Server on either the same machine as Cisco Unified MeetingPlace Web Conferencing or, for better performance, on a separate machine.
If you choose to install SQL Server on the same machine as Cisco Unified MeetingPlace Web Conferencing, choose Local as your SQL Server database location during your installation. If the installer fails to detect a version of SQL Server 2000 on your local system, it installs both SQL Server 2000 and the appropriate Service Pack for you automatically. No additional steps are required.
Note Check the Release Notes for your release of Cisco Unified MeetingPlace Web Conferencing for the required Service Pack.
If you choose to install SQL Server on a separate machine, install both SQL Server 2000 and the appropriate Service Pack before installing Cisco Unified MeetingPlace Web Conferencing; then, on the MCS, install Cisco Unified MeetingPlace Web Conferencing. During installation, choose Existing remote as your SQL Server database location and enter the appropriate SQL access information.
For more information about what conditions must be met for Cisco Unified MeetingPlace Web Conferencing to automatically install either SQL Server or MSDE, see Table 2-1.
Table 2-1 SQL Server Installation Requirements
If the following conditions are met...
|
Cisco Unified MeetingPlace Web Conferencing will...
|
•You install Cisco Unified MeetingPlace Web Conferencing on a Cisco MCS server or a Cisco MCS equivalent server that accepts the installation of the Cisco MCS server OS image
•During installation, you specify the SQL Server location as Local.
•The installer does not detect an existing installation of SQL Server on the local server.
|
Install a full version of SQL Server 2000
|
•You install Cisco Unified MeetingPlace Web Conferencing on a non-Cisco MCS server.
•During installation, you specify the SQL Server installation location as Local during the Cisco Unified MeetingPlace Web Conferencing installation.
•The installer does not detect an existing installation of SQL Server on the local server.
|
Install MSDE
|
•During installation, you specify the SQL Server installation location as Remote.
Note This option requires that you install either full SQL or MSDE on the remote server before you install Cisco Unified MeetingPlace Web Conferencing
OR
•You specify the SQL Server installation location as Local, but the Cisco Unified MeetingPlace Web Conferencing installer detects that SQL or MSDE is already installed on the local server.
|
Not install SQL Server or MSDE
|
•You install Cisco Unified MeetingPlace Web Conferencing on a Cisco MCS server.
•You install a full version of SQL Server on the same Cisco MCS server, or it already exists locally.
|
Install the SQL Server Service Pack
Note If the SQL Server Service Pack is not installed automatically, download the appropriate Service Pack from the Microsoft website and do a manual install. See the Release Notes for your release of Cisco Unified MeetingPlace Web Conferencing for the required Service Pack version.
|
About Sun Java Runtime Environment
Cisco Unified MeetingPlace Web Conferencing requires Sun Java Runtime Environment (JRE) 1.4.2_05. If you currently have a release of Sun JRE installed on the machine where you are installing Cisco Unified MeetingPlace Web Conferencing, make sure that it is Release 1.4.2_05. Otherwise, the installer will stop and prompt you to uninstall the Sun JRE before attempting your Cisco Unified MeetingPlace Web Conferencing install again.
If you do not have a release of Sun JRE installed, the installer loads it for you automatically. No additional steps are required.
Preinstallation Tasks: Cisco Unified MeetingPlace Web Conferencing Release 5.3
Before attempting to install Cisco Unified MeetingPlace Web Conferencing, read the Release Notes for Cisco Unified MeetingPlace Web Conferencing Release 5.3 for updated system requirements. When reviewing the system requirements, keep the following points in mind:
•If you are installing Cisco Unified MeetingPlace Web Conferencing in a segmented meeting access configuration, that is, allowing external access, also see "Installing Cisco Unified MeetingPlace Web Conferencing for a Segmented Meeting Access Configuration."
•If you are installing Cisco Unified MeetingPlace Web Conferencing in a load balancing configuration, also see Chapter 4, "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3 in a Load Balancing Configuration".
After reviewing the release notes, complete the following preinstallation tasks:
•Installing Cisco Unified MeetingPlace Audio Server Release 5.3
•(Optional) Installing SQL Server on a Remote Server
•Creating a Least Privileged SQL Account
•Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values
Installing Cisco Unified MeetingPlace Audio Server Release 5.3
You must install and configure the audio server software on a Cisco Unified MeetingPlace 8100 series server before you begin your Release 5.3 installation. For installation instructions, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server Release 5.3.
Installing SQL Server on a Remote Server
Cisco Unified MeetingPlace Web Conferencing requires SQL Server. You can choose to install SQL Server (or MSDE) on either the same machine as Cisco Unified MeetingPlace Web Conferencing or on a separate machine. If you choose to install SQL Server on a separate machine, install both SQL Server 2000 and the appropriate Service Pack on a separate Windows machine before installing Cisco Unified MeetingPlace Web Conferencing. This can be a Cisco MCS or legacy non-Cisco MCS.
Note While we support Microsoft SQL Server Database Engine (MSDE), we strongly recommend that all Cisco Unified MeetingPlace systems, particularly production systems, use a fully licensed SQL Server.
Creating a Least Privileged SQL Account
By default, Cisco Unified MeetingPlace Web Conferencing uses the SQL and MSDE built-in sa administrator account to connect to its database. Depending on your server hardware and the options that you choose during installation, Cisco Unified MeetingPlace Web Conferencing may install SQL or MSDE for you. For more information about SQL and MSDE installation, see the "About SQL Server Integration" section.
During the SQL or MSDE installation, you will be asked to set a password for the sa account. Be sure to set a strong password, without spaces. Often, a strong password is sufficiently secure to protect your system from unauthorized access. However, if you do not want to use a SQL account that has full administration rights, you can create a least-privileged SQL account for use by Cisco Unified MeetingPlace Web Conferencing.
Caution If you choose to create a SQL account that is dedicated to Cisco Unified MeetingPlace Web Conferencing use, ensure that it meets all the specified requirements in this procedure. Failure to do so can cause a database connection failure between Cisco Unified MeetingPlace Web Conferencing and the SQL Server and result in a total outage or broken features.
Note If Cisco TAC determines that your SQL account does not meet the requirements specified in this guide, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Conferencing database so that a new database can be created once the account problem is remedied.
The Cisco Unified MeetingPlace Web Conferencing installer does not verify the existence of the SQL account or the validity of its username-password combination. As such, you must verify that the SQL Server account that you plan to use exists and that it conforms to the required access rights before you install Cisco Unified MeetingPlace Web Conferencing. Therefore, to create a SQL account that you can use to access the Cisco Unified MeetingPlace database with authentication, complete the following procedures:
•Assigning Installation and Ongoing Rights
•Assigning Server and Database Roles
Assigning Installation and Ongoing Rights
During the installation of Cisco Unified MeetingPlace Web Conferencing, you are prompted to enter a SQL Server username and password. This SQL Server user must have the right to log in to the SQL Server instance that you specify during the installation. To assign and verify rights, complete the following procedure.
Procedure
Step 1 Assign the following additional rights to the SQL Server user:
•Create Database
•Create Table
•Create Default
Step 2 (Optional) After the installation is complete, remove the Create Database right from this SQL Server user.
Step 3 Verify that the SQL Server user has the following rights for all tables in the MPWEB database:
•Select
•Insert
•Update
•Delete
Note This user must be able to alter the MPWEB database.
Step 4 Proceed to "Assigning Server and Database Roles" section.
Assigning Server and Database Roles
SQL Server provides some built-in roles that simplify the process of granting and denying rights.
Restrictions
You cannot assign database roles until after the database is created. Therefore, wait until Cisco Unified MeetingPlace Web Conferencing completes installation before you assign roles.
Procedure
Step 1 To create a user with the proper rights for Cisco Unified MeetingPlace Web Conferencing, use the SQL Server Enterprise Manager to create a user and assign the following server role:
•dbcreator
Step 2 Assign the following database roles for the MPWEB database:
•public
•db_datareader
•db_datawriter
•db_ddladmin
•db_owner
Troubleshooting Tips
If you receive the following error, change the owner of the MPWEB database by entering the following command: exec sp_changedbowner 'sa'. This launches a procedure that is stored in the MPWEB database.
Error 21776: [SQL-DMO] The name 'dbo' was not found in the Users collection.
If the name is a qualified name, use [] to separate various parts of the name,
For more information about this error, see the Microsoft Knowledge Base Article 305711, BUG: DBO User Does Not Display in Enterprise Manager.
Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values
Gather and record the following information to prepare for your installation of Cisco Unified MeetingPlace Web Conferencing Release 5.3.
Table 2-2 Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values
Description
|
The MeetingPlace Server hostname.
This parameter refers to the Cisco Unified MeetingPlace Audio Server system hostname. If you are installing multiple web servers that share a database and point to the same Audio Server system, make sure that the audio server hostname on all of these web servers match.
Note If a connection exists between the web server and the Cisco Unified MeetingPlace Audio Server system—that is, if there is no firewall between them, port 5003 is not blocked, and the audio server system is up and running—then you can use an IP address instead of a hostname. However, using an IP address prevents you from taking advantage of the audio server system's reverse connection feature, which allows the audio server system to initiate a connection to the web server when port 5003 is blocked inbound.
|
Value
|
Hostname:
IP address:
|
Notes
|
|
Description
|
The location of the web server.
•Internal (Full Access)
Cisco Unified MeetingPlace Web Conferencing is installed with all features enabled and this server is placed inside your corporate network. In Segmented Meeting Access-2 Server (SMA-2S) deployments, this server functions as the internal web server.
•External (Limited Access)
Cisco Unified MeetingPlace Web Conferencing is installed with attend-only capability. In SMA-2S deployments, this server is placed outside your corporate firewall in an Internet-accessible network, such as a DMZ, and functions as the external web server.
•Both
Depending on your release of Cisco Unified MeetingPlace Web Conferencing, you may see this option referred to as Both (Full Access) or Both (SMA-1S).
Cisco Unified MeetingPlace Web Conferencing is installed on a single machine, but configured to host two websites. One website provides a full-access user interface to internal users while the second website provides attend-only access to Internet users. This server is placed in the DMZ and is the definition of a Segmented Meeting Access-1 Server (SMA-1S) deployment.
Note While the Both configuration has some security benefits, we strongly recommend the SMA-2S deployment for maximum security.
|
Value
|
Web server location:
|
Notes
|
|
Description
|
The web server hostname or static IP address.
Segmented meeting access (SMA) configurations require two hostnames or IP addresses: one for the internal web server or site and one for the external web server or site.
|
Value
|
Internal web server hostname:
Internal web server IP address:
|
Value
|
(Optional)
External web server hostname:
External web server IP address:
|
Notes
|
|
Description
|
The location of your SQL Server 2000 database.
•If you are installing SQL Server 2000 on this machine, enter Local Server.
•If you are pointing the web server to a version of SQL Server previously installed on a separate machine, enter Existing Remote Server.
If you are connecting to a remote SQL Server, also enter its hostname or IP address.
|
Value
|
SQL Server location
(Optional) Remote SQL Server hostname:
(Optional) Remote SQL Server IP address:
|
Notes
|
|
Description
|
Your SQL Server 2000 username and password.
If you are completing a new install of Cisco Unified MeetingPlace Web Conferencing with a local install of the SQL Server, use sa as your username.
Note You must enter a password. Cisco Unified MeetingPlace Web Conferencing does not support a blank password. The password you enter during this installation will override any blank or previously entered SQL Server password.
|
Value
|
Username:
Password:
|
Notes
|
|
Installation Tasks: Cisco Unified MeetingPlace Web Conferencing Release 5.3
The Cisco Unified MeetingPlace Web Conferencing installation is completed in two parts:
•Installing the Operating System on the Cisco MCS Server
•Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3
Installing the Operating System on the Cisco MCS Server
Procedure
Step 1 Dedicate a networked Cisco MCS on which to install Cisco Unified MeetingPlace Web Conferencing.
Step 2 (Optional) Verify that your system meets the installation requirements.
See the Release Notes for your Cisco Unified MeetingPlace Web Conferencing release to review the network and system requirements.
Step 3 Install the required Cisco MCS operating system on the Cisco MCS Unified CallManager Appliance.
•The operating system CD should have arrived with your Cisco Unified MeetingPlace application software. When the installer prompts you for the product key, enter BTOO VQES CCJU IEBI.
•For additional information about MCS OS installation, see the "About the Cisco MCS Unified CallManager Appliance" section in the Installation Planning Guide for Cisco Unified MeetingPlace Release 5.3.
Step 4 Make sure of the following:
•Microsoft IIS 5.0 is installed.
•IIS Administration Service and World Wide Web Publishing Service are running.
•A default website is configured in the IIS.
•You have Administrator privileges on the Cisco MCS.
Step 5 (Optional) If you have a release of Sun JRE installed, check that it is version 1.4.2_05. If it is not, uninstall Sun JRE.
•Cisco Unified MeetingPlace Web Conferencing installs the required release of Sun JRE for you during the Cisco Unified MeetingPlace Web Conferencing installation. For more information, see the "About the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation" section.
Step 6 Proceed to the "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3" section.
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3
The Cisco Unified MeetingPlace Web Conferencing executable takes approximately 35-45 minutes to install the following components:
•Cisco Unified MeetingPlace Gateway SIM
•Cisco Unified MeetingPlace Web Conferencing software
•The .NET framework
•(If the local server option is chosen) SQL Server 2000. This requires an automatic restart.
•(If the local server option is chosen) The appropriate release of the SQL Server 2000 Service Pack. This requires an automatic restart.
Note Check the Release Notes for your release of Cisco Unified MeetingPlace Web Conferencing for the SQL Server 2000 Service Pack required.
Before You Begin
•Make sure that your installation drive has sufficient disk space to allow for the storage of applications, attachments, recordings, and meeting and profile database information, which will grow over time. For more information, see the system requirements in the Release Notes for your Cisco Unified MeetingPlace Web Conferencing release.
•If you have any antivirus software running on a Cisco MCS, disable it before attempting your Cisco Unified MeetingPlace Web Conferencing installation.
•Make sure that your Cisco Unified MeetingPlace 8100 series server has Cisco Unified MeetingPlace Audio Server Release 5.3 or a later release installed.
•Complete the "Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values" section and have the values available.
•Complete the "Installing the Operating System on the Cisco MCS Server" section.
Restriction
We do not support installing or upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3 by using Terminal Services.
Procedure
Step 1 Close any open applications.
Step 2 Insert the Cisco Unified MeetingPlace Web Conferencing CD into your CD or DVD-ROM drive and double-click the .exe file to begin installation.
Note If you see a Missing Server Version error message, make sure that you have Cisco Unified MeetingPlace Audio Server Release 5.3 or a later release installed on your Cisco Unified MeetingPlace 8100 series server. If you do, proceed with the Cisco Unified MeetingPlace Web Conferencing installation. If you do not, upgrade your audio server software to Audio Server Release 5.3 before proceeding with this installation.
Step 3 After the install files are extracted, click Next and follow the instructions in the installer windows using information from the "Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values" section.
•If you enter an IP address instead of a hostname for the Cisco Unified MeetingPlace Audio Server system, a warning message appears regarding reverse connection.
•If this machine is in a network segment, such as a DMZ, and you are interested in reverse connection, enter a hostname instead of an IP address; then, proceed with your installation.
•If this machine has a connection to the Audio Server system—that is, if they are in the same network segment, port 5003 is open, and the Audio Server system is running—and you are not interested in reverse connection, then use the IP address and proceed with the installation.
Step 4 The installer installs the Gateway SIM first. When the InstallShield Wizard Complete window appears, click Finish. Your Gateway SIM is now installed.
Step 5 When the installer prompts you for your Installation Key, keep the following points in mind:
•If you are installing Cisco Unified MeetingPlace Web Conferencing on a machine that is already configured on the Audio Server system, enter this machine's ethernet address in the Installation Key Entry window; then, click Next.
•If this is a new installation of Cisco Unified MeetingPlace Web Conferencing, this machine is probably not configured on the Audio Server system. In this instance, leave this field blank and click Next.
Step 6 Continue following the instructions in the installer windows using information from the "Gathering Cisco Unified MeetingPlace Web Conferencing Installation Values" section.
Step 7 When you reach the final installer window, choose to restart your computer now; then, click Finish. You must restart your machine for changes to take effect. During installation, remember the following information:
Caution Do not interrupt the server during program installation or during automatic system shutdown or restart.
•If you chose Local Server as your SQL Server location, after the first reboot, the installer begins installing SQL Server. Status updates appear from the Cisco Unified MeetingPlace icon in your system tray, and when SQL Server installation completes, the server reboots automatically.
•If the installer detects a local SQL Server installation, after the second reboot, the installer begins installing the SQL Server Service Pack. Status updates appear from the Cisco Unified MeetingPlace icon in your system tray. When the Service Pack installation completes, the server reboots automatically.
•Installations of the SQL Server and the SQL Server Service Pack are slow, and depending on your server hardware, installations may take as long as 40 minutes or more to complete.
•The Cisco Unified MeetingPlace icon appears as an orange door 
.
•If the SQL Server installation appears to be taking too long (over 35 minutes), check your Task Manager to confirm that SQLInstall.exe is running.
•After the server reboots, the installer invokes SQLInstall.exe to create the MPWEB SQL database. This process may take 5-to-10 minutes.
Step 8 Open the Gateway SIM eventlog to monitor Cisco Unified MeetingPlace Web Conferencing application activities.
Step 9 Proceed to the "How to Test the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation" section.
How to Test the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation
After you install Cisco Unified MeetingPlace Web Conferencing, test the web server by completing the following procedures:
•Defining the Cisco Unified MeetingPlace Web Conferencing Server
•Testing the Web Server Over an HTTP Connection
•Testing the Web Server Over an HTTPS Connection
•Testing the Meeting Console Connection
Defining the Cisco Unified MeetingPlace Web Conferencing Server
Procedure
Step 1 Open your web browser and enter the URL of your web server.
•For internal web servers, the default URL structure is http://server where server is the name of your internal web server.
•For external web servers, the default URL structure is http://server/mpweb/admin/ where server is the name of your external web server.
Step 2 When the Cisco Unified MeetingPlace Web Conferencing home page appears, sign in by using your System Manager-level user ID and password; then, click Sign In Now.
•If you are on an internal web server, the Welcome page appears with your name displayed at the top. To access the administrative page, click Admin.
•If you are on an external web server, the administrative page appears.
Step 3 From the Admin page, click Web Server.
Step 4 From the "View" section of the page, click the name of the web server that you want to configure.
Information about this web server populates the "Edit" section of the page.
Step 5 For Hostname, enter the fully qualified domain name (FQDN) of your web server. If this field contains just the hostname of your web server, change it to the FQDN, that is, hostname.domain.com.
•If your web server is not in a Domain Name Server (DNS), insert the IP address instead.
•This hostname or IP address must be resolvable by its intended users. For details, see the "Testing the Web Server Over an HTTP Connection" section.
Step 6 For Web Conference Active, choose Yes or No.
•The default is Yes.
•Choosing No means that this web server will not host meetings.
Step 7 Click Submit.
Testing the Web Server Over an HTTP Connection
Make sure that the web server can resolve itself using the hostname configured on the Web Server administrative page. This is the hostname that you configured in Step 5 of the "Defining the Cisco Unified MeetingPlace Web Conferencing Server" section and is also the hostname end-users use to connect to this web server.
Before You Begin
Define the web server. For instructions, see the "Defining the Cisco Unified MeetingPlace Web Conferencing Server" section.
Procedure
Step 1 From the web server, use a web browser to connect to http://hostname.domain.com, where http://hostname.domain.com is the Fully Qualified Domain Name (FQDN) of your web server.
or
If your web server is not in a Domain Name Server (DNS), use a web browser to connect to an IP address from the web server.
•If the Cisco Unified MeetingPlace Web Conferencing home page appears, your connection is successful.
•If you receive an error message, see the "Problems with Cisco Unified MeetingPlace Web Conferencing Server Connections" section on page 6-3
Testing the Web Server Over an HTTPS Connection
Before You Begin
Your web server only allows HTTPS traffic.
Procedure
Step 1 From the web server, use a web browser to connect to https://hostname.domain.com, where http://hostname.domain.com is the Fully Qualified Domain Name (FQDN) of your web server.
or
If your web server is not in a Domain Name Server (DNS), use a web browser to connect to IP address from the web server.
•If the Cisco Unified MeetingPlace Web Conferencing home page appears, your connection is successful.
•If any security warning dialog boxes appear, see the "Problems with Cisco Unified MeetingPlace Web Conferencing Server Connections" section on page 6-3
Testing the Meeting Console Connection
Procedure
Step 1 From an end-user system, open a web browser and enter the Cisco Unified MeetingPlace Web Conferencing URL in the address field. Click Enter.
Step 2 Sign in by using your System Manager-level user ID and password.
Step 3 From the Welcome page, click Schedule Meeting.
Step 4 From the New Meeting scheduling page, fill in your meeting details; then, click Schedule.
Step 5 Return to the Welcome page and enter the meeting ID of the meeting you just scheduled; then, click Attend Meeting.
Step 6 Confirm that the meeting console loads properly.
Related Topics
For information about meeting console connection speeds and status, see the User Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.
Feedback
