Portal Technology Implementation

To implement PeopleTools portals, you need to:

  • Design and configure the portal environment.

  • Install PeopleSoft Pure Internet Architecture.

  • Configure your web profile.

  • Configure application security.

  • Set up the portal.

  • (Optional) Set up JSR 168.

  • Configure performance features, such as caching.

Note: These implementation activities assume that you have installed your required databases, application servers, and web servers.

In the designing phase of your implementation, take advantage of all Oracle resources for PeopleSoft applications including installation guides, certification requirements, red papers, and product documentation.

Build the physical network and server architecture that is necessary to support your implementation. Ensure that you consider the various facets of network management and security, including creating subnets with appropriate routers and switches; creating firewalls, proxy servers, and reverse proxy servers, and using Secure Sockets Layer/Transport Layer Security.

During implementation, you should research and understand how to:



Size servers appropriately

See your hardware configuration guides and PeopleSoft minimum requirements.

Configure software and hardware to optimize speed and performance

See your network administration guides.

Set up optimal load balancing

See your server configuration guides and industry best practices.

To install one or more PeopleTools portal sites, perform this step:



Run the PeopleSoft Pure Internet Architecture setup program for your database.

See PeopleSoft 9.2 Application Installation for your database platform.

During PeopleSoft Pure Internet Architecture setup, you'll be prompted to select one of the web profiles delivered with your PeopleSoft application or to specify a new web profile if no existing profile meets your needs. To configure your selected web profile, you perform the following step:



Configure your selected web profile.

See Configuring Web Profiles.

See Understanding WebLogic.

Applications come with roles and permissions that you can configure or use as delivered. Roles define the permission lists that are assigned to groups of people. A permission list defines a group of securable objects. A comprehensive role and permission list design is necessary to best manage which users can access each piece of content in the portal.

A powerful feature of PeopleTools security is the dynamic role. User membership to these roles is defined programmatically instead of by manually updating a membership list. Dynamic roles can simplify user role assignments significantly.

To secure access to content, you perform the following steps:



Configure permission lists, roles, and user profiles.

See Configuring Web Profiles.

(Optional) Set up single sign-on.

See Understanding Single Signon.

See Implementing Single Signon Functionality.

See Configuring the LDAP Directory.

To set up the portal, you perform the following steps:



Manage portal definitions.

See Administering Portal Definitions.

Define folders and set folder security.

See Administering Folders.

Define content references, create related links, and set content reference security.

See Administering Content References.

Add templates and set template security.

See Managing Portal Objects.

Create, configure, and secure homepages and dashboards.

See Understanding Homepages and Dashboard Pages.

JSR 168 is an emerging standard for portals running in a Java 2 Platform, Enterprise Edition architecture. It specifies content definitions much like pagelets, which present portal content defined according to the JSR 168 standard. Portlets are Java-based web components that you can register in the PeopleSoft portal. To set up JSR 168, perform the following step:



Implement JSR 168 portlets.

See Describing the Portlet Entity Registry.

Properly configuring caching options significantly increases portal performance. To administer caching features for the portal, perform the following steps:



Configure server-based caching.

See Administering Server-Based Caching.

Configure browser-based caching.

See Administering Browser-Based Caching.

Configure web server-based navigation caching.

See Administering Web Server-Based Navigation Caching.