weblogic install options

WebLogic 10.3.x Install Options

Last Updated: 12/26/12

http://www.oracle.com/us/

Oracle Page 2

WebLogic 10.3.x Install Options

Contents

Introduction .................................................................................................................................. 3

Intended Audience ...................................................................................................................... 3

Purpose of this Document ........................................................................................................... 3

What this Document Covers ....................................................................................................... 3

Types of WebLogic Domains (Single vs. Multi vs. DMS) ......................................................... 4

Overview ..................................................................................................................................... 4

Domain Types ............................................................................................................................. 5

Single-Server WebLogic Domain ........................................................................................... 5

Multi-Server WebLogic Domain............................................................................................. 6

Distributed Managed Server (DMS) Domain ......................................................................... 8

Advantages/Disadvantages to Each Domain Type ..................................................................... 9

What Domain Type Option Works Best for My Environment? ............................................... 10

How to Install Single-Server, Multi-Server or DMS ................................................................ 11

Clustered vs. Independent PIAs .............................................................................................. 12

Overview ................................................................................................................................... 12

PIA Types ................................................................................................................................. 13

Independent PIAs ................................................................................................................. 13

Clustered PIAs ..................................................................................................................... 14

Advantages/Disadvantages to Clustered vs Independent PIAs .............................................. 15

What PIA Type Works Best for My Environment? ................................................................. 16

How to Install Independent PIAs or Clustered PIAs ............................................................. 17

Other Resources ......................................................................................................................... 18

Oracle Page 3

Introduction

Intended Audience This document is intended for anyone who is installing a WebLogic 10.3.x domain in their PeopleSoft

environment and is looking for additional details (outside of information provided in PeopleTools 8.5x

Installation guide) on different types of WebLogic install options

Purpose of this Document The purpose of this document is to supplement the PeopleTools 8.5x installation guide by providing detail on

some of the WebLogic installation options where our customers sometimes require additional guidance, when

deciding what works best in their PeopleSoft environment.

What this Document Covers This document provides details on the different types of options available when installing and configuring your

WebLogic domain. Specifically:

1) Type of WebLogic Domain (Single-Server vs. Multi-Server vs. Distributed Managed Server) 2) Clustered PIAs vs. Independent PIA's

For each of the above installation options, this document covers:

a) A description of the option

b) Advantages/disadvantages

c) Recommendations on what option may work best for you

d) Installation information

Oracle Page 4

Types of WebLogic Domains (Single vs. Multi vs. DMS)

Overview

When installing a Weblogic domain, you have the option of choosing one of the following three domain types:

1) Single-Server Domain 2) Multi-Server Domain 3) Distributed Managed Server (DMS)

Below is a brief description of each domain type:

Single Server Domain: Domain consists of one java process that listens on one port and processes all incoming requests

Multi Server Domain: Domain consists of multiple java processes, each listening on different ports. Each java process (ie server)

can be configured to handle different types of tasks.

Distributed Managed Server: This is an extension of the Multi-Server domain whereby the domain is spread out over multiple physical

machines

The following sections explain each domain type in detail, followed by the advantages and disadvantages to

installing each of these domain types

Oracle Page 5

Domain Types

Single-Server WebLogic Domain For a single-server domain, the WebLogic domain uses just one java process, and the entire PeopleSoft

application is deployed to it. The domain listens on just one http port (as well as an https port) and all the

requests (PIA requests and WebLogicAdmin requests) go to this single java process. This is the easiest and

most basic type of domain to install.

In the past, weve not recommended single-server domains in production environments, since a single java

process was being shared for both PIA and WebLogicAdmin processing. However, with the introduction of 64-

bit WebLogic (starting with PeopleTools 8.51), the java process no longer has the restrictions on heap size. So

that makes the Single-Server domain a more viable solution, even in production environments. (More about this

in the advantages/disadvantages section)

EXAMPLE 1: Below is a diagram of a single-server WebLogic domain (uses one java process).

EXAMPLE 2: Note that you also have the option of installing multiple single-server domains on one machine

(or multiple single-server domains on multiple machines) But you need to make certain each domain is listening

on a different http and https port# (if multiple domains on one machine). If you have more than one PIA, then a

load balancer or reverse proxy server is needed in order to distribute the requests to the PIAs. Below is a

diagram showing two Single Server Weblogic domains on one machine (using a total of two java processes)

Web Server Machine

