Migrating Key Manager Plus from 32-bit to 64-bit Architecture

This document explains the detailed steps to migrate Key Manager Plus (running in both PostgreSQL and MS SQL) from 32-bit to the 64-bit architecture. Please be noted that this migration is applicable from Key Manager Plus version 6620.

Windows(SHA256 Checksum hash value)

Key Manager Plus.ppm 64-bitb3259b6944020d1c539eb7af854eb83dc718f45484f247beef724b279ba8039a
Linux(SHA256 Checksum hash value)

Key Manager Plus.ppm 64-bit9ee42e1c506144dca95949f8a8a65b39b9fae674dbe2d34a092c92fe8045f8c3

Prerequisites

  • Before commencing the migration, ensure if Key Manager Plus is running in a 64-bit OS environment. If the device's OS is 32-bit, then follow these steps to migrate to a 64-bit device.
  • Ensure that your product build number is 6620. Click here to upgrade to the latest build.
  • To avoid data loss during the upgrade, create a backup of the Key Manager Plus installation directory.

Migration Steps

  1. Stop Key Manager Plus service and exit the tray icon.
    Note: In case you store the database_params.conf file at a different location, you will have to copy the file back to the original location (i.e. <KMP Installation Folder>/conf/) before performing the migration.
  2. Shut down Key Manager Plus service.
  3. Now, right click on command prompt and run as administrator.
  4. Navigate to <KMP_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
  5. Click Browse and select the .ppm file that you downloaded. As a part of patch integrity verification from KMP build 6300 onwards, you must import an SSL certificate to complete the migration process. Click here to download the SSL certificate to be imported.
  6. In the pop-up that opens, click Browse and import the SSL certificate you downloaded in the previous step.
  7. Click Install in the Update Manager window to begin the upgrade process. Please note that importing the SSL certificate is mandatory while upgrading KMP.
  8. After applying the upgrade packs, start the Key Manager Plus service.

You have successfully migrated Key Manager Plus from 32-bit to 64-bit architecture.

Frequently asked questions

1. Is it mandatory to upgrade Key Manager Plus from 32-bit to 64-bit? What happens if we decide to continue with 32-bit?

It is not mandatory to upgrade Key Manager Plus to 64-bit. However, we highly recommend you to upgrade because we will be deprecating the 32-bit version soon.

2. I have 32-bit application running on a 32-bit machine. Can I still perform this migration?

No, you will not be able to migrate to Key Manager Plus 64-bit in a 32-bit machine.

3. How to migrate Key Manager Plus from 32-bit system to a 64-bit system?

Windows:

  1. Stop the Key Manager Plus service and exit the tray icon.
  2. Ensure that the PostgreSQL is not running in Task Manager.
  3. Take a backup of the Key Manager Plus installation directory.
  4. Copy the entire Key Manager Plus installation folder and move it to the new machine.
  5. Open command prompt as an administrator and navigate to <KMP_Installation_Folder>\bin and execute the following command: keymanager.bat install
  6. Now, move the encryption key (kmp_key.key) to the desired location.
  7. Open manage_key.conf under <KMP_Installation_Folder>\conf folder and specify the location of kmp_key.key.
  8. Start the Key Manager Plus service.
  9. To enable the tray icon, navigate to and right click on kmp.exe. In the pop-up that appears,
    • Select Properties and choose the Compatibility tab.
    • Select Run this program as administrator, click Apply and click Ok.
  10. Open <KMP_Installation_Folder>\conf\server.conf file using Wordpad and add new host name to update.

Troubleshooting tip:

If you experience any permission issues after the migration, open Command Prompt as an administrator and navigate to <KMP_Installation_Folder>\bin and execute the command initPgsql.bat
Now, start Key Manager Plus service.


Linux:

  1. Stop the Key Manager Plus application.
  2. Take a backup of the Key Manager Plus installation directory.
  3. Copy the entire Key Manager Plus installation folder and move it to the new machine.
  4. Now, move the encryption key (kmp_key.key) to the desired location.
  5. Open manage_key.conf under <KMP_Installation_Folder>\conf folder using Notepad and specify the location of kmp_key.key.
  6. Start the Key Manager Plus application.
  7. Open <KMP_Installation_Folder>\conf\server.conf file using Wordpad and add new host name to update.

Troubleshooting tip:

If you experience any permission issues after the migration, execute the following command:

  • chown -R postgres:postgres pgsql
  • chown -R postgres:postgres conf/ServerKey.key
  • chmod 755 bin/wrapper*.*

Now, start Key Manager Plus application.

4. Can we still perform this migration if we are using external databases?

Yes, you can migrate to the Key Manager Plus 64-bit when using an external database.

5. Is it safe to remove the 32-bit library files in <KMP installation directory> after this migration?

No, do not remove any files from the <KMP installation directory> after this migration.

6. Will there be any improvement in performance if we upgrade from 32-bit to 64-bit?

Yes, there will be a slight improvement in the overall performance of Key Manager Plus.

7. What will happen to the encryption key that is currently in use?

The encryption key that is currently in use will not be affected in any way.