Deploying Multiple PIAs to WebSphere ND 5

greasyservantInternet and Web Development

Jul 30, 2012 (5 years and 15 days ago)

342 views

Deploying Multiple PeopleSoft Internet Architectures
to WebSphere 5.1



Table of Contents


Overview

................................
................................
................................
.............................

3

Why and When to Use Virtual Hosting

................................
................................
..........

3

Virtual Host Resources

................................
................................
................................
...

4

IBM HTTP Server Virtual Hosts

................................
................................
................

4

IIS Virtual
Hosts

................................
................................
................................
.........

4

SunOne Web Server Virtual Hosts

................................
................................
.............

4

Multiple PIAs with WebSphere Base Instances

................................
................................
.

5

Configuration Steps

................................
................................
................................
........

5

Adding HTTP Server

................................
................................
................................
......

6

Multiple PIAs in a Single WebSphere Base Instance

................................
.........................

8

Configuration Steps

................................
................................
................................
........

8

Multiple PIAs with WebSphere ND

................................
................................
.................

10

Configuration Steps

................................
................................
................................
......

10

Adding HTTP Server

................................
................................
................................
....

10


Overview


This document outlines 5 different scenarios with WebSphere and the PeopleSoft Internet
Architecture. The first and second scenarios show

how to deploy multiple PIAs to
multiple WebSphere Base servers (one with no HTTP server and the other using an
HTTP server). The third scenario shows how to deploy multiple PIAs to a single
WebSphere Base server. The fourth and fifth scenarios explain h
ow to deploy multiple
PIAs to multiple WebSphere ND servers (one with no HTTP server and the other using
an HTTP server).


The PeopleSoft Internet Architecture (PIA) is deployed with a context root of ‘/’. This
cannot be changed. Deploying multiple PIAs
to WebSphere can cause conflicts since the
context roots are the same. The context root helps create a unique URL for the
application. Having two or more apps with the same URL makes some of the apps
inaccessible.


WebSphere allows the use of virtual h
osts to create unique URLs. This is done with
either a unique hostname or port. The below section is from the WebSphere InfoCenter
and explains when virtual hosting should be used:



Why and When to Use Virtual Hosting

Virtual hosts allow the administra
tor to isolate, and independently manage, multiple sets
of resources on the same physical machine.


Suppose an Internet Service Provider (ISP) has two customers whose Internet sites it
would like to host on the same machine. The ISP would like to keep the
two sites isolated
from one another, despite their sharing a machine. The ISP could associate the resources
of the first company with VirtualHost1 and the resources of the second company with
VirtualHost2.


Now suppose both company's sites offer the same s
ervlet. Each site has its own instances
of the servlet, which are unaware of the other site's instances. If the company whose site
is organized on VirtualHost2 is past due in paying its account with the ISP, the ISP can
refuse all servlet requests that are

routed to VirtualHost2. Even though the same servlet is
available on VirtualHost1, the requests directed at VirtualHost2 will not be routed there.

The servlets on one virtual host do not share their context with the servlets on the other
virtual host. Req
uests for the servlet on VirtualHost1 can continue as usual, even though
VirtualHost2 is refusing to fill requests for the same servlet.


Virtual Host Resources

IBM HTTP Server Virtual Hosts

http://www
-
306.ibm.com/software/webservers/httpservers/doc/v1328/htdocs/en_US/manual/mod/cor
e.html#namevirtualhost



IIS Virtual Hosts

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddo
cs/en
-
us/Default
.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en
-
us/wsa_hostmultwebsite.asp


SunOne Web Server Virtual Hosts

http://docs.sun.com/db/coll/S1_ipwebsr
vree60_en?q=Sun+ONE+Web+Server


Multiple PIAs with WebSphere Base Instances


Configuration Steps

1.

Install WebSphere Base 5.1 using the instructions provided by PeopleSoft.

2.

Start server1 using the startServer.[bat|sh] command.

Windows

<WAS_HOME>/bin/startS
erver.bat server1

Unix

<WAS_HOME>/bin/startServer.sh server1

3.

Use a browser to access the WebSphere Admin Console (ex.
http://localhost:9090/admin
)

4.

Expand
Servers
-
> Application Servers
.

5.

Click
New
.

6.

Enter a value
in the Server Name textfield (ex. server2).

7.

Click
Next
.

8.

Click
Finish
.

9.

Click
Save
.

10.

Click the
Save

button.

11.

Expand
Servers
-
> Application Servers

to verify that server2 was created.

12.

Start server2 using the startServer.[bat|sh] command.

Windows

<WAS_HOME>/bi
n/startServer.bat server2

Unix

<WAS_HOME>/bin/startServer.sh server2

13.

Install the first PIA into server1. During the installation:

