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 as managed servers, which are delivered in the multi-server configuration.
Note:
Do not create a web server domain using the names PIA, PIA1, PIA2, or weblogic. The name of the WebLogic domain and the server and cluster names within it must be unique. The names PIA, PIA1, and PIA2 are reserved for use by the PeopleSoft system. The name weblogic is reserved for use by the Oracle WebLogic software. These restrictions apply to single server and multi-server domain creation.
A multi-server domain in a PeopleSoft implementation creates the following servers:
| Term | Definition |
|---|---|
|
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:
-
Sign in to the WebLogic Remote Console.
-
Click Edit Tree, and then select Environment > Servers.
-
Click on the appropriate servlet, server, or application, and then select the General page.
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 |
HTTP port set during PIA setup. |
|
SSL Listen Port Enabled |
Enabled with demonstration self-signed digital certificates. |
|
HTTPS Listen port |
HTTPS port 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 |
HTTP port set during PIA setup. |
|
SSL Listen Port Enabled |
Enabled with demonstration self-signed digital certificates. |
|
SSL Listen Port |
HTTPS port 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 |
HTTP port set during PIA setup. |
|
SSL Listen Port Enabled |
Enabled with demonstration self-signed digital certificates. |
|
SSL Listen Port |
HTTPS port 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 |
8081 |
|
SSL Listen Port Enabled |
Disabled |
In the WebLogic Remote Console, click the Edit Tree tile, then select 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.
Example: Multi-Server Domain
The following table lists the elements for processes running within a typical multi-server domain:
| Process Type | WebLogic and PIA Elements |
|---|---|
|
WebLogic administration |
WebLogic Administration Server (WebLogicAdmin) WebLogic Node Manager |
|
Managed Server |
PIA1, PIA2 for PeopleSoft Interaction Hub |
|
Managed Server |
PIA for PSIGW |
|
Managed Server |
RPS for httpproxyservlet to proxy content for PIA1 and PIA2 |