180 A Portal Composite Pattern Using WebSphere Portal V5
This chapter focuses on the design approaches for portal solutions. We try to
cover some of the differences between traditional Web applications and portal
solutions from a design standpoint. We provide guidelines on how to design
portlet applications in WebSphere Portal V5 using different types of frameworks,
and discuss best practices for portlet development. We also include information
concerning performance, both in regard to portlet design and development, and
also in regard to response time tracing within a portal solution. In addition, we
show you how to add collaborative functionality to your portlet applications and
introduce you to an approach to integrate and reuse existing business
applications within the Portal.
What is not covered in this chapter is how to create portlets, generate war files,
install and update portlets, and so forth. For a discussion of all basic and
standard functionalities of WebSphere Portal, refer to the WebSphere Portal
InfoCenter and the WebSphere Portal Handbook.
WebSphere Portal InfoCenter:
WebSphere Portal Handbook: IBM WebSphere Portal for Multiplatforms V5
Another topic not covered here is system and resource management done by, for
example, the WebSphere Portal administration interface, WebSphere Resource
Analyzer or Tivoli Web Site Analyzer. For information on how to utilize these
products, see IBM WebSphere V5.0 Performance, Scalability, and High
Availability: WebSphere Handbook Series, SG24-6198. Also refer to IBM
WebSphere Portal V5 A Guide for Portlet Application Development, SG24-6076.
8.2 WebSphere Portal
WebSphere Portal is quickly becoming a standard infrastructure platform for
building enterprise-class applications. But it provides much more than just this;
WebSphere Portal delivers integrated content and applications, plus a unified,
Thus we can look at WebSphere Portal from two different angles. On one hand it
is a development platform for new applications, and on the other it enables the
integration of existing applications and processes. In this paper we reflect on
both aspects and discuss patterns and strategies that will help you build
successful Portlet applications.