Show TOC

Component documentationHow Requests Are Handled by Portal Runtime Locate this document in the navigation structure

 

The Portal Runtime has an HTTP servlet (prt) contained in a Java EE application (irj), which runs in the AS Java Web container. The servlet is the entry point for all requests, which are handled by the following components of the Portal Runtime:

  • Dispatcher: The prt servlet that receives the request. It selects the appropriate connection based on the request parameters, and passes the request to this connection.

  • Connection: The connection does the following:

    • Handles the servlet request and forwards it to the request manager (for the standard Portal Runtime connection portal).

    • Creates the portal request and response objects for the request.

    • Manages user authentication.

    • When requested, creates URLs for this connection.

    • Defines the hooks for the request. For more information, see Hooks.

  • Request Manager: The request manager does the following:

    • Builds the Portal Object Model (POM) tree and processes the POM and request events.

    • Executes the portal components involved in the request and retrieves the content.

  • Object Broker: The object broker manages the creation and lifecycle of all portal component and service objects. It manages all class loading and dependency issues.

Developers of portal applications have the tools to control what occurs within the request manager, especially what occurs during the creation of the POM tree and content, as described in Portal Object Model (POM).