The Oracle ATG Web Commerce LDAP Repository is an implementation of the Repository API that enables you to store and access profile data in an LDAP (Lightweight Directory Access Protocol) directory. The LDAP repository is similar in functionality to the SQL repository, as described earlier in this guide. While by default Oracle ATG Web Commerce Scenario Personalization is configured to use an SQL profile repository, you can change the configuration to use an LDAP repository instead. See the ATG Personalization Programming Guide for information about configuring Oracle ATG Web Commerce to use an LDAP profile repository. LDAP directories are widely used to store personnel information and other kinds of data. LDAP repository lets you to tap into the profile data you already have in an LDAP directory, and to share user information across multiple applications.

Also, you can configure Oracle ATG Web Commerce’s application security scheme to use an LDAP repository, rather than an SQL repository. See the Managing Access Control chapter in the ATG Platform Programming Guide for more information.

Just like the SQL repository, the LDAP repository implements the Oracle ATG Web Commerce Repository API to allow you to store, access, modify, and query user profile information. As in the SQL repository, repository items are first created as transient items (RAM profiles); they become persistent after they are added to the database.

It is important to note, however, that the LDAP repository implementation is not specific to user profiles in any way. Because an LDAP directory can be used to store any kind of data—people, groups, mailing lists, documents, printers—you can use the LDAP repository to expose any of that data in Oracle ATG Web Commerce. This chapter focuses on using LDAP as a profile repository, because that is the most common application of LDAP. However, other uses are possible.

This chapter includes the following sections: