Macromedia flash media server 2-managing flash media server ユーザーズマニュアル

ページ / 238
11
1
CHAPTER 1
Managing the Server
As a Flash Media Server administrator, you’ll need to perform several administrative tasks after 
the server is installed. This chapter describes how Macromedia Flash Media Server is 
configured when you first install it, how to set up additional administrators, and how to 
monitor the server’s activity. For many of these tasks, you’ll use the management console that 
was installed with the server. This chapter describes the management console in detail. 
Basic server settings
The server is installed with a set of configuration files in XML format. These files define a 
default server adaptor, a default applications directory, default server administrators, and 
default settings for application behavior.
The default server adaptor uses port 1935, the number assigned to Flash Media Server by the 
Internet Assigned Numbers Authority 
). Although you can use any port 
number, this increases the risk of conflicting with another application that may be assigned to 
the same port; for example, if you configure the server to use port 80 to support HTTP 
tunneling, the server might not run both a web server and the Flash Media Server bound to 
port 80. Applications must be authored to connect to the same port the server is using, in the 
NetConnection.connect statement. Be sure the port is not blocked by a firewall. 
The server is preconfigured with one adaptor containing one virtual host. The virtual host is 
equivalent to a domain name. The default applications directory for the default virtual host is 
the applications directory in the Flash Media Server 2 directory. You can view this location by 
looking at the value for the 
AppsDir
 tag in the vhost.xml file. This directory is where the 
server will look for application subdirectories at startup; you must place an application 
subdirectory here for each client application that you plan to connect to the server, and the 
client subdirectory must have the same name as the client application. The presence of the 
application subdirectory registers the application with the server.