Configure the WebSphere Commerce database when using customized DNs

Follow the steps on this page if you use customized DNs.

Prerequisite


You must update your database if at least one of the following conditions are true:

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. AIX|Linux|Solaris: Log on as the WebSphere Application Server user. For example, wasuser.

  2. Navigate to the following location: WC_installdir/schema/ db_type/ldap/

  3. Back up the updatedbforldap _ldap_type.sql file. For example, if you use Active Directory, the ldap_type is represented by "ad" while all other LDAP servers use the "default" type.

  4. Open the appropriate updatedbforldap _ldap_type.sql file in a text editor.

  5. Complete one of the following steps

    • If you are not using o=root organization, and o=default organization to represent Root Organization and Default Organization, search and replace the following parameters:

      Variable Value
      @WcsRootOrgDN@ Replace @WcsRootOrgDN@ with the root org DN.

      For example, dc=domain,dc=ibm,dc=com

      @WcsDefaultOrgDN@ Replace @WcsDefaultOrgDN@ with the default org RDN.

      For example, cn=users.

  • If you are using o=root organization, and o=default organization to represent Root Organization and Default Organization, delete the contents of the file.

  • If you are using an LDAP server other than Microsoft Active Directory, and the DN of the users on the LDAP server begins with a prefix other than "uid=", complete the following step:

  • Windows: Run the following SQL script to update your database:

    Run the following SQL script to update your database:

  • Next step: Configure Member Manager.


     

    Related Concepts


    Directory services and WebSphere Commerce

     

    Related tasks


    Configure directory services (LDAP) with WebSphere Commerce
    Configure Member Manager