Portlet Factory, Version 6.1.2
Overview: profiling
Creating applications with builders offers benefits over traditional development.
- Builders automate development tasks.
- Builders change their behavior, and the resulting web application, based on their inputs.
Profiling refers to the process of defining the profiles and profile entry values from which any profiled builder call inputs get their values.
The profiling process consists of the following general tasks:
- Create a profile set.
The profile set is created with a default profile (named Default) but with no profile entries.
- Add one or more profile entries to the profile set.
- Add one or more profiles to the profile set.
As you add each profile, the Default profile entries also apply to the profile.
- Customize each profile by changing one or more default profile entry values for that profile.
- Profile the builder call inputs in the builder call editor by selecting a profile entry from a specific profile set.
- Preview the effects of profiling on the model by applying various profile combinations.
Generally, the profiling process is iterative. You can perform any of these steps at any time. Typically, you do the steps multiple times to fine tune the variability of your application.
Note: Do not use the Navigator to rename a profile set. Because IBM® WebSphere Portlet Factory refers to profile sets by ID rather than by name, renaming a profile set in the Navigator causes problems when a model is run. The profile set name and ID will not be consistent. Always use WebSphere Portlet Factory Designer profile management tools and views when working with or modifying a profile set.
Advanced profile topics
Profiles make use of various selection handlers to access data. In addition, profile data can be stored in an external repository such as a database.
Parent topic: Working with WebSphere Portlet Factory
- Profiles
Profiles define the values to supply to profiled builder call inputs based on the segment (J2EE Role, or LDAP Group, for example) to which the user belongs.
- Profiling builder call inputs
Profiling a builder call input associates that input with the entry value specified in a profile.
- About previewing the effects of profiles
After you profile one or more builder call inputs, you can see how various profiles affect the model.
- Profile sets
A profile set defines the profile entries and the profiles that contain specific values for those entries.
- Setting the profile selection handler for a profile set
You can set the profile selection handler for a profile set.
- Profile selection and storage mechanisms
Custom profile selection and custom profile values let you gain finer control over your web application.
- WebSphere Portal Personalization Profile Rules and the Profile selection handler
IBM WebSphere Portlet Factory integrates with IBM WebSphere Portal Personalization Profile Rules using a profile selection handler.
- IBM WebSphere Portlet Factory Designer Profiling View and Dialogs
This table lists the various tools and views in WebSphere Portlet Factory Designer that you use to perform profile-related tasks.
- Profiling a portlet
You can profile a portlet like any other IBM WebSphere Portlet Factory model.
- Customization of profiles
When you manage a profile, you can customize it by manipulating values for entries that you have included in a profile set.
- Profile selection and storage management
The profile selection functionality provides a pluggable profile selection mechanism based on handlers (and configuration information for each handler) where any available profile selection handler can be selected for use with each profile set.
- About localizing content
You can localize pages in your web application by using the Imported Page and Localized Resource builders.
- Profile API manipulation
The exposed API on a profile set is identical to that for getting a profile from a profile set, however the name can be either the simple profile name or the fully qualified name that contains its hierarchy.
Library | Support |