Post-Upgrade Update of Encrypted Keystore Password Parameters

Post-Upgrade Update of Encrypted Keystore Password Parameters

Issue Description:

The SRM 6.1.x.x upgrade installs a fresh Tomcat 10 instance, overwriting the existing Tomcat configuration, resulting in the loss of any custom server.xml configurations, including the encrypted keystore password.

Summary:

After upgrading to SRM 6.1.x.x, the encrypted keystore password is not retained. This occurs because Tomcat does not support in-place upgrades across major versions. During the upgrade, Tomcat 10 installs a new conf directory with default configuration files, and any customizations made to the server.xml file in the previous Tomcat 9 installation are not automatically migrated.

Resolution:

A script has been developed to automatically read the required configuration parameters from server.xml.bak and apply them to the newly generated server.xml during the upgrade. This ensures that custom Tomcat configurations, including the encrypted keystore password, are retained after upgrade.

Steps:

  • Copy the attached update_encrypted_keystore_password_params.zip file to the /opt/APG/Web-Servers/Tomcat/Default/conf directory.
  • Navigate to /opt/APG/Web-Servers/Tomcat/Default/conf directory.
  • Unzip the script using below command
    • unzip -q update_encrypted_keystore_password_params.zip
  • Run below command to give execution permission
    • chmod +x  update_encrypted_keystore_password_params.sh
  • Execute the script :
    • ./update_encrypted_keystore_password_params.sh
    • Related Articles

    • SRM/SMR- 6.1.0.0 | Device Discovery status to be retained post 6.1.0.0 upgrade

      Symptoms Device discovery status greyed out post upgrade to SRM and SMR 6.1.0.0 environment. Cause Discovery status results are stored in h2 database. h2 database has been upgraded from version 2.1.x to 2.4.x in 6.1.0.0 release as the older version ...
    • SRM 6.1.1.0 | Windows Update Script (Windows_SRM_Update.ps1)

      Overview This script automates the SRM update process for windows environments. It supports both All-in-One (AIO) and Distributed deployments. Important Notes vApp/Binary SRM environments are not updated by this script; they are skipped and must be ...
    • SRM vApp External Automated Upgrade Script

      Overview This script automates the SRM update process for vApp environments. It supports both All-in-One (AIO) and Distributed deployments. Important Notes Windows SRM environments are not updated by this script they are skipped and must be handled ...
    • SRM Linux External Automated Upgrade Script

      Overview This script automates the update process for SRM binary linux platforms, including RHEL and SLES. It supports both All-in-One (AIO) and Distributed environments. Important Notes Windows SRM environments are not updated by this script; they ...
    • SRM 6.1.x.x: vApp External Automated Upgrade Script

      Overview This script automates the SRM update process for vApp environments. It supports both All-in-One (AIO) and Distributed deployments. Important Notes Windows SRM environments are not updated by this script they are skipped and must be handled ...