InfoCenter Home >
7: Multimachine management >
7.1: Using WebSphere Application Server in a multimachine environment >
7.1.3: Multimachine topologies >
7.1.3.6: HTTP server separation sample topologies >
7.1.3.6.2: Semi-remote OSE sample topology
7.1.3.6.2: Semi-remote OSE sample topology
Semi-remote OSE is a variation on the remote OSE topology. The difference between the
two topologies is whether an instance of the application server runs on the machine
that hosts the Web server. A semi-remote OSE configuration has an instance of an
application server running on the same machine as the Web server; a remote OSE
configuration does not.

Like remote OSE, semi-remote OSE can be used to direct client requests to additional
application server clones on other machines. In this example, it redirects client requests
to both the application server instance running on Machine A and the clones running on
Machine B.
Semi-remote OSE requires more steps than remote OSE. Using a semi-remote OSE
configuration is recommended only in situations where hardware limitations prevent you
from hosting the Web server on a dedicated machine.
In many production environments, one set of servers is configured to run HTTP servers
and another set of servers is configured to run application servers. If a customer either
needs to add capacity in a production environment or cannot fully replicate the production
configuration in the production test environment, semi-remote OSE provides a means of
load distribution between a machine hosting both the HTTP and application server and
machines hosting just the application server.
A semi-remote OSE configuration can also be used as a WebSphere proof of concept for
demonstrating OSE load distribution in situations where there are a limited number of
machines.
To create a semi-remote OSE configuration, do the following:
- Create a remote OSE configuration, following the steps in article 7.1.3.6.1, Remote OSE sample topology.
- Copy the product_installation_root/temp/queues.properties
file from the machine where the application server runs (Machine B) to the product_installation_root/temp directory
on the machine where the Web server runs (Machine A).
- Modify the the queues.properties file to identify both machines as
remote machines. The following is example of a modified queues.proerties file; the changed
lines are highlighted in bold:
# IBM WebSphere Plugin Communication Queues
#Friday March 23 18:05:13 PDF 2001
ose.srvgrp.ibmoselink.clonescount=2
ose.srvgrp=ibmoselink
ose.srvgrp.ibmoselink.type=FASTLINK
ose.srvgrp.ibmoselink.clone1.port=8110
ose.srvgrp.ibmoselink.clone1.type=remote
ose.srvgrp.ibmoselink.clone1.host=was-nt1
#
ose.srvgrp.ibmoselink.clone2.port=8110
ose.srvgrp.ibmoselink.clone2.type=remote
ose.srvgrp.ibmoselink.clone2.host=was-nt2
- Copy the modified queues.properties file, the rules.properties
file, and the vhosts.properties file to another directory, for example,
product_installation_root/temp/http. Copying these files to a different directory prevents the administrative server
from overwriting them.
- Create a new directory under the product_installation_root/properties
directory, for example, product_installation_root/properties/http.
- Copy the product_installation_root/properties/bootstrap.properties
file to the new directory you just created.
- In the copied bootstrap.properties file, change the value of the
ose.tmp.dir parameter to the product_installation_root/temp/http
directory. (That is, the directory where you placed the modified queues.properties
file, the rules.properties file, and the vhosts.properties
file.)
ose.tmp.dir=product_installation_root/temp/http
This parameter tells the HTTP server plug-in where to find the modified properties
files.
- In the HTTP server configuration file product_installation_root/properties/httpd.conf,
change the plug-in entry for the bootstrap.properties file to refer to
the modified of the file:
NcfAppServerConfig BootfFile
product_installation_root/properties/http/bootstrap.properties
- Restart the administrative servers, application servers, and HTTP server.
|
|