+

Search Tips   |   Advanced Search


Web 2.0 user interface features


Overview

Web 2.0 provides...


Web 2.0 portal theme with support for client side aggregation:

The portal can use client side aggregation (CSA) instead of server side aggregation (SSA). This has the following advantages:

Note that the Web 2.0 theme is deprecated in Portal 7, replaced by a new Page Builder 2 theme, which handles CSA/SSA more seamlessly and does not require XSLT knowledge.

WAI is also deprecated in WebSphere Portal v7.


Client side portlet programming model:

You can use the client side programming model for your portlets. You can do everything with the client side programming model that you can do with the server side portlet programming model. Additionally, the client side programming model has the following advantages:


Live text:

Live text provides elements embedded in portal pages that become active in the browser and are enhanced with additional functionality by JavaScript libraries.

For example, if you include portal user IDs in your portlet output and mark them as live text, users can click on these IDs in the browser and see a person info card or a context menu that allows them to send a mail to the person. Live text has the following advantages:


REST services:


Controller SPI:

The Controller SPI is a new public portal interface. It is not directly related to the new type of Web user experience, but it allows you to perform certain administrative tasks more easily.


Terminology

These are terms that are used in the documentation for the new features:

Client Side Aggregation (CSA)

Aggregation based on JavaScript and XSLT transformations that are executed on the client.

Server Side Aggregation (SSA)

Aggregation based on JSPs that are executed on the Server. This is the "old" portal aggregation model; this still works as before.

Pure Server Side Portlet

Normal server side portlet that uses Java and JSPs; it usually uses no JavaScript. Portlets that are written to the client side model use no or few JSPs.

AJAX Portlet

Normal server side portlet that uses lots of JavaScript and AJAX technologies and less Java & JSPs.

Differential Page Rendering (DPR)

Server side rendering model that is used by the Web 2.0 theme. The concept of DPR is to render only those parts of a portal page that were affected by the a user interaction.

For example, if a user interacts with a single self-contained portlet that runs in the Web 2.0 theme, the portal refreshes only this portlet rather than the entire portal page.

REST

Representational State Transfer.


Parent topic:

Designing a portal site