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

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

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); }

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<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.xml file for the adaptor you want to configure and locate the following code: <Adaptor> . the pass phrase must be specified in the SSLPassPhrase tag. Specify an absolute path or a path relative to the adaptor folder. Specify an absolute path or a path relative to the adaptor folder.. Your certificate file (if signed by an intermediate CA) should look something like the following: -----BEGIN CERTIFICATE----. The type attribute specifies the type of encoding used for the certificate key file. -----END CERTIFICATE---------BEGIN CERTIFICATE----.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The next BEGIN CERTIFICATE/END CERTIFICATE pair is the intermediate CA that signed your certificate. The location of the private key file for the certificate. it must include the intermediate certificate as part of the certificate that the server returns to the client.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. Secure incoming connections Specify the location of the SSL certificate and the certificate’s private key. -----END CERTIFICATE----- The first BEGIN CERTIFICATE/END CERTIFICATE pair is your certificate. SSLCertificateKeyFile type="PEM" . This can be either "PEM" or "ASN1". The private key and the certificate can be combined into one file. Element SSLCertificateFile Description The location of the certificate file to send to the client. and configure the adaptor to listen on a secure port. If the key file is encrypted... If a certificate is signed by an intermediate Certificate Authority (CA).... You can add additional sections as needed. The default value is "PEM".. </Adaptor> 2 Edit the following elements..

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

Secure outgoing connections 1 Open the Server. 5 Restart the server.pem</SSLCertificateFile> <SSLCertificateKeyFile>private2.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 443.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.Last updated 3/2/2010 FLASH MEDIA SERVER 3. edge2 will use the default configuration specified in the SSLServerCtx section that is directly under the SSL container tag. The edge2 server returns cert.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.pem</SSLCertificateFile> <SSLCertificateKeyFile>private. . Since there is no Edge tag for edge2.pem</SSLCertificateKeyFile> <SSLPassPhrase></SSLPassPhrase> <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> <SSLSessionTimeout>5</SSLSessionTimeout> </SSLServerCtx> <Edge name="edge1"> <SSLServerCtx> <SSLCertificateFile>cert2. <SSL> <SSLServerCtx> <SSLCertificateFile>cert.pem when a client connects to it on port 444.

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

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

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

create an XML tag in the JSEngine section of the Application.log.property.config. The property name corresponds to the tag’s name. Defining Application object properties You can define properties for the server-side Application object in the server’s Application. RTMPS. the properties are available only for that application. not from application.xml appropriately to resolve connections quickly.config["prop_name"] Note: The properties you define are accessible from 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. with the values jdoe and engineering.xx. you should configure the Adaptor.log. and the property value corresponds to the tag’s contents.5 CONFIGURATION AND ADMINISTRATION GUIDE 31 Configuring the server rtmp://[fd5e:624b:4c18:ffff:0:5efe:10.xml file. 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. To define a property.Last updated 3/2/2010 FLASH MEDIA SERVER 3.192. the properties are available for all applications on a virtual host.128. if necessary) in the server configuration files. 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. the following XML fragment defines the properties user_name and dept_name.log files (located in the RootInstall/logs/ directory). When the server starts.xx. host name. .xml file in an application folder. See HTTPIdent2. For example.config. it logs available stack configuration. The following xcomment fields from a sample edge log file indicate that the IPv6 stack and the IPv4 stack are available.xml file.xml configuration files.xx. and admin. If you define properties in an Application.prop_name application. if you are using an IPv4 host name (a host name that resolves to IPv4) on an RTMPT or RTMPTE connection. If you define properties in the default Application.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. edge. Check the logs. use the syntax in either of these examples: application.133.property. and RTMPE protocols with a network services database and use a service name (or decimal port number. and all available IP addresses for the host in the master.133.

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

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

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

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

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

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

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

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

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

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

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

The information in this panel is updated whenever the application instance generates a log message. log messages are still received. such as total uptime or number of users Sort applications list 1 Follow the steps in “Connect to the Administration Console” on page 40.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. 3 In the applications list. 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. View information about an application 1 Follow the steps in “Connect to the Administration Console” on page 40. 2 Click View Applications. (If the console refresh feature is paused. • Click the Clients column header to sort by client. 3 Select the application from the list. 1 Follow the steps in “Connect to the Administration Console” on page 40. 3 Select an application from the list. 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. 2 Click View Applications. 2 Click View Applications. all users are disconnected and all instance resources are released. 3 Select an application from the list.) .Last updated 3/2/2010 FLASH MEDIA SERVER 3. End an application instance When an application instance is ended. 4 Click Reload (circular arrow icon to the right of the Performance tab). 2 Click View Applications. do one of the following: • Click the Name column header to sort the applications list by name. 1 Follow the steps in “Connect to the Administration Console” on page 40.

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.

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

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

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

From here. • Review the access log and server log. you can perform the following actions: • Review the performance statistics for the computer where the applications are running. • Ping the server to verify that it is running. The Servers panel occupies the left side of the screen in this section of the Administration Console.Last updated 3/2/2010 FLASH MEDIA SERVER 3. • Connect to the selected server. . 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. if necessary. • Review information about the applications located on the server or virtual hosts. • 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. A series of tabs is displayed along the top of the Manage Servers panel. The servers are arranged in a tree structure. • Delete a server from the list. • Review information about connections to the server. The panel lists the servers and virtual hosts that you can access and manage. • Review server licenses and. add serial keys.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.

The following information is displayed: • Total number of current clients • Life span of the server • Graphical displays of active connections.xml and VHost. bandwidth resources consumed. 1 Follow the steps in “Connect to the Administration Console” on page 40. 3 Click Details.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 3 Click Connections. 2 Click Manage Servers. 2 Click Manage Servers. 3 Click Applications. such as streams and application instances. 4 Select a server from the list. • Run garbage collection to clear unused server resources.) • Stop a server or virtual host. . from memory. 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. 2 Click Manage Servers. 1 Follow the steps in “Connect to the Administration Console” on page 40.5 CONFIGURATION AND ADMINISTRATION GUIDE 52 Using the Administration Console • Restart the server or a virtual host. Viewing server details The Administration Console Details panel displays live information for the server. 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. (Automatic garbage collection intervals can be set in the Server. 4 Select a server from the list.xml configuration files.

along with the following information. . 6 Restart the server.ini or the <LicenseInfo> tag of the Server. 4 Select a server from the list. 5 Click Add Serial Key. 2 Click Manage Servers. 3 Click License. The name of each application. so note the capacity totals listed near the bottom of the Administration Console. Add a serial key Add serial keys in the Administration Console License panel. 2 Click Manage Servers. added by editing configuration files directly) to either fms.5 CONFIGURATION AND ADMINISTRATION GUIDE 53 Using the Administration Console 4 Select a server from the list.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 1 Follow the steps in “Connect to the Administration Console” on page 40. The lower frame displays information about custom licenses.xml file cannot be removed using the Administration Console. 3 Click License. 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. For each license. Note: Serial numbers that are added manually (that is. 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. Only serial numbers that are added using the Administration Console can be deleted using the Administration Console. 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. 4 Enter the serial key number in the text boxes at the bottom of the Administration Console.

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. Use the Find Previous and Clear Log buttons as necessary. type it in the Find text box and click Find Next. 5 To locate a specific string. 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.

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

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

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

Client stops playing or publishing a stream. Use the x-sid field (stream id) with the c-client-id field to find the corresponding play event. Also fires when NetStream. An application instance has stopped.0. The stream position is logged in the “c-spos” field. Client connects to server.0 and Flash Media Server 3 and later. This event occurs if an Authorization plug-in is present to handle the event. 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 resumes playing stream. A virtual host has started.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. Client begins recording a stream. the client sends a “seek” event.inBufferSeek=true and the client seeks outside the buffer. 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 . Server has started.inBufferSeek=false. This command asks the server to suspend transmission until the client sends a “startTransmit” event because there is enough data in the buffer. The stream position is logged in the “c-spos” field. 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. The stream position is logged in the “cspos” field. The seek position when the client seeks within the buffer when NetStream. Client plays a stream. Client pauses stream. Client jumps to a new location within a recorded stream. If a client seeks outside the buffer. The server received a “stopTransmit” command. Server has stopped. Client publishes a live stream. The server received a “startTransmit” command.Last updated 3/2/2010 FLASH MEDIA SERVER 3. This event occurs if an Authorization plug-in is present to handle the event. Client seeks in a stream and NetStream.115.inBufferSeek=true (called a “smart seek”). Client smart unpauses a stream. This command asks the server to transmit more data because the buffer is running low. Smart pause requires Flash Player 9. This type of pause is called a “smart pause”. Client stops recording a stream. A virtual host has stopped An application instance has started.

sc-bytes. 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. and xsname fields. c-referrer. cs-bytes. Server process ID. auth-record authorization codecchange authorization Fields in access logs Note: When the data for this field contains a space or delimiter. This event occurs if an Authorization plug-in is present to handle the event. Virtual host name. For a session. Application instance name. x-adaptor. this value is the number of seconds the client has been connected.” “Pacific Daylight Time. this value is the number of seconds the stream has played. This event occurs if an Authorization plug-in is present to handle the event.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The double quotation marks surrounding the data are not part of the data. Event category. but are present for better parsing of the data. The publisher codec changes during a live event. Time the event occurred. x-vhost. Application names. This applies to the tz. IP address or addresses of the server. Date of the event. x-ctx. see “Fields in diagnostic logs” on page 64. 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. Adaptor name. Duration of a stream or session event. CPU load. x-status c-ip . For a complete description of the x-status codes and descriptions. s-uri. the data is wrapped in double quotation marks. Time zone information.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. Event-dependent context information. c-user-agent. Logs data to the “x-codec-type” and “x-codec” fields. Memory usage (as reported by the getServerStats() method). For a stream. Client begins recording a stream. Client IP address.

in bytes. 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. To calculate the bandwidth usage per stream. in milliseconds.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. subtract cs-stream-bytes in the “publish” event from csstream-bytes in the “unpublish” event. Same as x-sname-query. Client ID. To calculate the bandwidth usage per stream. sc-bytes This field shows the number of bytes transferred from the server to the client. URI of the Flash Media Server application. This information can be used to bill customers per session. The stem portion of the s-uri field. To calculate the bandwidth usage per session. such as MP3 files. in seconds. 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 value of sc-stream-bytes can be greater than x-file-size after streaming files not encoded in FLV format. . URI of the referrer. Stream size. subtract sc-stream-bytes in the “play” event from sc-stream-bytes in the “stop” event. This is a composite field: cs-uri-stem + x-sname + x-file-ext + x-sname-query. Stream type (FLV. This field shows the number of bytes transferred from the client to the server per stream. sc-stream-bytes This field shows the number of bytes transferred from the server to the client per stream. MP3. Note: The value of sc-stream-bytes is not necessarily the same as the value of the QoS ByteCount property. User agent. This field shows the number of bytes transferred from the client to the server. or MP4). 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. 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). This is a composite field: cs-uri-stem + x-sname + x-file-ext. Stream length. To calculate the bandwidth usage per session.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Query portion of the stream URI specified in play or publish. The query portion of s-uri. Full path of the file representing the x-sname stream. Stream position.

