web server - Borland Technical Publications

IIS web server to Borland web container connectivity
Adding new clusters
The WebClusters.properties file tells the IIOP redirector:
■
■
the name of each available cluster: (ClusterList).
the web container identification.
■
whether to provide automatic load balancing (enable_loadbalancing) for a particular
cluster.
To add a new cluster, in the WebClusters.properties file:
1 add the name of the configured cluster to the ClusterList. For example:
ClusterList=cluster1,cluster2,cluster3
2 define each cluster by adding a line in the following format specifying the cluster
name, the required webcontainer_id attribute, and any additional attributes. For
example:
.webcontainer_id =
Note Failover and smart session are always enabled, for more information go to Chapter 7,
“Clustering web components.”
Table 5.7
For example:
Cluster definition attributes
Attribute Required Definition
webcontainer_id yes the object “bind” name or corbaloc string identifying
the web container(s) implementing the cluster.
enable_loadbalancing =
true|false
no
ClusterList=cluster1,cluster2,cluster3
cluster1.webcontainer_id = tc_inst1
To enable load balancing, do not include this
attribute or include and set to true; load balancing is
enabled by default. To disable load balancing, set to
false indicating that this cluster instance should not
employ load-balancing techniques. Warning:
Ensure that when entering the enable_loadbalancing
attribute you give it a legal value (true or false).
cluster2.webcontainer_id = corbaloc::127.20.20.2:20202,:127.20.20.3:20202/
tc_inst2
cluster2.enable_loadbalancing = true
Note
Note
cluster3.webcontainer_id = tc_inst3
cluster3.enable_loadbalancing = false
In the above example, the following three clusters are defined:
1 The first, uses the osagent naming scheme and is enabled for load balancing.
2 The second cluster employs the corbaloc naming scheme, and is also enabled for
load balancing.
3 The third uses the osagent naming scheme, but has the load balancing features
disabled.
To disable use of a particular cluster, simply remove the cluster name from the
ClusterList list. However, we recommend you do not remove clusters with active http
sessions attached to the web server (attached users), because requests to these “live”
sessions will fail.
Modifications you make to the WebClusters.properties file automatically take effect on
the next request. You do not need to restart your server(s).
Chapter 5: Web server to web container connectivity 55