Skip to Main Content
Return to Navigation

WebLogic Domain Types

This section provides an overview of Weblogic domain types and discusses:

Understanding WebLogic Domain Types

During PIA setup, you can choose between two different WebLogic domain configurations: a single-server domain and a multi-server domain. A multi-server domain can be expanded across multiple machines using the distributed managed server option. So, a distributed managed server implementation is a variation of the multi-server domain. Each of these domain configurations has a specific purpose but is fully customizable beyond that purpose.

This section discusses:

  • single-server domains.

  • multi-server domains.

  • distributed managed servers.

Single-Server Domains

In a single-server configuration, the WebLogic domain’s administration console and the J2EE components of PIA are all provided on a single instance of WebLogic Server. This configuration is intended for single-user or very small scale, non-critical production environments. It can be used as a starting point for you to familiarize yourself with WebLogic Server.

In a single-server domain, the resources used to administer WebLogic Server and your PeopleSoft application are not isolated from one another, therefore you don't administer each element individually. While each element must complete for the same resources, the low resource requirements of this configuration make it ideal for small scale and non-production usage.

The single-server domain in a PeopleSoft implementation consists of only one server: PIA.

Single-Server Deployment

Some of the servlets deployed in a single-server domain configuration must be accessed using a modified URL:

http://server:port/servlet_name/...

The single-server domain configuration deploys servlets as follows:

Application

Deployed to Server

Servlet Name in URL

PORTAL

PIA

(not needed)

PSIGW

PIA

PSIGW

PSEMHUB

PIA

PSEMHUB

PSINTERLINKS

PIA

PSINTERLINKS

Console

PIA

console

HttpProxyServlet

Defined but not deployed.

(not needed)

HttpClusterServlet

Defined but not deployed.

(not needed)

Single-Server Domain Specific Settings

To configure the single-server domain specific settings, launch the Administration Console.

In the console, expand the Environment tree and select Servers. Click on the PIA server. Select the Configuration tab, and the General sub-tab. The default web application for the PIA server is PORTAL. The single-server domain specific default settings for the PIA server are as follows:

Setting

Default Value

Listen address

* (all local IPs).

Listen Port

80 (set during PIA setup).

SSL Listen Port Enabled

Enabled with demonstration self-signed digital certificates.

SSL Listen Port

443 (set during PIA setup).

Note: To configure SSL, you must also define SSL certificates.

See Implementing WebLogic SSL Keys and Certificates.

Example: Single-Server Domain

The following illustrates sample contents of a typical single-server domain:

Server

Process Type

WebLogic and PIA Elements

Single server machine

WebLogic administration

Weblogic Administration Server

 

Server instance

PIA

 

Servlet or application

Administration Console

PORTAL

PSEMHUB

PSIGW

Multi-Server Domains

The multi-server domain configuration is intended for production environments. This configuration takes advantage of WebLogic’s administration server and managed server architecture. In a multi-server configuration, multiple instances of WebLogic server are used, each contributing a specific function. The WebLogic console is provided on the domain’s administration server, WebLogicAdmin, and the J2EE components of PIA are provided on individual or shared WebLogic managed servers.

A production application warrants process and resource pool isolation for greater stability and optionally tighter security controls, which this configuration provides. In a multi-server configuration, the resources used for WebLogic domain administration and monitoring are isolated from similar resources used to support the PIA application. A server process named WebLogicAdmin performs nothing but WebLogic administration, which includes domain administration and monitoring. Continuing that separation, the individual PIA servlets are (usually) isolated from each other. The PIA servlets are targeted and deployed across a portion of the six remaining server definitions, all of which are classified asmanaged servers, which are delivered in the multi-server configuration.

A multi-server domain in a PeopleSoft implementation creates the following servers:

WebLogicAdmin

Administration server for WebLogic domain administration.

PIA

Server for the PeopleSoft Interaction Hub and integration gateway.

PIA1

Server for the PeopleSoft Interaction Hub and integration gateway.

PIA2

Server for the PeopleSoft Interaction Hub and integration gateway.

PSEMHUB

Server for the PeopleSoft Environment Management Framework application.

RPS

Server for WebLogic reverse proxy server applications.

Multi-Server Servlet Deployment

Some of the servlets deployed in a multi-server domain configuration must be accessed using a modified URL:

http://server:port/servlet_name/...

