The <ATG11dir>/Motorprise/config/atg/userprofiling/userProfile.xml file is combined with the userProfile.xml files from the Oracle Commerce Platform, the Scenarios module, and Oracle Commerce Personalization. These files are combined per the rules of XML combination to produce one XML file that is then parsed and used to describe the item types in the repository. (For more information about XML file combination, see the Platform Programming Guide.) The combined file is reparsed each time the Profile Adapter Repository starts and it is never written out to disk, so we only need to maintain the separate files, not the combined one.

This approach allows users to define the user profile in a layered structure For example, the <ATG11dir>/Motorprise/config/atg/userprofiling/userProfile.xml defines only those properties that are specific to Motorprise. It “adds on” to the already existing user profile definition.

The underlying storage of the user profile repository is a relational database. The SQL Profile Repository is used to expose that data via the Repository API. In the XML file, we describe the mapping of repository items to the relational database tables and columns.

We used the following SQL script to create the database schema to store the user profile data:

<ATG11dir>Motorprise/sql/db_components/mysql/b2b_user_orddet_ddl.sql

After the profiles have been extended, an ATG Control Center user can set up profiles for customer organizations. Then, the administrator for that customer organization can create and edit users and suborganizations for that customer organization, using the Company Admin pages on the Motorprise web site.