Example: Creating a Profile Definition with Two Data Sources
One advantage to using Active Directory to store user profile data is that it provides more secure and specific user authentication. It is best to store only non-volatile data in Active Directory and to store frequently updated data in SQL Server.
The example in this section provides a scenario for creating a user profile definition that stores data in both a SQL Server database and an Active Directory database. This example is meant only to describe the process; it does not describe an actual profile you should use. You should design your profile definitions based on your business requirements.
This example presumes that you have installed and configured Active Directory domain controllers for your Commerce Server 2000 site.
For information about planning for Active Directory, see Planning for Active Directory Integration.
This section contains:
- Step 1: Create the ProfileService_ADSource Data Source
- Step 2: Add the AD User Object
- Step 3: Add Data Members to the AD User Object
- Step 4: Create the AD-SQL User Profile Definition
- Step 5: Add Property Groups to AD-SQL User
- Step 6: Add SQL Server Properties to AD-SQL User
All rights reserved.