Portal

Organizations strive to achieve the best combination of deep customer knowledge and mindshare, product leadership, and transactional efficiency as best suits their business goals. In order to obtain these goals, organizations leverage IT systems to provide various types of information to specific audiences. The Portal composite pattern assists in the design process for a portal implementation.

The Portal composite pattern leverages various mechanisms (e.g. content management, user interface formatting and display, data aggregation) to bring together the appropriate information and existing systems to serve the goals of the business.

The Portal composite pattern below has been revised based on a more detailed analysis of the key patterns required in a portal. The figure also shows the generic use cases which would indicate the need for a Portal composite pattern.

This figure differs slightly from the original redbook (SG24-6087) because the Dec 2004 re-engineering of the Information Aggregation and Data Integration patterns changed some of the Application pattern names.

The Business and Integration patterns that we have identified as the mandatory building blocks of the Portal composite pattern are as follows:

• Access Integration pattern
• Self-Service business pattern
  • Update portal preferances and personalize portal homepage
  • Access enterprise applications and data
  • Update personal information
  • Display home page and user log-in
• Collaboration business pattern
  • Hold an impromptu e-meeting
  • Visit a team room
  • Create and manage content
• Information Aggregation business pattern
  • Submit an inquiry
  • Search for and display content
• Application Integration pattern
  • Publish content

Please note that, based on the specific requirements of your portal, the Business and Integration pattern building blocks may vary. For example, you may find that you have use for the Extended Enterprise business pattern in addition to the ones we defined, or you may find that you only need Access Integration, Collaboration and the Information Integration business pattern. Based on your specific requirements,this would then be defined as a Portal custom design

If you're not yet sure that your business problem can be solved by the functionality enabled through a Portal solution design, the Portal general guidelines page provides additional information on choosing this Business pattern. Business and IT drivers, the e-business context appropriate for this solution type, and additional solution details are discussed here.

If you've determined that the Portal composite pattern can provide an appropriate solution design for your business need, the next step is to select an Application pattern. The Portal composite pattern is composed of multiple Business and Integration patterns that can each be developed with functionality enabled through one or many specific Application patterns.

• Updated Portal composite pattern

  Updated: 12-16-2004
  The Portal composite pattern has been updated for WPS V5 and the revised Information Aggregation and Application Integration patterns.

• Feasibility:
  This material will help you determine the high-level shape of an Extended Enterprise solution, and can ensure your approach looks similar to other successful implementations. Reuse of prior approaches can be an effective way to begin most major projects. Obviously, modifications will be needed for any unique requirements of a given set of partners. This pattern provides a drill-down from high-level architecture to low-level designs and guidance.

• Risk:
  Basing new projects on prior designs and ideas helps to lower the risk of failure. Creating or inventing approaches for each project tends to result in a lower success rate. Frequently, projects begun "from scratch" simply do not work and have major exposures in such areas as security, performance, availability, undefined requirements, and cost overrun.

• Cost-benefit:
  By starting with reasonably complete architecture you can save considerable development time and can obtain assurance that the end solution will have a much higher chance of success. Actual savings will vary, but project teams have realized a 10% to 50% reduction of work effort in their design and architecture phases alone.