The multi-server domain configuration deploys servlets as follows:

Application

Deployed to Server, Cluster (members)

Servlets Name in URL

PORTAL

PIA, PeopleSoftCluster (PIA1, PIA2)

(not needed)

PSIGW

PIA, PeopleSoftCluster (PIA1, PIA2)

PSIGW

PSEMHUB

PSEMHUB

PSEMHUB

PSINTERLINKS

PIA, PeopleSoftCluster (PIA1, PIA2)

PSINTERLINKS

Console

WebLogicAdmin

console

HttpProxyServlet

RPS

(not needed)

HttpClusterServlet

Defined but not deployed.

(not needed)

Multi-Server Domain Specific Default Settings

To configure the multi-server domain specific settings, launch the Administration Console. In the Domain Structure tree, expand Environment, select Servers and click on the appropriate servlet, server, or application. Then select the Configuration tab, and the General sub-tab.

The domain specific default settings for the WebLogicAdmin server are as follows:

WebLogicAdmin Setting

Default Value

Listen Address

* (all local IPs)

Listen Port

9999

SSL Listen Port Enabled

Disabled

The domain specific default settings for the PIA server are as follows:

PIA Setting

Default Value

Listen Address

* (all local IPs)

Listen Port

80 (set during PIA setup)

SSL Listen Port Enabled

Enabled with demonstration self-signed digital certificates.

HTTPS Listen port

443 (set during PIA setup)

The domain specific default settings for the PIA1 server are as follows:

PIA1 Setting

Default Value

Listen Address

Locally determined hostname.

Listen Port

80 (set during PIA setup)

SSL Listen Port Enabled

Enabled with demonstration self-signed digital certificates.

SSL Listen Port

443 (set during PIA setup)

The domain specific default settings for the PIA2 server are as follows:

PIA2 Setting

Default Value

Listen Address

127.0.0.1

Listen Port

80 (set during PIA setup)

SSL Listen Port Enabled

Enabled with demonstration self-signed digital certificates.

SSL Listen Port

443 (set during PIA setup)

The default web application for the PSEMHUB server is PSEMHUB. The domain specific default settings for the PSEMHUB server are as follows:

PSEMHUB Setting

Default Value

Listen Address

* (all local IPs)

Listen Port

8001

SSL Listen Port Enabled

Disabled

In the console, navigate to select Environments, then select RPS, then select Configuration, then select General to configure the RPS server. The default web application for the RPS server is HttpProxyServlet. The domain specific default settings for the RPS server are as follows:

RPS Setting

Default Value

Listen Address

* (all local IPs)

Listen Port

8080 (set during PIA setup)

SSL Listen Port Enabled

Enabled with demonstration self-signed digital certificates.

SSL Listen Port

8443 (set during PIA setup)

Note: To configure SSL, you must also define SSL certificates.

See Implementing WebLogic SSL Keys and Certificates.

Example: Multi-Server Domain

The following illustrates the elements running within a typical multi-server domain:

Server

Process Type

WebLogic and PIA Elements

Single server machine

WebLogic administration

WebLogic Administration Server (WebLogicAdmin)

WebLogic Node Manager

 

Managed Server

PIA 1, PIA 2 for PeopleSoft Interaction Hub

 

Managed Server

PIA for PSIGW

 

Managed Server

RPS for httpproxyservlet to proxy content for PIA 1 and PIA 2

Distributed Managed Servers

The distributed managed server configuration, although listed alongside the single-server and multi-server domain types, is not atrue domain type. It's an optional extension for an existing multi-server configuration. As with the multi-server domain type, this configuration takes advantage of WebLogic’s managed server architecture. The distributed managed server configuration is intended for production environments encompassing multiple machines.

A distributed managed server configuration enables you to spread a logical WebLogic domain configurationphysically across multiple machines in a heterogeneous network. One server machine might act as the domain administration server, while the other server machines act as distributed managed servers, running various manages servers, such as PIA1, PIA2, and so on. Typically, you would also take advantage of the WebLogic Node Manager, which enables a system administrator to control the managed servers remotely.

See your WebLogic Node Manager documentation.

In a distributed, multi-server configuration you can have multiple machines, multiple collections of resources and program files, multiple web server processes, and a replicated domain configuration file. In this model, if any of system resources or server instances becomes unavailable, work shifts to the next instance of that resource. In the multi-server configuration, an increase in PeopleSoft Interaction Hub usage, for example, can be accommodated by configuring an additional WebLogic server instance or machine to also serve the PeopleSoft Interaction Hub. Using distributed manages servers provides flexibility in shaping your hardware allocation to meet your system demands.

