Portal Federation with WebLogic Portal WRSP: Advanced IPC Techniques, Page 3
The advantage to this is if you want to have the listening portlet on a different page and have the user taken to that page as part of the interaction (a handy user experience design to keep from cluttering the page). Although in a file-based portal you can create this type of interaction by directly calling the page where the listening portlet resides, in a WSRP interaction you don't even know where that page is. A direct link won't work with WSRP both because it is administered in a separate portal application and because the instance ID of all WSRP portlets, pages, and books are generated at the time they are integrated into the consumer portal (I am purposely avoiding the debate of whether that should be done even without WSRP, in case you were wondering). Instead of generating links in code, you add a step to your event handling that will dynamically load the page in which the listening portlet resides. This is achieved by going to the portlet properties as you did before and adding the Activate Page action (this time with the screen shot because one picture is adequate to explain):
Figure 1: Adding Activate Page to Event Handling
There are many ways to share data between portlets. Oftentimes, portal developers never explore the IPC tools provided by the WebLogic Portal, either because they haven't needed to or did not have the time explore the documentation thoroughly enough. Those with more time on their hands have been able to discover that there are many robust APIs that facilitate developing a loosely coupled portal application. Even though the advantages to doing so are very clear when demonstrated in the WSRP context, they are of benefit even without WSRP.
There are other approaches to achieving the same results, as demonstrated in this series. Many of those approaches are provided in the documentation. The goal here was to share approaches that are not as easily found and provide some real-world context around the value of learning the advanced features of WLP. Although you will certainly be able to get by with what you have covered, you will be able to make the best choice for your project by reviewing the documentation in addition to these articles.
About the Author
Scott Nelson is a Senior Principal Consultant who strives to leverage portal technologies to provide businesses an improved ROI realized from a better user experience and reduced developer maintenance. In other words, he likes to do things better, faster, and cheaper.
Page 3 of 3