Java201.com

• Sharing Data among Federated Portals: Using WebLogic Portal, Tangosol Coherence and WSRP by Jason Howes   - [Clicks: 61]
  Learn how to combine BEA WebLogic Portal's WSRP extensions with Tangosol's Coherence product to efficiently share data between a Producer and its Consumers.
  http://dev2dev.bea.com/pub/a/2005/11/federated-portal-cache.html - Nov, 2005
• Introduction to Web Services for Remote Portlets by Bryan Castle   - [Clicks: 136]
  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. To the end-user, it appears that the portlet is running locally within their portal, but in reality the portlet resides in a remotely-running portlet container, and interaction occurs through the exchange of SOAP messages. Leveraging WSRP within a Service-Oriented Architecture provides a powerful combination whereby presentation-oriented portlet applications can be discovered and reused without engaging in additional development or deployment activities.
  http://www-128.ibm.com/developerworks/webservices/library/ws-wsrp/ - Apr, 2005
• Inside WSRP by Subbu Allamaraju   - [Clicks: 182]
  BEA WebLogic Portal 8.1 lets portals consume remote portlets by using the Web Services for Remote Portlets (WSRP) protocol. In most cases, portlets originally built and deployed for use by local portals will function the same when you move those portlets to remote WSRP Producers. WebLogic Portal and its WSRP Consumer and WSRP Producer capabilities are designed to shield portlets from the location of the portal. However in some cases, you may find that certain portlets behave differently or incorrectly. The most common cause of such behavior is implicit or explicit assumptions such portlets might have made about the location of the portal. In this article, I discuss some of the most common assumptions, and why such assumptions can interfere with the WSRP protocol in undesirable ways. My goal is to highlight best practices that you can employ to make portlets WSRP-friendly without necessarily compromising functionality.
  http://dev2dev.com/products/wlportal81/articles/inside_wsrp.jsp - Mar, 2005
• Portal Standards by Sue Vickers   - [Clicks: 289]
  As demonstrated by the emergence of multiple portal initiatives within organizations today, the benefits of enterprise portals are clearly understood. It's common to see several enterprise portal platforms deployed throughout an organization. However, many companies are attempting to standardize on one portal framework but are challenged with integrating disparate portal instances.
  [Includes source code]
  http://sys-con.com/story/?storyid=47686&DE=1 - Jan, 2005
• Plug-and-Play Remote Portlets by Kulvir Singh Bhogal, Andrew Sweet   - [Clicks: 64]
  In this article, we will further our study of portlet portability. In particular, we will focus our discussion on the Web services for remote portals (WSRP) standard. The vision of WSRP is to allow portlets to be exposed as Web services. The resulting Web service will be user-facing and interactive. Unlike traditional data-oriented Web services, a WSRP-compliant Web service will carry within its payload the presentation logic necessary to display and interact with the portlet; consequently, portlets can be readily plugged into remote portals.
  http://sys-con.com/story/?storyid=47658&DE=1 - Jan, 2005

[Top]

• Developing Portal Applications by Nils Gilman   - [Clicks: 76]
  Nils Gilman explains what the portal market is all about, how it evolved, what portals are, and future key directions such as the possibility of federated architectures with Web Services Remote Portlets (WSRP). Nils explains the two main differentiators of BEA's own WebLogic Portal and provides clear insight into why to use a portal product versus rolling out your own.
  http://dev2dev.bea.com/trainingevents/dev2devlive/ngilman.jsp - Jan, 2005

[Top]

• Creating a JSR 168 portlet for use by diverse portals using Web Services for Remote Portlets by Ron Lynn, Karl Bishop   - [Clicks: 139]
  In this two-part tutorial, Ron and Karl playfully guide you along the path of creating a JSR 168-compliant portlet which can be consumed by multiple portals using Web Services for Remote Portlets (WSRP). In part 1, you choose a path for creating the portlet: fork 1, uses the Rational development environment; fork 2 (for command-line die-hards), uses hand-coding in your favorite editor. You then enable the portlet to access a database using SQL. In part 2 (a future installment), you will make the portlet available to other portals using WSRP. This part will also demonstrate accessing the portlet in a portal running under IBM WebSphere Portal V5.1.
  [Formats: pdf]
  http://www-128.ibm.com/developerworks/websphere/library/tutorials/0510_lynn/0510_lynn_reg.html - Oct, 2005

[Top]