Macromedia BREEZE 5 User Manual

Installing and Configuring Breeze Edge Server

Trademarks

1 Step RoboPDF, ActiveEdit, ActiveTest, Authorware, Blue Sky Software, Blue Sky, Breeze, Breezo, Captivate, Central,
ColdFusion, Contribute, Database Explorer, Director, Dreamweaver, Fireworks, Flash, FlashCast, FlashHelp, Flash Lite,
FlashPaper, Flex, Flex Builder, Fontographer, FreeHand, Generator, HomeSite, JRun, MacRecorder, Macromedia, MXML,
RoboEngine, RoboHelp, RoboInfo, RoboPDF, Roundtrip, Roundtrip HTML, Shockwave, SoundEdit, Studio MX, UltraDev,
and WebHelp are either registered trademarks or trademarks of Macromedia, Inc. and may be registered in the United States or
in other jurisdictions including internationally. Other product names, logos, designs, titles, words, or phrases mentioned within
this publication may be trademarks, service marks, or trade names of Macromedia, Inc. or other entities and may be registered in
certain jurisdictions including internationally.

Third-Party Information

This guide contains links to third-party websites that are not under the control of Macromedia, and Macromedia is not
responsible for the content on any linked site. If you access a third-party website mentioned in this guide, then you do so at your
own risk. Macromedia provides these links only as a convenience, and the inclusion of the link does not imply that Macromedia
endorses or accepts any responsibility for the content on those third-party sites.

Copyright © 2005 Macromedia, Inc. All rights reserved. This manual may not be copied, photocopied, reproduced,
translated, or converted to any electronic or machine-readable form in whole or in part without written approval from
Macromedia, Inc. Notwithstanding the foregoing, the owner or authorized user of a valid copy of the software with which
this manual was provided may print out one copy of this manual from an electronic version of this manual for the sole
purpose of such owner or authorized user learning to use such software, provided that no part of this manual may be
printed out, reproduced, distributed, resold, or transmitted for any other purposes, including, without limitation,
commercial purposes, such as selling copies of this documentation or providing paid-for support services.

Acknowledgments

Project Management: Stephanie Gowin

Writing: John Norton

Editing: John Hammett

Production Management: Patrice O’Neill

Media Design and Production: Adam Barnett, Paul Benkman, John Francis, Mario Reynoso

Second Edition: October 2005

Macromedia, Inc.
601 Townsend St.
San Francisco, CA 94103

Contents

Introduction to edge servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Connecting to Breeze through edge servers . . . . . . . . . . . . . . . . . . . . . . .8

System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing Breeze Edge Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

The Breeze Edge Server license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring FCS for Breeze Edge Server . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring FCS for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Stopping and starting Breeze Edge Server . . . . . . . . . . . . . . . . . . . . . . 24

Deploying an edge server cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Scheduling maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3

4Contents

Macromedia Breeze Edge Server

For a successful installation and configuration of Macromedia Breeze Edge Server, read the
information provided in this document. It contains the following sections:

■ “Introduction to edge servers” on page 6

■ “Connecting to Breeze through edge servers” on page 8

■ “System requirements” on page 8

■ “Installing Breeze Edge Server” on page 9

■ “The Breeze Edge Server license file” on page 14

■ “Configuring FCS for Breeze Edge Server” on page 14

■ “Mapping the DNS entry for Breeze Edge Server” on page 15

■ “Configuring FCS for SSL” on page 16

■ “Alternative SSL implementations” on page 16

■ “HTTP tunneling” on page 17

■ “Adding the required SSL tags in the Adaptor.xml file” on page 17

■ “Locating the required SSL tags in the Server.xml file” on page 17

■ “Stopping and starting Breeze Edge Server” on page 24

■ “Deploying an edge server cluster” on page 25

■ “Scheduling maintenance” on page 26

5

Introduction to edge servers

Edge servers are configured to allocate and balance access to a Breeze server by using the
existing bandwidth resources more efficiently. Once the edge servers are deployed, users access
Breeze through their edge server. Edge servers authenticate these users and authorize their
requests for web services such as Macromedia Breeze Meeting rather than forwarding every
request to the Breeze server and consuming its resources for these tasks. If the data requested is
found in the edge server’s cache, it returns the Breeze Meeting data to the requesting client
(the user’s computer) without calling upon the Breeze server. This detour to the Breeze server
is transparent to users. In this scenario, no demands are placed on the origin Breeze server.

If the data requested is not found in the edge server’s cache, it forwards the client’s request to
the Breeze server, where the user is authenticated and the request for services authorized. The
Breeze server returns the results to the requesting edge server, which in turn delivers the results
to the requesting client. The edge server also stores this information in its cache, where other
authenticated users can access it. In this scenario, fewer requests for services are forwarded to
the origin Breeze server.

6 Macromedia Breeze Edge Server

An edge server is configured to intercept the requests for Breeze services from a particular
zone, to collect or aggregate these requests, and transmit them to the origin Breeze server. The
Breeze server returns the results to the edge server, which forwards the data to the user’s client
computer. A networked Breeze deployment might have multiple edge servers installed. For
example, one edge server might aggregate and forward requests from San Francisco and
another might aggregate and forward requests from Boston. Each edge server gathers the
requests from its clients and forwards them to the origin Breeze server located in a data center
in Chicago, receives the responses from the origin Breeze server, then transmits and distributes
them to the clients in its zone.

Meeting X

Meeting X

San Francisco

Breeze Edge

Boston

Breeze

Chicago

Breeze Edge

Company A

Introduction to edge servers 7

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 Requirement

Operating System Windows Server 2000

Windows Server 2003

Server Processor Pentium IV 3.6 GHz

Cache Processor 2 MB cache processor

Memory 4 GB RAM recommended

2 GB RAM minimum

Hard Drive 80 GB 10K RPM recommended

40 GB 7200 RPM minimum

Network Adaptor TCP/IP Adaptor supporting 1 GB over CAT5 Ethernet

Display SGVA supporting 800x600 or higher resolution

Drive CD-ROM or DVD-ROM

8 Macromedia Breeze Edge Server