Filter
Top Products
Chapter 11. Migrating WebSphere Commerce components 217
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm
Review the logs to ensure that no errors occurred while migrating the encrypted
data. The following errors are typical caused by an incorrect merchant key:
%3DES-F-CIPHERINIT; Exception caught while initializing the cipher object.
; java.lang.ArrayIndexOutOfBoundsException: 16
%3DES-F-DCRYPT; Exception caught while decrypting ;
javax.crypto.IllegalBlockSizeException: Input length (with padding) snot
multiple of 8 bytes
The above errors can also be related to encrypted data which has been
encrypted with different merchant keys. In that specific case please refer to
WebSphere Commerce V5.6 migration guide.
To see the complete migration script containing all the above steps, please refer
to Appendix C, “Migration scripts” on page 255.
11.4 Migrating Payment Manager
In the following migration scenario, WebSphere Payment Manager Node is the
old system to be migrated and WebSphere Commerce Payments Node is the
new system.
The following list highlights the necessary steps for the remote payment
migration:
1. Ensure that WebSphere Payment Manager is the right version. Supported
versions are 2.2.1.x, 3.1.3.x and 5.5.0.0.
2. Install WebSphere Commerce Payments V5.6 on the WebSphere Commerce
Payments Node.
Note: At the time of writing this book this script had an error when
managing the logs. The log files after execution are empty, but still can be
monitored during the execution time. We used the tail command (unix
command) as it would show the content on the fly (to have this unix
command in a windows environment, an additional unix tool package for
windows needs to be installed).
Note: Encrypted data is identified with a space at the front of the value. If
columns exists in the targeted tables with values that begin with space and is
not encrypted the above error will occur. If such values exists they must be
corrected by trimming the space(s) in the beginning of the value.