Secure > Enhance site security


Update encrypted data using Configuration Manager

Use the Database Update Tool to change the merchant key and update all encrypted data (for example, passwords or credit card numbers) in one or more WebSphere Commerce databases for a given instance.

This tool is only available if the merchant key is stored in the instance.xml file. If the merchant key is stored in another medium, see Update encrypted data using MigrateEncryptedInfo.


Procedure

  1. Open the Configuration Manager.

  2. Traverse to the specific database entry... WebSphere Commerce > node_name > Commerce > Instance List > instance > Instance Properties > Database > database_name .

  3. Right-click database_name and select Run Database Update Tool.

    • Select Update all databases for this instance to migrate encrypted data for all databases for the selected instance.

      This option does not apply.

    • Select Update selected database to migrate encrypted data for a specific database by selecting the database from the drop-down list (default).

  4. Select an action to run from the Action Item box, and fill in the required information in the Parameter field:

    Actions Parameters Action Required
    Change Merchant Key Old Merchant Key Enter the existing merchant key that you used when you created the current WCS instance.
    New Merchant Key Enter the new merchant key. This is a 16-digit hexadecimal number for the Configuration Manager to re-encrypt the currently encrypted data. The Merchant Key must have at least one alphanumeric character (a to f) and at least one numeric character (0 to 9). Any alphanumeric character must be entered in lower case letters, and you cannot have the same character entered more than four times in a row.

  5. Click OK to run the database update tool for the selected WebSphere Commerce database or for all the WebSphere Commerce databases.

  6. Upon successfully updating the configuration for the instance, we will receive a message indicating a successful update.

  7. Restart the WCS instance.


+

Search Tips   |   Advanced Search