a.

Specify a unique PS_HOME.

b.

Select server1 as the Server name.

c.

Specify a unique name as the application name (ex. peoplesoft1
).

d.

Specify server1’s internal HTTP transports for HTTP Port and HTTPS
Port.

14.

Install the second PIA into server2. During the installation:

a.

Specify a unique PS_HOME.

b.

Select server2 as the Server name.

c.

Specify a unique name as the application name (ex. peo
plesoft2).

d.

Specify server2’s internal HTTP transports for HTTP Port and HTTPS
Port.

15.

Stop and start both WebSphere instances (server1 and server2).

16.

Access the PIAs on the internal http tranports.

PIA1

http://<server_name>:9080/ps/signon.html

PIA2

http://<server_name>:9081/ps/signon.html




Adding HTTP Server

The HTTP Server uses the plugin
-
cfg.xml file to route requests to WebSphere. Since th
e
PIA has a concrete


1.

Edit the default_host Virtual Host.

a.

Remove any entries for *.*.

b.

For port 80 entries, specify a hostname (ex. crm.peoplesoft.com).

2.

Create a new Virtual Host.

a.

Expand
Environment
-
> Virtual Hosts
.

b.

Click
New.

c.

Enter a name for the V
irtual Host (ex. hr_host).

d.

Click
OK
.

3.

Click on the virtual host just created.

4.

Click
Host Aliases.

a.

Click
New
.

b.

Enter a hostname (ex. hr.peoplesoft.com) and the port = 80.

c.

Click
OK
.

5.

Expand
Applications
-
> Enterprise Applications
.

a.

A PIA using the default host d
oes not require this change. Any PIA that
uses another virtual host must make this change.

b.

Select a PIA that will not use the default_host virtual host (ex.
peoplesoft2).

c.

Uncheck the checkbox for
Use Metadata From Binaries
.

d.

Click
OK
.

e.

Save the changes.

6.

Retu
rn to the second PIA by expanding
Applications
-
> Enterprise Aplications

and selecting the second PIA.

a.

Click
Map Virtual Hosts to Web Modules
.

b.

Select all the web modules.

c.

For each web module, select the new virtual host from the drop down
menu.

d.

Click
OK
.

7.

S
ave the changes.

8.

Regenerate the plugin.

a.

Expand
Environment
-
> Update Web Server Plugin
.

b.

Click
OK

to regenerate the plugin.

9.

Restart the WebSphere servers.

10.

Edit the HTTP server’s configuration to allow name based virtual hosting. The
steps for the IBM HTTP
Server are shown below. See the Virtual Host Resources
section for information on IIS and SunOne.

a.

Open httpd.conf in a text editor.

b.

Find the section with the <VirtualHost> tag.

c.

Each servername that will be used to access the PIAs needs to be added to
http
d.conf. Add these lines with the correct ServerName values:

NameVirtualHost *

<VirtualHost *>

ServerName crm.peoplesoft.com

</VirtualHost>

<VirtualHost *>

ServerName hr.peoplesoft.com

</VirtualHost>

d.

Save the changes.

e.

Restart IHS for the changes to take ef
fect.

11.

Add Aliases for these servernames to DNS servers for the site.

Multiple PIAs in a Single WebSphere Base Instance


Configuration Steps

1.

Install WebSphere Base 5.1 using the instructions provided by PeopleSoft.

2.

Start server1 using the startServer.[bat|
sh] command.

Windows

<WAS_HOME>/bin/startServer.bat server1

Unix

<WAS_HOME>/bin/startServer.sh server1

3.

Install the first PIA. During the installation:

a.

Specify a unique PS_HOME.

b.

Select server1 as the Server name.

c.

Specify a unique name as the application
name (ex. peoplesof1).

d.

Specify server1’s internal HTTP transports for HTTP Port and HTTPS Port.

4.

Install the second PIA. During the installation:

a.

Specify a unique PS_HOME.

b.

Select server1 as the Server name.

c.

Specify a unique name as the application name (
ex. peoplesoft2).

d.

Specify server1’s internal HTTP transports for HTTP Port and HTTPS Port.

5.

Edit the default_host Virtual Host.

a.

Expand
Environment
-
> Virtual Hosts.

b.

Click
default_host
.

c.

Click
Host Aliases
.

d.

Delete any entries for *.*.

e.

For the internal tra
nsports (ex. 9080), specify a hostname (ex.
crm.peoplesoft.com).

f.

Save the Changes.

6.

Create a new Virtual Host.

a.

Expand
Environment
-
> Virtual Hosts
.

b.

Click
New.

c.

Enter a name for the Virtual Host (ex. hr_host).

d.

Click
OK
.

e.

Click on the virtual host just create
d.

f.

