Choosing builders that integrate IBM WebSphere Portal featuresAdded by IBM on August 31, 2010 | Version 1 (Original)
|Several builders help you integrate WebSphere Portal features.
Several builders help you integrate WebSphere Portal features.
Table 1. Builders to integrate WebSphere Portal features
|Task||Builder you should use|
|Add portlet-to-portlet communication such as Click-To-Action or Portlet Wiring.||See: Using actions and events.|
|Integrate people awareness or SameTime chat capabilities into a portlet.||The People Awareness builder can make names people-aware. It interacts with the Lotus® Collaborative Components available within WebSphere Portal.|
|Link to another portal page from a portlet.||The WebSphere Portal Link builder can link to another portlet or page in WebSphere Portal. The object you link to is referenced with a WebSphere Portal resource identifier.|
|Add custom edit or configure mode options for business users or administrators.||To enable Edit or Configure support, you must first profile the builder inputs that you want to make available for runtime configuration. Then specify the desired Edit/Configure behavior in WebSphere Portal in the Portlet Adapter builder. |
To create a custom UI for Edit or Configure, first create a customizer model that includes the Portlet Customizer builder. In the Portlet Adapter builder of the portlet model, specify your customizer model as the custom model choice.
|Create different variations of an application for different WebSphere Portal groups or roles.||Follow these steps:
- Profile the builder inputs that you want to vary.
- Create a named profile corresponding to each of the Portal groups or roles, and set the profile values as desired for each profile.
- In the Profile Set editor, in the Select Handler tab, choose WPS Group Segment Handler as the Profile Selection Handler.
- From the Manage Profiles tab of the Profile Set Editor, in the Advanced section of the Edit Profile dialog, select Add External and enter the name of the Portal group, Do this for each profile.
- In the Portlet Adapter builder for your model, select Do not expose in Portal tools for your profile set.
|Make a model available as a portlet. ||Any model containing the Portlet Adapter builder becomes available as a portlet. When you first portlet-enable a model this way, you must save the model file, then use the Portal Server WAR -> Build Portlet WAR command, to update the portlet WAR in WebSphere Portal server. |
|Implement single sign-on by storing user credentials in WebSphere Portal credential vault.||The WebSphere Portal Credential builder provides methods for saving and retrieving credentials (user names and passwords) from the WebSphere Portal credential vault.|
|Have a portlet to operate on data in the WebSphere Portal Content Model.||Use the Portal Document Manager Access builder builder to quickly create Web applications that operate on data in the WebSphere Portal Content Model. The builder allows you to specify the type of data to operate on, for example, documents, folders or libraries. Create, retrieve, update, and delete operations are supported.|
|Have a portlet to support searching for people or groups in WebSphere Portal.||The Directory Search builder provides a way to search for people or groups in WebSphere Portal directories or other types of directories.|
Parent topic: Choosing builders for common tasks: wpf7