IBM SG24-6320-00 manual Parameter, Encrypted data migration script parameters and behavior

6320ch_migrating.fm		Draft Document for Review July 28, 2004 7:33 pm
	Table 11-3 Encrypted data migration script parameters and behavior
	Behavior needed	Parameters to include
	A non-default WebSphere	dbtype
	Commerce Suite V5.1 merchant	instance (optional)
	key is used and should be
	reused.	example:
		migrateencryptedinfo db2 demo
	A default WebSphere	dbtype
	Commerce Suite V5.1 merchant	instance
	key is used and needs to be
	redefined as a custom merchant	new_key
	key.
	Note: The current default	example:
	merchant key is not used as a	migrateencryptedinfo db2 demo
	parameter	abcdef0123456789
	A non-default WebSphere	dbtype
	Commerce Suite V5.1 merchant	instance
	key is used but the user wants to
	define a new merchant key.	current_key
		new_key
		example:
		migrateencryptedinfo db2 demo
		0123456789abcdef abcdef0123456789

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

216Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide