user manual

82 BES Developer’s Guide
Configuring your Apache web server to invoke a CORBA server
Note Failover and smart session are always enabled, for more information go to
Chapter 7, “Clustering web components”..
For example:
ClusterList=cluster1,cluster2,cluster3
cluster1.webcontainer_id = tc_inst1
cluster2.webcontainer_id =
corbaloc::127.20.20.2:20202,:127.20.20.3:20202/tc_inst2
cluster2.enable_loadbalancing = true
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.
Note 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 CORBA server (attached users), because
requests to these "live" sessions will fail.
Note Modifications you make to the WebClusters.properties file automatically take
effect on the next request. You do not need to restart your server(s).
Mapping URIs to defined clusters
Once the cluster entry is defined, all that remains is to identify which HTTP
requests received by the web server need to be forwarded to your CORBA
Table 8.2 Cluster definition attributes
Attribute Required Definition
webcontainer_id yes the object "bind" name or corbaloc string
identifying the web container implementing the
cluster.
enable_loadbalancing no Load balancing is enabled by default; to enable
load balancing, do not include this attribute or
include and set to true. 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).