Single Server Domain peoplesoft

PIAListening on:

http port# 80 and https port# 443

Web Server Machine

Single Server Domain peoplesoft1

PIAListening on:


PIAListening on:


Single Server Domain peoplesoft2

Load Balancer (or RPS)

Listening on port

80

Oracle Page 6

Multi-Server WebLogic Domain For a multi-server domain, the WebLogic domain contains multiple servers (each with its own java process) and

the PeopleSoft application can be split among these servers. When you install a Multi-Server domain, it is set

up with seven server definitions:

1. WebLogicAdmin: Administrative server for WebLogic 2. PIA: This server houses an independent PIA used for portal, integration gateways, etc 3. PIA1: This server houses a clustered PIA used for same functions as PIA (above) 4. PIA2: This server houses a clustered PIA used for same functions as PIA and PIA1 5. PSOL: This server was previously used for PeopleSoft Online Library but is now obsolete. Refer to

PeopleTools Installation guide for more info about PeopleBooks install

6. PSEMHUB: This server is for the PeopleSoft Environment Management Framework Application 7. RPS: This server can be used as a Reverse Proxy Server

Even though the WebLogic domain is configured with all of the above server definitions, you dont need to use

them all. You choose to start only the servers you wish to use (most customers use only WebLogicAdmin&PIA)

EXAMPLE 1: In the example below, we have a multi-server domain where the WeblogicAdmin Server and

PIA are being used. So in this example, we have two java processes. The PeopleSoft requests go to PIA and

any administrative requests go to WebLogicAdmin. Note that WebLogicAdmin and PIA processes

communicate with one another.

EXAMPLE 2: Note that you can set up additional server definitions, outside of the seven pre-configured

definitions. For example, if you want two independent PIAs, you could clone the PIA and call it PIA-TWO as

in this example below (Independent PIAs and Clustered PIAs are discussed further in Section Clustered vs

Independent PIAs). This set-up would require a load balancer or proxy server in order to distribute the

incoming http requests to PIA and PIA-TWO

Web Server Machine

Multi Server Domain peoplesoft

WebLogicAdminListening on http port# 9999

PIAListening on:


Oracle Page 7

Web Server Machine



PIAListening on:


PIA-TWOListening on:


RPS (or Load Balancer)

Listening

on port 80

Oracle Page 8

Distributed Managed Server (DMS) Domain

This option is an extension of the Multi Server Domain selection and allows you to spread a multi-server

domain over multiple physical machines. Distributed Managed Servers are the most complex domain. Very

few PeopleSoft customers use this set-up, unless they choose to configure stateful failover and have the PIAs

installed on multiple-machines (refer to the Cluster vs. Independent PIAs section for more information about

stateful failover).

EXAMPLE 1: In this example, the WebLogic domain is spread out over two machines. The PIAs are

clustered. (more details about this in section Cluster vs. Independent PIAs). One machine contains

theWebLogicAdmin server and a PIA. The other machine contains a second PIA. A load balancer or proxy

server is needed to distribute the incoming http requests to PIA1 and PIA2.

EXAMPLE 2: You can also set up a DMS with independent PIAs as per the example below (refer to the

Cluster vs Independent PIAs section for more information about using Independent PIAs or Clustered PIAs)

Web Server Machine 1


PIA1Listening on:


PIA2Listening on:



Clustered PIA

Listening

on port 80

Load Balancer

(or RPS)



PIAListening on:





Listening

on port 80

Load Balancer

(or RPS)

Oracle Page 9

Advantages/Disadvantages to Each Domain Type

SINGLE-SERVER DOMAIN: Advantages:

Very simple set up and easy to support/maintain

Uses less resources (memory, CPU, file handles) since there is just one java process for the entire WebLogic domain

Disadvantages:

The PIA does not have a dedicated java process since it is shared with the WebLogicAdmin server. So this may not be the ideal setup in environments where there is a higher load on the web server,

since the PIA has to share its resources (memory, CPU, file handlers etc) with WebLogicAdmin

In environments where more than one PIA is needed, the single-server domain option can still be used (by setting up multiple single-server domains), but you cannot monitor/configure all of the

PIAs from a single, centralized WebLogic console. Instead each PIA would need to be

monitored/configured from a separate WebLogic console.

MULTI-SERVER DOMAIN: Advantages:

Allows for scalability as you can easily add/remove PIAs as needed, to a multi-server domain

