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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

4 Select a server from the list. 3 Click Server Log.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. 5 To locate a specific string.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 2 Click Manage Servers. Use the Find Previous and Clear Log buttons as necessary. 1 Follow the steps in “Connect to the Administration Console” on page 40. . type it in the Find text box and click Find Next.

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

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

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

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

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

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

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

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

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

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

5 CONFIGURATION AND ADMINISTRATION GUIDE 65 Monitoring and Managing Log Files Field x-pid x-status Event(s) All All Description Server process ID. The last four characters represent message ID. All message IDs are listed in “Diagnostic Log Messages” on page 196. The first three characters represent severity.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Status code: The code is a 10-character string that represents the severity. category. x-stx All Event-dependent context information. and message ID. All categories are listed in “Status categories in diagnostic logs” on page 65. 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 . as follows: (w) = warning (e) = error (i) = information (d) = debug (s) = trace from server-side script (_) = unknown The next three characters represent category.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Do not set this number too low. The number must be long enough to establish a TCP connection.Last updated 3/2/2010 FLASH MEDIA SERVER 3.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. Example <WaitTime>1000</WaitTime> See also Enabled. perform a UDP broadcast. AllowOverride . and return an XML response.

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

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

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

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

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

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

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

Core (%1$S) connection to admin 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. Connection to admin received. Socket migration to core (%1$S) failed. Core (%1$S) shutdown failed. create a new one. Registering core (%1$S). . Proxy to core (%1$S) failed. Core (%1$S) connected to admin. Process (%1$S): shared memory (%2$S) init failed. Core (%1$S) failed to establish proxy to edge.Last updated 3/2/2010 FLASH MEDIA SERVER 3. Core (%1$S) disconnecting from admin. Core (%1$S) failed to connect to admin. Core (%1$S) sending register command to edge. Core (%1$S) disconnected from edge. Core (%1$S) connecting to admin. Killing core now. Edge disconnected from core (%1$S). Connection from core %1$S received. Core (%1$S) disconnected: %2$S. Connection from core %1$S accepted. Core (%1$S) received close command from admin. Core (%1$S) connection to admin failed. 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): Failed to initiate connection to admin. Core (%1$S) socket migration failed. Starting admin app on core (%1$S). Command (%1$S) timed out. 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.

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

xml file description of tags 80 file structure 80 Adaptor.Last updated 3/2/2010 205 Index A access logs 29. 57.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. 59 Adaptor. defining 31 Application.xml file description of tags 93 Application.xml tags Access 94 AccumulatedFrames 94 AggregateMessages (Client) 94 AggregateMessages (Queue) 94 Allow 95 AllowDebugDefault 95 AllowHTTPTunnel 95 Application 96 Audio 96 AutoCloseIdleClients 96 AutoCommit 97 AutoSampleAccess 97 Bandwidth 97 BandwidthCap 98 BandwidthDetection 98 Bits 99 BufferRatio 99 Cache 99 CachePrefix 99 CacheUpdateInterval 100 Client 101 ClientToServer (Bandwidth) 101 ClientToServer (BandwidthCap) 101 CombineSamples 102 Connections 102 DataSize 102 Debug 102 DirLevelSWFScan 103 DisallowProtocols 103 Distribute 103 DuplicateDir 104 Duration 104 EnhancedSeek 105 Exception 105 FileObject 106 FinalHashTimeout 106 FirstHashTimeout 106 FlushOnData 106 FolderAccess 106 HiCPU 106 Host 107 HTTP 107 HTTP1_0 107 HTTPTunnel 107 IdleAckInterval 108 IdlePostInterval 108 Interface 109 Interval 109 . 38 application instances about 6 log messages 43 performance 47 reloading 43 view in Administration Console 42 application logs 63 Application object.

