Filter
Top Products
6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm
216 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
Table 11-3 Encrypted data migration script parameters and behavior
In our example we wanted to reencrypt the data with the current merchant key,
so we ran the script with the following parameters:
migrateEncryptedInfo db2 demo
Once the migration script is finished the following logs will be created:
CCInfoMigration.log
MKChangeUserAndCCInfoMigration.log
MigrateEncryptedInfoError.log
in directory:
<wc56_home>\logs
Behavior needed Parameters to include
A non-default WebSphere
Commerce Suite V5.1 merchant
key is used and should be
reused.
dbtype
instance (optional)
example:
migrateencryptedinfo db2 demo
A default WebSphere
Commerce Suite V5.1 merchant
key is used and needs to be
redefined as a custom merchant
key.
Note: The current default
merchant key is not used as a
parameter
dbtype
instance
new_key
example:
migrateencryptedinfo db2 demo
abcdef0123456789
A non-default WebSphere
Commerce Suite V5.1 merchant
key is used but the user wants to
define a new merchant key.
dbtype
instance
current_key
new_key
example:
migrateencryptedinfo db2 demo
0123456789abcdef abcdef0123456789