Web Server

Oracle supports Oracle WebLogic web server for use with PeopleSoft implementations.

The following software runs on the PeopleSoft web server:

Image: Web server running web server services and the web container where PeopleSoft servlets are installed

The following diagram explains about Web server running the web server services and the web container that in turn contain PeopleSoft Servlet installations.

The following PeopleSoft servlets reside on the web server:

When you install Tuxedo, Jolt gets installed by default. The PeopleSoft servlets on the web server transmit requests and data through a connection to Jolt, which runs on the application server. Jolt extends Tuxedo capabilities by acting as the communication layer between the Java-based environment of the servlets and the C++ environment of the application server. You configure the servlets to direct requests from the web server to a predefined Jolt port on the application server.

Image: PeopleSoft servlets on the web server sending messages to the application server through Jolt

The following diagram shows the relationship between Jolt and servlets on the web server:

Web browsers and integrated systems don't send requests directly to the application server. Instead, they send HTTP/S requests to the PeopleSoft servlets running on the web server. The web server translates the HTTP/S request into a Jolt request that is sent to a specified Jolt port. Then the application server, running on Tuxedo, submits the appropriate SQL to the database.

A supported web browser is the primary means by which end users access PeopleSoft applications and system administrators access administrative tools. You do not need to install other software on the workstation running the browser, such as connectivity software or downloaded applets.

The PeopleSoft system sends only the following to the browser:

• HTML

• JavaScript

• Cookies

Because the browser processes only this basic internet content, the client workstation is not burdened with unnecessary processing responsibility. All processing occurs at the server level.

After the system authenticates a user during signon, PeopleTools security deploys web browser cookies to store a unique access token for each user session. As the user navigates around the system, perhaps to a separate PeopleSoft application, the token in the browser cookie is used to reauthenticate the user and bypass the sign-in process. The browser authentication cookie is:

• an in-memory cookie, never written to disk.

• encrypted to prevent snooping.

• check-summed to prevent tampering.

Each PeopleSoft website has a browser capabilities file (browscap) located in:

<PIA_HOME>\webserv\<domain>\applications\peoplesoft\PORTAL.war\WEB-INF\psftdocs\<site>

The system uses the browser capabilities file to form rules based on the values received from the user-agent string sent from client browser connections. The user-agent string identifies various characteristics of the browser and provides system details required for host web servers to tailor content sent to that browser and platform type, as needed. Upon receiving the values passed in the user-agent string, the system matches the values to the rules stored in the browser capabilities file to determine various characteristics, including browser support level, browser type, operating system, device type, and so on.

The file itself contains documentation for the syntax for the properties and rules. However, it is not a file that would be modified regularly outside of Oracle development. It should be modified only if needed or if instructed to do so by Oracle representatives. Keep track of changes, as any changes made to the file would be overwritten during upgrades and maintenance updates.

if Chrome/
browserType=CHROME;
browserTypeClass=chrome;
browserFluidCapable=Y

if MSIE.*Trident/6.0
browserType=IE;
browserVersion=10.0;
ieTridentVersion=6.0;
browserTypeClass=ie;
browserFluidCapable=N

if windows nt 6.0
browserPlatform=WINVISTA/WIN2008;

if (?=.*mac)(?=.*ipad)
browserPlatform=MACIPAD;

if win
browserPlatformClass=win;
browserDeviceTypeClass=pc

if ipad
browserDeviceTypeClass=tablet

if (?=.*Mobile)(?=.*Touch)
browserDeviceTypeClass=phone

You can set up secure web folders to keep your content private and control which users have access.

See Creating Access Control for Files on the Web Server

See Authorize