Cache Control Interfaces 

There are interfaces that can be implemented by any portal component to have more accurate control of the cache:

·        ICachablePortalComponent Interface

·        ICacheValidator Interface

·        ICacheDiscriminator Interface

·        ICacheResourceValidator Interface

A portal administrator could always force the PRT to use the cache properties defined in the profile of the component instead of the methods implemented by the component by setting the property ForceProfileCachingParams to true.

Internal Caching Expiration

The PRT marks the cached content as expired in the following circumstances :

·        A request or a component event has been sent to the component

·        The node mark has changed on a node

·        The request type is REFRESH

·        An exception is raised when executing the service method that is supposed to be stored in the cache

Portal Application Repository

The application repository serves to provide information on all available portal applications (including portal components and portal services). In addition the portal application repository provides a central storage of application configuration and arbitrary application data.

The application repository is packaged and delivered as a standard portal service providing a JNDI interface to the following contexts:

Contexts

Folder	Description
com.sap.portal.system	Root context
com.sap.portal.system/archives	Folders for PAR files
com.sap.portal.system/applications	Folder containing the list of applications loaded in the repository
com.sap.portal.system/configuration	The configuration of the applications

Portal Connection Framework

The Portal Connection Framework (PCF) offers an API allowing to control the process of a request. This layer allows to plug several “Connection” implementations to the portal. Each implementation might have a different request cycle. Connection implementations are delivered and packaged as regular portal applications. The constraints are:

·        The application must be declared as “Load-on-startup” in the application-config section of the deployment descriptor

·        The connection must register itself to the portal registry:

The registration must bind an object of type IServletConnection in the “connections” JNDI context of the portal registry. This can be done during the initialization of a service that has been marked as Load-on-startup.

public synchronized void init(IServiceContext context) { mm_connection = new MyConnection(); try {     PortalRegistry.getInstance().bind(        "/runtime/connections/MyConnection",        mm_connection); } catch (NamingException e) { } }

·        The connection must implement the IServletConnection interface. The interface has one method:

Ў        handleRequest(IDispatcherContext) – the dispatcher context gives access to the environment in which the connection has been started. It gives access to the request, and the response.

There are two connections provided by the PRT:

Default Connections

Connection Name	Type	Description
/runtime/connections/portal	Servlet connection	The default portal connection
/runtime/connections/soap	SOAP connection	Handles any incoming SOAP requests