Exploiting the WebSphere Application Server V6.1 portlet container, Part 4. Migrating portlets between WebSphere Application Server and WebSphere Portal

From the developerWorks archives

Birga Rick and Stephan Hesmer

Date archived: January 3, 2017 | First published: November 01, 2006

This article series examines the JSR 168 portlet container available in IBM WebSphere Application Server V6.1 and differentiates its use from IBM WebSphere Portal.

Part 1 introduced the portlet container and described how to install and access a portlet, and how to use URL Addressability.

Part 2 illustrated some extended capabilities of the container including how to render a portlet within a window frame, display multiple portlets, get information about deployed portlets, and change the default portlet behaviour.

Part 3 showed how to use performance monitoring and measurement techniques to analyze performance bottlenecks with the portlet container.

Part 4 compares the extended portlet programming model of WebSphere Portal to portlet support in WebSphere Application Server so that you can determine what if anything you need to change if you decide to migrate your portlets between the two environments. You can download the sample portlet, and then deploy and run it in both platforms.

This series is for Java™ programmers, portlet programmers, and Web administrators who are familiar with the Java Portlet API. See Resources for links to information that can help you gain those skills.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=170279
ArticleTitle=Exploiting the WebSphere Application Server V6.1 portlet container: Part 4. Migrating portlets between WebSphere Application Server and WebSphere Portal
publish-date=11012006