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 tradema
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Macromedia Breeze Edge Server For a successful installation and configuration of Macromedia Breeze Edge Server, read the information provided in this document.
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.
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.
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.
Installing Breeze Edge Server Use the procedures described in this section to install the Breeze Edge Server. Macromedia recommends that you close all other applications before starting to install. To install and configure Breeze Edge Server: 1. Insert the installation CD into the CD-ROM drive. If the Macromedia Breeze Edge Server Setup wizard does not start automatically, double-click the setup.exe file in the installation CD’s root folder.
2. Click Next to continue. The License Agreement window appears. 3. Read the agreement, select I Accept the Agreement, and click Next to continue. The Select Destination Location window appears.
4. Click Next to accept the default installation location, or click Browse to select a different location, and then click Next. If the wizard detects a previous installation of a Breeze Edge Server, you will see the following screen. 5. Click Next to continue. The Select Start Menu Folder window appears.
6. Accept the default shortcut, or click Browse to select a different location, and then click Next. The Ready to Install window alerts you that the Breeze installation is about to begin. 7. 12 Review the choices for the destination folder where Breeze will be installed and for adding Macromedia Breeze Edge Server to the Start Menu folder.
8. Click Back if you want to review or change these settings, or click Install to continue. The Installing Breeze window appears. The wizard is beginning to extract the Breeze Edge Server files on the installation CD and install them. This process takes less than two minutes. 9. Click Cancel at any time if you want to abort or cancel the installation. When the installation is complete, the Completing the Macromedia Breeze Edge Server Setup Wizard window appears. 10.
The Breeze Edge Server license file When your order for Breeze Edge Server is processed, Macromedia Order Services dispatches an e-mail with the Breeze Edge Server license file (license.lic) attached. To install the Breeze Edge Server license file, do the following: 1. Go to c:\{install_path}\edgeserver\conf\win32\. 2. Create a folder named licenses, if it does not already exist. 3. Open the e-mail from Macromedia. 4. Save the license.lic file in the licenses folder.
Mapping the DNS entry for Breeze Edge Server Mapping the DNS entry for an edge server is comparable to mapping the BREEZE_HOST variable for Breeze Server on the Breeze Application Management Console. For example, if the value for BREEZE_HOST (the host name to use in a URL for accessing the Breeze origin server) is breeze.mycompany.com, the DNS entry for an edge server maps breeze.mycompany.com to the IP address of the nearest edge server. NO T E The values in the custom.
This tag now specifies that edge servers listen on ports 1935, 80, and 443. A port is defined as a secure port by placing a minus sign in front of the port number in a configuration variable or file. For example, you can configure a secure port by editing the HostPort tag of the Adaptor.xml file. :1935,80,-443 Port 443 is designated as a secure port that receives only RTMPS connections. Attempting an RTMPS connection request to ports 1935 or 80 results in a failure to connect.
HTTP tunneling For SSL to work properly, HTTP tunneling must be enabled. Clients use HTTP tunneling to connect to the server via SSL. NO T E HTTP tunneling is enabled by default. No user action is required. Adding the required SSL tags in the Adaptor.xml file All SSL tags in the Server.xml file are included by default. Not all of the required SSL tags in Adaptor.xml are present by default, however. You need to insert the following SSL-specific tags in the Adaptor.xml file.
Defining the SSL tags in FCS The following table lists alphabetically all the SSL-specific tags in both the Adaptor.xml and Server.xml files. You must configure these tags to enable SSL in FCS. FCS File XML Tag Default Description Adaptor.xml Redirect [none] Specifies whether unknown requests are redirected to an external server such as Breeze. When FCS receives an unknown request, the request is redirected to the specified redirect host. For redirection to work, HTTP tunneling must be enabled.
FCS File XML Tag Adaptor.xml SSLCipherSuite Default Description Specifies the ciphers to use. This is a list of colon-delimited components. A component can be a key exchange algorithm, authentication method, encryption method, digest type, or one of a selected number of aliases for common groupings. For a list of components, see the FCS documentation. The default setting for this tag is: ALL:!ADH:!LOW:!EXP:!MD5:@STRE NGTH Contact Breeze Technical Support before changing the default settings. Adaptor.
FCS File XML Tag Server.xml SSLCACertificateFile 20 Macromedia Breeze Edge Server Default Description This tag configures the server to act as an SSL client (out-going SSL connections), and is used only when making outgoing SSL connections. This tag specifies the name of a file that contains one or more certificates issued by a valid Certificate Authority (CA) in the Privacy Enhanced Mail (PEM) encryption format. A CA is an organization such as Verisign that issues certificates to people.
FCS File XML Tag Server.xml SSLCACertificatePath Default Description This tag specifies the name of a directory containing one or more (CA) certificates. Windows only: Because MS Windows installs certificates in the registry, there is no file system directory that contains all the certificates of trusted root certificates. You must import the certificates installed in the Windows certificate store into individual certificates and placed in a directory accessible by OpenSSL.
FCS File XML Tag Server.xml SSLCipherSuite Default Description Specifies the ciphers to use. This is a list of colon-delimited components. A component can be a key exchange algorithm, authentication method, encryption method, digest type, or one of a selected number of aliases for common groupings. For a list of components, see the FCS documentation. The default setting for this tag is: ALL:!ADH:!LOW:!EXP:!MD5: @STRENGTH Contact Breeze Technical Support before changing the default settings. Server.
FCS File XML Tag Default Description Server.xml SSLCACertificatePath [none] Specifies the name of a directory containing CA certificates. Each file in the directory must contain only a single CA certificate, and the files must be named by the subject name's hash and an extension of ".0". Win32 Only: If this tag is empty, FCS attempts to find CA certificates in the certs directory located at the same level as the conf directory.
FCS File XML Tag Default Description Server.xml SSLVerifyCertificate true Configures the server to act as an SSL client (out-going SSL connections). The tag specifies whether or not to verify the certificate that is returned by the server being connected to. Certificate verification is enabled by default. To disable certificate verification, specify false. Warning: Disabling the certificate verification can result in a security risk. Server.
To stop Breeze Edge Server: ■ Select Start > Programs > Macromedia > Macromedia Breeze 5 > Stop Breeze Server. To verify that Edge Server is not operating: ■ Go to the Control Panel. ■ Select the Services Panel. ■ Locate the following services: Flash Communication Administration Server and Flash Communication Server. Their status should read “stopped.” Deploying an edge server cluster Macromedia Breeze provides support for clustering edge servers.
Here are the basic steps in installing and configuring a cluster of edge servers. 1. Make sure each computer in the cluster meets the hardware, software, and network requirements, as described in “System requirements” on page 8. 2. Install the Breeze Edge Server license file on each edge server as described in “The Breeze Edge Server license file” on page 14. 3. Configure FCS for each edge server in the cluster, as described in “Configuring FCS for Breeze Edge Server” on page 14. 4.
