29
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
3
Restart the server.
Configure how applications are assigned to server processes
Note:
This section does not apply to Flash Media Streaming Server because it doesn’t support multiple processes.
In some scenarios, you might want to change how applications are assigned to server processes. 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) and fmscore (Linux). The master process is a monitor that starts core
processes when necessary. There can be only one master process running at a time, but there can be many core
processes running at a time.
Note:
The number of core processes you can run is limited by system memory. Do not run more than 100, and you
probably won’t need more than 20. If you are configuring the number of core processes and using the
reloadApp()
Administration API or HTTP command, see
Tech Note kb403044
.
You can configure how applications are assigned to server processes in the
Process
section of the Application.xml
configuration file. Settings in an Application.xml file in a virtual host folder (for example,
rootinstall
/conf/_defaultRoot_/_defaultVHost_/Application.xml) apply to all the applications running in that virtual
host. Settings in an Application.xml file in an application’s folder (for example,
rootinstall
/applications/myApp/Application.xml) apply only to that application. The following is the XML structure:
<Application>
<Process>
<Scope>vhost</Scope>
<Distribute numprocs="3"></Distribute>
<LifeTime>
<RollOver></RollOver>
<MaxCores></MaxCores>
</LifeTime>
<MaxFailures>2</MaxFailures>
<RecoveryTime>300</RecoveryTime>
</Process>
...
</Application>
Configure a process scope
❖
The
Scope
tag specifies at which level application instances are assigned to core processes. An application instance
can run by itself in a process or it can run in a process with other instances. Enter one of the following values for
the
Scope
element.
Element
Description
AutoCloseIdleClients
Disable this feature for an individual application by setting the
enable
attribute to
false
. If this
element is disabled in Server.xml, the feature is disabled for all applications, even if you specify
true
in the Application.xml file.
MaxIdleTime
Specifies the maximum idle time allowed, in seconds, before a client is disconnected. The default
idle time is 600 seconds (10 minutes). You can set a different value for each application.
If no value is set for this element, the server uses the value set in the Vhost.xml. file. If no value is set
for this element in the Vhost.xml file, the server uses the value in the Server.xml file.
The value of the
MaxIdleTime
element in the Vhost.xml file overrides the value of the
MaxIdleTime
element in the Server.xml file.