Cisco Cisco Unified MeetingPlace Web Conferencing Manuale Di Manutenzione

Pagina di 335
Chapter 5  Installing MeetingPlace Web 77
Load Balancing Behaviors and Limitations
All users log in to the MeetingPlace Web home page through the 
Primary MeetingPlace Web server. When they click the “Join 
Web Conference” button, a new window opens and the web 
conferencing session is directed to one of the secondary 
MeetingPlace Web servers.
If their meeting is held on MeetingPlace CS 1, then the web 
conferencing session will begin on the Primary MeetingPlace 
Web server. If their meeting is scheduled on MeetingPlace CS 5, 
then their web conferencing session will begin on the Secondary 
MeetingPlace Web server #4.
If the Secondary MeetingPlace Web server #1 fails, then only 
meetings scheduled on CS 2 and CS 8 will be unable to conduct 
web conferencing sessions. The remaining meetings on other CSs 
will still be able to conduct web conferencing sessions.
Primary MeetingPlace Web server: Handles all meetings on 
the specific MeetingPlace CS(s) that are assigned to it, as well as 
routing web conferencing sessions for meetings on other 
MeetingPlace CS(s) to the appropriate secondary web 
conferencing servers, using the mapping pattern shown in Figure 5-3.
Note: Each of the Secondary MeetingPlace Web servers will 
register itself into the MeetingPlace network servers’ database 
and be assigned a unit between 10 and 15. Please note that each 
MeetingPlace networked system can only support a maximum of 
six Windows servers running Latitude gateways.
Note: MeetingPlace Load Balancing is not supported in Internal/
External DMZ configurations. 
OL-6033-01                           Cisco MeetingPlace Web 3.0 System Manager's Guide