You can monitor/configure all the servers (PIAs, PSEMHUB, etc) from a single, centralized WebLogic console

The multi-server domain option is required for some functionality such as PSEMHUB. Disadvantages:

More machine resources (memory, CPU, file handles are needed) since the WebLogicAdmin and each managed server (PIA, PSEMHUB, etc) have a separate java process.

DISTRIBUTED MANAGED SERVER (DMS): Advantages:

Allows you to install multiple PIAs on different physical servers and manage them using a single centralized admin console

Allows for stateful failover, even when you have multiple physical web servers (refer to section Clustered vs. Independent PIAs for more details about stateful failover).

Disadvantages:

The configuration and installation of a DMS is complex

Starting/stopping the PIAs is not as straightforward with a DMS

Support/troubleshooting of a DMS is more difficult due to its complexity

Oracle Page 10

What Domain Type Option Works Best for My Environment?

The Advantages/Disadvantages section (see previous section) should help you decide what will work best for

your environment. In addition, below is some information on each domain type and situations when customers

would choose to use that domain type.

Single-Server Domains

Single-Server domains are often used in the following environments:

Test/Demo/Development environments (where there are few users. And there may also be fewer machine resources, such as memory, CPU, etc)

Small Production Environments (where one PIA is sufficient for all users)

Some customers choose the Single-Server Domain option even in large production environments. This can be accomplished by installing multiple single-server domains. The downside to this approach is that

you have to access a separate WebLogic console to monitor/configure each of the PIAs. But the upside

is the simplicity of installing/configuring a single-server domain.

Multi-Server Domains

Multi-Server domains are usually installed in Production environments, especially large environments where it

is necessary to use multiple PIAs. The attractive feature, for using multi-server domains in production

environment, is that you can view and configure all PIAs from a single Weblogic console.

Distributed Managed Server (DMS)

Very few PeopleSoft customers use DMS, as it is more complex to set-up, configure and support. But below

are the main reasons some customers choose to use it:

Customer wants to implement stateful failover AND they need to disperse PIAs over multiple physical servers (refer to next section for details about stateful failover)

Customer has PIAs spread over multiple physical servers and they want to be able to monitor and configure all of the PIAs from a single WebLogic console.

Oracle Page 11

How to Install Single-Server, Multi-Server or DMS

Single-Server Domains

To install a single-server domain, refer to the instructions in the PeopleTools 8.5x Installation guide. Below are

links to the Installation Documents

PeopleTools 8.50 Installation Guide



In the PeopleTools 8.5x Installation Guide (links above), you will need to refer to section Setting Up the

PeopleSoft Pure Internet Architecture option.

When installing the PIA, you will need to choose the Single Server Domain option.

After you install the PIA, refer to section (in installation guide) titled Verifying the PeopleSoft Pure Internet

Architecture Installation. This section provides instructions on how to start the PIA, in your environment

Multi-Server Domains

To install a a multi-server domain, refer to the instructions in the PeopleTools 8.5x Installation guide. Below

are links to the Installation Documents




In the PeopleTools 8.5x Installation Guide (links above), you will need to refer to section Setting Up the

PeopleSoft Pure Internet Architecture option.

When installing the PIA, you will need to choose the Multi Server Domain option.

After you install the multi-server domain, the next step is to determine which of the servers you wish to use (eg

PIA, PIA1, PSEMHUB, etc). If you are using more than one PIA, refer to the next section in this document:

How to Install Independent PIAs or Clustered PIAs.

After you install the PIA, refer to section (in installation guide) titled Verifying the PeopleSoft Pure Internet

Architecture Installation. This section provides instructions on how to start the server(s) you wish to use. Most

of our customers choose to use just the WebLogicAdmin server and PIA. To start these two servers, run:

startWebLogicAdmin.sh (or startWebLogicAdmin.cmd for Windows)

startManagedWebLogic.sh PIA (or startManagedWebLogic.cmd PIA for Windows)

Distributed Managed Server (DMS)

The following document provides step-by-step instructions on installing and starting a DMS:

Doc# 951393.1: How to Install and Configure WebLogic Clusters, Distributed Managed Servers and Node

Managers

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=887277.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1195906.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1369779.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=887277.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1195906.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1369779.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=951393.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=951393.1

Oracle Page 12

Clustered vs. Independent PIAs

Overview This section is applicable to you ONLY if :

