Secure > Enhance site security


Update encrypted data using MigrateEncryptedInfo

You can change the merchant key and update the encrypted data using the command line tool, MigrateEncryptedInfo. This utility supports two ways of specifying the values of the merchant keys. One is to provide the actual values of the old and new merchant keys as command line arguments. The other is to retrieve the values through the Key Locator Framework.


Before you begin

Before running the MigrateEncryptedInfo.sh utility, ensure that the user ID that runs the utility (wasuser) has full permission to access files and subfolders in the WC_INSTALL/instances/ instance directory.

Before running the MigrateEncryptedInfo script for Oracle 9i databases, set the UNDO table space to a sufficiently large size by setting the datafile for the UNDO table space to autoextend with maxsize unlimited. From an SQLPlus prompt, enter the following command:

alter database datafile undotablespace datafile autoextend on
maxsize unlimited;


Procedure

  1. Back up the database, following the instructions in your database engine documentation.

  2. Log on using a Windows user ID with Administrator authority.

  3. Switch to the WebSphere Application Server user ID (for example, wasuser):

    su - WC_non_root_user
    

  4. Stop the WC_instance application server in the WebSphere Application Server console. If it is running, use the WebSphere Application Server "stopServer" script to stop it.

  5. For DB2 databases, open a DB2 command window. For Oracle databases, open a regular command window.

  6. Switch to the WC_INSTALL\bin directory.

  7. Run the MigrateEncryptedInfo utility

    The MigrateEncryptedInfo tool generates the following log files:

    • CCInfoMigration.log

    • MKChangeUserAndCCInfoMigration.log

    • MigrateEncryptedInfoError.log

    in the following directory:

    • WC_USER/instances

    • WC_INSTALL/logs

    Review the information in these log files and ensure they do not contain any error messages.

  8. Start the WebSphere Commerce instance.

  9. Run the following command:

  10. Restart the WebSphere Commerce instance.


+

Search Tips   |   Advanced Search