Caching data in JSR 168 portlets with WebSphere Portal V5.1

From the developerWorks archives

Stefan Hepper and Stephan Hesmer

Date archived: January 3, 2017 | First published: August 31, 2005

Learn how you can cache data in JSR 168 portlets in order to avoid unnecessary backend requests. First, you see how to leverage the IBM WebSphere Application Server dynacache infrastructure to store cached data. Next, you see how to generate cache keys for data which is shared across all components in the Web application and which has a session scope. Then, you look at a second cache key generation technique to address the need for caching data that is private to a portlet window. An example bookmark portlet illustrates both caching techniques. This articles is intended for Java portlet programmers who are already familiar with the Java™ portlet API, and can create and deploy portlets on WebSphere Portal. 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.

ArticleTitle=Caching data in JSR 168 portlets with WebSphere Portal V5.1