Trademarks. Third-Party Information. Jabber is a registered trademark of the Jabber Software Foundation. Acknowledgments, страница 9

Linux uses case-sensitive filenames; filenames on Windows are case-insensitive.

■ Install Flash Media Server on the first server.

■ Configure this instance of Flash Media Server as an origin server.

■ Install and configure Flash Media Server on all of the edge or proxy servers that your license permits.

■ Make sure the fms.ini file is customized on each origin and proxy.

The fms.ini file is machine-specific.

■ Configure the origin server to listen on one port; you can configure proxies to listen on one or multiple ports.

■ Verify that all proxies can access the origin server.

■ Locate the origin server and those edge servers nearest to it on the same subnet.

■ If you are licensed to deploy a cluster, make sure all proxies in the cluster are configured identically.

■ Configure the conf directory on one proxy.

■ Place a copy of this conf directory in the same location on the other proxies.

■ Use a load balancer when you deploy more than one proxy.

■ Place the load balancer between the clients and the proxies.

■ Configure the balancer to access the proxies in round-robin mode.

■ Do not place the load balancer immediately before the origin server.

To set up a cluster of edge servers:

1.  Install and configure the first Flash Media Server.

Use the same serial number and license file each time you install Flash Media Server.

A special cluster license file is required. For more information, contact your Macromedia representative.

2.  Confirm that this Flash Media Server instance is working correctly.

3.  Configure the Flash Media Server instance as an origin server.

4.  Install and configure the next Flash Media Server in the cluster.

5.  Configure this Flash Media Server instance as an edge server.

6.  Make sure this edge server points to the origin server.

7.  Repeat steps 5 through 7 for each edge server that your license file allows.

Your Flash Media Servers are now clustered. To expand the cluster’s capacity, you may add new edge servers, if your license permits, to the cluster and configure them by following these instructions.

Maintaining edge server clusters

When an edge starts up, it broadcasts its presence to all other edges in the cluster. When an edge shuts down, it broadcasts that it is leaving the cluster. If an edge shuts down, all other edges in the cluster detect the change in state because the edges no longer receive the keepalive messages from that edge. The remaining edges automatically update their views of the cluster and remove the shut-down edge from their views. You only have to start and stop edges, and they automatically determine which edges are currently enrolled in the cluster.

Clearing the edge server cache

Macromedia recommends that you create a weekly scheduled task to clear the edge server cache.

To create a scheduled cache clearance:

1.  Create a cache.bat file to empty the cache directory.

The entry in the cache.bat file has the following syntax:

del /Q /S <cache_directory>\*.*

2.  Run the cache.bat file and verify that it deletes files in the cache directory.

■ Note that the directory structure remains; this is an expected behavior.

■ Any files currently locked by the edge server are not deleted; this is also an expected behavior.

3.  Select Control Panel > Scheduled Tasks > Add Scheduled Task.

4.  Select cache.bat as the new file to run.

Macromedia recommends that you schedule the task to run weekly during off hours, such as early Sunday morning.

Replicate this procedure on each edge server.