The client stream position when a “client-pause” or “client-seek” event is logged. This field is empty in the access.log file. This field is empty in the access. Bad request.log file. The file extension portion of the stream name for the stream that the server transitions from. The URL of the web page in which the client SWF file is embedded. unpublish. publish.log file. This event is visible only in the auth. 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. invalid parameter or client connected to server using an unknown protocol. the offset value indicates where to resume streaming. This event is visible only in the auth. connect. Client disconnected due to admin command. The name of the stream that the server transitions from (the original stream). This field is empty in the access.log file. Comments. play. Successful.log file. The maximum file size of a recorded stream. play status_transition status_unavailable status_bad_request 200 210 302 400 A transition between streams has occurred. Name of the plug-in. Connection rejected by Authorization plug-in or connection rejected due to invalid URI. stop play. The maximum duration of a recorded stream. stop connect connect. Connection rejected by application script or access denied by application. The transition mode sent by the client in the NetStream. Codec value of the “x-codec-type” retrieved in the Authorization plug-in’s E_CODEC_CHANGE event. Application currently unavailable.play2() call. The query stream portion of the stream name for the stream that the server transitions from. play. record stop. An event ID received by Authorization plug-in. publish. Client disconnected due to server shutdown (or application unloaded). When a stream is reconnected. connect. status_OK record. This event is visible only in the auth. x-codec-type x-codec Event status codes in access logs The Event status codes are based on HTTP response codes. This ID is unique for the client session but not across sessions. Codec type of the frame retrieved in the Authorization plug-in’s E_CODEC event.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.log file. publish status_unauthorized 401 connect status_forbidden 403 . The ID of a stream. This field is only available in authorization (auth-) events.Last updated 3/2/2010 FLASH MEDIA SERVER 3.

Unable to process message received when client connection was in pending or closed state. publish Symbol object_not_found client_disconnect status_conflict Status Code 404 408 409 Description Application or stream not found. Expected response not provided when issued an admin command. Client does not have privilege to broadcast. Unable to obtain ping response or client states not connected. Server internal error. Upstream connection closed. play connect server_internal_error bad_gateway 500 502 . closed due to inactive or idle status. 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. License to receive screen sharing video failed. SWF verification timeout. Resource limit exceeded or stream is already being published. Client connection invalid. play play connect. Error handling message. Client disconnected due to incompatibility with object encoding. Unable to process unknown data type. Stream stopped because client disconnected. Bad gateway. Expected response not provided when command was issued. License limit exceeded. Flash Media Server autoclose feature automatically closed the connection. disconnect the client. Close downstream connection.5 CONFIGURATION AND ADMINISTRATION GUIDE 62 Monitoring and Managing Log Files Field connect. connect play. Expected response not provided when command issued. unable to write data. SWF verification failure. Can also mean that a change has been made by the Authorization plug-in. Client is not connected or client terminated. Message queue too large.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Unsupported media type. Upstream connection closed because the last client disconnected.

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

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

or Restart. or restart Flash Media Server 1 Log in as a root user. 2 Change to the directory where the server is installed./fmsmgr server stop . stop./fmsmgr server start .5 • Choose Start > All Programs > Adobe > Flash Media Server 3.5 > Stop Flash Media Administration Server 3.5 • Choose Start > All Programs > Adobe > Flash Media Server 3. 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.5 Start. Start./fmsmgr server restart Start. 2 Do one of the following: • Select Flash Media Server (FMS) from the Services list and click Stop.5 > Stop Flash Media Server 3. • Select Flash Media Administration Server from the Services list and click Stop. or Restart. stop. Start and stop the server in Linux Start. Start.5 > Start 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.5 > Start Flash Media Administration Server 3. or restart the Administration Server 1 Log in as a root user. or restart the server from the Services window 1 Choose Start > Control Panel > Administrative Tools > Services. 3 Open a shell window and type one of the following: • • • . stop. Start the server from the Start menu ❖ Do one of the following: • Choose Start > All Programs > Adobe > Flash Media Server 3.5 Stop the server from the Start menu ❖ Do one of the following: • Choose Start > All Programs > Adobe > Flash Media Server 3. .

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

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

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

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

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

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. Invalid box version. Box is too large. Track has unsupported sample type. Too many tag boxes. File appears to be FLV with wrong extension. canSeekToEnd is false. Duplicate box. Invalid number of data entries in box. warnings are informative and are not fatal errors. Truncated box. This warning indicates that a track has an invalid video codec. and File Name. Found duplicate data track.. . Warnings are logged to the stdout file in the following format: Date. Error reading MP4 tables. 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. Time. Warning Number. but you may experience problems with playback.. Found duplicate audio track.. -108 MP4 Invalid video codec. Unsupported DRM scheme. Unrecognized box.. Invalid sample size. Invalid movie time scale. Ignoring. Flash Media Server will ignore the error that caused the warning and continue to load and play back the video or audio file.. Found duplicate video track. Flash Media Server ignores (will not play back) tracks that are encoded with unsupported codecs. Found incomplete track. Max is 64. Invalid chapter time.Last updated 3/2/2010 FLASH MEDIA SERVER 3.. File contains out-of-order movie fragments. File contains unexpected movie fragments. FLVCheck warnings Generally. Warning Message. Ignoring. Ignoring. Flash Media Server cannot play back the track.

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

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

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

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

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

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

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

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

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

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

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

The IP address can be explicitly configured and does not need to be the IP of the Flash Media Server machine. HTTPUserInfo HTTPNull Configures the server to respond to or reject an HTTP GET request for the “/” resource from a client. For a response to be returned.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 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. The default value is false.71</HTTPIdent2> See also HTTPNull. Using <HTTPIdent2> enables Flash Player to send a special HTTP request before connecting to Flash Media Server. even if the <HTTPIdent2> tag or the enabled attribute is missing. each connection may be sent to any one of many Flash Media Servers behind load balancers. (This allows RTMPT connections to be redirected to a different server. the HTTPIdent2 function must be enabled. If a single RTMPT session consists of multiple socket connections. When the enable attribute is set to true. Example <HTTPNull enable="false"> . If HTTPNull is disabled and the webserver is enabled.) If the tag is left empty.133. RTMPT (Tunnelled Real-Time Messaging Protocol) can have difficulties working with load balancers. the HTTPNull function is disabled. By default. This feature is enabled by default. 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. This causes the session to be split across machines. This function is available when using Flash Player Update 3 or later. 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). HTTPTunnel.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. Example <HTTPIdent2 enabled="true">10. the IP address is determined automatically. requests for the "/" resource are passed to the webserver. an HTTP 404 response is sent in response to an HTTP GET request. 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). HTTPTunnel.128. Attributes enable A Boolean value.

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

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

