10
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Deploying the server
Last updated 11/28/2012
3
Validate the XML and save the Vhost.xml file.
Element
Required/optional
Description
Mode
Required
Enter
local
to configure the server to run as an origin server. Enter
remote
to configure the server to run as an edge server.
Anonymous
Optional
A Boolean value specifying whether the edge server connection is implicit
(
true
) or explicit (
false
). The default value is
false
.
CacheDir
Optional
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
useAppName
.
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.
LocalAddress
Optional
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.
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.
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.
RouteEntry
Optional
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
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.