Oracle9iAS Portal Developer Kit
Understanding the provider.xml for URL-Based Portlets

PDK Release 2 (9.0.2 and later) - URL-Based


A web provider is one that is written as a web application. It is installed and hosted in a web server and is remote from Oracle9iAS Portal.  Previously, a web provider required development in Java, Java Servlets, and Java Server Pages.  Now, with the addition of the URL-based provider runtime, a web provider can manage a set of portlets in any language. 

With URL-based portlets, the PDK has extended its framework to create portlets in any programming language.  The only requirement is that your application is accessible through a URL.  To do this, the PDK offers a provider runtime called URLProviderInstance that implements the functions of a provider.  The URLProviderInstance extends DefaultProviderInstance.  Like DefaultProviderInstance, the URLProviderInstance's main function is to own and manage a set of portlets.  The URLProviderInstance also uses provider.xml as its initialization file.  

The provider.xml file lists and defines a set of portlets.  The portlets are normally Java, Java Servlets, or JSPs.  The provider.xml has been extended to list and define portlets of any language.  This article describes the configuration of provider.xml as it pertains to the URL-based portlets.

CONFIGURATION

The provider.xml file stores information that is used by the URLProvider.  URLProvider in turn is divided into two classes -

The provider.xml file stores information by hierarchy.  Its hierarchical nature starts with "Provider".  The file is organized to simplify the process required by the URLProviderInstance to parse the file.  The provider.xml file is also organized to increase readability. 

This section describes those tags within provider.xml that have been added and/or modified for URL-based portlets.  When creating your own provider.xml, you must follow the hierarchy and syntax required for the URLProviderInstance to properly parse the file.

Provider tag

The provider tag is the first tag in the provider.xml file.  Since the class attribute defaults to DefaultProviderDefinition, you need to specify oracle.portal.provider.v2.http.URLProviderDefinition  as the class that extends DefaultProviderDefinition.  The provider tag currently has two attributes which are supported by the URLProviderDefinition.  The provider tag has also been modified to accept the following tags:

Portlet tag

The provider has a tag called portlet. The portlet has an attribute named class through which portlet's runtime class can be specified.  It also contains the following tags. 

<registrationPortlet>false</registrationPortlet>
<accessControl>public</accessControl>
<renderer class="oracle.portal.provider.v2.render.RenderManager">
     <showPage class="oracle.portal.provider.v2.render.http.URLRenderer">   
     <accessControl>registered</accessControl>
     <pageUrl>http://support.sitescape.com/forum/support/dispatch.cgi</pageUrl>
    <filterType>text/xml</filterType>
    <filter class="oracle.portal.provider.v2.render.XmlFilter">
        <useAuthLinks>false</useAuthLinks>
        <stylesheet>D:/ sitescape/default_sitescape.xsl</stylesheet>
        <urlContentType>text/html</urlContentType>
    </filter>
    </showPage>
 </renderer>

 

For more information on the PDK runtime for URL-based portlets, refer to the following article:

Understanding the PDK Runtime for URL-Based Portlets


Revision History: