
Configuring Flash Communication Server 29
Deployment: two computers with authentication via an application server
You may decide to
have users authenticated before they are allowed to connect to your Flash Communication Server.
In this scenario, users connect first to the web/application server. If they are authenticated, the
application server creates a ticket that the user then uses to connect to the Flash Communication
Server. The Flash MX communication application must be designed to check for these tickets,
typically with server-side scripts.
About configuration levels
The server is capable of hosting more than one adaptor and more than one virtual host on each
adaptor. Each virtual host is equivalent to a domain name. Each virtual host can run more than
one communication application. (The Developer Edition of the server is limited to one adaptor
and one virtual host.)
When you’re ready to customize the server for your own virtual hosts and applications, you’ll edit
the server’s XML configuration files and the directory structure that contains them. The server
uses four configuration files in XML format: Server.xml, Adaptor.xml, Vhost.xml, and
Application.xml. You configure the server by editing the contents of these files, either in a text
editor or with the Administration Console.
The following sections explain in detail how to configure the server using these files.
HTTP/S user
authentication
request
1
Server-supplied
ticket
2
3
Connect
with ticket
- Web Server
- Database
- LDAP or other
directory
Application
Server
Flash Communication
Server MX
End user
Komentáře k této Příručce