When upgrading from version 4.0 to version 4.5 of Flash Media Server, be aware of changes to the XML configuration files.

ams.ini (fms.ini) changes

The configuration file fms.ini has been renamed to ams.ini.

The cache cleaning tool can be started when the HTTP server starts:

SERVER.HTCACHECLEAN_ENABLED = true

The cache root for the web server can be specified in this configuration file:

SERVER.HTCACHEROOT = /opt/adobe/ams/Apache2.2/cacheroot

The Flash Media Server 4.5 fms.ini file does not store the Administrator password. The following parameter has been removed from the 4.5 fms.ini file:

> # Password for server admin 
> # For example: 
> #    SERVER.ADMIN_PASSWORD = bar 
> # 
> SERVER.ADMIN_PASSWORD = adminadmin

The password is stored in the Users.xml file as a salted hash. To reset the password, see Delete administrator accounts and reset passwords.

Adaptor.xml file changes

The default value of MaxHeaderLineLength is now 8192.

There are two new elements: Adaptor/SSL/SSLVerifyClient and Adaptor/SSL/SSLVerifyDepth.

Two new tags FlowSendMaxBufferSize and FlowSendMaxUnsentAge have been introduced:<RTMFP enable="true"> <!-- Max value of the send buffer size. Rtmfp can auto-tune the send --> <!-- buffer size at runtime, but not greater than this value. --> <!-- Default is 2MB. This value can not be set less than 127 KB --> <FlowSendMaxBufferSize>2097152</FlowSendMaxBufferSize> <!-- Max unsent age of the send buffer allowed. Default is 8000 ms --> <FlowSendMaxUnsentAge>8000</FlowSendMaxUnsentAge> </RTMFP>

<RTMFP enable="true"> 
    <!-- Max value of the send buffer size. Rtmfp can auto-tune the send --> 
    <!-- buffer size at runtime, but not greater than this value.       --> 
    <!-- Default is 2MB. This value can not be set less than 127 KB         --> 
    <FlowSendMaxBufferSize>2097152</FlowSendMaxBufferSize> 
    <!-- Max unsent age of the send buffer allowed. Default is 8000 ms --> 
    <FlowSendMaxUnsentAge>8000</FlowSendMaxUnsentAge> 
</RTMFP>

Application.xml file changes

The PeerLookupEvents element is new. Use this element to determine how peer lookup events are dispatched.

The element /StreamManager/EventsDir specifies the physical location where Event information for live streaming is stored.

The RTMFP section provides the means to control the behavior of application-specific RTMFP functionality. It includes the following elements: PeerLookupEvents, GroupControl, and JoinLeaveEvents. The HDS section provides the means to control the behavior of application-specific HTTP dynamic streaming functionality. It includes the following elements: Recording and ContentProtection.

Logger.xml file changes

There are no changes to the Logger.xml file.

Server.xml file changes

You can specify how the cacheclean tool can be started: <!-- The command line option to start the cacheclean tool --> <!-- $Directory/$Program $RequiredOptions $AdditionalOptions --> <!-- (where $Directory can be either relative to $AMSROOT or --> <!-- absolute; All mandatory options for the Program need to be --> <!-- taken care inside RequiredOptions tag, and any additonal --> <!-- options need to be included in AdditionalOptions tag.) --> <!-- The cache is enabled/cleaned by default on Linux only. --> <HtCacheClean enabled="${SERVER.HTCACHECLEAN_ENABLED}"> <Directory>Apache2.2/bin</Directory> <Program>htcacheclean</Program> <RequiredOptions>-p${SERVER.HTCACHEROOT} -d5 -l1024K</RequiredOptions> <AdditionalOptions>-n -t -i</AdditionalOptions> </HtCacheClean>

The /RTMP/ConnectionTimeout element and /HTTP/ConnectionTimeout element specify how long to wait before timing out an outgoing connection, in milliseconds. The default is -1 which uses the OS timeout to block outgoing connections.

<!-- The command line option to start the cacheclean tool --> 
    <!-- $Directory/$Program $RequiredOptions $AdditionalOptions --> 
    <!-- (where $Directory can be either relative to $AMSROOT or --> 
    <!-- absolute; All mandatory options for the Program need to be --> 
    <!-- taken care inside RequiredOptions tag, and any additonal --> 
    <!-- options need to be included in AdditionalOptions tag.) --> 
    <!-- The cache is enabled/cleaned by default on Linux only. --> 
    <HtCacheClean enabled="${SERVER.HTCACHECLEAN_ENABLED}"> 
        <Directory>Apache2.2/bin</Directory> 
        <Program>htcacheclean</Program> 
        <RequiredOptions>-p${SERVER.HTCACHEROOT} -d5 -l1024K</RequiredOptions> 
        <AdditionalOptions>-n -t -i</AdditionalOptions> 
    </HtCacheClean>
<ConnectionTimeout>-1</ConnectionTimeout>

Enable a Registry core to activate a single AMSCore instance dedicated to handling services for Adobe Media Gateway. This AMSCore process comes to life on start-up and allows Adobe Media Gateway to register its services to Adobe Media Server. Enable this registry core only when using Adobe Media Gateway.

<Registry enabled="false"> 
    <!-- Adaptor to run registry core on --> 
    <AdaptorName>_defaultRoot_</AdaptorName> 
</Registry>

Note:

Adobe Media Gateway is discontinued as a part of Adobe Media Server, since AMS 5.0.7. Adobe Media Gateway is not a supported product now.

Users.xml file changes

The Users.xml file contains a salted password hash for the Administrator Console password:

<Password>e206a5e1b52dcb4eaf024ca6adbe321b86cf0079bb747b78134ddaf8375e10aff905da0b28e84c5a</Password>

Vhost.xml file changes

No changes.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy