
Chapter 214
Once you have specified the directory where you’ll store your application directories, you must
create a directory inside it for each client application you plan to use with that virtual host. Each
client application must have a directory with the same name that the client application uses when
connecting to the server. Once you have created a subdirectory for each of your applications, you
can decide whether to give any of the applications their own Application.xml file. By including an
Application.xml file in a client application’s directory, you can give that application different
settings from those defined in the virtual host’s Application.xml file, which serve as the default
settings for applications on the virtual host. For more information about the Application.xml file,
see Chapter 3, “Configuring Flash Communication Server,” on page 25.
Configuring virtual hosts
With the Enterprise and ISP versions of the server, you can add virtual hosts to the server’s
configuration. This is useful for separating sets of applications and allows you to define
administrators who have access only to a specific virtual host.
Each virtual host on the server is associated with an adaptor. You add a virtual host by adding a
directory inside the adaptor’s directory in the server’s conf directory. The virtual host’s directory
must be named with the virtual host name, such as www.myCompany.com.
Each new virtual host must include the following items:
• A Vhost.xml file.
• An Application.xml file.
• A directory named admin in the virtual host’s flashcom application directory (defined in the
VHost.xml file). This ensures that the Administration Console (admin.swf) will be able to
connect to the virtual host. For more information, see Using the Administration Console.
Uploading server-side scripts
In developing client applications for Flash Communication Server, you may decide to use server-
side scripts to implement some of their functionality. Server-side scripts should be uploaded to
the application directory for the application that uses them, or to a “scripts” directory inside the
application’s directory.
If you create server-side scripts that use characters that are not in the classic 7-bit ASCII character
set, such as non-English characters, you must use a text editor that encodes text in UTF-8 format.
Macromedia Dreamweaver MX encodes text in this format. (A list of text editors that use the
UTF-8 format is available at http://www.thefreecountry.com/developercity/editors.shtml.)
Script files that are encoded in UTF-8 format must be transferred to the server via a binary
file transfer.
For more information about using server-side scripts, see Developing Communication Applications.
Commenti su questo manuale