A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5

612 IBM WebSphere Host Publisher Version 3.5

19.6 Sample scenario: creating horizontal clones

In this section we consider a scenario where Host Publisher JVMs reside on

more than one machine and they are actually clones of each other. In this type of

configuration remote OSE is used to accomplish the horizontal cloning. The

HTTP or Web server resides here on separate machine while the application

servers are on separate machines.

For this sample scenario for horizontal cloning (see Figure 19-20 on page 612),

four different machines are used:

򐂰 Machine A: Web Server to hold the IBM HTTP server

򐂰 Machines B and C: Two machines for holding the Host Publisher Server

clones.

򐂰 Machine D: A machine to host the database for supporting WebSphere

Application Server (WAS).

Figure 19-20 Sample scenario for horizontal cloning

Chapter 19. Cloning and Workload Management (WLM) 613

Step 1: Installation

As shown in Figure 19-20, the following software will be required for this sample

scenario:

򐂰 Machine A

– In this machine DB2 UDB Version 7.1 will be installed, this will be needed

for WebSphere Application Server use.

– WebSphere Application Server (WAS) with fix pack 3 will also be installed.

Although only the HTTP server will be used in this machine, WAS is

required to install the WAS plug-in that will forward the HTTP request to

application servers on other machines using the remote OSE protocol.

Note: Do not start the IBM WS AdminServer service in this machine.

򐂰 Machines B and C

– Install DB2 UDB Version 7.1

– Install WebSphere Application Server version 3.5 with fix pack 3. Make

sure the IBM WS AdminServer service is not running in machines B and C

at this time.

– Install Host Publisher Server Version 3.5 in machines B and C. Host

Publisher will be installed but the JVM for Host Publisher will not be

created in WAS at this time because the IBM WS AdminServer service

has not been started yet.

Note: Installing Host Publisher Server without WAS Admin Server service

running could take an extra amount of time (for example the process waits

5 to 10 minutes for the completion of this piece before timing out). As an

alternative you may consider installing Host Publisher Server in both

machines with WAS up and running and then delete the Host Publisher

Server from one node. This would also remove Step 5 below.

򐂰 Machine D

– Install DB2 UDB Version 7.1 in machine D. This database will be used

later on to hold the WAS database and the session database for

WebSphere Application Servers in machines B and C.

– Create two empty databases. For example, one with name of WASDB and

another one with name SESSDB.

Step 2: Cataloging the node and remote database

The catalog tcpip node and catalog db commands are used in the client

machines to add a remote database. In this scenario, B and C are the client

machines running WAS and machine D has the remote database.