Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Community-based adaptation of producer-hosted applications

IP.com Disclosure Number: IPCOM000188536D
Original Publication Date: 2009-Oct-13
Included in the Prior Art Database: 2009-Oct-13
Document File: 3 page(s) / 30K

Publishing Venue

IBM

Abstract

Community - based adaptation of producer - hosted applications. This disclosure describes how changes to modifiable remote applications are managed and maintained in remote portal producers. In addition to that, it demonstrates how modification which are performed by a lionĀ“s share of the community can be propagated back to the users of this application and thus use the wisdom of the crowds to enhance and extend remote application in the way most cherished by the end - users.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 35% of the total text.

Page 1 of 3

Community-based adaptation of producer-hosted applications

A typical portal provides access to user specific information, applications and processes using local and remote information sources. It combines the aggregated applications and provides a unified presentation layer which is usually made up by portlets - components rendering markup fragments and plugged into the portal infrastructure - described in the Portlet Specification.

Portlets may be locally executed or integrated from remote sites which is described by a standard called WSRP (Web Services for Remote Portlets). Thereby WSRP Producer Portals provide remote access to so - called WSRP Portlets which are consumed by WSRP Consumer Portals. This technique allows for the integration of portlets across borders of different vendors and isolation of execution of alien code (portlets). Disadvantages of remote portlets include:

No context is shared between different remote portlets. Even though WSRP 2.0 allows sharing of rendering state information between portlets it does not allow remote portlets to share application logic
Remote portlets are unaware of the portal or the portal page they are aggregated in

Another important technology in the field of web portals is the concept of composite portal applications. Composite applications allow the composition of applications from multiple functional elements such as business components (like EJB's), static content as well as portal artefacts such as pages and portlets used to visualize the application. Among those, information and application context can be shared. An application template defines the various components, pages and portlets as well as wired defined between them that make up a such a composite application.

The existing prior art, British Patent Application, Appl.No.0905249.9, introduces a concept called remote dynamic applications that combines the two concepts (WSRP and Composite Applications) described above:

A remote application is provided by an application provider portal and consumed by an application consumer portal. It allows a consumer portal to dynamically instantiate and integrate remote composite portal applications from producer portals into the consumer portal system while keeping the application code isolated on the remote portal system. The communication between the consumer portal and the portal providing the remote portal application could be implemented using web services technologies for example by leveraging the extension mechanisms of the WSRP protocol.

The application template of a remote dynamic portal application additionally comprises information about the web services interface which is needed to communicate the application metadata from an application producer portal to an application consumer portal.

During the instantiation of a remote application the consumer portal reads the application template and created all local artefacts needed to integrate...