Configure the Flash Media Streaming Server

Overview

The Flash media streaming server delivers streaming content to students. This content includes Echoes (on-demand content) and/or real-time live webcasts. You can use either the Wowza Media Server (Wowza) or the Adobe Media Server (Adobe).

Besides the configuration information contained on this page, you may also want to review the bandwidth requirements and example scenarios provided in Bandwidth Requirements for Capture and Media Formats. While the information provided there is in the context of live webcasting, the specifications shown apply to both live webcasting and on-demand content delivery.

Configuration Options

The following pages provide the necessary instructions for installing and configuring the flash media server:

• Configure an External Wowza Media Server
• Configure an External Adobe Media Server

While you can install the flash media server on the same server as the ESS, for performance and scalability, we strongly recommend using a separate server. Both configurations are referred to as "external" because you will select "External Flash Server" in the Streaming Settings section of the System Settings page on the ESS. "Internal" configurations are only available for existing customers who are upgrading. See the note below.

You can use a single flash media server for both on-demand and live content, or you can use multiple flash media servers to deliver streaming content. Note the following points:

• Live webcasting must be streamed from a Wowza Media Server.
• You can have one flash media server (Wowza or Adobe) to deliver on-demand content, and another (Wowza) media server to deliver live content.

• If you use multiple flash streaming servers, one must be used for live content and one must be used for on-demand content; you cannot stream one type of content from two different servers (load-balancing).

Be sure you also obtain the proper licensing for the flash media server. For example, the use of Wowza requires a Wowza Production license, to allow for the number of concurrent connections required to stream ESS content to users. Refer to your flash media server documentation or sales representative for additional information.

As always, if you have questions or need clarification, contact Echo360 Technical Support for additional assistance.

Media Server Recommendations

Because media server load can vary dramatically from one installation to the next, it is difficult to make general recommendations. However, these are baseline requirements:

• 64-bit OS preferred
• 4 Cores (minimum)
• 8 GB RAM (minimum)
• 1 GB NIC

You are strongly encouraged to refer to the product websites for additional information and server requirements:

• Wowza: http://www.wowza.com/faq.
• Adobe: http://www.adobe.com/products/adobe-media-server-standard/tech-specs.html

Beyond these minimum requirements, consider the proportions of on-demand versus live content.

• When serving on-demand content, the server needs to move data from the storage disk to the streaming server to the student computer. But this data transfer does not have to happen in real time. The audio, video, and display is reassembled and synchronized when the Echo plays. This means the server should have fast data transfer ("fast disks") and a generous amount of CPU, but little RAM or network bandwidth.
• Live webcasting occurs in real time. It does not require a fast disk because data is not stored there during the webcast. It requires, by contrast, a fast network: the data (video, audio, display) must travel to multiple student computers and appear perfectly synchronized. It requires a high-bandwidth network with large amounts of RAM. 

Consider these questions when determining media server requirements and configuration options.

• Will I use live webcasting at all, or will I use on-demand content delivery only?
• Will I use live webcasting regularly for classes or only for special events or unusual situations?
• Will live webcasts replace current on-demand content or will I be providing regular live webcasts and on-demand content?
• If upgrading to EchoSystem 5.5 and currently using an internal configuration, does my current ESS/media server device have sufficient power to provide live webcasting in addition to my current on-demand load? Will I be better off moving to an external media server?

These links can help you estimate system needs:

• Deployment Planning. Provides system planning considerations as well as file transfer and content delivery information within the context of how network bandwidth is used.
• Bandwidth Requirements for Capture and Media Formats. Provides very specific information regarding the bandwidth used for live (and on-demand) content delivery and how to calculate it accurately. 
• Wowza FAQs page. Useful if you are using a Wowza Media server. The Performance and Scalability section of this page provides performance testing information for both on-demand and live content delivery, as well as the hardware specifications for the machine on which the tests were performed.

Adjust the Wowza Media Server

If you are using a Wowza media server, you should review and, if necessary, adjust the settings applied by the initial configuration. Refer to these pages on the Wowza website:

• Wowza FAQs page: http://www.wowza.com/faq. See the section on performance and scalability.
• General performance tuning: http://www.wowzamedia.com/forums/content.php?46.
• If you are running Wowza on Linux, information on running Wowza as a named user in Linux: http://www.wowza.com/forums/content.php?433
• Wowza configuration tuning: http://www.wowza.com/forums/content.php?5-general-tuning.
• If you are using Wowza with a Java Virtual Machine (JVM) on Windows: http://www.wowza.com/forums/showthread.php?1029-Windows-tuning-running-the-quot-server-quot-Java-VM-(tuning).
  

Review the Firewall Port settings for the Wowza Media Server, especially if you do live webcasts.