Loading user data

The information on this page describes how to load user data.

When loading user data into the database, load the following database tables:

Optionally, you can also load the following tables:

Use the following as a reference when loading these tables.


Where:

**1**

The MEMBER_ID primary key space (KEYS table) is shared by the USERS, ORGENTITY, and MBRGRP tables.

**2**

The DN should be lower-case and in the following format: "uid=" + logonid + "," + parent_organization_DN"

**3**

Type 'C' is for consumer direct users; 'B' is for a business direct users. Consumer direct users are listed in the WebSphere Commerce Accelerator. Business direct users are listed in the WebSphere Commerce Organization Administration Console.

**4**

A random string that is unique to each user. This string is appended to the password before hashing.

**5**

The encrypted logon password that is generated when using the wcs_password utility, which takes the plain text password and SALT value as input values.

**6**

A user can only have one permanent self-address (SELFADDRESS=1, STATUS='P'). This is the address associated with the user's registration. Other permanent addresses in the user's address book should be have SELFADDRESS=0 and STATUS='P'. Any old addresses that have changed are marked temporary (STATUS='T').

**7**

One row in the MBRREL table should be created for each ancestor. For example, if you are creating a user under the default organization, then create one record to indicate that the parent (sequence=1) is the default organization, and the grandparent (sequence = 2) is the root organization

**8**

The MBRROLE table defines the roles that the user plays in the system. By default, you will want a user that registers to a store to have the Registered Customer role (-29) in the store's organization.

There are three different methods for loading data into your tables:

 

Related Reference


Example: Loading data into the MEMBER table (idresgen utility)