Scenario-related profile data must be stored in a SQL repository. If you use a composite profile repository, scenario data must be stored in the primary view, which must use a SQL repository as its data source.

The scenario data that must be in the primary view is any scenario property described in the default userProfile.xml file included with the Scenarios module.

If you want to use scenarios that perform queries against a user directory (for example, scenarios that filter users according to their roles or organizations), the user directory information must be stored in a SQL repository. You cannot run scenarios against an LDAP-based user directory, even within a composite repository.

Note also that the Scenarios module uses the values of some profile properties, either as criteria for triggering an element or as part of the process of tracking a user’s progress through a scenario. If you change the names of any of the profile properties required by the Scenarios module, you must update the /atg/userprofiling/PropertyManager component for the Scenarios module (class atg.scenario.userprofiling.ScenarioPropertyManager) to register the new names.

If you choose to keep both the default SQL profile repository and a separate composite repository (see Creating a Separate Composite Profile Repository), you must also update the subjectRepository property in the /atg/scenario/ScenarioManager component to point to the new repository.

loading table of contents...