A content selector targets users with personalized Web content taken from BEA's Virtual Content Repository. Content selectors return and display multiple content nodes.
When a user views a portal desktop or a portlet containing a content selector, the content selector's rules and back-end logic look for a match of properties such as the the user's profile information. If the properties match the content selector rules, the content selector runs a query and retrieves and displays all content matching the query.
Note: When library services (versioning, lifecycle status, and so on) are enabled for a BEA repository, system properties are always available (published) to queries unless the content item has a retired status. If you want to retrieve content based on its lifecycle status, you must use a the cm_objectClass system property in your content query. If your queries use only system properties only, the query retrieves all content items with matching system properties that are not retired.
Content Selectors are scoped to the enterprise application, so you can include Content Selectors in any JSPs within the enterprise application.
To create a Content Selector
To modify a Content Selector
To modify a Content Selector, open its file by double-clicking it in the Application window. Modify the appropriate conditions. Click the query link and modify the queries.
To delete a Content Selector query
To delete a Content Selector
To delete a Content Selector, select it in the Application window, press the Delete key, and click OK in the confirmation dialog box. Also delete any <pz:contentSelector> tags in your JSPs that reference the Content Selector you deleted.
Tutorial: Showing Personalized Content in a Portlet
How Do I: Create a Personalized Portlet?
Content Selector Designer window
Personalization Conditions Reference
Developing Personalized Applications