The profile repository requires a template to define users in the profile repository. The ATG platform features a default profile template that you can redesign to suit your needs. However, as you customize the profile template, be sure that your schema retains the item descriptors and properties that are required by the PAF and the baseline or custom gears you are using in your portal application. The PAF expects a profile item descriptor named user, with at a minimum properties named login, firstName, and lastName

The PAF extends the default profile template to include new item descriptors (gearUser, personalizedRegion, personalizedCommunity, personalizedPage) that store information about how a user may have customized his or her portal pages. These profile template changes are added in the following file:

<ATG10dir>/Portal/paf/config/atg/userprofiling/userProfile.xml

In addition, the Favorite Communities gear extends the default profile template to include a userCommunity property that describes the communities to which a visitor belongs. This property is added in the following file:

<ATG10dir>/Portal/communities/config/atg/userprofiling/userProfile.xml

The Alerts gear extends the default profile template to include properties that store the user’s alerts and alert preferences. These profile template changes are added in the following file:

<ATG10dir>/Portal/alert/config/atg/userprofiling/userProfile.xml

When you use the ATG platform with the Portal module, these files are included in your ATG CONFIGPATH and are combined with the other user profile template definition files that share its Nucleus address of /atg/userprofiling/userProfile.xml.

You can add user information to your repository by editing the ATG platform user profile template, or by extending the template to include other tables. For more information on modifying the profile template, refer to the ATG Personalization Programming Guide.