xml 133 Server.xml 140 symbols in 10 Users. 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. native 32 C CGI programs 39 checkpoint events 29.xml 175 Vhost. 57 clients closing idle connections of 14 limiting connections from 14 view active 45 clusters 1 configuration files Adaptor.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml 178 connections closing idle 14 limiting 14.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) 23. in video files 71 Event Viewer (Windows) 67 . 146 D debug connection 30 diagnostic logs 64 E edge servers cache 73 chain 5 configuring 2 connecting to 4 deploying 1 file cache (on Linux) 74 file cache (Windows) 73 environmental variables 11 Errors.xml 80 Application. using 23 CrossDomainPath (Server.xml 93 directory structure 6 editing 9 Logger. combining 13 B backing up log files 56 bandwidth detection.

179 ACCP 140 ActiveProfile 141 Admin 141 AdminElem 141 AdminServer 141 Allow 141 Application 142 ApplicationGC 142 AuthEvent 143 AuthMessage 143.xml file configuring 55 description of tags 133 file structure 134 Logger. 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.5 CONFIGURATION AND ADMINISTRATION GUIDE 207 Index F FLV errors 71 FLV files. 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 . checking 69 FLVCachePurge (Server. 135. 136. 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. on Linux 74 performance 51 starting and stopping 66 testing 67 viewing events 67 server processes.xml file 55.Last updated 3/2/2010 FLASH MEDIA SERVER 3.xml) 123 R RecordsNumber 164 refresh rate 41 RetryNumber 165 RetrySleep 165 rotating log files 56 S scripts.xml tags Access 140.xml tags Access 134. 140 Server. See server-side scripts security and RTMPE 23 and SSL 24 configuring features 19 limiting domain access to 23 SWF verification 19 serial keys adding 53 server checking status of 67 hierarchy 6 log file 54 managing.xml) 123 Q QualifiedStreamsMapping (Application. configurable 31 P performance improving 12 monitoring server 51 permissions administration APIs 76 for administrators 175 PublishTimeout (Application. configuring 16 Server.xml) 149 FLVCheck tool 69 FMSCheck tool 67 fmsmgr utility 74 H HTTP proxying 38 I IPv6 configuring 30 disabling 162 enabling 162 on Linux 84 L licenses 53 Linux and IPv6 84 using with Flash Media Server 74 load balancing clusters 1 log files and IPv6 56 application 55 backing up 56 configuration files for 55 diagnostic 55 managing 55 messages 196 rotating 56 server server access 55 web server 55 Logger.

xml file file structure 179 summary of tags 179 Vhost. 164. 26 tags in Server. 190 SSLCACertificatePath 169. 163. 193 SSLVerifyDepth 172.xml tags AdminServer 175 Allow (HTTP Commands) 175 Allow (User) 175 Deny (HTTPCommands) 176 Deny (User) 176 Enable 176 HTTPCommands 176 Order (HTTPCommands) 177 Order (User) 177 Password 177 Root 178 User 178 UserList 178 V variables 11 Vhost.Last updated 3/2/2010 FLASH MEDIA SERVER 3. 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.xml 27. 190 SSLClientCtx 171 SSLRandomSeed 171 SSLSessionCacheGC 172 SSLVerifyCertificate 172. 28 tags in VHost. 172 SSLCACertificateFile 169.xml 25. 168.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. 193 SWFFolder 172 SWFVerification 173 TerminatingCharacters 173 ThreadPoolGC 173 Time 173 TrimSize 173 TTL 173 UID 174 UpdateInterval 174 UpdateInterval (Cache) 174 server-side scripts and configurable object properties 31 setting storage directories 34 shared objects default location of 34 setting location of 34 view active 46 SSL certificates 25 configuring 24 tags in Adaptor.xml file description of tags 175 file structure 175 permissions for admin APIs 76 summary of tags 175 Users.xml tags AggregateMessages 179 Alias 179 AliasList 180 Allow 180 AllowOverride 180 Anonymous 180 .xml 28 storage directories 34 storageDir element 34 streams cache size 12 chunk size 13 view live 44 U Users. 190 SSLCipherSuite 169.

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