Installation guide

YoucancongureFlashMediaServertospawnFMSCoreprocessesbyconguringthescopenode

in the global Application.xml le. Valid scopes include adaptor, vhost, app, inst.

Depending on the scope you choose, you can congure each core process separately. For example,

if you congure the system to scope adaptors to dierent core processes, each setting in the specic

adaptor.xmlleandallsubsequentXMLlesareusedtocongurethatcoreprocess.Inthis

conguration,youcanseteachcoreprocesstolistenonadierentport,orchangetheSSLor

HTTP tunneling settings.

Inanotherexample,ifyousetscopetoapp, you can congure each core process with

bandwidth limits, provided you have a separate application.xml le for each application

running on your system.

e following process conguration is the default:

</LifeTime>

</Process>

Let’slookathowchangingthescopesettingaectsyoursystem.efollowingguresillustrate

the eect of changing your scope conguration.

ese settings are optimal for stateful applications where clients need to communicate with each

other(chat,livevideo,gaming,ordata-sharingsolutions).

No process scope (default setting). All clients connect to

a single scope.

<scope>adaptor</scope>

Process scope “adaptor.” Each adaptor has its own

core process. Virtual hosts and applications running

on dierent adaptors do not interfere.