Installation guide

Send aggregate messages
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 9,0,115,0 or later.
By default, applications break up aggregate messages into individual messages before delivering
them to clients. By default, aggregate messages are enabled. Applications can be congured not
to deliver aggregate messages by setting the AggregateMessages parameter to false in the
Application.x ml le.
SendingaggregatemessagesreducesCPUusageandincreasesservercapacity.However,itcan
introducesomelatency,soitisnotrecommendedforreal-timeone-to-onecommunication.Itis
recommended for on-demand and live broadcast applications where latency will have little eect.
Congure content storage
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 6 or later.
Storagecongurationisimportanttoserverperformance.Ifyourharddiskaccessisnotfast
enough to keep up with the bitrate of your content, your clients will receive buer empty
messages and the overall quality of service will suer.
eservercanuselocalornetworkstoragetoservemediales.Inthe Application.xml le,
you can change the default location where streams and shared objects are stored, and map
virtual directories to physical directories on local or network storage to manage your content.
is can be very convenient in team environments, when you may not always want content
creators to have direct access to your Flash Media Server, or if you have a large library of media
les that you don’t want to copy to your Flash Media Server.
Conguring security features
Flash Media Server 3 has several security features that you can easily set in the conguration
les.(Formoreinformationaboutsecuringyourserverandcontent,refertothe“Security
features”section.)
Verify SWF les
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 9,0,115,0 or later.
e server can be congured to verify client SWF les before allowing them to connect to an
application.VerifyingSWFlespreventssomeonefromcreatingtheirownSWFlesthat
attempt to stream your content, or using your server resources. e server compares the
connecting SWF with existing SWF les on your Flash Media Server, and allows the connection
if there is a match.
IntheApplication.xml le, you can specify one or more folders on the server to hold these
SWF verication les. is is done within the node, <SWFVerication>. You can also
congure the versions to check the length of time the verication data is held in cache, and any
exceptions(suchasFlashMediaEncoder).Youcanalsocongurehowoentheservershould
checkforupdatedSWFvericationles.HereisasamplefromtheApplication.xml le. By
default SWFVerication is turned o.
38