When the cache size reaches the maximum size. Occasionally. 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. when connections close under abnormal conditions. UpdateInterval MaxWriteDelay The HTTP tunnelling protocol ensures that a server will be able to write every four seconds. Example <MaxSize>100</MaxSize> See also Path.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 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. By default. Example <MaxFailures>2</MaxFailures> See also IdleAckInterval MaxSize Specifies the maximum number of HTTP requests the server keeps in the cache. the server reduces the cache. See also HTTPTunnel . the notification may not reach the server. which may continue to place writes in a queue. The default wait time is 40 seconds. The default number of failures is 2.

Last updated 3/2/2010 FLASH MEDIA SERVER 3. The alternative sequence Deny.+!*'() See also HTTPTunnel Order Specifies the sequence in which the server evaluates the Allow and Deny elements. Example The following is the default sequence: <Order>Allow. Example <MimeType>application/x-fcs</Mimetype> See also HTTPTunnel NeedClose A Boolean value specifying whether or not HTTP 1. The server generally uses the MIME type specified by the incoming requests. and 0-9.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. 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.Deny</Order> The default sequence indicates that access to a server is denied unless it is specified in the Allow element. The default value is true. The server uses the entry for the MIMEType element only if it is unable to determine the MIME type from the incoming requests. and the special characters $-_. The ID must contain URL-safe characters: alphanumerical A-Z. Example <NeedClose>true</NeedClose> See also MaxWriteDelay NodeID Specifies a unique node identification that supports the implementation of load balancers. a-z.Allow indicates that access to a server is allowed unless specified in the Deny element and not specified in the Allow element. which closes the connections.Deny</Order> . The following is the default sequence: <Order>Allow.0 non-keepalive connections are closed once the response is written. If the NodeID element is used.

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

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

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

SSLCipherSuite. It is a base64 encoding that makes the password less readable. SSLSessionTimeout SSLServerCtx Container element. Example <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite> See also SSLCertificateFile. When a client connects to a server for the first time. which the client can place in the cache and reuse at a later time. SSLCertificateKeyFile. 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. the server sends back a session object to the client. this element is left blank. . SSLCertificateKeyFile. it must perform the full handshake. If the key file is not encrypted. SSLPassPhrase. The server does not require the full SSL handshake if the session is still valid. 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". SSLCertificateKeyFile. SSLSessionTimeout SSLSessionTimeout Specifies in minutes how long a SSL-based session remains valid. encode the password in base64 format and set the encrypt attribute to true. Specifies the password to use for decrypting the key file if the key file is encrypted. After that first handshake. SSL sessions are used to improve performance by avoiding the need to perform the full SSL handshake for every connection. it is not a true encryption. SSLCipherSuite. Contained elements SSLCertificateFile.Last updated 3/2/2010 FLASH MEDIA SERVER 3. it can send back the cached session object. SSLSessionTimeout SSLPassPhrase Specifies the passphrase to use for encrypting the private key file. SSLPassPhrase. See also SSLCertificateFile. The default time period is 5 minutes. The elements in this section control the incoming SSL configuration for this adaptor. To prevent plain text passwords from appearing in the configuration file.

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

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

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

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

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

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

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

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

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

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

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. The default percentage of utilization is 80. See also SWFVerification FlushOnData Specifies whether the server flushes the message queue when a data message arrives. which allow access to a particular file only. The default is true. This allows two levels of permissions: file-level access (a value of false). MaxQueueSize. and folderlevel access (a value of true).5 CONFIGURATION AND ADMINISTRATION GUIDE 106 XML configuration files reference FileObject Container element. The VirtualDirectory element nested within this container configures the JSEngine file object settings. so the server can send out the messages immediately. 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. Example <HiCPU>80</HiCPU> . This element is important for streaming data-only messages. 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. AccumulatedIFrames FolderAccess Configures the level of permission that the Access plug-in can set for accessing streams and shared objects. MaxQueueDelay. See also Queue. which allows access to a particular directory.Last updated 3/2/2010 FLASH MEDIA SERVER 3.

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

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. If the IdlePostInterval element is set to a value that lies outside of this range. 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 interval for an idle post ranges from 0 to 4064 milliseconds. the server will not be able to send any data to the client for the selected duration. Idle posts are sent when Flash Player has no data to send.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 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. The interval cannot be set to a negative value. but posting is necessary to provide the server with an opportunity to send data downstream to the client. The default interval is 512 milliseconds. Example <IdlePostInterval>512</IdlePostInterval> . WriteBufferSize IdlePostInterval Specifies how long Flash Player should wait before sending an idle post to the server. IdleAckInterval. This interval implies that the client may not be able to reach the server for the selected duration. MimeType. Example <IdleAckInterval>512</IdleAckInterval> See also IdlePostInterval. the default value of 512 milliseconds is used. Note: At times. MimeType.

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

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

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

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

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

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

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

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

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

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

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