You are using multiple PIAs in your environment -AND-

You are using a Multi-Server Domain or a Distributed Managed Server (DMS)

If you are using a Single-Server Domain, this doesnt apply to your environment. Also, if you are using a

Multi-Server Domain with just one PIA, this does not apply to you.

When using more than one PIA in a Multi-Server Domain (or DMS), you have the choice of the following:

1) Independent PIAs: With this set up, each PIA runs independently and is not aware of other PIAs nor does it attempt to communicate with other PIAs (this is the simpler of the two set ups)

2) Clustered PIAs: With this set up, all of the PIAs are aware of each other and can communicate with one another via multicasting or unicasting. This set up is one option for implementing stateful fail-over as the

PIAs can back each other up. (Note that starting with PeopleTools 8.52, the recommended option, for

stateful failover, is to use Coherence*Web)

Your decision to use independent PIAs or clustered PIAs is solely dependent on ONE

factor and that is whether you are going to implement stateful failover. If you are not using stateful failover, you should use independent PIAs. If you are using stateful failover (and not implementing

Oracle Coherence), then you should use clustered PIAs.

So to summarize, you would use a clustered PIA only if:

1. You wish to use stateful failover -AND-

2. You are implementing stateful failover via a WebLogic cluster (as opposed to using Coherence*Web)

If you are not familiar with stateful failover, then refer to the following information which describes the types of

failover (stateful vs. stateless):

Stateless Failover

In Stateless Failover, the data is not replicated. So if the web server, that user is accessing, becomes

unavailable, then the user will lose any information that they are in the process of updating. However,

