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