MigrateEncryptedFiles utility

The MigrateEncryptedFiles utility updates the encrypted information in configuration files from 3DES encryption to AES encryption, and sets the encryption mechanism to AES.

Syntax diagram for MigrateEncryptedFiles utility

Parameter values

checkAESFilesFlag
Checks if the current encryption mechanism is set as AES_Files.
checkInstanceAESFilesFlag
Checks if the current instance encryption mechanism is set as AES_Files.
instance_name
The name of the WebSphere Commerce instance with which you are working (for example, demo).
Note: If you do not specify an instance, the utility updates all instances on your environment.
checkProductAESFilesFlag
Checks if the current runtime product encryption mechanism is set as AES_Files.
restoreProductBackupFiles
Restores the product backup files.
restoreInstanceBackupFiles
Restores the instance backup files.
MigrateCustomizedFiles
Migrates the runtime customized files.

Usage

  1. To migrate configuration files to use AES encryption:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh
      • WindowsMigrateEncryptedFiles.bat
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat
    3. Verify that the utility completed successfully:
      1. Review the information in the log file to ensure that it does not contain any error messages:
        • WC_installdir/logs/MigrateEncryptedFiles_timestamp.log
      2. Review the following file and ensure that the AES_FILES parameter is set to true:
        • LinuxAIXWindowsFor IBM i OS operating systemWC_installdir/xml/product.xml
        • LinuxAIXWindowsFor IBM i OS operating systemWAS_installdir\profiles\instance_name\installedApps\instance_name_cell\instance_name.ear\xml\config\wc-server.xml
        • WebSphere Commerce Developerworkspace_dir\WC\xml\config\wc-server.xml
  2. To verify the current encryption mechanism to ensure that it is set as AES_Files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to check for the flag:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh checkAESFilesFlag
      • WindowsMigrateEncryptedFiles.bat checkAESFilesFlag
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat checkAESFilesFlag
    3. Verify the utility results.
  3. To verify the current instance encryption mechanism to ensure that it is set as AES_Files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to check for the flag:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh checkInstanceAESFilesFlag -DinstanceName=instance_name
      • WindowsMigrateEncryptedFiles.bat checkInstanceAESFilesFlag -DinstanceName=instance_name
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat checkInstanceAESFilesFlag -DinstanceName=instance_name
    3. Verify the utility results.
  4. To verify the current runtime product encryption mechanism to ensure that it is set as AES_Files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to check for the flag:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh checkProductAESFilesFlag
      • WindowsMigrateEncryptedFiles.bat checkProductAESFilesFlag
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat checkProductAESFilesFlag
    3. Verify the utility results.
  5. To restore the product backup files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to restore the files:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh restoreProductBackupFiles
      • WindowsMigrateEncryptedFiles.bat restoreProductBackupFiles
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat restoreProductBackupFiles
    3. Verify the utility results.
  6. To restore the instance backup files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to restore the files:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh restoreInstanceBackupFiles -DinstanceName=instance_name
      • WindowsMigrateEncryptedFiles.bat restoreInstanceBackupFiles -DinstanceName=instance_name
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat restoreInstanceBackupFiles -DinstanceName=instance_name
    3. Verify the utility results.
  7. To migrate the product customized files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to migrate the files:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh MigrateCustomizedFiles -DinputFile=absoluteInputFile
      • WindowsMigrateEncryptedFiles.bat MigrateCustomizedFiles -DinputFile=absoluteInputFile
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat MigrateCustomizedFiles -DinputFile=absoluteInputFile
    3. Verify the utility results.
  8. To migrate the runtime instance customized files:
    1. Go to the following directory:
      • WC_installdir/bin
      • WebSphere Commerce DeveloperWCDE_installdir\bin
    2. Run the MigrateEncryptedFiles utility to migrate the files:
      • LinuxAIXFor IBM i OS operating systemMigrateEncryptedFiles.sh MigrateCustomizedFiles -DinputFile=absoluteInputFile -DinstanceName=instance_name
      • WindowsMigrateEncryptedFiles.bat MigrateCustomizedFiles -DinputFile=absoluteInputFile -DinstanceName=instance_name
      • WebSphere Commerce DeveloperMigrateEncryptedFiles.bat MigrateCustomizedFiles -DinputFile=absoluteInputFile -DinstanceName=instance_name
    3. Verify the utility results.