Integration of Existing Grid Tools in Sakai VRE

Wang

Concurrency and Computation

2007

SUMMARYWSRP (Web Services for Remote Portlets) is a promising Web services specification used to standardize presentation-based access to remote Web portal content. In combination with the JSR-168 standard, portlet developers are freed of doing the hard work in publishing their portlets to a remote portal: ideally it is the duty of a portal framework to publish the portlets it manages. Code reusability can now be achieved with JSR-168 while 'deploy once' is achieved through WSRP. In this paper the WSRP support provided by selected open-source portal frameworks including the eXo platform, Liferay, StringBeans and uPortal are reported. WSRP4J, which is not a portal framework but a reference implementation of the WSRP 1.0 specification, is also discussed. Based on our test results, a WSRP consumer has been developed for Sakai, a collaboration and learning environment, based on the WSRP4J consumer, which enables Sakai to consume JSR-168 portlets.

“…For reasons of brevity, details are not given here but can be found in [8]. A screenshot of a remote LdapBrowser portlet running inside Sakai is shown in Figure 3.…”

Section: Wsrp Consumer For Sakaimentioning

confidence: 99%

“…Based on our tests above, the ProxyPortlet (WSRP4J WSRP consumer) has been converted to a Sakai WSRP consumer tool. For reasons of brevity, details are not given here but can be found in [8]. A screenshot of a remote LdapBrowser portlet running inside Sakai is shown in Figure 3.…”

Section: Wsrp Consumer For Sakaimentioning

confidence: 99%

Investigation of WSRP support in selected open‐source portal frameworks

Wang

Concurrency and Computation

2007

“…After receiving markup fragments from the Producer, the Consumer renders the markup for the user. Owing to the length limit, details of interaction between Consumer and Producer are not given here but can be found in [15]. Figure 5 shows the interface to the WSRP search engine.…”

Section: System Workflowmentioning

confidence: 99%

Plug‐and‐play remote portlet publishing

Wang

Concurrency and Computation

et al. 2007

SUMMARYWeb Services for Remote Portlets (WSRP) is gaining attention among portal developers and vendors to enable easy development, increased richness in functionality, pluggability, and flexibility of deployment. Whilst currently not supporting all WSRP functionalities, open-source portal frameworks could in future use WSRP Consumers to access remote portlets found from a WSRP Producer registry service. This implies that we need a central registry for the remote portlets and a more expressive WSRP Consumer interface to implement the remote portlet functions. This paper reports on an investigation into a new system architecture, which includes a Web Services repository, registry, and client interface. The Web Services repository holds portlets as remote resource producers. A new data structure for expressing remote portlets is found and published by populating a Universal Description, Discovery and Integration (UDDI) registry. A remote portlet publish and search engine for UDDI has also been developed. Finally, a remote portlet client interface was developed as a Web application. The client interface supports remote portlet features, as well as window status and mode functions.

“…Thus any application equipped with a consumer (Web service client) is able to consume these portlets without local deployment. For detailed information about this approach, refer to [23].…”

Section: Bringing Web 20 Elements In Grid Portals Vs Bringing Grid mentioning

confidence: 99%

Bringing AJAX to grid portals

2007 International Symposium on Collaborative Technologies and Systems

2007

Self Cite

Grid portals provide researchers the power of Grid through Web browsers. Today these portals are mostly Java-based and therefore the Java Portlet Specification 1.0 (JSR 168) has been widely adopted. Acting as Web components, portlets wrap relatively independent individual functionalities like Grid proxy credential management and job submission. These components can then be aggregated for construction of portal pages. One of the key issues Grid portals are facing now is that they are not as attractive as desktop applications because they lack instant response and complex visual effects. To address this, we are going to investigate Asynchronous JavaScript and XML (AJAX). AJAX is becoming increasingly popular in the Web development community, in particular, it is one of the key aspects of today's Web 2.0. In this paper, we will discuss how Grid portals can benefit from AJAX so that more end-users could be attracted.