Filter
Top Products
Chapter 10. Pre-migration steps 197
Draft Document for Review July 28, 2004 7:33 pm 6320ch_before_migration.fm
Users with an entry in BUSPROF and with PROFILETYPE set to B (Business user)
will be assigned the organization, pointed to by the ORGUNIT_ID or ORG_ID
columns, as follows:
– If ORGUNIT_ID is not null, the organization pointed to by ORGUNIT_ID, is
used. as the user’s parent organization
– If ORGUNIT_ID is null and ORG_ID is not null, the organization pointed to by
ORG_ID, is used as the user’s parent organization.
– If both ORGUNIT_ID and ORG_ID are null, the user is assigned
Default Oganization as parent organization.
Since business users should not be assigned Default Oganization, we
recommend that you ensure that all your business users an entry in BUSPROF
with the right organization specified in ORGUNIT_ID.
Profile types
The WebSphere Commerce Suite V5.1 and WebSphere Commerce V5.6
schema allows for three profile types, as defined by the PROFILETYPE column of
the USERS table:
C - Consumer (B2C)
B - Business (B2B)
null - No profile data
It is recommended to clean up this column in a way that all users have either a
Consumer or a Business profile. In other words, ensure that no rows in the USERS
table have the PROFILETYPE column set to null.
In our scenario we changed the “null” profile type values to “B” by running the
following commands:
1. Connect to the commerce database
DB2 connect to <WC_db> using <db_user_id> using <db_user_password>
2. Update the users profile type
DB2 update users set profiletype=’B’ where profiletype is null
Administrators
Administrators with register type S or A (Site administrator or Administrators,
respectively) that also belongs to an access group must have their profile type
set to B (Business user).
This is because all future administrators created in Organization Administration
Console will have profile type B. This can be done with the following SQL:
DB2 update users set profiletype='B'