Publishing JSR 168 Portlets as Remote Portlets With WSRP

Java Specification Request (JSR) 168: Portlet Specification enables interoperability among portlets and portals by defining the APIs that standardize preferences, security, and other configurations. By taking advantage of the Web Services for Remote Portlets (WSRP) capability in Sun Java System Portal Server 7 (henceforth, Portal Server), you can publish a locally deployed JSR 168 portlet as a remote one and consume or display other remotely published portlets in Portal Server. This article describes the publication procedure with an example portlet and offers troubleshooting tips.

Time To Discusss WSRP...

I thought I’d start this next wave of postings with the subject I’ve avoided the longest - WSRP. This one will be a little long…

JSR 168, WSRP, Portlets and Enterprise Portal

The JSR 168, WSRP, Portlets and Enterprise Portal blog. You will find everything related to portlets, enterprise portal servers, WSRP and JSR 168.

Introduction to Web Services for Remote Portlets

Use WSRP in a Service-Oriented Architecture. Get an introduction to Web Services for Remote Portlets (WSRP), a specification which defines how to leverage SOAP-based Web services that generate mark-up fragments within a portal application. By defining a set of common interfaces, WSRP allows portals to display remotely-running portlets inside their pages without requiring any additional programming by the portal developers.