Installation guide

Distributed cores
Feature in Flash Media Interactive Server; requires Flash Player 6 or later.
To further increase the capacity and reliability of your server, you can distribute connections
acrossmultipleprocessesforaspecicscope.Forexample,ifyourscopewassetto“adaptor,”you
could have connections spread across any number of core processes for each virtual host.
Likeprocessscopes,thedistributedcorefeatureletsyouincreasethecapacityofyourserver.
Distributed cores let you engage more RAM for caching and more threading for the
process-intensive connection routine. ey cannot be used when deploying a multiway hybrid or
live solution because connections need to be on the same core process to share communication.
Security features
Encrypted media support
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 10 or later.
Flash Media Server 3.5 now supports les that are protected through Flash Media Rights
Management Server. You can leverage all the streaming and interactive features of Flash
Media Server 3.5 to deliver signed and encrypted content, or even deliver via HTTP with the
built-in HTTP server. For more information about Flash Media Rights Management Server,
see www.adobe.com/products/ashmediarightsmanagement.
SWF verication
Enhanced in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 9,0,115,0 or later.
SWF verication in Flash Media Server 3.5 is a security feature that allows you to directly control
which SWF les can connect to your server. Without implementing this feature, any SWF with
theproperconnectionUniformResourceIdentier(URI)andapplicationnamecouldfreely
connect, potentially accessing your streams and using server resources.
With SWF verication, you can congure the server to check that the SWF le attempting to
access a certain application or application instance belongs to a group of preapproved SWF les.
Enablingthisfeatureiseasy.YousimplystoreacopyoftheapprovedSWFleintheapplication
directory and turn on the feature in the Application.xml le. When a SWF le connects to
the server, the server veries that the le exactly matches the SWF le in your application
directory, and then accepts the connection.
To approve a SWF le for any instance of a certain application, you place it in the SWFs directory
in that application’s folder. To approve a SWF le for a specic instance, you place it in the SWFs
directory inside that instance’s folder. is feature has been enhanced in Flash Media Server 3.5
to allow verication of SWF les without requiring copies on the server computer. You can now
use the File plug-in to retrieve SWF les that are stored in distributed locations.
Note: If you’re deploying an Adobe AIR application, copy the SWF le that you compiled either into the Adobe
AIR package or to the server to make it available for SWF verication, or use the File plug-in to point to its
remote location.
Standardized server redirection handling
Enhanced feature in Flash Media Interactive Server; requires Flash Player 6 or later.
Flash Media Server 3.5 supports stream redirection in RTMP, which behaves much like HTTP
302redirection.isfeaturecanbeenabledbyusinganaccessadaptorserver-sideplug-inorin
server-sideActionScript.Forexample,whileusinganaccessadaptorrunningonanEdgeserver,
you could use this redirect method to notify a client that a requested video does not exist in the
expectedlocation,andpassitanewURIforthestream.ItcouldalsobeusefulforotherFlash
Media Server load-balancing schemes as well as content organization.
22