Method for dynamically integrating remote portlets into portals

• US 7,502,833 B2
• Filed: 03/12/2002
• Issued: 03/10/2009
• Est. Priority Date: 05/11/2001
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schaeck, Thomas
• Primary Examiner(s): Dollinger; Tonia L. M.
• Assistant Examiner(s): BILGRAMI, ASGHAR H
• Application Number:
  US10/095,421
• Publication Number:
  US 20020169852A1
• Time in Patent Office: 2,555 Days
• Field of Search: 709/217, 705/26, 705/42
• US Class Current: 709/217
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking

Abstract

The present invention discloses a method allowing dynamically integrating remote portlets into each Portal by providing local portlets as remote portlet Web-Services by providing, to each Portal-Server, a publishing functionality allowing electronic creation of a service description for each single local portlet and publishing it into a Central-Registry and a find/binding functionality to find remote portlet Web-Services via the Central-Registry and bind them using the service description for accessing the remote portlet. Preferably, each Portal-Server includes a Portlet-Registry component as well as a Portlet-Proxy. The Portlet-Registry provides service description to the Portlet-Proxy that establishes a SOAP-communication with a remote Portal-Server providing the remote portlet Web-Service to be selected. The main advantage of the present invention is that local portlets become available for all Portal-Server without requiring local installation of the portlet code itself. Furthermore, new remote portlets can be included into a portal by finding them in a registry and binding them.

Claims

1. A method for dynamically integrating a local portlet of a local portal server into a remote portal server connected via network, comprising the steps of:

using a SOAP/HTTP communication protocol component to establish communication between the portal server and the portlet;

creating a service description of said local portlet;

publishing said service description into a UDDI; and

enabling execution of said local portlet at said local portal server in response to a request from said remote portal server by means of finding and binding of said service description of said local portlet in said UDDI by said remote portal server and establishing communication with said local portlet using access information in said service description in said UDDI, wherein said communication is without installation of portlet code of the local portlet onto the remote portal server.

2. A method according to claim 1, wherein said access information of each remote portlet is stored in a local portlet registry and selection of access information of a single remote portlet from said portlet registry is initiated by portlet user.