You can create as many profile entries as you need and save them as a profile set.
A profile set consists of zero or more profile entries. A profile set entry represents a single aspect of a business relationship that you want to make variable.
You can map each profile entry in those profiles to a builder call by profiling that builder input.
You manage profile entries in one of the following ways:
- The Profile Entries editor can add, modify, and delete entries.
To access the Profile Entries editor, click the Entries tab of the Profile Manager.
- The Profile Input dialog can add or modify entries.
To access this dialog, click the profile button [
] located beside a builder input.
Every entry that is created has six definition fields:
- User interface (UI) Type (for example, a radio box or select box)
- Extra Data
- Default Value
- Execution Time
When you add a profile entry, the entry is actually shared by all existing and future profiles. Except for the Default Value
field, the values of the definition fields are the same for all profiles. The Default Value
field is the only field whose data can be changed on a per-profile instance. The Default Value
field is the only customizable field. To see the settings of all six fields of an entry, use the Entries
tab of the profile manager.
You customize an entry value for a given profile either in the Manage Profiles editor of the profile manager or when you profile a builder call input. In either case, you are changing the Default Value
field of that entry for that profile.
You can also create a Java class that dynamically assigns data to profile values based on some runtime condition or business logic. Profile Value Selection handlers, as these Java classes are known, allow for even more flexibility in providing variability in your Web application.
Using execution time profile entries
You can set profile entries to be resolved at execution time by setting their Execution Time value to true
Values for profile entries
Profile entries have a fixed format.
About specifying choices in profile manager
Refer to this information when specifying choices in profile manager.
Creating profile entry value setters
You can assign the values for profile entries at generation time.
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.
Previewing the effects of profile-enablement
After you have created your profile sets, customized the profile entries, and profiled one or more builder call inputs, you can test the effects of profiling on the generated web application by using the Applied Profiles view.
Profile child retrieval
Using the ProfileSetStorageManager getChildProfiles(..)
method you can now get the immediate children of a specified profile.
Accessing profiles from linked Java object methods
If you want to determine the current profile being used by the model or access the profile values for the current profile in an LJO method, you can access the current profile through the com.bowstreet.generation.ProfileData
A new interface is available that supports the retrieval of a potentially larger number of profiles. This interface is the description of the profile and not all of its data. The different storage handlers implement this class.
Using execution time profile data
IBM® WebSphere® Portlet Factory can gain access to profile data at execution time rather than at WebApp generation time.
Container node flag
A container node flag supports the ability to query a profile set for its hierarchy without having to filter out thousands of leaf nodes.
Parent topic: Adding a profile entry
Creating and opening profile sets
About generated file names