Exploiting the WebSphere Portal programming model, Part 4: Making your portal dynamic and context sensitive

From the developerWorks archives

Jan Engehausen, Stefan Hepper, Andreas Nauerz, and Juergen Schaeck

Date archived: January 3, 2017 | Last updated: September 27, 2006|First published: August 02, 2006

This final part describes how to exploit the IBM® WebSphere® Portal V5.1.0.1 programming model to make your portals more dynamic and context sensitive. By using the Model SPI, you can access the different sub-models within the overall portal model, and then base your markup rendering on these models. You see an example that accesses page meta data, so that the administrator can set a context for this page that is then leveraged by the portlets on that page. Next, you see how to use the Dynamic UI Manager API to launch temporary, dynamic pages, and to set a specific context for a page. A flight booking application demonstrates the Dynamic UI Manager API, by creating dynamic pages for the different steps in the booking process.

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=Exploiting the WebSphere Portal programming model: Part 4: Making your portal dynamic and context sensitive