Contained elements ObjectEncoding NotifyAudioStop Container element. Streams that use H.5 CONFIGURATION AND ADMINISTRATION GUIDE 120 XML configuration files reference See also SWFFolder. 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 default is AMF3. This can be AMF0 or AMF3.Last updated 3/2/2010 FLASH MEDIA SERVER 3. See also Server MsgQueue Container element. Recorded. The default can be overridden for each individual NetConnection by setting the NetConnection. This setting ensures that regardless of the buffer setting there are enough messages to begin playback quickly. The default value is 64. The element nested within this container specifies object encoding to use for SSAS NetConnection. 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.objectEncoding property to either 0 for AMF0 or 3 for AMF3. Server NetConnection Container element. . Setting this value to less than 64 may cause content with a low FPS to delay before starting. Example <NotifyAudioStop enabled="false"></NotifyAudioStop> Contained elements Duration ObjectEncoding Specifies the default object encoding to use for SSAS NetConnection.264 or any other pipelined codec need messages to begin playback. Contained elements Live (MsgQueue).

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. SendDuplicateStart. Note that older clients might not support chunk sizes larger than 1024 bytes. add application logic to avoid stream name collision. BandwidthCap. If set to true. see the PublishTimeout element. MaxMessageSizeLosslessVideo OverridePublisher Deprecated. Tunnel. Username Port Specifies the proxy port to connect to if the port is not specified as part of the host in the Host element. The server breaks stream content into chunks of this size. BandwidthDetection. MsgQueue. Example <OutChunkSize>4096</OutChunkSize> See also Bandwidth. This can have a minimum value of 128 bytes and a maximum value of 65536 bytes.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. the chunk setting is capped at 1024 bytes. HTTPTunnel. Password. SendDuplicateOnMetaData Password Specifies the password for connecting to the proxy. The default value is false.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Tunnel. See also Host. Live (StreamManager). 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. Port. Type. See also Host. The default value is 4096. Example <OverridePublisher>true</OverridePublisher> See also Audio. Type. Username .

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

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

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

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

The server first looks in the location where the main. Each application instance runs in its own process. MaxGCSkipCount. the script engine searches.x behavior and sends onMetaData based on the start position. XMLSocket.asc or application_name. MaxFailures. once falls back to FMS 1. Example <ScriptLibPath>${APP. false sends onMetaData for play only. MaxTimeOut (JSEngine).asc file with the load() method. This is the default value. The default value is true. Example <SendDuplicateOnMetaData>true</SendDuplicateOnMetaData> See also SendDuplicateStart . If you choose this value.asc file is located. you must also set the Distribute numprocs attribute to a value greater than 1. If no onMetaData is found at the start position. These paths are used to resolve a script file that is loaded with the load API. the list of paths specified in this element.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. regardless of the command. The following values are available: • • • true sends onMetaData for the play and seek commands. 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. If the script file is not found there.Last updated 3/2/2010 FLASH MEDIA SERVER 3. All application instances in a virtual host run together in a process. in sequence. FileObject. 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. no onMetaData is sent. All instances of a single application run together in a process. Example <Scope>vhost</Scope> See also Distribute. LifeTime.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The elements nested within the Edge container configure resources for the fmsedge process. SocketTableSize. Specifying a positive value scans that number of subfolders. Contained elements MaxEventQueueThreads.5 CONFIGURATION AND ADMINISTRATION GUIDE 147 XML configuration files reference Directory Located in the Httpd container. The parent folder is specified in the SWFFolder element. Contained elements MinIOThreads. The elements nested within the Edge container configure the RTMP protocol for the fmsedge process. MaxIOThreads. . 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. Specifying a negative value scans all subfolders. SocketTableSize. 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. DirLevelSWFScan Specifies the number of levels of subfolders within a parent folder to scan for SWF files. NumSchedQueues EdgeCore Container element. MinEventQueueThreads. MaxIOThreads.Last updated 3/2/2010 FLASH MEDIA SERVER 3. The elements nested within the ECCP container configure ECCP (Edge Server-Core Server Communication Protocol). The default value is Apache2. SocketOverflowBuckets Edge (ResourceLimits) Container element. The directory containing the web server. See also SWFFolder ECCP Container element. Contained elements MinIOThreads. which means that the server scans only one subfolder level. Specifying zero scans the parent folder and no subfolders. SocketOverflowBuckets. CoreTimeout Edge Container element. The default value is 1.2.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The default value is 1. Example <NetworkingIPv6 enable="false" /> NumCRThreads Located in the RTMP (Connector) container. 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). Order Located in the AdminServer container. 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. set: <Order>Deny. if desired. This is an empty tag. The default value is 1024 bytes.Last updated 3/2/2010 FLASH MEDIA SERVER 3. You can tune the size of each cache. Flash Media Server automatically detects the operating system configuration. depending on the type of content you are delivering. and other data in memory. The operating system network stack should be configured to support IPv6. Example To process the request if not in <Deny> or in <Allow>. . Specifies the order in which to evaluate the Allow and Deny elements.Allow</Order> To process the request if in <Allow> and not in <Deny>. Options Located in the Httpd container. Deny</Order> OtherAutoBufferReadSize Located in the Playback container. audio. The number of scheduler queues. Example <NumCRThreads>0</NumCRThreads> NumSchedQueues Located in the Edge (ResourceLimits) container. Each data type (audio. set: <Order>Allow. and other) has its own cache. video. The minimum size is 1024 bytes. Specifies the number of completion routine threads in Windows 32-bit systems for edge server I/O processing.

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

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

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

