FAQ: How the Portal Page Engine(PPE) and Invalidation Requests Work
(Doc ID 430820.1)
Last updated on FEBRUARY 03, 2020
Applies to:Portal - Version 220.127.116.11 to 18.104.22.168.0 [Release 9iASR2 to FMW11g]
Information in this document applies to any platform.
Sometimes Oracle Portal is seen to be one of the more complicated components in the Middleware stack. Whilst Oracle Portal does use most of the Middlware software components (OID, SSO, WebCache, OHS, etc.), Oracle Portal uses standard calls and methods common to other component with two notable exceptions. These two are:
1) The events of the Parallel Page Engine Servlet (PPE)
2) The mechanism for issuing WebCache Invalidations.
This bulletin attempts to take the mystic out of these two special events thus enabling customers to be more confident in using and configuring Oracle Portal for their own specific environment.
This is not a problem solving note but just a documentation note aiming to provide clarity to some of the more complicated part of the Portal application. However, there are some links below to relevant problem solving notes.
This bulletin does not attempt to cover all Oracle Portal configuration issues. It will only concentrate on the two events that are unique to the Oracle Portal component within the AS10g component stack, namely the PPE and Invalidation events.
For an in-depth description of both these activities, please refer to the appropriate chapters of the Portal Configuration guide 10.1.2 or 10.1.4 or the Fusion Middleware Administrator's Guide for Oracle Portal 11.1.1 on the Oracle Technology Network (OTN) website.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Parallel Page Engine Servlet Events|
|2. Invalidation Events|