ADOBE FLASH MEDIA SERVER 3.

5 Configuration and Administration Guide
® ®

Last updated 3/2/2010

© 2009 Adobe Systems Incorporated. All rights reserved.
Copyright

Adobe® Flash® Media Server 3.5 Configuration and Administration Guide If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any permission required from the copyright owner. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization. Adobe, the Adobe logo, Adobe AIR, ActionScript, and Flash are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the US and other countries. Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac, Macintosh, and Mac OS are trademarks of Apple Inc., registered in the United States and other countries. All other trademarks are the property of their respective owners. This work is licensed under the Creative Commons Attribution Non-Commercial 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/3.0/us/ Portions include software under the following terms: Sorenson Spark™ video compression and decompression technology licensed from Sorenson Media, Inc. Speech compression and decompression technology licensed from Nellymoser, Inc. (www.nellymoser.com) Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA. Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101, consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60, 60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.

Last updated 3/2/2010

iii

Contents
Chapter 1: Deploying the server Deploying servers in a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Deploying edge servers ................................................................................................ 1

Chapter 2: Configuring the server Provisioning the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Working with configuration files Configuring performance features Configuring security features Configuring content storage ....................................................................................... 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Performing general configuration tasks Configuring Apache HTTP Server

Chapter 3: Using the Administration Console Connecting to the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Inspecting applications Manage administrators Managing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4: Monitoring and Managing Log Files Working with log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Access logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Application logs Diagnostic logs

Chapter 5: Administering the server Start and stop the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Checking server status Checking video files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Clearing the edge server cache Managing the server on Linux

Chapter 6: Using the Administration API Working with the Administration API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Chapter 7: XML configuration files reference Adaptor.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Application.xml file Logger.xml file Server.xml file Users.xml file Vhost.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE iv
Contents

Chapter 8: Diagnostic Log Messages Message IDs in diagnostic logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

1 Install Adobe® Flash® Media Server and verify the installation on each computer.Last updated 3/2/2010 1 Chapter 1: Deploying the server Deploying servers in a cluster Workflow for deploying servers in a cluster You can deploy multiple servers behind a load balancer to distribute the client load over multiple servers. 2 Configure a load balancer to see the servers hosting Flash Media Interactive Server or Flash Media Streaming Server.com/go/learn_fms_redundancy_en • www. then for HTTP tunnelling to work. Configure the load balancer to distribute the load in round-robin mode and to monitor over TCP port 1935.adobe. Cookies can be enabled in the load balancer or in the Adaptor. or Flash Media Streaming Server) in a cluster.adobe.com/go/learn_fms_clustering_en • www. see the following articles: • www.com/go/learn_fms_scalable_en Deploying edge servers Workflow for deploying edge servers Note: Flash Media Streaming Server cannot be configured as an edge server.0. By default. Flash Media Development Server.adobe. Clustering multiple servers behind a load balancer Add all the servers in the cluster to the pool (server farm) in the load balancer. . The load balancer distributes traffic among all the servers in the pool. which eliminates single points of failure. To run the server as an edge server.28 or later in Windows only.xml configuration file in the Adaptor/HTTPTunnel/SetCookie element. Ensure that you deploy all servers on computers that meet the minimum system requirements. cookies are currently supported only on Adobe® Flash® Player 9. you should enable cookies when you deploy servers behind a load balancer. use lowercase names for all folders and applications. You can deploy any version of the server (Flash Media Interactive Server. Deploying multiple servers enables you to scale an application for more clients and creates redundancy. If the server does not have an externally visible IP address. Note: For cross-platform compatibility. The load balancer checks the cookie and sends requests with this cookie to the same server. For more information. the server runs as an origin server. you must configure an XML file. Note: For tunnelling connections. Typically you would run Flash Media Interactive Server as an origin server on one computer and run Flash Media Interactive Server as an edge server on another computer.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 2
Deploying the server

It is also possible to run one server in hybrid mode—that is, to configure some virtual hosts to run as edge servers and other virtual hosts to run as origin servers. This scenario is good for development but not for production.
1. Install Flash Media Interactive Server and verify the installation on each computer.

Deploy all edge and origin servers on computers that meet the minimum system requirements. For information about installing and verifying installation, see the Installation Guide. Note: For cross-platform compatibility, use lowercase names for all folders and applications.
2. Configure an edge server and restart.

On the edge server, edit the Vhost.xml file of the virtual host you want to run as an edge server.
3. Verify that the edge server can communicate with the origin server.

The easiest way to verify is to create an explicit connection. Create a SWF file with an explicit connection to the edge server and run the vod or live service.
4. If you’re installing multiple edge servers, copy the Vhost.xml file to the same directory on each edge server. 5. Verify that each edge server can communicate with the origin server. 6. Place the origin server and those edge servers nearest to it on the same subnet. 7. If you’re deploying more than one edge server, configure a load balancer.

Place the load balancer between the clients and the edges. Configure the load balancer to access the pool of edge servers in round-robin mode and to monitor over TCP port 1935. Use the virtual IP (VIP) address of the pool as the IP address in the RouteEntry element of each edge server’s Vhost.xml file. For detailed information on how to configure the RouteEntry element, see the comments in the RouteEntry element of the default Vhost.xml file, or see RouteEntry.

Configure edge servers
To configure the server to run as an edge server, edit the Vhost.xml configuration file of the virtual host you want to run as an edge server. The Vhost.xml file defines how the edge server connects clients to the origin server. Note: You can also configure some virtual hosts to run applications locally (as origins), while others run applications remotely (as edges); this is called mixed mode or hybrid mode. Configure a virtual host to run as an edge server 1 Open the Vhost.xml file of the virtual host you want to configure and locate the following code (comments have been removed):

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 3
Deploying the server

<VirtualHost> ... <Proxy> <Mode>local</Mode> <Anonymous>false</Anonymous> <CacheDir enabled="false" useAppName="true"></CacheDir> <LocalAddress></LocalAddress> <RouteTable protocol=""> <RouteEntry></RouteEntry> </RouteTable> <EdgeAutoDiscovery> <Enabled>false</Enabled> <AllowOverride>true</AllowOverride> <WaitTime>1000</WaitTime> </EdgeAutoDiscovery> </Proxy> </VirtualHost>

Note: The default VHost.xml file is located in the RootInstall/conf/_defaultRoot_/_defaultVHost_ directory.
2 Edit the following XML elements, as needed.
Element
Mode

Required/optional Required

Description Enter local to configure the server to run as an origin server. Enter remote to configure the server to run as an edge server. A Boolean value specifying whether the edge server connection is implicit (true) or explicit (false). The default value is false. Enables or disables the caching of streams to disk, in addition to caching in memory, on an edge server and allows you to specify the cache location. There are two attributes: enabled and appname. To enable caching, set the enabled attribute to "true". When enabled, the server places streams in the RootInstall/cache/appName directory by default. Use the useAppName attribute to specify whether to use the application name as the name of the cache for the application. Vod applications get significant performance gains when caching is enabled.

Anonymous

Optional

CacheDir

Optional

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 4
Deploying the server

Element
LocalAddress

Required/optional Optional

Description Specifies the local IP address to which to bind a proxy's outgoing connection (the proxy’s loopback address). This element allows the administrator to control network traffic by isolating incoming and outgoing traffic to separate network interfaces. Specifies, in each RouteEntry element, how to route connections from the origin to the edge. There is one attribute, protocol, that indicates the protocol of the outgoing connection. Set this attribute to either "rtmp" or "rtmps". To override the RouteTable protocol for a specific RouteEntry element, add a protocol attribute to the RouteEntry element you want to change. Each RouteEntry element maps a host/port pair to a different host/port pair. In the following example, connections to host1:port1 are routed to host2:port2:
host1:port1;host2:port2

RouteTable

Optional; create a routing table when it is not necessary or desirable for application developers to see the origin server URL or when you want to use implicit connections. Optional

RouteEntry

Typically, host1:port1 is your edge server and host2:port2 is your origin server. The following example routes connections destined for host "edge" on port 1935 to host "origin" on port 80:
<RouteEntry>edge:1935;origin:80</RouteEntry>

You can specify a wildcard character (*) for any host or port. The following example routes connections destined for any host on any port to host "origin" on port 1935:
<RouteEntry>*:*;origin:1935</RouteEntry>

You can also specify a wildcard for the host/port to which connections are being routed. The following example routes connections destined for any host on any port to the same host on port 80:
<RouteEntry>*:*;*:80</RouteEntry>

To reject connections, you can specify that a host/port combination be routed to null:
<RouteEntry>edge:80;null</RouteEntry>

The RouteEntry element has a protocol attribute. This attribute overrides the RouteTable protocol for a specific RouteEntry element. For example, RouteTable may have one RouteEntry element that specifies an encrypted outgoing RTMPS connection and another RouteEntry tag that specifies the regular RTMP connection. If a protocol is not specified, the outgoing connection uses the same protocol as the incoming connection.

3 Validate the XML and save the Vhost.xml file. 4 Restart the server.

More Help topics
“Adaptors and virtual hosts” on page 6

Connect to an edge server
There are two types of edge server connections: explicit and implicit (also called anonymous).

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 5
Deploying the server

An explicit edge server prefixes its address to the origin server’s URL in the client NetConnection.connect() call. For example, for applications running on fms.foo.com, instead of clients connecting to an application with a connection string such as rtmp://fms.foo.com/app/inst, clients are directed through the edge, which prefixes its protocol and hostname to the origin URL, as in the following:
rtmp://fmsedge.foo.com/?rtmp://fms.foo.com/app/inst

An implicit edge server does not change or modify the origin server’s URL in the client NetConnection.connect() call. The identity (the IP address and port number) of the implicit edge is hidden from the application developer. Create an explicit connection ❖ Use the following syntax in a client-side NetConnection.connect() call to make an explicit connection to an edge server:
rtmp://edge/?rtmp://origin/app

A question mark (?) separates the edge’s prefix from the main URL. The prefix contains only the protocol, hostname, and optionally the port number. The prefix must always end with a trailing slash. Create an implicit connection 1 In the Vhost.xml configuration file, set the Proxy/Anonymous element to true. Note: Restart the server after changing the Vhost.xml file.
2 In the Vhost.xml file, create a routing table in the RouteTable element; for more information, see the comments

about RouteEntry tags in the Vhost.xml file installed with Flash Media Server.
3 Use the following syntax in a client-side NetConnection.connect() call to make an implicit connection to an

edge server:
rtmp://edge/app/appinstance

Connect edge servers in a chain ❖ You can chain together any number of edges when you make connections to the origin server. Use the following syntax to chain two explicit edges to direct connection requests to the origin server:
rtmp://edge1/?rtmp://edge2/?rtmp://origin/app/inst

As the connection moves through each edge in the chain, the server consumes the first token in the string. For example, after making the connection to edge1, the connection string changes to:
rtmp://edge2/?rtmp://origin/app/inst

Note: You can specify the RTMPT protocol only for the edges, not for the origin. When you use URL decoration to chain edges, Flash Player 7 and earlier versions may have problems with shared objects because of the embedded question mark (?) character in the URL. Call the following function to encode or escape the question marks from the URL before passing the URL to the shared object:
function escapeURI(uri) { index = uri.indexOf('?'); if (index == -1) return uri; prefix = uri.substring(0, index); uri = uri.substring(index); return prefix += escape(uri); }

xml. virtual host (also called vhost). You can assign an IP address or a port number to an adaptor. and application instances—has distinct configuration settings stored in XML files in the RootInstall/conf directory: Server.com and www. The server is divided into hierarchical levels: server.test. For this reason. Note: For information about registering applications with the server and storing media. conf Server. but not to a virtual host. Each virtual host hosts one or more applications. You can add adaptors and virtual hosts to organize the server for hosting multiple applications and sites. application. Each application has one or more instances. You can provision Flash Media Server in several ways. For example. There are also configuration files for information about administrators and logging: Users. you can provision it so that each customer has their own section. If you’re hosting multiple websites on a server. see “Configuring content storage” on page 33. which enables you to use one file to configure the server. Provisioning allows multiple administrators to configure their own sections on one server. assign it to its own adaptor.xml Users.xml. adaptor.Last updated 3/2/2010 6 Chapter 2: Configuring the server Provisioning the server Adaptors and virtual hosts Provisioning a server divides the server into separate sections. use adaptors to organize virtual hosts by IP address or port number.xml. This is called running the server in hybrid mode. Vhost. If you use your server for hosting. use virtual hosts to give customers their own root folders. you could use two virtual hosts to host www.xml Default structure of the server’s configuration (conf) directory .xml _defaultVHost_ Application.xml Logger.xml and Logger. depending on your needs. and Application.xml.com on the same server. For example.xml. The server is at the top level and contains one or more adaptors. if a virtual host needs its own IP address to configure SSL. virtual host. Configuration folder structure Each of these levels—server. You can also configure one virtual host to run as an edge server and one to run as an origin server.example.ini _defaultRoot_ Adaptor. Adaptor.xml Vhost. adaptor. and application. Each adaptor contains one or more virtual hosts. The most important configuration parameters have been pulled out to the fms.xml fms.ini file.

for example. 6 To log in to the Administration Console on the new adaptor. Each virtual host must have a Vhost. the adaptor can listen on all available interfaces. For information about logging in to the Administration Console. either internally or externally. The server must have a Server. fms.5 CONFIGURATION AND ADMINISTRATION GUIDE 7 Configuring the server Edit any of these XML files in a text or XML editor and restart the server for the changes to take effect.xx:1935</HostPort> <HostPort name="edge2" ctl_channel=":19351">yy. adaptor2/admin. If an IP address is not specified.xx. multiple adaptors can listen on port 1935.yy:1935</HostPort> 5 Restart the server.xml file in its root directory. • The server has one initialization file. create or paste a copy of an Application. • You may place an Application.xml file that serves as a default to all applications in that virtual host and a Users.yy. The following rules define the conf directory structure: • The root configuration folder is RootInstall/conf. in the RootInstall/conf directory. • Virtual host directories may also contain an Application. you also must restart Flash Media Administration Server. see “Working with configuration files” on page 9. • The default adaptor’s root directory is RootInstall/conf/_defaultRoot_.ini. Each adaptor must have a default virtual host. or they cannot interoperate.xml or fms. see “Connecting to the Administration Console” on page 40.xml file. and a Users.xml file and a Vhost.xml file. including the administrator user name and password and the settings you chose during installation.yy. • The default virtual host’s root directory is RootInstall/conf/_defaultRoot_/_defaultVHost_. for example. as in the following example: <HostPort name="edge1" ctl_channel=":19350">xx. use the syntax adaptorname/username in the Username box. The server uses the control channel (ctl_channel) attribute internally to communicate between server processes (adding a HostPort element creates a new FMSEdge process).xml file. For more information.xml file. . Ensure that the control channels on which separate adaptors listen are different from each other.xml file in its root directory.xml file in the conf directory. For more information about registered application directories.xml file in an application’s registered directory to create an application-specific configuration.xx. You cannot remove or modify the name of this directory. You cannot remove or modify the name of this directory.xml file. You cannot remove or modify the name of this directory. In addition. a Logger. the control channels of two adaptors must be different. 2 In the adaptor2 directory. unless they use different IP addresses.xml file in the adaptor directory.xml file that contains information about administrators of that virtual host. If you modify Users. This file contains commonly used settings. Add an adaptor 1 Create a new directory with the name of the adaptor in the RootInstall/conf folder. Each adaptor directory must contain a _defaultVHost_ directory and an Adaptor. create or paste a copy of the _defaultVHost_ directory and an Adaptor. If a host has multiple IP addresses. add a HostPort element to listen on a new port for this adaptor: <HostPort name="edge2" ctl_channel=":19351">:1936</HostPort> The name attribute must be unique on the server. 4 In the Adaptor. The server uses the HostPort value to listen for clients—no two adaptors can listen on the same port. 3 In the _defaultVHost_ directory. The control channel (ctl_channel) attribute and the HostPort value specify the ports to which an IP address should bind. RootInstall/conf/adaptor2.Last updated 3/2/2010 FLASH MEDIA SERVER 3. see the Developer Guide. Each adaptor must have an Adaptor.ini.

Note: You can call the startVHost() Administration API or log in to the Administration Console without restarting the server. 7 Connect to the new virtual host by specifying the virtual host name. 2 Copy an Application.xml Users. For information about logging in to the Administration Console. see “Connecting to the Administration Console” on page 40. 5 Restart the server. Administrators are either server-level users (similar to a root user) or virtual host-level users.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml Vhost.xml file. .xml _defaultVHost_ Application.xml file. specify an application directory in the AppsDir element.xml Logger.xml Users. a Vhost.xml file is required only if you are defining administrators for this virtual host. and a Users.xml file to the new virtual host folder.xml The conf directory with an additional adaptor called adaptor2 Add a virtual host 1 Create a folder with the name of the virtual host in an adaptor folder. in the Server name field. for example.) 3 In the Vhost. RootInstall/conf/_defaultRoot_/www.example. www. If you log in to an adaptor other than the default adaptor.xml fms.xml _defaultVHost_ Application.xml Users.5 CONFIGURATION AND ADMINISTRATION GUIDE 8 Configuring the server Administrators are defined in the UserList section of the Users.example. 6 Log in to the Administration Console.xml Vhost. conf Server. for example.com.xml adaptor2 Adaptor. you are considered a virtual host administrator and don’t have privileges to manage the server or users.xml file.com<\AppsDir> Note: It is possible to use the same applications directory for multiple virtual hosts.xml file.ini _defaultRoot_ Adaptor.example. 8 Connect a test application to the new virtual host to make sure it works.xml file. but it causes namespace conflicts and is not recommended. (The Users.com. for example: <AppsDir>C:\www. 4 Validate the XML and save the Vhost.

application-specific Application.xml file override the values in the vhost-level Application.xml fms. and hierarchy. you also must restart Flash Media Administration Server. To edit a configuration file.xml The conf directory with an additional virtual host called www. You can also prevent settings in the vhost-level Application. Navigate to rootinstall\applications\vod and rootinstall\applications\live. see “Configuration folder structure” on page 6.xml.xml files cannot override that tag’s setting. and restart the server.xml www.xml Users.xml _defaultVHost_ Application.ini _defaultRoot_ Adaptor.com Overriding values in the Application.xml file You can place an Application. • You can override the LoadOnStartup tag. Each folder contains an Application.com Application.example.xml Vhost. as in the following: <LoadOnStartup override="no">false</LoadOnStartup> The following rules apply: • When the override="no".Last updated 3/2/2010 FLASH MEDIA SERVER 3. Add an override attribute to any tag and set it to "no".5 CONFIGURATION AND ADMINISTRATION GUIDE 9 Configuring the server conf Server. open it in a text editor.xml Users. Values set in the application-level Application.xml Logger.xml file. Working with configuration files Editing configuration files Note: For information about configuration file names. • You cannot override the subtags of the LoadOnStartup tag. modify and save it. The values in these files override the values in the vhost-level file rootinstall\conf\_defaultRoot_\_defaultVHost_\Application. .xml file.xml Users.xml file in an application’s folder.xml. If you modify Users.xml Vhost. locations.xml file.xml settings from being overridden by the applicationlevel Application.example. To see an example. look at the vod and live applications included with Flash Media Server.

The ROOT symbol is mapped to the location of the FMSMaster. You can also create additional map files and reference them from the substitution. 4 Save the file and restart the server.xml in the RootInstall/conf folder that maps the symbols to strings that the server substitutes when it reads the configuration files.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 3 For example. this substitution. 3 Enter a new value for the SERVER.xml file. Create a file named substitution. future updates are faster: you can edit the map file instead of editing each configuration file.xml.xml file in the RootInstall/conf directory. 2 Enter the following XML structure: <Root> <Symbols> <SymbolName>StringToMapTo</SymbolName> </Symbols> </Root> Add a SymbolName element for each symbol you want to create. 2 Save a copy to another location as a backup. 4 The server processes the additional map files in the order in which they appear (in KeyValueFile elements in the substitution. 5 Open the Administration Console and log in with your new password. 5 Symbols defined in external map files are processed in the order in which they appear in each file.xml file. the server looks for the Symbols tag and processes the child tags in the order in which they appear.xml file maps the symbol TESTUSERNAME to the value janedoe: <Root> <Symbols> <TESTUSERNAME>janedoe</TESTUSERNAME> </Symbols> </Root> . When the server starts.ini in a text editor.xml file exists. The server builds the symbol map in the following order: 1 The predefined symbols ROOT and CONF are evaluated. After you’ve set up a map file. it looks for the fms.ini file 1 Open RootInstall/conf/fms.ADMIN_PASSWORD parameter.5 CONFIGURATION AND ADMINISTRATION GUIDE 10 Configuring the server It’s a good idea to check that the XML is valid after editing an XML configuration file.exe file and the CONF symbol is mapped to the location of the Server. ROOT and CONF. The server has two predefined symbols.xml file).ini file. 3 If the substitution. Edit the fms.ini file is evaluated.xml file: 1 Create a new XML file and save it in the RootInstall/conf folder as substitution. The installer defines a few mappings during the installation process and stores them in the fms. Using symbols in configuration files To simplify configuration. Create a substitution. that are always available.ini file and the substitution. 2 The fms. you can use symbols as values for XML elements in configuration files.

The syntax for specifying an environment variable as a symbol is ${%ENV_VAR_NAME%}. create one or more KeyValueFile elements in the substitution. Note: If you change the Users. but no white space within double quotation marks. When the server reads the XML file. .xml file. They simply contain a collection of symbol-value pairs.txt: <Root> <KeyValueFile>C:\testfiles\mySymbols. you must restart the server. the server maps the following symbol to the COMPUTERNAME variable: ${%COMPUTERNAME%} When you use an environment variable. it substitutes the value from the substitution.xml.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file in a text editor. the following references the file C:\testfiles\mySymbols.ADMIN_USERNAME}"> and replace the symbol SERVER. The % characters indicate to the server that the symbol refers to an environment variable and not to a user-defined string. Using environment variables To refer to an environment variable in one of the XML configuration files. it is surrounded by quotation marks.ADMIN_USERNAME with the symbol TESTUSERNAME. you can also create additional map files. you don’t have to define it in the substitution. Do not place comments on the same line as a symbol definition. Creating additional map files You can specify all of your text substitution mappings under the Symbols tag in substitution.txt</KeyValueFile> </Root> These external files are not in XML format. it would not be surrounded by quotation marks.xml file. However. 5 Locate the line <User name="${SERVER. To do this. 6 Restart the Administration Server. you must restart the Administration Server. The server trims leading or trailing white space from both the symbol and the value. If the symbol were used as a regular value. If you change any other XML configuration file.5 CONFIGURATION AND ADMINISTRATION GUIDE 11 Configuring the server 4 Open the RootInstall/conf/Users.xml file. Each element can hold the location of one external file. where each pair appears on a separate line and takes the following form: symbol=value The following example shows three symbol-value pairs: USER_NAME=foo USER_PSWD = bar HELLO= "world and worlds" Place comments on separate lines that begin with a number sign (#). For example. use the name of the environment variable within percent (%) characters. The first equal sign (=) in a line is considered the delimiter that separates the symbol and the value.xml file as follows: <User name="janedoe"> Note: Because this symbol is used as an attribute. For example.

FLVCACHE_MAXSIZE. As long as the cache has not reached capacity. To decrease the amount of memory the server process uses. the server gives the stream a reference to the segment for playback. Each time a stream attempts to access a segment. if there still isn’t enough room for a new segment. decrease the value of SERVER. After removing all unused segments. This value shares memory with the running process and has a limit of 2 GB in Windows and 3 GB in Linux. Note: Cache settings have no effect on live streams. This is the maximum size of the cache. For more information about the core log file. Adobe recommends that you ensure that your total system memory usage does not exceed the process limit of your OS. 1 Open the RootInstall/conf/fms.FLVCACHE_MAXSIZE parameter. To increase the probability that a requested stream will be located in the recorded media cache. increase the value of SERVER. the server retrieves the segment from its source.FLVCACHE_MAXSIZE.ini file. segments of the stream are stored in a cache on the server. the server checks the cache. and returns a reference to that segment to the stream. While a large cache size is useful. When the cache is full. 2 Edit the SERVER. the server notifies the client that the stream is not available and makes an entry in the core log file. If the segment is available. complete the following tasks: 1 “Configure the recorded media cache” on page 12 2 “Configure the size of stream chunks” on page 13 Configure the recorded media cache When a stream is requested from the server.5 CONFIGURATION AND ADMINISTRATION GUIDE 12 Configuring the server Configuring performance features Configure the server for live video delivery To configure the server to deliver live media. Consider memory limits and desired memory and stream performance when utilizing the memory cache. starting with the least recently used. see “Monitoring and Managing Log Files” on page 55. . If the segment is not available. The size of the cache limits the number of unique streams the server can publish. as live streams do not need or utilize the cache. The default value is 500. the server places segments in the cache. If you have cache-full events in the core log file. 3 Restart the server. increase the size of the cache or limit the number of streams playing.Last updated 3/2/2010 FLASH MEDIA SERVER 3. inserts it into the cache. complete the following task: ❖ “Combine audio samples” on page 13 Configure the server for vod delivery To configure the server to deliver recorded media. the server removes unused segments. in megabytes.

60. 1 Open the RootInstall/conf/fms. 1 Open the Application. audio samples are not combined. However. combine audio samples. 3 Restart the server. You can specify the size of a chunk. The default value is 80.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 2 In the Client element. the more benefit is gained from larger chunk sizes. Large values reduce CPU usage because there are fewer writes. Send aggregate messages Sending aggregate messages reduces CPU usage and increases server capacity. The default value is 8. The default value is 4096 bytes.xml file” on page 93. The default value is 60.SUBSCRIBERS: If there are more than this number of subscribers to a stream. 2 Locate the following XML code: <Client> . set this value to 1.. set the OutChunkSize element to a value between 128 and 65536 bytes.xml file. The larger the content size and the higher the bandwidth of the receiving connection.COMBINESAMPLES_MAXSAMPLES: Combine this many samples into one message.ini file. the server breaks up aggregate messages into individual messages before delivering them to clients. set this value to 8. APP. 2 Edit the following parameters: • • • • APP.5 CONFIGURATION AND ADMINISTRATION GUIDE 13 Configuring the server Configure the size of stream chunks Streams break into chunks as they are written to the network. For more information.COMBINESAMPLES_HICPU: If the CPU is higher than this value. APP. To increase live streaming capacity. To increase live streaming capacity. To increase live streaming capacity. set this value to 1. audio samples are combined. 1 Open the Application. <AggregateMessages enabled="true"></AggregateMessages> <Client> 3 Make sure that the enabled attribute is set to true (the default). Important: Do not combine audio samples if you are also using the live aggregation message feature.0. When this setting is disabled.xml file. To increase live streaming capacity. 4 Validate the XML and save the Application. APP.xml file. . audio samples are not combined.COMBINESAMPLES_LOCPU: If the CPU is lower than this value. 5 Restart the server. 3 Restart the server. set this value to 1. Combine audio samples To handle more connections while broadcasting a live stream. large values can delay other content on lower bandwidth connections.. see “Application. The default value is 4.0 and above. You can configure applications to deliver aggregate messages to clients running on Flash Player 9.

. and Application.5. unless the values are defined in the Vhost. The values defined in the Server.xml.xml file (the Vhost. Each port the server is configured to listen on represents a listener. such as 12.xml files.g. Close idle connections Sometimes users abandon their connections to an application.Last updated 3/2/2010 FLASH MEDIA SERVER 3.. The values defined in the Application.xml file. The value of this element is a global setting for all listeners.xml file. the server imposes a maximum total combined rate of 30 connections per second. 1 Locate the following code in the Server. You can set a fractional maximum connection rate. To close idle connections. If the element is set to 10 connections per second.xml.. Vhost. A value of 0 or -1 disables this feature. each listener has a limit of 10 connections per second. 2 Validate the XML and save the XML file. the server can close the idle clients. If there are three listeners and the MaxConnectionRate is set to 10. by default). Enable closing idle connections 1 Locate the following code in the Server. When a client has been idle longer than the maximum idle time (10 minutes.xml files and Application.xml file override the values defined in the Vhost.xml configuration file: <Root> <Server> .. The server also writes a message such as “Client x has been idle for y seconds” in the core and event logs.Closed.5 CONFIGURATION AND ADMINISTRATION GUIDE 14 Configuring the server Limit connection requests A high connection rate to the server can negatively impact the experience of users already connected to the server.Connect. Once you enable the feature in the Server.xml configuration files specify how often the server should check for idle clients. <Protocol> <RTMP> <Edge> <MaxConnectionRate>100</MaxConnectionRate> Element MaxConnectionRate Description The maximum number of incoming connections per second the server accepts. publishing) or receiving (e. you can disable the feature for individual virtual hosts or individual applications in the Vhost.g. enable the feature in the Server. The server closes the client connection to the server and writes an x-status code of 432 in the access log.xml file: . A client is active when it is sending (e.Connect.xml file. Impact Connections requested at a rate above this value remain in the TCP/IP socket queue and are silently discarded by the operating system whenever the queue becomes too long. subscribing to) data. Listeners are defined in the HostPort element in the Adaptor. the server sends a status message to the NetConnection object (the client) with the code property set to NetConnection. 3 Restart the server.xml values).xml values override the Server. To reclaim these resources for new and active clients.Idle followed by NetConnection.xml configuration file apply to all clients connected to the server.xml file. per listener. Elements in the Server.

in seconds. consider the type of applications running on the server. Configure settings for virtual hosts You can disable this feature for a virtual host or specify a different maximum idle time for a virtual host in the Vhost. If this element is 0 or less. .xml. When you configure this element.xml file and remove the comments: <VirtualHost> <AutoCloseIdleClients enable="false"> <MaxIdleTime>600</MaxIdleTime> </AutoCloseIdleClients> </VirtualHost> 2 Edit the following elements. The default value is false. MaxIdleTime 3 Restart the server. You can set a different value for each virtual host. before a client is disconnected. file. The default idle time is 600 seconds (10 minutes). 1 Locate the following code in the Vhost. A shorter interval results in more reliable disconnection times but can also result in decreased server performance. the feature is disabled for all virtual hosts. If this element is disabled in Server.xml file. the server uses the value set in the Server.xml. the feature is disabled. Element AutoCloseIdleClients Description Set the enable attribute to true to close idle clients.xml file overrides the value of the MaxIdleTime element in the Server. in seconds. a user might leave the window to idle out. if you have an application allowing users to watch short video clips. Specifies the interval. A low value may cause unneeded disconnections. Impact CheckInterval A client is disconnected the first time the server checks for idle connections if the client has exceeded the MaxIdleTime value. in seconds. If the enable attribute is omitted or not set to true.xml file. before a client is disconnected.5 CONFIGURATION AND ADMINISTRATION GUIDE 15 Configuring the server <AutoCloseIdleClients enable="false"> <CheckInterval>60</CheckInterval> <MaxIdleTime>600</MaxIdleTime> </AutoCloseIdleClients> 2 Edit the following elements.Last updated 3/2/2010 FLASH MEDIA SERVER 3. the default idle time is used.xml file. If no value is set for this element. The value of the MaxIdleTime element in the Vhost. The default idle time is 600 seconds (10 minutes). The default interval is 60 seconds. even if you specify true in the Vhost. Specifies the maximum idle time allowed. For example. Element AutoCloseIdleClients Description Disable this feature for an individual virtual host by setting the enable attribute to false. MaxIdleTime Specifies the maximum idle time allowed. at which the server checks for active client connections.

exe (Windows) or fmsmaster (Linux). Element AutoCloseIdleClients Description Disable this feature for an individual application by setting the enable attribute to false. In some scenarios. If this element is disabled in Server. 1 Locate the following code in the Application. file. The value of the MaxIdleTime element in the Vhost.exe (Windows) and fmscore (Linux). Settings in an Application. If no value is set for this element.xml file in a virtual host folder (for example. the server uses the value set in the Vhost. You can configure how applications are assigned to server processes in the Process section of the Application. Note: The number of core processes you can run is limited by system memory.xml file. even if you specify true in the Application. Application instances run in processes called FMSCore. The master process is a monitor that starts core processes when necessary.xml file. The default idle time is 600 seconds (10 minutes).xml file. before a client is disconnected. RootInstall/applications/myApp/Application.xml file and remove the comments: <VirtualHost> <AutoCloseIdleClients enable="false"> <MaxIdleTime>600</MaxIdleTime> </AutoCloseIdleClients> </VirtualHost> 2 Edit the following elements. When you start the server.xml.xml file in an application’s folder (for example. Settings in an Application. and you probably won’t need more than 20.xml.xml) apply only to that application.xml) apply to all the applications running in that virtual host. see Tech Note kb403044.xml configuration file.5 CONFIGURATION AND ADMINISTRATION GUIDE 16 Configuring the server Configure settings for applications You can disable this feature for an application or specify a different maximum idle time for an application in the Application. If you are configuring the number of core processes and using the reloadApp() Administration API or HTTP command. the server uses the value in the Server.xml file overrides the value of the MaxIdleTime element in the Server. You can set a different value for each application. MaxIdleTime 3 Restart the server. Specifies the maximum idle time allowed.xml file. the feature is disabled for all applications.Last updated 3/2/2010 FLASH MEDIA SERVER 3. but there can be many core processes running at a time. you are starting a process called FMSMaster. RootInstall/conf/_defaultRoot_/_defaultVHost_/Application. Configure how applications are assigned to server processes Note: This section is only applicable to Flash Media Interactive Server and Flash Media Development Server. Do not run more than 100. The following is the XML structure: .xml file. Flash Media Streaming Server doesn’t support multiple processes. If no value is set for this element in the Vhost. in seconds. There can be only one master process running at a time. you might want to change how applications are assigned to server processes.

In this scenario. You can set the Distribute numprocs attribute to a value greater than 1 to distribute instances across that number of processes. you could either distribute those instances to one core process (<Scope>app</Scope>) or three core processes (<Scope>inst</Scope>). if the value of Scope is adaptor. Distribute a process scope among multiple core processes The four process scopes don’t provide a good distribution for all scenarios. a number between 3 and 11 is realistic for most cases. Value adaptor vhost app inst Description All application instances in an adaptor run together in a process. you could set Scope to app and Distribute numprocs to 3 to distribute the application instances among three core processes.Last updated 3/2/2010 FLASH MEDIA SERVER 3. if you have one application and want to run 25 instances of that application. the value of Distribute can be vhosts. 3 Enter one of the following values for the Distribute element. which contain applications. The value of the Distribute tag must be a scope that is lower in order than the value in the Scope tag. For example. the value of Distribute can be insts or clients. An application instance can run by itself in a process or it can run in a process with other instances. Note: There is no limit to the value of the numprocs attribute. which means that the default behavior is to distribute application instances to three core processes.. Running every instance in its own process can create many processes. apps. the server uses the value immediately lower than the one specified in the Scope tag. </Application> Configure a process scope ❖ The Scope tag specifies at which level application instances are assigned to core processes. insts. Each application instance runs in its own process. Enter one of the following values for the Scope element. If the value of Scope is app.5 CONFIGURATION AND ADMINISTRATION GUIDE 17 Configuring the server <Application> <Process> <Scope>vhost</Scope> <Distribute numprocs="3"></Distribute> <LifeTime> <RollOver></RollOver> <MaxCores></MaxCores> </LifeTime> <MaxFailures>2</MaxFailures> <RecoveryTime>300</RecoveryTime> </Process> . All instances of a single application run together in a process. 1 Set the scope value.. Adobe recommends using prime number values because they result in a more even distribution of connections to processes. which contain clients. All application instances in a virtual host run together in a process. . By default. Scopes have an enclosing relationship with a strict ordering: adaptors contain virtual hosts. 2 Set the numprocs value to a value higher than 1. but you should never need more than 40. The default value of numprocs is 3. or clients. which contain instances. Depending on available RAM. In other words. This provides the best application isolation and uses the most system resources. This is the default value.

The duration of process 1 is partially determined by the current time when process 1 starts. process 2 then accepts new client connections until process 3 starts. the current time is 12:20. Process 1 starts C. The following diagram depicts the way in which the server rolls over processes.. when process 1 starts. Each client connection runs in its own process. it accepts new client connections to the application until process 2 starts. it accepts new connections until the next process starts: that is. This feature is disabled by default. Chat and gaming applications are not stateless because all clients share the application state. Process 3 starts E. In the XML. Stateless applications don’t require clients to interact with other clients and don’t have clients accessing live streams. Client connections B. because the maximum core processes limit was reached When each process starts. clients Configure the number of core processes and how long each process runs ❖ Specify the number of core processes in the MaxCores tag (the maximum number of core processes that can exist concurrently) and the number of seconds that a core process can run in the RollOver tag. Process 1 ends. For example. Each application instance runs in its own process. This is the default value. All instances of an application run together in a process. as shown in the diagram. if a shared chat application were set to client. Process 4 starts. the messages wouldn't reach everyone in the chat because they’d be split into separate processes. When a core process reaches the limit.. and so on. Most vod (video on demand) applications are stateless because each client plays content independently of all other clients. when process 1 starts. To disable this feature. Process 2 starts D. and the maximum core processes value is set to 3. A B C D E 12:00 12:20 1:00 2:00 3:00 4:00 5:00 A. any new connections roll over to a new core process. indicating that every hour a new process should start. For example. the rollover time is set to 3600 seconds (1 hour).Last updated 3/2/2010 FLASH MEDIA SERVER 3. set RollOver to 0. you must also set the Distribute numprocs attribute to a value greater than 1. . The duration of the first process is determined by the clock time. so the duration of process 1 is only 40 minutes (because it is 40 minutes until the beginning of the hour in real time). because rollover values are calibrated to the real clock time. Note that the duration of process 1 might or might not be the full duration specified by the rollover value. subsequent processes have a duration equal to the specified rollover time. Use this value for stateless applications only. If you choose this value. indicating that the maximum number of processes at any given time is 3: <Process> <Scope>app</Scope> <LifeTime> <RollOver>3600</RollOver> <MaxCores>3</MaxCores> </LifeTime> .5 CONFIGURATION AND ADMINISTRATION GUIDE 18 Configuring the server Value vhosts apps insts Description All instances of applications in a virtual host run together in a process.

Verifying SWF files prevents third parties from creating their own applications that attempt to stream your resources. you must set an identical RollOver value for each VHost. For more information. To allow localhost connections. To disable this feature. To do this. set the Distribute numprocs attribute to a value greater than 1.com. but clients are disconnected periodically. set MaxCores to 0. 3 Restart the server. By default. Use this feature to guard against a behavior in which a faulty core process can use the entire CPU by being repeatedly launched very quickly. old core processes continue to serve earlier connections. you can specify a value in the MaxCores tag to limit the maximum number of core processes that can run simultaneously. 1 Open the RootInstall/conf/fms.ALLOW parameter to a comma-delimited list of domains that are allowed to connect to the server. If a value is set. This ensures that an application instance is not split across multiple processes. This feature is disabled by default.5 CONFIGURATION AND ADMINISTRATION GUIDE 19 Configuring the server Note: If you have multiple VHosts with Process/Scope set to adaptor. Check for process failures 1 Enter a value in the MaxFailures tag to specify the maximum number of process failures allowed before a core process is disabled. specify localhost.ALLOW = example. . the server ignores any value you assign to MaxCores and sets it to 1. VHOST. In this case. such as vod applications. In stateless applications. The default value is all.com allows connections from the example.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file” on page 178.ini file. Enter a value in the RecoveryTime tag to specify the minimum recovery time for contained elements. set the tag to 0 to disable checking for process failures. you can restrict which domains are allowed to connect to a virtual host. If the application is not stateless.com domains. connections are allowed from all domains. then set the Distribute tag to clients or set the Scope tag to inst. see “Vhost. example2. Note: Applications that are loaded using the Administration API (including applications loaded using the Administration Console) are not checked for process failures. Note: An application is considered stateless if you configure it to distribute clients over multiple processes. The default value is 2. only the domains listed are accepted. a master process will not launch a core process until a minimum recovery time elapses.com and example2. 2 Once disabled. For example. Configuring security features Restrict which domains can connect to a virtual host If desired. Verify SWF files You can configure the server to verify client SWF files before allowing them to connect to an application. 2 Set the VHOST.

0 and later of Flash Media Streaming Server.xml file defines the location of verifying SWF files in the SWFFolder tag. Configure the application-specific Application. You can override this default in the SWFFolder tag of the Application.xml file and an Application. The plug-in developer overrides these values with paths to the external content repository.xml or Server. Locating SWF files for verification The server looks for verifying SWF files in the following locations. Flash Media Interactive Server. • All applications in a virtual host.xml file. SWF verification is disabled by default. By default. 2 The Vhost-level Application. Configure the Server.xml file. When verification is enabled. You can verify SWF files at the following server scopes: • Individual applications. • Administrative applications that have access to all server levels.xml file.115.xml file. Note: SWF files connecting to Flash Media Administration Server cannot be verified. The server does not send a NetStream status message to the client.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The Application. The SWFFolder tag defines the location.xml file. To verify SWF files. For client applications that comprise multiple SWF files or SWF files that dynamically load other SWF files. The server passes any values present in Application.xml file. This feature is supported in versions 3.xml file: . in order: 1 The application-specific Application. 4 If a File plug-in is enabled for retrieval of SWF files. the server verifies it. you must set <SWFVerification enable = "true"> in the Application. the SWF file that contains the NetConnection object to connect to the server is the one that the server attempts to verify. the server looks in the default location: /applications/application_name/SWFs.xml configuration file. Note: If you’re deploying an Adobe AIR application.0. Configure the Application. or in the File plug-in. If a client SWF file fails verification.xml to the plug-in. the server verifies that the client SWF file requesting a connection to the server matches the verifying SWF file. the Server. The verifying SWF file is a copy of the client SWF file that you place on the server or in an external content repository. it is allowed to connect to the application. adding the path <SWFFolder>C:\Program Files\Adobe\Flash Media Server 3. the server looks for verifying SWF files in that file path. This Application. and Flash Media Development Server. which means SWF files that are common to all applications. If the SWF file is verified. the server calls the File plug-in. If SWFFolder contains a file path. If SWFFolder is empty. the server looks for verifying SWF files in that file path. Configure SWF verification for applications 1 Locate the following section of the Application. This tag specifies a location for global SWF files. copy the SWF file you compiled into the AIR package to the server or external content repository. the server looks in RootInstall/applications/application_name/SWFs folder for the verifying SWF file. 3 The server checks the SWFFolder tag in the Server. you can add a path to the folder from which you serve SWF files.xml file defines the location of verifying SWF files for all applications on the virtual host. When the client SWF file connects to the server. If SWFFolder is empty. If you installed Apache with Flash Media Server. if it exists.0 or later or Adobe® AIR™. For example.5 CONFIGURATION AND ADMINISTRATION GUIDE 20 Configuring the server Note: Verification of SWF files requires Flash Player 9. the server looks in the default location: /applications/application_name/SWFs. on Windows.5\webroot</SWFFolder> prevents you from needing to maintain two copies of each SWF file.xml file in the Vhost folder. If SWFFolder contains a file path.xml file. the server disconnects the NetConnection object and logs an event to the access log.

These SWF files are used to verify connecting SWF files. Specifies the number of levels of subfolders within a parent folder to scan for SWF files. enter the path to the folder from which you are serving SWF files. Adobe recommends keeping the default value. MinGoodVersion None. The default value is "false".Last updated 3/2/2010 FLASH MEDIA SERVER 3. Specifying a positive value scans that number of subfolder levels. The default value is 5 seconds. Element SWFVerification Attribute enabled Description Set the enabled attribute to "true" or "false" to turn this feature on or off. They are the verifying SWF files. .5\webroot. <SWFVerification enabled="false"> <SWFFolder></SWFFolder> <MinGoodVersion></MinGoodVersion> <DirLevelSWFScan>1</DirLevelSWFScan> <MaxInitDelay>5</MaxInitDelay> <FirstHashTimeout>5</FirstHashTimeout> <FinalHashTimeout>60</FinalHashTimeout> <UserAgentExceptions> <Exception to="" from=""/> </UserAgentExceptions> <Cache> <TTL></TTL> <UpdateInterval></UpdateInterval> </Cache> </SWFVerification> </Application> 2 Edit the following elements. which means that the server scans only one subfolder level. leave this field blank. DirLevelSWFScan None. verifying SWF files should be placed in the applications/myApplication/SWFs folder. Specifying zero scans the parent folder and no subfolders. Specifies the minimum version of this feature to accept. MaxInitDelay None FirstHashTimeout None FinalHashTimeout None UserAgentExceptions None. For example. if you’re serving SWF files from the webroot directory on Windows.5 CONFIGURATION AND ADMINISTRATION GUIDE 21 Configuring the server <Application> . A single folder or a semicolon-delimited list of folders that contain copies of client SWF files. Specifying a negative value scans all subfolder levels. for an application called myApplication. if there isn’t a value set for this element. The maximum amount of time that a client can use to provide its first verification to the server. SWFFolder None. The maximum amount of time to process SWF files. which allows this and all future versions. The default value is the application's folder appended with /SWFs. Container. The maximum amount of time that a client can use to provide its final verification to the server. The default value is 1. If you are using the File plug-in to verify SWF files in an external content repository. The parent folder is specified in the SWFFolder element. If you installed Apache with Flash Media Server. This is a reserved field that works with Flash Player.. The default value is 0.. For example. in seconds. enter the path C:\Program Files\Adobe\Flash Media Server 3.

to bypass SWF verification. as in the following: <SWFVerification enabled="true"> . The default value is 1440 minutes (24 hours). Certain applications—for example. enable verification in the Vhost-level or application-specific Application. Container. Note: Multiple SWF files may exist in either directory.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Cache TTL None. applications/myMediaApp/SWFs/chat01. . create a folder called SWFs in the application’s folder on the server.xml file. ❖ In the Server. Create verification exceptions ❖ Add Exception elements to the UserAgentExceptions section of the Application. 2 To verify SWF files for application instances. UpdateInterval None. Use the from and to attributes to indicate the lowest and highest versions to except. and so on.xml file. users can connect to the application until the cache expires.. None. create instance folders in the SWFs directory. see the comments in the Application. such as Flash Media Live Encoder. A SWF file can be renamed and still used for verification as long as it’s a copy of the client SWF file. This is a string comparison. SWF files in the SWFs directory can verify all instances of the application..5"/> </UserAgentExceptions> </SWFVerification> Configure SWF verification globally You can configure verification for a group of SWF files on the server that are common to all applications. You can also configure other values for these SWF files. applications/myMediaApp/SWFs/chat02.0" from="FME/2. in minutes. The default value is 5 minutes.xml file. Create folders for the verifying SWF files 1 If the SWFFolder value is the default. SWF files within an instance folder can verify only that instance. with editing to make all numeric fields equal in length. The maximum time in minutes to wait for the server to scan the SWFs folders for updates when there is a miss in the cache. which means a SWF file copied to the SWFs folder is picked up by the server within 5 minutes. SWF files in the SWFs folder verify connections to any instance of the myMediaApp application. the verification values stay in the cache for 24 hours.xml file Root/Server/SWFVerification/SWFFolder tag. specify folders that hold the verifying SWF files. for example. You can add one or more exceptions to the SWF verification rules that allow specified user agents.5 CONFIGURATION AND ADMINISTRATION GUIDE 22 Configuring the server Element Exception Attribute from to Description A user agent to except from verification. For example. create the folder applications/myMediaApp/SWFs. Note: In addition to configuring the SWFFolder tag in the Server. For more information. for an application called myMediaApp. <UserAgentExceptions> <Exception to="FME/0. See “Configure SWF Verification for Applications” in this topic. The time to live for the SWF file.xml file and “Create verification exceptions” later in this topic. Adobe® Flash® Media Live Encoder—do not support the form of SWF verification used by the server. If a SWF file is removed from the server.

nc.mydomain.com. If an application specifies RTMPE without explicitly specifying a port. and restart the server.com/crossdomain. 1 Open RootInstall/conf/Server. foo. If desired. which can be a security risk.xml</CrossDomainPath> 3 Validate the Server.xml file.connect() URL. <CrossDomainPath></CrossDomainPath> 2 Specify the location of the cross-domain file in the CrossDomainPathElement. Note: RTMPE cannot currently be used between servers or from edge to origin. in the following order: 1935 (RTMPE). 4 Validate the XML.60</Allow>.133. in the NetConnection. The crossdomain XML file lets you specify a list of domains from which clients can access the edge server or Administration Server. you can disable RTMPE at the adaptor level. you can change this in the AdminServer section of the Server. RTMPS can be used instead. RTMPE requires about 15% more processing power than RTMP.. you might want to disable RTMPE (encrypted Real-Time Messaging Protocol). respectively. 1 Open RootInstall/conf/Server. Disable RTMPE By default. 3 Alternatively.com.60.. Flash Player scans ports just like it does with RTMP. </AdminServer> 2 Edit the Allow element to specify which connections to Flash Media Administration Server the server responds to. for the Administration Server): <Server> .xml and locate the following code: <AdminServer> .foo. which lets you specify a list of domains from which a client can access the server. edit the CrossDomainPath element to specify a cross-domain file. for example: <CrossDomainPath>http://store.. If you don’t control the applications that connect to Flash Media Server and you don’t want them to use RTMPE. For example: <Allow>x. 1 Open the Adaptor.xml file. This is specified as a comma-delimited list of host names. save the Server.. In some scenarios.xml file. as well as the keyword all.. RTMPE is enabled in the server’s Adaptor. To request an encrypted or encrypted tunnelling channel. Limit access to Flash Media Administration Server By default.xml file. 10.com/myMediaApplication").Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file for the adaptor you want to disable (located in RootInstall/conf). 443 (RTMPE). 80 (RTMPE).xml and locate the CrossDomainPath element in the Server element (or the AdminServer element. and full or partial IP addresses. and restart the server. Because RTMPE uses encrypted channels. applications specify rtmpe or rtmpte. 80 (RTMPTE). <Allow>all</Allow> . 10. 2 Locate the following XML: .5 CONFIGURATION AND ADMINISTRATION GUIDE 23 Configuring the server Restrict access to the server with a cross-domain file You can restrict access to an edge server or the Administration Server with a cross-domain XML file. save it.connect("rtmpe://www. there is a minor impact on performance.1. In these cases.example.. for example. a client can connect to Flash Media Administration Server from any domain or IP address. domain names.

as follows: ADAPTOR. Flash Media Server returns data to the client over port 443. 80. nc. By default. Flash Media Server provides native support for both incoming and outgoing SSL connections. .connect() method. -1935.proxyType property to "best" before connecting.This is enabled by default.ini file. 2 Specify the RTMPS protocol in the call to the NetConnection. If SSL is configured. for example. enter -443 in the ADAPTOR. To configure SSL. which is an 128-bit encrypted protocol. see the NetConnection. use RTMPS only for applications that require a higher level of security or that handle sensitive or critical data. clients must do the following: 1 Set the NetConnection. To connect to Flash Media Server over an SSL connection. 4 Restart the server. nc.connect() entry in the ActionScript® 3. See also “XML configuration files reference” on page 80 Configure SSL Secure Sockets Layer (SSL) is a protocol for enabling secure communications over TCP/IP.Last updated 3/2/2010 FLASH MEDIA SERVER 3.proxyType = "best".adobe.allow these protocols on this adaptor --> <RTMPE enabled="true"></RTMPE> </RTMP 3 Set the RTMPE enabled attribute to "false".HOSTPORT = :1935. Note: All server editions support a version of RTMP called RTMPE. 443. If you configure any port other than 443 as secure. RTMPS adheres to SSL standards for secure network connections and enables connections through a TCP socket on a secure port.0 Language Reference. The default secure port for RTMPS is 443. To configure the default secure port. For more information. 80 (RTMP tunneling). it scans the following ports in order: 1935. An incoming connection is a connection between Flash Player and the server.connect("rtmps://fmsexamples.0 Language Reference or in the ActionScript 2.RTMPE is the encrypted RTMP protocol covering both RTMPE and RTMPTE --> <!-. when Flash Player connects to Flash Media Server. Because secure connections require extra processing power and may affect the server’s performance.HOSTPORT parameter in the RootInstall/conf/fms. To specify that a port is secure.-443 When Flash Player encounters an “rtmps://fmsdomain/application” string. for example. the following client code connects securely: var nc:NetConnection = new NetConnection(). the client must specify the port in the URI.5 CONFIGURATION AND ADMINISTRATION GUIDE 24 Configuring the server <RTMP> <!-. it communicates with Flash Media Server over port 443. An outgoing connection is a connection between two servers.com/vod/instance1"). setting enabled to "false will not --> <!-. RTMPE is more lightweight than SSL and is enabled by default. place a minus (“-”) sign in front of the port number. specify that a port is secure. “rtmps://host:1935/app”. Traffic with an “rtmp://” string uses port 1935. Data passed over the secure connection is encrypted to avoid eavesdropping by unauthorized third parties.

. SSLCertificateKeyFile type="PEM" .. Element SSLCertificateFile Description The location of the certificate file to send to the client. -----END CERTIFICATE---------BEGIN CERTIFICATE----. If a certificate is signed by an intermediate Certificate Authority (CA). The location of the private key file for the certificate.xml file for the adaptor you want to configure and locate the following code: <Adaptor> . The default value is "PEM". the pass phrase must be specified in the SSLPassPhrase tag.. The private key and the certificate can be combined into one file.. You can add additional sections as needed. The next BEGIN CERTIFICATE/END CERTIFICATE pair is the intermediate CA that signed your certificate. </Adaptor> 2 Edit the following elements. Specify an absolute path or a path relative to the adaptor folder. <SSL> <SSLServerCtx> <SSLCertificateFile></SSLCertificateFile> <SSLCertificateKeyFile type="PEM"></SSLCertificateKeyFile> <SSLPassPhrase></SSLPassPhrase> <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> <SSLSessionTimeout>5</SSLSessionTimeout> </SSLServerCtx> </SSL> . 1 Open the Adaptor.. Your certificate file (if signed by an intermediate CA) should look something like the following: -----BEGIN CERTIFICATE----.5 CONFIGURATION AND ADMINISTRATION GUIDE 25 Configuring the server Certificates You can get an SSL certificate from a certificate authority or create a certificate yourself.. The type attribute specifies the type of encoding used for the certificate key file. -----END CERTIFICATE----- The first BEGIN CERTIFICATE/END CERTIFICATE pair is your certificate. it must include the intermediate certificate as part of the certificate that the server returns to the client. This can be either "PEM" or "ASN1".Last updated 3/2/2010 FLASH MEDIA SERVER 3. and configure the adaptor to listen on a secure port.. If the key file is encrypted. Secure incoming connections Specify the location of the SSL certificate and the certificate’s private key.. Specify an absolute path or a path relative to the adaptor folder.

Each domain name must have its own certificate.Last updated 3/2/2010 FLASH MEDIA SERVER 3. each virtual host has its own domain name. An RTMP connection to port 443 also fails: the server tries to perform a SSL handshake that the client fails to complete.. If the private key file is not encrypted. specify a minus sign before the port number in the ADAPTOR.00. if you’re hosting multiple customers.. add the following HostPort tag in addition to the default HostPort tag: <HostPort name="edge2" ctl_channel=":19351">:1936.-443 This configuration tells the server to listen on ports 1935 and 443.HOSTPORT}</HostPort> </HostPortList> . Configure incoming connections when multiple virtual hosts are assigned to one adaptor You can configure the server to return a certificate based on which port a client connects to. The default value is 5.HOSTPORT = :1935. Any value less than 1 is read as 1. <Ho4stPortList> <HostPort name="edge1" ctl_channel=":19350">${ADAPTOR.log file to verify that no errors have been reported. or one of a selected number of aliases for common groupings.-444</HostPort> 3 For each HostPort element. For example. encryption method. The SSL ciphers: a colon-delimited list of components. A component can be a key exchange algorithm. If you don’t specify an Edge element. An RTMPS connection to port 1935 fails: the client attempts to perform a SSL handshake that the server fails to complete. 1 Locate the following code in the Adaptor. 4 Restart the server. the edge uses the default SSL configuration. and that 443 is a secure port that receives only RTMPS connections. The amount of time in minutes a session remains valid. If a client reconnects to a session before SessionTimeout is reached. Note: Generally. the cipher suite list isn’t sent during the SSL handshake.HOSTPORT parameter in the RootInstall/conf/fms. This lets you assign multiple virtual hosts to one adaptor and return a different certificate for each virtual host.. enter an Edge element under the SSL element with an identical name attribute.5 CONFIGURATION AND ADMINISTRATION GUIDE 26 Configuring the server Element SSLPassPhrase Description The pass phrase to use for decrypting the private key file. An RTMPS connection to port 443 succeeds: the client performs a SSL handshake that the server completes. The possible values are listed here: “SSLCipherSuite” on page 91. digest type. leave this tag empty. SSLCipherSuite SessionTimeout 3 To configure a secure port for an adaptor.. 5 Check the RootInstall/logs/edge. authentication method. Do not change the default settings unless you are very familiar with SSL ciphers.ini file. </Adaptor> 2 Create new HostPort elements with unique name and ctl_channel attributes and unique port values for RTMP and SSL. as follows: ADAPTOR. .xml file: <Adaptor> .

pem</SSLCertificateFile> <SSLCertificateKeyFile>private2. Since there is no Edge tag for edge2.pem</SSLCertificateFile> <SSLCertificateKeyFile>private.pem</SSLCertificateKeyFile> <SSLPassPhrase></SSLPassPhrase> <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> <SSLSessionTimeout>5</SSLSessionTimeout> </SSLServerCtx> <Edge name="edge1"> <SSLServerCtx> <SSLCertificateFile>cert2.Last updated 3/2/2010 FLASH MEDIA SERVER 3.pem when a client connects to it on port 443. . 5 Restart the server. <SSL> <SSLServerCtx> <SSLCertificateFile>cert. edge2 will use the default configuration specified in the SSLServerCtx section that is directly under the SSL container tag.pem</SSLCertificateKeyFile> <SSLPassPhrase></SSLPassPhrase> <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> <SSLSessionTimeout>5</SSLSessionTimeout> </SSLServerCtx> </Edge> </SSL> 4 Validate the XML and save the file. The edge2 server returns cert.5 CONFIGURATION AND ADMINISTRATION GUIDE 27 Configuring the server This sample code demonstrates how to configure edge1 to return cert2.pem when a client connects to it on port 444. Secure outgoing connections 1 Open the Server.xml file and locate the following code: <Root> <Server> <SSL> <SSLEngine></SSLEngine> <SSLRandomSeed></SSLRandomSeed> <SSLClientCtx> <SSLVerifyCertificate>true</SSLVerifyCertificate> <SSLCACertificatePath></SSLCACertificatePath> <SSLCACertificateFile></SSLCACertificateFile> <SSLVerifyDepth>9</SSLVerifyDepth> <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> </SSLClientCtx> </SSL> </Server> </Root> 2 Edit the following elements.

and the file name must be hash and the extension ".xml files and enter the new values. You can import the Windows certificate store to the certs directory by running FMSMaster -console -initialize from a command line. Specifies the maximum depth of an acceptable certificate.xml. and the default value is 16. as this tag is a server-level setting that cannot be overridden in Adaptor. e98140a6. and implement a different set of ciphers in a third virtual host. The SSL ciphers: a colon-delimited list of components. The default value is 9.0. On a Windows 32-bit operating system. Each file in the folder must contain only a single certificate. A Boolean value specifying whether to verify the certificate returned by the server being connected to (true) or not (false). A component can be a key exchange algorithm. you must specify the location of the certificates. The default value is true. you might want to use a different certificate for each virtual host. the server looks for certificates in the RootInstall\certs directory. certificate verification fails.0". ❖ Copy the SSL section in the Server. in minutes. 1 Uncomment the SSL section under the Proxy tag in the appropriate Vhost. Configure virtual hosts to manage outgoing SSL connections independently For example. Do not change the default settings unless you are very familiar with SSL ciphers. However. or one of a selected number of aliases for common groupings. the more random numbers the PRNG will contain. You cannot specify anything less than 8 bytes. If a self-signed root certificate cannot be found within this depth. SSLCACertificatePath SSLCACertificateFile SSLVerifyDepth Specifies the name of a file containing one or more certificates in PEM format. assign one virtual host to each adaptor and configure your adaptors individually to override the settings in the Server.Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 28 Configuring the server Element SSLRandomSeed Description The number of bytes of entropy to use for seeding the pseudo-random number generator (PRNG). if this tag is empty. Do not disable verification unless you are certain you understand the ramifications. for example. A folder containing certificates. The more entropy. In this case. Disabling certificate verification can result in a security hazard. digest type.xml file.xml file: . In Linux. The possible values are listed here: “SSLCipherSuite” on page 169. SSLSessionCacheGC SSLVerifyCertificate How often to flush expired sessions from the server-side session cache. use a certificate in a different folder for one virtual host. encryption method. you can disable certificate checking in one virtual host.xml file to the Adaptor. You don’t need to copy the SSLRandomSeed tag. SSLCipherSuite Configure adaptors to manage outgoing SSL connections independently The SSL section in the Server. authentication method. The server may take longer to start up if you specify a large number.xml file configures all adaptors to use the same settings. Entropy is a measure of randomness.

. Performing general configuration tasks Enable checkpoint logging events Many companies use statistics from the access log to bill customers. Flash Media Server listens on port 1935 by default. For more information. To solve this problem.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Configure Flash Media Server to work with a hardware SSL proxy When you use a hardware SSL proxy. If an SSL tag is omitted from this section. the events you use to calculate billing might not occur within a billing cycle. 1 Open the RootInstall/conf/Server. The following are available as checkpoint events: connect-continue.xml file in a text editor. You can disable checkpoints at the vhost and application level in the Vhost.xml files. see the comments in the XML files located in the RootInstall/conf folder. If your programming includes live events or 24/7 programming.xml and Application. If you’ve changed the default port. you don't need to configure Flash Media Server for SSL.. 4 You can optionally set values for the CheckInterval and LogInterval elements to indicate how often the server should check for and log events.xml file. You must enable checkpoint events at the server level in the Server. The hardware encrypts the data and forwards it to the Internet. and publish-continue. You can also override the logging interval at the vhost and application levels. 2 Restart the server. Configure the hardware to forward data to Flash Media Server on port 1935. The hardware sits between Flash Media Server and the Internet. Configure the hardware to listen externally on port 443 to receive encrypted data sent over Internet from clients. .5 CONFIGURATION AND ADMINISTRATION GUIDE 29 Configuring the server <VirtualHost> . like this: <Checkpoints enable="true">. 2 Locate the Root/Server/Logging/Checkpoints element: <Checkpoints enable="false"> <CheckInterval>60</CheckInterval> <LogInterval>3600</LogInterval> </Checkpoints> 3 Set the Checkpoints enable attribute to true. you can enable checkpoint events. Checkpoint events log bytes periodically during an event. the server uses the default settings. play-continue. <Proxy> <SSL> <SSLClientCtx> <SSLVerifyCertificate></SSLVerifyCertificate> <SSLCACertificatePath></SSLCACertificatePath> <SSLCACertifcateFile></SSLCACertificateFile> <SSLVerifyDepth></SSLVerifyDepth> <SSLCipherSuite></SSLCipherSuite> </SSLClientCtx> </SSL> </Proxy> </VirtualHost> When the SSL tag is present. the entire SSL section is used to configure the virtual host. configure the hardware to forward data on that port. Data sent between Flash Media Server and the hardware is unencrypted.

IPv4. Allow the server to listen on IPv6 sockets. the server does not allow this connection. Allow Administration API methods to be called over HTTP You must specify each Administration API method that may be called over HTTP. Important: In Red Hat® Linux systems. 5 Restart the server. For more information. Note: Debug connections count against license limits. Configuring IPv6 IPv6 (Internet Protocol version 6) is a new version of Internet Protocol that supports 128-bit addresses. or in the server configuration files.xml file of the virtual host or application you want to configure.NetworkingIPV6 enable attribute to "true". Wherever a numeric IPv6 address is used in a client-side script. Open the RootInstall/conf/fms. you must update the NETWORKING_IPV6 value in /etc/sysconfig/network when installing or uninstalling IPv6. 6 Restart the server. You may need to activate IPv6 on the interfaces. 4 Save and validate the file. enclose it in brackets: .HTTPCOMMAND_ALLOW parameter to a comma-delimited list of APIs. see the operating system’s Help.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The current version of Internet Protocol. 2 Locate the following XML: <Debug> <MaxPendingDebugConnections>50</MaxPendingDebugConnections> <AllowDebugDefault>false</AllowDebugDefault> </Debug> 3 Set the AllowDebugDefault element to true.ini file and set the SERVER. Restart the server. 1 Open the RootInstall/conf/fms. IPv6 is embedded in all operating systems that the server supports. A system that only runs IPv6 can't communicate with a system that only runs IPv4. supports 32-bit addresses.xml file” on page 175. For more information. By default. Activate IPv6 on the network interface card. 2 Set the USERS. server-side script. The default value is ping. 1 Open the Application. the Administration Console must make a special debugging connection to the server. see “Users.ini file. Enclose numeric IPv6 addresses in URLs in brackets. IPv6 alleviates the address shortage problem on the Internet. and restart the server. Allow application debugging connections To play back streams and obtain data from shared objects.5 CONFIGURATION AND ADMINISTRATION GUIDE 30 Configuring the server 5 Save and validate the file.

xml configuration files. the properties are available only for that application. with the values jdoe and engineering.108]:1935/streamtest You must specify the interface zone index for a link-local address: rtmp://[fe80::204:23ff:fe14:da1c%4]:1935/streamtest It’s a good idea to register the RTMP.prop_name application.42 IPv6: fe80::204:23ff:fe14:da1c%4 Listener started ( _defaultRoot__? ) : 19350/v6 Listener started ( _defaultRoot__? ) : 19350/v4 Listener started ( _defaultRoot__? ) : 1935/v6 Listener started ( _defaultRoot__? ) : 1935/v4 Note: On IPv6-enabled Linux. and admin.config["prop_name"] Note: The properties you define are accessible from application. and that the server host has dual addresses and is listening on both interfaces: FMS detected IPv6 protocol stack! FMS config <NetworkingIPv6 enable=true> FMS running in IPv6 protocol stack mode! Host: fmsqewin2k3-02 IPv4: 10.133. respectively: <Application> <JSEngine> <config> <user_name>jdoe</user_name> <dept_name>engineering</dept_name> </config> </JSEngine> </Application> To access the property in server-side code. use the syntax in either of these examples: application. and the property value corresponds to the tag’s contents.xx.xx.192. you should configure the Adaptor.Last updated 3/2/2010 FLASH MEDIA SERVER 3. . edge.log. the properties are available for all applications on a virtual host. host name.property.5 CONFIGURATION AND ADMINISTRATION GUIDE 31 Configuring the server rtmp://[fd5e:624b:4c18:ffff:0:5efe:10. if you are using an IPv4 host name (a host name that resolves to IPv4) on an RTMPT or RTMPTE connection.config.log.128. The following xcomment fields from a sample edge log file indicate that the IPv6 stack and the IPv4 stack are available.xml appropriately to resolve connections quickly.config. If you define properties in the default Application.133. For example. the following XML fragment defines the properties user_name and dept_name. If you define properties in an Application. if necessary) in the server configuration files. See HTTPIdent2. To define a property.xml file in an application folder. it logs available stack configuration.log files (located in the RootInstall/logs/ directory). Check the logs. create an XML tag in the JSEngine section of the Application. RTMPS.xx. The property name corresponds to the tag’s name.xml file.property.xml file. and all available IP addresses for the host in the master. Defining Application object properties You can define properties for the server-side Application object in the server’s Application. not from application. When the server starts. and RTMPE protocols with a network services database and use a service name (or decimal port number.

dept_name + " department. You can also use environment variables and symbols you define in the substitution.xml file: <Application> <JSEngine> <config> <compName>${%COMPUTERNAME%}</compName> <dept>${DEPT}</dept> </config> </JSEngine> </Application> In a server-side script. given the previous XML fragment. assume that the environment variable COMPUTERNAME is equal to jsmith01."). For example.config.compName). .config.dept). Also. which results in more accurate data.config.config["user_name"] + " and I work in the " + application.config["dept_name"] + " department. More Help topics “Using symbols in configuration files” on page 10 Configure or disable native bandwidth detection The server can detect a client’s bandwidth in the core server code (called native bandwidth detection).xml file. and you have defined a symbol named DEPT in the substitution. Native bandwidth detection is enabled and configured by default.5 CONFIGURATION AND ADMINISTRATION GUIDE 32 Configuring the server For example. the following trace() statements are valid: trace("I am " + application. the outermost edge server detects the bandwidth. trace("I am " + application.config. the following XML appears in the Application. The output from either statement would be as follows: I am jdoe and I work in the engineering department. if a client connects through edge servers."). the following trace statements are valid: trace("My computer's name is: " + application. trace("My department is: " + application. or in a serverside script (called script-based bandwidth detection).user_name + " and I work in the " + application. Native bandwidth detection is faster than script-based because the core server code is written in C and C++.xml file: <Root> <Symbols> <DEPT>Engineering</DEPT> </Symbols> </Root> In addition.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The output is as follows: My computer's name is: jsmith01 My department is: Engineering Note: Server-side ActionScript trace()statements display in the Live Log panel of the Administration Console. with native bandwidth detection.

Within the applications folder.ini file: • Registered applications folder: VHOST. By default. For example. <BandwidthDetection enabled="true"> <MaxRate>-1</MaxRate> <DataSize>16384</DataSize> <MaxWait>2</MaxWait> </BandwidthDetection> . For example. and the amount of time the server sends data to the client.APPSDIR .. 1 Locate the following code in the Application. Increasing this number provides a more accurate bandwidth figure. Configuring content storage Setting the location of application files The presence of an application folder within the applications folder tells the server that the application exists. The maximum rate in Kbps that the server sends data to the client. you can configure the size of the data chunks. 4 Restart the server.5 CONFIGURATION AND ADMINISTRATION GUIDE 33 Configuring the server The server detects bandwidth by sending a series of data chunks to the client. set the enabled attribute to false and restart the server. followed by 2x bytes. To detect the client’s bandwidth.xml file: .. . and so on until MaxWait time has elapsed. . If desired. edit the locations in the following parameters in the fms.xml file. 2 Edit the following elements. each time sending this much more data. The number of seconds the server sends data to the client. x bytes are sent. DataSize MaxWait 3 Save and validate the Application... Within each individual application folder. The default value is -1. the following path is to an instance of an application called “my_application”: RootInstall/applications/my_application/first_instance To change the location of the applications folder and the live and vod applications. each larger than the last. the rate at which they’re sent. create subfolders to create instances of applications. which sends the data at whatever rate is necessary to measure bandwidth. but it also forces the client to wait longer... Element BandwidthDetection MaxRate Description Set the enabled attribute to "true" or "false" to turn this feature on or off. see the Developer Guide. For more information about detecting bandwidth in an application. The amount of data in bytes that the server sends to the client. the applications folder is located at RootInstall/applications. followed by 3x bytes.Last updated 3/2/2010 FLASH MEDIA SERVER 3... the server attempts to send a series of random blocks of data to the client. create subfolders for your applications. Note: To disable native bandwidth detection.

you can set the storage directory to that other directory instead of copying content to the application directory.5 CONFIGURATION AND ADMINISTRATION GUIDE 34 Configuring the server • Live application: LIVE_DIR • Vod application: VOD_DIR Mapping directories to network drives By default. If the server is running as a service and the user is logged out. When you specify a value for the <storageDir> element in the application-specific XML. Use the StorageDir tag in the Application. use virtual directories. A Windows network-mapped drive is not valid when a user is logged out. Let’s say. all recorded streams for an application are stored in a streams folder in the application directory. when you specify a value in the virtual host-level Application. you must create physical subdirectories for different application instances. for example. 1 Stop Flash Media Server and Flash Media Administration Server. You can change the service user to a user with network access privileges with a UNC path. For example. . Flash Media Server sandboxes the content for each instance of an application. If you do not want resources to be sandboxed by application and application instance. Setting the location of recorded streams and shared objects By default.) 4 Restart Flash Media Server and Flash Media Administration Server. you set the storage directory to C:\Content for the chatApp application: <storageDir>C:\Content</storageDir> When a user connects to the firstRoom instance of the chatApp application and tries to play a stream.xml. To run with the mapped drive. the mapped drive is removed as well. 2 Make the changes to the configuration. lock the server instead of logging out. Within the directory that you specify as the storage directory. 3 Check that the server user has appropriate access rights to map to the network drive (system account rights are usually not sufficient. a user who connects to the secondRoom instance would not be able to access the content in C:\Content\firstRoom. the scope is extended to all the applications on that virtual host. Otherwise. Shared objects are stored in a shared objects folder in the application directory.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Using the UNC path is preferred when the server is running as a service. Note: Adobe strongly recommends that folders that store streams always contain only streams and no other application files. the server runs as System Account with no access to network drives. that value is specific to the application. You could do this for vod applications. Content for each instance is sandboxed from other instance of the same application.xml file to specify a different location to store streams or shared objects. if you already have a collection of video files in a directory other than the application directory. the server looks for the stream in a subfolder C:\Content\firstRoom.

xml file. .xml file. <VirtualDirectory> controls the storage location of all applications on that virtual host. When a name is specified. A connecting client will be able to play a file in the virtual directory. --> <Streams>/.xml file’s mapping of '/' (if it exists) for this application only.Specifies application specific virtual directory mapping for recorded streams. you configure the <VirtualDirectory> tag in Vhost. To map a directory in this way. Any instance of the application can access video files in that location (unlike with <storageDir>).xml file or the Vhost. although Adobe recommends that if you want control at the virtual host level.flv" to the source property of a call to FLVPlayback.play(). Virtual directory example: vod One usage scenario for this element is to specify a directory to use for a specific vod application and put video files in this directory to stream them instantly. • When specified in an application-specific Application. • When specified in the virtual-host Application.flv.xml file. by connecting to the vod application and issuing a NetStream play() call: ns. You would use the <VirtualDirectory> element in the application-specific Application. but other applications cannot. and you can retain your existing classification and categorization of resources.C:\my_videos</Streams> </VirtualDirectory> </StreamManager> </Application> This code overrides the VHost.5 CONFIGURATION AND ADMINISTRATION GUIDE 35 Configuring the server Mapping virtual directories to physical directories Flash Media Server stores recorded streams and video and audio files in default locations in the application directory. you can use the <VirtualDirectory> element in the Vhost. or by passing "rtmp://myDomain/VOD/sample. By mapping a virtual directory to a physical directory. • You can specify multiple physical directories for a single virtual directory.play("sample"). Use multiple <Streams> tags. you might want to specify particular locations for these resources. <VirtualDirectory> controls only the storage location of resources for that application. All applications on the virtual host can access video files in the specified location. but without restricting access by application or application instance. such as C:\my_videos\sample. edit the application-specific Application. you do not need to copy resources to Flash Media Server’s application directory. This element provides various options: • You can specify a virtual directory name or not. The order in which the server determines the correct directory to use for streams is as follows: 1 Virtual directory (as specified in <VirtualDirectory>) 2 Storage directory (as specified in <storageDir>) 3 Default location (the streams folder in the application directory) Note: Adobe strongly recommends that folders that store streams always contain only streams and no other application files.xml file instead of the virtual-host Application.xml file.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml or the Application. the server maps the name to the specified directory and first looks for the stream in the specified directory. To map a virtual directory for an application. as shown in the following example: <Application> <StreamManager> <VirtualDirectory> <!-.xml file. In some scenarios.xml file to include the virtual directory.

c:\low_bandwidth2</Streams> <Streams>high.flv file in the c:\high_bandwidth folder.flv file in the C:\low_bandwidth and C:\low_bandwidth2 folders. including mapping to a network drive. the server publishes the stream to the default streams directory. C:\low_bandwidth\sample. and you might want to store high-bandwidth and low-bandwidth video in separate folders.xml file. Note that if the client calls ns.play("high/sample") tells the server to look for the sample. You can create a mapping wherein all streams that start with low are stored in specific directories. Virtual directory example: Separating high.xml.play(”low/sample”). then the server looks in the default location (the streams folder) for the file. because the URI specified ("myStream") does not match the virtual directory name that is specified ("low"). .flv inside the directory specified by the storage directory element (<storageDir>). In the first case. the client calls ns. Similarly. It has a higher precedence than the virtual directory mapping in the Vhost. your application could allow users to view either high-bandwidth video or low-bandwidth video.play("sample"). and all streams that start with high are stored in a different directory: <VirtualDirectory> <Streams>low. the stream name does not match any virtual directory specified. protecting your streams from being accessed by other applications on the same virtual host. so it will always be checked first.5 CONFIGURATION AND ADMINISTRATION GUIDE 36 Configuring the server The <VirtualDirectory> element in the application-specific Application.c:\high_bandwidth</Streams> </VirtualDirectory> When the client wants to access low-bandwidth video. C:\low_bandwidth and C:\low_bandwidth2. For example.flv file in the low-bandwidth storage area on the server. ns.flv A client connects to the sample. and how the configurations determine the directory to which a recorded stream is published. If no storage directory is specified by <storageDir>. which is mapped in Application.Last updated 3/2/2010 FLASH MEDIA SERVER 3. a call to ns. the order in which the server looks for files is: 1 Virtual directory (as specified in <VirtualDirectory>) 2 Storage directory (as specified in <storageDir>) 3 Default location (the streams folder in the application directory) Virtual directory example: Local and network file paths The following table shows three examples of different virtual directory configurations. that is. so the server will then look for sample.play("low/sample").and low-bandwidth video One way you can use directory mapping is to separate storage of different kinds of resources. This call tells the server to look for the sample.c:\low_bandwidth</Streams> <Streams>low.xml file affects only that particular application.

2/conf folder. For more information. such as ASC • Handle any non-standard MIME types required for progressive download • Serve the default server-status and server-info pages • Modify source directories Enable Apache When you install Flash Media Server and choose to install Apache. edit the fms. Installation locations The Apache server that installs with Flash Media Server differs from a standard Apache installation in the following ways: • The apachectl files are in the RootInstall/Apache2. The Flash Media Server installation of Apache is like the standard installation. The Apache root installation folder is RootInstall/Apache2. and media assets from Flash Media Server. it is enabled by default. you can deliver client SWF files. The Apache documentation and configuration files use “ServerRoot” to indicate the Apache root installation folder. . • The httpd.\RootInstall\applications\yourApp\streams\_definst_\myStream.ini and Adaptor. Alternate configurations To do any of the following.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml files. you can serve video over HTTP progressive download as a fallback solution for web proxies that break RTMP or RTMPT. Note: The Flash Media Server documentation uses “RootInstall” to indicate the Flash Media Server root installation folder (C:\Program Files\Adobe\Flash Media Server 3. see “Monitoring and Managing Log Files” on page 55. • The log files are in the RootInstall/Apache2.2/conf/httpd..flv e:\fmsstreams\myStream.xml <VirtualDirectory><Streams> tag low. The web root is RootInstall/webroot.e:\fmsstreams low.flv Configuring Apache HTTP Server About Apache HTTP Server Flash Media Server 3. You can use Apache documentation for most configuration tasks.\\mynetworkDrive\share\fmsstreams URI in NetStream call Location of published stream "myStream" "low/myStream" "low/myStream" c:\.e:\fmsstreams low. container HTML pages.ini file in a text editor.5 includes Apache HTTP Server.5 by default on Windows). 1 Open the fms..2/logs folder. You can serve content over HTTP.2/manual/programs folder.conf file: • Handle multiple adaptors or virtual hosts • Block sensitive file types. as well as RTMP. In addition.flv \\mynetworkDrive\share\fmsstreams\myStream.conf file and the standard secondary configuration files are in the RootInstall/Apache2. edit the RootInstall/Apache2. To manually enable Apache.2. If you install and enable the web server.5 CONFIGURATION AND ADMINISTRATION GUIDE 37 Configuring the server Mapping in Vhost.

HOST = :8134 Setting the parameter to no value disables HTTP proxying: HTTPPROXY.com/app. HTML files. Place files that you want to deliver over HTTP in the correct folders. 5 Set the enable attribute of the HttpProxy tag to "true". 6 Save and validate the Adaptor.5 CONFIGURATION AND ADMINISTRATION GUIDE 38 Configuring the server 2 Add port 80 to the ADAPTOR.com/cgi-bin/someScript.HTTPD_ENABLED = true 4 Open the Adaptor. The following default configuration proxies port 80 HTTP requests to local port 8134: HTTPPROXY. set a value for the HTTPPROXY.HOST parameter. Apache is configured to use following paths: Path / /cgi-bin /local-cgi-bin Location RootInstall/Apache2.Last updated 3/2/2010 FLASH MEDIA SERVER 3.swf http://myFMSServer.ini file.pl http://myFMSServer.xml file. To allow Flash Media Server to serve media over HTTP when RTMPT is blocked. You can also specify the port to proxy to or proxy to a remote server. set the parameter to the remote server you want to use: HTTPPROXY.xml file is located in the RootInstall\conf\_defaultRoot_ folder.ini file. Configure HTTP proxying Flash Media Server uses port 80 for RTMPT connections. ADAPTOR.HTTPD_ENABLED parameter to true: SERVER.HOST = webfarm.2/local-cgi-bin Example URL http://myFMSServer. In the fms. open the file for the adaptor you want to configure.2/webroot RootInstall/Apache2.2/cgi-bin RootInstall/Apache2.HOST parameter. The default Adaptor. JPG files.HOSTPORT tag. Flash Media Server proxies HTTP connections to port 8134. By default.pl . as in the following: <HttpProxy enable="true" maxbuf="16384"> <Host port="80">${HTTPPROXY. HTTP connections by default use port 80.com/local-cgi-bin/someScript.HOST}</Host> </HttpProxy> Set the value of the HTTPPROXY. 80 3 To start and stop Apache when Flash Media Server starts and stops.ini file.example. you can enable or disable proxying through the HTTPPROXY. set the SERVER. If you have multiple adaptors. To enable HTTP proxying.HOSTPORT = :1935. Configure HTTP proxying in the RootInstall/conf/fms.com:80 Deliver SWF files and HTML files over HTTP Apache can deliver SWF files.HOST variable in the RootInstall/conf/fms. You can also remove the variable and set the value directly in the Host tag. and many other standard file types over HTTP. 7 Restart the server.xml configuration file in a text editor.HOST = To proxy to a remote server.

com/hd/someVideo. if a client requests the URL http://fms. on the other hand. Apache assumes any file you place in the RootInstall/Apache2.2. Apache attempts to execute the file RootInstall/Apache2. If you have a CGI program used by server-side ActionScript. The following keywords are reserved words: open.apache.example. To change the location of the cgi-bin or the local-cgi-bin.2/cgi-bin/someScript.deny Allow from all </Directory> Copy media files to the RootInstall/applications/hd/streams/_definst_/ folder to serve them over HTTP. are accessible only to Flash Media Server.2/local-cgi-bin Notes Accessible to anyone through an HTTP call.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Accessible only to Flash Media Server.org.pl.5 CONFIGURATION AND ADMINISTRATION GUIDE 39 Configuring the server These folders are global. To create a web directory for an application.2/cgi-bin RootInstall/Apache2.apache.2/conf/httpd. fcs. crossdomain. edit the httpd.flv. Deploying CGI programs By default.com/cgi-bin/someScript. not application-specific. use custom aliases to give the HTTP virtual directories slightly different names from the RTMP applications. For example. idle.example. either use one of the predefined web directories or create a web directory for that application. such as “open_”. Any SWF files and HTML files you want to serve over HTTP must be in these folders or in application-specific folders.flv file from the RootInstall/applications/hd/streams/_definst_/ folder. Using Apache as a WebDAV host You can configure the web server to act as a WebDAV host. place it in the local-cgi-bin folder. For example. For example. fpad.pl. close. Files in the local-cgi-bin folder.9 documentation at www. To create aliases for application-specific folders. see the Apache documentation at www.2/cgi-bin folder is a CGI program. Reserved words cannot be used for directory names under the webroot directory or for anything else.2/conf/httpd.org. Apache is configured with the following global aliases: Alias /cgi-bin/ /local-cgi-bin/ Path RootInstall/Apache2. Apache serves it the someVideo.conf file.conf file. . For information. the following lines create an alias that points to the streams directory of an application called “hd”: Alias /hd/ "applications/hd/streams/_definst_/" <Directory "applications/hd/streams/_definst_/"> Options Indexes MultiViews FollowSymLinks AllowOverride None Order allow. add an alias to the RootInstall/Apache2. edit the RootInstall/Apache2.conf file. Create web directories for applications To have Apache serve content over HTTP. fms. send. If you have applications with these names.xml. see the Apache HTTP Server version 2. For more information about editing the configuration file. if a client requests http://fms.

do one of the following: • Type localhost if the server and the Administration Console are running on the same computer. which connects to Adobe Flash Media Server. monitor applications.swf files to the Mac. select Start > Programs > Adobe > Flash Media Server 3. This name is an alias you can use to connect to a server quickly. do one of the following: • On Windows. Entering localhost connects you to the default virtual host on this computer. for example. Open the fms_adminConsole. If the Administration Server is installed on a port other than 1111 (the default). the fms_adminConsole. By default. 1 To open the Administration Console. 2 (Optional) Specify a server name. your session is specific to a virtual host.swf and fms_adminConsole. 3 In the Server Address box. You can change the port number of the Administration Server after installation by editing the fms.swf and fms_adminConsole.swf files in a browser with Flash Player. Application developers can also use the Administration Console to debug applications.htm and fms_adminConsole. When you log in to the Administration Console as a virtual host administrator. Connecting to the Administration Console About the Administration Console The Administration Console is an Adobe Flash Player application (fms_adminConsole. the Administration Server must be running. To log in to the Administration Console. • On Mac® OS. • On Linux. Server administrators have access to all applications running on the server. Connect to the Administration Console There are two types of administrators: server administrators and virtual host (vhost) administrators. The Administration Console remembers the server address for this server name the next time the console is opened. Use the Flash Media Server Administration API Reference to build your own administrative applications.htm files are located in the RootInstall/webroot folder.htm and fms_adminConsole. . The Administration Console connects to Adobe Flash Media Administration Server.ini file.htm files are located in the root installation folder.5 > Flash Media Administration Console. the fms_adminConsole. If you installed Apache with Flash Media Server. localhost:1234. copy the fms_adminConsole. Otherwise.Last updated 3/2/2010 40 Chapter 3: Using the Administration Console Use the Adobe Flash Media Server Administration Console to maintain the server. and manage users. open the fms_adminConsole. and you can only manage applications running on that virtual host. the Administration Server in installed on port 1111 (the default value at installation time).htm file in a web browser that has Flash Player installed. Note: The Administration Console calls Administration APIs to inspect and manage the server. you must enter the port number as well.swf) that lets you manage the server and view information about applications running on the server.

xml file allow the connection from the other computer’s IP address. Click the question mark icon to display links to Flash Media Server Help. Ensure your computer has permission to connect to the specified port on the other computer. you must specify the name of the adaptor. Change the refresh rate of the Administration Console ❖ Click the pop-up menu next to Refresh Rate (upper-right corner) and select a new time duration. Near the top of every screen of the Administration Console are two icons. verify that the Allow and Deny tags in the Users. In both cases.htm and fms_adminConsole. • If you are connecting remotely by running the Administration Console on another computer.Last updated 3/2/2010 FLASH MEDIA SERVER 3.ini file. enter the fully qualified host name (for example. scroll down.com) or the IP address and port number (12.34. 7 (Optional) Click Revert to return the Administration Console to its default settings.example.78:1112) of the Administration Server to which you want to connect. (The Revert button. Pause refreshing the Administration Console 1 Click the pop-up menu next to Refresh Rate (upper-right corner).myCompany. www. check that the Administration Server has not been configured to prohibit connections from the specific domain or IP address you are using. The username and password are stored in the RootInstall/conf/fms. For example. does not affect the server. Also. All custom resizing within the Administration Console is restored to the original state. Reverting deletes all saved servers. 4 Enter your username and password.5 CONFIGURATION AND ADMINISTRATION GUIDE 41 Using the Administration Console • To connect to a virtual host other than the default virtual host. or make sure that this file is in the webroot directory so it can be accessed remotely. such as 10 seconds.swf to the other computer. and passwords from the Administration Console. Otherwise. user names. 5 (Optional) Select the Remember My Password option. Change or pause the refresh rate The information in the Administration Console panels refreshes every 5 seconds by default.56. If you are the server administrator who installed the server. enter the username and password you received from the server administrator. The host name must be mapped to a valid network IP address. To run the Administration Console from a computer other than the one in which the server is installed. you can edit your local hosts file at windows\system32\drivers\etc\hosts. Note: The color of the vertical bar in the upper-right corner (next to the question mark icon) indicates whether the Administration Console is connected (green) or not connected (red) to a server. enter the server’s name (FlashMediaServer. . however. To test this behavior on Windows. To log in to a virtual host that is not on the default adaptor.) 8 Click Login. copy fms_adminConsole. You can change the refresh rate to any time interval between 1 and 60 seconds.com). the vhost administrator JLee would enter the following information in the Username box: _secondAdaptor_/JLee. Click the folder icon to display links to the Flash Media Server website and related resources. and select Pause. 6 (Optional) Select the Automatically Connect Me option. You can disconnect at any time by clicking Logoff. enter the administrator user name and password you entered during installation. when logging in to a virtual host on the adaptor _secondAdaptor_. or pause refreshing at any time.

3 Enter the administrator user name and password. 6 Select the application from the pop-up menu. Press Enter to submit the name and start the application instance. which can be edited.Last updated 3/2/2010 FLASH MEDIA SERVER 3. To cancel. Note: If you add an application while the Administration service is running and the new application doesn't appear in the Administration Console. or unload application instances. press Shift+Escape. (The application must already be configured on the server. From here. click the pop-up menu and select a time duration. load.5 CONFIGURATION AND ADMINISTRATION GUIDE 42 Using the Administration Console 2 Click Pause Refresh to continue.) 7 The Administration Console adds a default instance _definst_. the state of an application can be monitored. 3 To start refreshing information again. 4 Click View Applications. Manually load an application instance in the Administration Console 1 Follow the steps in “Connect to the Administration Console” on page 40. . 2 Enter the name and address of the server or virtual host to which you want to connect. 5 Click New Instance. the Administration Console displays a panel that lists the currently running application instances. move to another panel and then back to refresh the console. A red border appears around the panels of the Administration Console to show that the refresh feature is paused. Use the View Applications panel to view. Inspecting applications View applications After connecting to a server or virtual host.

(If the console refresh feature is paused. 2 Click View Applications. The information in this panel is updated whenever the application instance generates a log message. 1 Follow the steps in “Connect to the Administration Console” on page 40. all users are disconnected and all instance resources are released. 1 Follow the steps in “Connect to the Administration Console” on page 40. 2 Click View Applications.5 CONFIGURATION AND ADMINISTRATION GUIDE 43 Using the Administration Console Reload an application instance in the Administration Console Reload an application instance to reload the server-side scripts for the instance or to disconnect all of its users while immediately allowing new connections. 4 Click Reload (circular arrow icon to the right of the Performance tab). 3 Select an application from the list.Last updated 3/2/2010 FLASH MEDIA SERVER 3.) . 3 Select an application from the list. View information about an application 1 Follow the steps in “Connect to the Administration Console” on page 40. End an application instance When an application instance is ended. 2 Click View Applications. do one of the following: • Click the Name column header to sort the applications list by name. log messages are still received. 4 Click Unload (stop icon to the right of the Performance tab) Viewing log messages for an application The Administration Console Live Log panel displays log messages and trace() statements from server-side scripts for the selected application instance. such as total uptime or number of users Sort applications list 1 Follow the steps in “Connect to the Administration Console” on page 40. 3 In the applications list. • Click the Clients column header to sort by client. 2 Click View Applications. The following information is listed for the application on the different tabs: • Log messages generated by the application instance on the server • A list of clients connected to the application instance • A list of active shared objects for the application instance • A list of active streams for the application instance • Information about the overall state of the selected application instance. 3 Select the application from the list.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 44
Using the Administration Console

Live Log panel

1 Follow the steps in “Connect to the Administration Console” on page 40. 2 Click View Applications. 3 Click Live Log. 4 Select an application from the list. 5 Type text in the Find text box and click Find Next. Use the Find Previous and Clear Log buttons as necessary.

Viewing active streams
Use the Administration Console Streams panel to view information about streams and to play streams.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 45
Using the Administration Console

Streams panel

1 Follow the steps in “Connect to the Administration Console” on page 40. 2 Click View Applications. 3 Click Streams. 4 Select an application from the list. The Streams panel displays the following information:

• Name: For NetStream streams, the name is the NetStream ID (a server-generated number). For a live stream
being published, the entry displays the live stream name. For a recorded steam, the entry displays the FLV or MP3 filename; for example, flv:stream2.flv or mp3:sound.mp3. If a client requests the stream2.flv, there will be two entries: one for flv:stream2.flv (stored) and one for the actual network stream going to the client.

• Type: A string that describes the type of stream, either stored, live, or NetStream.
5 Select a stream to view its properties. The values of the properties are as follows:

• Name: The actual stream name, not streamID. • Status: States if the stream is publishing, playing live, or playing recorded. • Client: The client ID playing the stream. • Time: The time that the client started playing the stream.
Note: If the stream type is available for debugging, the Administration Console displays its properties in the adjoining panel. If the type is not available for debugging, an error message is displayed.
6 Click Play Stream to start playing the selected stream in a separate window that is the size of the selected stream.

(The Play Stream button appears only if a debug connection is possible. Only named streams can be played.)

Viewing active clients
The Administration Console Clients panel lists detailed information about all clients connected to an application.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 46
Using the Administration Console

Clients panel

1 Follow the steps in “Connect to the Administration Console” on page 40. 2 Click View Applications. 3 Click Clients. 4 Select an application from the list. The following information is displayed:

• Client ID: The internal ID of the client; this represents a server-generated number that Flash Media Server uses
to identify each client.

• Protocol: The connection protocol that the client uses, such as RTMP. • Bytes In and Bytes Out: The average bytes per second being sent to and from the server. The Administration
Console calculates this ratio by dividing the total number of bytes received in the most recent 15 seconds by 15. When the panel first appears, these figures appear as pending because there is only one data point to start with; figures appear after the panel is open for 15 seconds.

• Connection Time: The date and time the client connected. • Messages In and Messages Out: The number of messages sent to or from the client. Messages In reflects update
requests sent from clients to the server; Messages Out reflects notification of successful updates sent from the server to connected clients.

• Drops: The number of messages dropped since the client connected. For live streams, audio, and video,
messages may be dropped; for recorded streams, only video messages are dropped. Command messages are never dropped.

Viewing active shared objects
The Administration Console Shared Objects panel lists the active shared objects for an application and can be useful when debugging an application. The information is automatically refreshed every 5 seconds, or click Refresh to refresh at any time. The Administration Console displays the name, type (persistent or temporary), and connections (number of users subscribed) of each shared object.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 47
Using the Administration Console

Shared Objects panel

Note: The Administration Console was built using ActionScript 2.0 and cannot understand AMF3 data. Therefore, the Administration Console cannot display data in remote shared objects in applications built in ActionScript 3.0 unless the application sets the NetConnection.objectEncoding property to AMF0.
1 Follow the steps in “Connect to the Administration Console” on page 40. 2 Click View Applications. 3 Click Shared Objects. 4 Select an application from the list. 5 To display information about a shared object, click the object. The number of users currently connected to and

using the shared object is displayed, along with the data properties assigned to the shared object.

View performance information
The Administration Console Performance panel shows information about the overall state of the application instance. The information is automatically refreshed every 5 seconds, or click Refresh to refresh at any time.

. including data sent. • Bandwidth: The amount of data that the application instance manages. and the combined amount of data traffic.) • Lifespan: The length of time the application instance has been running and the date and time it began to run.5 CONFIGURATION AND ADMINISTRATION GUIDE 48 Using the Administration Console Performance panel 1 Follow the steps in “Connect to the Administration Console” on page 40. For example.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 3 Click Performance. active clients. • CPU and Memory Usage: The percentage of CPU and memory used by Flash Media Server. 4 Select an application from the list. • Bytes Per Second: The average number of bytes sent per second for this application instance. these figures appear as pending because there is only one data point to start with. (To determine why connections may have failed. The Administration Console calculates this ratio by determining the total number of bytes received in the most recent 15 seconds and dividing that value by 15. 5 Select and deselect checkboxes to customize the information displayed on the graphs. including the total number of clients who connected to the application instance since it started. and command messages) sent per second. look at the Live Log panel under View Applications. 2 Click View Applications. When the panel first appears. select Total and deselect In and Out to show only the total amount of bandwidth used. and the number of users whose attempts to connect to the application instance were rejected. figures appear after the panel is open for 15 seconds. • Messages Per Second: The average number of messages (video frames. The following information is displayed: • Clients: Information about clients connected to this application instance. audio packets. data received. in the Bandwidth graph. • Active Connections: The number of users currently connected to the application instance.

xml file.xml file.Deny</Order> </User> <User name="janedoe"> <Password encrypt="false">S4mpl3P4ss</Password> <Allow></Allow> <Deny></Deny> <Order>Allow. The Administration Console adds the new user and password to the Users. Virtual host administrators can manage the applications on their virtual host—for example. Edit the Users.xml file. and Order elements specify the hosts from which the administrator can connect to the Administration Console. 2 Locate the UserList section. .Deny</Order> </User> </UserList> For more information. The Allow. 3 Add a new <User></User> section for each server administrator you want to add. The User name attribute specifies the user name.ADMIN_USERNAME}"> <Password encrypt="false">${SERVER. The Password element specifies the password. 3 Click New User. such as restarting or shutting down the server. Virtual host administrators can access and perform operations on the View Applications tabs.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Server administrators can control all virtual hosts and perform server-level tasks. 4 Enter the user name and password and click Save.xml file to add server administrators 1 Open the RootInstall/conf/Users. Server administrators can access and perform all operations on all tabs. The following sample XML adds a user who can connect from any domain: <UserList> <User name="${SERVER. they can reload or disconnect applications. There are two types of administrators: server administrators and virtual host administrators. Deny. see the comments in the Users. 2 Select the Manage Users tab. 1 Log in to the Administration Console as a server administrator.5 CONFIGURATION AND ADMINISTRATION GUIDE 49 Using the Administration Console Manage administrators About administrator roles Administrators are users who are allowed to log in to the Administration Console. They cannot manage servers or administrative users.ADMIN_PASSWORD}</Password> <Allow></Allow> <Deny></Deny> <Order>Allow. Add administrators Use the Administration Console to add server administrators Note: You must be a server administrator (not a virtual host administrator) to access the Manage Users tab. You do not need to restart either server.

Delete administrator accounts and reset passwords You must be a server administrator (not a virtual host administrator) to perform operations on the Manage Users tab. If the file doesn’t exist. 2 Click Manage Users.Last updated 3/2/2010 FLASH MEDIA SERVER 3. for example. 5 Confirm the action. copy the Users. RootInstall/conf/_defaultRoot_/www.ADMIN_PASSWORD}</Password> <Allow></Allow> <Deny></Deny> <Order>Allow. Delete user account 1 Log in to the Administration Console as a server administrator.ADMIN_USERNAME}"> <Password encrypt="false">${SERVER. The Allow. The following sample XML adds a user who can connect from any domain: <UserList> <User name="${SERVER. The User name attribute specifies the user name.xml file in the root folder of the virtual host. 3 Add a new <User></User> section for each virtual host administrator you want to add. 4 Click Delete This User Account On The Server. .xml file from the RootInstall/conf folder. 3 Select a user. Reset user password 1 Log in to the Administration Console as a server administrator. Deny. see the comments in the Users. 3 Select a user.xml file.xml file.xml. The Password element specifies the password.sampleVhost.Deny</Order> </User> <User name="vHostAdmin"> <Password encrypt="false">Ex4mpl3P4ss</Password> <Allow></Allow> <Deny></Deny> <Order>Allow. 5 Type a new password.xml file. 4 Validate the XML and save the Users. and Order elements specify the hosts from which the administrator can connect to the Administration Console.5 CONFIGURATION AND ADMINISTRATION GUIDE 50 Using the Administration Console 4 Validate the XML and save the Users.Deny</Order> </User> </UserList> For more information. 2 Locate the UserList section.com/Users. 2 Click Manage Users. Add virtual host administrators 1 Open the Users. 4 Click Reset The Password For This User.

• Ping the server to verify that it is running. • Review the access log and server log. • Delete a server from the list.Last updated 3/2/2010 FLASH MEDIA SERVER 3. • Connect to the selected server. • Review information about connections to the server. you can perform the following actions: • Review the performance statistics for the computer where the applications are running. From here. • Edit server login information (user name and password) and select options such as remembering the password and automatically connecting when logging in to the server. The servers are arranged in a tree structure. A series of tabs is displayed along the top of the Manage Servers panel. if necessary.5 CONFIGURATION AND ADMINISTRATION GUIDE 51 Using the Administration Console Managing the server Monitoring server performance You can review the performance of individual servers or a group of servers using the Administration Console. . • Review information about the applications located on the server or virtual hosts. Manage Servers panel Use the small buttons at the top and bottom of the panel to perform the following tasks: • Add a new server to the list. add serial keys. • Review server licenses and. The panel lists the servers and virtual hosts that you can access and manage. The Servers panel occupies the left side of the screen in this section of the Administration Console.

1 Follow the steps in “Connect to the Administration Console” on page 40. from memory. 4 Select a server from the list. The following information is displayed: • Total number of current clients • Life span of the server • Graphical displays of active connections. 2 Click Manage Servers.xml configuration files. and CPU and memory resources consumed Viewing connection details The Administration Console Connections panel lists all client connections to the selected server. 1 Follow the steps in “Connect to the Administration Console” on page 40. The following information is displayed for each client accessing the server or virtual host: • Server name • If connection has been made • Number of connections • Number of disconnections • Number of bytes in and out • Number of messages dropped Viewing application details The Administration Console Applications panel displays detailed information for all the applications running on the selected server or virtual host. 2 Click Manage Servers.5 CONFIGURATION AND ADMINISTRATION GUIDE 52 Using the Administration Console • Restart the server or a virtual host. 3 Click Details. • Run garbage collection to clear unused server resources. bandwidth resources consumed. 3 Click Connections. 4 Select a server from the list. 3 Click Applications.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 1 Follow the steps in “Connect to the Administration Console” on page 40.) • Stop a server or virtual host.xml and VHost. . 2 Click Manage Servers. Viewing server details The Administration Console Details panel displays live information for the server. such as streams and application instances. (Automatic garbage collection intervals can be set in the Server.

4 Enter the serial key number in the text boxes at the bottom of the Administration Console. Add a serial key Add serial keys in the Administration Console License panel. the following information is displayed: • The individual serial key number • Authorized peak number of client connections • Bandwidth cap • Whether the license is valid (true) or not (false) Note: Your organization may have more than one license. so note the capacity totals listed near the bottom of the Administration Console. 2 Click Manage Servers. 6 Restart the server. along with the following information. The lower frame displays information about custom licenses. 4 Select a server from the list. 5 Click Add Serial Key. 3 Click License. For each license.xml file cannot be removed using the Administration Console.Last updated 3/2/2010 FLASH MEDIA SERVER 3. is displayed: • Server name • Application name • Number of instances of the application that have been loaded on and unloaded from the server • Number of users that are connected • Number of users that have connected and disconnected • Number of instances currently active • Number of instances that have been unloaded from the server • Total number of connections that have been accepted or rejected for each application Viewing license files The Administration Console License panel is where you add serial keys. 3 Click License. The name of each application. 2 Click Manage Servers.5 CONFIGURATION AND ADMINISTRATION GUIDE 53 Using the Administration Console 4 Select a server from the list.ini or the <LicenseInfo> tag of the Server. 1 Follow the steps in “Connect to the Administration Console” on page 40. Note: Serial numbers that are added manually (that is. . 1 Follow the steps in “Connect to the Administration Console” on page 40. The panel also displays detailed information for all serial keys authorizing you to run Flash Media Server on the selected server. added by editing configuration files directly) to either fms. Only serial numbers that are added using the Administration Console can be deleted using the Administration Console.

2 Click Manage Servers.5 CONFIGURATION AND ADMINISTRATION GUIDE 54 Using the Administration Console View the access log file The Administration Console Server Log panel displays messages that are written to the access log. . type it in the Find text box and click Find Next.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 1 Follow the steps in “Connect to the Administration Console” on page 40. 3 Click Server Log. 4 Select a server from the list. 5 To locate a specific string. Use the Find Previous and Clear Log buttons as necessary.

application. Administrators can use standard parsing tools to parse the log files.xml files. edit the RootInstall/Apache2. The log files track server activity. Working with web server log files Flash Media Server installs with the Apache HTTP Server. If the Scope tag is set to server. access.Last updated 3/2/2010 55 Chapter 4: Monitoring and Managing Log Files Adobe Flash Media Server has a variety of log files to help you manage and troubleshoot the server. The default location of the Apache log files is RootInstall/Apache2.xml file doesn’t exist. Logs are in W3C format. the Logger.XX. For more information. Working with log files About log files The server maintains several different types of logs. The server outputs statistics about client connections and stream activity to access logs.xml file in the RootInstall/conf folder determines the logging configuration for the whole server. The logs are in the default Apache error and combined access log formats.xml files in virtual host root folders to control the behavior of each virtual host.xml files are ignored.2/logs. diagnostic logs Track information about server operations.log Tracks information about users accessing the server. see comments in the Server. For more information about Apache log files. The Logging section also contains a Scope tag that determines whether the server writes separate log files for each virtual host or one file for the entire server.xml configuration files to configure logging. To change the location of the log files.xml and Logger.org. Note: In Adobe Flash Player 9 Update 3.conf file. If the Scope tag is set to vhost and a virtual host Logger. The server also maintains diagnostic logs and application logs for application activities.log Tracks information about activities in application instances. and general diagnostics. Configuration files for logging Use the Server.xml file contains a Logging section that controls logging behavior for the entire server.xml file controls the logging behavior. Flash Player no longer notifies the server about pause events. If the Scope tag is set to server. virtual host Logger.xml and Logger. such as who is accessing the server. The Logging section includes an Enable tag that determines whether the server logs events. how users are working with applications. The location of each log file is determined by the Directory and FileName tags in the Logger.apache.xml files installed in the RootInstall/conf directory. you can place Logger. see the Apache documentation at www.XX.2/conf/httpd. Flash Media Server handles log rotation for the Apache logs. . The Server. The Apache logs are named access_log and error_log. If the Scope tag is set to vhost. the root Logger.

For important log files. One option is to rotate log files. and that the Flash Media Server host has dual addresses and is listening on both interfaces. you need to activate IPv6 on the network interface card. only the two /v6 entries would be displayed. Flash Media Server (when it starts) logs available stack configuration. However.xml configuration files. Alternatively. The following x-comment fields from a sample edge log file indicate that the IPv6 stack and the IPv4 stack are available. You can move the current active file. see “Configuration files for logging” on page 55. host name.42 IPv6: fe80::204:23ff:fe14:da1c%4 Listener started ( _defaultRoot__? ) : 19350/v6 Listener started ( _defaultRoot__? ) : 19350/v4 Listener started ( _defaultRoot__? ) : 1935/v6 Listener started ( _defaultRoot__? ) : 1935/v4 Note: In Red Hat Linux.xx.xml configuration files that effectively turn off rotation. see the Logger. FMS detected IPv6 protocol stack! FMS config <NetworkingIPv6 enable=true> FMS running in IPv6 protocol stack mode! Host: fmsqewin2k3-02 IPv4: 10. edge. but there are methods for managing log file size. . Verifying IPv6 in log files IPv6 (Internet Protocol version 6) is a new version of the Internet Protocol that supports 128-bit addresses. and admin. the edge logs display only the highest IP version the socket listeners are using. see “Configuring IPv6” on page 30. For more information about using IPv6.xx. moving or deleting the oldest files. To use IPv6.Last updated 3/2/2010 FLASH MEDIA SERVER 3. and enclose numeric IPv6 addresses in URLs within brackets. move the log directory to a backup location. even if the socket listeners accept connections over both IPv4 and IPv6.log.xx. The first option is to set a daily rotation at a certain time. and all available IP addresses for the host in the master.192. You can write an operating system script to delete or back up the log regularly.log.xml file installed in the /conf directory. maximum file size in kilobytes. enable Flash Media Server to listen on IPv6 sockets. Two types of rotation schedules can be established. Name. For more information about the Logger. the server creates a new file on the next log event. setting daily at 00:00 rotates files every 24 hours at midnight. Note: Log file rotation cannot be disabled.log files. For example.133. and maximum number of log files to keep can also be customized using the rotation element. After following those steps.xml file to specify a rotation schedule for log files.5 CONFIGURATION AND ADMINISTRATION GUIDE 56 Monitoring and Managing Log Files Rotating and backing up log files Log files grow larger over time. Use the rotation element in the Logger. For an example. Choose a large value for the MaxSize tag. you can set values in the Logger. set a rotation that occurs when the log exceeds a specified length. Set the Schedule type to "duration" and choose a long maximum duration. In the example above. in Linux.

A checkpoint event that provides updates of a corresponding publish event at intervals. To solve this problem. If your programming includes live events or 24/7 programming. how much total bandwidth was consumed during the session. date. Client plays a stream. You can configure how often the server logs checkpoint events. MM. and publish-continue.” (This is a separate scope tag just for logging. Client connects to the server. play-continue. respectively. Substitution strings can be found in the [] brackets.5 CONFIGURATION AND ADMINISTRATION GUIDE 57 Monitoring and Managing Log Files Access logs Reading access logs The access log records information about requests by Flash Player and Flash Media Server application instances. You can use the substitution string to customize the filename of the access log. such as when a user connected to the server. The following are available as checkpoint events: connectcontinue. You can use the status codes associated with specific events to troubleshoot event failures. Using these logs. When logging is configured on a per-virtual-host basis. with YYYY. Checkpoint events log bytes periodically from the start to the end of an event. access.xml file to “vhost. you can find out about various events.2007052401. and which streams were accessed by the connection (and similar resource information).log. You can also use this information to determine which applications are used most. Client publishes a live stream. Client unpublishes a live stream. The default configuration creates a single access log per server. Client disconnects. Logging can be customized to record all events or only specific events by editing the <Events> and <Fields> elements in the Logger. disconnect publish unpublish publish-continue session stream stream stream play stream . Use the c-client-id field to find the corresponding connect event. month. all logs for a particular virtual host are found in a subdirectory within the logs directory.) To configure the server to create separate log files for each virtual host. see “Enable checkpoint logging events” on page 29. and for each category.[YYYYMMDDNN]. Logging events periodically for live and 24/7 applications Many companies use statistics from the access log to bill customers. For information about configuring checkpoint events. it defines events that can be recorded.log. A checkpoint event that provides updates of a corresponding connect event at intervals. and NN representing year. and version.xml file. the events you need to calculate billing might not occur within a billing cycle. waiting for the client to be authenticated.Last updated 3/2/2010 FLASH MEDIA SERVER 3. you can enable checkpoint events.) Flash Media Server defines event categories. Use the x-sid field (stream id) and the c-client-id field to find the corresponding publish event. (For example. Access events defined in access logs Event connect-pending connect connect-continue Category session session session Description Client connects to the server.xx. The default access log is access. DD. which is located in the RootInstall/logs directory.log could be named access. The name of the subdirectory matches the virtual host name. set the value of the Scope tag in the Server. You can also configure the server to create a separate file per virtual host.

Use the x-sid field (stream id) with the c-client-id field to find the corresponding play event. This event occurs if an Authorization plug-in is present to handle the event.0. Server has started. This event occurs if an Authorization plug-in is present to handle the event. This event occurs if an Authorization plug-in is present to handle the event. If a client seeks outside the buffer.0 and Flash Media Server 3 and later. Smart pause requires Flash Player 9. Client stops playing or publishing a stream. This event occurs if an Authorization plug-in is present to handle the event.5 CONFIGURATION AND ADMINISTRATION GUIDE 58 Monitoring and Managing Log Files Event play-continue Category stream Description A checkpoint event that provides updates of a corresponding play event at intervals. An application instance has stopped. A virtual host has started.inBufferSeek=false. The server received a “startTransmit” command. the client sends a “seek” event. Client publishes a live stream. The seek position when the client seeks within the buffer when NetStream. Client jumps to a new location within a recorded stream. Client resumes playing stream. Also fires when NetStream.inBufferSeek=true and the client seeks outside the buffer.inBufferSeek=true (called a “smart seek”). A virtual host has stopped An application instance has started. Client seeks in a stream and NetStream. Client pauses a stream but the server still sends data to the client so the player has enough data to play when the client unpauses. Client begins recording a stream. Client stops recording a stream. Client pauses stream. The stream position is logged in the “cspos” field. pause unpause client-pause stream stream stream client-unpause seek stream stream client-seek stream stop record recordstop start-transmit stream stream stream stream stop-transmit stream server-start server-stop vhost-start vhost-stop app-start app-stop auth-connect server server vhost vhost application application authorization auth-play authorization auth-publish authorization auth-seek authorization . This command asks the server to transmit more data because the buffer is running low. The stream position is logged in the “c-spos” field. The stream position is logged in the “c-spos” field.115. Client connects to server. This command asks the server to suspend transmission until the client sends a “startTransmit” event because there is enough data in the buffer. Client smart unpauses a stream. Client plays a stream.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Server has stopped. The server received a “stopTransmit” command. This type of pause is called a “smart pause”.

For a complete description of the x-status codes and descriptions. This event occurs if an Authorization plug-in is present to handle the event. Adaptor name. Client IP address. Logs data to the “x-codec-type” and “x-codec” fields. The publisher codec changes during a live event. c-referrer. This event occurs if an Authorization plug-in is present to handle the event.” or “Pacific Standard Time” Field x-event x-category date time tz x-ctx s-ip x-pid x-cpu-load x-mem-load x-adaptor x-vhost x-app x-appinst x-duration Description Type of event. c-user-agent. but are present for better parsing of the data. Date of the event. sc-bytes. Time zone information. The following formats apply to the fields in the table below: For date: YYYY-MM-DD For time: hh:mm:ss For time zone: string such as “UTC. For a stream. x-adaptor.5 CONFIGURATION AND ADMINISTRATION GUIDE 59 Monitoring and Managing Log Files Event filenametransform Category authorization Description A virtual stream path has been mapped to a physical location. Virtual host name. x-status c-ip . see “Fields in diagnostic logs” on page 64. This event occurs if an Authorization plug-in is present to handle the event. This applies to the tz. x-vhost. the data is wrapped in double quotation marks. CPU load. this value is the number of seconds the client has been connected. Duration of a stream or session event. and xsname fields. Time the event occurred. s-uri. Event-dependent context information. The double quotation marks surrounding the data are not part of the data. Memory usage (as reported by the getServerStats() method). Event category. Client begins recording a stream. Application instance name. auth-record authorization codecchange authorization Fields in access logs Note: When the data for this field contains a space or delimiter.Last updated 3/2/2010 FLASH MEDIA SERVER 3. IP address or addresses of the server. Application names. this value is the number of seconds the stream has played. cs-bytes. For a session.” “Pacific Daylight Time. x-ctx. Server process ID.

in bytes. User agent. Stream type (FLV. subtract sc-bytes in the “connect” event by sc-bytes in the “disconnect” event c-connect-type Type of connection received by the server: Normal: Connection from a client. The stem portion of the s-uri field. in seconds. This field shows the number of bytes transferred from the client to the server per stream. URI of the Flash Media Server application. This is a composite field: cs-uri-stem + x-sname + x-file-ext. The value of sc-stream-bytes can be greater than x-file-size after streaming files not encoded in FLV format. sc-stream-bytes This field shows the number of bytes transferred from the server to the client per stream. Full path of the file representing the x-sname stream. The query portion of s-uri. Client ID. Note: The value of sc-stream-bytes is not necessarily the same as the value of the QoS ByteCount property. To calculate the bandwidth usage per stream. MP3. URI of the referrer. Query portion of the stream URI specified in play or publish. in milliseconds. Same as x-sname-query. This information can be used to bill customers per session. This information can be used to bill customers per session. x-service-name Name of the service providing the connection (only applicable to certain connection types). To calculate the bandwidth usage per session.5 CONFIGURATION AND ADMINISTRATION GUIDE 60 Monitoring and Managing Log Files Field c-proto s-uri cs-uri-stem cs-uri-query c-referrer c-user-agent c-client-id cs-bytes Description Connection protocol. This is a composite field: cs-uri-stem + x-sname + x-file-ext + x-sname-query. This field shows the number of bytes transferred from the client to the server. such as MP3 files. Stream length. subtract cs-stream-bytes in the “publish” event from csstream-bytes in the “unpublish” event. such as Flash Player Group: Connection between an edge and an origin server Virtual: Client connection that goes through an edge server. subtract cs-bytes in the “connect” event from cs-bytes in the “disconnect” event. To calculate the bandwidth usage per session. using the group connection between the servers for transmission x-sname x-sname-query x-suri-query x-suri-stem x-suri x-file-name x-file-ext x-file-size x-file-length x-spos cs-stream-bytes Stream name. or MP4). subtract sc-stream-bytes in the “play” event from sc-stream-bytes in the “stop” event. Stream size. Stream position.Last updated 3/2/2010 FLASH MEDIA SERVER 3. sc-bytes This field shows the number of bytes transferred from the server to the client. . To calculate the bandwidth usage per stream.

The file extension portion of the stream name for the stream that the server transitions from. This ID is unique for the client session but not across sessions. Field connect pending disconnect disconnect Symbol status_continue status_admin_command status_shutdown Status Code 100 102 103 Description Waiting for the application to authenticate.5 CONFIGURATION AND ADMINISTRATION GUIDE 61 Monitoring and Managing Log Files Field x-sc-qos-bytes x-comment x-sid x-trans-sname x-trans-sname-query x-trans-file-ext x-plugin x-page-url x-smax-rec-size x-smax-rec-duration x-trans-mode x-offset c-spos x-eid Description Number of bytes sent to the client for quality of service. The transition mode sent by the client in the NetStream. Client disconnected due to admin command.log file. An event ID received by Authorization plug-in. unpublish. The query stream portion of the stream name for the stream that the server transitions from. Client disconnected due to server shutdown (or application unloaded). This field is only available in authorization (auth-) events. x-codec-type x-codec Event status codes in access logs The Event status codes are based on HTTP response codes. invalid parameter or client connected to server using an unknown protocol. Comments. This event is visible only in the auth.Last updated 3/2/2010 FLASH MEDIA SERVER 3.log file.play2() call. The URL of the web page in which the client SWF file is embedded. the offset value indicates where to resume streaming.log file. connect. connect. stop connect connect. This field is empty in the access. Connection rejected by Authorization plug-in or connection rejected due to invalid URI. play. The maximum file size of a recorded stream. The name of the stream that the server transitions from (the original stream). The maximum duration of a recorded stream. status_OK record. publish status_unauthorized 401 connect status_forbidden 403 . publish. This event is visible only in the auth. The ID of a stream. Connection rejected by application script or access denied by application. This field is empty in the access. Bad request. record stop. Application currently unavailable. This field is empty in the access.log file.log file. When a stream is reconnected. stop play. The client stream position when a “client-pause” or “client-seek” event is logged. play status_transition status_unavailable status_bad_request 200 210 302 400 A transition between streams has occurred. Name of the plug-in. Codec value of the “x-codec-type” retrieved in the Authorization plug-in’s E_CODEC_CHANGE event. publish. play. Codec type of the frame retrieved in the Authorization plug-in’s E_CODEC event.log file. This event is visible only in the auth. Successful.

Error handling message. License limit exceeded. SWF verification failure. publish disconnect connect disconnect disconnect disconnect connect status_lic_limit_exceeded unsupported_type data_exceeded chunkstream_error cannot_broadcast cannot_screenshare remote_link_closed process_msg_failed 413 415 416 417 418 419 420 422 disconnect disconnect process_msg_exception process_remote_msg_failed 423 424 disconnect process_admin_msg_failed 425 disconnect process_rtmp_S2S_msg_failed 426 disconnect write_error 427 disconnect invalid_session 428 disconnect gc_client 429 disconnect disconnect remote_onstop remote_on_client_disconnect 430 431 disconnect gc_idle_client 432 disconnect disconnect disconnect swf_hash_fail swf_hash_timeout encoding_mismatch_error 433 434 435 disconnect. Client disconnected due to incompatibility with object encoding. publish Symbol object_not_found client_disconnect status_conflict Status Code 404 408 409 Description Application or stream not found. License to receive screen sharing video failed. Client does not have privilege to broadcast. Upstream connection closed. Client connection invalid. Can also mean that a change has been made by the Authorization plug-in. Upstream connection closed because the last client disconnected. Bad gateway. Unable to process unknown data type. Unsupported media type. Stream stopped because client disconnected. Unable to obtain ping response or client states not connected. Flash Media Server autoclose feature automatically closed the connection. Close downstream connection.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Server internal error. closed due to inactive or idle status. play play connect. unable to write data. Expected response not provided when command was issued. disconnect the client. play connect server_internal_error bad_gateway 500 502 . Unable to process message received when client connection was in pending or closed state. Client is not connected or client terminated. SWF verification timeout.5 CONFIGURATION AND ADMINISTRATION GUIDE 62 Monitoring and Managing Log Files Field connect. Message queue too large. Expected response not provided when issued an admin command. Expected response not provided when command issued. connect play. Resource limit exceeded or stream is already being published.

. by default. The application folder is located in the matching virtual host directory. Bad application data. located in the subdirectory within the Flash Media Server logs directory. The “xx” in the filename is a two-digit number representing the history of the application log. for instance.5 CONFIGURATION AND ADMINISTRATION GUIDE 63 Monitoring and Managing Log Files Field connect Symbol service_unavailable Status Code 503 Description Service unavailable.00. disconnect disconnect disconnect js_disconnect js_close_previous_client js_exception 600 601 602 disconnect disconnect play js_chunkstream_error js_debug_forbidden js_gc_object 603 604 605 Application logs Application log file The application log records information about activities in application instances. Time of the event. to create one application log per application instance. ~fcstreamjshook() clean up. Application disconnect. Application does not allow debug connections. The default application log is application. The most recent logs can be found in application. Fields in application logs Field date time Event(s) All All Description Date of the event.xx. Flash Media Server is configured.Last updated 3/2/2010 FLASH MEDIA SERVER 3. An unknown exception is thrown from the JS engine.log.log. Network connection was closed or reused. This log is used primarily for debugging (logging uncommon events that occur in an application instance). too many connections pending for authorization by access module.

Time at which event occurred.log.xx. edge. For a list of messages that appear in the diagnostic log files. to create a diagnostic log for each type of process. by default. Flash Media Server is configured. The “xx” in the filename is a two-digit number representing the version of the log. This log is used primarily for debugging (logging uncommon events that occur in Flash Media Server processes). and httpcache.log. admin. The last four characters represent message ID. as follows: (w) = warning (e) = error (i) = information (d) = debug (s) = trace from server-side script (_) = unknown The next three characters represent category. The default diagnostic logs are master. All message IDs are listed in “Diagnostic Log Messages” on page 196. The first three characters represent severity. Diagnostic logs Diagnostic log file The diagnostic log records information about Flash Media Server operations (this is in addition to the information logged by the operating system).xx. All the diagnostic logs are located in the Flash Media Server logs directory. . Fields in diagnostic logs Field date time Event(s) All All Description Date on which the event occurred.Last updated 3/2/2010 FLASH MEDIA SERVER 3. see “Diagnostic Log Messages” on page 196. All categories are listed in “Status categories in diagnostic logs” on page 65. Status code: The code is a 10-character string that represents the severity.xx. category.log.xx.log. x-ctx All Event-dependent context information.log. core.xx.5 CONFIGURATION AND ADMINISTRATION GUIDE 64 Monitoring and Managing Log Files Field x-pid x-status Event(s) All All Description Server process ID. and message ID.

Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 65 Monitoring and Managing Log Files Field x-pid x-status Event(s) All All Description Server process ID. All message IDs are listed in “Diagnostic Log Messages” on page 196. x-stx All Event-dependent context information. and message ID. category. The first three characters represent severity. The last four characters represent message ID. as follows: (w) = warning (e) = error (i) = information (d) = debug (s) = trace from server-side script (_) = unknown The next three characters represent category. Status categories in diagnostic logs Category 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 Description TCService TCServer Presence Storage Stream SMTP Adaptor JavaScript TCApplication TCConnector Admin SharedObject Configuration VirtualHost SSL . All categories are listed in “Status categories in diagnostic logs” on page 65. Status code: The code is a 10-character string that represents the severity.

Start the server from the Start menu ❖ Do one of the following: • Choose Start > All Programs > Adobe > Flash Media Server 3. 2 Do one of the following: • Select Flash Media Server (FMS) from the Services list and click Stop. stop. or Restart. or restart the Administration Server 1 Log in as a root user. stop. Start and stop the server Start and stop the server in Windows Use one of the following methods to shut down or restart the server. 3 Open a shell window and type one of the following: • • • . .5 > Stop Flash Media Administration Server 3.5 > Start Flash Media Server 3. or restart Flash Media Server 1 Log in as a root user. Start./fmsmgr server start . stop.5 > Start Flash Media Administration Server 3./fmsmgr server stop . or Restart. Start and stop the server in Linux Start. or restart the server from the Services window 1 Choose Start > Control Panel > Administrative Tools > Services.5 • Choose Start > All Programs > Adobe > Flash Media Server 3. Start. 2 Change to the directory where the server is installed. • Select Flash Media Administration Server from the Services list and click Stop.5 Stop the server from the Start menu ❖ Do one of the following: • Choose Start > All Programs > Adobe > Flash Media Server 3.5 Start.5 > Stop Flash Media Server 3.5 • Choose Start > All Programs > Adobe > Flash Media Server 3.Last updated 3/2/2010 66 Chapter 5: Administering the server Perform regular administrative tasks to keep the server running smoothly./fmsmgr server restart Start.

3 Open a shell window and type one of the following: • • • . select Settings > Control Panel > Administrative Tools > Event Viewer. . stop. FMSCheck is completely scriptable using the language of your choice. Start. or restart Flash Media Server using the command line 1 * cd /<the directory where FMS is installed>./server [start | stop | restart]. 2 Enter . 2 Enter . 3 Double-click an event generated by Flash Media Server to view details. A small video file for testing is included. C shell. it does the following: • Checks the connection to any instance of an application • Checks all active instances of the server by connecting to those applications • Can publish and play a stream • Can play the available server-side stream for an application Note: Currently. (The following steps are accurate if you are working directly on the server.) 1 From the Windows Start menu. or Python.xml file must be configured to accept a connection from this tool (this configuration is required to use --allapps and its dependent commands)./fmsmgr adminserver restart Start. To view the events from another Windows machine. 2 Select the Application panel. When the tool connects to Flash Media Server. As a command line tool. The Users./fmsmgr adminserver start . The tool is available for both Windows and Linux using different executable files. use Event Viewer to open a remote connection to the server. or restart the Administration Server using the command line 1 * cd /<the directory where FMS is installed>. The Event Viewer displays a list of events that the server generates. what the response time is. stop. Checking server status View server events in the Windows Event Viewer The Windows Event Viewer can be used for tracking Flash Media Server activity and debugging server applications. and which fmscore processes are not responding. FMSCheck provides information about whether the server is running or not. Check server health FMSCheck is a command line utility program that can be used to diagnose and determine server status.5 CONFIGURATION AND ADMINISTRATION GUIDE 67 Administering the server 2 Change to the directory where the server is installed./adminserver [start | stop | restart].Last updated 3/2/2010 FLASH MEDIA SERVER 3. bash. FMSCheck only supports RTMP connections and does not check for shared objects./fmsmgr adminserver stop . such as Cscript.

5 CONFIGURATION AND ADMINISTRATION GUIDE 68 Administering the server FMSCheck commands and options Option --host <hostname> --port <number> --app <app> Description Required. Example: --host localhost Port number is optional. tests are run on each application serially (connect to the first application. the existing file is overwritten. After the file is published. Both record and append are optional. This command must be used along with --pubfile. the name of the output file to be created on server side. The value of <sec> is in seconds. --apswd. If the program does not receive a response from the server within this interval. If you specify a very long stagger time (longer than the duration of the test). Values for start and duration must be in positive numbers or 0 and represent the number of seconds. it is automatically played to verify the success of the publish operation. if there is a large number of applications. an error is returned. You cannot give the play and publish commands at the same time. use the following: --parallel 10 --stagger <sec> Inserts a pause between tests. However. run test. This command is used along with --parallel. and the default value is 1 second. The default value is 1935. only a positive number. Running parallel without specifying max tests every application in parallel. Example: --play foo 10 5 --allapps --help --logfile <file> --play <name> [start [duration]] --publish <name> <duration> [record|append] Publishes files to the server. Displays Help for using FMSCheck. tells the program where to connect the server. Administrator must specify the application. Prints a version string. and -ahostport options in order to log in to the Administration Server. zero. the administrator must use the --auser. Allows the program to output a response to a file. such as authentication. to run 10 tests in parallel. Example: --port 1935 Allows the program to connect to an application. This command must be used with --publish. This command is used with --allapps. If neither is specified.log Instructs the program to play video files. fmscheck -v . The administrator must configure Users. For example. The default value of start is any.xml to accept connections from this program. If there is more than one application. in seconds. run test. Example: --pubfile input. The duration parameter is required. If this option is not specified. connect to the second application. Example: --app app1/inst1 Queries the Administration Server for active instances and makes a connection to each active instance. If the file already exists and record is used.Last updated 3/2/2010 FLASH MEDIA SERVER 3. running all of them in parallel may not be desirable. Indicate the maximum number of applications that can be run in parallel by specifying a value for max. and the duration. Example: rtmp://host/app/inst?foo=abcd --query <" "> --timeout <sec> Specifies a timeout value. Example: --stagger 2 Allows you to input your own string for special purposes. or all is allowed. Example: --publish foo -1 --pubfile <file> Specifies a filename. In this case. the default behavior is to record. You can specify all to play the entire file. Example: --logfile output. verify that the timeout value is adequate.flv --publish output 10 --parallel [<max>] Allows the program to play multiple applications at the same time. Options are start and duration. Specify the name of the input video file residing on the client side. then you are effectively running in serial mode. The default value of duration is 1 second. which plays the file from the beginning. and so on). a result cannot be provided. This command can take time to finish.

The tool supports unicode filenames. At least one application failed. but some of the tools create files that do not comply with the FLV standard. bad message headers. In addition. Connection failed. Play failed. . Checking video files Checking FLV files created or modified with third-party tools Third-party tools are available to create and modify FLV files. The tool verifies that metadata is readable. FMSCheck return codes Return codes for the FMSCheck tool report the status after the tool has been run. Operation timed out. the default port is 1111.exe.exe --host localhost --app app1 --play foo 0 10 --logfile output. Invalid command line argument.exe --host localhost --app app1 --logfile output. invalid onMetaData messages. File not found. Example: --ahostport 1111 Usage examples for Windows: • • • • * fmscheck. and checks that the FLV file is seekable by Flash Media Server. Code 0 -1 -2 -3 -4 -5 -6 -7 Status Success.txt All of the Windows examples can be adapted to Linux by using * . The FLVCheck tool can be used to analyze FLV files before they are deployed on Flash Media Server.txt * fmscheck. Publish failed./fmscheck instead of * fmscheck. If the port number is not specified in the command line. Example: --auser admin Specifies a password for the Administration Server.flv --publish bar 10 --logfile output. specifies an accurate duration.txt * fmscheck. The tool can then merge the server metadata with the data present in the file. Note: The FLVCheck tool does not correct FLV file content corruption. and corrupted audio and video. Common problems include bad timestamps in the FLV file.txt * fmscheck.5 CONFIGURATION AND ADMINISTRATION GUIDE 69 Administering the server Option --auser <username> --apswd <password> --ahostport <port> Description Specifies a user name for the Administration Server user.Last updated 3/2/2010 FLASH MEDIA SERVER 3.exe --host localhost --allapps --auser admin --apswd admin --parallel 10 -stagger 2 --timeout 100 logfile output.exe --host localhost --app app1 --pubfile foo. The tool does fix metadata by scanning the Duration and Can Seek To End metadata fields. Example: --apswd admin Specifies the Administration Server port number. the tool can also add or update metadata to reflect file duration correctly.

not the text output. Option -f [ --file ] file . Relative paths may be used./test/123. Displays an example and information about command-line parameters.) Only the Duration and Can Seek To End metadata fields are corrected. use the FLVCheck tool to verify that the server can play back your files. Provides a description of options and an example. that FLVCheck reports. try the “/” character instead. in seconds.5 CONFIGURATION AND ADMINISTRATION GUIDE 70 Administering the server Checking other video files Flash Media Server supports playback and recording of H.264-encoded video and HE-AAC-encoded audio within an MPEG-4–based container format. the server logs a warning that the metadata duration is incorrect. All MP4 files and Adobe F4V files are part of the supported subset. (FLV files only) If a metadata tag is corrupted. 2 Use the following syntax to run the FLVCheck tool: flvcheck [-option] <file .> For example.. A subset of the MPEG-4 standards are supported. (If the file contains no errors. Specifies the margin of error.. The --help option overrides this option. specify -d 0. creates a new copy of the original FLV file in the same directory as the original. Description Specifies the path to the video file(s) being checked. If the margin has not been exceeded.Last updated 3/2/2010 FLASH MEDIA SERVER 3.. the executable is named flvcheck. be returned.. -v [--verbose] -V [ --version ] -n [ --nobanner ] -h [ --help ] -d [ --duration ] -q [ --quiet ] Specifies that only the status code. Prints version information. Treat warnings as errors. nothing will be logged.flv . To get the exact duration. Turns off header. to check two files: flvcheck -f abc. 1 Open your operating system’s command prompt and change directories to RootInstall/tools. with corrected metadata. Note: The FLVCheck tool does not correct corrupted H. Fix a stall in video playback (FLV only).) When validating metadata. Check a video file with the FLVCheck tool The FLVCheck tool is a command line program.flv The following table describes the command line options available. a backup file is not created. For MPEG-4–based container formats. (Avoid using the “\\xd3 character.) Sets the verbose flag.264-encoded files or make any other fixes to MP4/F4V files. the absolute difference between metadata_duration and actual_duration is calculated and compared against the margin specified in this command. -w [ --warnings] -W [--warnings_as_errors] -s [ --fixvideostall ] -u [ --usage ] -m [ --fixmeta ] . Display warnings. If the margin is exceeded.. (The default is 2 seconds.

4 (FLV files only) If an error is returned from an FLV file due to a metadata error. -15 MP4 Too many tracks. For example. and FileName. Errors and warnings are logged in a log file (stdout). If there are one or more errors. but the tool cannot create a file with corrected metadata. The duration field in the metadata may be inaccurate by a few seconds. This error occurs if the MP4 file is empty. types of errors. Unrecognized message type. If a return code of -1 is returned. the error is logged to the stdout file in the following format: Date. flvcheck -f abc. you can use the tool to try to correct the problem. . Cannot open file. a positive number indicating the total number of invalid files found is returned. Error numbers -2 -3 -4 -5 Error type General General General General Error messages Invalid file system path specified.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The possible error numbers. Unparsable data message. -6 General Cannot create corrected file. File does not contain a movie box. Invalid FLV data offset.flv -d 5 would allow the metadata duration to be inaccurate +/. Try the following: a Use the -m option to try to fix the metadata in the file: flvcheck -m <file> [-quiet] [-help] b Use the -d option to change the duration field margin of error. This error could occur if the MP4 file contains audio or video encoded with unsupported codecs. File read error. MP4/F4V files cannot be fixed using the FLVCheck tool. Other types of errors cannot be fixed using the FLVCheck tool. -7 -8 -9 -10 -11 -12 -13 FLV FLV FLV FLV FLV FLV MP4 Invalid FLV signature.5 seconds. and messages are as follows.5 CONFIGURATION AND ADMINISTRATION GUIDE 71 Administering the server 3 If the FLVCheck tool finds no errors in the FLV file. indicating that the encoding of part or all of the file is not compatible with the codecs that are supported. an invalid command-line parameter was specified. This error occurs if you run the tool with the -m option set. ErrorNumber. ErrorMessage. Flash Media Server cannot read the file. Maximum allowed is 64. Time. FLVCheck errors If an error is found. Invalid FLV message footer. Found backward timestamp. -14 MP4 File does not contain any valid tracks. the status code returned is 0. File not found.

Time. . File contains out-of-order movie fragments.. warnings are informative and are not fatal errors. Warning number -100 -101 -102 -103 -104 -105 -106 -107 Warning type General FLV MP4 MP4 MP4 MP4 MP4 MP4 Message Metadata duration is missing or is incorrect.. Ignoring. Ignoring. Warning Message. Unrecognized box.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Flash Media Server cannot play back the track. Too many tag boxes. Ignoring. Warning Number. but you may experience problems with playback. Flash Media Server ignores (will not play back) tracks that are encoded with unsupported codecs. Duplicate box. Invalid chapter time. Error reading MP4 tables. Invalid number of data entries in box. canSeekToEnd is false. Found duplicate data track. File appears to be FLV with wrong extension. Invalid box version.. Found duplicate audio track. Found duplicate video track. File contains unexpected movie fragments.5 CONFIGURATION AND ADMINISTRATION GUIDE 72 Administering the server Error numbers -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 Error type MP4 MP4 MP4 MP4 MP4 MP4 MP4 MP4 MP4 MP4 General MP4 MP4 MP4 MP4 Error messages Only one sample type allowed per track. and File Name.. This warning indicates that a track has an invalid video codec. -108 MP4 Invalid video codec. Truncated box. Max is 64.. Invalid sample size. Track has unsupported sample type. Unsupported DRM scheme. Flash Media Server will ignore the error that caused the warning and continue to load and play back the video or audio file. Invalid movie time scale. Found incomplete track. Warnings are logged to the stdout file in the following format: Date. FLVCheck warnings Generally.. Box is too large.

Sample(s) skipped.bat as the new file to run. File has unsupported metadata format. you must delete unused files to manage disk usage. Audio messages found but audio flag not set. -110 -111 -112 -113 -114 -115 -116 -117 -118 -119 -120 -121 -122 FLV MP4 MP4 FLV FLV FLV FLV MP4 MP4 FLV MP4 MP4 MP4 Video may appear stalled due to lack of audio data. Track contains unsupported edit list. Video flag set but no video messages found. . You can use the timestamp to determine when a cached file was used.bat file and verify that it deletes files in the cache directory.5 CONFIGURATION AND ADMINISTRATION GUIDE 73 Administering the server Warning number -109 Warning type MP4 Message Invalid audio codec.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Will only be partially playable. Audio flag set but no audio messages found. 3 Select Control Panel > Scheduled Tasks > Add Scheduled Task. 1 Create a cache.* 2 Run the cache. 5 Replicate this procedure on each edge server. File is truncated. Box has extraneous bytes at end. Manage the edge server cache in Windows You can create a weekly scheduled task to clear the edge server cache. Edge servers update the timestamp of a file each time the file is used. this is expected behavior. Video messages found but video flag not set.bat file to empty the cache directory. Bad NellyMoser Frequency. 4 Select cache. This warning indicates that a track has an invalid audio codec. Clearing the edge server cache Deleting files from the edge server cache Edge servers do not delete content automatically. Invalid Track Extends Box. The directory structure remains and any files currently locked by the edge server are not deleted.bat file has the following syntax: del /Q /S <cache_directory>\*. The entry in the cache. Track contains unsupported sample flags. Missing FLV metadata. Flash Media Server cannot play back the track.

mp3" -exec rm-f{}\. Starts. or restarts Flash Media Administration Server. If <service_name> does not exist. Warning: Use this command only if you want to uninstall the server service. . (For details about the cron utility. find <cache_directory> -name "*.Last updated 3/2/2010 FLASH MEDIA SERVER 3. such as adding users or checking the status of applications. The <install_dir> parameter is the absolute directory path where you installed Flash Media Server.sh to run. see the documentation for your Linux distribution. Sets the Flash Media Administration service to start manually. the command fails.) Managing the server on Linux Use the fmsmgr utility to perform basic management tasks for Flash Media Server running on Linux systems. 2 Verify that the script is executable by running the following command: $ chmod 700 cache.sh to empty the cache directory. If <service_name> already appears in the fmsmgr tables. Removes the Flash Media Server service from the fmsmgr tables. the old entry is updated with the new one.sh to verify that it deletes the correct files in the cache directory. with additional information about services that are currently running. Command fmsmgr adminserver start|stop|restart fmsmgr server <service_name> start|stop|restart fmsmgr clearautostart fmsmgr list Description Starts. You must be a root user to use the fmsmgr utility. the corresponding Administration service is also removed. 4 Use the cron utility to schedule cache. fmsmgr remove fmsmgr add <service_name> <install_dir> Add a Flash Media Server service to the fmsmgr tables.5 CONFIGURATION AND ADMINISTRATION GUIDE 74 Administering the server Manage the edge server cache in Linux 1 Create a shell script named cache. The server name is fms by default.flv" -exec rm-f{}\. If you remove a server service. you still need to manually remove the installed files.mp4" -exec rm-f{}\. The cache.sh script has the following syntax: find <cache_directory> -name "*. stops. if you do not specify <service_name>. or restarts a Flash Media Server service. such as starting and stopping the server and services. Note: You can add any additional file types to the script. stops. including Administration services. find <cache_directory> -name "*. A root user must use the fmsmgr utility to start the Flash Media Administration Server before anyone can use the Administration Console.sh 3 Run cache. use the Administration Console. You do not need to be a root user to use the Administration Console. For tasks not listed in the following table. Syntax fmsmgr server <service_name> <cmd> For commands that use the <service_name> parameter. Note: Running multiple Flash Media Server services concurrently is not supported. the command is performed on the name of the server you selected during installation. Lists all the services installed.

Sets the Flash Media Administration service to start manually. The Administration service name is the same as the Flash Media Server service name. Any installed Administration service can be used to administer one or more servers.Last updated 3/2/2010 FLASH MEDIA SERVER 3. fmsmgr getadmin fmsmgr setautostart<service_name> fmsmgr clearautostart <service_name> fmsmgr suggestname Gets the name of the default Administration service. Only one Administration service can be running at a time.5 CONFIGURATION AND ADMINISTRATION GUIDE 75 Administering the server Command fmsmgr setadmin <service_name> Description Changes the default Administration service. Suggests a service name that does not already appear in the fmsmgr tables. . Sets the Flash Media Server service to start automatically when the system is started.

see “XML configuration files reference” on page 80. For more information.changePswd</Allow> <Deny>All</Deny> <Order>Deny.ini file in the RootInstall/conf folder. For example.xml file that give you finer control over permissions. use your valid port number in all examples. if you have.Allow</Deny> </HTTPCommands> </AdminServer> Note: There are additional XML elements in the Users.HTTPCOMMAND_ALLOW parameter is set to true. For example. • This document assumes that you have not changed the default port number (1111) for the Administration Server. the administrator JLee would enter the following information for the administrator user name parameter in the method call: _secondAdaptor_/JLee. 1 Open the fms. the following code allows the ping() and changePswd() methods: <AdminServer> <HTTPCommands> <Enable>${USERS. enter method names in a comma-delimited list to allow HTTP requests to execute Administration API calls.xml file in the RootInstall/conf folder.HTTPCOMMAND_ALLOW}/Enable> <Allow>ping. 2 Make sure that the USERS.Last updated 3/2/2010 76 Chapter 6: Using the Administration API Working with the Administration API About the Administration API Use the Administration API to monitor. if you do not specify a virtual host in the scope parameter. manage. 5 Save the file and restart Flash Media Administration Server. • By default. 4 In the <Allow> element. it is assumed that you want to perform the command on the virtual host to which you connected when you logged in to Flash Media Server. when logging in (over RTMP using NetConnection) to a virtual host on the adaptor _secondAdaptor_. Set permissions for Administration API method calls over HTTP Note: You do not need to set permissions to call methods over RTMP. Here are a few important tips for working with the Administration API: • Both Adobe Flash Media Server and Flash Media Administration Server must be running. and configure the server from an Adobe Flash Player or Adobe AIR client over RTMP or RTMPE or from a web client over HTTP. When logging in to a virtual host not on the default adaptor. For example. administrators are logged in to the “_defaultRoot_” adaptor. The API is described in detail in Adobe Flash Media Server Administration API Reference. . The Flash Media Server Administration Console was built using the Administration API. 3 Open the Users. a default value may be used depending on the method. virtual-host administrators must specify the name of the adaptor. • If you do not specify an optional parameter.

2.bar:456} . "Hello World" 'String2' The only exceptions are the auser and apswd parameters.[31.ini file.3. 3 The server sends the XML results back to the browser: <?xml version="1.Last updated 3/2/2010 FLASH MEDIA SERVER 3.Call. [1. which should be passed without quotation marks. • Numbers are passed as either integer or floating-point literals."hi"] [10.5 CONFIGURATION AND ADMINISTRATION GUIDE 77 Using the Administration API Call an Administration API method over HTTP 1 Verify that Flash Media Administration Server is running.0" encoding="utf-8" ?> <result> <level>status</level> <code>NetConnection. use the server address instead of localhost. This example uses a web browser because it’s the simplest client and good for testing purposes. You can use either single quotation marks (') or double quotation marks (").4] ['abcd'. Parameters passed in an HTTP request must adhere to the following formatting rules: • Name the parameters in the string. the application name must be included within quotation marks (" ") for methods such as reloadApp() and unload App() to work properly. For example. the following code calls the addAdmin() method: http://localhost:1111/admin/addAdmin?auser=adminname&apswd=adminpassword&username="joe"&pa ssword="pass123"&vhost="_defaultRoot_/foo.40] • Objects are passed as inline object literals.03 -45 Note: When a number is used for an application name.34.myCompany. • Arrays are passed as comma-separated values enclosed in square brackets.32]. {foo:123.Success</code> <timestamp>10/3/2007 05:31:01 PM</timestamp> </result> Constructing an HTTP request string Many Administration APIs expect one or more parameters in addition to auser and apswd. 245 1. Note: You can construct an Administration API call from any language that can send HTTP requests.com" • Strings are passed as literals surrounded by quotation marks. 2 Open a browser window and enter the following in the address bar: http://localhost:1111/admin/ping?auser=username&apswd=password If the web browser is on a different computer than Flash Media Server.20. which are located in the fms. Substitute your administrator user name and password.

Some information objects have a data property (containing return data.com/admin:1111.Last updated 3/2/2010 FLASH MEDIA SERVER 3. . can connect to the server. 2 Call the NetConnection. code. Note: To call the Administration API over RTMPE. Note: If you want to connect to a virtual host.onResult = function(info){ if (info.text). . follow the instructions below. new onGetAppStats().Call. To call Administration APIs over RTMP. printObj(info. onGetAppStats(): ncAdmin.connect("rtmp://localhost:1111/admin".text = "Info for "+appName. ncAdmin.text+ " returned:" + newline. new onGetAppStats(). but change the protocol in the example NetConnection. "635xjh27"). function onGetAppStats(){ this. The following sample is built in Flash.call("getAppStats".description.. passing in three parameters: the URI of the Administration Server. rtmp://www. 1 In the client application. an administrator user name.call() method and pass it the Administration API method.Success"){ outputBox. the response object onGetAppStats() captures the result of the call. All information objects have level.code != "NetConnection. you need a Flash Player or AIR client. Create your first application This section contains the code for a simple Flash application that calls the getAppStats() method.5 CONFIGURATION AND ADMINISTRATION GUIDE 78 Using the Administration API {user:"Joe".connect() call to RTMPE. The getAppStats() method returns performance data for an application running on the server. often in an object or array) and description and details properties. and vod is the name of the application instance from which to retrieve statistics..call("getAppStats".ssn:"123-45-6789"} Call Administration API methods over RTMP or RTMPE To call the Administration API over RTMP or RTMPE. The following code creates a NetConnection for the administrator MHill with password 635xjh27 to the server on localhost: ncAdmin = new NetConnection(). appName. outputBox). and timestamp properties.myVhost. create a NetConnection to Flash Media Administration Server. a response object (if needed) and any parameters (if needed): ncAdmin. 3 Define a function to handle the information object returned by the Administration API method. which typically provide information about errors. and an administrator password. "vod"). } } } The data is returned to the handler function in an information object. Only valid administrators. in this example. as defined in the Users. you need a Flash Player or AIR client. "MHill". } else { outputBox.text = "Call failed: " + info.xml configuration file. specify the virtual host’s domain name or IP address as part of the URI— for example.

appName.call("getAppStats".text += prop + " = " + obj[prop] + newline."admin_name". for example.text = "Info for "+appName. 1 In Flash. ActionScript 2.text+ " returned:" + newline.onRelease = function(){ doGetAppStats().Call. dynamic text field called outputBox • A scroll component attached to the outputBox text field Note: Since this is a Flash Media Server application. create an application with the following elements: • An input text field named appName • A button called button_btn • A multiline.text). outputBox).5 CONFIGURATION AND ADMINISTRATION GUIDE 79 Using the Administration API Note: You can call Administration APIs from applications written in ActionScript 1."admin_pass"). new onGetAppStats().text += "\t". } 3 Before running this sample application.onResult = function(info){ if (info.connect("rtmp://localhost:1111/admin". 5 Run the sample Flash application and enter the name of the application you started in step 3 in the input text field.0. . destination. you must create an application directory with the application name in the RootInstall\applications directory.0. } function printObj(obj. printObj(info.code != "NetConnection. destination){ for (var prop in obj) { destination.text = "Call failed: " + info.Success"){ outputBox.Last updated 3/2/2010 FLASH MEDIA SERVER 3. start another Flash Media Server application. /** Makes the API call. if (typeof (obj[prop]) == "object") { // recursively call printObj printObj(obj[prop]. } }. } else { outputBox. } } } button_btn. destination). } // Calls the getAppStats() API on the name of application // in the input text field // places the response in the onGetAppStats funtion ncAdmin. 4 Open the Administration Console to verify that the application you started in step 3 is running. 2 Enter the following code on frame 1 of a Flash file: /** Establishes the connection to Flash Media Server **/ ncAdmin = new NetConnection(). or ActionScript 3. ncAdmin. // Replace admin_name and admin_pass with your // administrator name and password.0.description. "getAppStats" **/ function doGetAppStats() { function onGetAppStats(){ this.

adobe.60. Each adaptor directory must contain an Adaptor. Contains all the elements in the Adaptor. Important: Some XML elements should not be configured without contacting Adobe Support.xml file. and/or full or partial IP addresses from which clients can connect to the server. For example. You can also implement SSL with the Adaptor.com. Adaptor Root element.xml file is the configuration file for individual network adaptors. the communications ports the adaptor binds to.1.Last updated 3/2/2010 80 Chapter 7: XML configuration files reference Edit the configuration files in the RootInstall/conf directory to configure the server. The name of the directory is the name of the adaptor. 10. the default adaptor included with the server at installation is named _defaultRoot_ and its directory is found in the conf/ directory. if you want to use different digital certificates for different adaptors. These elements are marked with an Important note.xml file.xml file. Example <Allow>foo.60</Allow> See also Deny.com. To change an adaptor’s settings. More Help topics “Editing configuration files” on page 9 Adaptor. 10.xml file. To see the element structure and default values in the Adaptor.xml file. Each adaptor has its own directory inside the server’s conf directory.xml file The Adaptor. It determines the number of threads that can be used by the adaptor. edit the elements in its Adaptor. Order .xml file. see the RootInstall/conf/_defaultRoot_/Adaptor. and the IP addresses or domains from which the adaptor can accept connections. Allow A comma-delimited list of host names. domain names.133.yourcompany.

60</Deny> See also Allow. WriteBufferSize.1.1only keepalive Description Allow all HTTP tunnelling connections. MimeType. MaxWriteDelay Enable Specifies whether or not to allow HTTP tunnelling connections. These are the possible values for the Enable element: Value true false http1. Redirect.com. IdleAckInterval.133. SetCookie. and/or full or partial IP addresses from which clients cannot connect to the server.0 keepalive connections. Allow HTTP 1.yourcompany. Disallow all HTTP tunnelling connections. MimeType.60. Order Edge Container element.com. Allow only HTTP 1. adobe.1 or HTTP 1. Example <Deny>foo. NeedClose. SetCookie.1 tunnelling connections. Important: Only one application can use a port at a time. 10. MaxWriteDelay .Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <Enable>true</Enable> See also IdlePostInterval. Contained elements Enable. Each edge can have different HTTPTunnel configurations. This is the default value. Redirect. Attribute name A name identifying an edge. Contains elements that specify an edge to configure for HTTP tunnelling. if you configure Flash Media Server to use port 80 for HTTP tunnelling. IdleAckInterval. domain names. For example. Edges are defined in HostPort elements in the HostPortList container. 10. Use the name specified in the HostPort element. MimeType. IdlePostInterval. WriteBufferSize. the web server cannot use port 80.5 CONFIGURATION AND ADMINISTRATION GUIDE 81 XML configuration files reference Deny A comma-delimited list of host names.

HOSTPORT parameter in the RootInstall/conf/fms. the web server cannot use port 80. When assigning port numbers. <EnableAltVhost>false</EnableAltVhost> See also HTTPTunnel.80.-443. add a HostPort element for each IP address.0. each must have a different ctl_channel. 80. The client will attempt to perform an SSL handshake that the server will fail to complete.Last updated 3/2/2010 FLASH MEDIA SERVER 3. don’t specify anything in front of the colon. The format is IP:port. Flash Media Server logs a warning in the Access log file indicating that the specified IP:port is in use. See also Redirect HostPort Specifies to which IP address and port(s) an adaptor binds. and 443.5 CONFIGURATION AND ADMINISTRATION GUIDE 82 XML configuration files reference EnableAltVhost Determines whether an alternative virtual host may be specified as a part of the RTMP URL as query parameter rtmp://host1/app/?_fcs_vhost=host2. it connects to an FMSEdge process on this internal port to establish a control channel.) RTMPS connection attempts to ports 1935 or 80 will not succeed. RTMP. This element is exposed as the ADAPTOR. the first adaptor to bind to the specified HostPort wins.. SSL Host Redirects unknown requests to an external server. This does not apply to administrative connections. Similarly. This value instructs the adaptor to bind to any IP address on ports 1935. Example The following HostPort value instructs the adaptor to bind to the IP address 127.port. where 443 is designated as a secure port that will only receive RTMPS connections. When an FMSCore process is started (fmscore in Linux). To bind to any IP address. If you want to bind an adaptor to multiple IP addresses. Each HostPort element corresponds to an FMSEdge process. . ctl_channel The internal port that an FMSEdge (fmsedge in Linux) process listens on.port.ini file. which are always on by default. For example. To resolve this conflict. The default value is :1935. if you configure Flash Media Server to use port 80 for HTTP tunnelling. (A port is marked as secure by specifying a minus sign in front of the port number. a conflict results. If there are multiple HostPort elements. If there are multiple HostPort elements. a regular RTMP connection to port 443 fails because the server tries to perform an SSL handshake that the client fails to complete. 80. where 443 is designated as a secure port that will only receive RTMPS connections.. The default value is false.. and 443. If another process tries to bind to the same IP:port combination. keep in mind the following: • There is a risk in assigning more than one adaptor to listen on the same IP:port pair. each must have a different name.0. • Only one application can use a port at a time.. Attributes name A name to identify this HostPort element.1 on ports 1935.

80.0.0. When the enable attribute is set to true.0. the <FCS></FCS> response is returned without content. it logs the request to the edge. Attributes enable A Boolean value specifying whether the server responds to an HTTP identification request (true) or not (false).-443</HostPort> If there is no colon in the HostPort value.0.0. The entire response is enclosed in <FCS></FCS> elements.HOSTPORT}</HostPort> <HostPort name="edge2" ctl_channel=":19351">:1936.Last updated 3/2/2010 FLASH MEDIA SERVER 3.1</HostPort> <HostPort>127. or there is a colon with no ports specified.0.1:1935. the HTTPIdent function must be enabled and the client must do a POST or GET for the "/fcs/ident" resource.0.1 on port 1935: <HostPort>127. The default value is false. For a response to be returned. Example <HTTPIdent enable="true"> <Company>Adobe System Inc</Company> <Team>Flash Media Server</Team> </HTTPIdent> The following is an example request: http://serverIP:1935/fcs/ident The following is an example response: . When the server receives an HTTP Identification request.5 CONFIGURATION AND ADMINISTRATION GUIDE 83 XML configuration files reference <HostPort>127. If the HTTPIdent function is enabled but no content is specified.xx.1:</HostPort> See also HostPortList HostPortList Container element.0. all elements in the HTTPIdent section are returned as a response. the data is assumed to be an IP address and binds to port 1935.-444</HostPort> </HostPortList> Contained elements HostPort HTTPIdent Configures the server to respond to or reject an HTTP identification request from a client. Example <HostPortList> <HostPort name="edge1" ctl_channel=":19350">${ADAPTOR. The elements in this container list HostPort elements associated with this adaptor. The following values instruct the adaptor to bind to IP 127.log file. which are added by the server.

If you are running Flash Media Server on Linux and have enabled IPv6 but are using an IPv4 hostname (a hostname that resolves to IPv4).Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <HTTPNull enable="false"> . RTMPT (Tunnelled Real-Time Messaging Protocol) can have difficulties working with load balancers. The IP address can be explicitly configured and does not need to be the IP of the Flash Media Server machine. This feature is enabled by default. the HTTPIdent2 function must be enabled. even if the <HTTPIdent2> tag or the enabled attribute is missing. If a single RTMPT session consists of multiple socket connections. Attributes enabled A Boolean value specifying whether the server responds to a special HTTP identification request before making a RTMPT connection (true) or not (false). Attributes enable A Boolean value.) If the tag is left empty. This causes the session to be split across machines. Example <HTTPIdent2 enabled="true">10. requests for the "/" resource are passed to the webserver.133. HTTPUserInfo HTTPIdent2 Configures the server to respond to or reject a special HTTP request from the client before the client attempts to make a RTMPT connection to Flash Media Server.128. HTTPTunnel. For a response to be returned. the IP address is determined automatically. The default value is false. each connection may be sent to any one of many Flash Media Servers behind load balancers. an HTTP 404 response is sent in response to an HTTP GET request.5 CONFIGURATION AND ADMINISTRATION GUIDE 84 XML configuration files reference <fcs> <Company>Adobe System Inc</Company> <Team>Flash Media Server</Team> </fcs> See also HTTPNull. HTTPUserInfo HTTPNull Configures the server to respond to or reject an HTTP GET request for the “/” resource from a client. then use this tag to resolve RTMPTE and RTMPE connections more quickly: either set the enabled attribute to false or set it to true and set the value of the tag to the IP address to which you’re connecting. HTTPTunnel. (This allows RTMPT connections to be redirected to a different server. This function is available when using Flash Player Update 3 or later. If HTTPNull is disabled and the webserver is enabled. the HTTPNull function is disabled.71</HTTPIdent2> See also HTTPNull. Using <HTTPIdent2> enables Flash Player to send a special HTTP request before connecting to Flash Media Server. When the enable attribute is set to true. By default.

MaxSize.xml file. or replace the variable in the Adaptor. For example. The elements in this section configure the incoming HTTP tunnelling connections to the adaptor. automatically handling the case when producers and consumers differ widely in bandwidth. For proxying to work.HOST = :8134 HTTPTunnel Container element.5 CONFIGURATION AND ADMINISTRATION GUIDE 85 XML configuration files reference HttpProxy Specifies whether the server proxies unknown requests to an external server.ini file. The following is from the default Adaptor. The elements in this section configure the absolute path to XML files and the cache settings.xml file: <HttpProxy enable="true" maxbuf="16384"> <Host port="80">${HTTPPROXY. HTTPTunnel/Enable must be set to true.example.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example In the default Adaptor. if you configure Flash Media Server to use port 80 for HTTP tunnelling. The default value is 16384. Contained elements Enable HTTPUserInfo Container element. maxbuf The size of the io buffers. the value of the Host element is a variable from the fms.HOST}</Host> </HttpProxy> The IP address and port to which the server proxies unknown HTTP requests. the server uses a localhost port.HTTPPROXY. as in the following: HTTPPROXY.HOST = webfarm.ini file. UpdateInterval . Contained elements Path. Request proxying to a specific host can be further controlled based upon port on which the request arrived. You can set the value of HTTPPROXY. Attributes enable A Boolean value. The default value is true.com:80 If you do not specify an IP address or domain name. the web server cannot use port 80.xml file. Flow control kicks in when the buffer in either direction fills up. Each edge can have different HTTPTunnel configurations. Note: Only one application can use a port at a time.HOST in the fms.

Applications that do not have high latencies can use the configuration 1024/2048. in seconds. Example <IdleTimeout>8</IdleTimeout> See also IdlePostInterval. The default setting for IdleTimeout is 8 seconds. For applications not sensitive to high latencies. Example <IdlePostInterval>512</IdlePostInterval> See also IdleAckInterval. which provides medium latency. Applications desiring low latency may configure the combination of values 128/256 for IdlePostInterval and IdleAckInterval elements. The default value is 512 milliseconds. use the combination 1024/2048. IdleAckInterval . IdleTimeout IdlePostInterval Specifies the interval in milliseconds at which the client sends idle posts to the server to indicate that Flash Player has no data to send. Values that are too high may result in disconnected sessions consuming server resources for longer than necessary. in seconds. The value of IdleTimeout indicates the maximum time. that such a session may remain idle before it will be automatically disconnected. Values that are too low may cause clients with very high latencies to become disconnected.5 CONFIGURATION AND ADMINISTRATION GUIDE 86 XML configuration files reference IdleAckInterval Specifies the maximum time in milliseconds the server waits before it sends an acknowledgement code for a client idle post. An IdleTimeout of -1 indicates that idle tunnel sessions will not be disconnected. and that the receiving server is ready to accept transmissions. <IdleAckInterval>512</IdleAckInterval> See also IdlePostInterval. When a client using HTTP tunnelling disconnects unexpectedly. IdleTimeout IdleTimeout Specifies the maximum inactivity time. Applications desiring low latency may configure the combination of values 128/256 for the IdlePostInterval and IdleAckInterval elements. for a tunnel session before it is closed. The values for this element and the IdlePostInterval element affect the latency observed by a client tunnelling into the server.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Low values reduce the latency but increase the network bandwidth overhead. Lower values reduce latency but increase the network bandwidth overhead. These elements should be configured at the same time. An acknowledgement code is a transmission control character used to indicate that a transmitted message was received uncorrupted and without errors. The default settings for the IdleAckInterval and IdlePostInterval elements provide medium latency and are set to 512/512 milliseconds. their session may remain open for a long period of time after disconnecting.

Occasionally. See also HTTPTunnel . Example <Edge name="Edge1"> <Enable>true</Enable> <IdlePostInterval>512</IdlePostInterval> <IdleAckInterval>512</IdleAckInterval> <MimeType>application/x-fms</MimeType> <WriteBufferSize>16</WriteBufferSize> <SetCookie>false</SetCookie> <Redirect enable="false" maxbuf="16384"> <Host port="80">:8080</Host> </Redirect> <NeedClose>true</NeedClose> <MaxWriteDelay>40</MaxWriteDelay> </Edge> You may want to use this sample code as a template for configuring each edge server. the server reduces the cache. when connections close under abnormal conditions. which may continue to place writes in a queue. The default number of failures is 2. When the cache size reaches the maximum size. UpdateInterval MaxWriteDelay The HTTP tunnelling protocol ensures that a server will be able to write every four seconds. the value is 100.5 CONFIGURATION AND ADMINISTRATION GUIDE 87 XML configuration files reference MaxFailures Specifies the maximum number of failures an edge server may incur before it restarts. Anomalous connections are closed after the specified wait time.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <MaxFailures>2</MaxFailures> See also IdleAckInterval MaxSize Specifies the maximum number of HTTP requests the server keeps in the cache. the notification may not reach the server. Example <MaxSize>100</MaxSize> See also Path. By default. The default wait time is 40 seconds.

and 0-9.Allow indicates that access to a server is allowed unless specified in the Deny element and not specified in the Allow element.Last updated 3/2/2010 FLASH MEDIA SERVER 3. which closes the connections. The following is the default sequence: <Order>Allow.Deny</Order> .0 non-keepalive connections are closed once the response is written.+!*'() See also HTTPTunnel Order Specifies the sequence in which the server evaluates the Allow and Deny elements. The default value is true. The ID must contain URL-safe characters: alphanumerical A-Z. The server generally uses the MIME type specified by the incoming requests. Example The following is the default sequence: <Order>Allow. Example <NeedClose>true</NeedClose> See also MaxWriteDelay NodeID Specifies a unique node identification that supports the implementation of load balancers. The alternative sequence Deny. and the special characters $-_.Deny</Order> The default sequence indicates that access to a server is denied unless it is specified in the Allow element. a-z.5 CONFIGURATION AND ADMINISTRATION GUIDE 88 XML configuration files reference MimeType Specifies the default MIME (Multi-purpose Internet Mail Extensions) type header sent on tunnel responses. The server uses the entry for the MIMEType element only if it is unable to determine the MIME type from the incoming requests. a following string of up to nine characters is prefixed to the tunnel session IDs and can be used by the load balancers to uniquely identify each node in the cluster. Example <MimeType>application/x-fcs</Mimetype> See also HTTPTunnel NeedClose A Boolean value specifying whether or not HTTP 1. If the NodeID element is used.

UpdateInterval RecoveryTime Specifies the number of seconds an edge server waits before restarting after a failure.Last updated 3/2/2010 FLASH MEDIA SERVER 3. . See also MaxSize. The number of failures is specified by the MaxFailures element. The maxbuf attribute determines how big the IO buffers are. When an edge server fails. the request is considered an error and the connection is closed. it waits for the interval specified here before it restarts. Example <RecoveryTime>30</RecoveryTime> See also MaxSize Redirect Specifies whether or not the adaptor redirects unknown requests to an external server. <Redirect enable="false" maxbuf="16384"> <Host port="80">:8080</Host> <Host port="443">:8443</Host> </Redirect> See also MaxWriteDelay. By default. The wait time is specified in seconds. HTTP tunnelling must be enabled. it is set to uInfo/ in the FMS install directory. Deny Path Specifies the absolute path of the folder where the server looks for XML files.5 CONFIGURATION AND ADMINISTRATION GUIDE 89 XML configuration files reference See also Allow. Flow control automatically handles the request when the bandwidth resources for producers and consumers differ widely. At any other time. An unknown request may connect only when it is the first request on a newly accepted connection. Flow control begins when the buffer in either direction fills up. Note: For redirection to work. NeedClose ResourceLimits Container element. Example This example instructs the server to redirect unknown requests to the specified redirect host.

This element is enabled by default. The elements in this container determine whether encrypted RTMP (RTMPE) and encrypted tunnelling RTMP (RTMPTE) can be used. Example <RTMPE enabled="true"></RTMPE> See also RTMP SetCookie Specifies whether or not the server sets a cookie. RecoveryTime RTMP Container element. known as SSL. The elements in this section configure the incoming connections via the Secure Sockets Layer protocol. setting enabled to false will not allow RTMPE or RTMPTE on this adaptor. Keep in mind that the cookie adds to the HTTP header size and increases the bandwidth overhead. Contained elements RTMPE RTMPE Specifies whether encrypted RTMP (RTMPE) can be used. The SSL elements in Adaptor. you should enable cookies when you deploy servers behind a load balancer. in Windows only. cookies are currently supported only on Flash Player 9. Note: For tunnelling connections.0.Last updated 3/2/2010 FLASH MEDIA SERVER 3. If the server does not have an externally visible IP address.28 or later. Example <SetCookie>false</SetCookie> See also NodeID SSL Container element.xml configure the server to act as an SSL-enabled server to accept incoming SSL connections. then for HTTP tunnelling to work.5 CONFIGURATION AND ADMINISTRATION GUIDE 90 XML configuration files reference The elements in this container configure the resource limits for the edge server. Contained elements MaxFailures. The load balancer checks the cookie and sends requests with this cookie to the same server. RTMPE is the encrypted RTMP protocol covering both RTMPE and RTMPTE. .

Example <SSLCertificateFile>c:\myCertFile</SSLCertificateFile> See also SSLCertificateKeyFile. you then use the SSL elements to configure the server for SSL.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file. This element contains a list of colon-delimited components. Contained elements SSLServerCtx SSLCertificateFile Specifies the location of the certificate to return to clients who want to make a secure connection to the server. authentication method. digest type. • If the private key file is encrypted. or one of a selected number of aliases for common groupings. SSLSessionTimeout SSLCipherSuite Specifies the suite of encryption ciphers that the server uses to secure incoming connections. If an absolute path to the key file is not specified.xml file. or by creating it yourself with a product such as OpenSSL. • Specify the location of the certificate in the SSLCertificateFile element. specify the passphrase to use for decrypting the private key file in the SSLPassPhrase element. • Specify where to find the associated private key file in the SSLCertificateKeyFile element. If this file is encrypted.5 CONFIGURATION AND ADMINISTRATION GUIDE 91 XML configuration files reference You need to acquire a digital certificate to use SSL. The default is PEM. such as Verisign. • Save the modified Adaptor. it is assumed to be relative to the adaptor directory. encryption method. Once you get your SSL certificate through a certificate authority. the certificate location is assumed to be relative to the adaptor directory. . If an absolute path is not specified. The following is a quick start to allowing SSL-enabled connections to the server: • to the SSL section of the Adaptor. SSLCipherSuite. A component can be a key exchange algorithm. SSLSessionTimeout SSLCertificateKeyFile This specifies the location of the private key file that corresponds to the public key in the certificate specified in SSLCertificateFile element. See also SSLCertificateFile. SSLPassPhrase. The encryption format is either PEM (Privacy Enhanced Mail) or ASN1 (Abstract Syntax Notation 1). SSLCipherSuite. SSLPassPhrase. a password must be specified for decrypting and placed in the SSLPassPhrase element described below. Example <SSLCertificateKeyFile type="PEM"></SSLCertificateKeyFile> The type attribute specifies the type of encoding used for the certificate key file.

Last updated 3/2/2010 FLASH MEDIA SERVER 3. this element is left blank. it must perform the full handshake. Example <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> See also SSLCertificateFile. SSLSessionTimeout SSLServerCtx Container element. It is a base64 encoding that makes the password less readable. See also SSLCertificateFile. SSLPassPhrase. To prevent plain text passwords from appearing in the configuration file. The elements in this section control the incoming SSL configuration for this adaptor. SSL sessions are used to improve performance by avoiding the need to perform the full SSL handshake for every connection. When a client connects to a server for the first time. it can send back the cached session object. SSLSessionTimeout SSLPassPhrase Specifies the passphrase to use for encrypting the private key file. The default time period is 5 minutes. SSLCertificateKeyFile. SSLPassPhrase. SSLCipherSuite. Specifies the password to use for decrypting the key file if the key file is encrypted. the server sends back a session object to the client. encode the password in base64 format and set the encrypt attribute to true. SSLCipherSuite. The server does not require the full SSL handshake if the session is still valid. SSLCertificateKeyFile. SSLSessionTimeout SSLSessionTimeout Specifies in minutes how long a SSL-based session remains valid. If the key file is not encrypted. After that first handshake. SSLCertificateKeyFile. Example <SSLPassPhrase encrypt="true">dGluY2Fu</SSLPassPhrase> The encrypted password is equivalent to the plain text format: <SSLPassPhrase>tincan</SSLPassPhrase> or <SSLPassPhrase encrypt="false" >tincan</SSLPassPhrase> Even though the element attribute is named "encrypt". it is not a true encryption. which the client can place in the cache and reuse at a later time. Contained elements SSLCertificateFile. . If the client connects to the same server again at a later time.5 CONFIGURATION AND ADMINISTRATION GUIDE 92 XML configuration files reference Note: Contact Adobe Support before changing the default settings as listed in this example.

By default.xml file in the application directory override settings in the Application. .xml file to the application’s registered application directory (/applications/app_name) and edit it to include the settings you want. In most cases. Example <WriteBufferSize>16</WriteBufferSize> See also ResourceLimits Application.xml file The Application. • If an element has the override attribute set to no. The Application. it is ignored. These settings include the size of the Server-Side Media ActionScript runtime engine. the value is 5000 milliseconds.xml files cannot override that element’s setting. SSLPassPhrase. SSLCipherSuite UpdateInterval Specifies how often the server refreshes the cache content. the location at which streams and shared objects are stored. then all subelements also cannot be overridden. and bandwidth limitations. copy an Application. If you want to have different settings for a particular application. in milliseconds. but not always. • If an Application.xml file contains the settings for Flash Media Server applications. You can add an override attribute to certain elements in a virtual host’s Application. application-specific Application. as in the following: <LoadOnStartup override="no">false</LoadOnStartup> The server uses the following rules when applying the override attribute: • When the override attribute is included in an element and set to no. Example <UpdateInterval>5000</UpdateInterval> See also Path. SSLCertificateKeyFile. the settings in the Application.xml file is located in the application directory and specifies a different value than the default for an element that cannot be overridden.xml file in the virtual host directory configures the default settings for all applications within the virtual host. MaxSize WriteBufferSize Specifies the size of the write buffer in kilobytes. and the default is used.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file in the virtual host directory.xml file. The default size is 16 KB.5 CONFIGURATION AND ADMINISTRATION GUIDE 93 XML configuration files reference Example <SSLSessionTimeout>5</SSLTimeout> See also SSLCertificateFile.

Contains elements that configure logging in the Access log. see the Application. contains an element that control the size of the aggregate messages.5 CONFIGURATION AND ADMINISTRATION GUIDE 94 XML configuration files reference • If the default Application. To see the element structure and default values. aggregate messages are broken up into individual messages before being delivered to clients. The Access plug-in consists of the libconnect.dll file. Note: By default. • All subelements under the LoadOnStartup element cannot be overridden. The elements in this section specify the maximum size and duration of intermediate frames a live stream can hold in the buffer.xml file is missing or invalid. It intercepts and examines each connection request to Flash Media Server to determine whether the connection should be accepted or rejected. it is ignored.xml configuration file is invalid. .Last updated 3/2/2010 FLASH MEDIA SERVER 3. When the enabled attribute is set to true. Contained elements MaxTime. The Client element in this XML file includes an override="no" attribute by default.xml file installed with Flash Media Server in the RootInstall/conf/_defaultRoot_/_defaultVhost_ directory. • To change an element so it cannot be overridden. MaxSize (AccumulatedIFrames) AggregateMessages (Client) Specifies whether or not to send aggregate messages to clients. AggregateMessages (Queue) Container element. the server will not start. • If the user-specified Application. the server will deliver aggregate messages to clients that support them. When this setting is disabled. the LoadOnStartup element can be overridden. set the override tag to no in the uppermost tag. Contained elements Checkpoints AccumulatedIFrames Container element. the Bandwidth and BandwidthCap container elements include an override parameter set to yes. • If you omit the override attribute. which allows the values for the ClientToServer and ServerToClient elements nested in these sections to be overridden. Contained elements FolderAccess Access (Logging) Container element. Access Container element. The default is false.

. aggregate messages are always broken up into individual messages before being delivered to clients. Flash Player communicates with the server using the RTMP protocol over port 1935. This is an opening that allows debug connections on a per application basis. UnrestrictedAuth AllowDebugDefault Specifies the default value for application. If that fails. MaxMessageSizeLosslessVideo. Example <Allow>true</Allow> See also Max. In some cases. or use the HTTP protocol to transmit RTMP packets (called HTTP tunnelling) if there is a firewall that allows only HTTP content to be sent out to public servers. whether messages in the queue can be combined to form aggregate messages.allowDebug.5 CONFIGURATION AND ADMINISTRATION GUIDE 95 XML configuration files reference This element also specifies.Last updated 3/2/2010 FLASH MEDIA SERVER 3. By default. Flash Player has to negotiate a connection to Flash Media Server through an edge server. The server attempts to send aggregate messages to supported clients whenever possible. it will try again over ports 443 and 80 in an attempt to get around firewall settings. the server creates aggregate messages. allowing HTTP redirects. when queuing is enabled. HTTPTunnel. When this setting is disabled. When the enabled attribute is set to true (the default value). The default value is false. The values for this element are described in the following table. Example <AggregateMessages enabled="false"><\AggregateMessages> See also MaxAggMsgSize. Example <AllowDebugDefault>false</AllowDebug Default> See also MaxPendingDebugConnections AllowHTTPTunnel This element configures the server to allow HTTP tunnelling connections into this application. which prevents TCP/IP connections over nonstandard ports. OutChunkSize Allow Specifies whether or not to allow the "following and Location:" header that is sent with redirection of an HTTP header. The default is true.

unless values are defined in the Application. Allows HTTP 1. The Vhost.1only keepalive Description Allows tunnelling connections. unless the values are defined in the Vhost. .xml values override the Vhost. MaxAppIdleTime.xml values. AllowHTTPTunnel. (Subsequently. When a client has been idle longer than the maximum idle time (60 seconds by default). The Application.xml file.5 CONFIGURATION AND ADMINISTRATION GUIDE 96 XML configuration files reference Value true false http1. SharedObjManager.xml file. Contains elements that determine whether or not to close idle clients automatically.xml. The default value is false.xml files or for individual applications in Application. Password AutoCloseIdleClients Container element. Set the enable attribute to true to close idle clients. Contained elements CombineSamples. If the enable attribute is omitted or set to false. Once you enable the feature in the Server.xml configuration file apply to all clients connected to the Vhost. The elements in this section specify the settings for audio streams on the server. you must enable the feature in the Server. The server also writes a message such as “Client x has been idle for y seconds” in the core and event logs.xml. See also Process.xml values. LoadOnStartup.xml configuration file apply to all clients connected to the server. Example <AllowHTTPTunnel>true></AllowHTTPTunnel> See also Allow Application This is the root element for Application. SWFVerification Audio Container element. the server sends a status message to the NetConnectionobject (the client). StreamManager. The server closes the client connection to the server and writes a message to the access log. Use the AutoCloseIdleClients element to specify how often the server should check for idle clients. you can disable the feature for individual virtual hosts in the Vhost. the values defined in the Server. SendSilence. JSEngine.xml values override the Server.0 and 1. Disallows tunnelling connections.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file. Debug.1 keepalive connections.1 connections only. A client is active when it is sending or receiving data. To configure the closing of idle connections. Allows HTTP 1. Client. HTTP. The values defined in the Vhost. the feature is disabled.xml file.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 97
XML configuration files reference

Example
<AutoCloseIdleClients enable="false"> <CheckInterval>60</CheckInterval> <MaxIdleTime>600</MaxIdleTime> </AutoCloseIdleClients>

AudioSampleAccess
Allows the client application to access the raw uncompressed audio data in a stream. By default, this element is disabled. To enable it, set the enable attribute to true. In the tag, specify a list of semicolon-delimited folders to which client applications have access. When this element is enabled, all clients can access the audio data in streams in the specified folders. To enable access to all audio data streamed by the server, specify / in the tag. The folder path is restricted to the application’s streams folder or folders, so do not use absolute paths in the list of folders. While you can also enable access through Server-Side ActionScript, this element allows access to the data without requiring Server-Side ActionScript. You can also override this element with the Access plug-in or Server-Side ActionScript. Example If an application is configured to store streams in folders C:\low_quality and C:\high_quality, the configuration to allow access to sample those streams is as follows:
<AudioSampleAccess enabled="true">low_quality;high_quality</AudioSampleAccess>

See also
VideoSampleAccess

AutoCommit
Specifies whether shared objects are automatically committed when they have been changed. Setting this element to false disables Flash Player function for all shared objects within this instance. Note: If the AutoCommit function is disabled, the server-side script has to call the save function or the SharedObject.commit command for the shared object to persist; otherwise, all data will be lost when the application is shut down. Example
<AutoCommit>true</AutoCommit>

See also
StorageDir, DuplicateDir, ResyncDepth, LockTimeout, MaxProperties, MaxPropertySize

Bandwidth
Container element. The elements nested in this container specify the bandwidth settings for upstream (client-to-server) and downstream (server-to-client) data. By default, the Bandwidth element includes an override parameter set to yes, which allows the values for the ClientToServer and ServerToClient elements to be overridden as well.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 98
XML configuration files reference

Contained elements
ClientToServer (Bandwidth), ServerToClient (Bandwidth)

BandwidthCap
Container element. The elements in this section specify the bandwidth settings that a user can set. By default, this element includes an override parameter set to yes, which allows the values for the ClientToServer and ServerToClient elements nested in this section to be overridden, too. Contained elements
ClientToServer (BandwidthCap), ServerToClient (BandwidthCap)

BandwidthDetection
Container element. This element contains settings for how the server detects bandwidth. Set the enable attribute to true or false to turn this feature on or off. The server can detect client bandwidth in the core server code (native) or in a server-side script (script-based). Native bandwidth detection is enabled by default and is faster than script-based because the core server code is written in C and C++. The server detects bandwidth by sending a series of data chunks to the client, each larger than the last. You can configure the size of the data chunks, the rate at which they are sent, and the amount of time the server sends data to the client. The following table lists the values available for the BandwidthDetection element.
Element
BandwidthDetection

Description Set the enabled attribute to true or false to turn this feature on or off. The maximum rate in Kbps at which the server sends data to the client. The default value is -1, which sends the data at whatever rate is necessary to measure bandwidth. The amount of data in bytes that the server sends to the client. To detect the client’s bandwidth, the server attempts to send a series of random blocks of data to the client, each time sending this much more data. For example, x bytes are sent, followed by 2x bytes, followed by 3x bytes, and so on until MaxWait time has elapsed. The number of seconds the server sends data to the client. Increasing this number provides a more accurate bandwidth figure but also forces the client to wait longer.

MaxRate

DataSize

MaxWait

Example
<BandwidthDetection enabled="true"> <MaxRate>-1</MaxRate> <DataSize>16384</DataSize> <MaxWait>2</MaxWait> </BandwidthDetection>

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 99
XML configuration files reference

Contained elements MaxRate, DataSize, MinBufferTime (Live)

Bits
This element contains the settings for Flash Player on the Windows and Macintosh platforms. Example
<Bits from="WIN 6,0,0,0" to="WIN 7,0,55,0">0x01</Bits> <Bits from="MAC 6,0,0,0" to="MAC 7,0,55,0">0x01</Bits>

See also
UserAgent

BufferRatio
Specifies the ratio of the buffer length used by server-side stream to live buffer. Example
<BufferRatio>0.5</BufferRatio>

See also
Server

Cache
Container element; contains elements that configure the cache setting for SWF verification. See also TTL, UpdateInterval

CachePrefix
Specifies the cache prefix that is passed from the origin server to the edge server. This element is set on the origin server. The edge server uses the value of this element as a relative path to locate the cache file defined in the CacheDir element. The type attribute provides additional specification for the cache prefix. The type attribute can be set to path or sname. The default is path. Examples
<CachePrefix type="path"></CachePrefix>

When the attribute type is path, the server appends the physical path of the recorded stream to the prefix.
<CachePrefix type="sname"></CachePrefix>

When the attribute type is sname, the server appends the stream name to the prefix. The cache prefix is any text with or without preset parameters. The prefix can be any name without special characters, such as \, :, *, ?, ", <, >, |. All parameters are surrounded by “?”. The server substitutes the actual names for everything specified within the “?”.

Last updated 3/2/2010

FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 100
XML configuration files reference

By default, the prefix is set to ?IP?.
Cache prefix
?IP? ?APP? ?APPINST? ?VHOST?

Actual name IP address of the server Application name Application instance vhost name

You can include the IP address in the prefix to avoid file collision. For example, the edge server might be connecting to two different origin servers with the same file in c:\data\foo.flv. Adding the IP to the prefix for these files points each file to the appropriate server. If you want more than one origin server to share the cache file, do not include the IP as a parameter. Remember the cache prefix is a relative path used by the edge server to look up the cache stream file. Examples The cache prefix creates a relative path in the edge’s CacheDir. All parameters are separated by \ or /.
<CachePrefix type="path">c:\fms\flvs\foo.flv. data/?IP?</CacheDir>

resolves to:
data/xxx.xxx.xxx.xxx/c/fms/flvs/foo.flv <CachePrefix type="path">?APPINST?/data</CacheDir>

resolves to:
app1/inst1/data/c/fms/flvs/foo.flv <CachePrefix type="path">origin1/data/</CacheDir>

resolves to:
origin1/data/c/fms/flvs/foo.flv

See also
StorageDir, DuplicateDir, CacheUpdateInterval

CacheUpdateInterval
This element defines the wait interval for updating cache streaming in the edge server. The interval is defined in milliseconds. The default value is 10 minutes. The minimum interval is 10 seconds. The maximum interval is 24 hours. Example
<CacheUpdateInterval>10</CacheUpdateInterval>

See also
StorageDir, DuplicateDir, CachePrefix

For example. For example. MsgQueue.000 bytes per second. and publish-continue. the events you use to calculate billing might not occur within a billing cycle. Logging checkpoint events to the Access log is enabled in the Vhost. The following are available as checkpoint events: connect-continue. To solve this problem. a customer can set any bandwidth limit for their applications. This allows ISPs to host applications for customers and ensure that no customer abuses the bandwidth limit. This allows ISPs to host applications for customers and ensure that no customer abuses the bandwidth limit. If your programming includes live events or 24/7 programming. but the values in the BandwidthCap section are not.xml file by default. you can enable checkpoint events. Contained elements LogInterval Client Container element.xml file. HTTPTunnel. The values in the Bandwidth section can be overridden.Last updated 3/2/2010 FLASH MEDIA SERVER 3. You can disable logging checkpoints for this application. a customer can set any bandwidth limit for their applications. Contained elements Bandwidth.000 bytes per second. or if the value is invalid.000. The values in the Bandwidth section can be overridden. Example <ClientToServer>1250000</ClientToServer> See also ServerToClient (Bandwidth) ClientToServer (BandwidthCap) Specifies the maximum bandwidth a client can send to the server. BandwidthCap. or change the checkpoint interval of this application. but the values in the BandwidthCap section are not. The default bandwidth is 100. but cannot exceed the caps set by the ISP. the server uses the value set in the Vhost. ClientToServer (Bandwidth) Specifies the bandwidth the client can use for sending data upstream to the server. the Client element includes an override="no" parameter. OutChunkSize.5 CONFIGURATION AND ADMINISTRATION GUIDE 101 XML configuration files reference Checkpoints Many companies use statistics from the access log to bill customers. Checkpoint events log bytes periodically during an event. By default.250. play-continue. The default bandwidth is 1.xml file. The elements nested within this container configure the client. You can configure this value in the Bandwidth section of XML and in the BandwidthCap section of XML. but cannot exceed the caps set by the ISP. BandwidthDetection. MaxMessageSizeLosslessVideo. If the checkpoint interval is not specified in the Application. You can configure this value in the Bandwidth section of XML and in the BandwidthCap section of XML. Individual applications cannot override how the elements in the Client section are configured. .

5 CONFIGURATION AND ADMINISTRATION GUIDE 102 XML configuration files reference Example <ClientToServer>100000000</ClientToServer> See also ServerToClient (BandwidthCap) CombineSamples Container element. Interface DataSize Specifies the amount of data in bytes that the server sends to the client. MaxSamples. Subscribers Connections Container element. and so on until MaxWait time has elapsed.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <DataSize>16384</DataSize> See also MaxRate. The elements in this section configure debug connections. including the maximum number of connections and the value for application. Contained elements MaxTimeOut (Connections). followed by 2x bytes. Reuse. This strategy saves the CPU and bandwidth overhead when transmitting individual audio packets only. x bytes are sent. HiCPU. followed by 3x bytes. Note: Use this strategy of combining sound samples advisedly during periods of high CPU usage. Contained elements AllowDebugDefault. the server attempts to send a series of random blocks of data to the client. The server conserves system resources by combining sound samples. as it can cause latency. For example. MaxPendingDebugConnections . each time sending this much more data. The elements in this section configure the HTTP connections for this application. Contained elements LoCPU. To detect the client’s bandwidth. MinBufferTime (Live) Debug Container element.allowDebug.

the numprocs attribute must be set to a value higher than 0 or 1. Specifying rtmp includes rtmp and rtmpt connections. The default value is 1. By default. insts. Each virtual host is allotted three core processes. Note: There is no limit to the value of the numprocs attribute. or rtmpe. which allows all protocols to connect to the server. the value of Distribute can be insts or clients. or clients. The default value is insts. This feature is turned on by default. apps. For example. which contain clients. Specifying rtmpe includes rtmpe and rtmpte connections. which means that the server scans only one subfolder level. Distribute Specifies how to distribute application instances to processes. the following XML disallows rtmp and rtmps and only allows clients to connect over rtmpe: <DisallowedProtocols>rtmp. but you should never need more than 40.Last updated 3/2/2010 FLASH MEDIA SERVER 3. three core processes will run. Any protocol not specified is allowed. To use this feature. Specify protocols in a comma delimited list. This tag contains a numprocs attribute. rtmps. Specifying zero scans the parent folder and no subfolders. If the value of Scope is app. the server uses the value immediately lower than the one specified in the Scope tag. See also Enabled DirLevelSWFScan Specifies the number of levels of subfolders within a parent folder to scan for SWF files. so systems that use multiple virtual hosts will generate more running processes. The default value of the numprocs attribute is 3. The value of the Distribute tag must be a scope that is lower in order than the value in the Scope tag. Specifying a positive value scans that number of subfolder levels. which specifies the maximum number of processes to run concurrently. The default value is false. meaning each application instance runs in its own process. for all your applications and application instances under a single virtual host. which contain instances. Specifying a negative value scans all subfolder levels. You can specify rtmp. With the default configuration. The parent folder is specified in the SWFFolder element. In other words. SWFVerification DisallowedProtocols Specifies which protocols cannot be used to connect to an application. See also SWFFolder. which contain applications.5 CONFIGURATION AND ADMINISTRATION GUIDE 103 XML configuration files reference Diagnostic Specifies whether diagnostic logging for the message queue is enabled. The following table lists the values available for the Distribute element: . the value of Distribute can be vhosts. if the value of Scope is adaptor.rtmps</DisallowedProtocols> The default value is blank. Scopes have an enclosing relationship with a strict ordering: adaptors contain virtual hosts.

the messages wouldn't reach everyone in the chat because they’d be split into separate processes. This location serves as a backup for shared object files and recorded stream files. in seconds. you must also set the Distribute numprocs attribute to a value greater than 1. The minimum wait time is 1 second. change the appName attribute to "true". This location must already exist when a shared object is copied to it. If you choose this value. <DuplicateDir appName="true">c:\backupSharedObjects</DuplicateDir> <DuplicateDir appName="true">c:\backupStreams</DuplicateDir> See also StorageDir Duration This element instructs the server how long. This is the default value. Each application instance runs in its own process. Specifies the physical location where duplicate copies of shared objects or recorded streams are stored. MaxFailures. clients Example <Distribute numproc="1"></Distribute> See also Scope. Example To include the application name in the paths for the backup files. There is effectively no maximum value (the maximum is the maximum value of a 32-bit integer).xml file: one is in the SharedObjManager container and one is in the StreamManager container. Use this value for stateless applications—applications that don’t require clients to interact with other clients and don’t have clients accessing live streams. All instances of an application run together in a process. Chat and gaming applications are not stateless because all clients share the application state. Most vod (video on demand) applications are stateless because each client plays content independently of all other clients. The default wait time is 3 seconds. to wait before it notifies the client when the audio has stopped in the middle of a live or recorded audio stream. if a shared chat application were set to client.Last updated 3/2/2010 FLASH MEDIA SERVER 3. This is one of two DuplicateDir elements in the Application.5 CONFIGURATION AND ADMINISTRATION GUIDE 104 XML configuration files reference Value vhosts apps insts Description All instances of applications in a virtual host run together in a process. For example. Each client connection runs in its own process. RecoveryTime DuplicateDir Note: This feature has been deprecated. LifeTime. Example <Duration>3</Duration> .

Example <EnhancedSeek>true</EnhancedSeek> See also KeyFrameInterval EraseOnPublish When set to true. See also Diagnostic EnhancedSeek This element enables or disables fine-tuning of the seeking performance within streams by creating a keyframe.0" and From="WIN 9. For H.0. See also UserAgentExceptions . See also Live (StreamManager) Exception This element indicates that a specific user agent is an exception to authentication. By default.0 as its UserAgent. Add To="WIN 9. This is a string comparison with editing to make all numeric fields equal length. The default value is false.28. the server erases a recorded stream when a new publisher starts publishing.28.5 CONFIGURATION AND ADMINISTRATION GUIDE 105 XML configuration files reference See also Password Enabled Specifies whether diagnostic logging for the message queue is enabled. Note: The server generates new keyframes for Sorenson Spark-encoded FLV files. The default value is true.Last updated 3/2/2010 FLASH MEDIA SERVER 3.0. a new keyframe is dynamically generated to provide smooth seeking to that index point.0" and only that version is an exception.264-encoded video. using a specific Flash Player will report WIN 9. When set to true. For On2 VP6. this setting is disabled and the server does not erase a recorded stream.28. Keyframes improve the visual display of video files while seeking. For example. The server does not insert keyframes and all seeks begin at the nearest existing keyframe.0. the new keyframe is calculated and generated in Flash Player 9 Update 3 or later. the new keyframe is calculated and generated in Flash Player 9a or later. Use the from and to attributes to indicate the lowest and highest versions to except.

This allows two levels of permissions: file-level access (a value of false). Example <HiCPU>80</HiCPU> . which allow access to a particular file only. so the server can send out the messages immediately.5 CONFIGURATION AND ADMINISTRATION GUIDE 106 XML configuration files reference FileObject Container element.Last updated 3/2/2010 FLASH MEDIA SERVER 3. See also Queue. and folderlevel access (a value of true). This element is important for streaming data-only messages. See also SWFVerification FirstHashTimeout This element defines the maximum amount of time that a client can use to provide its first verification to the server. Example <FolderAccess>false</FolderAccess> See also Access HiCPU This element instructs the server to start combining samples when CPU utilization is higher than the specified percentage of CPU resources. MaxQueueDelay. MaxQueueSize. AccumulatedIFrames FolderAccess Configures the level of permission that the Access plug-in can set for accessing streams and shared objects. Contained elements VirtualDirectory FinalHashTimeout This element defines the maximum amount of time that a client can use to provide its final verification to the server. The VirtualDirectory element nested within this container configures the JSEngine file object settings. See also SWFVerification FlushOnData Specifies whether the server flushes the message queue when a data message arrives. which allows access to a particular directory. The default is true. The default percentage of utilization is 80.

Selecting too small a delay value for the above parameters will increase the polling frequency and reduce network performance and efficiency. Redirect HTTP1_0 This element determines whether or not the server can use the HTTP 1.com:8080</Host> See also Port. Type. Proxy. The elements nested within this container configure the parameters for HTTP tunnelling (sending RTMP packets through HTTP). LoCPU. . The value of the Host element can be the host name or an IP address. The Application. Connections. Tunnel. The frequency of polling affects both network performance and the efficiency of the HTTP protocol. The default is false. Verbose. Redirect HTTPTunnel Container element.example.xml configuration file offers three settings for these parameters.5 CONFIGURATION AND ADMINISTRATION GUIDE 107 XML configuration files reference See also Subscribers. The elements in this section configure the HTTP connection settings for this application. disallowing the use of the HTTP 1. Password HTTP Container element. Example <Host>www. Proxy.0 protocol. The tunnelling protocol is based on the client continuously polling the server. Example <HTTP1_0>false</HTTP1_0> See also HTTP.0 protocol. Connections. Contained elements HTTP1_0. MaxSamples Host This element identifies the HTTP proxy. The IdleAckInterval and IdlePostInterval elements control the polling frequency on a per-client basis. The following table presents these settings. The port number can also be specified in the Port element.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Verbose. Username. Selecting too high values can adversely affect the interactivity of the application and the server.

This interval implies that the client may not be able to reach the server for the selected duration. the server will not be able to send any data to the client for the selected duration. but posting is necessary to provide the server with an opportunity to send data downstream to the client. WriteBufferSize IdleAckInterval Specifies the maximum time the server may wait before it sends back an ack (acknowledgement code) for an idle post sent by the client. The server may respond sooner than the value of this element if it has data to send back to the client or if some other client is being blocked by the current idle request. Example <IdlePostInterval>512</IdlePostInterval> . Example <IdleAckInterval>512</IdleAckInterval> See also IdlePostInterval. the default value of 512 milliseconds is used. Note: At times. WriteBufferSize IdlePostInterval Specifies how long Flash Player should wait before sending an idle post to the server. Idle posts are sent when Flash Player has no data to send. The interval cannot be set to a negative value. The default interval is 512 milliseconds. IdleAckInterval.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The interval for an idle post ranges from 0 to 4064 milliseconds. MimeType.5 CONFIGURATION AND ADMINISTRATION GUIDE 108 XML configuration files reference Acceptable Latency Low Medium High IdlePostInterval 128 milliseconds 512 milliseconds 1024 milliseconds IdleAckInterval 256 milliseconds 512 milliseconds 2048 milliseconds Example <HTTPTunnel> <IdlePortInterval>512</IdlePostInterval> <IdleAckInterval>512</IdleAckInterval> <MimeType>application/x-fcs</MimeType> <WriteBufferSize>16</WritebufferSize> </HTTPTunnel> Contained elements IdlePostInterval. MimeType. If the IdlePostInterval element is set to a value that lies outside of this range.

The property name corresponds to the tag’s name. an IP address. The default interval is 3 seconds.Last updated 3/2/2010 FLASH MEDIA SERVER 3. or a host name. Defining properties in an Application. respectively: <JSEngine> <config> <user_name>jdoe</user_name> <dept_name>engineering</dept_name> </config> </JSEngine> .xml file in an application folder creates properties available for that application only.xml file creates properties available for all applications on a virtual host. Defining properties in the default Application. In the server Application. Silence messages are used to support older versions of Flash Player. Reuse Interval Specifies the interval in milliseconds for sending silence messages when no audio is being published to a live stream. create an XML tag. Example <Interface>www. Example <Interval>3</Interval> See also SendSilence JSEngine Container element.5 CONFIGURATION AND ADMINISTRATION GUIDE 109 XML configuration files reference See also IdleAckInterval. The server only sends the silence message to clients specified in the UserAgent element in the Client section. The name can be an interface name. Set this to 0 to disable silence message transmission. you can define properties for the server-side Application object. with the values jdoe and engineering. Bit-flag 0x01 is used to control the silence message. and the property value corresponds to the tag’s contents. WriteBufferSize Interface This element defines the name to use as the outgoing network interface. Example The following XML fragment defines the properties user_name and dept_name.com</Interface> See also MaxTimeOut (Connections).example.xml configuration files. To define a property. MimeType. The elements nested within this container configure the JavaScript engine.

not from application. Contained elements MaxCores. MaxTimeOut (JSEngine). NetConnection KeyFrameInterval This element defines how often to generate and save keyframes in an FLV file. MaxLatency. Contained elements RuntimeSize. Queue. or 43%. DuplicateDir. or 17%. Process rollover happens only when the Scope element is set to inst. CacheUpdateInterval LifeTime Container element. and the amount of time the server waits before allowing another publisher to take over a live stream. PublishTimeout. The value of this element is defined in milliseconds. EraseOnPublish . For example. The elements nested within this container configure the intermediate frames in a live stream and the message queue. MaxGCSkipCount.config. however.prop_name application. Setting a higher value for the interval. The initial value is 60000. the server uses a default value of 1000. which is an increase of 13 KB. Setting this element to a higher value than the initial value reduces the number of keyframes added to the FLV file and thus reduces the file size. RollOver Live (StreamManager) Container element.5 CONFIGURATION AND ADMINISTRATION GUIDE 110 XML configuration files reference To access the property in server-side code. Example <KeyFrameInterval>1000</KeyFrameInterval> See also StorageDir. use the syntax in either of these examples: application. a 15-second video with a file size of 76 KB is increased only to 89 KB when the KeyFrameInterval element is set to 5000. Note: Be aware of the correlation between file size and accuracy of seeking when you set this value. ScriptLibPath. set this element to a nonzero value.config.property. Contained elements AccumulatedIFrames. However. reduces the seeking accuracy. To roll over such processes.config["prop_name"] Note: The properties you define are accessible from application. XMLSocket. This element determines the lifetime of core processes. which is the recommended value. which is an increase of 33 KB. The same video has a size of 109 KB with the KeyFrameInterval element set to 1000.property.Last updated 3/2/2010 FLASH MEDIA SERVER 3. StartClockOnPublish. if this tag is unspecified or set to a value out of range. FileObject.

MaxProperties. Contains elements that control the server logs. HiCPU. . JSEngine. Example <LoadOnStartup>false</LoadOnStartup> See also Process. MinBufferTime (Live) LoadOnStartup This element determines whether or not the server loads an application instance when the server starts. If you set this element to true. The elements nested within this container configure live audio. AutoCommit. The timeout value is specified in seconds. StreamManager LockTimeout Specifies the timeout value before automatically unlocking a shared object if there is a client waiting for an update. ResyncDepth. MaxAppIdleTime. MaxSamples Logging A container element. Example <LoCPU>60</LoCPU> See also Subscribers.5 CONFIGURATION AND ADMINISTRATION GUIDE 111 XML configuration files reference Live (MsgQueue) Container element. The default value is false.Last updated 3/2/2010 FLASH MEDIA SERVER 3. an instance of each application on the server will be loaded at start-up. MaxPropertySize LoCPU This element instructs the server to stop combining samples when CPU utilization is lower than the specified percentage of CPU resources. Contained elements MaxAudioLatency. DuplicateDir. which instructs the server to wait for an indefinite time. The default percentage of utilization is 60. The default value is -1. Having an application instance loaded at server start-up saves time when the first client connects to that application. Example <LockTimeout>-1</LockTimeout> See also StorageDir.

See also Allow MaxAggMsgSize Specifies the maximum size in bytes of the aggregate messages created from the message queue. ApplicationGC MaxAudioLatency Specifies that live audio should be dropped if audio exceeds the time specified. Time is expressed in milliseconds. it is not evaluated as idle.Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 112 XML configuration files reference Contained elements Access (Logging) LogInterval The interval at which the server logs checkpoint events. Example <MaxAudioLatency>2000</MaxAudioLatency> See also MinBufferTime (Live) . If the application instance is loaded with no clients connected. See also Checkpoints Max This element defines the maximum number of redirects allowed. An application instance is evaluated as idle after all clients disconnect from it. MaxQueueDelay. JSEngine. AccumulatedIFrames MaxAppIdleTime Specifies the maximum time an application instance can remain idle with no clients connected before it is unloaded from the server’s memory. The default value is 4096. in seconds. Example <MaxAppIdleTime>600</MaxAppIdleTime> See also Process. MaxQueueSize. See also Queue. The maximum idle time is specified. LoadOnStartup. The default is 600 seconds (10 minutes). StreamManager. FlushOnData. when aggregate messages are enabled.

The default value is -1.5 CONFIGURATION AND ADMINISTRATION GUIDE 113 XML configuration files reference MaxBufferRetries Specifies the maximum number of attempts to start buffering stream data. MaxSizeCap. For more information on setting the maximum number of core processes. Setting the value -1 removes the maximum duration cap. DuplicateDir. See also MaxDurationCap. It is only applicable in edge servers. MaxSize (Recording) MaxDurationCap Specifies the cap on the maximum duration (in seconds) of a recorded file.Last updated 3/2/2010 FLASH MEDIA SERVER 3. This configuration tag prevents the server from indefinitely trying to buffer data that is never delivered by the origin server. in seconds. The value -1 means there is no maximum duration. The value 0 disables recording. The default value of 128 is sufficient in most cases. a customer can set any MaxDuration for their applications. MaxSize (Recording) . CachePrefix. CacheUpdateInterval MaxCores The value of this element determines how many core processes can exist for an application. of a recorded file. Example <MaxBufferRetries>128</MaxBufferRetries> See also StorageDir. Note: The F_STREAM_RECORD_MAXDURATION field in the Authorization plug-in can override this value. The default value is zero. By default. Setting the value 0 disables recording. MaxSizeCap. the MaxCores function is disabled. Values set in the MaxDuration element or in Server-Side ActionScript cannot exceed this value. Note: The F_STREAM_RECORD_MAXDURATION field in the Authorization plug-in can override this value. RollOver MaxDuration Specifies the maximum duration. See also MaxDuration. but cannot exceed the MaxDurationCap set by the ISP. For example. This element allows ISPs to host applications for customers and ensure that no customer abuses the MaxDuration limit. see “Configure how applications are assigned to server processes” on page 16. Set this parameter when you deploy a DVR application to prevent the disk from exceeding its capacity. Example <MaxCores>0</MaxCores> See also LifeTime. The default value is -1.

If MaxGCSkipCount is set to 0. XMLSocket.xml file to override the value set in the Server.xml file by default. NetConnection MaxFailures The value of this element determines the maximum number of core process failures that can occur before a core process is disabled. the server does not launch a core process until some minimum recovery time has elapsed. so in some cases you must force the server to perform GC regardless of the JS engine state. ScriptLibPath. However. the server forces a GC when the skip count exceeds the value in MaxGCSkipCount.xml file. If MaxGCSkipCount is set to a positive value. Distribute. Example <MaxFailures>2</MaxFailures> See also Scope.FileObject.xml file to override the value set in the Vhost. LifeTime. This value is set in the Server. Having a time lag for recovery avoids a denial-of-service action. By default. This element determines the frequency of the garbage collection process. See also AutoCloseIdleClients MaxInitDelay The maximum number of seconds used to process SWF files. MaxTimeOut (JSEngine). Example <MaxInitDelay>5</MaxInitDelay> Example SWFVerification . Example <MaxGCSkipCount>-1</MaxSGCSkipCount> See also RuntimeSize.xml file.5 CONFIGURATION AND ADMINISTRATION GUIDE 114 XML configuration files reference MaxGCSkipCount Specifies the maximum number of times that the server will skip garbage collection (GC) when the JS engine is busy.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The default value is 5 seconds. Once the core processes are disabled. the JS engine does not necessarily perform GC when it is busy. which can happen when a faulty core consumes all CPU resources by repeatedly launching itself. You can set the value in the Application. RecoveryTime MaxIdleTime The maximum time a client can be idle before the server closes the connection. the server only performs GC when the JS engine is not busy. You can set the value in the Vhost. the server forces a GC regardless of the JS engine state.

) Once the specified number is reached. Example <MaxPropertySize>-1</MaxPropertySize> . To specify unlimited size.Last updated 3/2/2010 FLASH MEDIA SERVER 3. LockTimeout. the timestamp is the last message time.5 CONFIGURATION AND ADMINISTRATION GUIDE 115 XML configuration files reference MaxLatency The maximum latency. of incoming messages in a live stream. AccumulatedIFrames. ResyncDepth. If the injection time is larger than MaxLatency. this setting determines the timestamp of the message. Example <MaxPendingDebugConnections>50</MaxPendingDebugConnections> See also AllowDebugDefault MaxProperties The maximum number of properties for each shared object. Otherwise. MaxPropertySize MaxPropertySize The maximum size in bytes for each property of a shared object. use -1. Example <MaxProperties>-1</MaxProperties> See also StorageDir. in milliseconds. When a server-side script injects a data message into a live stream. See also Live (StreamManager) MaxMessageSizeLosslessVideo Specifies the maximum size of messages for screen-sharing packets. the server adds the time difference between the last message time and the injection time to the timestamp of the data message. The default is 50. debugging connections are disabled. To specify unlimited. UserAgent MaxPendingDebugConnections Specifies the maximum number of pending debug connections. AutoCommit. The minimum value is 0. the oldest pending debug connection is rejected to create space. Example <MaxMessageSizeLosslessVideo>0</MaxMessageSizeLosslessVideo> See also OutChunkSize. Access. DuplicateDir. use -1. (If the number is set to 0. The default value is 500.

The default value of -1 sends the data at whatever rate is necessary to measure bandwidth without throttling. Example <MaxRate>-1</MaxRate> See also DataSize. MaxProperties MaxQueueDelay Specifies how often the server will flush the message queue. MinBufferTime (Live) MaxSamples Specifies how many sound samples can be combined into one message. AggregateMessages (Queue) MaxQueueSize Specifies how often the server will flush the message queue. MaxQueueDelay. in bytes. See also Queue. of intermediate frames that a live stream can hold in the buffer. A value of 0 disables queuing. MaxQueueSize. A default value of -1 means the size of intermediate frames is unlimited. FlushOnData. AggregateMessages (Queue) MaxRate Specifies the maximum rate in Kbps at which the server sends data to the client. FlushOnData. ResyncDepth. LockTimeout. If the buffer size is larger than MaxSize. The default value is 500 milliseconds. See also Queue. in milliseconds.5 CONFIGURATION AND ADMINISTRATION GUIDE 116 XML configuration files reference See also StorageDir. The default number of samples is 4. DuplicateDir. AutoCommit.Last updated 3/2/2010 FLASH MEDIA SERVER 3. This setting prevents the buffer from growing too large and should be set larger than the total size of intermediate frames between keyframes. This enables clients to catch up to the latest message even if they join between keyframes. See also Audio MaxSize (AccumulatedIFrames) Specifies the maximum size. in kilobytes. the server clears the messages. Example <MaxSize>-1</MaxSize> . The default value is 4096. The buffer contains a history of the video messages up to the last keyframe.

This element allows ISPs to host applications for customers and ensure that no customer abuses the MaxSize limit. CacheUpdateInterval. in seconds. The value 0 disables recording. The buffer contains a history of the video messages up to the last keyframe. MaxDurationCap MaxSizeCap Specifies the maximum size cap. The value 0 disables recording. HiCPU MaxSize (Recording) Specifies the maximum size. but cannot exceed the MaxSizeCap set by the ISP. The default value is -1. of a recorded file. Example <MaxTime>-1</MaxTime> . This setting prevents the buffer from growing too large and should be set larger than the keyframe interval. the server clears the messages.5 CONFIGURATION AND ADMINISTRATION GUIDE 117 XML configuration files reference See also Subscribers. See also MaxSizeCap. The default value of -1 means the duration is unlimited. This enables clients to catch up to the latest message even if they join between keyframes. MaxBufferRetries MaxTime Specifies the maximum duration. MaxDuration. of intermediate frames that a live stream can hold in the buffer. in kilobytes. Set this parameter when you deploy a DVR application to prevent the disk from exceeding its capacity. MaxDurationCap MaxStreamsBeforeGC Specifies that garbage collection (GC) should be forced if the stream list grows over the set value. MaxDuration. Note: The F_STREAM_RECORD_MAXSIZE field in the Authorization plug-in can override this value. The value -1 means there is no maximum size. CachePrefix. of a recorded file. See also MaxSize (Recording). Example <MaxStreamsBeforeGC>-1</MaxStreamsBeforeGC> See also StorageDir. For example. DuplicateDir. Note: The F_STREAM_RECORD_MAXSIZE field in the Authorization plug-in can override this value. GC occurs during the application GC interval.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The default value is -1 (unlimited). in kilobytes. The value -1 means there is no maximum size. If the duration in the buffer is larger than the MaxTime. The default value is -1. a customer can set any MaxSize for their applications. LoCPU.

FileObject. NetConnection MaxTimeOut (Connections) This element defines the maximum time for a transfer to be completed. then the script is evaluated as a runaway script and its execution is terminated. after the applications and scripts have been thoroughly tested. Interface MaxTimeOut (JSEngine) The maximum time. NetConnection MaxUnprocessedChars Specifies how much data can be received from an XML server (without receiving an end tag) before XMLSocket closes the connection. FileObject. the risk of aborting correctly functioning operations increases. In a production environment. MaxGCSkipCount.5 CONFIGURATION AND ADMINISTRATION GUIDE 118 XML configuration files reference See also RuntimeSize. If its execution takes longer than the maximum allowed time. a script can take to execute a JavaScript (Server-Side ActionScript) function. This setting may be useful in a debugging environment. ScriptLibPath. MaxGCSkipCount. Example <MaxTimeOut>60</MaxTimeOut> See also Reuse. but it also forces the client to wait longer. you should set this element to a more realistic value that does not impose limits on the time scripts take to execute.maxUnprocessedChars. If the value of this element is too low. This can be overridden by each XMLSocket by specifying the property XML. Setting a maximum time to execute a script prevents infinite looping in scripts. in seconds.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The default value is 0 and no checks are performed to detect runaway scripts. Increasing this number provides a more accurate bandwidth figure. Example <MaxUnprocessedChars>4096</MaxUnprocessedChars> See also XMLSocket MaxWait This element specifies the number of seconds to wait before the server sends data to the client. Example <MaxTimeOut>0</MaxTimeOut> See also RuntimeSize. . Operations such as DNS lock-ups may take more time. but that number cannot exceed the number specified in this element. XMLSocket. The default time is 60 seconds. ScriptLibPath. XMLSocket.

DataSize MimeType Specifies the default MIME (Multi-purpose Internet Mail Extensions) type header sent on tunnel responses. The value cannot be set below this by Flash Player. WriteBufferSize MinBufferTime (Live) Specifies the default buffer length in milliseconds for the live audio and video queue.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The server generally uses the MIME type specified by the incoming requests. The default value is 0. IdlePostInterval. The server will use the entry for the MIMEType element only when it is unable to determine the MIME type from the incoming requests. Example <MinBufferTime>2000</MinBufferTime> See also MaxAudioLatency MinBufferTime (Recorded) Specifies the default buffer length in milliseconds for audio and video. which allows the current and all future versions. Example <MinGoodVersion>0</MinGoodVersion> . Example <MinBufferTime>2000</MinBufferTime> See also Recorded MinGoodVersion Specifies the minimum accepted version of SWF verification allowed by the server.5 CONFIGURATION AND ADMINISTRATION GUIDE 119 XML configuration files reference Example <MaxWait>4096</MaxWait> See also MaxRate. Example <MimeType>application/x-fcs</MimeType> See also IdleAckInterval.

objectEncoding property to either 0 for AMF0 or 3 for AMF3. Streams that use H. The default can be overridden for each individual NetConnection by setting the NetConnection.Last updated 3/2/2010 FLASH MEDIA SERVER 3. See also Server MsgQueue Container element.264 or any other pipelined codec need messages to begin playback. Setting this value to less than 64 may cause content with a low FPS to delay before starting. Contained elements ObjectEncoding NotifyAudioStop Container element. Recorded. Example <NotifyAudioStop enabled="false"></NotifyAudioStop> Contained elements Duration ObjectEncoding Specifies the default object encoding to use for SSAS NetConnection. Server NetConnection Container element. Contained elements Live (MsgQueue). The default value is 64. This can be AMF0 or AMF3. The element nested within this container specifies object encoding to use for SSAS NetConnection.5 CONFIGURATION AND ADMINISTRATION GUIDE 120 XML configuration files reference See also SWFFolder. This setting ensures that regardless of the buffer setting there are enough messages to begin playback quickly. . The default is AMF3. The Duration element nested within this container determines whether or not the server is notified when an audio transmission ending on a stream is encountered. The elements nested within this container configure live and recorded audio. UserAgentExceptions MinQueuedVideo The minimum number of video messages to queue at the start of a stream.

The server breaks stream content into chunks of this size. Note that older clients might not support chunk sizes larger than 1024 bytes. Type. Live (StreamManager). This can have a minimum value of 128 bytes and a maximum value of 65536 bytes. add application logic to avoid stream name collision. See also Host. Specifies whether a second client is able to take over the ownership of a live stream when the stream is already published by another client. SendDuplicateStart. HTTPTunnel. Type. The default value is 4096. Tunnel. Username . Larger values reduce CPU usage but cause larger writes that can delay other content on lower bandwidth connections. If the chunk setting is larger than these clients can support. The default value is false. If set to true. SendDuplicateOnMetaData Password Specifies the password for connecting to the proxy. BandwidthDetection. the chunk setting is capped at 1024 bytes. Password. Example <OutChunkSize>4096</OutChunkSize> See also Bandwidth. See also Host. MaxMessageSizeLosslessVideo OverridePublisher Deprecated. Username Port Specifies the proxy port to connect to if the port is not specified as part of the host in the Host element. MsgQueue.Last updated 3/2/2010 FLASH MEDIA SERVER 3. see the PublishTimeout element.5 CONFIGURATION AND ADMINISTRATION GUIDE 121 XML configuration files reference Example <ObjectEncoding>AMF3</ObjectEncoding> See also NetConnection OutChunkSize Specifies the RTMP chunk size in bytes to use in all streams for this application. Tunnel. BandwidthCap. Port. Example <OverridePublisher>true</OverridePublisher> See also Audio.

Process rollover happens only when the Scope element is set to inst. Value Scope Description Specifies the level at which application instances are assigned to core processes. the server sends messages through multiple channels and prioritizes messages based on the message type. Scopes have an enclosing relationship with a strict ordering: adaptors contain virtual hosts. Specifies how to distribute application instances to processes. Distribute LifeTime MaxFailures RecoveryTime Contained elements Scope. The elements nested within this container configure the HTTP Proxy settings. apps. which contain applications. which contain clients. LifeTime. insts. Specifies the lifetime of core processes. The following table lists descriptions of the contained elements. If the value is set to true. if the value of Scope is adaptor. prioritization is set to false.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Tunnel. or clients). Distribution may be turned off by setting numproc to 0 or 1. Proxy Container element. By default. Specifies the recovery time for a core. Username. The elements nested within this container determine how a core process is managed. Password . Type. Messages are sent out through one channel and all messages have the same priority. Distribute. This setting is relevant for multi-point publishing. RecoveryTime. The value of the Distribute tag must be a scope that is lower in order than the value in the Scope tag (for example. MaxFailures. The value for this element determines the maximum number of core process failures that can occur before a core process is disabled. which is the correct setting to avoid possible latency when server-side NetStream objects are used to publish messages to remote servers. Contained elements Host. the value of Distribute can be vhosts. Port. which contain instances.5 CONFIGURATION AND ADMINISTRATION GUIDE 122 XML configuration files reference Prioritization Specifies whether outgoing messages are prioritized by message type when sending across a server-to-server connection. as follows (where 1 has the highest priority): 1 Data 2 Audio 3 Video See also Server Process Container element.

You can disable queuing so that individual messages are immediately sent to subscribers. FlushOnData. contains elements that configure the settings of the message queue.5 CONFIGURATION AND ADMINISTRATION GUIDE 123 XML configuration files reference PublishTimeout Specifies how long in milliseconds the server waits to receive a response from a publisher when another client tries to publish to the same stream. Contained elements MaxQueueSize. disable this setting by setting the value of the tag to -1. suppose client 1 and client 2 both request to play myStream. This tag replaces the OverridePublisher tag. For example. Flash Media Server pings the first publisher and waits to receive a response. To prevent the server from pinging the first client. an E_FILENAME_TRANSFORM event occurs in the Authorization plug-in. This tag is applicable when using the Authorization plug-in. To disable queuing. QualifiedStreamsMapping Enables mapping of virtual stream paths to different physical locations. Contained elements MinBufferTime (Recorded) Recording Container element. Queue Container element. Contained elements MaxDuration. The default value is 2000 milliseconds. The element nested within this container specifies the ratio of buffer length used by the server-side stream to the live buffer. The elements nested within this container specify the duration and file size of files recorded by the server. When a client requests to play a stream. MaxSizeCap .flv for client 1 and c:\video2\myStream. If the first publisher fails to respond within the time specified in this tag.flv. MaxSize (Recording).Last updated 3/2/2010 FLASH MEDIA SERVER 3.flv for client 2. the server allows the second publisher to take over the live stream. You can remap the stream to c:\video1\myStream. A message queue is used to buffer incoming messages from the publisher so that the server can send messages in chunks to the subscribers. AggregateMessages (Queue) Recorded Container element. MaxQueueDelay. MaxDurationCap. You can map the stream differently for each client in the F_STREAM_PATH property of your Authorization plug-in code. set the enabled attribute to false. If a client tries to publish to the same live stream that is being published by another client.

The recovery time for a core process is specified. which happens when a faulty core process consumes all CPU time by repeatedly launching itself. LifeTime. The shared object is resynchronized when its version number is greater than the head version minus the current version. Contained elements Allow. The default is to reuse connections. The default value of -1 sends a resynchronized version of the file with every connection. DuplicateDir. The server will not launch a core process until some minimum recovery time has elapsed. MaxPropertySize Reuse This element configures whether or not the server explicitly closes the HTTP connection after each transfer. Example <RecoveryTime>300</RecoveryTime> See also Scope. UnrestrictedAuth ResyncDepth This element instructs the server to resynchronize a shared object file. The time lag for recovery can avoid a denial-of-service action. A value of 0 disables any checking for process failures. AutoCommit. Example <ResyncDepth>-1</ResyncDepth> See also StorageDir. Set this to false to use a new connection after every transfer. Note: Loading an application with Flash Media Administration Server tools or APIs bypasses this check. MaxFailures Redirect Container element. MaxProperties. LockTimeout. The elements nested within this container configure the settings for redirecting the HTTP connection. Max. in seconds. Interface .5 CONFIGURATION AND ADMINISTRATION GUIDE 124 XML configuration files reference RecoveryTime Specifies the recovery time for a core. Distribute.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <Reuse>true</Reuse> See also MaxTimeOut (Connections).

an out-ofmemory error occurs and the application instance is shut down.xml file in an application’s folder apply only to that application. you must increase the engine size. The following table lists the values available for the Scope element. see “Configure how applications are assigned to server processes” on page 16. All subsequent connections are directed to the new core. FileObject.exe (Windows) fmscore (Linux). XMLSocket. . The rollover functionality is disabled by default. ScriptLibPath. The default size is 1024 kilobytes. Settings made in an Application. which is the equivalent of 1 megabyte.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Settings in an Application. Application instances run in processes called FMSCore. NetConnection Scope This element determines the level at which application instances are assigned to core processes. Example <RuntimeSize>1024</RuntimeSize> See also MaxGCSkipCount.exe (Windows) or fmsmaster (Linux). Starting Flash Media Server starts a process called FMSMaster.xml file in a virtual host folder apply to all applications running in that virtual host. MaxTimeOut (JSEngine). For more information on rollover processes. The default value is 0 (seconds). Only one master process can run at a time. Example <Rollover>0</RollOver> See also MaxCores RuntimeSize Specifies the maximum size in kilobytes that a particular application instance can use to run Server-Side ActionScript code before the server removes unreferenced and unused JavaScript objects. but many core processes can run at the same time. The default value applies when the engine size lies outside of these limits. If your application consumes a significant amount of memory.5 CONFIGURATION AND ADMINISTRATION GUIDE 125 XML configuration files reference RollOver Specifies how many seconds a core process can be in use before the server creates a new core process. If you create a new script object that will cause the runtime size of the application instance to exceed the value of this element. increasing the engine size to 30720 (30 MB) is sufficient to run intensive Server-Side ActionScript operations. The master process is a monitor that starts core processes when necessary. After the time limit for a core is reached. In most cases. The lower and upper limits on the size of the JavaScript engine are 10 kilobytes and 51200 kilobytes (50 megabytes). a new core is instantiated.

in sequence. All instances of a single application run together in a process. MaxGCSkipCount.5 CONFIGURATION AND ADMINISTRATION GUIDE 126 XML configuration files reference Value adaptor vhost app inst Description All application instances in an adaptor run together in a process. Example <SendDuplicateOnMetaData>true</SendDuplicateOnMetaData> See also SendDuplicateStart . If the script file is not found there. These paths are used to resolve a script file that is loaded with the load API. The default value is true. the script engine searches. FileObject.asc file is located. the list of paths specified in this element. MaxFailures. Each application instance runs in its own process.asc or application_name. All application instances in a virtual host run together in a process. you must also set the Distribute numprocs attribute to a value greater than 1. If you choose this value. The server first looks in the location where the main.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The following values are available: • • • true sends onMetaData for the play and seek commands. Example <ScriptLibPath>${APP.asc file with the load() method. regardless of the command. XMLSocket. Example <Scope>vhost</Scope> See also Distribute. LifeTime. If no onMetaData is found at the start position. once falls back to FMS 1. This is the default value. false sends onMetaData for play only. MaxTimeOut (JSEngine). no onMetaData is sent.x behavior and sends onMetaData based on the start position. NetConnection SendDuplicateOnMetaData Specifies whether an onMetaData message is sent at the beginning of video files when the play and seek commands are called.JS_SCRIPTLIBPATH}</ScriptLibPath> See also RuntimeSize. RecoveryTime ScriptLibPath This element is a list of paths delimited by semicolons instructing the server where to look for server-side scripts loaded into a main.

Prioritization ServerToClient (Bandwidth) Specifies the bandwidth in bytes per second that the server can use for sending data downstream to the client.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Contains two elements: BufferRatio. OverridePublisher SendSilence Container element. a customer can set any bandwidth limit for their applications. Contained elements Interval Server Container element. seek. which specifies the ratio of the buffer length used by the server-side stream to the live buffer. You can configure this value in the Bandwidth section of XML and in the BandwidthCap section of XML. Example <ServerToClient>250000</ServerToClient> See also ClientToServer (Bandwidth) ServerToClient (BandwidthCap) Specifies the maximum bandwidth in bytes per second that the server can use for sending data downstream to the client. This allows ISPs to host applications for customers and ensure that no customer abuses the bandwidth limit.Start is sent for all commands. but cannot exceed the caps set by the ISP. The Interval element nested within this container configures the settings for sending silent messages. The default bandwidth is 250.000 bytes per second. The values in the Bandwidth section can be overridden. Contained elements BufferRatio. If set to false. which specifies whether to prioritize outgoing messages for server-to-server connections.5 CONFIGURATION AND ADMINISTRATION GUIDE 127 XML configuration files reference SendDuplicateStart Specifies whether status message NetStream. For example. and Prioritization. but the values in the BandwidthCap section are not. and unpause. only the play command receives the start message. including play. Example <SendDuplicateStart>true</SendDuplicateStart> See also SendDuplicateOnMetaData. .Play.

Contained elements StorageDir. ResyncDepth. AutoCommit.000 bytes per second. Example <ServerToClient>10000000</ServerToClient> See also ClientToServer (BandwidthCap) SharedObjManager Container element.Last updated 3/2/2010 FLASH MEDIA SERVER 3. leave this value false. multibitrate streaming. MaxProperties. The values in the Bandwidth section can be overridden. Set this element only if the files for shared objects or recorded streams must be stored in a location other than the application directory. The default value is false. but cannot exceed the caps set by the ISP. Example <StorageDir>C:\myapp\sharedobjects\</StorageDir> <StorageDir>C:\myapp\streams\</StorageDir> See also DuplicateDir StreamManager Container element. The elements nested within this container configure the Shared Object Manager setting of an application. a customer can set any bandwidth limit for their applications.000. The elements in this section configure the Stream Manager settings for this application. You can configure this value in the Bandwidth section of XML and in the BandwidthCap section of XML. DuplicateDir. LockTimeout. To use dynamic. This allows ISPs to host applications for customers and ensure that no customer abuses the bandwidth limit. See also Live (StreamManager) StorageDir Specifies the physical location where shared objects or streams are stored.5 CONFIGURATION AND ADMINISTRATION GUIDE 128 XML configuration files reference The default bandwidth is 10. For example. but the values in the BandwidthCap section can not. By default the physical location is not set. . MaxPropertySize StartClockOnPublish Specifies whether the stream time is sensitive to the difference between publish time and the arrival of the first stream message.

The server compares these SWF files to client SWF files connecting to applications on the server. authenticating SWF files should be placed in C:\applications\myApplication\SWFs. MaxSize (Recording). DirLevelSWFScan. . FirstHashTimeout. FinalHashTimeout. MinGoodVersion. See also MinGoodVersion. The default number of subscribers is 8. When streaming through a proxy server. UserAgentExceptions. MaxDuration. Example <Subscribers>8</Subscribers> See also LoCPU. ThrottleDisplayInterval. SendDuplicateOnMetaData. SWF files located under an instance named folder can only connect to that specific instance. Contained elements SWFFolder. ThrottleLoads.5 CONFIGURATION AND ADMINISTRATION GUIDE 129 XML configuration files reference Contained elements StorageDir. ThrottleBoundaryRequest. MaxDurationCap Subscribers This element instructs the server to combine sound samples only if there are more than the default number of subscribers to that stream. Cache ThrottleBoundaryRequest Controls the maximum number of concurrent boundary requests per recorded stream. Specifies how the server verifies client SWF files before allowing the files to connect to an application. MaxSamples SWFFolder Specifies a single folder or a semicolon-delimited list of folders containing copies of client SWF files. Use a semicolon to separate multiple directories. KeyFrameInterval. Example For an application named myApplication located at C:\applications\. SendDuplicateStart. Audio. CacheUpdateInterval. Verifying SWF files is a security measure that prevents someone from creating their own SWF files that can attempt to stream your resources. see “Verify SWF files” on page 19. EnhancedSeek. DuplicateDir. Live (StreamManager).Last updated 3/2/2010 FLASH MEDIA SERVER 3. HiCPU. the boundary information about video segments are sent to the proxy server by request. The default value of the SWFFolder element is the application's folder appended with /SWFs. Note: SWF files connecting to Flash Media Administration Server cannot be verified. MaxStreamsBeforeGC. UserAgentExceptions SWFVerification Container element. CachePrefix. MaxInitDelay. MaxBufferRetries. For more information. MaxSizeCap.

The default value is 8. Type. Example <ThrottleLoads enable="true">8</ThrottleLoads> See also ThrottleBoundaryRequest. Password TTL Specifies in minutes how long each SWF file remains in the cache. video segments are sent to the proxy server by request. The default value is 1440 minutes (24 hours). Example <ThrottleDisplayInterva>64</ThrottleDisplayInterval> See also ThrottleBoundaryRequest. ThrottleLoads ThrottleLoads Controls the maximum number of concurrent segment loads per recorded stream. The default setting is false. See also Cache. Username. which means the server displays the message 1 out of 64 times when the throttle queue is full. Port. When streaming through a proxy server. The default value is 64. Example <Tunnel>false</Tunnel> See also Host.Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 130 XML configuration files reference The default value is 8. ThrottleLoads ThrottleDisplayInterval Controls the interval at which the server displays the throttle queue length. ThrottleDisplayInterval Tunnel Specifies whether or not to tunnel all operations through a given HTTP proxy. Example <ThrottleBoundaryRequest enable="false">8</ThrottleBoundaryRequest> See also ThrottleDisplayInterval. UpdateInterval .

Example <UnrestrictedAuth>true</UnrestrictedAuth> See also Allow. Example <Type>HTTP</Type> See also Host. The settings for clients vary according to whether Flash Player platform is Windows or Macintosh. Password UnrestrictedAuth A Boolean value that determines whether or not to allow sending the user name/password combination with each HTTP redirect. Sending the user name/password combination is useful only if the Allow element permits redirections. Port. The default is HTTP. Setting the value 0x01 will configure the player and platform for silent messages. Contains an element that specifies a user agent that should be an exception to authentication.28. Example <UserAgentExceptions> <Exception to="WIN 9.5 CONFIGURATION AND ADMINISTRATION GUIDE 131 XML configuration files reference Type Specifies the type of proxy being connected to. Use the to and from attributes to indicate the lowest and highest versions to except. The value for this element can be HTTP or SOCKS5. TTL UserAgent Container element. Username.0. Tunnel. See also Cache.28.0"</Exception> </UserAgentExceptions> . Contained elements Bits UserAgentExceptions Container element. The default setting is true.0" from="WIN 9.Last updated 3/2/2010 FLASH MEDIA SERVER 3.0. Max UpdateInterval Specifies the maximum time in minutes to wait for the server to scan the SWF folders for updates when there is a miss in the cache. The default value is 5 minutes.

See also Host. so do not use absolute paths in the list of folders. To enable it. Example If an application is configured to store streams in folders C:\low_quality and C:\high_quality. When this element is enabled. By default. specify / in the tag. To enable access to all video data streamed by the server. all clients can access the video data in streams in the specified folders. specify a list of semicolon-delimited folders to which client applications have access. see comments in the Application. In the tag. Port. You can also override this element with the Access plug-in or Server-Side ActionScript. Redirect VideoSampleAccess Allows the client application to access the raw uncompressed video data in a stream.5 CONFIGURATION AND ADMINISTRATION GUIDE 132 XML configuration files reference Contained elements Exception Username Specifies the user name for connecting to the edge. this element allows access to the data without requiring Server-Side ActionScript. .xml file and “Mapping virtual directories to physical directories” on page 35.high_quality</VideoSampleAccess> See also AudioSampleAccess VirtualDirectory Specifies virtual directory mappings for Server-Side ActionScript File objects. the configuration to allow access to sample those streams is as follows: <VideoSampleAccess enabled="true">low_quality. Tunnel. Password Verbose This element determines whether or not the server outputs verbose information during HTTP operations. While you can also enable access through Server-Side ActionScript. Type. Proxy. Example <Verbose>false</Verbose> See also HTTP1_0. The folder path is restricted to the application’s streams folder or folders. For more information.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Connections. set the enable attribute to true. this element is disabled.

IdleAckInterval. The default size is 16 KB.physical_dir_path</VirtualDirectory> See also FileObject WindowsPerAck Controls how many messages can be sent before receiving an acknowledgement from the other end.5 CONFIGURATION AND ADMINISTRATION GUIDE 133 XML configuration files reference Example <VirtualDirectory>virtual_dir_name. .Last updated 3/2/2010 FLASH MEDIA SERVER 3.maxUnprocessedChars. MimeType XMLSocket Container element.xml contains the elements and information used to configure log files. WriteBufferSize Specifies in kilobytes the size of the write buffer.You can edit this file to add or change configuration information. Contains an element that specifies how much data can be received from the XML server (without receiving an end tag) before XMLSocket closes the connection. The default location of the log files is in the /logs directory in the server installation directory. This can be overridden by each XMLSocket by specifying the property XML. Note: Adobe recommends that you do not change the value of this element. including the location of the log files.xml file is located at the root level of the /conf directory and is the configuration file for the logging file system. Logger.xml file The Logger. but that number cannot exceed the number specified in this element. Example <WriteBufferSize>16</WriteBufferSize> See also IdlePostInterval. Example <XMLSocket> <MaxUnprocessedChars>4096</MaxUnprocessedChars> </XMLSocket> Contained elements MaxUnprocessedChars Logger.

Field names displayed in the log file are in English. see the Logger. . Directory. Rotation. Contained elements LogServer. To see the element structure and default values.xml file installed in the RootInstall/conf/ folder. If the name of the recorded stream is in a language other than English. in the Access. QuoteFields. Contained elements LogServer Application Container element.adobe. may be in another language.5 CONFIGURATION AND ADMINISTRATION GUIDE 134 XML configuration files reference Log files are written in English.xml file enables or disables the log files. FileName. Events. see the Plug-in Developer Guide at www. the columns x-sname and x-suri-stem show the name of the stream. depending on the filename and the operating system. The elements nested within this container configure the Access log settings. Access Container element.com/go/learn_fms_plugindev_en. Time admin Container element. Contained elements Directory. The elements in this section configure the AuthEvent log file settings. the name is written in that language. For more information. Contained elements LogServer. Directory. Time.log file. EscapeFields AuthMessage Container element. Rotation AuthEvent Container element. Fields. Note: Log file rotation cannot be disabled. FileName.Last updated 3/2/2010 FLASH MEDIA SERVER 3. To effectively turn off rotation. however. The Logging section in the Server. Some content within the log file. even if the server is running on an English-language operating system. Delimiter. Time. The elements nested within this container configure the admin log settings. For example. The elements nested within this container configure the Application log file settings. choose a large maximum size and a long maximum duration for the log files.

QuoteFields Diagnostic Container element.) • colon (:) • hyphen (-) See also Directory. since # is used as the comment element in the Logger.adobe.Last updated 3/2/2010 FLASH MEDIA SERVER 3.com/go/learn_fms_plugindev_en. Time. Contained elements Directory. The following characters are not allowed as delimiters: • triple quotation marks (''' ) • paired double quotation marks ("") • comma (. Contained elements LogServer Delimiter Specifies whether or not to use a single quotation mark (') as a delimiter to separate the fields in the log file. The use of the number sign (#) as a delimiter is not recommended. Example <Directory>${LOGGER. For more information. The elements nested within this container configure the core log settings. Contained elements Directory. Time. Rotation core Container element. A delimiter is used to separate the fields in the log file. By default.LOGDIR}</Directory> . the log files are located in the logs directory in the server installation directory. The elements in this section configure the diagnostic log file.xml file. EscapeFields. see the Plug-in Developer Guide at www.5 CONFIGURATION AND ADMINISTRATION GUIDE 135 XML configuration files reference The elements in this section configure the AuthMessage log file settings. Rotation Directory Specifies the directory where the log files are located.

The elements nested within this container configure the edge log settings. the carat (^).5 CONFIGURATION AND ADMINISTRATION GUIDE 136 XML configuration files reference See also Time. open or closed angle brackets (< >). Directory. Rotation DisplayFieldsHeader Formatting element. Specifies how many lines to write to the log file before repeating the field headers. This element controls whether or not the fields in the log file are escaped when unsafe characters are found. For a list of events that are recorded in the Access log file. By default. Events. it is set to enable. Delimiter. square brackets ([ ]). FileName. See also Fields Fields Specifies which fields for an event are logged in the Access log file.Last updated 3/2/2010 FLASH MEDIA SERVER 3. the number sign (#). The keyword * instructs the server to log all events. . Specify events in a semicolon-separated list. the tilde (~). The default line count is 100 lines. and the apostrophe (' ). the percent sign (%). Fields. QuoteFields edge Container element. Example <EscapeFields>enable</EscapeFields> See also LogServer. This optional flag can be set to enable or disable. and QuoteFields Events Specifies the events written to the log file. Rotation. bar (|). EscapeFields. see “Access events defined in access logs” on page 57. open or closed curly braces ({ }). Example <DisplayFieldsHeader>100</DisplayFieldsHeader> See also Delimiter. Contained elements LogServer EscapeFields Formatting element. Time. a double quotation mark ("). The unsafe characters are as follows: the space character.

log. N represents the version number of the file.01. M represents the month of its creation. Time. access. 2007. EscapeFields History Specifies the maximum number of log files to keep. Rotation FileName Specifies the name of the Access log file. For example. M represents 4 (April). The field specification is a semicolon-separated list of one or more fields associated with an event in the log file. Note that there is no limit on the number of versions. access. date. Directory. The elements in this section configure the settings for the File plug-in log file settings. MM represents 04 (April). Example access. see “Fields in access logs” on page 59. The files are named access.03. and so on. Adobe recommends that you include the following fields in the fields to be logged: the type. For a list of fields associated with events in the Access log file.com/go/learn_fms_plugindev_en. category. Contained elements Directory. Delimiter.5 CONFIGURATION AND ADMINISTRATION GUIDE 137 XML configuration files reference Fields are associated with the events found in the Access log file. Schedule. the formats M or MM are both allowed. See also LogServer.log This example identifies version 43 of the access log file for October 30. the formats D or DD are both allowed. Fields without data are left empty. Not every field is associated with each event in the log file. See also Events FileIO Container element. QuoteFields. Example <History>5<History> See also MaxSize. see the Plug-in Developer Guide at www. Events. The repetition of a letter represents the number of digits.log. and time fields. Y represents the year of its creation.log. The default number of files to retain is 5.02.Last updated 3/2/2010 FLASH MEDIA SERVER 3. For more information. Rotation. Rename .adobe. D represents the day of the month of the file’s creation. Time. The Access log filename includes a date stamp and version number. the format YYYY must be used. The keyword * specifies that all fields are to be logged.2007103043. Fields.

The default file size is 10240 KB.Last updated 3/2/2010 FLASH MEDIA SERVER 3. DisplayFieldsHeader master Container element. The Logger element is a container for all the other elements in Logger.xml. History. or approximately 1 MB. By default.5 CONFIGURATION AND ADMINISTRATION GUIDE 138 XML configuration files reference HostPort Specifies the IP and port of the log server. ServerID. Contained elements HostPort. The elements nested within this container configure the master log settings. Example <Maxsize>10240</MaxSize> See also Schedule.xxx. LogServer Container element. DisplayFieldsHeader Logger Root element.xxx. . it is set to disable. The elements nested in this section configure the server to send messages to a remote log server.xxx:1234</HostPort> See also ServerID. Specifies whether or not to use quotation marks to surround those fields in the log file that include a space. Example <HostPort>xxx. This element can be set to enable or disable. Rename QuoteFields Formatting element. Contained elements LogServer MaxSize Specifies the maximum log file size in bytes.

The log file with the highest version number keeps the oldest log history. If Rename is set to true. Schedule. <Schedule type="hh:mm"></Schedule> If the type attribute is duration. the timestamp 00:00 causes the file to rotate every midnight. History. Delimiter.00. The duration is specified in minutes. application. FileName.log is renamed application. The elements in this section configure the rotation of the log files.log is renamed application.02. If Rename is set to false. Events. Rotation. This occurs until the maximum history setting is reached. The log file with the lowest version number keeps the oldest log history. Rename Schedule Specifies the rotation schedule for the log files. EscapeFields Rename Specifies a new name for log files when rotation occurs. Schedule. History Rotation Container element. <Schedule type="daily"></Schedule> If the type attribute is hh:mm. <Schedule type="duration"></Schedule> See also MaxSize. Contained elements MaxSize. a new log file is created with the next available version when rotation occurs.5 CONFIGURATION AND ADMINISTRATION GUIDE 139 XML configuration files reference Example <QuoteFields>disable</QuoteFields> See also LogServer. and application. Examples If the type attribute is daily. The default is true. Time.log.01.Last updated 3/2/2010 FLASH MEDIA SERVER 3. the server rotates the log files every 24 hours. Fields.01.log (and so on) when it is time to rotate the log files. Rename . Examples <Rename>true</Rename> See also MaxSize. rotation occurs when the duration of the log exceeds a specified length. There are two types of scheduling: daily rotation and rotation that occurs when the log exceeds a specified length. Directory. History.

xxx:1234</ServerID> See also HostPort. The elements nested within the Access container configure the Access log settings. the value of the ServerID element is the IP address of the server whose events are being logged. The default is local time. Edits made in the Server. DisplayFieldsHeader Time The Timefield in a log file can be logged either in UTC (GMT) or local time.xml file affect the entire server unless they are overridden in another configuration file.xml file is located at the root level of the conf directory. Contained elements Enable. SocketOverflowBuckets .xml.xxx. See also Logging Server. The Flash Media Administration Console connects to Flash Media Administration Server. SocketTableSize. gmt.Last updated 3/2/2010 FLASH MEDIA SERVER 3. To see the element structure and default values in Server.xml file installed with Flash Media Server in the RootInstall/conf/ directory. The setting for the Time element can be used to override the server-wide configuration. Flash Media Administration Server and the active cores communicate over ACCP.xml file The Server. The Access logs are located in the RootInstall\logs directory.xxx.5 CONFIGURATION AND ADMINISTRATION GUIDE 140 XML configuration files reference ServerID By default. Contained elements MinIOThreads. Access Container element. This protocol is also used for collecting performance metrics and issuing administrative commands to Flash Media Server cores. or local. Scope ACCP Container element. The elements nested within the ACCP container configure the Admin Core Communication Protocol (ACCP). Example <ServerID>xxx. Valid values are utc. MaxIOThreads. see the Server. which in turn connects to Flash Media Server.

SocketGC.60.foo. Deny. which means the element name is displayed as <_x>. The getActiveVHost() command lists only the active virtual hosts. This potential security risk can be managed by the Allow element. and other licensed limits. Mask.5 CONFIGURATION AND ADMINISTRATION GUIDE 141 XML configuration files reference ActiveProfile Specifies the limits enforced by the server on each license key (set in the LicenseInfo element). Permissible administrator connections are detailed as a comma-delimited list of host names. Process. Contained elements RTMP (AdminServer). otherwise the element name is displayed as <elem name="x">. SocketTableSize. connection.1. The elements nested within the AdminServer container configure Flash Media Administration Server. RTMP is the protocol used for communication between Flash Player and Flash Media Server. See also Process. The keyword all can also be used. By default.60</Allow> . Deny. Allow. The getActiveVHostStats()command allows administrators to query the statistics information for all active virtual hosts. The default value is false. 10. Select a profile to determine bandwidth. and full or partial IP addresses.com. LicenseInfo Admin Container element. AdminElem.133. foo. Example <Allow>x. Contained elements MinIOThreads. The elements nested within the Admin container configure the RTMP (Real-Time Messaging Protocol) for the fmsadmin process.Last updated 3/2/2010 FLASH MEDIA SERVER 3. SocketOverflowBuckets AdminElem Specifies the format used to display an element name in an HTTP command. Allow. Example <AdminElem>true</AdminElem> See also Process. To display <elem name="x"> instead of <_x> in the HTTP command. Order AdminServer Container element.com. domain names. Order. a client can connect to Flash Media Administration Server from any domain or IP address. MaxIOThreads. set the AdminElem element to true. HostPort. 10. CrossDomainPath Allow Specifies the administrator connections that are to be accepted.

To override this behavior. The Enable element nested within the Application container enables the Application log file. See also Playback AllowAnyAVCProfile By default. Application Container element. if you are delivering audio-only content.xml.264 video profiles that are not supported by Flash Player 10. set this value to true. Each data type (audio. An application is considered idle if it has no clients connected for longer than the amount of time specified in MaxAppIdleTime in Application.5 CONFIGURATION AND ADMINISTRATION GUIDE 142 XML configuration files reference or <Allow>all</Allow> See also Deny. The default value is 5. increase the AudioAutoBufferReadSize buffer. . You can tune the size of each cache. To override this behavior. which is also the minimum value for this element. The default interval is 5 minutes. For example. Contained elements Enable ApplicationGC Specifies in minutes how often the server checks for and removes unused application instances. the server does not stream any AAC audio profiles that are not supported by Flash Player 10. See also Playback AllowedVideoLag The number of seconds the server holds audio messages in the recording buffer while waiting for a video message. Order AllowAnyAACProfile By default. to achieve better disk performance.Last updated 3/2/2010 FLASH MEDIA SERVER 3. AudioAutoBufferReadSize The server caches F4V/MP4 video. audio. the server does not stream any H. This lag allows the server to sort timestamps before flushing the buffer to disk when video is delayed. and other data in memory. and decrease the VideoAutoBufferReadSize buffer. depending on the type of content you are delivering. video. and other) has its own cache. set this value to true. Caching data allows the server to make fewer disk reads and to perform better.

xml configuration file apply to all clients connected to the virtual host. you must enable the feature in the Server. (Subsequently. Use AutoCloseIdleClients to specify how often the server should check for idle clients. the server sends a status message to the NetConnection object (the client). The values defined in the Server. Once you enable the feature in the Server. The Enable element nested within the AuthMessage container enables the logging of messages from the Authorization plug-in.xml file. The Vhost.xml values override the Server.xml configuration file apply to all clients connected to the server.xml files or for individual applications in Application. Set the enable attribute to true to close idle clients. The server closes the client connection to the server and writes a message to the access log. To configure the closing of idle connections.xml file. you can disable the feature for individual virtual hosts in the Vhost. the feature is disabled. unless values are defined in the Application.) Example <AutoCloseIdleClients enable="false"> <CheckInterval>60</CheckInterval> <MaxIdleTime>600</MaxIdleTime> </AutoCloseIdleClients> Contained elements CheckInterval. When a client has been idle longer than the maximum idle time (60 seconds by default). The Application. If the enable attribute is omitted or set to false. The default value is 51200 bytes.xml values.Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 143 XML configuration files reference The minimum size is 1024 bytes. Determines whether or not to automatically close idle clients. The Enable element nested within the AuthEvent container enables the logging of events from the Authorization plug-in. Contained elements AuthMessage AutoCloseIdleClients Container element. the values defined in the Vhost.xml values.xml values override the Vhost. Contained elements Enable AuthMessage Container element.xml file. The default value is false.xml. unless the values are defined in the Vhost. OtherAutoBufferReadSize AuthEvent Container element. A client is active when it is sending or receiving data.xml file. See also VideoAutoBufferReadSize. The server also writes a message such as “Client x has been idle for y seconds” in the core and event logs. MaxIdleTime .

UpdateInterval (Cache) CheckInterval Specifies the interval. LogInterval Connector Container element. Contained elements CheckInterval. The minimum and default value is 60 seconds. Flash Media Server provides connectors that allow application scripts to connect to other Flash Media Servers or HTTP servers. at which the server checks for active client connections.5 CONFIGURATION AND ADMINISTRATION GUIDE 144 XML configuration files reference Cache Container element. You can also override the logging interval at the vhost and application levels.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file. and publish-continue. The following are available as checkpoint events: connect-continue. The default value is false. You must enable checkpoint events at the server level in the Server. Checkpoint events log bytes periodically from the start to the end of an event. Set the enable attribute to true to turn on checkpoint events in logs.xml files. play-continue. in seconds. This element contains the enable attribute which you can set to true or false. See also TTL. The value of true enables the operation on the specified content type and false disables it. but can also result in decreased server performance. .xml and Application. Contained elements HTTP. Example <CheckInterval>60</CheckInterval> See also Checkpoints Checkpoints Enables logging checkpoint events. You can disable checkpoints at the vhost and application level in the Vhost. RTMP (Connector) Content Enables operations in the current File plug-in on content (streams or SWF files). A client is disconnected the first time the server checks for idle connections if the client has exceeded the MaxIdleTime value. A shorter interval results in more reliable disconnection times. Contains elements that configure the cache setting for SWF verification. The elements nested within the Connector container configure the connector subsystem.

Example <CoreGC>300</CoreGC> See also CoreExitDelay CoreTimeout Specifies the timeout value. The default is 300 seconds. an idle core is given to exit on its own before it is removed from the server. Enable if you plan to use the File plug-in to retrieve SWF files for verification by the server. Enables stream file operations. which you can set to the following values: • • Streams. This element is nested within the FilePlugin tag. in seconds. Example <CoreExitDelay>60</CoreExitDelay> See also CoreGC CoreGC Specifies how often.5 CONFIGURATION AND ADMINISTRATION GUIDE 145 XML configuration files reference This element contains the type attribute. The default wait time is 20 seconds. Enables operations on SWF files. Contained elements MinIOThreads. . MaxIOThreads. in seconds. in seconds. for detecting unresponsive cores. The elements nested within the Core container configure the RTMP protocol for the FMSCore. Enabled by default. to check for and remove idle or unused cores. Example <Content type="Streams">true</Content> <Content type="SWF">false</Content> See also FilePlugin Core Container element.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Disabled by default. SWF.exe process. SocketOverflowBuckets CoreExitDelay Specifies how much wait time. SocketTableSize. The default timeout is 30 seconds. A value of 0 disables the timeout check.

Example <Deny>x.Last updated 3/2/2010 FLASH MEDIA SERVER 3.com. which allows clients from all domains to access the server. Use it for both edge and administration server requests. Contained elements Enable . or the keyword all. The default interval is 1 second.5 CONFIGURATION AND ADMINISTRATION GUIDE 146 XML configuration files reference Example <CoreTimeout>30</CoreTimeout> See also CoreGC CPUMonitor Specifies. The default value is *. This element is nested within both the Server element and the AdminServer element. Order Diagnostic Container element.133. 10. domain names. and full or partial IP addresses.1. foo. The Enable element nested within the Diagnostic section enables the diagnostic log file.xml</CrossDomainPath> Deny Specifies administrator connections that should be ignored. Example <CPUMonitor>1</CPUMonitor> See also ResourceLimits CrossDomainPath Specifies an absolute path on the server to a cross-domain file. in seconds. The connections are specified as a comma-delimited list of host names. Example <CrossDomainPath>C:/Security/config/files/fms/crossdomain. This element lets you specify a list of domains from which a client can access the server. 10. how often the server monitors CPU usage.foo.60</Deny> or <Deny>all</Deny> See also Allow.60. The value cannot be set to less than 1 second.com.

Specifying a negative value scans all subfolders. Contained elements MinIOThreads. Flash Media Server edge processes and Flash Media Server core processes use ECCP to migrate socket connections and to proxy connections that have not been migrated. SocketTableSize. CoreTimeout Edge Container element. See also SWFFolder ECCP Container element. Contained elements MinIOThreads. Specifying zero scans the parent folder and no subfolders. The parent folder is specified in the SWFFolder element. The elements nested within the Edge container configure resources for the fmsedge process. The elements nested within the Edge container configure the RTMP protocol for the fmsedge process. MaxIOThreads.2. .5 CONFIGURATION AND ADMINISTRATION GUIDE 147 XML configuration files reference Directory Located in the Httpd container. SocketOverflowBuckets. SocketTableSize. MaxIOThreads. Specifying a positive value scans that number of subfolders. The default value is Apache2. The elements nested within the ECCP container configure ECCP (Edge Server-Core Server Communication Protocol). The elements nested within the EdgeCore container control the IPC (interprocess communication) message queue used by edge and core processes to communicate with each other. DirLevelSWFScan Specifies the number of levels of subfolders within a parent folder to scan for SWF files. Contained elements MaxEventQueueThreads. SocketOverflowBuckets Edge (ResourceLimits) Container element. The directory containing the web server. MinEventQueueThreads. The default value is 1.Last updated 3/2/2010 FLASH MEDIA SERVER 3. which means that the server scans only one subfolder level. NumSchedQueues EdgeCore Container element.

Contained elements Enable FilePlugin Container element. This element contains elements to configure file operations that are handled by the File plug-in. Do not change this value if you want to achieve the highest possible server performance. Diagnostic. The Enable element nested within the FileIO container enables logging from the File plug-in. Application. Setting the enabled attribute to false disables the File plug-in.xml uses Enable elements in the Logging container to enable or disable the Access. MaxQueueSize Enable Server. Example <FileCheckInterval>120</FileCheckInterval> FileIO Container element. AuthEvent. in seconds. A very large number means the server does not refresh the cache even when there is a file change. Example <Access> <enable>true</Enable> </Access> See also Access. how often the server reloads the video segment in the cache when there is a file change. Specifies.and FileIO logs. false disables the logging process. AuthMessage. FileIO EnableAggMsgs Located in the Playback container. . Aggregating messages increases server performance. FileCheckInterval Located in the FLVCache container. Application. A value of true enables the logging process. The default value is true.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The minimum value is 1 second. Note: This setting applies to playback of MP4/F4V files only. AuthMessage. There is no maximum value. The default value is true. Diagnostic.5 CONFIGURATION AND ADMINISTRATION GUIDE 148 XML configuration files reference Contained elements HeapSize. The default value is 120 seconds. AuthEvent.

LargeMemPool. decrease the size of the cache. Example <FreeMemRatio>0. and SegmentsPool containers. When more free memory is available to a thread than the specified ratio. MaxKeyframeCacheSize FLVCachePurge Located in the ResourceLimits container. The range of this setting is from 0 (0%) to 1 (100%). the default value of 60 is used. SmallMemPool. To minimize the amount of memory used in the server process.5%). The default setting is 0.5 (50%).5</FreeMemRatio> FreeRatio Located in the MessageCache. Use this setting to configure the cache for optimal memory use. The recorded media cache size is specified as a percentage of the total available RAM on the system. in minutes. FLVCacheSize Located in the ResourceLimits container. The minimum value is 1 minute. Specifies the maximum percentage of total memory that the total pool size may occupy. SmallMemPool.125 (12. The default setting is 0. If you are receiving “cache full” events in the core log file or want to increase the chance that streams will find the information needed in the cache.Last updated 3/2/2010 FLASH MEDIA SERVER 3. and SegmentsPool containers. Content FLVCache Container element. The default value is 60 minutes. If you specify a value of less than 1minute.5 CONFIGURATION AND ADMINISTRATION GUIDE 149 XML configuration files reference Contained elements MaxNumberOfRequests. Specifies how often. the freed memory returns to the global pool. The maximum setting is 100 (100%). to remove unused files from the cache. The default setting for the cache size is 10 (10%). . LargeMemPool. in which case virtual memory will also be used. MaxSize (FLVCache). Specifies the maximum size of the recorded media cache. Example <FLVCacheSize>10</FLVCacheSize> FreeMemRatio Located in the MessageCache. Contained elements FileCheckInterval. Specifies the percentage of the message cache to be consumed by the free list on a per-thread basis. increase the size of the cache. The range of this setting is from 0 (0%) to 1 (100%). Contains elements that control the size and features of the recorded media cache.

the freed memory returns to the operating system. MaxQueueSize GlobalRatio Located in the MessageCache. IdleTime. Contained elements HeapSize. Example <GlobalRatio>0. This element is applicable to Flash Media Server running on Linux systems only.4</GlobalRatio> HandleCache Container element. TrimSize. SmallMemPool. The elements nested within the GlobalQueue container control the IPC message queue used by all processes to communicate with each other. LargeMemPool. Specifies the group ID of the process. the server or Administration Server runs as root. GCInterval .5 CONFIGURATION AND ADMINISTRATION GUIDE 150 XML configuration files reference Example <FreeRatio>0. Contains elements that configure how to cache handles used for HTTP requests. Example <GCInterval>60</GCInterval> GID Located in the Process containers.125</FreeRatio> GCInterval Located in the HandleCache container. This section is used for connections to Flash Remoting. The default is 60 minutes. The range of this setting is from 0 (0%) to 1 (100%). Specifies in minutes how often to remove idle handles. and SegmentsPool containers.4 (40%). Specifies the percentage of the message cache to be consumed by the free list on a global basis. The default setting is 0.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Contained elements MaxSize (HandleCache). When more free memory is available to a thread than the specified ratio. If you do not specify a UID or GID. See also UID GlobalQueue Container element.

Allocates 2xN threads. the value is 100 KB.5 CONFIGURATION AND ADMINISTRATION GUIDE 151 XML configuration files reference HeapSize Specifies the maximum size. Associates the default value with the number (N) of processors. which in turn connects to Flash Media Server. they are connecting to Flash Media Administration Server. in kilobytes. Only one port number may be specified in this element. The default is to bind to any available IP on port 1111. Example <HostPort>ip:port</HostPort> See also AdminServer HTTP Container element. of the shared memory heap used for an IPC (interprocess communication) message queue. Container EdgeCore GlobalQueue Services Default Value 1024 2048 2048 Description If the maximum size of this element is not specified. The following reference table gives the default values for all thread configurations. The Administration Service is separate from Flash Media Server. The elements nested within the HTTP container configure the HTTP connector used to connect to Flash Remoting. When administrators connect to the server with the Administration Console. Example <EdgeCore> <HeapSize>1024</HeapSize> </EdgeCore> See also MaxQueueSize HostPort Specifies the IP address and port number that Flash Media Administration Server binds to. Allocates the exact number of threads specified.Last updated 3/2/2010 FLASH MEDIA SERVER 3. . Allocates 1xN threads. The default value for this element varies according to its container. Default Value 0 >0 >0 -1 -2 Description Allocates the default number of threads.

Flash Media Server uses IPC queues to send messages from one core to another or from one process to another. The default value is localhost:11110. Program. By default the enabled attribute is set to "${SERVER. If no HTTP requests have been made to the host for the length of time specified. Contained elements Directory. The elements nested within the IPCQueues container configure the IPC queues.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Service IdleTime Located in the HandleCache container. Flash Media Server uses the settings in the Directory. such as master to core. the SERVER. Options.HTTPD_ENABLED}". If a value for Service is present. and Service elements to execute the following command lines: $Directory/$Program -d $Directory $Options -k start $Directory/$Program -d $Directory $Options -k stop Note: The value of $Directory can be absolute or relative to $FMSROOT. MaxConnectionQueueSize. some cached handles are cleared. or core to edge. Example <IdleTime>10</IdleTime IpcHostPort The interface and port the server listens on internally for connections from the fmscore process to the Administration Server. Service specifies the name used to install the webserver as an NT service. Unlike protocols. HandleCache Httpd Specifies how the built-in webserver is stopped and started. Flash Media Server starts and stops the web server automatically. -n $Service is appended to both commands. By default. The default wait time is 10 minutes.ini file. When enabled is set to true. Specifies the amount of time to wait before releasing cached handles. Options. EdgeCore. Linux ignores this section of the command. queues are used for short or one-time messages that may have more than one target. IPCQueues Container element. Services LargeMemPool Container element. On Windows only.5 CONFIGURATION AND ADMINISTRATION GUIDE 152 XML configuration files reference Contained elements MinConnectionThreads. MaxConnectionThreads. Contained elements GlobalQueue. . Program.HTTPD_ENABLED variable is set to true in the fms.

log file. Log files are written in English. For example. added by editing those files directly) to either fms. Field names in the log file are in English. MaxUnitSize.LICENSEINFO}</LicenseInfo> Note: Serial numbers that are added manually (that is. the server logs a checkpoint every check interval. this value is a parameter in the fms. See also Checkpoints Logging Container element. in the access. may be in another language. FreeRatio. FreeMemRatio LicenseInfo The license number. Contained elements MaxCacheUnits. If the value is smaller. Only serial numbers that are added using the Administration Console can be deleted using the Administration Console. The IP loopback address is usually the default localhost address.5 CONFIGURATION AND ADMINISTRATION GUIDE 153 XML configuration files reference The elements nested within the LargeMemPool container configure the large memory pool. This value should be larger than the value for CheckInterval. LogInterval Specifies how often to log a checkpoint. UpdateInterval. The elements nested within the Logging container configure general logging properties for the server.xml file.ini file: <LicenseInfo>${SERVER. Localhost Specifies the IP loopback address.ini or the LicenseInfo tag of Server. localhost can map to an erroneous interface. . Example <LicenseInfo>${SERVER. The server must reference itself locally. in seconds. however. the columns x-sname and x-suri-stem show the name of the stream. By default. MaxAge. MaxCacheSize. The default value is 3600 seconds (60 minutes). GlobalRatio. which caches large chunks of memory within the server to increase the performance of large allocations.LICENSEINFO}</LicenseInfo> LicenseInfoEx Contains license keys added using the Administration Console. If the name of the recorded stream is in a language other than English. even if the server is running on an English-language operating system. The server uses the default loopback address as the local loopback. depending on the filename and the operating system. Set the configuration properties of the individual log files in the Logger. the name is written in the log file in that language. With more than one network interface.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Some content within the log file.xml file cannot be removed using the Administration Console.

The user must enter the mask in a three-digit octal format. AuthEvent. This element defines the maximum reuse count before the cache unit is freed. Therefore. If the mask is set to 022. FileIO Mask A three-digit octal value used by the Linux umask (user permissions mask) command to set a file creation mask. This element controls who has read/write access to shared object and stream files on the server. By default.Last updated 3/2/2010 FLASH MEDIA SERVER 3. RetryNumber. CoreExitDelay MaxAge Located in the MessageCache. This element is applicable to Flash Media Server running on Linux systems only. Example <MaxAge>1000000</MaxAge> MaxAggMsgSize The maximum size of an aggregate message. all Flash Media Server object files are created with permission 0666 & ~017 = 0660 = rw-rw----. The default value is 64. Application. RecordsNumber. AuthMessage. are created on the server side with permission 0666. The owner and the users who belong to the same group as the owner get read/write permission to the files. the file created is assigned permission 0666 & ~022 = 0644 = rw-r--r--.000. Note: This setting applies to playback of MP4/F4V files only. Access.000. Master Container element. This key is used by umask to set the file creation mask. . in kilobytes. The elements nested within the Master container configure the resource limits for the master server. All Flash Media Server object files. SmallMemPool. and SegmentsPool containers. RetrySleep. LargeMemPool. Contained elements CoreGC. such as stream files or shared object files.5 CONFIGURATION AND ADMINISTRATION GUIDE 154 XML configuration files reference Contained elements Time. See also Playback MaxAudioSampleDescriptions Located in the Recording container. the creation mask is set to 017 in octal. Diagnostic. The default setting for this element is 017 in octal. The default count is 1.

The default is 4096 units. If the codec type changes more than the number of available descriptions. Example <MaxCacheUnits>4096</MaxCacheUnits> MaxConnectionQueueSize Located in the HTTP container. and SegmentsPool containers. To use the default. You can set a fractional maximum connection rate. and SegmentsPool containers. The default number of pending requests is 1000. The server allocates space for sample descriptions when it creates a file. However.5. This element defines the maximum number of free units in the cache. Connections requested at a rate above the value specified in this element remain in the TCP/IP socket queue and are silently discarded by the operating system whenever the queue becomes too long. two different audio codecs each have their own sample description. This element defines the maximum size of the cache in megabytes. Connection requests are rejected if this limit is exceeded. Example <MaxConnectionQueueSize>-1</MaxConnectionQueueSize> MaxConnectionRate Located in the RTMP (Protocol) and Edge containers. If there are three listeners and the MaxConnectionRate is set to 10. specify -1. A value of 0 or -1 disables the feature. LargeMemPool. Specifies the maximum number of incoming connections per second that the server’s socket listener accepts. Example <MaxCacheSize>100</MaxCacheSize> MaxCacheUnits Located in the MessageCache. each listener has a limit of 10 connections per second. For example. MaxCacheSize Located in the MessageCache. . such as 12. The socket listeners are configured in the Adaptor. Keep in mind that the number of free units may be less than maximum if the value of the MaxCacheSize limit is reached. This is a global setting for all socket listeners. If the element is set to 10 connections per second. LargeMemPool. the server imposes a maximum total combined rate of 30 connections per second. Note: This setting applies to recording MP4/F4V files only.Last updated 3/2/2010 FLASH MEDIA SERVER 3. SmallMemPool. adding too many descriptions takes up unnecessary space for every file that the server records.xml configuration file using the HostPort element under the HostPortList container element. The default is 100 MB.5 CONFIGURATION AND ADMINISTRATION GUIDE 155 XML configuration files reference Each change in codec for a content type has a sample description. Specifies the maximum number of connection requests that can be pending. SmallMemPool. The default value is 10. the server stops recording.

MaxEventQueueThreads Located in the Edge (ResourceLimits) container. The minimum value is 1. raise the value of HTTP/MaxConnectionThreads to 20. The default value is 100. The minimum value is 32. For HTTP. or data content ends while other such content continues. MaxELSTEntries Located in the Recording container. setting this value too high takes up unnecessary space in each recorded file. Gaps occur during an append to the file or when video. To use the default. Note: This setting applies to recording MP4/F4V files only. the default number is 5. MaxDataSampleDescriptions Located in the Recording container. If more gaps or appends occur than the value specified in the MaxELSTEntries tag.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The maximum number of threads per scheduler queue. The maximum number of kilobytes to accumulate before flushing the recording buffer. MaxFlushSize Located in the RecBuffer container. For example. the server stops recording. The default value is -2. MaxFlushTime Located in the RecBuffer container. recording ends. The server uses ELST entries when there are gaps in content. two different data encoding formats each have their own sample description. The maximum number of ELST entries in a recording. Note: This setting applies to recording MP4/F4V files only. However. adding too many descriptions takes up unnecessary space for every file that the server records. If the encoding format type changes more than the number of available descriptions. The default value is 5. . For RTMP. To use the default. The default value is 10. audio. If the server is taking a long time to process connections. However. the default number is 10. The server allocates space for sample descriptions when it creates a file.5 CONFIGURATION AND ADMINISTRATION GUIDE 156 XML configuration files reference Example <MaxConnectionRate>100</MaxConnectionRate> MaxConnectionThreads Located in the HTTP and RTMP (Connector)containers. specify 0. Specifies the maximum number of threads used to process connection requests. Each change in codec for a content type has a sample description. The maximum number of seconds to wait before flushing the recording buffer. The default value is 256. specify 0.

Core. Specifies the maximum idle time allowed. the server uses 1200 seconds (20 minutes). The default value is 3600 seconds (60 minutes). If you set a value of 60 or less. Flash Media Server can receive connections through various protocols. before a client is disconnected. Use the following information to configure all I/O and connection threads processing: • A value of 0 allocates the default number of threads (10). Example <MaxInitDelay>5</MaxInitDelay> See also SWFVerification MaxIOThreads Located in the RTMP (Connector). A low value may cause unneeded disconnections. When you configure this element. • A value greater than 0 allocates the exact number of threads specified. • A value less than 0 ties the number of connection threads to the number (N) of processors.5 CONFIGURATION AND ADMINISTRATION GUIDE 157 XML configuration files reference MaxIdleTime Located in the AutoCloseIdleClients container. For example. a user might leave the window to idle out. Use 0 for the default value. Container ACCP Admin Core ECCP Edge RTMP Default Value 10 10 10 10 10 32 Description Use 0 for the default value.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Use 0 for the default value. if you have an application with which users watch short video clips. MaxInitDelay The maximum number of seconds that is used to process SWF files. This element is used in the verification of SWF files. The default value is 5 seconds. Specifies the maximum number of threads that can be created for I/O processing. The default value for this element varies according to which container protocol it is nested within. • -2 means 2 x N threads. Use 0 for the default value. Admin. as follows: • -1 means 1 x N threads. . and ACCP containers. consider the type of applications running on the server. in seconds. ECCP. and so on. Use -1 for the default value. Use 0 for the default value. Edge.

. When messages are sent to a process that is not running. which allows unlimited requests. You can increase this value up to 4GB if a file has larger samples. Adobe generally recommends keeping the default value of 0. the server generates keyframes that are saved in the cache. you can use this value to identify problems with the File plug-in. you may want to lower this number. the number of pending requests increases up to the value of MaxNumberofRequests. EdgeCore. MaxQueueSize Located in the GlobalQueue. The default value is 2000 keyframes. The default size is 100 KB. The value is specified in kilobytes. in kilobytes.5 CONFIGURATION AND ADMINISTRATION GUIDE 158 XML configuration files reference Example <RTMP> <MaxIOThreads>32</MaxIOThreads> </RTMP> MaxKeyframeCacheSize Located in the FLVCache container. subsequent requests are rejected. If an application uses many large recorded media files.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Flash Media Server does not count the number of requests made to the File plug-in or responses returned from the File plug-in. the message can be put in a pending queue for the process. (For more information. Once MaxNumberofRequests is reached. Example <MaxKeyframeCacheSize>0</MaxKeyframeCacheSize> MaxNumberOfRequests Specifies the maximum number of pending requests to the File plug-in. the cache uses less memory. When the process starts again. it picks up the messages. See also Playback MaxSize (FLVCache) Located in the FLVCache container. Specifies the maximum number of keyframes in the cache for each recorded media file. If the plug-in does not respond to a request from the server. Services containers. When enhanced seeking is enabled. If necessary. Limiting messages saves shared memory if the process never starts. Use the MaxQueueSize element to limit the number of messages left in the pending queue. By default. see EnhancedSeek in the Application.) If you lower MaxKeyframeCacheSize. The default value is 0. MaxSampleSize The maximum allowable size of a sample in an F4V/MP4 file. The default value is 16777216 (16 MB).xml file. Specifies the maximum number of pending IPC messages in the queue.

The server logs a warning when the timestamps between two adjacent messages are bigger than the difference in real time plus the value set here for MaxTimestampSkew.5 CONFIGURATION AND ADMINISTRATION GUIDE 159 XML configuration files reference Specifies the maximum size of the recorded media cache in megabytes. audio. but hurts performance. files with up to this many tracks can be parsed. and SegmentsPool containers. This element is disabled by default. MaxUnitSize Located in the MessageCache. A shorter buffer decreases latency between real-time and playback. There is no maximum value. LargeMemPool. decrease the value of MaxSize. The default value is 200 and the minimum value is 0. Example <MaxSize>100</MaxSize> MaxSize (RecBuffer) Located in the RecBuffer container. When you add DVR functionality to an application. the size of the recording buffer affects the play-while-record experience. SmallMemPool. and data track may be played. the longer the data will be held in the buffer before written to disk. To enable the element. MaxSize (HandleCache) Located in the HandleCache container. it can be the maximum number of handles that the operating system can support. The higher the value. Specifies the maximum size to which the buffer can grow before messages are committed to file. increase the value of MaxSize. This value shares memory with the running process and has a limit of 2 GB in Windows and 3 GB in Linux. The minimum value is 0.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The default value is 64. The maximum number of tracks allowed in a file. Specifies the maximum gap in milliseconds between two adjacent messages when comparing the message timestamps with the real time. The size of the cache limits the number of unique streams the server can publish. . The default value is 500 MB. Example <MaxTimestampSkew>2</MaxTimestampSkew> MaxTracks Located in the Playback container. Example <MaxSize>5120</MaxSize> MaxTimestampSkew Located in the RecBuffer container. Specifies the maximum number of handles to cache. set the value to a positive number. While only one video. which means that no handles are cached. To increase the probability that a requested stream will be located in the recorded media cache. The default value is 100 handles. To decrease the amount of memory the server process uses. More than this amount is a file error.

the server doesn’t cache any messages greater than MaxUnitSize. If the codec type changes more than the number of available descriptions. For example. two different video codecs each have their own sample description. of a memory chunk allowed in a memory pool. Note: This setting applies to recording MP4/F4V files only. MaxAge. MessageCache Container element. The default is 1 multiplied by the number of processors. The elements nested within the MessageCache container control how the message cache holds onto messages used by the system running Flash Media Server and keeps them in memory for reuse instead of returning them and requesting them from the operating system. The server allocates space for sample descriptions when it creates a file. MaxCacheSize. The default size is 16 KB. Specifies the minimum number of threads in the pool for I/O operations. Recycling them improves the server’s performance. Messages are the essential communication units of Flash Media Server. Flash Media Server has several memory pools (distinct from the recorded media cache) that hold memory in chunks. FreeRatio. adding too many descriptions takes up unnecessary space for every file that the records. MaxUnitSize. However. Example <MessageCache> <MaxUnitSize>16</MaxUnitSize> </MessageCache> MaxVideoSampleDescriptions Located in the Recording container. specify the value 0. the server stops recording.Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 160 XML configuration files reference Specifies the maximum size. For example. UpdateInterval. in kilobytes. GlobalRatio. . Example <MinConnectionThreads>0</MinConnectionThreads> MinEventQueueThreads Located in the Edge (ResourceLimits) container. Each change in codec for a content type has a sample description. This setting ensures that chunks larger than MaxUnitSize are released to system memory instead of being held in the pool so that large memory chunks are available. if this tag is under the MessageCache tag. FreeMemRatio MinConnectionThreads Located in the HTTP and RTMP (Connector) containers. The default value is 10. Contained elements MaxCacheUnits. To use the default.

. The element specifies the minimum number of threads that can be created for I/O operations. The default value of 0 accepts current and all future versions. Use 0 for the default value. ECCP. Flash Media Server can receive connections through various protocols. and ACCP containers. The default value for this element varies according to which container protocol it is nested within. Use 0 for the default value. F4V. MinGoodVersion Located in the SWFVerification container. Use 0 for the default value. MOV. Use -1 for the default value. Use 0 for the default value. Edge. The default interval for checking and removing content is 60 seconds. and other MP4 file types. Core. Container ACCP Admin Core ECCP Edge RTMP Default Value 2X number of processors 2X number of processors 2X number of processors 2X number of processors 2X number of processors 2X number of processors Description Use 0 for the default value. Admin. Example <MinGoodVersion>0</MinGoodVersion> MinIOThreads Located in the RTMP (Connector).Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <ECCP> <MinIOThreads>0</MinIOThreads> </ECCP> Mp4 Container element. The default value is 2. Specifies the minimum accepted version of SWF verification feature that the server allows. The Mp4 elements configure how the server plays and records MP4. Recording.5 CONFIGURATION AND ADMINISTRATION GUIDE 161 XML configuration files reference The minimum number of threads per scheduler queue. MsgPoolGC Specifies how often the server checks for content in and removes content from the global message pool. Contained elements Playback.

The default value is 1024 bytes. Example To process the request if not in <Deny> or in <Allow>. audio. Order Located in the AdminServer container. set: <Order>Deny. and other data in memory. The number of scheduler queues. The default value is 1. This is an empty tag. Caching data allows the server to make fewer disk reads and to perform better. to achieve better disk performance.5 CONFIGURATION AND ADMINISTRATION GUIDE 162 XML configuration files reference NetworkingIPv6 Enables or disables Internet Protocol version 6 (IPv6).Allow</Order> To process the request if in <Allow> and not in <Deny>. Each data type (audio. The operating system network stack should be configured to support IPv6.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Options Located in the Httpd container. and other) has its own cache. . Example <NetworkingIPv6 enable="false" /> NumCRThreads Located in the RTMP (Connector) container. Flash Media Server automatically detects the operating system configuration. if desired. Deny</Order> OtherAutoBufferReadSize Located in the Playback container. You can tune the size of each cache. Specifies the order in which to evaluate the Allow and Deny elements. Example <NumCRThreads>0</NumCRThreads> NumSchedQueues Located in the Edge (ResourceLimits) container. Specifies the number of completion routine threads in Windows 32-bit systems for edge server I/O processing. set: <Order>Allow. The minimum size is 1024 bytes. The server caches F4V/MP4 video. this element can force Flash Media Server to use IPv4 even if IPv6 is available. Specifies additional switches for the command-line argument that starts and stops the web server. video. depending on the type of content you are delivering.

Last updated 3/2/2010 FLASH MEDIA SERVER 3. The default value is 60. The elements nested within the Process element contain the UID and GID elements for all server processes.5 CONFIGURATION AND ADMINISTRATION GUIDE 163 XML configuration files reference Playback Container element. F4V. MaxAggMsgSize. Contained elements FilePlugin. in seconds. MaxTracks. Contained elements UID. AllowAnyAVCProfile Plugins Container element. The elements nested within the Plugins element configure plug-ins. EnableAggMsgs. ProcVMSizeNominal The log notification threshold for reverting to a nominal process virtual memory use. in megabytes. The default value is 1800. UserDefined Process Container element. The elements are applicable to servers running on Linux systems only. For security reasons. AllowAnyAACProfile. Program Located in the Httpd container. The location of the executable file for the web server. OtherAutoBufferReadSize. the server runs as root. and other MP4 file types. MOV. after the ProcVMSizeWarn threshold has been triggered. ProcVMSizeWarn The log warning threshold for high process virtual memory use. . Protocol Container element. There are 2 Process elements. Contained elements VideoAutoBufferReadSize. one for Flash Media Server and one for Flash Media Administration Server. The Playback elements configure how the server plays back MP4. AudioAutoBufferReadSize. in megabytes. all the server processes switch from root to the UID and GID. GID ProcVMSizeMonitorInterval The monitoring interval for process virtual memory use. The default value is bin/httpd. If you do not specify a value for UID and GID. on Linux. The default value is 1600. MaxSampleSize.

but hurts performance. follow these guidelines: • A value of 0 allocates the default number of threads (10). MaxFlushSize.Last updated 3/2/2010 FLASH MEDIA SERVER 3. To set the values of all I/O and connection threads processing. Larger buffers provide better performance for some use cases. ECCP. RecBuffer Container element. use this element to create a public IP address.The default value of -1 allows an unlimited number of records. The Recording elements configure how the server records F4V/MP4 file types. MaxTimestampSkew. If an attempt to open the log fails and the number of records in the queue is greater than or equal to this number. However. etc. The elements in this container configure those protocols and how the connection requests are received. The default value is 4096. RTMP (Protocol) PublicIP Specifies that if the system has more than two network ports. ReadBufferSize The size of the largest I/O read buffers that the server uses. Contains elements that configure the buffer for recording. MaxVideoSampleDescriptions RecordsNumber The number of records in the log queue. Contained elements MaxELSTEntries. • A value less than 0 ties the number of connection threads to the number (N) of processors: • -1 means 1 x N threads • -2 means 2 x N threads. the core process is shut down. MaxAudioSampleDescriptions. larger buffers use more memory. Contained elements MaxSize (RecBuffer). Contained elements ACCP.5 CONFIGURATION AND ADMINISTRATION GUIDE 164 XML configuration files reference Flash Media Server receives connections through various protocols. • A value greater than 0 allocates the exact number of threads specified. MaxDataSampleDescriptions. MaxFlushTime. in kilobytes. the size of the recording buffer affects the play-while-record experience. . A shorter buffer decreases latency between real-time and playback. AllowedVideoLag Recording Container element. When you add DVR functionality to an application.

FLVCache. RetrySleep Number of milliseconds the server waits before retrying to open a log file. The elements nested within the ResourceLimits container specify the maximum resource limits for the server. LargeMemPool. This container holds elements that configure which versions of RTMP can be used to connect to the Administration Server. ProcVMSizeWarn.ProcVMSizeNominal. including the HTTP and RTMP protocols. MsgPoolGC.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Relevant when opening a log file fails. IPCQueues. The default value is 0. Contained elements RTMPE RTMP (Connector) Container element. Protocol. Allocates the exact number of threads specified. RTMP is the protocol used for communication between Flash Player and Flash Media Server. Master RetryNumber Number of times to retry opening a log file. The Root element is a container for all the other elements in the Server. ApplicationGC. ThreadPoolGC. Default Value 0 Description Allocates the default number of threads (10). FLVCacheSize.xml file. SSLSessionCacheGC. ProcVMSizeMonitorInterval. This container holds the elements that configure RTMP (Real-Time Messaging Protocol) for communication between Flash Remoting and Flash Media Server. Contained elements FLVCachePurge. RecBuffer. The default value is 100 ms. RTMP (AdminServer) Container element.5 CONFIGURATION AND ADMINISTRATION GUIDE 165 XML configuration files reference ResourceLimits Container element. SegmentsPool. >0 . SocketGC. The following reference table lists the default values for all thread configurations. SmallMemPool. CPUMonitor. Root Container element. Relevant when opening a log file fails. MessageCache. Connector.

This container holds the elements that configure RTMP (Real-Time Messaging Protocol).) The default value is true. MaxUnitSize. which enables logging for all processes on the server. MaxConnectionQueueSize RTMP (Protocol) Container element. Core. MaxCacheSize. MinConnectionThreads. This element determines whether to write a separate log file for each virtual host or to write one log file for the server. . FreeMemRatio Server Container element. MaxAge. Admin. SegmentsPool Container element. UpdateInterval. MaxIOThreads. Specifies whether Encrypted Real-Time Messaging Protocol (RTMPE) can be used to connect to the Administration Server. GlobalRatio.5 CONFIGURATION AND ADMINISTRATION GUIDE 166 XML configuration files reference Default Value <0 -1 -2 Description Associates the default value with the number (N) of processors. SocketSndBuf. SocketRcvBuff RTMPE Located in the RTMP container. Contained elements Edge. FreeRatio. The value for this element is server or vhost. Allocates 1xN threads. Contained elements MinIOThreads. The default is server. MaxConnectionThreads. The elements in this section configure how the segments pool caches segments of video files within Flash Media Server to increase performance of video streaming and keep frequently used video files in memory. (RTMPE also covers RTMPTE. Scope Located in the Logging container. RTMP is the protocol used for communication between Flash Player and Flash Media Server.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Allocates 2xN threads. Contained elements MaxCacheUnits. Setting this element to false prohibits RTMPE and RTMPTE from being used. NumCRThreads.

some application servers require this information as a part of incoming connection requests. Plugins. On Windows only. Contained elements NetworkingIPv6. Contained elements MaxCacheUnits.global. AutoCloseIdleClients. Example <ServerDomain>mydomain. GlobalRatio. Specifies how often.5 CONFIGURATION AND ADMINISTRATION GUIDE 167 XML configuration files reference The elements nested within the Server element contains the elements that configure the server. SWFVerification. MaxAge. the host name field is not supplied in the referrer header. LicenseInfo. Localhost. The default value is 60 seconds. in seconds. For security purposes. Contained elements HeapSize. Streams. Logging. the server checks for and removes inactive sockets. The elements in this section configure the small memory pool. MaxQueueSize SmallMemPool Container element. Httpd ServerDomain Specifies the host name (with the domain) of the server computer. SSL.mycompany. specifies the name used to install the webserver as an NT service.com</ServerDomain> Service Located in the Httpd container. UpdateInterval. The elements in this section control the IPC message queue used by the edge and core processes to communicate with each other. AdminServer. Example <SocketGC>60</SocketGC> . which saves small chunks of memory in the server to increase performance of small allocations. CrossDomainPath. Services Container element. Process. Mask.Last updated 3/2/2010 FLASH MEDIA SERVER 3. If this element is not set. If this element is empty the hostname field is empty in referrer header. PublicIP. The server uses this value to set the hostname in the referrer header tag when making a net connection to a remote server. ResourceLimits. MaxCacheSize. FreeMemRatio SocketGC Located in the AdminServer and ResourceLimits containers. MaxUnitSize. ReadBufferSize. LicenseInfoEx. FreeRatio.

in bytes. SSLClientCtx . Setting a high value significantly increases the amount of memory used by each client. SocketSndBuf The size of the client socket send buffer. The default value is 0. You should explicitly set this value only if you have a very high bandwidth connection that requires a large socket buffer. It is recommended that you do not explicitly set this value. It is recommended that you do not explicitly set this value.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Use -1 for the default value. Core. Example <Admin> <SocketTableSize>-1</SocketTableSize> </Admin> SSL Container element. Setting a high value significantly increases the amount of memory used by each client. SSLSessionCacheGC. ACCP containers. Core. Admin. ECCP. in bytes. Contained elements SSLRandomSeed. specify -1 to use the default number of buckets. ECCP.5 CONFIGURATION AND ADMINISTRATION GUIDE 168 XML configuration files reference SocketOverflowBuckets Located in the Edge. The SSL elements in Server. SocketTableSize Located in the Edge. The default value is 0. Example <Admin> <SocketOverflowBuckets>-1</SocketOverflowBuckets> </Admin> SocketRcvBuff The size of the client socket receive buffer. Admin. You should explicitly set this value only if you have a very high bandwidth connection that requires a large socket buffer. Specifies the number of overflow buckets if all slots in the socket table are in use. which tells the server to use the operating system default values. which tells the server to use the operating system default values. The default size is 200. The default number of buckets is 16. ACCP containers.xml configure the server to act as an SSL-enabled client by securing the outgoing connections. Specifies the size of the direct-access socket table for quick look-up.

there are special keywords and prefixes. • If . block low-strength ciphers. . but block those using anonymous Diffie-Hellman authentication. but some or all of the ciphers can be added again later. encryption method. and the prefix ! removes the cipher from the list. In addition. • If + is used. • Lists of cipher suites can be combined in a single cipher string using the + character as a logical and operation. attempts are made to find CA certificates in the certs directory located at the same level as the conf directory. For Win32 only: If this element is empty. such as RC4-SHA. • It can represent a list of cipher suites containing a certain algorithm. then the ciphers are deleted from the list. Specifies the name of a directory containing CA certificates. -. block export ciphers. File names must be the hash with “0” as the file extension. The cipher list consists of one or more cipher strings separated by colons. • It can consist of a single cipher suite. The default cipher list instructs the server to accept all ciphers. but colons are normally used. • If ! is used. digest type. block MD5 hashing. For example. and sort ciphers by strength from highest to lowest level of encryption. The string of ciphers can take several different forms. Specifies the name of a file that contains one or more CA (Certificate Authority) digital certificates in PEM (Privacy Enhanced Mail) encryption format. such as a key-exchange algorithm. This option doesn't add any new ciphers—it just moves matching existing ones. then the ciphers are moved to the end of the list. Each file in the directory must contain only a single CA certificate. or one of a selected number of aliases for common groupings. SSLCACertificatePath Located in the SSLClientCtx container.is used. the keyword ALL specifies all ciphers. Specifies the suite of encryption ciphers that the server uses to secure communications. authentication method.console .5 CONFIGURATION AND ADMINISTRATION GUIDE 169 XML configuration files reference SSLCACertificateFile Located in the SSLClientCtx container. Each item in the cipher list specifies the inclusion or exclusion of an algorithm or cipher. For example.Last updated 3/2/2010 FLASH MEDIA SERVER 3.initialize from the command line. The ciphers deleted can never reappear in the list even if they are explicitly stated. The Windows certificate store can be imported into this directory by running FMSMaster . or cipher suites of a certain type. Commas or spaces are also acceptable separators. SHA1 represents all cipher suites using the digest algorithm SHA1. • Each cipher string can be optionally preceded by the characters !. This element is a colon-delimited list of encryption resources. or +. Important: Contact Adobe Support before changing the default settings. and SSLv3 represents all SSL v3 algorithms. SSLCipherSuite Located in the SSLClientCtx container. then the ciphers are permanently deleted from the list. For example. SHA1+DES represents all cipher suites containing the SHA1 and DES algorithms.

and medium-strength encryption. The server evaluates both strings as equivalent. including only those ciphers the server is prepared to accept. • The cipher string @STRENGTH sorts the current cipher list in order of the length of the encryption algorithm key. <SSLCipherSuite>RSA:!NULL!EXP</SSLCipherSuite> <SSLCipherSuite>RSA:LOW:MEDIUM:HIGH</SSLCipherSuite> This cipher list instructs the server to accept all ciphers but place them in order of decreasing strength.5 CONFIGURATION AND ADMINISTRATION GUIDE 170 XML configuration files reference • If none of these characters is present.Last updated 3/2/2010 FLASH MEDIA SERVER 3. and reject export-strength versions. Example This cipher string instructs the server to accept all ciphers except those using anonymous or ephemeral Diffie-Hellman key exchange. the server does not evaluate them. then the string is just interpreted as a list of ciphers to be appended to the current preference list. • If the list includes any ciphers already present. in the order of preference. <SSLCipherSuite>ALL:!ADH:!EDH</SSLCipherSuite> These cipher strings instruct the server to accept only RSA key exchange and refuse export or null encryption. Key exchange algorithm kRSA kDHr kDHd RSA DH EDH ADH Description Key exchange Diffie-Hellman key exchange with RSA key Diffie-Hellman key exchange with DSA key Ephemeral Diffie-Hellman key exchange RSA key exchange Ephemeral Diffie-Hellman key exchange Anonymous Diffie-Hellman key exchange Authentication methods aNULL aRSA aDSS aDH Description No authentication RSA authentication DSS authentication Diffie-Hellman authentication . with the high being preferred. The components can be combined with the appropriate prefixes to create a list of ciphers. <SSLCipherSuite>ALL:+HIGH:+MEDIUM:+LOW:+EXP:+NULL</SSLCipherSuite> This string instructs the server to accept only high. <SSLCipherSuite>ALL:+SSLv2</SSLCipherSuite> The following is the complete list of components that the server can evaluate. This sequencing allows clients to negotiate for the strongest cipher that both they and the server can accept. <SSLCipherSuite>ALL:+HIGH:!LOW:!EXP:!NULL</SSLCipherSuite> This string instructs the server to accept all ciphers but to order them so that SSLv2 ciphers come after SSLv3 ciphers.

Contained elements SSLVerifyCertificate. SSLCipherSuite SSLRandomSeed Located in the SSL container. SSLCACertificatePath. Specifies how often to flush expired sessions from the server-side session cache. DES) 128-bit encryption Triple-DES encoding Digest types MD5 SHA1 SHA Description MD5 hash function SHA1 hash function SHA hash function Additional aliases All SSLv2 SSLv3 DSS Description All ciphers All SSL version 2. SSLCACertificateFile.Last updated 3/2/2010 FLASH MEDIA SERVER 3.0 ciphers All SSL version 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 171 XML configuration files reference Encryption methods eNULL DES 3DES RC4 RC2 IDEA NULL EXP LOW MEDIUM HIGH Description No encoding DES encoding Triple-DES encoding RC4 encoding RC2 encoding IDEA encoding No encryption All export ciphers (40-bit encryption) Low-strength ciphers (no export. SSLVerifyDepth. Configures the server to act as an SSL-enabled client by securing the outgoing connections. Example <SSLRandomSeed>ALL:!ADH:!EDH</SSLRandomSeed> .0 ciphers All ciphers using DSS authentication SSLClientCtx Container element.

specify false. Use a semicolon to separate multiple directories. Contained elements Mp4 SWFFolder Located in the SWFVerification container.D:\SWFs</SWFFolder> . The default value is 9. and other MP4 file types. Example The following example allows SWF files from either the C or the D directory to be authenticated: <SWFFolder>C:\SWFs. Specifies how often to check for and remove expired sessions from the server-side session cache. certificate verification fails. Example <SSLSessionCacheGC>5</SSLSessionCacheGC> SSLVerifyCertificate Located in the SSLClientCtx container. Specifies a folder containing SWF files that are verified to connect to any application on this server. MOV.5 CONFIGURATION AND ADMINISTRATION GUIDE 172 XML configuration files reference SSLSessionCacheGC Located in the SSL container. If a self-signed root certificate cannot be found within this depth. F4V. The Streams elements configure how the server plays and records MP4.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <SSLVerifyCertificate>true</SSLVerifyCertificate> SSLVerifyDepth Located in the SSLClientCtx container. Note: Disabling certificate verification can result in security problems. Certificate verification is enabled by default. Specifies whether the certificate returned by the server should be verified. To disable certificate verification. Specifies the maximum depth of the certificate chain to accept. Example <SSLVerifyDepth>9</SSLVerifyDepth> Streams Container element.

Specifies the final characters of each log entry in log files. representing 0% to 100%.Cache TerminatingCharacters Located in the Logging container. Specifies in minutes how often Flash Media Server checks for and removes unused I/O threads. DirLevelSWFScan. Contained elements SWFFolder.2</TrimSize> TTL Located in the Cache container. The default time is 20 minutes.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <TrimSize>0. Specifies the time field in a log file. Example <TerminatingCharacters>CRLF</TerminatingCharacters> ThreadPoolGC Located in the ResourceLimits container. You cannot specify less than 20 minutes. MaxInitDelay. Can be specified as a number between 0 and 1.5 CONFIGURATION AND ADMINISTRATION GUIDE 173 XML configuration files reference SWFVerification Container element.2 (20%). The time field in a log file can be specified either as UMT (GMT) or local time. MinGoodVersion. The default is CRLF (carriage return and line feed). Example <Time>local</Time> TrimSize Located in the HandleCache container. . Contains elements that configure how SWF files connecting to an application are verified. The default value is 0. Example <ThreadPoolGC>25</ThreadPoolGC> Time Located in the Logging container. The default setting is local. Specifies a percentage of cached handles to remove.

see the getConfig() method in the Flash Media Interactive Server plug-in API Reference available at www. The default value is 153600 bytes. The default value is 1440 minutes (24 hours). Example <UpdateInterval>1024</UpdateInterval> UpdateInterval (Cache) Located in the Cache container.Last updated 3/2/2010 FLASH MEDIA SERVER 3. depending on the type of content you are delivering. This element contains the server process user ID. The default value is every 1024 messages. The default value is 5 minutes. For example. UID Located in the Process containers. increase the AudioAutoBufferReadSize buffer. audio. to achieve better disk performance. This element is applicable to Flash Media Server running on Linux systems only. Each data type (audio. Specifies the maximum time in minutes to wait for the server to scan the SWF folders for updates when there is a miss in the cache. See also GID UpdateInterval Specifies how often thread statistics are collected.5 CONFIGURATION AND ADMINISTRATION GUIDE 174 XML configuration files reference Specifies in minutes how long each SWF file remains in the SWF verification data cache. Caching data allows the server to make fewer disk reads and to perform better.com/go/learn_fms_pluginapi_en. The minimum size is 1024 bytes. For more information. UserDefined Container element. You can tune the size of each cache. If you do not specify a UID or GID. if you are delivering audio-only content. VideoAutoBufferReadSize Located in the Playback container. The server caches F4V/MP4 video. video. and other data in memory. . and other) has its own cache. Define elements within the UserDefined element to store data that File plug-ins and Authorization plug-ins can retrieve. the server or Administration Server runs as root. and decrease the VideoAutoBufferReadSize buffer.adobe.

yourcompany. Example <Allow>foo. Deny (HTTPCommands).60</Allow> See also Password.xml file The Users.com. which in turn connects to the server.10. Order (HTTPCommands) Allow (User) Lists the specific hosts from which an administrator can connect to Flash Media Administration Server. You authorize the administrator’s access by creating a comma-delimited list of the accessible host names or domain names and/or full or partial IP addresses.1. The Administration Service is separate from Flash Media Server.xml file installed with Flash Media Server in the RootInstall/conf/ directory. Contained elements HTTPCommands Allow (HTTPCommands) Lists the Flash Media Administration Server commands that the administrator can access using HTTP.com.com. see the Users.com. Adobe does not recommend this usage as it creates a security risk. The HttpCommands container nested within the AdminServer container configures the access level to Flash Media Administration Server. The value All authorizes the administrator to use all HTTP commands. use the IP addresses in the Allow element to improve the server’s performance when processing connection requests.xm file is located at the root level of the RootInstall/conf directory. However.133. adobe. they are connecting to Flash Media Administration Server. 10. When administrators use the Administration Console to connect to Flash Media Server. 10.1.yourcompany.60</Allow> See also Enable. You can authorize an administrator to use multiple HTTP commands for access by creating a comma-separated list of the commands. AdminServer Container element.adobe.10. Edit this file to set permissions for Administration API calls to Flash Media Administration Server. To see the element structure and default values. Deny (User).60. Order (User) . Example <Allow>foo.5 CONFIGURATION AND ADMINISTRATION GUIDE 175 XML configuration files reference Users. Edit this file to identify Flash Media Server administrators and set their access permissions.60. Whenever possible.Last updated 3/2/2010 FLASH MEDIA SERVER 3.133. The administrator can only connect to the server from those hosts specified in this Allow element.

To disable administrative access through the use of HTTP requests.10. <Deny>foo.133. This Deny element lists the Flash Media Administration Server commands that an administrator cannot use through HTTP.60. Allow (HTTPCommands). Example This example lists the computers sending connection requests that Flash Media Administration Server will not accept. .Last updated 3/2/2010 FLASH MEDIA SERVER 3.Allow</Deny> See also Enable.yourcompany. You can deny an administrator the use of multiple HTTP commands to access the Administration Service by creating a comma-separated list of those HTTP commands.com.5 CONFIGURATION AND ADMINISTRATION GUIDE 176 XML configuration files reference Deny (HTTPCommands) Flash Media Server uses two elements named Deny: the Deny element in the User container and the Deny element in the HTTPCommands container. Example <Deny>Deny.1. Allow (User). Order (HTTPCommands) HTTPCommands Container element. You restrict the administrator’s access by creating a comma-delimited list of those host names or domain names and/or (full or partial) IP addresses. Order (HTTPCommands) Deny (User) Flash Media Server uses two elements named Deny: the Deny element in the User container and the Deny element in the HTTPCommands container. Order (User) Enable This element enables or disables the use of HTTP requests to execute administrative commands. This element lists those hosts from which the administrator is not authorized to connect to Flash Media Administration Server. do not set this element.com. Example <Enable>true</Enable> See also Allow (HTTPCommands).60</Deny> See also Password. Setting this element enables HTTP requests to execute administrative commands.10.adobe. Deny (HTTPCommands).

5 CONFIGURATION AND ADMINISTRATION GUIDE 177 XML configuration files reference This section contains the settings for those Flash Media Administration Server commands that can be accessed through HTTP. . Order (HTTPCommands) Order (HTTPCommands) Flash Media Server uses two Order elements: one in the HTTPCommands container and another in the User container. Specifies the order in which to evaluate the Deny and Allow commands. Deny (HTTPCommands). the encrypt attribute instructs the server to encrypt the contents of the password. <Order>Deny.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Allow (User). Example The sequence Deny. Passwords cannot be empty strings (""). When the encrypt attribute is set to true. Allow means the HTTP command is allowed if the command is in the Allow list of commands or not in the Deny list. Deny means the HTTP command is allowed if it is in the Allow list of commands and not in the Deny list. <Order>Allow. Deny means that administrative access is allowed unless the user is specified in the Allow list of commands and not in the Deny list: <Order>Allow. Allow (HTTPCommands). The default value is ping. Specifies the sequence in which Flash Media Server evaluates the Allow and Deny elements for an administrator.Deny</Order> The alternative sequence Deny. restart the server. Example The default sequence Allow. In the following example. <Order>Deny. Deny (HTTPCommands) Order (User) Flash Media Server uses two Order elements: one in the HTTPCommands container. and the other in the User container. and it is interpreted as an encoded string.Deny</Order> See also Enable. Passwords are usually encrypted. Allow means that administrative access is allowed unless the user is specified in the Deny list of commands and not specified in the Allow list. Deny (User) Password Specifies the password for vhost administrators.Allow</Order> See also Password. Allow (HTTPCommands).Allow</Order> The sequence Allow. Contained elements Enable. the password you see in the file is the encrypted password. Specify each Administration API that may be called over HTTP in a commadelimited list. When finished.

Last updated 3/2/2010 FLASH MEDIA SERVER 3. limits on the resources the virtual host can use.xml file The Vhost. Allow (User). the location of the virtual host’s application directory. Password. Deny (User). The Root element is a container for all the other elements. Order (User) Vhost. The UserList element defines and holds information about server administrators.xml configuration file defines an individual virtual host. You can identify multiple administrators of a virtual host by creating a profile for each administrator. These settings include aliases for the virtual host. If the Users. The Vhost. Example <Root name="_defaultVHost_"> User This element identifies an administrator of the server. Example Use the name attribute to identify the login name of a Flash Media Server administrator: <User name="jsmith"></User> See also UserList UserList Container element. Order (User) Root Container element.xml file resides under a virtual host (to define administrators for that virtual host). .5 CONFIGURATION AND ADMINISTRATION GUIDE 178 XML configuration files reference Example <Password encryt="true"></password> See also Allow (User).xml file contains elements that define the settings for the virtual host. Each virtual host directory on the server contains its own Vhost.xml file. then this tag must have its name attribute set to the name of the virtual host under which it resides. Deny (User). and other parameters. Contained elements User.

The Access logs are located in the RootInstall\logs directory. or if you want to be able to connect to this virtual host with different names. such as streaming. then the first match that is found is taken. the server attempts to connect it to _defaultVHost_.xml file installed with Flash Media Server in the RootInstall/conf/_defaultRoot_/_defaultVhost_ directory. If the edge server receives aggregate messages from the origin when this setting is disabled. To see the element structure and default values in Vhost.adobe. RouteEntry Alias The Alias element specifies the assumed name(s) of the virtual host. the messages will be broken up before being cached.adobe. Keep in mind that abc must still map to the same IP address as “abc. such as a WINS address or a hosts file. If more than one virtual host on the same adaptor has been defined with the same alias. then specify the alias abc. but you wish to connect by simply specifying “abc”. Each adaptor must contain a _defaultVHost_ directory in addition to the custom virtual hosts that you define. Access Container element.com. You can avoid unexpected behavior by specifying a unique alias for each virtual host. An alias is an alternative short name to use when connecting to the virtual host. If a client application tries to connect to a virtual host that does not exist. The Alias element lets you specify additional names to connect to this virtual host. Example <AggregateMessages enabled="true" <MaxAggMsgSize>65536</MaxAggMsgSize>> </AggregateMessages> See also EdgeAutoDiscovery. If you are using a secure port for the adaptor that contains the virtual host.adobe. that specifies an IP address on the server computer. Use the Alias element to shorten long host names. Example <Alias name="abc">abc.Last updated 3/2/2010 FLASH MEDIA SERVER 3.com”. The name of the directory must be the actual name of the virtual host.com”. The default value is false. .adobe.xml.5 CONFIGURATION AND ADMINISTRATION GUIDE 179 XML configuration files reference Each virtual host must have its own directory inside the adaptor directory. Each defined virtual host must be mapped to a DNS (domain name server) entry or another name resolution. see the Vhost.com</Alias> If the name of this virtual host is “abc. in addition to _defaultVHost_. The elements nested within the Access container configure the Access log settings. Contained elements AggregateMessages Determines whether aggregate messages are delivered from the edge cache when the virtual host is configured as an edge server. you can only define one virtual host for the adaptor.

Adobe does not recommend the use of all. it may create a security risk. You can specify an unlimited number of aliases by adding additional Alias elements.com domains. Contained elements AggregateMessages Allow This element is a comma-delimited list of domains that are allowed to connect to this virtual host.5 CONFIGURATION AND ADMINISTRATION GUIDE 180 XML configuration files reference See also AliasList AliasList Container element. If enabled. Both anonymous and explicit proxies intercept and aggregate the clients’ requests to connect to the origin server. . Setting this element to true creates an implicit proxy to intercept the incoming URIs. The default value is false.com. Here are some key differences between anonymous and explicit proxies: • The identity (IP address and port number) of an anonymous server is hidden from the client. <Allow>localhost</Allow> This example allows localhost connections only.com</Allow> This example allows only connections from the adobe. edge autodiscovery is performed by default. Example <AllowOverride>true</AllowOverride> See also Enabled. See also Anonymous AllowOverride Specifies whether overriding edge autodiscovery is allowed by specifying the rtmpd protocol. the only connections allowed are those coming from the same domain. The elements nested in this section list the alias(es) for this virtual host. <Allow>all</Allow> This example allows connections from all domains. If the Allow element is left empty. Each Alias must map to the IP address of the virtual host. Examples <Allow>adobe.com and yourcompany. WaitTime Anonymous Configures the virtual host as an anonymous proxy (also called an implicit or transparent proxy) or as an explicit proxy.Last updated 3/2/2010 FLASH MEDIA SERVER 3.yourcompany. The default value is all.

MaxStreams. MaxSharedObjects AppsDir Specifies the Applications directory for this virtual host. Note: If you use this tag to map to a network drive. Example <Anonymous>falsetrue</Anonymous> See also Mode. RouteTable. MaxAppInstances. The default interval is 1 minute. and Script engines. AggregateMessages AppInstanceGC Specifies how often to check for and remove unused resources for application instances. • The routing information in the URI for a chain of explicit proxies specifies the edge servers that are chained together to intercept connection requests to the origin server. Streams. CacheDir. LocalAddress.5\applications.Last updated 3/2/2010 FLASH MEDIA SERVER 3. • The URI for an explicit proxy specifies the edge server(s) that will intercept connection requests to the origin server. the default location is /opt/adobe/fms/applications. MaxEdgeConnections. • In Windows. . • In Linux. • Any anonymous proxy in the chain passes on. such as Shared Objects. You can create a chain of proxies by specifying them in the URI. • The URI for a chain of explicit proxies directs all clients’ connection requests through a specific sequence of edge servers before making the connection to the origin server. Example <AppInstanceGC>1</AppInstanceGC> See also MaxConnections. see “Mapping directories to network drives” on page 34 for additional information. • The routing information in the URI for a chain of explicit proxies specifically identifies the sequence of edge servers in the chain. The Applications directory is the base directory where all applications for this virtual host are defined. the default AppsDir location is C:\Program Files\Adobe\Flash Media Server 3. • The explicit proxy modifies the routing information in the URI by stripping off its token or identifier in the URI before passing the URI on to the next server in the chain. EdgeAutoDiscovery. without modification. You define an application by creating a subdirectory with the application name.5 CONFIGURATION AND ADMINISTRATION GUIDE 181 XML configuration files reference • The anonymous proxy does not change or modify the routing information in the incoming URI before connecting the client(s) to the origin server. the routing information in the URI to the next edge server in the chain.

The values defined in the Vhost. Example <AutoCloseIdleClients enable="false"> <MaxIdleTime>600</MaxIdleTime> </AutoCloseIdleClients> See also AppsDir. The server closes the client connection to the server and writes a message to the access log. This ensures that the Administration Console (fms_adminConsole.swf) will be able to connect to the virtual host.xml values override the Server. Subsequently.D:\NewApps</AppsDir> You can specify multiple applications directories by separating locations with a semicolon (.xml file.xml values. the feature is disabled. the values defined in the Server. unless the values are defined in the Vhost. Determines whether or not to close idle clients automatically. you must enable the feature in the Server. When a client has been idle longer than the maximum idle time (60 seconds by default). The Application. MaxIdleTime CacheDir Container element. Set the enable attribute to true to close idle clients. You can specify two locations.xml file. The server also writes a message such as “Client x has been idle for y seconds” in the core and event logs. unless values are defined in the Application.xml values. If no location is specified for this element.5 CONFIGURATION AND ADMINISTRATION GUIDE 182 XML configuration files reference Example 1 <AppsDir>C:\MyApps. the applications directory is assumed to be located in the vhost directory. Use AutoCloseIdleClients to specify how often the server should check for idle clients.xml configuration file apply to all clients connected to the server. Once you enable the feature in the Server. A client is active when it is sending or receiving data.xml file.). each of which contains application subdirectories. be sure to include a directory named admin in each directory. you can disable the feature for individual virtual hosts in the Vhost. If you change the default location of the AppsDir element.xml file.xml. ResourceLimits.xml configuration file apply to all clients connected to the Vhost. The default value is false.xml files or for individual applications in Application. . VirtualKeys AutoCloseIdleClients Container element.Last updated 3/2/2010 FLASH MEDIA SERVER 3. If the enable attribute is omitted or set to false. the server sends a status message to the NetConnectionobject (the client). The Vhost.xml values override the Vhost. To configure the closing of idle connections. Example 2 The following example shows a mapping to a network drive: <AppsDir>\\myNetworkDrive\share\fmsapps</AppsDir> See also AliasList.

The useAppDir attribute determines whether to separate cache subdirectories by application.xml files. RouteTable. You can disable checkpoints at the vhost and application level in the Vhost. An edge server may connect to another server that is part of a cluster. If a server has multiple virtual hosts. The edge server caches content locally to aid performance. Path. Caching static content can reduce the overall load placed on the origin server. LogInterval DNSSuffix Specifies the primary DNS suffix for this virtual host. each virtual host should point to its own cache directory. AppsDir.xml and Application. This element controls whether the cached streams are written to disk. ResourceLimits. especially for vod (video on demand) applications. The following are available as checkpoint events: connect-continue. Checkpoint events log bytes periodically from the start to the end of an event.5 CONFIGURATION AND ADMINISTRATION GUIDE 183 XML configuration files reference This element enables or disables writing recorded streams to disk. the edge server tries to determine which server in the cluster it should connect to (may or may not be the server specified in the URL). then this element is used as the domain suffix. You must enable checkpoint events at the server level in the Server. Set this element on an edge server or an intermediate origin server to control the caching behavior. If a reverse DNS look up fails to return the domain as part of the host name. You can also override the logging interval at the vhost and application levels. Anonymous. The contents of the cache change.xml file. Contained elements CheckInterval. See also AliasList. LocalAddress. VirtualKeys. VirtualDirectory EdgeAutoDiscovery Container element. MaxSize See also RequestTimeout Checkpoints Enables logging checkpoint events. The default value is true. and publish-continue. Contains elements that configure edge autodiscovery. The default value is false. .Last updated 3/2/2010 FLASH MEDIA SERVER 3. In this case. This element contains the enable attribute which you can set to true or false. Contained elements Mode. The default value of the enabled attribute is false. Set the enable attribute to true to turn on checkpoint events in logs. in addition to being cached in memory. play-continue.

0">A</Key> 7. AllowOverride.0.9.9">B</Key> 9. The keys can be any alphanumeric value.0. <VirtualDirectory> <Streams key="A">vod.0" 6.45.setVirtualPath() entries in the Server-Side ActionScript Language Reference. The default value is false. If Enabled is set to true. In the following example.0.0.play("vod/someMovie").0">A</Key> 7. it is served the stream c:\on2\someMovie.5 CONFIGURATION AND ADMINISTRATION GUIDE 184 XML configuration files reference Example <EdgeAutoDiscovery> <Enabled>false</Enabled> <AllowOverride>true</AllowOverride> >WaitTime>1000</WaitTime> </EdgeAutoDiscovery> See also Enabled.play("vod/someMovie").Last updated 3/2/2010 FLASH MEDIA SERVER 3. For more information.flv. if a client with key A requests a stream with the URL NetStream. the edge server tries to determine to which server in a cluster it should connect.0.0. see the Client.0. Example <Enabled>false</Enabled> See also AllowOverride.0" 6.virtualKey and Stream.45. you map virtual directories used in URLs to physical directories containing streams. In the following example.0" to="WIN to="WIN to="MAC to="MAC 9. it is served the stream c:\sorenson\someMovie.adobe. See also VirtualKeys .0.com/go/learn_fms_content_en. For more information. the keys are A and B: <VirtualKeys> <Key from="WIN <Key from="WIN <Key from="MAC <Key from="MAC </VirtualKeys> 8.c:\sorenson</Streams> </VirtualDirectory> Note: You can also set these values in a server-side script.0.9. You can add Key elements that map Flash Player information to keys.c:\on2</Streams> <Streams key="B">vod.flv.0. it sends the server a string containing its platform and version information.9. If a client with key B requests a stream with the URL NetStream. WaitTime Enabled Specifies whether edge autodiscovery is enabled. WaitTime Key When Flash Player connects to Flash Media Server.0" 8.9">B</Key> In the VirtualDirectory element. see the “Configuring content storage” section of the Configuration and Administration Guide at www.9.

The LocalAddress element lets you allocate incoming and outgoing connections to different network interfaces. If the value is smaller. Aggregate messages received directly from the origin server are returned as is and their size is determined by the origin server settings for aggregate message size. This setting only applies to messages retrieved from the disk cache. the server logs a checkpoint every check interval. because each chat room represents a separate instance of the application on the server. Contained elements LogInterval Specifies how often to log a checkpoint. in seconds. This value should be larger than the value for CheckInterval. If the LocalAddress element is not specified. Contains elements that control logging. then outgoing connections bind to the value of the INADDR_ANY Windows system variable. . The default number is 15. See also Proxy Logging Container element.) The default size is 65.536.5 CONFIGURATION AND ADMINISTRATION GUIDE 185 XML configuration files reference LocalAddress This element binds an outgoing edge connection to a specific local IP address. A chat application. (Aggregate messages must be enabled.Last updated 3/2/2010 FLASH MEDIA SERVER 3.000 application instances. Example <MaxAggMsgSize>66536</MaxAggMsgSize> See also AggregateMessages MaxAppInstances Specifies the maximum number of application instances that can be loaded into this virtual host. for example. A Flash SWF file defines which application instance it is connecting to by the parameters it includes with its ActionScript connect call. The default value is 3600 seconds (60 minutes). This strategy is useful when configuring an edge to either transparently pass on or intercept requests and responses. See also MaxAggMsgSize Specifies the size in bytes of aggregate messages returned from the edge cache. might require more than one instance.

MaxStreams. Example <MaxEdgeConnections>1</MaxEdgeConnections> See also MaxConnections.5 CONFIGURATION AND ADMINISTRATION GUIDE 186 XML configuration files reference Example <MaxAppInstances>15000</MaxAppInstances> See also MaxConnections. AppInstanceGC MaxIdleTime Specifies the maximum idle time allowed. AppInstanceGC MaxEdgeConnections Specifies the maximum number of connections that can remotely connect to this virtual host. before a client is disconnected.000. The default number is -1. in seconds. The default idle time is 3600 seconds (60 minutes). the server uses the value in the Server. MaxStreams. If you set a value lower than 60 seconds. Example <MaxConnections>-1</MaxConnections> See also MaxAppInstances. Connections are denied if the specified limit is exceeded. AppInstanceGC MaxConnections Specifies the maximum number of clients that can connect to this virtual host. MaxSharedObjects. MaxEdgeConnections.xml file. . The maximum number of allowed connections is encoded in the license file. This number is enforced by the license key. If no value is set for this element in the Vhost. The default number of shared objects is 50. The value for the MaxIdleTime element in the Vhost. Example <MaxIdleTime>3600</MaxIdleTime> See also AutoCloseIdleClients MaxSharedObjects Specifies the maximum number of shared objects that can be created.xml file. the server uses the value 1200 seconds (20 minutes). which represents an unlimited number of connections. MaxEdgeConnections.xml file. A different value can be set for each virtual host. MaxSharedObjects.xml file overrides the value of the MaxIdleTime element in the Server.Last updated 3/2/2010 FLASH MEDIA SERVER 3. MaxSharedObjects. MaxAppInstances. MaxStreams.

A value of 0 disables the disk cache. The Mode element can be set to local or remote. The server does LRU (least recently used) cleanup of the cache to keep it under the maximum size. The default setting is local. MaxAppInstances. Example <Mode>local</Mode> See also Anonymous.000. EdgeAutoDiscovery Path Specifies the physical location of the proxy cache. the virtual host is evaluated as an alias for the default virtual host and assumes its configuration. MaxStreams.Last updated 3/2/2010 FLASH MEDIA SERVER 3. CacheDir. RouteTable. The default value is 32 gigabytes.5 CONFIGURATION AND ADMINISTRATION GUIDE 187 XML configuration files reference Example <MaxSharedObjects>50000</MaxSharedObjects> See also MaxConnections. The value must be an absolute path. MaxAppInstances. AppInstanceGC MaxSize Specifies the maximum allowed size of the disk cache. MaxEdgeConnections. The default number of streams is 250. • When the Mode element is set to remote. A value of -1 specifies no maximum. See also MaxStreams Specifies the maximum number of streams that can be created. • If the Mode element is undefined. Flash Media Server runs its applications locally and is called an origin server. AppInstanceGC Mode The Mode element configures whether the server runs as an origin server or as an edge server. By default. • When the Mode element is set to local. Example <MaxStreams>250000</MaxStreams> See also MaxConnections. the server behaves as an edge server that connects to the applications running on an origin server. . the location is RootInstall/cache/. LocalAddress. MaxSharedObjects. in gigabytes. Relative paths are ignored and the server uses the default folder.

the server waits for a response to a request from an upstream server. MaxSharedObjects. Note: Whenever a virtual host is configured as an edge server. SSL. as demonstrated in the following examples. If this virtual host is configured to run in remote mode and you want to configure the properties of an outgoing SSL connection to an upstream server. AppInstanceGC. RouteTable. Implicit proxies hide the routing information from the clients. . Flash Media Server applies the protocol specified in the RouteTable element. EdgeAutoDiscovery. it behaves locally as a remote server. MaxAppInstances. The connection syntax for this element is flexible. The default value is 2 seconds. content. CacheDir. MaxStreams. Contained elements Mode. See also CacheDir ResourceLimits Container element. Edge servers are configured with the RouteEntry element to direct connections to another destination. A request can be for metadata. RouteEntry Instructs the edge server to forward the connection request to one server’s IP address and port number [host:port] to a different IP address and port number. If no protocol is specified. This value -1 specifies an unlimited amount of time (no timeout). LocalAddress.5 CONFIGURATION AND ADMINISTRATION GUIDE 188 XML configuration files reference See also Proxy Container element. AggregateMessages. Contained elements MaxConnections. You can also add the protocol attribute to an individual RouteEntry element to specify how the edge server reroutes requests. in seconds. RequestTimeout RequestTimeout The maximum amount of time. Examples This example shows how you can configure the edge to route all connections to the host foo to the host bar.xml file. the SSL connection to upstream servers will use the default configuration specified in the SSL section of the Server. The RouteTable element contains the RouteEntry elements that control where the edge server reroutes requests. The elements in this section specify the maximum resource limits for this virtual host. and so on. Anonymous. The elements nested in this section configure this virtual host as an edge server that can forward connection requests from applications running on one remote server to another server. MaxEdgeConnections.Last updated 3/2/2010 FLASH MEDIA SERVER 3. however.

The RouteTable element can be left empty or it can contain one or more RouteEntry elements. the connection would be routed to foo:1936. <RouteEntry>*:*. <RouteEntry>*:*. Flash Media Server applies the protocol configured in the RouteTable list unless the mapping for a particular RouteEntry element overrides it. Administrators use these elements to route connections to the desired destination.*:1936</RouteEntry> The example instructs the server to use the values for host and port on the left side as the values for host and port on the right side. then the outgoing connection will also be secure.*:80</RouteEntry> The example instructs the server to route a host:port combination to null.bar:80</RouteEntry> </RouteTable> </Proxy> Use of the wildcard character * to replace host and port. even if the incoming connection was not secure. The protocol attribute specifies the protocol to use for the outgoing connection. Its effect is to reject all connections destined for foo:80. . For example. • Specifying rtmps instructs the edge to use a secure outgoing connection. and to route connections destined for any host on any port to the same host on port 80. The attribute is set to "" (an empty string). <RouteEntry>*:*. • Specifying rtmp instructs the edge not to use a secure outgoing connection. You can override the security status for a connection mapping by specifying a protocol attribute in a RouteEntry element. • If the incoming connection was not secure. • Specifying "" (an empty string) means preserving the security status of the incoming connection.null</RouteEntry> See also RouteTable RouteTable Container element. <RouteTable protocol="rtmp"> or <RouteTable protocol="rtmps"> The RouteEntry elements nested under the RouteTable element specify the routing information for the edge server.foo:1935</RouteEntry> The example instructs the server to route connections to any host on any port to the specified host on port 1936. even if the incoming connection was secure. <RouteEntry>foo:80. • If the incoming connection was secure.The example shows how to route connections destined for any host on any port to port 1935 on the host foo. if you were to connect to foo:1935.5 CONFIGURATION AND ADMINISTRATION GUIDE 189 XML configuration files reference <Proxy> <RouteTable protocol=""> <RouteEntry>foo:1935. the outgoing connection will not be secure. By default. rtmp for a connection that isn’t secure.Last updated 3/2/2010 FLASH MEDIA SERVER 3. or rtmps for a secure connection.

SSLCipherSuite Specifies the suite of encryption ciphers that the server uses to secure communications.xml file override the SSL elements in the Server. The Windows certificate store can be imported into this directory by running FMSMaster . Flash Media Server uses the default values specified in the SSL section of Server.xml file. You can also override the configuration for outgoing SSL connections for an individual virtual host in Vhost.console . SSLVerifyDepth SSLCACertificateFile Specifies the name of a file that contains one or more CA (Certificate Authority) digital certificates in PEM (Privacy Enhanced Mail) encryption format.xml by copying the SSL elements in Server. SSLCACertificatePath.xml.xml file.xml file is not evaluated.Last updated 3/2/2010 FLASH MEDIA SERVER 3. the following sequence of events takes place: • The SSL elements in the Vhost. For Win32 only: If this element is empty. SSLVerifyCertificate.xml file match the SSL elements in the Server. When Flash Media Server acts as a client to make an outgoing SSL connection. • If the SSL elements in the Vhost. Contained elements SSLCACertificateFile.xml file.xml file to configure the connection. SSLCACertificatePath Specifies the name of a directory containing CA certificates.xml file are not present.xml file are evaluated first. • If the SSL elements in the Vhost. then you must enable this section and configure its SSL elements appropriately. For more information on the SSL elements in Server. SSLCipherSuite. If a virtual host is running in remote mode as an edge server and you want to configure the properties of an outgoing SSL connection to an upstream server. . attempts are made to find CA certificates in the certs directory located at the same level as the conf directory. • If the SSL elements in an edge’s Vhost.5 CONFIGURATION AND ADMINISTRATION GUIDE 190 XML configuration files reference Contained elements RouteEntry SSL Container element.xml file to configure the connection. see SSL. Flash Media Server uses the SSL elements in the Vhost.xml to the corresponding SSL section in the Vhost. the SSL information in the vhost. Each file in the directory must contain only a single CA certificate.initialize from the command line. Flash Media Server uses the default values for SSL in the Server. Note: When Flash Media Server is running in local mode as an origin server. File names must be the hash with “0” as the file extension.xml to configure the SSL connection to upstream servers.

• If ! is used. • Lists of cipher suites can be combined in a single cipher string using the + character as a logical and operation. such as a key-exchange algorithm. then the string is just interpreted as a list of ciphers to be appended to the current preference list. or +.5 CONFIGURATION AND ADMINISTRATION GUIDE 191 XML configuration files reference This element is a colon-delimited list of encryption resources. The cipher list consists of one or more cipher strings separated by colons.is used. but block those using anonymous Diffie-Hellman authentication. SHA1+DES represents all cipher suites containing the SHA1 and DES algorithms. <SSLCipherSuite>ALL:!ADH:!EDH</SSLCipherSuite> These cipher strings instruct the server to accept only RSA key exchange and refuse export or null encryption. <SSLCipherSuite>RSA:!NULL!EXP</SSLCipherSuite> <SSLCipherSuite>RSA:LOW:MEDIUM:HIGH</SSLCipherSuite> This cipher list instructs the server to accept all ciphers but place them in order of decreasing strength. block low-strength ciphers. or cipher suites of a certain type. • If + is used. encryption method. such as RC4-SHA. then the ciphers are permanently deleted from the list. In addition. -. This option doesn't add any new ciphers—it just moves matching existing ones. • If . and sort ciphers by strength from highest to lowest level of encryption. • If the list includes any ciphers already present. but colons are normally used. and SSLv3 represents all SSL v3 algorithms. Important: Contact Adobe Support before changing the default settings. block export ciphers. <SSLCipherSuite>ALL:+HIGH:+MEDIUM:+LOW:+EXP:+NULL</SSLCipherSuite> .Last updated 3/2/2010 FLASH MEDIA SERVER 3. For example. in the order of preference. This sequencing allows clients to negotiate for the strongest cipher that both they and the server can accept. Commas or spaces are also acceptable separators. The components can be combined with the appropriate prefixes to create a list of ciphers. and the prefix ! removes the cipher from the list. The server evaluates both strings as equivalent. but some or all of the ciphers can be added again later. The default cipher list instructs the server to accept all ciphers. the server does not evaluate them. • It can represent a list of cipher suites containing a certain algorithm. For example. block MD5 hashing. The ciphers deleted can never reappear in the list even if they are explicitly stated. • Each cipher string can be optionally preceded by the characters !. then the ciphers are moved to the end of the list. or one of a selected number of aliases for common groupings. then the ciphers are deleted from the list. authentication method. SHA1 represents all cipher suites using the digest algorithm SHA1. • If none of these characters is present. digest type. including only those ciphers the server is prepared to accept. The string of ciphers can take several different forms. Each item in the cipher list specifies the inclusion or exclusion of an algorithm or cipher. • It can consist of a single cipher suite. there are special keywords and prefixes. • The cipher string @STRENGTH sorts the current cipher list in order of the length of the encryption algorithm key. the keyword ALL specifies all ciphers. Example This cipher string instructs the server to accept all ciphers except those using anonymous or ephemeral Diffie-Hellman key exchange. For example.

DES) 128-bit encryption Triple-DES encoding . Key exchange algorithm kRSA kDHr kDHd RSA DH EDH ADH Description Key exchange Diffie-Hellman key exchange with RSA key Diffie-Hellman key exchange with DSA key Ephemeral Diffie-Hellman key exchange RSA key exchange Ephemeral Diffie-Hellman key exchange Anonymous Diffie-Hellman key exchange Authentication methods aNULL aRSA aDSS aDH Description No authentication RSA authentication DSS authentication Diffie-Hellman authentication Encryption methods eNULL DES 3DES RC4 RC2 IDEA NULL EXP LOW MEDIUM HIGH Description No encoding DES encoding Triple-DES encoding RC4 encoding RC2 encoding IDEA encoding No encryption All export ciphers (40-bit encryption) Low-strength ciphers (no export.5 CONFIGURATION AND ADMINISTRATION GUIDE 192 XML configuration files reference This string instructs the server to accept only high. and reject export-strength versions. <SSLCipherSuite>ALL:+HIGH:!LOW:!EXP:!NULL</SSLCipherSuite> This string instructs the server to accept all ciphers but to order them so that SSLv2 ciphers come after SSLv3 ciphers. <SSLCipherSuite>ALL:+SSLv2</SSLCipherSuite> The following is the complete list of components that the server can evaluate. with the high being preferred.and medium-strength encryption.Last updated 3/2/2010 FLASH MEDIA SERVER 3.

you specify a relative path that points to a shared directory that multiple applications can access. If there is no virtual directory for foo/bar. The stream named foo/bar maps to the physical file c:\data\bar. specify false. Certificate verification is enabled by default.c:\data</Streams> If a stream is named foo/bar/x. Since a virtual directory mapping does exist for foo. . the server adds one. The default value is 9.0 ciphers All SSL version 3. To disable certificate verification.flv.0 ciphers All ciphers using DSS authentication SSLVerifyCertificate Specifies whether the certificate returned by the server should be verified. certificate verification fails.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The Streams element enables you to specify a virtual directory for stored stream resources used by more than one application.flv.5 CONFIGURATION AND ADMINISTRATION GUIDE 193 XML configuration files reference Digest types MD5 SHA1 SHA Description MD5 hash function SHA1 hash function SHA hash function Additional aliases All SSLv2 SSLv3 DSS Description All ciphers All SSL version 2. Note: If the virtual directory you specify does not end with a backslash. You can specify multiple virtual directory mappings for streams by adding additional Streams elements—one for each virtual directory mapping. Examples The following configuration maps all streams whose names begin with foo/ to the physical directory c:\data.bar maps to the file c:\data\bar\x. Example <SSLVerifyDepth>9</SSLVerifyDepth> Streams Specifies the virtual directory mapping for recorded streams. <Streams>foo. If a self-signed root certificate cannot be found within this depth. the stream foo. By using a virtual directory. SSLVerifyDepth Specifies the maximum depth of the certificate chain to accept.adobe. For more information. see the “Configuring content storage” section of the Configuration and Administration Guide at www. the server checks for a virtual directory mapping for foo. the server tries to find a virtual directory mapping for foo/bar. Note: Disabling certificate verification can result in security problems.com/go/learn_fms_content_en.

Note: If you are mapping a virtual directory to a drive on another computer. Use these elements to deliver streams to clients based on Flash Player version.Last updated 3/2/2010 FLASH MEDIA SERVER 3. see VirtualKeys. VirtualKeys Lets you map Flash Player versions to keys.d:\sharedStreams</Streams> </VirtualDirectory> Contained elements Streams See also VirtualKeys VirtualHost Root element of the Vhost. using the following VirtualDirectory XML. Example For example. For more information.flv: <VirtualDirectory> <Streams>vod. make sure that the computer running Flash Media Server has the right permissions to access the other computer.C:\flashmediaserver\myapplications\shared\resources\</Streams> If the application “videoConference” refers to an item common/video/recorded/june5 and the application “collaboration” refers to common/video/recorded/june5.play("vod/myVideo"). You can use the VirtualDirectory element in conjunction with the VirtualKeys element to serve content based on Flash Player version information. <Streams>common. For detailed information on mapping virtual directories. see “Mapping directories to network drives” on page 34. Flash Media Server serves the resource from the physical directory.5 CONFIGURATION AND ADMINISTRATION GUIDE 194 XML configuration files reference The following configuration maps streams whose paths begin with common/ to the folder C:\flashmediaserver\myapplications\shared\resources.xml file. see “Mapping virtual directories to physical directories” on page 35. This element contains all the configuration elements for the Vhost. The keys are used in the VirtualDirectory element to map URLs to physical locations on a server. they both point to the same item C:\flashmediaserver\myapplications\shared\resources\video\recorded\june5\. Virtual directories let you share resources among applications.xml file. When the beginning portion of a resource’s URI matches a virtual directory. . See also VirtualDirectory VirtualDirectory Specifies virtual directory mappings for resources such as recorded streams. For more information. if a client called NetStream. the server would play the file d:\sharedStreams\myVideo.

Do not set this number too low.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <WaitTime>1000</WaitTime> See also Enabled.5 CONFIGURATION AND ADMINISTRATION GUIDE 195 XML configuration files reference Contained elements Key WaitTime Specifies length to wait in milliseconds for edge autodiscovery. The number must be long enough to establish a TCP connection. and return an XML response. perform a UDP broadcast. collect the UDP responses. AllowOverride .

log. lock count %2$S. or users that you can use for debugging.log. Clients not allowed to broadcast message. and httpcache.xx. Response object not found (%1$S). Method not found (%1$S). IP %2$S. Server initialization failed. Unlock called without matching lock for shared object %1$S. p1.xx. port %3$S: %4$S. pn]). Service Control Manager failed (%1$S: %2$S). see “Access logs” on page 57 and “Application logs” on page 63.xx.log. Failed to stop virtual host (%1$S). Message ID 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 Description Received termination signal. Error during shutdown process. invalid parameters: call(methodName[. admin. core. Received interrupt signal. Failed to execute method (%1$S). . process will be terminated. Service Control Manager reported (%1$S: %2$S). Failed to create listener for adaptor %1$S. Asynchronous I/O operation failed (%1$S: %2$S). Ignoring message from client during authentication.xx.log) record information about server operations. For status codes related to applications. Reinitializing server.log.. Missing unlock for shared object %1$S.Last updated 3/2/2010 196 Chapter 8: Diagnostic Log Messages Message IDs in diagnostic logs The IDs of messages that appear in the diagnostic log files (master.xx. The call method failed. server shutdown in progress. edge. resultObj. Failed to create thread (%1$S). Nested lock for shared object %1$S. server shutdown in progress. Message IDs can be useful for administrators who want to write error-handling scripts. lock count %2$S. Invalid application. Server starting. instances. Failed to stop %1$S listeners for adaptor %2$S. rejecting message (%1$S). Server stopped %1$S. service will be stopped. Dropping application (%1$S) message. Command name not found in the message.. Failed to start the following listeners for adaptor %1$S: %2$S.

Read access denied for shared object %1$S. Write access denied for shared object %1$S. Virtual host %1$S is not available. Alive. Script execution is taking too long. Resource limit violation. Connect failed ( %1$S. Admin request received from an invalid Administration Server. Rejecting connection from %1$S to %2$S. Illegal subscriber: %1$S cannot subscribe to %2$S. connection may be lost (%1$S). Read access denied for stream %1$S. %2$S ): %3$S. Bad network data. Write access denied for stream %1$S. Unknown %1$S command issued for stream %2$S (application %3$S).Last updated 3/2/2010 FLASH MEDIA SERVER 3. No adaptors defined. Exception while processing message. Unable to create shared object: %1$S. NetConnection. Invalid parameters to %1$S method.Call. Connect from host (%1$S) not allowed. Failed to remove administrator: %1$S.5 CONFIGURATION AND ADMINISTRATION GUIDE 197 Diagnostic Log Messages Message ID 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 Description Connection to %1$S lost. Invalid user ID (%1$S). . Invalid proxy object. terminating connection: %1$S. Failed to start server.Failed Invalid application name (%1$S). Resource limit violation. Failed to create administrator: %1$S. Administrator login failed for user %1$S. Failed to start virtual host (%1$S). Unable to create stream: %1$S. Adaptor already defined with the name %1$S. Failed to change password: %1$S. Reserved property (%1$S). Parse error at line %1$S: %2$S. Failed to open configuration file: %1$S.

%2$S). Admin user requires valid user name and password. Failed to record %1$S. Pausing %1$S. %3$S) : Failed to load application instance %1$S. Stopped playing %1$S.Admin. Play stop failed.CommandFailed Invalid parameters to %1$S method. Stream %1$S has been idling for %2$S second(s). Unpausing %1$S. Invalid virtual host alias : %1$S. Illegal access property (%1$S). %1$S applications unloaded. Connection to Flash Media Server has been disconnected. Audio receiving disabled (stream ID: %1$S). stream ID: %1$S. %3$S) : Connection rejected to application instance %1$S.5 CONFIGURATION AND ADMINISTRATION GUIDE 198 Diagnostic Log Messages Message ID 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 Description NetConnection.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Failed to restart virtual host (%1$S). Failed to load application %1$S. Connection rejected: maximum user limit reached for application instance %1$S. Failed to play %1$S (stream ID: %2$S). Failed to unload application %1$S. Failed to publish %1$S. Recording %1$S. Started playing %1$S. New NetStream created (stream ID: %1$S). %1$S is now unpublished. . (%2$S. Failed to play (stream ID: %1$S). NetStream deleted (stream ID: %1$S). %1$S is now published. (%2$S. Audio receiving enabled (stream ID: %1$S). Publishing %1$S. Playing and resetting %1$S. Error registering class: name mismatch (%1$S. Client already connected to an application. Stopped recording %1$S.

%3$S): Invalid application name (%1$S). Invalid shared object (%1$S). Failed to open shared object file (%1$S) for write. Unknown exception caught in %1$S. Invalid schedule event format (%1$S). Configuration error for adaptor %1$S: IP %2$S and port %3$S are already in use. JavaScript engine runtime is low on free memory. Failed to flush shared object (%1$S).Last updated 3/2/2010 FLASH MEDIA SERVER 3. Failed to play %1$S. Connection succeeded. Video receiving disabled (stream ID: %1$S). JavaScript runtime is out of memory. App: %3$S). Invalid NetStream ID (%1$S). Failed to open shared object file (%1$S) for read. stream not found.5 CONFIGURATION AND ADMINISTRATION GUIDE 199 Diagnostic Log Messages Message ID 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 Description Failed to enable audio receiving (stream ID: %1$S). Flash Media Server is already running or other processes are using the same ports. Failed to start listeners for adaptor %1$S. Insufficient admin privileges to perform %1$S command. Invalid method name (%1$S). Failed to seek %1$S (stream ID: %2$S). Failed to seek (stream ID: %1$S). Failed to create adaptor: %1$S. VHost: %2$S. Configuration file not found: %1$S Invalid configuration file: %1$S Server aborted. (%2$S. Check the JavaScript runtime size for this application in the configuration file. Invalid stream name (%1$S). Video receiving enabled (stream ID: %1$S). Failed to stop playing (stream ID: %1$S). Failed to receive video (stream ID: %1$S). Failed to initialize listeners for adaptor %1$. Server started (%1$S). Set video fps to %1$S (stream ID: %2$S). Take action. server shutting down instance (Adaptor: %1$S. Seeking %1$S (stream ID: %2$S). 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 . Connection failed.

Call. Rejecting connection. Invalid admin command: %1$S. (%2$S. License key specified does not allow multiple virtual host support. %3$S/%1$S): Current server bandwidth usage exceeds license limit set.Call. Unable to create new application instance: %1$S. Preload application aborted. Server shutting down. Multiprocessor support available only in Enterprise Edition. Invalid shared object file (%1$S). index file not found or mismatch. Invalid object name (stream ID: %1$S). Failed to load admin application. Unable to load new application: %1$S. Unable to locate script file: %1$S. NetConnection. %3$S): Application (%1$S) is not defined. shared object (%1$S) has been locked for %2$S sec. Potential deadlock.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Invalid license key: %1$S License key specified does not allow multiple adaptor support. Beta expired. (%2$S. (%2$S. Shutting down instance: %1$S. %3$S): Resource limit violation.Call. invalid arguments. (%2$S. %3$S/%1$S): Current virtual host bandwidth usage exceeds max limit set. . invalid arguments. Command successful. (%2$S. %3$S): Application (%1$S) is currently offline.Success Unable to locate server configuration file during startup. Failed to play %1$S. %3$S): Resource limit violation.5 CONFIGURATION AND ADMINISTRATION GUIDE 200 Diagnostic Log Messages Message ID 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 Description Failed to initialize shared object from persistent store (%1$S). Unable to create directory %1$S. Script is taking too long to process the event. (%2$S. Rejecting connection to: %1$S. Server shutdown failed. Breaking potential deadlock. Pause %1$S failed. Trial run expired. (%2$S. NetConnection. shared object(%1$S) lock reset to unlocked. %3$S): Resource limit violation. Rejecting connection.AccessDenied NetConnection.BadValue Publish %1$S failed. Admin command setApplicationState failed for %1$S.

Exception while processing message: %1$S. Failed to execute admin command: %1$S. Pending queue size limit %1$S reached. Failed to remove application: %1$S. %3$S): Max connections allowed exceed license limit. Failed to play %1$S. Listener started (%1$S): %2$S.5 CONFIGURATION AND ADMINISTRATION GUIDE 201 Diagnostic Log Messages Message ID 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 Description License key has expired. using %3$S.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Current %3$S] . Application directory does not exist: %1$S Using default application directory: %1$S Application instance is not loaded: %1$S Error: command message sent before client connection has been accepted. Rejecting connection to: %1$S. (%2$S. Attempt to reconnect to Flash Media Server. Max Allowed %2$S. Exception caught in %1$S while processing streaming data inside %2$S. Invalid value set for configuration key: %1$S = %2$S. Failed to initialize cryptographic accelerator: %1$S. Generic message code. Restarting listener (%1$S): %2$S. Adaptor (%1$S) has an SSL configuration error on port %2$S. Instance will be unloaded: %1$S. Info from %1$S:%2$S. Unknown exception occurred. Rejecting connection request Host: %2$S:%3$S. Failed to seed the pseudorandom number generator. [Virtual host (%1$S). Client to server bandwidth limit exceeded. Out of memory: %1$S. Warning from %1$S:%2$S. Invalid shared object name (%1$S). System memory load (%1$S) is high. adaptor not found: %2$S. System memory load (%1$S) is now below the maximum threshold. Failed login attempt from %1$S at %2$S. An internal version control error has occurred. Failed to record %1$S. Invalid cryptographic accelerator: %1$S. no space left on device. Unloaded application instance %1$S. Error from %1$S:%2$S.

File is in closed state (%2$S). Failed to start edge: %1$S %2$S.5 CONFIGURATION AND ADMINISTRATION GUIDE 202 Diagnostic Log Messages Message ID 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 Description Server to client bandwidth limit exceeded. Switching to Developer Edition. Missing arguments to %1$S method. [Virtual host (%1$S). arguments: %2$S. %1$S failed. Invalid argument %2$S. Last saved version %3$S. Switching to Developer Edition. Failed to start core: %1$S %2$S. Object is not a file (%2$S). File object creation failed (%1$S). File operation %1$S failed. Personal and Professional licenses cannot be mixed. Administrator (%1$S) already exists. Failed to play stream %1$S: Recorded mode not supported. Failed to open log file. Too many trial licenses detected. Core (%1$S) is no longer active. Edge (%1$S) is no longer active. Consider increasing the heap size to prevent future memory allocation failures. Max Allowed %2$S. Log aborted. Reason: %1$S. Disconnecting client. Switching to Developer Edition. Message queue is too large. as auto commit is set to false. 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 . OEM licences cannot be mixed with any other kind. Commercial and Educational licenses cannot be mixed. Connection rejected by server. Current version %2$S. Duplicate license key: %1$S Expired license key: %1$S No primary license key found. Virtual host (%1$S) does not exist.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Shared object %1$S has changed and is not being saved. Invalid admin stream: %1$S . Server memory usage too high. Switching to Developer Edition. NFR licences cannot be mixed with any other kind. %2$S File operation %1$S failed. arguments: %2$S. Core (%1$S) started. Switching to Developer Edition. Switching to Developer Edition. Shared memory heap (%1$S) has exceeded 90 usage. File operation %1$S failed. Invalid substitution variable: %1$S Resetting service failure action from %1$S to %2$S. Current %3$S] Adaptor (%1$S) does not exist. Edge (%1$S) started.

Registering core (%1$S). Connection to admin received. create a new one. Recovering edge %1$S with %2$S failure[s] after %3$S seconds! Edge (%1$S) %2$S experienced %3$S failure[s]! Core (%1$S) %2$S experienced %3$S failure[s]! Core (%1$S) %2$S is not responding and is being restarted! Core (%1$S) is no longer active. Edge disconnected from core (%1$S). Socket migration to core (%1$S) failed. Process (%1$S): failed to map view of shared memory (%2$S).5 CONFIGURATION AND ADMINISTRATION GUIDE 203 Diagnostic Log Messages Message ID 1228 1229 1230 1231 1132 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 Description Failed to create process mutex. Core (%1$S) socket migration failed. Core (%1$S) sending register command to edge. Command (%1$S) timed out. Core (%1$S) disconnected from edge. Core (%1$S) connected to admin. Recovering core %1$S with %2$S failure[s] after %3$S seconds! Core (%1$S) did not shut down as expected. Core (%1$S) connection to admin failed. Core (%1$S) received close command from admin. Core (%1$S) failed to establish proxy to edge. Process (%1$S): shared memory (%2$S) init failed. Core (%1$S) disconnecting from admin. Core (%1$S) connection to admin accepted. Core (%1$S) failed to connect to admin.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Starting admin app on core (%1$S). Killing core now. Core (%1$S): Failed to initiate connection to admin. Connection from core %1$S accepted. Proxy to core (%1$S) failed. Failed to send connect response to core %1$S. Core (%1$S) connecting to admin. Connection from core %1$S received. Core (%1$S) disconnected: %2$S. . Core (%1$S) shutdown failed.

SWF verification timeout.5 CONFIGURATION AND ADMINISTRATION GUIDE 204 Diagnostic Log Messages Message ID 1262 1263 1373 1374 1375 Description OpenProcess(PROCESS_TERMINATE) failed with %1$S. SWF verification unsupported by client.Last updated 3/2/2010 FLASH MEDIA SERVER 3. disconnecting client. disconnecting client. OpenProcess(PROCESS_QUERY_INFORMATION) failed for pid (%1$S) with %2$S. SWF verification failed. . disconnecting client.

xml file description of tags 80 file structure 80 Adaptor.xml tags Access 94 AccumulatedFrames 94 AggregateMessages (Client) 94 AggregateMessages (Queue) 94 Allow 95 AllowDebugDefault 95 AllowHTTPTunnel 95 Application 96 Audio 96 AutoCloseIdleClients 96 AutoCommit 97 AutoSampleAccess 97 Bandwidth 97 BandwidthCap 98 BandwidthDetection 98 Bits 99 BufferRatio 99 Cache 99 CachePrefix 99 CacheUpdateInterval 100 Client 101 ClientToServer (Bandwidth) 101 ClientToServer (BandwidthCap) 101 CombineSamples 102 Connections 102 DataSize 102 Debug 102 DirLevelSWFScan 103 DisallowProtocols 103 Distribute 103 DuplicateDir 104 Duration 104 EnhancedSeek 105 Exception 105 FileObject 106 FinalHashTimeout 106 FirstHashTimeout 106 FlushOnData 106 FolderAccess 106 HiCPU 106 Host 107 HTTP 107 HTTP1_0 107 HTTPTunnel 107 IdleAckInterval 108 IdlePostInterval 108 Interface 109 Interval 109 . 38 application instances about 6 log messages 43 performance 47 reloading 43 view in Administration Console 42 application logs 63 Application object.xml tags Adaptor 80 Allow 80 Deny 81 Edge 81 Enable 81 EnableAltVhost 82 HostPort 82 HostPortList 83 HTTPIdent 83 HTTPIdent2 84 HTTPNull 84 HTTPTunnel 85 HTTPUserInfo 85 IdleAckInterval 86 IdlePostInterval 86 IdleTimeout 86 MaxFailures 87 MaxSize 87 MaxWriteDelay 87 MimeType 88 NeedClose 88 NodeID 88 Order 88 Path 89 RecoveryTime 89 Redirect 89 ResourceLimits 89 RTMP 90 RTMPE 90 SetCookie 90 SSL 90 SSLCertificateFile 91 SSLCertificateKeyFile 91 SSLCipherSuite 91 SSLPassPhrase 92 SSLServerCtx 92 SSLSessionTimeout 92 UpdateInterval 93 WriteBufferSize 93 adaptors about 6 adding 7 configuring 80 creating 8 directory structure 7 administration APIs about 76 allowing use of 30 calling over HTTP 77 calling over RTMP 78 HTTP parameters 77 permissions 76 sample application 78 Administration Console about 40 application log 43 connecting to 40 debug connection 30 refresh rate 41 view applications 42 view server performance 51 Administration Server administrators 49 APIs 40 connecting to 40 default port 40 administrators defining in Administration Console 49 managing 49 Apache HTTP server 37. 57.Last updated 3/2/2010 205 Index A access logs 29.xml file description of tags 93 Application. defining 31 Application. 59 Adaptor.

xml 93 directory structure 6 editing 9 Logger.xml 175 Vhost.5 CONFIGURATION AND ADMINISTRATION GUIDE 206 Index JSEngine 109 KeyFrameInterval 110 LifeTime 110 Live (MsgQueue) 111 Live (StreamManager) 110 LoadOnStartup 111 LockTimeout 111 LoCPU 111 Max 112 MaxAggMsgSize 112 MaxAppIdleTime 112 MaxAudioLatency 112 MaxBufferRetries 113 MaxCores 113 MaxFailures 114 MaxGCSkipCount 114 MaxInitDelay 114 MaxMessagesLosslessvideo 115 MaxPendingDebugConnections 115 MaxProperties 115 MaxPropertySize 115 MaxQueueDelay 116 MaxQueueSize 116 MaxRate 116 MaxSamples 116 MaxSize 116 MaxStreamsBeforeGC 117 MaxTime 117 MaxTimeOut (Connections) 118 MaxTimeOut (JSEngine) 118 MaxUnprocessedChars 118 MaxWait 118 MimeType 119 MinBufferTime (Live) 119 MinBufferTime (Recorded) 119 MinGoodVersion 119 MsgQue 120 NetConnection 120 NotifyAudioStop 120 ObjectEncoding 120 OutChunkSize 121 OverridePublisher 121 Password 121 Port 121 Prioritization 122 Process 122 Proxy 122 PublishTimeout 123 QualifiedStreamsMapping 123 Queue 123 Recorded 123 RecoveryTime 124 Redirect 124 ResyncDepth 124 Reuse 124 RollOver 125 RuntimeSize 125 Scope 125 ScriptLibPath 126 SendDuplicateOnMetaData 126 SendDuplicateStart 127 SendSilence 127 Server 127 ServerToClient (Bandwidth) 127 ServerToClient (BandwidthCap) 127 SharedObjManager 128 StorageDir 128 StreamManager 128 Subscribers 129 SWFFolder 129 SWFVerification 129 ThrottleBoundaryRequest 129 ThrottleDisplayInterval 130 ThrottleLoads 130 TTL 130 Tunnel 130 Type 131 UnrestrictedAuth 131 UpdateInterval 131 UserAgent 131 UserAgentExceptions 131 Username 132 Verbose 132 VideoSampleAccess 132 VirtualDirectory 132 WindowsPerAck 133 WriteBuffSize 133 XMLSocket 133 audio samples. in video files 71 Event Viewer (Windows) 67 . 146 D debug connection 30 diagnostic logs 64 E edge servers cache 73 chain 5 configuring 2 connecting to 4 deploying 1 file cache (on Linux) 74 file cache (Windows) 73 environmental variables 11 Errors.xml 178 connections closing idle 14 limiting 14.xml 80 Application. 57 clients closing idle connections of 14 limiting connections from 14 view active 45 clusters 1 configuration files Adaptor.xml 140 symbols in 10 Users.xml) 23. 155 content storage configuring 33 mapping directories 34 virtual directories 35 core processes assigning 16 configuring 16 distributing 17 maximum number of 18 rolling over 18 cross-domain XML file. combining 13 B backing up log files 56 bandwidth detection.xml 133 Server. native 32 C CGI programs 39 checkpoint events 29.Last updated 3/2/2010 FLASH MEDIA SERVER 3. using 23 CrossDomainPath (Server.

xml) 149 FLVCheck tool 69 FMSCheck tool 67 fmsmgr utility 74 H HTTP proxying 38 I IPv6 configuring 30 disabling 162 enabling 162 on Linux 84 L licenses 53 Linux and IPv6 84 using with Flash Media Server 74 load balancing clusters 1 log files and IPv6 56 application 55 backing up 56 configuration files for 55 diagnostic 55 managing 55 messages 196 rotating 56 server server access 55 web server 55 Logger. 146 AutoCloseIdleClients 143 Cache 144 CheckInterval 144 Connector 144 Content 144 Core 145 CoreExitDelay 145 CoreGC 145 CoreTimeOut 145 CPUMonitor 146 CrossDomainPath 146 Deny 146 Diagnostic 146 DirLevelSWFScan 147 . 135. 179 ACCP 140 ActiveProfile 141 Admin 141 AdminElem 141 AdminServer 141 Allow 141 Application 142 ApplicationGC 142 AuthEvent 143 AuthMessage 143.xml) 123 Q QualifiedStreamsMapping (Application.xml tags Access 140. configuring 16 Server.xml file configuring 55 description of tags 133 file structure 134 Logger. 136. checking 69 FLVCachePurge (Server. 140 Server. configurable 31 P performance improving 12 monitoring server 51 permissions administration APIs 76 for administrators 175 PublishTimeout (Application.xml tags Access 134. See server-side scripts security and RTMPE 23 and SSL 24 configuring features 19 limiting domain access to 23 SWF verification 19 serial keys adding 53 server checking status of 67 hierarchy 6 log file 54 managing.xml) 123 R RecordsNumber 164 refresh rate 41 RetryNumber 165 RetrySleep 165 rotating log files 56 S scripts. 138 Application 134 AuthEvent 134 AuthMessage 134 Delimiter 135 Diagnostic 135 Directory 135 DisplayFieldsHeader 136 EscapeFields 136 Events 136 Fields 136 FileIO 137 FileName 137 History 137 HostPort 138 Logger 138 LogServer 138 MaxSize 138 QuoteFields 138 Rename 139 Rotation 139 Schedule 139 ServerID 140 Time 140 logs. on Linux 74 performance 51 starting and stopping 66 testing 67 viewing events 67 server processes.xml file 55.5 CONFIGURATION AND ADMINISTRATION GUIDE 207 Index F FLV errors 71 FLV files. See log files M map files 11 mapping virtual directories 35 messages aggregating 13 in diagnostic logs 196 viewing log messages for applications 43 MP4 errors 71 N native bandwidth detection 32 O object properties.Last updated 3/2/2010 FLASH MEDIA SERVER 3.

190 SSLClientCtx 171 SSLRandomSeed 171 SSLSessionCacheGC 172 SSLVerifyCertificate 172.xml tags AdminServer 175 Allow (HTTP Commands) 175 Allow (User) 175 Deny (HTTPCommands) 176 Deny (User) 176 Enable 176 HTTPCommands 176 Order (HTTPCommands) 177 Order (User) 177 Password 177 Root 178 User 178 UserList 178 V variables 11 Vhost.xml file description of tags 175 file structure 175 permissions for admin APIs 76 summary of tags 175 Users. 190 SSLCACertificatePath 169. 26 tags in Server. 190 SSLCipherSuite 169.xml tags AggregateMessages 179 Alias 179 AliasList 180 Allow 180 AllowOverride 180 Anonymous 180 . 174 Process (Server) 163 Protocol 163 PublicIP 164 RecBuffer 164 RecordsNumber 164 ResourceLimits 165 RetryNumber 165 RetrySleep 165 Root 165 RTMP (AdminServer) 165 RTMP (Connector) 165 RTMP (Protocol) 166 RTMPE 166 Scope 166 SegmentsPool 166 Server 166 ServerDomain 167 Services 167 SmallMemPool 167 SocketGC 167 SocketOverflowBuckets 168 SocketRcvBuff 168 SocketSndBuf 168 SocketTableSize 168 SSL 161. 163.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 172 SSLCACertificateFile 169.5 CONFIGURATION AND ADMINISTRATION GUIDE 208 Index ECCP 147 Edge 147 EdgeCore 147 Enable 148 FileCheckInterval 148 FileIO 148 FilePlugin 148 FLVCache 149 FLVCachePurge 149 FLVCacheSize 149 FreeMemRatio 149 FreeRatio 149 GCInterval 150 GID 150 GlobalQueue 150 GlobalRatio 150 HandleCache 150 HostPort 151 HTTP 151 IdleTime 152 IPCQueues 152 LargeMemPool 152 LicenseInfo 153 LicenseInfoEx 153 LocalHost 153 Logging 153 Mask 154 Master 154 MaxAge 154 MaxCacheSize 155 MaxCacheUnits 155 MaxConnectionRate 155 MaxIdleTime 157 MaxInitDelay 157 MaxIOThreads 157 MaxKeyframeCacheSize 158 MaxNumberOfRequests 158 MaxQueueSize 158 MaxSize (FLVCache) 159 MaxSize (HandleCache) 159 MaxSize (RecBuffer) 159 MaxTimestampSkew 159 MaxUnitSize 159 MessageCache 160 MinConnectionThreads 160 MinGoodVersion 161 MinIOThreads 161 MinPoolGC 161 NetworkingIPv6 162 NumCRThreads 162 Order 162 Plugins 163.xml 25. 28 tags in VHost.xml file file structure 179 summary of tags 179 Vhost.xml 27. 168.xml 28 storage directories 34 storageDir element 34 streams cache size 12 chunk size 13 view live 44 U Users. 164. 193 SSLVerifyDepth 172. 193 SWFFolder 172 SWFVerification 173 TerminatingCharacters 173 ThreadPoolGC 173 Time 173 TrimSize 173 TTL 173 UID 174 UpdateInterval 174 UpdateInterval (Cache) 174 server-side scripts and configurable object properties 31 setting storage directories 34 shared objects default location of 34 setting location of 34 view active 46 SSL certificates 25 configuring 24 tags in Adaptor.

xml) 133 .Last updated 3/2/2010 FLASH MEDIA SERVER 3.5 CONFIGURATION AND ADMINISTRATION GUIDE 209 Index AppInstanceGC 181 AppsDir 181 AutoCloseIdleClients 182 CacheDir 183 DNSSuffix 183 EdgeAutoDiscovery 183 Enabled 184 LocalAddress 185 MaxAggMsgSize 185 MaxAppInstances 185 MaxConnections 186 MaxEdgeConnections 186 MaxIdleTime 186 MaxSharedObjects 186 MaxStreams 187 Mode 187 Proxy 188 ResourceLimits 188 RouteEntry 188 RouteTable 189 SSL 190 Streams 193 VirtualDirectory 194 VirtualHost 194 VirtualKeys 194 WaitTime 195 virtual directories 35 virtual hosts about 6 connecting to 41 creating 8 directory structure 6 VirtualDirectory element 35 W WebDAV 39 Windows Event Viewer 67 WindowsPerAck (Application.