This container holds the elements that configure RTMP (Real-Time Messaging Protocol). RTMP is the protocol used for communication between Flash Player and Flash Media Server. The default is server. SegmentsPool Container element. Scope Located in the Logging container.) The default value is true. MinConnectionThreads. GlobalRatio. Contained elements MaxCacheUnits. Specifies whether Encrypted Real-Time Messaging Protocol (RTMPE) can be used to connect to the Administration Server. This element determines whether to write a separate log file for each virtual host or to write one log file for the server. MaxConnectionQueueSize RTMP (Protocol) Container element. 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. Contained elements Edge. Contained elements MinIOThreads. Allocates 2xN threads. SocketSndBuf. (RTMPE also covers RTMPTE. Core. FreeRatio. MaxAge. SocketRcvBuff RTMPE Located in the RTMP container. Setting this element to false prohibits RTMPE and RTMPTE from being used. . Admin. NumCRThreads. UpdateInterval. MaxConnectionThreads.Last updated 3/2/2010 FLASH MEDIA SERVER 3. MaxCacheSize. The value for this element is server or vhost. Allocates 1xN threads. which enables logging for all processes on the server. FreeMemRatio Server Container element. MaxIOThreads.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. MaxUnitSize.

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

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

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

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

SSLCACertificatePath.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 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. Example <SSLRandomSeed>ALL:!ADH:!EDH</SSLRandomSeed> . SSLVerifyDepth. SSLCipherSuite SSLRandomSeed Located in the SSL container. Specifies how often to flush expired sessions from the server-side session cache. Contained elements SSLVerifyCertificate.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. Configures the server to act as an SSL-enabled client by securing the outgoing connections.0 ciphers All ciphers using DSS authentication SSLClientCtx Container element.

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

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

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

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

This element lists those hosts from which the administrator is not authorized to connect to Flash Media Administration Server. Setting this element enables HTTP requests to execute administrative commands. Allow (HTTPCommands). Example <Enable>true</Enable> See also Allow (HTTPCommands).1. do not set this element. Order (User) Enable This element enables or disables the use of HTTP requests to execute administrative commands. This Deny element lists the Flash Media Administration Server commands that an administrator cannot use through HTTP.60.10. 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. 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. Deny (HTTPCommands).10.Allow</Deny> See also Enable.60</Deny> See also Password.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. To disable administrative access through the use of HTTP requests. . <Deny>foo.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example This example lists the computers sending connection requests that Flash Media Administration Server will not accept. Order (HTTPCommands) HTTPCommands Container element.yourcompany. Allow (User).com.133.com. Example <Deny>Deny. 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.adobe.

Allow (HTTPCommands). 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 (HTTPCommands) Order (User) Flash Media Server uses two Order elements: one in the HTTPCommands container. Deny (HTTPCommands). Specifies the order in which to evaluate the Deny and Allow commands. Example The default sequence Allow.Allow</Order> See also Password.Last updated 3/2/2010 FLASH MEDIA SERVER 3. restart the server.Deny</Order> See also Enable. the encrypt attribute instructs the server to encrypt the contents of the password. <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. Contained elements Enable. Specify each Administration API that may be called over HTTP in a commadelimited list. Passwords cannot be empty strings (""). The default value is ping.Deny</Order> The alternative sequence Deny. and the other in the User container. Allow (User). . Example The sequence Deny. When finished. <Order>Deny. Passwords are usually encrypted. When the encrypt attribute is set to true. In the following example.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. Allow means the HTTP command is allowed if the command is in the Allow list of commands or not in the Deny list. Allow (HTTPCommands). the password you see in the file is the encrypted password. <Order>Deny. Deny (User) Password Specifies the password for vhost administrators. Deny means the HTTP command is allowed if it is in the Allow list of commands and not in the Deny list. Specifies the sequence in which Flash Media Server evaluates the Allow and Deny elements for an administrator. Order (HTTPCommands) Order (HTTPCommands) Flash Media Server uses two Order elements: one in the HTTPCommands container and another in the User container. and it is interpreted as an encoded string.Allow</Order> The sequence Allow.

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

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

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

MaxAppInstances. • 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. AggregateMessages AppInstanceGC Specifies how often to check for and remove unused resources for application instances. • In Windows. such as Shared Objects. The default interval is 1 minute. You define an application by creating a subdirectory with the application name. without modification. Streams. . Note: If you use this tag to map to a network drive. • 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. EdgeAutoDiscovery. • 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. You can create a chain of proxies by specifying them in the URI. • Any anonymous proxy in the chain passes on. the default location is /opt/adobe/fms/applications. MaxStreams. CacheDir. the routing information in the URI to the next edge server in the chain. the default AppsDir location is C:\Program Files\Adobe\Flash Media Server 3. The Applications directory is the base directory where all applications for this virtual host are defined.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Example <Anonymous>falsetrue</Anonymous> See also Mode. RouteTable. Example <AppInstanceGC>1</AppInstanceGC> See also MaxConnections. see “Mapping directories to network drives” on page 34 for additional information. LocalAddress. and Script engines. • In Linux. • The routing information in the URI for a chain of explicit proxies specifically identifies the sequence of edge servers in the chain. MaxSharedObjects AppsDir Specifies the Applications directory for this virtual host.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 URI for an explicit proxy specifies the edge server(s) that will intercept connection requests to the origin server.5\applications. MaxEdgeConnections.

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

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

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

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

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

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

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

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

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

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

Last updated 3/2/2010 FLASH MEDIA SERVER 3. and reject export-strength versions.5 CONFIGURATION AND ADMINISTRATION GUIDE 192 XML configuration files reference This string instructs the server to accept only high. with the high being preferred. DES) 128-bit encryption Triple-DES encoding . <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.and medium-strength 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 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. <SSLCipherSuite>ALL:+SSLv2</SSLCipherSuite> The following is the complete list of components that the server can evaluate.

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

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

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

lock count %2$S. process will be terminated. Failed to start the following listeners for adaptor %1$S: %2$S. Failed to create listener for adaptor %1$S. Server initialization failed. Failed to stop %1$S listeners for adaptor %2$S. Asynchronous I/O operation failed (%1$S: %2$S). and httpcache. Command name not found in the message. Failed to stop virtual host (%1$S). Server starting. Failed to create thread (%1$S). .log. Unlock called without matching lock for shared object %1$S. see “Access logs” on page 57 and “Application logs” on page 63. edge. Nested lock for shared object %1$S. Service Control Manager reported (%1$S: %2$S). or users that you can use for debugging.log. invalid parameters: call(methodName[. Service Control Manager failed (%1$S: %2$S).xx... service will be stopped. Ignoring message from client during authentication.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. Response object not found (%1$S). IP %2$S. Reinitializing server. For status codes related to applications. lock count %2$S. pn]). admin.log. server shutdown in progress. 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.xx. p1.log) record information about server operations. Invalid application.xx. instances. Clients not allowed to broadcast message. rejecting message (%1$S). The call method failed. Missing unlock for shared object %1$S.log. core. resultObj.xx. Method not found (%1$S). server shutdown in progress. Server stopped %1$S. Received interrupt signal. Failed to execute method (%1$S). port %3$S: %4$S. Message IDs can be useful for administrators who want to write error-handling scripts.xx. Dropping application (%1$S) message.