the user will remain logged into the PeopleSoft application (since the cookie information is still

available on user's browser)

Stateful Failover (also known as session replication and seamless user session transfer)

In Stateful Failover, the data is replicated. So if the web server, that user is accessing, becomes

unavailable, then there is a seamless transfer of user session to another Weblogic server. The user does

not lose any information that they are in the process of updating.

Stateful Failover functionality was recently added to PeopleTools, therefore there are not very many

PeopleSoft customers who have implemented stateful failover. Thus most of our customers choose to install

independent PIAs.

The following sections explain each independent vs. clustered PIAs, in detail.

Oracle Page 13

PIA Types

Independent PIAs

With this set up, each PIA is running independently and there is no communication between the different PIAs.

Example 1: In this example, there are two independent PIAs, each installed on the same machine

Example 2: In this example, there are three independent PIAs, one on Web Server Machine#1 and two more

on Web Server Machine#2

Web Server Machine



PIAListening on:




RPS (or Load Balancer)

Listening

on port 80



PIAListening on:





Listening

on port 80

Load Balancer

(or RPS) PIA-THREEListening on:


Oracle Page 14

Clustered PIAs

With this set up, the PIAs are configured to be in a cluster and multicasting/unicasting is used so that the

PIAs can communicate with one another. As mentioned earlier, the clustered PIA is needed only if you are

implementing stateful failover, as the cluster configuration allows the PIAs to replicate session data of other

PIAs. Thus, if one of the PIAs goes down, the users session can be seamlessly transferred to another PIA.

Note that even though the PIAs are clustered, each uses its own java process and it listens on its own http port.

The clustered PIA is much more complex because of the multicasting/unicasting going on between the PIAs.

Also, there is more memory overhead if you configure the PIAs to replicate each others session info.

Therefore we recommend using it only if you need stateful failover (and if you choose not to use

Coherence*Web for stateful failover implementation)

Example 1: Below is an example of a clustered PIA, with two PIA members, on a multi-server domain

Example 2: Below is an example of a clustered PIA on a distributed managed server domain.

Web Server Machine



PIA1Listening on:


PIA2Listening on:


Load Balancer (or RPS)

Listening

on port 80Clustered PIA



PIA1Listening on:


PIA2Listening on:



Clustered PIA

Listening

on port 80

Load Balancer

(or RPS)

Oracle Page 15

Advantages/Disadvantages to Clustered vs Independent PIAs

INDEPENDENT PIA: Advantages:

Very simple

Uses less resources than clustered PIA, since there is no communication between PIAs and since session info is not stored on multiple PIAs

Disadvantages:

None

CLUSTERED PIA: Advantages:

Allows for stateful failover (in the event that you are not using Oracle Coherence*Web for stateful failover)

Disadvantages:

This is a rather complex setup since unicasting/multicasting is required for communication between PIAs

More machine resources (memory and CPU) required for each PIA since the PIAs back up each others session info and since unicasting/multicasting communications occur between each of the

PIAs

Oracle Page 16

What PIA Type Works Best for My Environment?

As mentioned above, you should always use independent PIAs unless:

1. You wish to use stateful failover -AND

2. You are implementing stateful failover via a WebLogic cluster (as opposed to using Coherence*Web)

NOTE: Starting with PeopleTools 8.52, we recommend installing Oracle Coherence*Web (instead of using a

WebLogic clustered PIA) in order to obtain stateful failover. For more details about use of Coherence*Web

refer to attachment Red Paper Deploying Coherence for PIA.pdf in the following document:

Doc# 747378.1: WHITE PAPER : Clustering and High Availability for PeopleTools

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=747378.1

Oracle Page 17

How to Install Independent PIAs or Clustered PIAs

How to Install a Clustered PIA:

A clustered PIA is automatically configured when you install a Multi-Server WebLogic domain or a DMS. The

clustered PIA is defined with two servers: PIA1 and PIA2. You can easily clone PIA1 or PIA2 if you wish to

add more PIAs to the cluster. The following document provides details on installing a cluster and how to

configure it for stateful failover:

Doc# 951393.1: How to Install and Configure WebLogic Clusters, Distributed Managed Servers and Node

Managers

How to Install Independent PIAs

An independent PIA, named PIA is automatically configured when you install a Multi-Server WebLogic

domain or a DMS. To add more independent PIAs, you need to clone PIA. This is done as follows:

1. Bring up the WebLogic Console: a. Open browser and use url http://web-server-machine:9999/console b. Log in (default username is system and default password is Passw0rd)

2. Clone PIA a. Click Lock & Edit button on top left menu bar b. On left menu, expand Environment and click Servers c. Now click the check box next to PIA d. Click the Clone button e. A new window is displayed. Enter a new server name. Example: PIA_TWO f. Note that each PIA needs to listen on a different port (if on same machine), so you will need

to change the port# value.

g. Click Ok. Then click Activate changes h. Repeat above process for however many PIAs you need.

3. Next we need to deploy the Peoplesoft Application to the new PIA(s). a. Click Lock & Edit button on top left menu bar b. Choose Deployments on left-hand menu c. Open the peoplesoft application by clicking on peoplesoft hyperlink d. Go to Targets tab e. Click box next to Component to choose all components f. Click Change Targets button g. You should see the list of available servers, including your new PIA_TWO h. Select it i. Click Yes button. j. Now click Activate Changes

You can now start each PIA in a similar fashion to how you start PIA. Example:

startManagedWebLogic.sh PIA

startManagedWebLogic.sh PIA_TWO

If the WebLogic domain is installed on Windows, you can create a Windows service for each PIA. Example:

installNTService.cmd PIA

installNTService.cmd PIA_TWO

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=951393.1https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=951393.1http://web-server-machine:9999/console

Oracle Page 18

Other Resources

This document concentrated on a couple key configurations to consider when installing WebLogic PIA:

1) Domain type

2) Clustered vs. Independent PIA's

In addition to the above configurations, there are many other things to consider when installing/configuring

WebLogic such as setting heap size, configuring SSL, getting latest Weblogic patches, etc. Below are other

resources that may help you with any other WebLogic configurations that you need help with:

This knowledge document provides a variety of information on using WebLogic 10.3.x with PeopleSoft: Doc ID 1390513.2: Information Center: WebLogic 10.3.x for PeopleSoft

The PeopleBooks "System and Server Administration" includes a section on working with WebLogic. This can be accessed as follows:

1. Go to the Oracle Hosted PeopleBooks Site: http://docs.oracle.com/cd/E17566_01/epm91pbr0/eng/psbooks/psft_homepage.htm

2. Go to 'PeopleTools' section and choose your PeopleTools Release 3. Go to the 'Administration Tools' section and click on 'PeopleTools 8.5x: System and Server

Administration'

4. Refer to chapter 'Working with Oracle WebLogic'

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1390513.2http://docs.oracle.com/cd/E17566_01/epm91pbr0/eng/psbooks/psft_homepage.htm

weblogic install options

Documents

x domain

singleserver weblogic

domain types

clustered pias

clustered vs independent

domain type option works

pia types

intended audience