Prepare the LDAP server for use with WebSphere Commerce

+

Search Tips   |   Advanced Search

 

Before you begin, decide the DN that you will use for Root organization and Default organization.

• Root Organization is at the top of the membership hierarchy, and all other organizations are descendants of it.

• Default Organization is directly under Root Organization, and is the parent of guest and B2C users. B2B users should not be created under the Default Organization. Instead, they should be created under their respective buyer and seller organizations.

If a user is manually created in the LDAP server, then the user logs on to WebSphere Commerce, or performs single sign-on to WebSphere Commerce, the user will be automatically replicated into the WebSphere Commerce database, however the password will only exist on the LDAP server. The attributes that are replicated is determined based on the ldapentry.xml file. When the user is created in the WebSphere Commerce database, the profile type of the user will be specified as 'C' (B2C user) if the parent organization of the user is Default Organization, and 'B' (B2B user) otherwise. This is important because only 'B' type users can be managed from the Organization Administration Console, whereas 'C' type users can be managed from the Accelerator.

WebSphere Commerce provides default DN for Root Organization and Default Organization...

• "o=root organization"
• "o=default organization,o=root organization".

You can customize these names to your own settings. For example, by following the appropriate configuration procedure, use...

"dc= domain,dc=ibm,dc=com"

...to replace...

"o=root organization"

...and...

"cn=users,dc= domain,dc=ibm,dc=com"

...to replace...

"o=default organization,o=root organization"

The relationship of the user to its parent organizations is defined in the MBRREL table and also mirrored in the DN for the user.

1. After you decide on the DN for Root Organization and Default Organization, create these organizations on your directory server. For more information, see:

   • AIX|Linux|Solaris|Windows:

     Configuring IBM Directory Server for use with WebSphere Commerce

   • AIX|Linux|Solaris|Windows:

     Configuring IBM Lotus Domino LDAP service for use with WebSphere Commerce

   • I5/OS:

     Configure IBM i5/OS Directory Services for use with WebSphere Commerce

   • Windows: Configure Microsoft Active Directory for use with WebSphere Commerce

   • Solaris|Configure Sun Java System Directory Server for use with WebSphere

2. Optional: Set up LDAP over SSL.

After you have completed configuring your directory server, install Member Manager.

 

Related Concepts

Directory services and WebSphere Commerce
Configure directory services (LDAP) with WebSphere Commerce