Installation guide

Illustration of process scopes
Distributed cores
New 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will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
SWF verication
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 9,0,115,0 or later.
SWF verication is a new security feature in Flash Media Server 3 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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foranyinstanceofacertainapplication,you’dplaceitintheSWFs directory
in that application’s folder; to approve a SWF for a specic instance, you’d place it in the SWFs
directory inside that instance folder.
Note: If you’re deploying an Adobe AIR application, copy the SWF le that you compiled into the Adobe AIR
package, to the server to make it available for SWF verication.
21