Use widgets
The page builder theme architecture allows the portal to render both iWidgets and portlets alongside on the same portal pages.
Manage the widgets rendered on pages is similar to managing portlets. For details about managing widgets refer to the following topics.
The portal supports only iWidgets written to comply with the iWidget specification 2.1.
When you use widgets, refer to the hints and tips about using widgets given under the topic about Hints and tips for the Page Builder theme and widgets.
How iWidgets are represented in the portal model
For easy handling of iWidgets WebSphere Portal provides a dedicated IWidget Wrapper portlet. This portlet maps the iWidget concept into the portal administration model.
Register iWidgets for use with the Page Builder theme
To make the portal aware of available iWidgets, you register the iWidget definitions in the portal by telling the portal the location from where it can load the iWidget definition XML.
Reusing registered iWidgets
When you register an iWidget in the portal, a copy or clone of the IWidgetWrapper portlet is created to map the iWidget model to the portal model. The new portlet carries the title and the description as defined in the iWidget definition: this way you can locate and manage it as other portlets in the portal.
Customize iWidget attributes
When you register an iWidget in the portal, most sections of the iWidget definition and microformat are stored in the portal model as portlet preferences of a copy or clone of the IWidgetWrapper portlet.
Update iWidget attributes when refreshing iWidget definitions
In general, when you refresh an iWidget definition, the previous iWidget definition data stored in the portal model of the portal are replaced. The exception to this rule are iWidget attributes, that is items of the attributes item set, which are defined in the iWidget definition.
Design a site using Page Builder themes and skins
Related reference
Hints and tips for the Page Builder theme and widgets
|