Filter
Top Products
6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm
108 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
3. Customer Service Representative
We found that Store Administrator would be a more suitable role for these two
users. Therefore we assigned these two users the Store Administrator role
instead.
Delete all roles for user:
delete from accmbrgrp where users_id=<users_id>
Add Store Administrator as role for our users:
insert into accmbrgrp values (-6,<users_id>,-2000,NULL)
Where <users_id> is the ID of the users that should be assigned the Store
Administrator role.
6.3.6 Custom message types
If you have created any custom message types in the MSGTYPES table, you may
be required to update the MSGTYPE_ID column for your new types in order to avoid
a conflict with new message types introduced in WebSphere Commerce V5.6. If
you have not created any custom types, you can safely skip this sub-section.
As the MSGTYPE_ID column in the MSGTYPES must contain unique values, you must
ensure that any custom message types that you have created do not have a
MSGTYPE_ID the same as any new types in WebSphere Commerce V5.6. The
simplest way to ensure that this does not happen is to update your custom types
by adding 10000 to MSGTYPE_IDs. This must be done manually from a DB2
Command Window or the DB2 Command Center.
Failure to complete this step for custom message types can result in the
database migration script failing to complete successfully.
6.3.7 Dropping foreign key references
If you have created any custom tables that have foreign key references to tables
in the standard WebSphere Commerce data model, you must drop these foreign
keys before proceeding with the migration. During the database migration, many
tables are dropped, replaced with new versions and then re-populated with your
data. If foreign key relationships exist, this may prevent the tables from being
dropped, leading to the database migration script failing.
You must also drop any custom views that have been created in the database, as
these may interfere with the operation of the database migration scripts.