Click
Host Aliases.

g.

Click
New
.

h.

Enter a hostname (ex. hr.peoplesoft.com) and the internal transport (ex. 9080).

i.

Click
OK
.

j.

Save the changes.

7.

Expand
Applications
-
> Enterprise Applications
.

a.

A PIA using the default host does not require this change. Any PIA

that uses
another virtual host must make this change.

b.

Select a PIA that will not use the default_host virtual host (ex. peoplesoft2).

c.

Uncheck the checkbox for
Use Metadata From Binaries
.

d.

Click
OK
.

e.

Save the changes.

8.

Return to the second PIA (ex. peoplesoft
2) by expanding
Applications
-
> Enterprise
Aplications.

a.

Select the second PIA.

b.

Click
Map Virtual Hosts to Web Modules
.

c.

Select all the web modules.

d.

For each web module, select the new virtual host (ex. hr_host) from the drop
down menu.

e.

Click
OK
.

f.

Save the
changes.

9.

Stop and start WebSphere server1 instance.

10.

Access the PIAs on the internal http tranports. For example:

PIA1

http://<server_name>:9080/ps/signon.html

where <server_name> is the hostname
sp
ecified in the default_host (ex. crm.peoplesoft.com).

PIA2

http://<server_name>:9080/ps/signon.html

where <server_name> is the hostname
specified in the hr_host (ex. hr.peoplesoft.com).

Multiple PI
As with WebSphere ND


Configuration Steps

1.

Using PeopleSoft’s Clustering and High Availability Redpaper, create two PIA
ear files. These ear files should have unique PS_HOME and application name
values. The ear files can be deployed to WebSphere clusters
(as shown in
redpaper) or to individual WebSphere application servers (as shown in the
InfoCenter
http://publib.bou
lder.ibm.com/infocenter/ws51help/index.jsp?topic=/com.ibm.we
bsphere.nd.doc/info/ae/ae/trun_app_instwiz.html
). Once the PIAs are deployed,
the duplicate context roots need to be changed using virtual hosts shown below.

2.

Edit the default_host Virtual Host.


a.

Expand
Environment
-
> Virtual Hosts
.

b.

Click default_host.

c.

Click
Host Aliases
.

d.

Delete any entries for *.*.

e.

Create an entry with a hostname (ex. crm.peoplesoft.com) and the server’s
HTTP transport (ex. 9080).

3.

Create a new Virtual Host for the
second

PIA.


a.

Expand
Environment
-
> Virtual Hosts
.

b.

Click
New.

c.

Enter a name for the Virtual Host (ex. hr_host).

d.

Click
OK
.

4.

Click on the virtual host just created.

a.

Click
Host Aliases.

b.

Click
New
.

c.

Enter a hostname (ex. hr.peoplesoft.com) and the server’s HTTP transport
(ex
. 9081).

d.

Click
OK
.

5.

Expand
Applications
-
> Enterprise Applications
.

a.

A PIA using the default host does not require this change. Any PIA that
uses another virtual host must make this change.

b.

Click
Map Virtual Hosts for Web Modules
.

c.

Select all the web modules.

d.

For each web module, select the new virtual host from the drop down
menu.

e.

Click
OK
.

f.

Save the changes.

6.

Restart the Application Servers/Clusters for the changes to take effect.

7.

Access the PIAs on their internal HTTP transports (ex. 9080 and 9081).


Adding H
TTP Server

1.

After completing the steps in the previous section, update the default_host with
port 80.

a.

Expand
Environment
-
> Virtual Hosts
.

b.

Click default_host.

c.

Click
Host Aliases
.

d.

Create an entry with a hostname (ex. crm.peoplesoft.com) and the HTTP
server’
s port (default is 80).

2.

Repeat the above step for the second virtual host (ex. hr_host).

3.

Regenerate the plugin.

a.

Expand
Environment
-
> Update Web Server Plugin
.

b.

Click
OK

to regenerate the plugin.

4.

Restart the Application Servers.

5.

Edit the HTTP server’s confi
guration to allow name based virtual hosting. The
steps for the IBM HTTP Server are shown below. See the Virtual Host Resources
section for information on IIS and SunOne.

a.

Open httpd.conf in a text editor.

b.

Find the section with the <VirtualHost> tag.

c.

Each

servername that will be used to access the PIAs needs to be added to
httpd.conf. Add these lines with the correct ServerName values:

NameVirtualHost *

<VirtualHost *>

ServerName crm.peoplesoft.com

</VirtualHost>

<VirtualHost *>

ServerName hr.peoplesoft.c
om

</VirtualHost>

d.

Save the changes.

e.

Restart IHS for the changes to take effect.

6.

Add Aliases for these servernames to DNS servers for the site.