Access Integration::Single Sign-on and Personalized Delivery application patterns: Combined Runtime patterns

It is possible to customize an Access Integration solution to take advantage of two Application patterns: Single Sign-On and Personalized Delivery. The two Runtime patterns for this design documented below, combine the nodes required to fulfill both functions.

Combination Runtime pattern variation 1
(Click a node to get a detailed explanation.)
Design Last Updated: 3-2002

The first combined Runtime pattern shown above is used when the situation calls for Web Single Sign-On and rules-based personalization. Both Application patterns are shown as overlays here to illustrate the location of the Application pattern tiers in the Runtime pattern. In addition, the Web server function was separated from the primary presentation and application server functions for added security.

The Web server redirector node allows the business logic to be located in the internal network, giving it the protection of both firewalls. The Web server redirector performs limited functions. It serves static HTML pages, forwarding the rest of the requests to the Web presentation server. There is limited security at this node. Webseal could be used to enhance this.

The Web presentation server, together with the Directory server, provides Single Sign-On capability, allowing users to sign on one time in order to access multiple applications. It runs the servlets and JSPs necessary for presenting the data to the user. It interacts with the personalization server to build customized output for users based on identity or role.

The personalization server classifies the users and determines specific content suitable for presentation to the user.

Each node in the internal network uses the directory and security services node as a central location for security information, making the single sign-on possible.

Combination Runtime pattern variation 2
(Click a node to get a detailed explanation.)
Design Last Updated: 3-2002

The second combined Runtime pattern, shown above, is used when the situation calls for extended single sign-on capabilities and rules-based personalization. This Runtime pattern uses the same runtime nodes as the previous combination, but a back-end application server has been added. The back-end server participates in using single sign-on, either through credential mapping or credential propagation.

What's Next
Next, review Combined Product mappings for the Single Sign-On and Personalized Delivery application patterns.