Exploiting the WebSphere Application Server V6.1 portlet container, Part 3: Administering the portlet container

From the developerWorks archives

Stephan Hesmer and Birga Rick

Date archived: January 3, 2017 | First published: August 30, 2006

This article series examines the JSR 168 portlet container available in IBM WebSphere Application Server V6.1 and differentiates its use from 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.

In this part, you learn how to administer the JSR 168 portlet container in WebSphere Application Server. You see how to configure and use portlet caching capabilities, performance metrics, and the extended deployment descriptor. You can download example code that accompanies this series and illustrates many of features of the WebSphere Application Server V6.1 portlet container.

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=156819
ArticleTitle=Exploiting the WebSphere Application Server V6.1 portlet container: Part 3: Administering the portlet container
publish-date=08302006