Share via


Updating the Application Runtime

For the latest version of Commerce Server 2007 Help, see the Microsoft Web site.

After you write your application to deny updates, you must update the application runtime according to the procedure outlined in this topic. For this procedure, you must make changes in the Web.config file of the application runtime, as well as the Profiles Web service Web.config file.

Note

The application runtime and Profiles Web service must have the same encryption keys to function properly. If you update one, you must update the other at the same time.

To update the application runtime

  1. Store the newly generated public key hex string as the publicKey.

  2. Store the newly generated private key hex string as the privateKey.

  3. Update the keyIndex so that the value that is not the current value becomes the new value. That is, if the keyIndex is 1, it becomes 2; if the keyIndex is 2, it becomes 1.

  4. The privateKey that becomes the current privateKey (privateKey1 if keyIndex=1, privateKey2 if keyIndex=2) takes the value of the new private key hex string.

    Note

    Do not delete the old publicKey and privateKey values until after the profile data has been re-encrypted. Doing so will leave you unable to decrypt the old data.

  5. After the Web.config files have been updated, you must reinitialize the run-time application and the Profiles Web service so that the new key values are read from the repository.

See Also

Other Resources

How to Add Encrypted Properties for Profiles

Profiles System Tools

Profile Key Manager

Preparing to Use the Profile Key Manager

Generating a New Encryption Key

Denying Updates

Updating the Stored Data

Using the Profile Key Manager

Profile Key Manager Command Line Utility Reference

Decrypting Profile Data