Configuring Semi OSE-Remote in a Multi-Node Environment

Technote (FAQ)
Problem
How to configure semi OSE-remote to work in a multi-node environment so that all requests always go to one clone.
Solution
OSE-Remote exists when you have WebSphere and the Web server(s) residing on separate physical machines.

Semi OSE-Remote is the configuration that exists when you have both WebSphere and a Web server that reside on the same physical machine.

This document explains how to setup semi OSE-Remote in a multi-node environment where there is 2 or more machines, which have both WebSphere and a WebServer on each machine.

When using IBM HTTP Server:
1. Follow the usual steps for configuring remote OSE.
a. Create your final configuration for application server and clones.
b. Modify the host alias entry on the virtual host, as required.
c. Change the servlet engine transport to inet socket on Windows and AIX OS.
d. Start your application server Model
e. Stop the application server Model

2. Modify the queues.properties file so that both machines are remote.

Original queues.properties file:
#IBM WebSphere Plugin Communication Queues
#Tue Aug 20 14:00:54 EDT 2002
ose.srvgrp=ibmoselink,ibmoselink1

ose.srvgrp.ibmoselink.clonescount=1
ose.srvgrp.ibmoselink.type=FASTLINK
ose.srvgrp.ibmoselink.clone1.type=local
ose.srvgrp.ibmoselink.clone1.port=8993

ose.srvgrp.ibmoselink1.clonescount=1
ose.srvgrp.ibmoselink1.type=FASTLINK
ose.srvgrp.ibmoselink1.clone1.type=local
ose.srvgrp.ibmoselink1.clone1.port=8994


Edited queues.properties file:
#Tue Aug 20 14:00:54 EDT 2002
ose.srvgrp=ibmoselink,ibmoselink1

ose.srvgrp.ibmoselink.clonescount=1
ose.srvgrp.ibmoselink.type=FASTLINK
ose.srvgrp.ibmoselink.clone1.port=8993
ose.srvgrp.ibmoselink.clone1.type=local

ose.srvgrp.ibmoselink1.clonescount=2
ose.srvgrp.ibmoselink1.type=FASTLINK
ose.srvgrp.ibmoselink1.clone1.type=remote
ose.srvgrp.ibmoselink1.clone1.host=jimmy
ose.srvgrp.ibmoselink1.clone1.port=8994
ose.srvgrp.ibmoselink1.clone2.type=remote
ose.srvgrp.ibmoselink1.clone2.host=jimmy2
ose.srvgrp.ibmoselink1.clone2.port=8994

NOTE: What you want to ensure is to add the <servergroup>.clonescount=2 to reflect the second clone that is located on the remote node (jimmy2). Also add the <servergroup>.clone2.type, <servergroup>.clone2.host and <servergroup>.clone2.port.

3. Place the modified file and a copy of the rules.properties and vhost.properties files into a different directory. For example, create an http subdirectory below the WAS_root/temp and place the files into the new sub-directory, the WAS_root/temp/http directory.

4. Copy the bootstrap.properties file in WAS_root/properties. The key entry looks like ose.tmp.dir=d:/WEBSPH~1/temp/. This property specifies the directory where the administrative server places the three properties files noted above, and where the HTTP server plug-in looks for the properties files. In the copy, change the entry so that the HTTP Server can find the properties files.

Like: d:/WEBSH~1/APPSER~1/temp/http (this is the location of the modified queues.properties and vhost.properties and rules.properties).

NOTE: Use a copy of the bootstrap.properties file because you want the administrative server to continue to update the properties files in their original location, and leave the modified files unchanged. To simplify administration, create an http sub directory under WAS_root/properties and place the modified bootstrap.properties file. The directory and the file will look like: WAS_root/properties/http/bootstrap.proerties

5. Modify the plug-in entry for the bootstrap.properties file in the IHS and Apache config file. The entry is:

NcfAppServerConfig Bootfile
D:\WEBSPH~1\APPSER~1\properties\boostrap.properties

Because you want the plugin to use the modified bootstrap.properties in the WAS_root/properties/http directory, change the entry to point to the location of the modified bootstrap.properties.

ADDITIONAL:
See the correct entries for Netscape iPlanet and IIS in the Release Notes of WebSphere Application Server 3.5.5 under the heading: Using a model, clone, and a remote node name in the main server default host (defects 101332, 101336 and 103823).
    Historical Number
    PMR 69292 b344 000
    Product Alias/Synonym
    WebSphere AppServer 3.5.x











    Document Information

    Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Plug-in
    Operating system(s): Multi-Platform
    Software version: 3.5
    Software edition: Advanced
    Reference #: 1064153
    IBM Group: Software Group
    Modified date: 2003-06-20