MACROMEDIA COLDFUSION MX-CLUSTERCATS Manual de usuario Pagina 105

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 156
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 104
Load-balancing devices 95
9 Edit the cluster properties as described in the following table:
10 Click OK.
When configured, ClusterCATS automatically sets the state of each cluster member to
Passive and provides the load-balancing and high availability data it acquires to
LocalDirector. LocalDirector actively manages HTTP traffic across the cluster.
Using third-party load-balancing devices
Third-party load-balancing devices actively distribute load to the web servers based on
packet flow while ClusterCATS monitors JRun and ColdFusion load and availability. If
ClusterCATS detects that the server is becoming overloaded, it supersedes the
load-balancing device and redirects traffic accordingly.
This section describes how to configure a third-party load-balancing device with
ClusterCATS in the following sections:
“Using third-party load-balancing devices in Windows” on page 96
“Using third-party load-balancing devices in UNIX” on page 97
Field Description
Website Alias Enter the name of the virtual server (www.yourcompany.com)
you created in step 3.
LocalDirector IP
Address
Enter the IP address of Cisco LocalDirector.
DFP Agent Listen
Port
Enter the port number on which the cluster's DFP agent should
listen for incoming LocalDirector connection requests. This
should be the same port specified in the LocalDirector
dynamic-feedback as described in step 5.
Update Frequency
(sec)
Enter the frequency with which you want ClusterCATS to update
the LocalDirector with availability data.
This is typically between 5 and 30. You can enter up to 120.
As you add web servers to the cluster, set a larger value. This
minimizes the overhead of traffic to LocalDirector.
HTTP Port Enter the port number on which each cluster member listens for
unsecured HTTP requests. Enter 0 if not applicable.
HTTPS Port Enter the port number on which each cluster member listens for
secured HTTP requests. Enter 0 if not applicable.
Bind ID Enter the same Bind ID specified for the explicit (real) servers on
the LocalDirector in step 4. For ClusterCATS/LocalDirector
integration to work as intended, the server name, port number,
and bind ID combination must be the same on this ClusterCATS
Load Balance tab as on the LocalDirector box.
Vista de pagina 104
1 2 ... 100 101 102 103 104 105 106 107 108 109 110 ... 155 156

Comentarios a estos manuales

Sin comentarios