Flash Media Server Install
Flash Media Server Install
® ®
SERVER
INSTALLATION GUIDE
© 2007 Adobe Systems Incorporated. All rights reserved.
Adobe® Flash® Media Server Installation 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 trans-
mitted, 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 Incorpo-
rated. 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, Flash, and Flex are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Windows is either a registered trademark or a trademark of Microsoft Corporation inthe
United States and/or other countries. All other trademarks are the property of their respective owners.
Portions include software under the following terms:
Sorenson™ Spark™ video compression and decompression technology licensed from Sorenson Media, Inc.
Licensee shall not use the MP3 compressed audio within the Software for real time broadcasting (terrestrial, satellite, cable or other media), or broadcasting via Internet or other
networks, such as but not limited to intranets, etc., or in pay-audio or audio on demand applications to any non-PC device (i.e., mobile phones or set-top boxes). Licensee
acknowledges that use of the Software for non-PC devices, as described herein, may require the payment of licensing royalties or other amounts to third parties who may hold
intellectual property rights related to the MP3 technology and that Adobe has not paid any royalties or other amounts on account of third party intellectual property rights for
such use. If Licensee requires an MP3 decoder for such non-PC use, Licensee is responsible for obtaining the necessary MP3 technology license.
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.
iii
Contents
Chapter 1: Before you begin
Overview of Flash Media Server ........................................................... 1
About the documentation ................................................................ 1
Support .................................................................................. 2
Third-party resources ..................................................................... 2
Typographical conventions ................................................................ 2
• Adobe Flash Media Interactive Server Plug-in API Reference documents the C++ API you use to create plug-ins.
Support
You may want to explore these other sources of support for Flash Media Server:
• The Flash Media Server Support Center at www.adobe.com/go/flashmediaserver_support_en provides
TechNotes and up-to-date information about Flash Media Server.
• The Flash Media Server DevNet site at www.adobe.com/go/flashmediaserver_desdev_en provides tips and
samples for creating Flash Media Server applications.
• The Flash Media Server Online Forum at www.adobe.com/go/flashmediaserver_forum_en provides a place for
you to chat with other Flash Media Server users.
• For late-breaking information and a complete list of issues that are still outstanding, read the Flash Media Server
release notes at www.adobe.com/go/flashmediaserver_releasenotes_en.
Third-party resources
Adobe recommends several websites with links to third-party resources on Flash Media Server, including the
following:
• Adobe Flash Media Server community sites
• Adobe Flash Media Server books
• Object-oriented programming concepts
You can access these websites at www.adobe.com/go/flashmediaserver_resources_en.
Typographical conventions
The following typographical conventions are used in this manual:
• Code font indicates ActionScript statements, HTML tag and attribute names, and literal text used in examples.
• Italic indicates placeholder elements in code or paths. For example, attachAudio(source) means that you
should specify your own value for source; /settings/myPrinter/ means that you should specify your own location for
myPrinter.
• Directory paths are written with forward slashes (/). If you are running Flash Media Server on a Windows
operating system, replace the forward slashes with backslashes. When a path is specific to the Windows operating
system, backslashes (\) are used.
3
System requirements
For the most up-to-date requirements, see http://www.adobe.com/go/learn_fms_sysreqs_en.
Note: When CPU usage of the server is above 80%, quality of service cannot be guaranteed.
Preparing to install
Designing a deployment
A Flash Media Server deployment can be as simple as one computer or as complex as multiple clusters of edge servers
and origin servers with authentication and content storage performed on separate computers. For information about
designing a deployment, see the Technical Overview.
You must run the installer on each computer on which you want to run Flash Media Server. After running the
installer, you can configure the server to run as an origin server or an edge server.
Some antivirus programs, such as Panda Antivirus, and programs that install their own wrappers for system-level
socket calls may cause Flash Media Server to fail. (Other antivirus programs, such as Norton AntiVirus™, are
compatible with Flash Media Server.) If you are experiencing problems with Flash Media Server and have antivirus
software installed, try removing the antivirus program.
Do not run Flash Media Server with virtualization software. Virtualization software impacts server performance and
is an unsupported configuration.
Preparing to upgrade
Workflow for upgrading
Upgrade paths
You can upgrade to Flash Media Interactive Server 3 from any Flash Media Server 2 installation or from Flash Media
Streaming Server. There is no upgrade path to Flash Media Streaming Server.
The Flash Media Server 3 installer performs the following:
1 (Windows only) Saves the existing serial number, applications directory, and conf directory (which contains the
configuration files).
2 Uninstalls the existing Flash Media Server 2 installation.
3 Prompts for a serial number. If you do not enter a serial number, Flash Media Development Server is installed.
Back up data
1 Before you upgrade to Flash Media Server 3, save copies of the following folders to another computer or to
external media:
• conf/
• licenses/
• modules/
• applications/
2 After installing the server, do the following:
ADOBE FLASH MEDIA SERVER 5
Installation Guide
• Modify the new configuration files to match the settings from your old files that you want to keep, for
example, host port settings, application and streams virtual folder settings, and so on. Restart the server.
• You don’t need to copy your license files to Flash Media Server 3, as there are no upgrade paths for license
files.
• If you have C++ plug-ins (also called adaptors) that you want to reuse, you must recompile them. On
Windows, use MicrosoftVisual Studio .NET 2003 or Microsoft Visual C++ 2005. On Linux, use GNU Compiler
Collection 3.4.x. For more information, see Working with plug-ins in Adobe Flash Media Interactive Server Plug-
in Developer Guide.
• Copy any applications you want to deploy on Flash Media Server 3 to the RootInstall/applications folder.
13 If you have a Flash Media Server 3 license (LIC) file, place it in the RootInstall/licenses folder and restart the
server.
14 To verify your installation, see Verifying installation.
11 If you have a Flash Media Server 3 license (LIC) file, place it in the RootInstall/licenses folder and restart the
server.
12 To verify your installation, see Verifying installation.
Use the fmsmgr utility to perform other tasks as well, such as configuring the service to start automatically when the
system is started. For more information, see “Managing the server on Linux” on page 72 in the Configuration and
Administration Guide.
applications Folder The default directory that holds Flash Media Server applications. When you create
an application, create a folder in the applications folder with the application’s name,
for example, applications/mediaApp. Use this name in the client NetConnection call
to connect to the application (for example,
nc.connect("rtmp://someFMSserver.com/mediaApp")).
You can change the location of the applications directory in the Flash Media Server
3/conf/fms.ini file or in the AppsDir tag in the Vhost.xml configuration file.
certs Folder The certificates of trusted Certificate Authorities. The installer imports certifications
from the Microsoft Windows certificate store into a format and location accessible
by Open SSL.
conf Folder Contains the hierarchy of XML configuration files and the fms.ini file.
licenses Folder Contains the LIC files (signed FMS licenses). The LIC file establishes the licensed
capabilities of the server.
logs Folder As soon as the server is started, it creates a logs directory containing all of the server
logs.
modules Folder Contains plug-ins that extend the functionality of the server.
scriptlib Folder Contains Server-Side ActionScript (ASC) files to use in server-side scripts. You can
change this location in the ScriptLibPath tag in the Application.xml file.
tools Folder Contains BAT files that you can use to start or stop the main server and the Adminis-
tration Server. Also contains the fmscheck.exe, flvcheck.exe, and far.exe tools.
FMSAdmin.exe File Flash Media Administration Server. When administrators connect to the server with
the Administration Console, they are actually connected to the Administration
Server, which communicates with the server to perform administration tasks. To call
an Administration API, Flash Media Administration Server must be running.
FMSCore.exe File The executable where Flash Media Server services run. All script execution and
streaming takes place from this location.
FMSEdge.exe File Monitors for connections to Flash Media Server, and passes connections to an
FMSCore process. There can be more than one instance of FMSEdge running on the
system.
fms_adminConsole.swf and Files The Administration Console and the HTML page in which it is embedded.
fms_adminConsole.htm
ReadMe.htm File Late-breaking information and important details about Flash Media Server.
Miscellaneous DLL files Files The server uses various DLL files to provide functionality that the Windows platform
can’t provide, including js32.dll, the Server-Side ActionScript engine (Mozilla
SpiderMonkey).
applications Directory The default directory that holds Flash Media Server applications. When you create
an application, create a folder in the applications folder with the application’s name,
for example, applications/mediaApp. Use this name in the client NetConnection call
to connect to the application (for example,
nc.connect("rtmp://someFMSserver.com/mediaApp")).
You can change the location of the applications directory in the Flash Media Server
3/conf/fms.ini file or in the AppsDir tag in the Vhost.xml configuration file.
conf Directory Contains the hierarchy of XML configuration files and the fms.ini file.
licenses Directory The directory in which to copy LIC files (signed FMS licenses). The LIC file establishes
the licensed capabilities of the server.
logs Directory As soon as the server is started, it creates a logs directory containing all of the server
logs.
modules Directory Contains plug-ins that extend the functionality of the server.
scriptlib Directory Contains Server-Side ActionScript (ASC) files to use in server-side scripts. You can
change this location in the ScriptLibPath tag in the Application.xml file.
fms_adminConsole.swf and Files The Administration Console and the HTML page in which it is embedded.
fms_adminConsole.htm
fmsadmin File The Flash Media Administration Server. When administrators connect to the server
with the Administration Console, they are actually connected to the Administration
Server, which communicates with the server to perform administration tasks. To call
an Administration API, this file must be running.
ADOBE FLASH MEDIA SERVER 12
Installation Guide
fmscore File The executable where Flash Media Server services run. The way the server is config-
ured determines how many services run on a single FMSCore. All script execution
and streaming takes place from this location.
fmsedge File Monitors for connections to Flash Media Server and passes connections to a
FMSCore process. There can be more than one instance of FMSEdge running on the
system.
ReadMe.htm File Late-breaking information and important details about Flash Media Server.
far tool Command-line compiler utility that lets you package all server-side scripts into one
archive file.
fms Script Packages the combination of calling adminserver and server at the same time.
fmsconfig and fmsini Files Configuration files used by the server during installation.
fmsmgr Script Starts and stops the server. It also checks on status and other actions, such as
controlling autostart status.
adminserver Script Start, stop, and restart the Administration Server directly. This script is also used to
set up fmsadmin correctly.
Publish a stream
1 Double-click the RootInstall/samples/applications/vod/vodtest.html file to open the application in a browser.
2 Click Go to stream the sample.flv file or select another version of the sample file from the drop-down menu and
click Go.
3 If you can’t see the video playing, take the following steps:
• Verify that the RootInstall/applications/vod directory is installed and contains the following files:
allowedHTMLdomains.txt, allowedSWFdomains.txt, Application.xml, and main.far. The RootInstall/applica-
tions/vod/media folder should contain the media files. If any files are missing, uninstall and reinstall the server.
• Use the Services window (Windows) or the service window (Linux) to verify that Flash Media Server and
Flash Media Administration Server are running.
• Verify that the URL in the sample vod client is rtmp://localhost/vod/sample.flv.
• Check the system logs for errors.
• Contact Adobe Support.
For information about configuring the vod service for use in a production environment, see Adobe Flash Media
Server Developer Guide.
• Verify that the RootInstall/applications/live directory is installed and contains the following files:
allowedHTMLdomains.txt, allowedSWFdomains.txt, Application.xml, and main.far. If it doesn’t, uninstall and
reinstall the server.
• Use the Services window (Windows) or the service window (Linux) to verify that Flash Media Server and
Flash Media Administration Server are running.
• Verify that the URL in the sample live client is rtmp://localhost/live/livestream.
• Verify that the URL in Flash Media Encoder is rtmp://localhost/live and the Stream is livestream.
• Check the system logs for errors.
• Contact Adobe Support.
For information about configuring the live service for use in a production environment, see the Developer Guide.
INDEX 15
Index
A streaming video 13
adaptors. See plug-ins support 2, 3
Administration Console 12
connecting on Linux 13 T
connecting on Windows 12 third-party software conflicts 3
C U
community 2 uninstalling
conflicts, software 3 from Linux 8
from Windows 8
D upgrade paths 4
data, backing up 4
documentation 1 V
video on demand.See vod service
E video, streaming 13
edge server, installing 3 vod service 13
F W
Flash Media Encoder 13 Windows, installing on 5
FlashMediaServer3.exe file 5
FlashMediaServer3.tar.gz file 6
forums 2
L
license files 3, 6
license numbers 6
Linux, installing on 6
live service 13
O
origin server, installing 3
P
plug-ins, recompiling 5
publishing point 13
R
release notes 2
resources 2
S
serial keys.See serial numbers 3
serial numbers 3, 5
software conflicts 3