IBM BS029ML Self Help Guide - Page 24

2.1 Building the right Portal architecture WebSphere Portal Server architectures come in many shapes and forms. This is in part attributed to the demands of modern day e-business, where the need to establish a robust, open, scalable, and strategic infrastructure platform to set the standard for system reuse and interoperability exists. WebSphere Portal Server achieves all of these goals through the establishment of an extensible framework of services, and then, by being deployed as an Enterprise Application on top of either WebSphere Application Server or WebSphere Process Server (certain restrictions apply). Leveraging upon the strengths of the underlying WebSphere technology make it possible for WebSphere Portal Server to support everything from the small workgroup (WebSphere Portal Express) to the high-volume enterprise, to the geographically distributed Portal. Indeed, IBM recognizes that "one size does not fit all" when it comes to planning and architecting a Portal solution. To the experienced Portal Solution team, functional and operation aspects need to be considered with equal rigor and importance when implementing a successful Portal solution. It is acknowledged that the principles of good architectural design and development go hand in hand with the adoption of a suitable methodology. Indeed, the IBM Global Services Method (GS-Method or GSM) has been the basis for many successful WebSphere Portal Server deployments. However, the merits and application of such methodologies are beyond the scope of this particular Redpaper. 2.1.1 Addressing functionality Functionality remains the main driving force behind many of the systems and solutions that we use each day. Without functionality, a system or solution fast becomes obsolete. Portals are no exception to this rule. Although no specific functional requirements are documented within this chapter, as attempting to do so would prove futile given the uniqueness of many WebSphere Portal Server deployments, one can dramatically improve the success factor of a deployment by accurately capturing conditions such as the following: What the specific applications, services, or products are that a WebSphere Portal Server implementation should support. What the high level capabilities are that an implementation should have, for example, security, user collaboration, user interface, and so on. What the general use cases are that best describe the business functionality required from the implementation. 2.1.2 Addressing integration Integration is not a trivial issue and requires time and effort to accurately establish the most appropriate solution. A good WebSphere Portal Server architecture, therefore, addresses integration as early on in a project as possible. WebSphere Portal Server integration can be loosely classified into the following three categories. 10 IBM WebSphere Portal V6 Self Help Guide