Benefits of the Distributed Managed Server

A distributed managed server configuration provides the same benefits as a multi-server configuration with the added benefit of hardware isolation. This option requires a multi-server installation to be performed to some other location, which will contain the configuration for this distributed managed server.

The fundamental benefits of a multi-server configuration include:

  • Dedicated service providers: Web servers can be dedicated to providing PeopleSoft Interaction Hub and are insolated from other portions of PIA such as PeopleSoft Integration Gateway or PeopleBooks.

  • Redundant service providers: Multiple web servers can be used to serve different aspects of PIA, providing load balancing and failover support.

  • Distributed resources: Multiple web server machines can be used, each capable of serving different or redundant aspects of PIA.

  • Centralized and replicated configuration: Master domain configuration is centralized and distributed server information is replicated locally.

The server configuration settings for a distributed managed server are maintained by that domain’s administration server are stored locally on that administration server. Configuration settings are replicated to a managed server during its startup, but are only maintained as a read-only backup copy for that individual managed server in the event that the administration server isn't available the next time this particular managed server needs to be started.

Note: Only one managed server can be run per distributed managed server domain directory. If you intend to run multiple distributed managed servers on a single machine, perform the PIA install and create unique distributed managed server domain directories, one for each distributed managed server that you intend to run on that machine.

Example: Distributed Managed Server

The following illustrates the multiple servers, their roles, and the various elements running on the multiple server machines within a sample distributed managed server configuration:

Server

Role

WebLogic and PIA Elements

Server 1

Domain Administration Server

WebLogic Administration Server (WebLogicAdmin)

Server 2

Distributed Managed Server

PIA1 (for PeopleSoft Interaction Hub)

PIA2 (for PeopleSoft Interaction Hub)

WebLogic Node Manager

Server 3

Distributed Managed Server

PIA3 (for PeopleSoft Interaction Hub)

PIA4 (for PeopleSoft Interaction Hub)

WebLogic Node Manager

Server 4

Distributed Managed Server

PIA (for Integration Gateway)

WebLogic Node Manager

Server 5

Distributed Managed Server

