Update starter store archives when using non-default distinguished names

The steps on this page detail how to update your starter store archives when using non-default distinguished names.

Complete one of the following sections based on the fix pack level of your WebSphere Commerce configuration:

  1. If you use DNs other than the default DNs provided by WebSphere Commerce, update some of the starter store archives. You can find the following directories that contain the store archive (SAR) files for the various starter stores: WC_installdir /starterstores

    1. Navigate to the directory that contains the starter store you want to publish and complete the following steps:

    2. Open the SAR file for the starter store using a ZIP file utility.

    3. Update any XML or DTD files in the SAR file as follows:

      1. Open the file in a text editor.

      2. Depending on the DNs that you are using, you are required to complete the updates similar to the following example. For example, if you use "dc=domain,dc=ibm,dc=com" as Root Organization, "cn=users,dc=domain,dc=ibm,dc=com" as Default Organization, and "cn=username,cn=users,dc=domain,dc=ibm,dc=com" for user DNs, make the following changes:

        1. Change any instances of o=Root Organization to dc=domain,dc=ibm,dc=com.

        2. Change any instances of o=Default organization to cn=users.

        3. Change any instances of "uid=" to "cn=" (If your user DNs are using "cn=" instead of "uid=").

    4. Save your changes to the file.

    5. Update all XML and DTD files in the SAR file.

    6. Update the following WebSphere Commerce contract template files if they exist:

    7. Update the EAR file XML configuration directory. For more information, see the ways to update application files topic in the WAS Information Center.

  2. If you use DNs other than the default DNs provided by WebSphere Commerce, do the following:

    1. Depending on the DNs that you are using, you are required to complete the updates similar to the following example. For example, if you use "dc=domain,dc=ibm,dc=com" as Root Organization, "cn=users,dc=domain,dc=ibm,dc=com" as Default Organization, and "cn=username,cn=users,dc=domain,dc=ibm,dc=com" for user DNs, make the following changes to the WebSphere Commerce configuration file:

      1. Open the WebSphere Commerce configuration file in a text editor and search for the following section: <MemberSubSystem>

      2. Add the following entries at the end of the <MemberSubSystem> section 
        <DNMappings>
  <mapping external="dc=domain,dc=ibm,dc=com" internal="o=root organization" name="root org"/>
  <mapping external="cn=users,dc=domain,dc=ibm,dc=com" internal="o=default organization" name="default org"/>
</DNMappings>
<RDNNameMappings>
  <mapping external="cn=username,cn=users,dc=domain,dc=ibm,dc=com" internal="uid" name="uid"/>
</RDNNameMappings>

      3. Save your changes to the file.

    2. Update the following WebSphere Commerce contract template files if they exist:

    3. Start your WebSphere Commerce instance if it is not already started.

    4. Run the following command:

    5. Restart your WebSphere Commerce instance.

 

Related Concepts


Directory services and WebSphere Commerce

 

Related tasks


Configure directory services (LDAP) with WebSphere Commerce
Configure WebSphere Commerce for use with Microsoft Active Directory
Enabling LDAP in the Configuration Manager
Enabling WebSphere Commerce Payments for use with LDAP