When you use application objects that are not installed, you must define the application objects by using a set of Personalization wizards that are provided with IBM
® Application Developer or develop application objects according to a set of public programming interfaces. After you define the application objects, the application objects are registered to the Personalization server through the Personalization browser. When you use the installed application objects, you do not have to define or register the application objects.
The Device, Referrer, Public Render Parameter, and Shared Data application objects are installed with 18.104.22.168 but are not enabled. You must run a configuration task to enable these application objects. For more information about enabling the application objects, see the related task link. Once enabled, you can use the application objects in rules.
The location attributes for the Device application object are not enabled by just running a configuration task and require more steps.
The following topics contain an overview of the installed application objects. This overview includes descriptions and examples of using the application objects in rules that you create. To select the attributes that are used in the examples, you must enable the application objects. Instructions for enabling the location attributes associated with the Device application are also included in this section.
Device application objectParent topic: Content targeting and application objects
Enabling or disabling the content targeting feature and application objects
The Device application object displays content by device class or by location (city, country, latitude, and longitude).
Referrer application object
You can target your content to users based on what site the user came from before the user accessed your site. You can also target your content by the search parameters that are entered by users in a search engine.
Public Render Parameters application object
The Public Render Parameter application object provides read and write access to public render parameters. Public render parameters allow portlets to share navigational state information and preserve this information across requests. Use this object in rules when you need your site to store a user's selection as a public render parameter during the action phase and have other portlets read this public render parameter during the render phase.
Shared Data application object
The Shared Data application object is used in rules to share complex data between web applications and IBM WebSphere
® Portal in a user's session.