Installation guide

InpreviousversionsofFlashMediaServer,utilizinganSSLwastheonlyoptiontoencryptyour
streamdata.However,thisresultedinanoticeablyslowerconnection.enewRTMPEinFlash
MediaServer3securesthechannelwith128-bitencryptionbetweentheclientandtheserver
withouttheperformancedegradationofSSL,andwithouttheneedforacerticate.
SimilartotheimplementationofSSL(RTMPS),you’llonlyneedtospecifyRTMPEinyour
client’s connection string to utilize the protocol. For example:
nc.connect(“rt mpe://w w w.exa mple.com/myApplication”)
RTMPEbehavesexactlylikeRTMP,butisencrypted.Additionally,youcanrequestanencrypted
tunnelingconnectionbyspecifyingRTMPTE.
Built-in bandwidth detection
New feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 6 or later.
Bandwidth detection is built into Flash Media Server, and is enabled by default. e new
bandwidth detection, called native bandwidth detection, provides better performance and
scalabilitythanscriptedbandwidthdetection.Tousenativebandwidthdetection,simplymake
sure bandwidth detection is enabled, and write client code that calls functions built into Flash
MediaServer.isfeatureiscompatiblewithActionScript2and3,andnoserver-sidecode
is required.
You can also choose to disable native bandwidth detection and implement detection in a
server-sidescript,especiallyifyouwanttoreuseexistingcode.Touseserver-sidebandwidth
detection, use the specialized main.asc le Adobe provides for bandwidth detection and
disable native bandwidth detection in the Application.xml le. For more information, refer
to the Adobe Flash Media Interactive Server 3 Developer Guide.
Process scopes
New feature in Flash Media Interactive Server; requires Flash Player 6 or later.
FlashMediaInteractiveServer3givesyoucontroloverhowserverprocessesareallocated.When
you start the server, you are starting a process called FMSMaster.exe(Windows)or
fmsmaster (Linux).ApplicationinstancesruninprocessescalledFMSCore.exe(Windows)
or fmscore(Linux).
Flash Media Server operates with multiple processes. With the default installation, there will be
four processes running: master,Edge,core, and admin.
e master process is a monitor that starts core processes when necessary. ere can only be one
master process running at a time, but there can be many core processes running at a time. You
can congure how applications are assigned to server processes in the Application.xml le.
You can specify the number of processes, the process scope, how long a process runs, and the
number of process failures allowed before a core process is disabled.
ClientsalwaysconnectthroughtheEdgeprocess(whetheranEdge/Origincongurationexists
ornot).emasterprocessisresponsibleforspawningandrollingovereachcoreprocess.
Clientsneverconnecttothemasterprocess,andthemasterprocesscannotbecongured.e
followinggureillustratesthemaster,core,andEdgeprocesses.
20