The Client has a dedicated flashcom server running on port 80 (IIS or Apache is NOT installed as those applications will conflict on port 80 [http]).
The Flashcom server requires a small set of files that are copied into a specific Macromedia/Flash Communications Server folder on the flashcom server.
Client also requires a web server and/or already existing website that has JSP support configured and running where the website part of the code will reside.
The USER accesses the resource by opening a browser and going to their URL, as in the following example:
http://www.companydomainname.com/meeting OR http://meeting.companydomainname.com
[NOTE: Italicized words are variables and can be replaced with the actual domain name and/or virtual web directory name]
User enters URL accessing the "index.jsp" resource, which in turn launches the MegaMeeting code and presents the user with a GUEST/HOST Login Screen. For authentication purposes, the URL must have a corresponding entry in the "home system" database file located on the MegaMeeting.com servers. [Example - If a client accesses the system by going to http://meeting.domainname.com, then the "home-system" database file must have a "wildcard" entry for *.domainname.com].
When the user clicks the HOST button, the system requests a USERNAME and PASSWORD. Utilizing the "flash remoting" features of the MegaMeeting.com Macromedia Cold Fusion servers, these credentials are passed to and stored on the MegaMeeting.com SQL servers. Upon authentication, the user is presented with the HOST OPTIONS screen. The user can choose to accept the randomly generated meeting name or create a meeting name of their own and then click either the "Create & Join" button or the "Create Only" button. In each case, the meeting name is stored on the MegaMeeting.com SQL servers and once joined, the meeting actually "moves" to the Flashcom server where the meeting elements (objects) are managed and distributed to the meeting participants.
In addition to the aforementioned server products, in an "Island" configuration, the client is also required to have their own Macromedia Cold Fusion Enterprise Server
and Microsoft SQL Server. All usernames and passwords are stored on the client's SQL server and any/all data remoting to the SQL server is handled by the client's Cold
Fusion server. This configuration does not require authentication with the "home system" database file located on the MegaMeeting.com servers.
HARDWARE, SOFTWARE AND OPERATING SYSTEM PRE-REQUISITES:
For Both the "Non-Island" and "Island" configurations, a Dedicated Flashcom Server is required with the following:
Dual Intel Xeon Processors (min. of 2.8 GHz each)
2 x 40GB SATA Drives
Windows 2000 Server or Windows 2003 Server
Note: MegaMeeting.com recommends the use of Microsoft Windows 2000 Server or Microsoft Windows 2003 Server. Although the Macromedia Flashcom Server can be installed on a Linux system, only the SUSE version of Linux has passed our tests.
Additional "Non-Island" requirements:
Web Server or Existing Web Site w/JSP Support
Enough Bandwidth from an Internal or External Data Center to SupportVideo/Web Conferencing Needs (see Explanation of Bandwidth Requirements, below)
Additional "Island" requirements:
Web Server or Existing Web Site w/ Macromedia Cold Fusion
Microsoft SQL Server 2000 or Microsoft SQL Server 2005
Enough Bandwidth from an Internal or External Data Center to Support Video/Web Conferencing Needs (see Explanation of Bandwidth Requirements, below)
1. Each person that displays video in a conference transmits 70,000 bps of information. This is based on 160x120 resolution at 10fps.
a. If x people are in a conference, with ALL x displaying video, the amount of bandwidth required = x squared times 70,000 bps
i. As an example, if two people are in a conference, and BOTH are displaying video, the amount of bandwidth required = 2 squared times 70,000 = 4 times 70,000 = 280,000 bps
ii. If 10 people are in a conference, and ALL 10 are displaying video, the amount of bandwidth required = 10 squared times 70,000 = 100 times 70,000 = 7,000,000 bps
2. A good rule of thumb for presentations is to allow (conservatively) 250,000 bps for each host and guest that are in the meeting room (320,000 bps if the host is also presenting video, i.e. you need to add in the 70,000 bps for the hostís video). This number may be quite a bit lower if the images are not changing very often (it can be as low as 135,000 bps if spreadsheets, word documents, etc. are being displayed).
a. As an example, if a host is presenting to 2 guests, a conservative estimate regarding the amount of bandwidth required is 3 times 250,000 = 750,000 bps.
b. If a host is presenting to 49 guests, a conservative estimate regarding the amount of bandwidth required is 50 times 250,000 = 12,500,000 bps.