web server - Borland Technical Publications

Configuring your Apache web server to invoke a CORBA server
Note
“cluster” is used to represent a CORBA object instance(s) that is known to the system
by a single name or URI. The IIOP connector is able to load-balance across multiple
instances, hence the term “cluster” is used.
The two configuration files are:
Table 8.1
IIOP configuration file
Apache IIOP connection configuration files
Adding new CORBA servers (clusters)
Mapping URIs to defined clusters
Description
Specifies the cluster(s) and the corresponding
CORBA server(s) for each cluster.
Maps URI references to the clusters defined in the
WebClusters.properties file.
Modifying either of these configuration files can be done so without starting up or
shutting down the Apache web server(s) or CORBA server(s) because the file is
automatically loaded by the IIOP connector.
Adding new CORBA servers (clusters)
CORBA servers are known as “clusters” to the IIOP connector. To configure your
CORBA server for use with the IIOP connector, you need to define and add a “cluster”
to the WebClusters.properties file.
The WebClusters.properties file tells the IIOP connector:
■
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:
a add the name of the configured cluster to the ClusterList. For example:
ClusterList=cluster1,cluster2,cluster3
b define each cluster by adding a line in the following format specifying the cluster
name, the required webcontainer_id attribute, and any additional attributes (see
the following cluster definition attribute table). For example:
.webcontainer_id =
Note Failover and smart session are always enabled, for more information go to Chapter 7,
“Clustering web components.”
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 loadbalancing
techniques. Warning: Ensure that when
entering the enable_loadbalancing attribute you give it a
legal value (true or false).
70 BES Developer’s Guide