Portal Content Abstraction 

The portal content abstraction is an API that gives PRT the ability to start and render any kind of portal objects. However, a portal component is the simplest portal object that can be started, but PRT does not make any assumptions about the object type and does not know about the source of the object and its implementation.

The content abstraction enables PRT to be independent of the structure of the content itself. The concept of roles, worksets, iViews, pages, templates or other objects has no impact on the PRT.

JNDI Basis

The API used to achieve this abstraction is based on the JNDI API. This approach ensures that you can take advantage of JNDI defined operations and adhere to this existing standard. All metadata regarding authentication (and more) is passed using standard JNDI properties.

JNDI Service Providers

All portal applications have to register their own JNDI Service provider in a namespace. The contract between the content provider and PRT is:

·        The JNDI provider must be able to provide objects that implement the IPropertyContentProvider and IPropertyContentinterfaces

·        The IPropertyContent implementation must provide the CodeLink property at least. This property is used to get the corresponding PAR file and therefore the implementation from the application repository