Portal Framework 

The Portal Framework is a logical environment that consists of a collection of software components. Some of these enable implementation of iViews. Others are interfaces of the portal infrastructure that run processes such as:

·        Creating pages and applying their defined layouts

·        Managing styles and themes

·        Providing access to the resources needed at runtime

These components are contained in the following:

·        Portal Runtime (PRT), an entity that manages iViews. For more information, refer to the section, Portal Runtime.

·        Portal Content Directory (PCD), service-based implementation of the portal infrastructure that interfaces with the database shared by the SAP Web Application and the portal. For more information, see Portal Content Directory.

·        A database shared with SAP Web Application Server. It serves as a central location in which an aggregation of specific portal data is maintained and selectively obtained at runtime for further processing. The PCD has interfaces to the database. For additional information, see Database.

In addition, the Portal Framework is comprised of standard technologies, such as HTML, WML, and XML, as well as protocols such as the following:

·        Hypertext Transport Protocol, and Secured Sockets Layer (HTTP and HTTPS)

·        Authentication protocols, including access to directory servers such as Lightweight Directory Access Protocol (LDAP), Active Directory Services, digital certificates and logon tickets

·        Java Database Connectivity (JDBC), a database protocol for connecting Java software to data in a database system

·        Simple Object Access Protocol (SOAP), a protocol that interfaces with Hypertext Transfer Protocol (HTTP) and Extensible Markup Language (XML), to enable exchange of information across different platforms.

·        SAP Java Connector (JCO), an SAP proprietary interface that allows communication with SAP systems using Java applications

·        P4, an SAP proprietary RMI-based protocol in the J2EE Engine that enables passing messages to components.

·        Hyperrelational Navigation Protocol (HRNP), an SAP proprietary protocol that enables  Drag&Relate functionality in iViews.

The following figure shows the components in the Portal Framework

The following are the main tasks of the Portal Framework:

·        Running development tools for creating portal content, such as iViews, pages, roles, and worksets

·        Running iViews and pages