web server - Borland Technical Publications

Chapter
7
Chapter7Clustering web components
This section discusses the clustering of multiple web components which includes
Apache web servers and the Tomcat-based Borland web containers. In a typical
deployment scenario, you can use multiple Borland Partitions to work together in
providing a scalable n-tier solution.
Each Borland Partition can have the same or different services. Depending on your
clustering scheme, these services can be turned off or on. In any case, leveraging
these resources together or clustering, makes deployment of your web application
more efficient. Clustering of the web components involves session management, load
balancing and fault tolerance (failover).
Stateless and stateful connection services
Important
Interaction between the client and server involves two types of services: stateless and
stateful. A stateless service does not maintain a state between the client and the
server. There is no “conversation” between the server and the client while processing a
client request. In a stateful service, the client and server maintains a dialog of
information.
For information about the location of the Borland web container configuration files, go
to Chapter 4, “Web components.”
For documentation updates, go to www.borland.com/techpubs/bes.
The Borland IIOP connector
The IIOP connector is software that is designed to allow an http web server to redirect
requests to the Borland web container. The Borland Enterprise Server includes the
IIOP connector for the Apache 2.0 and Microsoft Internet Information Server (IIS)
versions 5.0, 5.1 and 6.0 web servers. The job of handling the redirection of http
requests is split between two components:
■
■
a native library running on the web server.
a jar file running of the web container.
Chapter 7: Clustering web components 61