Browse Prior Art Database

Self-Configured Mechanism For Automated Discovery of Portlets For Page Compositions

IP.com Disclosure Number: IPCOM000031669D
Original Publication Date: 2004-Oct-04
Included in the Prior Art Database: 2004-Oct-04
Document File: 2 page(s) / 84K

Publishing Venue

IBM

Abstract

Portlets are dynamic entities that have a life-cycle used to generate dynamic HTML, cHTML or WML markup fragments. The aggregation of these portlets is used to create a page on the web or a wireless device. Currently, there are XML based tools that only allow to add pre-existing portlets to a page. Also, there are user interfaces that allow to add portlets to pages at any point in time. However, these approaches are not automated and require human intervention.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Self-Configured Mechanism For Automated Discovery of Portlets For Page Compositions

The problem being solved is the ability of the Portal Server to behave as a self-configuring entity when new applications are deployed with new portlets . We will describe a fully-automated technique for portlets to advertise their availability so that the appropriate page compositions can consume them at the appropriate time. The advantage of this technique is that newly created pages can add a pre-existing portlet and also newly installed portlets can be added to pre-existing pages by using a XML based deployment tool that automates the whole process. This requires no human intervention and is a very useful technique in upgrading from a lower level to a higher level as the user upgrades their product. Another benefit is a faster and more efficient approach as this also works in the lightweight versions of the Portal where the user interface may not exist.

The invention:

The invention enables the user to seamlessly discover portlets that are to be added to page compositions and enhances the self-configuring capabilities of the Portal by maintaining a Portlet MetaData repository of pertinent information. The repository holds the portlet specific metadata which includes the portlet reference, list of pages that are consumers of the portlet, a flag that reflects if the portlet reference is valid along with all the other relevant data. Note that all the portlets from the disparate applications have a unique identifier which is qualified by appending the application name with the portlet name.

We will illustrate the process with Figure 1 on the next page. For the sake of argument, let us assume that a web application WAR2 is being currently installed on the Portal Server with the intent of creating a new page called Page1. This page holds a reference to portlets A, B and C....