MACROMEDIA FLASH MEDIA SERVER 2-MANAGING FLASH MEDIA SERVER Manual page 184

Each virtual host can contain multiple Application.xml files. The Application.xml file in the
virtual host directory configures the default settings for applications within the virtual host. If
you want to have different settings for a particular application, create a specific
Application.xml file in the application's registered application directory (for example, ../
applications/app_name) with the settings you want.
Overriding default settings
Flash Media Server administrators can include the optional
tags in the virtual host's Application.xml file.
Example
<LoadOnStartup override="no">false</LoadOnStartup>
By default, the
Bandwidth
parameter set to
"yes"
tags nested in these sections to be overridden. The
ServerToClient
files includes an
override="no"
Here are the rules Flash Media Server uses when applying the
When the
override
Application.xml files can not override that tag's setting.
All subtags under the
If you omit the
override
The Application.xml file contains the following file structure.
<Application>
<Process>
<Scope></Scope>
<LifeTime>
<RollOver></RollOver>
<MaxCores></MaxCores>
</LifeTime>
<MaxFailures></MaxFailures>
<RecoveryTime></RecoveryTime>
</Process>
<LoadOnStartup>false</LoadOnStartup>
<MaxAppIdleTime>1200</MaxAppIdleTime>
<JSEngine>
<RuntimeSize>1024</RuntimeSize>
<MaxTimeOut>0</MaxTimeOut>
<ScriptLibPath></ScriptLibPath>
<FileObject>
<VirtualDirectory></VirtualDirectory>
</FileObject>
</JSEngine>
184 Configuration Files
and
BandwidthCap
, which allows the values for the
attribute by default.
attribute is included in a tag and set to
tag cannot be overridden.
LoadOnStartup
attribute, the
override
container tags includes an
ClientToServer
override
no
tag can be overridden.
LoadOnStartup
attribute for certain
override
and
tag in this XML
Client
attribute:
, application-specific