Oracle9iAS Portal Developer Kit
Understanding the provider.xml for URL Services

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 consisted only of the JPDK which meant development in Java, Java Servlets, and Java Server Pages.  Now, with the addition of the PDK URL Services, a Web Provider manages a set of portlets in any language. 

The PDK URL Services has extended the existing JPDK Framework to create portlets regardless of the programming language.  The only requirement is that your application is accessible through a URL.  To do this, the PDK URL Services offers a Provider Runtime called URLProvider that implements the functions of a provider.  The URLProvider extends DefaultProvider.  Like DefaultProvider, the URLProvider's main function is to own and manage a set of portlets.  The URLProvider 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.  The article describes the configuration of the provider.xml as it pertains to the PDK URL Services.  For information about the default configuration and usage of the provider.xml file, please review the Provider Definition XML Tag Reference

CONFIGURATION

The provider.xml file stores information that is used by the URLProvider.  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 URLProvider 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 Services.  When creating your own provider.xml, you must follow the hierarchy and syntax required for the URLProvider 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 DefaultProvider, you will need to specify oracle.portal.provider.v1.http.URLProvider  as the class that implements oracle.portal.provider.v1.Provider.  The provider tag currently has two attributes which are supported by the URLProvider.  The provider tag has also been modified to accept the following tags:

Portlet tag

The provider has a tag called portlet. The portlet tag has three attributes.  It also contains the following tags. 

The following sub-tags are available under <inputParameter>: -

Example of usage:

<inputParameter class="oracle.portal.provider.v1.URLPortletParameter"> 

    <name>term</name>

    <isMandatory>false</isMandatory>

    <displayName>Search Oreilly for </displayName> 

    <value>JAVA</value> 

</inputParameter>
<registrationPortlet>false</registrationPortlet>
<redirectUrl>inspRedirectUrl</redirectUrl>
<accessControl>public</accessControl>

Using the above filter, HRefs of type

<a href="http://www.yahoo.com" type="1">Link to Yahoo</a> will not be rendered inline.


Revision History: