MACROMEDIA FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS Use Manual
  1. Manuals
  2. Brands
  3. MACROMEDIA Manuals
  4. Software
  5. FIREWORKS 2-USING FIREWORKS
  6. Use manual
MACROMEDIA FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS Use Manual

MACROMEDIA FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS Use Manual

Using flash media server edge servers
Hide thumbs Also See for FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS:
Table of Contents

Advertisement

Quick Links

Download this manual
Using Flash Media Server
Edge Servers

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS and is the answer not in the manual?

Questions and answers

Related Manuals for MACROMEDIA FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS

Summary of Contents for MACROMEDIA FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS

  • Page 1 Using Flash Media Server Edge Servers...
  • Page 2 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.

  • Page 3: Table Of Contents

    Contents Using Edge and Origin Servers ......5 Introducing edge servers ........5 How edge servers work .
  • Page 4 Contents...

  • Page 5: Using Edge And Origin Servers

    Using Edge and Origin Servers This chapter describes the various strategies for deploying Flash Media Server with edge and origin servers. Introducing edge servers Until this release of Flash Media Server, clients always connected directly to the computer where the application was running. These applications were running locally, since their execution occurred on the same computer that the clients were connected to.

  • Page 6: How Edge Servers Work

    Deploying edge servers lets administrators distribute the incoming connection requests for Flash Media Server services. Traffic between clients and the origin server uses the existing bandwidth and system resources more efficiently. More traffic occurs locally between the clients’ computers and the edge server. Without edge servers, all clients have to connect to a Flash Media Server origin server, no matter where that server is located.
  • Page 7 Such constraints may prompt the Flash Media Server and network administrators to consider a different deployment strategy. The strategy involves configuring Flash Media Server to redistribute the load on system and bandwidth resources by running some virtual hosts as edge servers and other virtual hosts as origin servers. Rather than forwarding every request to the origin server and consuming resources for such repetitive tasks, the edge server collects the requests from a large number of clients and aggregates them into one connection to the origin server.
  • Page 8 Users in these zones always access the origin server through their assigned edge servers. These edge servers receive the responses from the origin server, then distribute them back to the clients (the users’ computers) in their respective zones: Paris or Tokyo. The edge also stores the data received from the origin server in a cache, and makes it available to other clients that connect to this edge server.

  • Page 9: Caching Data In Edge Servers

    Caching data in edge servers An edge server is designed to intercept the requests for Flash Media Server services from users in a particular zone, collect or aggregate these requests, and transmit them to the origin server. The origin server returns the results to the edge server, which in turn sends the data back to the user’s client computer.

  • Page 10: Explicit And Implicit Proxies

    With the edge servers sitting in the DMZ, the network operators can open access to port 1936, avoiding the system overhead and risk of HTTP tunneling. Because the edge server performs stream splitting and stream caching, it uses the connection to the origin server efficiently, reducing the Internet bandwidth cost.

  • Page 11: Reverse Proxies

    Administrators can explicitly specify that any connection request to an origin server be automatically routed through an edge or proxy server. For example, if your applications are running on fms.foo.com, you can redirect the connection request from the users’ computers to another server (or virtual host) called fmsproxy.foo.com which is configured to run in remote mode...

  • Page 12: Routing Information

    For example, if your applications are running on fms-secure.foo.com, you can direct the connection requests from clients’ devices or computers to the proxy server (or virtual host) called fms.foo.com which makes the connection to fms-secure.foo.com where your applications are running. The client is not aware that its request is being sent to another server.

  • Page 13: Detecting The Presence Of Proxy Servers

    Detecting the presence of proxy servers Flash Player 8 automatically detects any edge servers in its proximity. When an edge server is available, Flash Player automatically routes the connection from the client to the origin server through the proxy server. These edge servers are defined as implicit proxies since the client is generally unaware that its communication with Flash Media Server is being routed through a proxy.

  • Page 14: Configuring Edge Servers

    A second problem surfaces when RTMPT is specified in the URI. You may specify this protocol only for the first prefix. The following are valid URIs: rtmpt://foo/?rtmp://bar/app/inst rtmpt://foo:443/?rtmp://bar/app/inst The following are invalid URIs: rtmpt://foo/?rtmpt://bar/app/inst rtmp://foo/?rtmpt://bar/app/inst Configuring edge servers All Flash Media Server functionalities—live streaming, on-demand streaming, messaging, shared object handling, scripting—take place as application instances.

  • Page 15: Deploying A Cluster Of Edge Servers

    You can find examples of the configuration files, their tag structures, detailed information about the tags, including cross references to associated tags, syntax, and examples in Chapter 3, “Configuration Files” in Managing Flash Media Server. Deploying a cluster of edge servers You can also deploy a group of connected edge servers as a cluster.

  • Page 16: Connecting To A Cluster Of Edge Servers

    Connecting to a cluster of edge servers When edge servers are configured into a cluster, the clients probably do not know that edge servers are present and servicing their connection requests. This is a secure and desirable strategy for disguising the address of the origin server. A different scheme for connecting clients to Flash Media Server is required.

  • Page 17: Clustering Reverse Proxies

    When the load on an edge starts to scale down, so does its affinity value. Because the client always looks to connect to the edge with the lowest affinity value, this edge begins to take back connections that had spilled over into the next edge. The objective is to balance the number of connection requests to the available resources, and have all connections to the same application instance again pass through the same edge.

  • Page 18: Setting Up Origin And Proxy Servers

    Use the following guidelines as you install and configure the origin and proxy servers. Using these guidelines helps ensure satisfactory performance and results: Make sure your Macromedia license permits you to use proxy servers or a proxy cluster. Deploy all proxy and origin servers on identical computers.

  • Page 19: Maintaining Edge Server Clusters

    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. Confirm that this Flash Media Server instance is working correctly. Configure the Flash Media Server instance as an origin server.

  • Page 20: Clearing The Edge Server Cache

    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: 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>\*.*...

This manual is also suitable for:

Flash media server 2

Table of Contents