Skip to main content

Front-end Integration::Personalized Delivery application pattern: Runtime patterns

Overview

As with single sign-on, personalization delivery can also take various implementation forms.

Participatory personalization

Personalized Delivery::Participatory personalization::Runtime pattern Web Application Server Web Application Server Personalization Server Design Last Updated: 03-2002
(Click a node to get a detailed explanation.)

Participatory personalization allows the user to design the content and the layout of the content that they see by explicitly choosing from a selection of options. The personalization service stores the customization results in a profile record.

Participatory personalization allows the user to design the content and the layout of the content that they see by explicitly choosing from a selection of options. The personalization service stores the customization results in a profile record.

Predictive personalization

Personalized Delivery application pattern::Predictive personalization::Runtime pattern Web Application Server Web Application Server Inference Engine Design Last Updated: 03-2002
(Click a node to get a detailed explanation.)

Predictive personalization uses an inference engine to personalize content based on the past history (click stream) of user (all users) behavior. The inference engine may reference a user profile for demographic information to categorize users.

The benefits of a predictive personalization solution include:

  • Enables the enterprise to control access to applications and information while empowering users.
  • Enables the enterprise to make users aware of opportunities of which they may not otherwise be aware.
  • Enables the enterprise to monitor users' behavior and habits automatically.

The disadvantages to this solution include:

  • Personalization techniques can be perceived as intrusive.
  • Predictive technologies can be difficult to apply effectively without careful identification of goals and measurement.
  • Will likely require extensive analysis and preparation to be effective.
  • Can be relatively complex for an organization new to personalization techniques.

Prescriptive pesonalization

Personalized Delivery application pattern::Prescriptive pesonalization::Runtime pattern Web Application Server Web Application Server Rules Engine Design Last Updated: 03-2002
(Click a node to get a detailed explanation.)

Prescriptive personalization provides a rules engine that delivers targeted content based on business rules defined by the enterprise. The personalization rules are based on data being requested by the user and the user's profile information.

The benefits of this solution are that it enables the enterprise to have fine-grained control over access to applications and data while improving users' efficiency, and facilitate a better end-user experience. The main disadvantage is that proper implementation can be challenging if business rules are complex.

Next, review Combined Runtime patterns that merge functionality from the Single Sign-On and Personalized Delivery application patterns.

Close [x]

Web Application Server

A Web application server node is an application server that includes an HTTP server (also known as a Web server) and is typically designed for access by HTTP clients and to host both presentation and business logic.

The Web application server node is a functional extension of the informational (publishing-based) Web server. It provides the technology platform and contains the components to support access to both public and user specific information by users employing Web browser technology. For the latter, the node provides robust services to allow users to communicate with shared applications and databases. In this way, it acts as an interface to business functions, such as banking, lending, and HR systems.

The node can contain these data types:

  • HTML text pages, images, multimedia content to be downloaded to the client browser
  • JavaServer Pages
  • Application program libraries, such as Java applets for dynamic download to client Workstations

See Also

Additional Resources

  • (in English) ESS

Close [x]

Rules Engine

The rules engine delivers targeted content based on business rules defined by the enterprise. The personalization rules are based on data being requested by the user and the user's profile information.

Close [x]

Inference Engine

The inference engine is used to personalize content based on the past history (click stream) of user (all users) behavior. The inference engine may reference a user profile for demographic information to categorize users.

Close [x]

Personalization Server (Rules Engine)

The personalization server node works with the presentation server node to customize the presentation with data that matches a user’s interest. The personalization server identifies the type or class of the user based on information available about the user. Based on this classification, data taken from a content datastore either in the Personalization tier or from back-end sources is selected for presentation to the user. It provides the mapping function of user classification to content data.

The personalization server contains the rules that determine what types of user’s can have access to certain type of information. These are also referred to as access control rules and are directly related to business rules and processes. This is referred to as the Personalized Delivery::Prescriptive runtime pattern. The personalization server also allows the user to design the content and the layout of the content that they see by explicitly choosing from a selection of options. This is referred to as the Personalized Delivery::Participatory runtime pattern. You can use either or both of these patterns for the Portal composite pattern.