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.
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.
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: Developing Web applications with IBM WebSphere Portlet Factory
Hiding a menu item by using profiling
Profiling actions in an action list
Profiling actions on and off in an action list