web server - Borland Technical Publications

Large data transfer
Important
Note
Note
Adding new web applications
By default, your web application is not made available through Apache. In order to
make it available through Apache, you must add some information to the web
application descriptor. For step-by-step instructions on how to do so, go to the
Management Console User's Guide.
For new applications that you have deployed to the Borland web container, you need to
do the following to make them available through the Apache web server. Use the
UriMapFile.properties file to map HTTP URI strings to web cluster names configured in
the WebClusters.properties file (see “Adding new clusters” on page 46.)
■
In the UriMapFile.properties file, type:
=
where is a standard URI string or a wild-card string, and
is the cluster name as it appears in the ClusterList entry in the
WebClusters.properties file.
For example:
/examples = cluster1
/examples/* = cluster1
/petstore/index.jsp = cluster2
/petstore/servlet/* = cluster2
In this example:
■
■
Any URI that starts with /examples will be forwarded to a web container running in
the “cluster1” web cluster.
URIs matching either /petstore/index.jsp or starting with /petstore/servlet will be
routed to “cluster2”.
With the URI mappings, the wild-card “*” is only valid in the last term of the URI and
may represent the follow cases:
■
the whole term (and all inferior references) as in /examples/*.
■
the filename part of a file specification as in /examples/*.jsp.
Modifications you make to the UriMapFile.properties file automatically take effect on
the next request. You do not need to restart your server(s).
If the WebCluster.properties or UriMapFile.properties is altered, then it is automatically
loaded by the IIOP connector. This means that the adding and removing of web
applications and the altering of cluster configurations may be done so without starting
up or shutting down the Apache web server(s) or Borland web container(s).
Large data transfer
This section details the BES options available to you for handling large data transfers
between a client and the Borland web container with Apache 2.0 in between. The data
to be transferred may be either:
■
■
static content obtained from a file, or
dynamically generated content
Typically, the content length is known in advance for static content, but is not known for
dynamic content.
Chapter 5: Web server to web container connectivity 47