user manual

Chapter 5: Web server to web container connectivity 61
IIS to Borland web container connectivity
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 web 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).
Adding new web applications
Important By default, your web applications are not made available through IIS. In order
to make a web application available through IIS, 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, Using the
Deployment Descriptor Editor, Web Deploy Paths section.
The \examples context is useful for verifying your IIS/IIOP installation
configuration, however, for new applications that you have deployed to the
Borland web container, you need to do the following to make them available
through the IIS 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 47).
■
In the UriMapFile.properties file, type:
<uri-mapping> = <clustername>
where <uri-mapping> is a standard URI string or a wild-card string, and
<clustername> 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".
Note 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.