Page Assembly

Previous sections in this PeopleBook have described the individual components of PeopleSoft Pure Internet Architecture. This section provides a high-level overview.

  1. An HTTP request is sent from the user's browser to the portal’s web server, which invokes the portal servlet. Assume that the browser is requesting a PeopleSoft application page.

  2. The portal servlet makes a request to the Portal Processor to fetch the content reference for the link selected by the user. The Portal Processor fetches the content reference from the portal registry and passes a partially completed HTML document back to the portal servlet.

  3. The content reference could be pointing to any or several of the content providers (specified by a node). Each content reference is referenced in a partially completed HTML document. The portal servlet issues the HTTP request to the appropriate web server and retrieves the HTML document.

  4. The portal servlet then completes the page assembly process with the template, merging the content from the HTML document, and then serves the completed page back to the user’s web browser.

The following diagram illustrates the numerous sources of data for page assembly in the PeopleSoft Pure Internet Architecture:

gv_PeopleSoftPureInternetArchitectureProcessingFlow7e40_tprt743f