Providing artifact and configuration cohesion across disparate portal application models
First Claim
1. A system for providing artifact and configuration cohesion across disparate portal application models, comprising a memory that stores:
- an editor system for launching an editor for a portal page in a client interface, the editor being a standalone browser client-side application included in a client-side component associated with the portal page, and for passing initial configuration parameters from a portal server to the editor as a URL parameter to a new pop-up window in which the editor resides;
an artifact assimilation system for applying characteristics expressed by the portal server to the editor after the launch and for polling the portal server using a variable that is indicative of changed characteristics to be applied to the editor, the variable comprising an identifier corresponding to the editor; and
a query system for retrieving services from the portal server by the editor,wherein the system provides artifact and configuration cohesion between the portal page and the client side component after the launch without data loss, without requiring data refresh, and without round-tripping.
1 Assignment
0 Petitions
Accused Products
Abstract
Under the present invention, a client-based editor is launched (e.g., from a web server or the like) within a client interface such as a browser. Upon being launched, initial configuration parameters are passed from a portal server to the editor. The present invention also provides a “communications tunnel” between the editor and the portal server in the form of a portlet interface on the web server. This is so that any characteristics expressed by the portal server (e.g., changes to the initial configuration parameters) can be pushed to the editor. Moreover, the portlet interface allows the editor to query the portal server to obtain any needed services (e.g. a spreadsheet computation).
-
Citations
22 Claims
-
1. A system for providing artifact and configuration cohesion across disparate portal application models, comprising a memory that stores:
-
an editor system for launching an editor for a portal page in a client interface, the editor being a standalone browser client-side application included in a client-side component associated with the portal page, and for passing initial configuration parameters from a portal server to the editor as a URL parameter to a new pop-up window in which the editor resides; an artifact assimilation system for applying characteristics expressed by the portal server to the editor after the launch and for polling the portal server using a variable that is indicative of changed characteristics to be applied to the editor, the variable comprising an identifier corresponding to the editor; and a query system for retrieving services from the portal server by the editor, wherein the system provides artifact and configuration cohesion between the portal page and the client side component after the launch without data loss, without requiring data refresh, and without round-tripping. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A method for providing artifact and configuration cohesion across disparate portal application models, the method implemented by a computer and comprising:
-
passing initial configuration parameters to an editor from a portal server as a URL parameter to a new pop-up window in which the editor resides, the editor being a standalone browser client-side application that is launched for the portal page in a client interface, the editor being included in a client-side component associated with the portal page; applying characteristics expressed by the portal server to the editor after the launch; polling the portal server using a variable that is indicative of changed characteristics to be applied to the editor, the variable comprising an identifier corresponding to the editor; and retrieving services from the portal server by the editor, wherein the method provides artifact and configuration cohesion between the portal page and the client side component after the launch without data loss, without requiring data refresh, and without round-tripping. - View Dependent Claims (8, 9, 10, 11, 18, 19, 20, 21, 22)
-
-
12. A program product stored on a tangible storage medium for providing artifact and configuration cohesion across disparate portal application models, which when executed comprises:
-
program code for passing initial configuration parameters from a portal server as a URL parameter to a new pop-up window in which an editor resides, the editor being a standalone browser client-side application that is launched for the portal page in a client interface, the editor being included in a client-side component associated with the portal page; program code for applying characteristics expressed by the portal server to the editor after the launch; program code for polling the portal server using a variable that is indicative of changed characteristics to be applied to the editor, the variable comprising an identifier corresponding to the editor; and program code for retrieving services from the portal server by the editor, wherein the program product provides artifact and configuration cohesion between the portal page and the client side component after the launch without data loss, without requiring data refresh, and without round-tripping. - View Dependent Claims (13, 14, 15, 16)
-
-
17. A system for deploying an application for providing artifact and configuration cohesion across disparate portal application models, comprising:
-
a computer infrastructure comprising memory storing instructions, the instructions operable to; pass initial configuration parameters to an editor from a portal server as a URL parameter to a new pop-up window in which the editor resides, the editor being a standalone browser client-side application that is launched for the portal page in a client interface, the editor being included in a client-side component associated with the portal page; apply characteristics expressed by the portal server to the editor after the launch; poll the portal server using a variable that is indicative of changed characteristics to be applied to the editor, the variable comprising an identifier corresponding to the editor; and retrieve services from the portal server by the editor, wherein the system provides artifact and configuration cohesion between the portal page and the client side component after the launch without data loss, without requiring data refresh, and without round-tripping.
-
Specification