Connecting to Breeze through edge
servers
When edge servers are present on an organization's network, Breeze users connect to Breeze
Meeting indirectly through the edge (or proxy) server. This connection occurs transparently.
To Breeze users, it appears that they are connected directly to the Breeze server hosting Breeze
Meeting, but they are most likely connected through the proxy or edge server servicing their
local network. Edge servers offload traffic to the origin Breeze server caching static content
like recorded Breeze meetings and presentations.
These take place behind the network connection to the Breeze server. The client (the user's
computer) connects to the edge (proxy) server instead of making a direct connection to Flash
Communication Server (FCS) (Breeze Meeting) directly. The edge server in turn connects to
the origin Breeze server. Many additional steps, such as user authentication and permissions
authorization, are hidden from the Breeze user.
Edge servers provide an additional layer of defense between the user's Internet connection and
the Breeze server. All traffic coming from the Internet and with Breeze as its destination goes
through the edge server.
System requirements
This release of Edge Server is certified to support up to 500 users or 50 meeting rooms. The
following table lists the hardware requirements for edge servers.
Component
Operating System
Server Processor
Cache Processor
Memory
Hard Drive
Network Adaptor
Display
Drive
8
Macromedia Breeze Edge Server
Requirement
Windows Server 2000
Windows Server 2003
Pentium IV 3.6 GHz
2 MB cache processor
4 GB RAM recommended
2 GB RAM minimum
80 GB 10K RPM recommended
40 GB 7200 RPM minimum
TCP/IP Adaptor supporting 1 GB over CAT5 Ethernet
SGVA supporting 800x600 or higher resolution
CD-ROM or DVD-ROM
Need help?
Do you have a question about the BREEZE 5 - INSTALLING AND CONFIGURING EDGE SERVER and is the answer not in the manual?