RPS (for httpproxyservlet

WebLogic Node Manager

Common Default Settings

Single-server and multi-server domain configurations have many settings in common.

Domain Defaults

Many of these common settings can be configured in the WebLogic Server Console, but some are configured in other environments. Default values are listed when available.

Setting

Default Value

Where To Configure In the Administration Console

SSL functionality

Enabled with demonstration self-signed digital certificates.

Environment, Servers server name, Configuration, Keystores tab and SSL tab.

Command line: pskeymanager

Server logs

Weblogic domain\logs\server name_*.log

Environment, Servers, server name, Logging.

HTTP access log

Disabled

Environment, Servers, server name, Logging, HTTP.

HTTP keep-Alive

30 seconds

Environment, Servers, server name, Protocols, HTTP.

HTTPS keep-Alive

60 seconds

Environment, Servers, server name, Protocols, HTTP.

Low memory settings

various

Environment, Servers, server name, Configuration, Tuning.

Stuck Thread Max Time

600

Environment, Servers, server name, Configuration, Tuning.

Stuck Thread Timer Interval

60

Environment, Servers, server name, Configuration, Tuning.

Enable Administration Port

Disabled

Click the domain name (such as peoplesoft) in the Domain Structure section, then select Configuration, General.

PORTAL HTTP session monitoring

On (applies only to servers running PORTAL)

Deployments, Applications, peoplesoft, PORTAL, Monitoring.

System administrator user ID

system (set during PIA setup)

Security Realms, myrealm, Users and Groups, Users.

System administrator password

password (set during PIA setup)

Security Realms, myrealm, Users and Groups, Users.

System operator user ID

operator

Security Realms, myrealm, Users and Groups, Users.

System operator password

password

Security Realms, myrealm, Users and Groups, Users.

System monitor user ID

monitor

Security Realms, myrealm, Users and Groups, Users.

System monitor password

password

Security Realms, myrealm, Users and Groups, Users.

Script and Environment Defaults

Modify these settings by editing a setEnv script or applying command line parameter overrides to WebLogic control scripts.

The following settings specify the names and structure of various directories on the web server machine.

Setting

Default Value

Description/Override

PS_HOME

(none)

PeopleSoft home directory (set during PIA setup).

BEA_HOME

(none)

High-level install directory (set during PIA setup). Where Tuxedo and WebLogic may be installed.

WL_HOME

(none)

WebLogic home directory (set during PIA setup).

DOMAIN_NAME

peoplesoft

Name of this WebLogic domain (set during PIA setup).

JAVA_HOME

(Depends on the operating system platform.)

Location of Java. Set during PIA setup or with a call to WebLogic's CommEnv script.

Note: You configure Java VM options including JVM memory size using the JAVA_OPTIONS_OSplatform parameter, during PIA setup.

The following are miscellaneous settings.

Setting

Default Value

Description/Override

HOSTNAME

Local hostname

Set during PIA setup.

PRODUCTION_MODE

TRUE

Enable WebLogic production mode (set during PIA setup).

DISCOVERY_MODE

FALSE

Disable auto detection of unregistered applications.

Script: setEnv

WLS_USER

Operator

Use to stop WebLogic with stop scripts and run it as a Windows service.

WLS_PW

Password

Use to stop WebLogic with stop scripts and run it as a Windows service.

ADMINSERVER_PROTOCOL

HTTP

Protocol used for managed server to connect to administration server (not used in single-server domain).

ADMINSERVER_HOSTNAME

Single-server: local hostname.

Multi-server: local hostname.

Distributed server: (none — set manually).

Administration server’s hostname that managed servers attempt to connect to by default when started. Set during PIA setup (except distributed server).

ADMINSERVER_PORT

Single-server: HTTP port of PIA server.

Multi-server: 9999.

Distributed server: (none — set manually).

Administration server’s Listen port that managed servers attempt to connect to by default when started. Set during PIA setup (except distributed server).

ADMINSERVER_SERVERNAME

Single-server: PIA.

Multi-server: WebLogicAdmin.

Distributed server: WebLogicAdmin.

WebLogic server instance name of this domain's administration server, used for stopping and starting the server.

WL_VERSION

Detected major WebLogic version.

WebLogic major version, such as 10.

WL_SERVICEPACK

Detected minor WebLogic version.

WebLogic service pack level.

WL_PATCH

Detected WebLogic patch version.

WebLogic patch level.

BACKGROUND_PROCESS

TRUE

Run WebLogic server as a background process. On UNIX you can force foreground execution using the start script’s -foreground option.

The following are debugging output settings.

Setting

Default Value

Description/Override

SET CAPTURE_STDOUT_STDERR

FALSE

(Windows only) Capture standard output and standard error of a WebLogic server running as a foreground process. You can also set this with the start script’s –capture option.

ENABLE_JDPA_DEBUG

FALSE

(PeopleSoft development only) Enable JDPA debug support. You can also set this with the start script’s –debug option.

ENABLE_VERBOSE_GC

FALSE

Enable verbose output of Java’s garbage collector. You can also set this with the start script’s –verbose:gc option.

ENABLE_VERBOSE_SSL

FALSE

Enable SSL debug support. Produces verbose SSL output. You can also set this with the start script’s –verbose:ssl option.

ENABLE_VERBOSE_WL

FALSE

Enable verbose output for the core WebLogic server (not verbose output of PIA). You can also set this with the start script’s –verbose:wl option.

MAX_FILE_DESCRIPTORS

4096

The number of open file descriptors set for any Weblogic server process.

The following are HTTP forward proxy support settings.

Setting

Default Value

Description/Override

ENABLE_HTTP_PROXY

FALSE

Enable the use of the forward http proxy.

HTTP_PROXY_HTTPHOST

(none)

IP address or hostname of the forward HTTP proxy server for HTTP requests.

HTTP_PROXY_HTTPPORT

(none)

HTTP Port number of the forward HTTP proxy server for HTTP requests.

HTTP_PROXY_HTTPSHOST

(none)

IP address or hostname of the forward HTTP proxy server for HTTPS requests.

HTTP_PROXY_HTTPSPORT

(none)

HTTP Port number of the forward HTTP proxy server for HTTPS requests.

HTTP_PROXY_NONPROXY_HOSTS

localhost,local hostname, anddomainname.

Host names and domain names of content servers that will not be proxied.