Installation guide
• IftheAMF3clientdecidestosendaByteArray,forexample,thentheAMF0clientwillbe
disconnected,sinceAMF0clientsdon’tunderstandByteArrays.(WhenanAMF0clientis
disconnected because of incompatible encoding, this event will be logged in the server’s
logles.)
Wherever the server needs to serialize data for clients, it will generally attempt to serialize data
rstinAMF0.Ifthatisnotpossible,theserverwillautomaticallyserializethedatainAMF3.
is support is available in all of the basic communication methods: NetConnection.call,
Client.call, application.broadcastMsg, SharedObjects, NetStream.send,
anddataembeddedinvideoles.It’salsoimportanttonotethataserver-to-server
NetConnection(throughserver-sideActionScript)willdefaulttoAMF3.
Inaddition,defaultobjectencodingcanbesetintheApplication.x ml le. is can also be
overridden for each individual NetConnection via the NetConnection.object-
Encoding property. For example, the Application.x ml may say AMF3, but you can set a
NetConnectiontobeAMF0bysettingthisproperty,orviceversa.
e addition of AMF3 support gives Flash Media Server 3 a much more exible tool for data
sharing, and opens up even richer possibilities for interactive applications—in many cases
eliminating the need to integrate with other backend server technologies.
Administration API
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 6 or later.
eAdministrationAPIcanbeusedtocreatecustomtoolstomonitor,congure,andmanage
FlashMediaServer3.eAdministrationAPImethodscanbecalledoverHTTPviaaweb
client,orviaaFlashPlayerorAdobeAIRclientoverRTMPfromanyversionofclient-side
ActionScript. Administration methods can be used to perform tasks such as adding or removing
administration accounts, server conguration, garbage collection, virtual host administration,
application and stream monitoring, and more.
FordetailsaboutusingtheAdministrationAPI,see“UsingtheAdministrationAPI”inthe
Adobe Flash Media Server Conguration and Administration Guide.Itisalsodescribedindetail
in the Adobe Flash Media Server Administration API Reference.
Deploying Flash Media Server 3
InstallingFlashMediaServer3isasimpleprocess,whetherdeployingtoLinuxorWindows
platforms. Your rst step is to design your deployment structure. Flash Media Server can consist
ofindividualinstallations,asinglepublishingpointconnectedwithaCDN,oramorecomplex
Edge/Originarchitecture,ifrequired.Itisrecommendedthatyouconsultthe Adobe Flash Media
Server Technical Overview manual to help you assess your needs and design your specic
deployment.
Regardlessofyourdeploymentstructure,youmustruntheinstalleroneachcomputeronwhich
youwanttorunFlashMediaServer.Onceitisinstalled,youneedtocongureeachserver
individually,designatingEdgeandOriginservers,andsoon.Fordetailedinstallationinstruc-
tions, refer to the Adobe Flash Media Server Installation Guide.
Upgrading from Flash Media Server 2
AllofyourMacromediaFlashMediaServer2andMacromediaFlashCommunicationServer
applicationswillbefullycompatiblewithFlashMediaInteractiveServer3,soupgradingshould
beaseamlessprocess.NoupgradeisavailablefromFlashMediaServer2toFlashMedia
StreamingServer3becauseitisanewproduct.ToupgradetoFlashMediaStreamingServer,you
must purchase a full license.
First, the target installation folder for Flash Media Server 3 is dierent from the Flash Media
Server2installationfolder.InWindows,thedefaultfolderisProgram Files\Adobe\
Flash Media Server 3.InLinux,thedefaultfolderisnow/opt/adobe/fms.
28