Server pooling extends connection pooling capabilities by allowing the naming and grouping of one or more FlashConnect connections. Server pools can connect one or more database servers to one or more Web servers. Server pools enable the distribution of an application across several systems, and allow load balancing and tighter control of resource allocation. Setting up, configuring and using server pools are optional.
The URL specifies which system should process a request and which server pool to use.
FlashConnect assigns the connection to any database server which supports that server pool using the value assigned to the w3ServerPool variable.
To start server pools in groups:
When starting FlashConnect with WWW-MANAGER, WWW-MANAGER uses the WWW-POOL command to enable each configured server pool and starts the w3Monitor. The w3Monitor uses the WWW-START command to start the WWW-IRUN phantom processes, which service the FlashConnect enabled Web pages.
To start individual lines:
When both the Web server and the FlashConnect service are properly configured and started, start the FlashConnect servers.
Log to the www account.
Use the WWW-START command to start the servers. For example:
|
WWW-START NUMSERVERS HOST PORT [POOLNAME] |
where
|
NUMSERVERS |
Number of new FlashConnect servers to start. |
|
HOST |
TCP/IP address or host name that the FlashConnect service is running on. |
|
PORT |
TCP/IP port number that the FlashConnect service is listening on. Port 1505 is the default port number. |
|
POOLNAME |
Server pool name of this set of FlashConnect servers. The name is case-sensitive. If left blank, these servers are added to the default pool. |
For example, to start ten connections in the GAME server pool on www.rainingdatagames.com (assuming that www.rainingdatagames.com has a Web server and FlashConnect service running on it), use this command:
|
WWW-START 10 WWW.RAININGDATAGAMES.COM 1505 GAME |
To stop server pools in groups:
When stopping FlashConnect with WWW-MANAGER, WWW-MANAGER stops the w3Monitor and then uses WWW-STOP to shut down each configured server pool. Occasionally, it is necessary to manually start and stop both the w3Monitor and FlashConnect connections. This process stops the w3Monitor from the configuration file.
To stop individual lines or server pools:
Use the WWW-STOP command from the www account to stop FlashConnect connections.
|
WWW-STOP [SERVER-POOL|DATABASE LINE] {(OPTIONS} |
where
|
SERVER-POOL |
Name of server pool to stop. |
|
|
DATABASE LINE |
Database line to stop that is running FlashConnect (Port). |
|
|
OPTIONS |
F |
Forces the database server to disconnect and closes sockets when WWW-STOP fails, (possibly because all FlashConnect lines are in use). Only stopped lines are impacted. |
|
Q |
Stops all lines in the server pool, stops those connected to this database. |
|
|
NOTE |
If WWW-STOP is issued with neither a PORT or a POOLNAME specified, no action is taken |
Examples
To stop all GAME servers, use the command:
|
WWW-STOP GAME |
To stop only the server running on database line number 98, use the command:
|
WWW-STOP 98 |
To stop all entries in the default server pool on this database server, use the command:
|
WWW-STOP DEFAULT |
See Also