47
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
It’s a good idea to register the RTMP, RTMPS, and RTMPE protocols with a network services database and use a
service name (or decimal port number, if necessary) in the server configuration files.
Check the logs
When the server starts, it logs available stack configuration, host name, and all available IP addresses for the host in
the master.xx.log, edge.xx.log, and admin.xx.log files (located in the
rootinstall
/logs/ directory). The following x-
comment fields from a sample edge log file indicate that the IPv6 stack and the IPv4 stack are available, 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.133.192.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
On Red Hat Linux, the edge logs display only the highest IP version the socket listeners are using, even if the socket
listeners accept connections over both IPv4 and IPv6. In the previous example, only the v6 entries would be displayed.
On IPv6-enabled Linux, if you are using an host name that resolves to IPv4 host name with an RTMPT or RTMPTE
connection, configure the Adaptor.xml appropriately to resolve connections quickly. See “
HTTPIdent2
” on page 128.
Defining Application object properties
You can define properties for the server-side Application object in the server’s Application.xml configuration files. If
you define properties in the default Application.xml file, the properties are available for all applications on a virtual
host. If you define properties in an Application.xml file in an application folder, the properties are available only for
that application.
To define a property, create an XML tag in the
ScriptEngine
section of the Application.xml file. The property name
corresponds to the tag’s name, and the property value corresponds to the tag’s contents.
For example, the following XML fragment defines the properties
user_name
and
dept_name
, with the values
jdoe
and
engineering
, respectively:
<Application>
<ScriptEngine>
<config>
<user_name>jdoe</user_name>
<dept_name>engineering</dept_name>
</config>
</ScriptEngine>
</Application>
To access the property in server-side code, use the syntax in either of these examples:
application.config.prop_name
application.config["prop_name"]
Note:
The properties you define are accessible from
application.config.property
, not from
application.property
.
For example, given the previous XML fragment, the following
trace()
statements are valid: