Cisco Systems Conference Phone Testing the Web Server Over an Http Connection, Before You Begin

Page 31

Chapter 2 Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3

How to Test the Cisco Unified MeetingPlace Web Conferencing Release 5.3 Installation

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 on page 2-13.

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 on page 2-12and 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 on page 2-12.

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

 

 

Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3

 

 

 

 

 

 

OL-10029-01

 

 

2-13

 

 

 

 

 

Image 31
Contents Corporate Headquarters Copyright 2004-2006 Cisco Systems, Inc. All rights reserved N T E N T S About the SMA-2S Configuration with SSL and Segmented DNS Releases What to Do First Preface Term Definition Naming ConventionsAdditional References Preface Additional References About Cisco Unified MeetingPlace Terms for Single Sign On Software Integration Configuration RestrictionsTerms of Support for Single Sign On Software Integration Feature Description New Features and Enhancements in ReleaseFeature Description New Features and Enhancements in Release New Features and Enhancements in Release Feature Description About SQL Server Integration Related Topics Msde Database SizeIf the following conditions are met About SQL Server Installation OptionsAbout Sun Java Runtime Environment Installing SQL Server on a Remote Server Installing Cisco Unified MeetingPlace Audio Server ReleaseCreating a Least Privileged SQL Account Procedure Assigning Installation and Ongoing RightsRestrictions Troubleshooting TipsInternal Full Access Installing the Operating System on the Cisco MCS Server Before You Begin Restriction Procedure Testing the Web Server Over an Http Connection Testing the Meeting Console Connection Testing the Web Server Over an Https ConnectionAbout Segmented Meeting Access LAN/WAN DMZ About the SMA-1S ConfigurationAbout the SMA-2S Configuration Example About the SMA-2S Configuration with SSL and Segmented DNSGathering Basic Information About Your Web Server What to Do Next Information, see the About SQL Server Integration section on Restrictions Before You Begin OL-10029-01 A P T E R Cisco Unified MeetingPlace Web Conferencing Clusters One Cluster Configuration 121506 Internal ThenSuggestions for a Robust Cisco Unified MeetingPlace System Default Behavior of Load Balancing in Video-Enabled SystemsSQL Server Considerations Video Meetings in Segmented Meeting Access DeploymentsEnd-User Considerations Install the first internal web serverPreparing the Internal Cluster Preparing the External Cluster Creating a Common Storage Location Configuring Services for the First Internal Web Server Installing the First Internal Web ServerProcedure Registry Key Action Installing Additional Internal Web ServersCopying Guids From the Internal to the External Web Server Installing the First External Web ServerConfiguring Services for the First External Web Server Procedure Installing Additional External Web Servers Configuring Redirection of External Meetings Configuring Ad-Hoc Video Meetings Disabling Load Balancing Viewing the Amount of Web-Conferencing Load on a ServerOL-10029-01 A P T E R Load Balancing in Release 5.3333 and Later User Authentication Methods in Release 5.3235 and LaterBacking Up the Mpweb Database and MPWEB-Slave Database Right-clickMPWEB and choose All Tasks Backup DatabaseOpen Explorer Backing Up Cisco Unified MeetingPlace Registry InformationThis section contains the following procedures Upgrading a Standalone Web Server Restrictions Upgrading Web Servers Sharing the Same Database Click Change/Remove Uninstalling Cisco Unified MeetingPlace Web ConferencingRemoving SQL Server or Msde Reboot your serverWhat to Do First Locating the Software Download Page on Cisco.com Checking the Cisco MCS Operating System ReleaseObtaining Additional Assistance Resolving Https Connection Problems Resolving Http Connection ProblemsOL-10029-01 D E IN-2 IN-3 IN-4