Portal composite pattern::Runtime pattern and
Self-Service::Directly Integrated Single-Channel application pattern

Overview
Runtime patterns define functional nodes that underpin an Application pattern. The Application pattern exists as an abstract representation of application functions, whereas the Runtime pattern is a middleware representation of the functions that must be performed, the network structure to be used, and the systems management features.

A portal implementation leverages the concept of personalization, multi-device type access, a presentation rendering mechanism, and a business rules engine. These are combined with the ability to search and index content (of various types and formats), provide collaboration, and manage content via a workflow to provide both content aggregation and a collaborative environment.

The Portal composite runtime pattern represents a starting point for most portal implementations, providing a way to identify those functional areas that will likely need to be addressed when considering this type of implementation.

Consequently, the Portal composite runtime pattern represents a preliminary step towards an operational architecture that can be implemented in a target environment to provide secure data aggregation, multi-client access and collaboration.

Self-Service::Directly Integrated Single-Channel::Runtime pattern=Variation 1
This Runtime pattern uses one Web server and one application server, effectively splitting the function of a Web application server across two machines. In this case the application sever resides in the internal network to provide it with more security. The application server node will run both presentation and business logic. The Web server remains in the DMZ. A Web server redirector is used to forward the requests from the Web server to the application server.

Applying it to the Portal composite runtime pattern
This more closely resembles the architectural rigor of an idealized portal implementation where core nodes are separated by secure layers. Thus, this most closely adheres to the approach described in the Portal composite runtime pattern where each major node is separated so that the resulting architecture is more component based and thus each functional node can be separately secured and thus isolated in the case of system failure, component replacement, or when performing functional system enhancements. The following figure shows the Directly Integrated Single Channel overlaid on the Portal composite runtime pattern.

Directly Integrated Single Channel and Portal composite runtime pattern
(Click a node to get a detailed explanation.)
Design Last Updated: 12-07-2004

The Portal Server node supports the Presentation tier in the Application pattern. This Presentation tier represents the Portal view. The Application Server node supports the application tier in the Application pattern. This Application tier represents the Portal application.

What's Next
If you would like to review additional Application patterns, and their corresponding Runtime patterns, return to the Portal: Select Application pattern page.

For a mapping of products that support the Runtime nodes shown above, review the Portal product mapping.