Filter
Top Products
Chapter 11. Migrating WebSphere Commerce components 215
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm
data, instead a system key was used. Since this behavior has changed the data
must be re-encrypted.
To summarize, the encrypted data must be re-encrypted because:
Salt key is introduced for passwords
One way hash keys are used for passwords
Prior to WebSphere Commerce Suite V5.1.1.2 a system key was used for
encrypting credit card data instead of using the merchant key
A default merchant key is not valid and a new merchant key must be defined
and therefore the encrypted data must be re-encrypted with the new
merchant key
Encrypted data is migrated by calling the migrateencryptedinfo.bat script
located in:
<wc56_home>\bin\
In our example:
D:\WebSphere\CommerceServer56\bin
The script must have the following mandatory parameters:
-dbtype
The optional parameters are:
-instance
-current_key
-new_key
Table 11-2 Encrypted data migration script parameters
The script behaves in different ways depending on what parameters it receives.
Parameter name Parameter value
dbtype The database type.
‘db2’ for DB2
‘oracle’ for Oracle
instance The WebSphere Commerce Suite V5.1 instance name. This
parameter is optional as long as their is only one instance
existing.
current_key The current merchant key
new_key The new merchant key (must conform with WebSphere
Commerce V5.6 merchant key restrictions)