Troubleshooting Steps for Tomcat Upgrade Failure

Troubleshooting Steps for Tomcat Upgrade Failure

  1. Verify Folder Existence 

    1. Check if the ApplicationsManager/working/apache/tomcat_9_new folder exists. If it does, please delete this folder.

  2. Download and Extract Tomcat

    1. Use the appropriate version-specific ZIP based on your APM version:

    2. Extract the content and locate the tomcat_9_new folder.

    3. Copy tomcat_9_new to the AppManager/working/apache/ directory.

  3. Rename the Existing Tomcat Folder

    1. Rename the existing AppManager/working/apache/tomcat folder to include the base build version, e.g., tomcat_old_9_16861.

  4. Rename the New Tomcat Folder 

    1. Rename the newly copied AppManager/working/apache/tomcat_9_new folder to tomcat.

  5. Copy Keystore File

    1. Copy appmanager.keystore from the old Tomcat directory (AppManager/working/apache/tomcat_old_9_16861) to the new Tomcat directory (AppManager/working/apache/tomcat) if exists.

  6. Copy Configuration Backup 

    1. Copy the content of the conf/backup folder from the previous Tomcat directory (AppManager/working/apache/tomcat_old_9_16861/conf/backup) to the conf folder in the new Tomcat directory (AppManager/working/apache/tomcat/conf).

  7. Copy the Webapps Folder 

    1. Copy the webapps folder from the previous Tomcat directory (AppManager/working/apache/tomcat_old_9_16861/webapps) to the new Tomcat directory (AppManager/working/apache/tomcat) if exists.

  8. Update Keystore and Truststore Files in server.xml  

    1. Open the server.xml file in the AppManager/working/apache/tomcat_old_9_16861/conf/backup directory.

    2. Locate the <Connector> element(s) with the SSLEnabled attribute set to true.

    3. Note down the paths for truststoreFile and keystoreFile attributes, if they exist.

    4. Copy the noted files (e.g., keystore and truststore) from the old Tomcat directory to the same relative location in the new Tomcat directory i.e AppManager/working/apache/tomcat.

    5. Update the server.xml file in the new Tomcat configuration to reflect these paths if necessary.

  9. Update TLSv1.3 Ciphers (Applicable only to APM version less than 170000) 
    1. Open the server.xml file in the AppManager/working/apache/tomcat/conf/backup directory.
    2. Locate the <Connector> element(s) with SSLEnabled="true".
    3. Update the ciphers attribute to TOMCAT_CIPHERS. This will apply a default, secure set of ciphers.
      NotesNote: You can skip this step if you prefer to configure your own custom ciphers.
  10. Use TOMCAT_CIPHERS Variable (Applicable only when upgrading to APM version 176600) - Optional
    1. Open the server.xml file in the AppManager/working/apache/tomcat/conf/backup directory.
    2. Locate the <Connector> element(s) with SSLEnabled="true".
    3. Update the ciphers attribute to TOMCAT_CIPHERS. This will apply a default, secure set of ciphers.
Notes
Note: You can skip this step if you prefer to configure your own custom ciphers.



      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                      Related Products