
186 Configuration Files
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 override attribute for certain
tags in the virtual host’s Application.xml file.
Example
<LoadOnStartup override="no">false</LoadOnStartup>
By default, the Bandwidth and BandwidthCap container tags includes an override
parameter set to
“yes”, which allows the values for the ClientToServer and
ServerToClient tags nested in these sections to be overridden. The Client tag in this XML
files includes an
override="no" attribute by default.
Here are the rules Flash Media Server uses when applying the
override attribute:
■ When the override attribute is included in a tag and set to no, application-specific
Application.xml files can not override that tag’s setting.
■ All subtags under the LoadOnStartup tag cannot be overridden.
■ If you omit the override attribute, the LoadOnStartup tag can be overridden.
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>
Commenti su questo manuale