A composite profile repository can have any number of composite views, for example “user,” “broker,” and “investor.” Each composite view is a top layer of data consolidated from any number of contributing views. One contributing view is designated as the “primary view,” which provides the ID space for the item that the views define. (Again, these concepts are explained in more detail in the Composite Repositories chapter in the ATG Repository Guide.)

The following diagram shows a data model for a composite profile repository that has one composite view and stores profile data as follows:

  • Scenario data and user preferences are stored in a SQL repository

  • The user’s phone number is stored in a separate SQL repository

  • The user’s first name and last name are stored in an LDAP directory

    Composite Profile Repository Data Model

loading table of contents...