Last updated 3/2/2010 FLASH MEDIA SERVER 3. Admin request received from an invalid Administration Server. Failed to create administrator: %1$S. Reserved property (%1$S). Invalid user ID (%1$S). Rejecting connection from %1$S to %2$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. Unknown %1$S command issued for stream %2$S (application %3$S). Invalid proxy object. terminating connection: %1$S. Unable to create shared object: %1$S. Write access denied for stream %1$S. Unable to create stream: %1$S. Resource limit violation. %2$S ): %3$S. Connect failed ( %1$S.Failed Invalid application name (%1$S). Write access denied for shared object %1$S. Failed to remove administrator: %1$S. Read access denied for stream %1$S. Failed to open configuration file: %1$S. Failed to start server. Invalid parameters to %1$S method. Virtual host %1$S is not available. Bad network data. Failed to start virtual host (%1$S). Resource limit violation. Exception while processing message. No adaptors defined. Adaptor already defined with the name %1$S. Script execution is taking too long. connection may be lost (%1$S). Alive. Parse error at line %1$S: %2$S. Illegal subscriber: %1$S cannot subscribe to %2$S. Read access denied for shared object %1$S. Connect from host (%1$S) not allowed. NetConnection. Administrator login failed for user %1$S.Call. Failed to change password: %1$S. .

Audio receiving disabled (stream ID: %1$S). Illegal access property (%1$S). Stream %1$S has been idling for %2$S second(s). Pausing %1$S. Unpausing %1$S. Connection rejected: maximum user limit reached for application instance %1$S. Failed to restart virtual host (%1$S). %3$S) : Failed to load application instance %1$S. Recording %1$S. Started playing %1$S. %2$S). New NetStream created (stream ID: %1$S). Publishing %1$S. Failed to publish %1$S. (%2$S. Playing and resetting %1$S. %1$S is now published. Admin user requires valid user name and password.CommandFailed Invalid parameters to %1$S method. Error registering class: name mismatch (%1$S. Connection to Flash Media Server has been disconnected. Invalid virtual host alias : %1$S. Stopped playing %1$S. Audio receiving enabled (stream ID: %1$S).Admin. . Failed to unload application %1$S. Failed to play (stream ID: %1$S). Client already connected to an application.Last updated 3/2/2010 FLASH MEDIA SERVER 3. %1$S is now unpublished. (%2$S. Failed to load application %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. Failed to record %1$S. Play stop failed. stream ID: %1$S. Stopped recording %1$S. %1$S applications unloaded. NetStream deleted (stream ID: %1$S). Failed to play %1$S (stream ID: %2$S). %3$S) : Connection rejected to application instance %1$S.

%3$S): Invalid application name (%1$S). App: %3$S). Failed to flush shared object (%1$S). JavaScript runtime is out of memory. Video receiving disabled (stream ID: %1$S). Failed to open shared object file (%1$S) for read. Unknown exception caught in %1$S. Connection failed. Failed to initialize listeners for adaptor %1$. Set video fps to %1$S (stream ID: %2$S). Failed to start listeners for adaptor %1$S.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). Failed to play %1$S. Failed to seek (stream ID: %1$S). Video receiving enabled (stream ID: %1$S). Take action. server shutting down instance (Adaptor: %1$S. Invalid stream name (%1$S). VHost: %2$S. Flash Media Server is already running or other processes are using the same ports. Invalid schedule event format (%1$S). Configuration error for adaptor %1$S: IP %2$S and port %3$S are already in use. Failed to receive video (stream ID: %1$S). Failed to stop playing (stream ID: %1$S). Invalid method name (%1$S).Last updated 3/2/2010 FLASH MEDIA SERVER 3. Failed to seek %1$S (stream ID: %2$S). Check the JavaScript runtime size for this application in the configuration file. (%2$S. Failed to create adaptor: %1$S. Server started (%1$S). Invalid NetStream ID (%1$S). 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 . Failed to open shared object file (%1$S) for write. Seeking %1$S (stream ID: %2$S). JavaScript engine runtime is low on free memory. stream not found. Insufficient admin privileges to perform %1$S command. Connection succeeded. Invalid shared object (%1$S). Configuration file not found: %1$S Invalid configuration file: %1$S Server aborted.

Call. Admin command setApplicationState failed for %1$S. Rejecting connection to: %1$S. %3$S): Resource limit violation. (%2$S. Breaking potential deadlock. Trial run expired. Failed to load admin application. Rejecting connection. Failed to play %1$S. Pause %1$S failed. Server shutting down. Invalid admin command: %1$S.BadValue Publish %1$S failed. index file not found or mismatch. Unable to load new application: %1$S. Rejecting connection. Unable to locate script file: %1$S. (%2$S. Unable to create new application instance: %1$S. Invalid shared object file (%1$S).Call. %3$S): Application (%1$S) is currently offline. Server shutdown failed. . (%2$S.Last updated 3/2/2010 FLASH MEDIA SERVER 3.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). shared object(%1$S) lock reset to unlocked. Invalid object name (stream ID: %1$S). Multiprocessor support available only in Enterprise Edition. %3$S): Application (%1$S) is not defined. Command successful. invalid arguments. %3$S/%1$S): Current virtual host bandwidth usage exceeds max limit set. Script is taking too long to process the event. shared object (%1$S) has been locked for %2$S sec. (%2$S. (%2$S.Success Unable to locate server configuration file during startup. Potential deadlock.AccessDenied NetConnection. Unable to create directory %1$S. (%2$S. invalid arguments. %3$S): Resource limit violation. License key specified does not allow multiple virtual host support. (%2$S. NetConnection. Beta expired.Call. %3$S/%1$S): Current server bandwidth usage exceeds license limit set. Preload application aborted. Shutting down instance: %1$S. %3$S): Resource limit violation. NetConnection. Invalid license key: %1$S License key specified does not allow multiple adaptor support.

%3$S): Max connections allowed exceed license limit.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Failed to seed the pseudorandom number generator. Rejecting connection request Host: %2$S:%3$S. Invalid shared object name (%1$S). Exception caught in %1$S while processing streaming data inside %2$S. System memory load (%1$S) is high. 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. Client to server bandwidth limit exceeded. no space left on device. Pending queue size limit %1$S reached. Error from %1$S:%2$S. System memory load (%1$S) is now below the maximum threshold. using %3$S. Listener started (%1$S): %2$S. Failed login attempt from %1$S at %2$S. Current %3$S] . Info from %1$S:%2$S. Attempt to reconnect to Flash Media Server. Unknown exception occurred. Out of memory: %1$S. Failed to execute admin command: %1$S. Instance will be unloaded: %1$S. Failed to remove application: %1$S. Max Allowed %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. Failed to record %1$S. Adaptor (%1$S) has an SSL configuration error on port %2$S. Exception while processing message: %1$S. Warning from %1$S:%2$S. adaptor not found: %2$S. Failed to play %1$S. Unloaded application instance %1$S. (%2$S. Restarting listener (%1$S): %2$S. Rejecting connection to: %1$S. [Virtual host (%1$S). Failed to initialize cryptographic accelerator: %1$S. Generic message code. An internal version control error has occurred. Invalid cryptographic accelerator: %1$S. Invalid value set for configuration key: %1$S = %2$S.

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

Command (%1$S) timed out. Proxy to core (%1$S) failed. Socket migration to core (%1$S) failed. Registering core (%1$S). Core (%1$S) sending register command to edge. Core (%1$S) failed to establish proxy to edge. Connection to admin received. Core (%1$S) failed to connect to admin. . Recovering core %1$S with %2$S failure[s] after %3$S seconds! Core (%1$S) did not shut down as expected. Failed to send connect response to core %1$S. Core (%1$S) connection to admin failed. Starting admin app on core (%1$S). Core (%1$S) received close command from admin. Core (%1$S) socket migration failed. Core (%1$S) connection to admin accepted.Last updated 3/2/2010 FLASH MEDIA SERVER 3. create a new one. Process (%1$S): shared memory (%2$S) init failed. Core (%1$S) disconnected from edge. Core (%1$S): Failed to initiate connection to admin. Connection from core %1$S accepted.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. Edge disconnected from core (%1$S). Core (%1$S) connecting to admin. Core (%1$S) shutdown failed. Core (%1$S) connected to admin. Process (%1$S): failed to map view of shared memory (%2$S). 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. Core (%1$S) disconnecting from admin. Killing core now. Core (%1$S) disconnected: %2$S. Connection from core %1$S received.

SWF verification failed. disconnecting client. SWF verification unsupported by client. disconnecting client. . OpenProcess(PROCESS_QUERY_INFORMATION) failed for pid (%1$S) with %2$S.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 timeout. disconnecting client.Last updated 3/2/2010 FLASH MEDIA SERVER 3.

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 .xml file description of tags 80 file structure 80 Adaptor.Last updated 3/2/2010 205 Index A access logs 29. 38 application instances about 6 log messages 43 performance 47 reloading 43 view in Administration Console 42 application logs 63 Application object. defining 31 Application. 59 Adaptor. 57.xml file description of tags 93 Application.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.

xml 178 connections closing idle 14 limiting 14.xml 80 Application. native 32 C CGI programs 39 checkpoint events 29.Last updated 3/2/2010 FLASH MEDIA SERVER 3. in video files 71 Event Viewer (Windows) 67 . 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 175 Vhost. using 23 CrossDomainPath (Server.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.xml 93 directory structure 6 editing 9 Logger. 57 clients closing idle connections of 14 limiting connections from 14 view active 45 clusters 1 configuration files Adaptor.xml 133 Server. 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) 23.xml 140 symbols in 10 Users.

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.5 CONFIGURATION AND ADMINISTRATION GUIDE 207 Index F FLV errors 71 FLV files. configuring 16 Server. checking 69 FLVCachePurge (Server. 135.xml) 123 R RecordsNumber 164 refresh rate 41 RetryNumber 165 RetrySleep 165 rotating log files 56 S scripts.xml) 123 Q QualifiedStreamsMapping (Application.xml tags Access 140. on Linux 74 performance 51 starting and stopping 66 testing 67 viewing events 67 server processes. configurable 31 P performance improving 12 monitoring server 51 permissions administration APIs 76 for administrators 175 PublishTimeout (Application. 140 Server. 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.xml tags Access 134.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. 179 ACCP 140 ActiveProfile 141 Admin 141 AdminElem 141 AdminServer 141 Allow 141 Application 142 ApplicationGC 142 AuthEvent 143 AuthMessage 143. 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 .xml file 55. 136.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml file configuring 55 description of tags 133 file structure 134 Logger. 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 28 storage directories 34 storageDir element 34 streams cache size 12 chunk size 13 view live 44 U Users. 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. 172 SSLCACertificateFile 169.xml 27.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. 164.xml file description of tags 175 file structure 175 permissions for admin APIs 76 summary of tags 175 Users. 28 tags in VHost. 26 tags in Server.xml file file structure 179 summary of tags 179 Vhost. 193 SSLVerifyDepth 172. 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. 190 SSLClientCtx 171 SSLRandomSeed 171 SSLSessionCacheGC 172 SSLVerifyCertificate 172. 168. 190 SSLCACertificatePath 169. 190 SSLCipherSuite 169. 163.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml tags AggregateMessages 179 Alias 179 AliasList 180 Allow 180 AllowOverride 180 Anonymous 180 .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 25.

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.xml) 133 .

Sign up to vote on this title
UsefulNot useful