The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Developing JSR 168 compliant cooperative portlets

Amber Roy-Chowdhury (amberr@us.ibm.com), Senior Software Engineer, EMC

Amber Roy-Chowdhury is a Senior Software Engineer at IBM, based in Research Triangle Park, NC. He works on WebSphere Portal architecture and development. He is currently the architect and technical lead for the brokered communication framework for WebSphere Portal, known as the Property Broker. Previously, Amber has worked on lead development roles on the WebSphere Application Server and Encina Transaction Processing Monitor products. Amber holds a Ph.D. from the University of Illinois, Urbana-Champaign.

Yuping Wu (conniewu@us.ibm.com), Advisory Software Engineer, EMC

Yuping Connie Wu is an Advisory Software Engineer in IBM Software Group in Research Triangle Park, North Carolina. She works in WebSphere Portal Development, where she is responsible for the development of PropertyBroker for WebSphere Portal and for WebSphere Translation Server. Previously, she was involved in a variety of IBM software products including Web Traffic Experace, WebSphere Application Server, and WebSphere Transcoding Publisher. Connie holds an MS degree from North Carolina State University.

Summary: This article describes how to use the WebSphere Portal cooperative portlets feature in portlets, which are written to the JSR 168 standard API and run in WebSphere Portal V5.1. You learn the steps for developing standard portlets to exploit portlet cooperation, and you see the concepts illustrated in a sample application.

Date: 11 Jul 2005 (Published 01 Dec 2004)
Level: Intermediate

Activity: 3740 views
Comments:

Get the downloads

This article describes how to use the WebSphere Portal cooperative portlets feature in portlets, which are written to the JSR 168 standard API and run in WebSphere Portal V5.1. You learn the steps for developing standard portlets to exploit portlet cooperation, and you see the concepts illustrated in a sample application.

JSR 168 is a specification from the Java™ Community Process for portlet development. Version 1.0 addresses requirements such as aggregation, personalization, presentation, and security for portlets running in a portal environment. However, it does not address portlet cooperation (the capability of portlets on a page to interact by sharing information), except for making the HttpSession object available.

IBM® WebSphere® Portal V5.1 supports JSR 168, and includes a portlet run-time environment which also supports cooperative portlets. By using the programming techniques demonstrated in this article, you can exploit this extension, and your portlets will also function correctly in other portlet containers which support JSR 168. When deployed in a non-IBM, standards compliant portal server, these portlets gracefully degrade; that is, they simply do not use the cooperative portlets functionality.

Downloads