Maintaining portlet data currency while minimizing latency

• US 8,468,217 B2
• Filed: 07/26/2006
• Issued: 06/18/2013
• Est. Priority Date: 07/26/2006
• Status: Active Grant

• Current Assignee: Maplebear Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Appleyard, James P., Flores, Romelia H., Salcido, Jason A.
• Primary Examiner(s): Zele, Krista
• Assistant Examiner(s): SCOTT, RANDY A
• Application Number:
  US11/460,164
• Publication Number:
  US 20080040450A1
• Time in Patent Office: 2,519 Days
• Field of Search: 709/217, 709/218, 709/219, 709/220, 709/221, 709/222, 705/100, 705/106, 705/14, 715/764, 715/223
• US Class Current: 709/219
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

Providing data to portlets can include a step of registering a plurality of portlets to determine a type of data required by the portlets. The registering can establish a portlet context for handling future data requests for the portlets. A type of information associated with one of the portlets can be determined. A data acquisition process can be initialized to obtain the determined type of information from a data source. A data request can be received for data of the determined type from the associated portlet. Data can be acquired from the data source using the initialized process. The data request can be responded to using the acquired data. In one embodiment, the acquisition of data from the source and the updating of the portlets can occur asynchronously, where a cache is used to temporarily store data acquired from the data source that is used to update the portlets.

Claims

1. A method for providing data to portlets comprising:

registering, with a portal server, a plurality of portlets executing on a client to determine by the portal server a type of data required by each of the plurality of portlets, wherein the registering establishes a portlet context for handling future data requests received from the portlets at the portal server for each of the plurality of portlets, and wherein the plurality of portlets are organized into a common data set;

determining, at the portal server, responsive to registering the plurality of portlets as a common data set, a type of information associated with one each one of the plurality of portlets in the common data set;

initializing, at the portal server, responsive to determining the type of information, a data acquisition process to obtain the determined type of information from a data source for each one of the plurality of portlets in the common data set;

acquiring data corresponding to the type of information from the data source at the portal server using the initialized data acquisition process;

the portal server placing the acquired data in a data store associated with the portal server;

receiving a data request at the portal server for data of the determined type from at least one of the plurality of portlets;

aggregating data for the plurality of portlets in the common data set into an aggregated data set at the portal server in response to the data request; and

responding to the data request by transmitting the aggregated data set to the client, wherein the client uses the aggregated data set to satisfy the data request and to provide data to at least one other portlet in the common data set.

2. The method of claim 1, wherein the plurality of portlets are a subset of all portlets of the client.

3. The method of claim 1, wherein the portal server service is one of a plurality of portal servers configured in a cluster of portal servers.

4. The method of claim 3, wherein the plurality of portal servers include a backup node and a primary node, where the backup node automatically performs the steps of claim 1 normally handled by the primary node should the primary node fail.

5. The method of claim 3, wherein the plurality of portal servers utilize load balancing to distribute load received from a plurality of clients.

6. The method of claim 1, wherein the portal server includes a registration handler, a master handler, and a data handler, wherein the registration handler performs the registering step, wherein the master handler performs the receiving and responding steps, and wherein the data handler performs the acquiring step.

7. The method of claim 6, wherein the data source is a service provider of a Service Oriented Architecture (SOA), and wherein the data acquisition process is a Web service.

8. The method of claim 1, wherein the data source is a service provider of a Service Oriented Architecture (SOA), and wherein the data acquisition process is a Web service.

9. The method of claim 1, wherein the acquiring step places the acquired data in a local cache before the data request is received, wherein the responding step utilizes preexisting acquired data in the local cache.

10. The method of claim 1, wherein the receiving of the data requests reoccur with a known frequency specified in the registering step.

11. The method of claim 1, wherein the acquiring step automatically reoccurs with a frequency specified for the data acquisition process.

12. The method of claim 1, wherein the data source is a first data source, the method further comprising:

determining a second type of information associated with a different one of the portlets, wherein the initializing and acquiring steps use the data acquisition process to obtain the second type of information from a second data source, whereby the data acquisition process aggregates data from the second data source into the aggregated data set.

13. The method of claim 1, wherein the steps of claim 1 are performed by at least one of a human agent and a computing device manipulated by the human agent, the steps being performed in response to a service request.

14. A method for providing data to portlets comprising:

registering, with a portal server, a plurality of portlets executing on a client to determine by the portal server a type of data required by each of the plurality of portlets, wherein the registering establishes a portlet context for handling future data requests received from the portlets at the portal server for each of the plurality of portlets, and wherein the plurality of portlets are organized into a common data set;

receiving, at the portal server, data update requests originating from a plurality of

different portlets of a client which are registered with the portal server and organized into a common data set, wherein each of the data update requests are reoccurring requests for data to keep information displayed in each of the portlets at the client current with a corresponding data source;

for each of the data update requests, establishing, at the portal server, a data acquisition process with the data source;

automatically creating a data service at the portal server configured to provide data needed to respond to the received data update requests;

the data service receiving data from the data source corresponding to the data update requests-and storing the data in a data store associated with the portal server;

aggregating the data into an aggregated data set at the portal server, the aggregated data set including data for each of the plurality of different portlets in the common data set; and

responding to the data update requests by transmitting the aggregated data set from the portal server to the client having the plurality of different portlets, wherein the data service is a Web service, and wherein the data source is a service provider of a Service Oriented Architecture.

15. The method of claim 14, wherein the data service repetitively receives the data from the data source with a specified frequency that is asynchronous with the reoccurring requests.

16. The method of claim 14, wherein the data source is a first data source, wherein at least some of the data update requests correspond to a second data source, and data is further received from the second data source by the data acquisition process.

17. The method of claim 14, further comprising:

registering, with a portal server, a plurality of different portlets, that execute on a client, to determine, by the portal server, a type of data required by each of the plurality of different portlets, wherein the registering establishes a portlet context for handling data requests that are subsequently received from the portlets at the portal server for each of the plurality of different portlets, and wherein the plurality of different portlets are organized into a common data set.

18. A portal server including a non-transitory machine readable storage medium, comprising:

program code stored in the machine readable storage which when executed by the portal server provides functionality for a registration handler configured to register Web pages including a plurality of portlets, wherein the registration handler determines types of data required by each of the plurality of portlets and a frequency with which data updates of the determined types of data are needed, wherein the portlets are organized into a common data set, wherein the registration handler establishes a portlet context for handling future data requests received from the portlets at the portal server for each of the plurality of portlets, and wherein the plurality of portlets are organized into a common data set;

program code stored in the machine readable storage which when executed by the portal server provides functionality for a master handler configured to receive data update requests of the determined types from the portlets and to respond to the data update requests; and

program code stored in the machine readable storage which when executed by the portal server provides functionality for a data handler configured to repetitively obtain data of the determined types of data from data sources in accordance with data acquisition processes spawned by the master handler and executed by the data handler, wherein the data handler aggregates the data into an aggregated data set;

wherein the portal server responds to the data update requests by transmitting the aggregated data set.

19. The portal server of claim 18, further comprising:

a portal data store configured to cache data acquired from the data handler, wherein the master handler utilizes previously acquired data stored in the portal data store to directly respond to the update requests.

20. The portal server of claim 18, wherein the portal server is one of a plurality of portal servers which are clustered to provide resilient operation should one of the plurality of portal servers fail.