IBM SG24-6320-00 manual Wcim.bat behavior, Tables used by migrateEncryptedInfo script file

6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm

instead a system key was used. Since this behavior has changed the data must be re-encrypted.

b.PDI flag enforcement: The variable PDIEncrypt (on off) in the instance file indicates if credit card data is encrypted. Depending on the value of this variable credit card information is encrypted or decrypted accordingly. This script provides you with an opportunity to change and enforce the PDI encryption setting.

2.The second invocation of the MKChangeApp command uses the config file schema\dbtype\migration\DBUpdate.txt, which defines the following two actions:

a.Password migration: Passwords are re-encrypted using the random Salt values and one way hash keys

b.Merchant key migration: This script allows you with opportunity to change your merchant key and migrate your data based on the new merchant key.

This script acts on the following tables.

Table 12-1 Tables used by migrateEncryptedInfo script file

TABLE	COLUMNS	UNIQUE ID	Notes
	UPDATED
USERREG	LOGONPASSWO	USERS_ID	Password related
	RD,		information
	SALT
ORDERPAYINFO	VALUE	ORDERPAYINFO_	Credit Card related
		ID	information
ORDPAYMTHD	PAYDEVICE	ORDERS_ID,	Credit card related
		PAYMETHOD,	information
		PAYDEVICE,
		REFUNDNUMBER
PATTRVALUE	STRINGVALUE	PATTRVALUE_ID	Personalization
	ENCRYPTFLAG		attributes, handled
			with credit card
			data processing
			(table began to
			exist in v5.4
			onwards)

wcim.bat behavior

Here is a brief description on what WCIM does at the high level.

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