Troubleshooting Steps for Tomcat Upgrade Failure
Verify Folder Existence
Check if the ApplicationsManager/working/apache/tomcat_9_new folder exists. If it does, please delete this folder.
Download and Extract Tomcat
Use the appropriate version-specific ZIP based on your APM version:
- For APM versions 170000 to less than 172500, download this ZIP.
- For APM versions 172500 to less than 176600, download this ZIP.
Extract the content and locate the tomcat_9_new folder.
Copy tomcat_9_new to the AppManager/working/apache/ directory.
Rename the Existing Tomcat Folder
Rename the existing AppManager/working/apache/tomcat folder to include the base build version, e.g., tomcat_old_9_16861.
Rename the New Tomcat Folder
Rename the newly copied AppManager/working/apache/tomcat_9_new folder to tomcat.
Copy Keystore File
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.
Copy Configuration Backup
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).
Copy the Webapps Folder
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.
Update Keystore and Truststore Files in server.xml
Open the server.xml file in the AppManager/working/apache/tomcat_old_9_16861/conf/backup directory.
Locate the <Connector> element(s) with the SSLEnabled attribute set to true.
Note down the paths for truststoreFile and keystoreFile attributes, if they exist.
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.
Update the server.xml file in the new Tomcat configuration to reflect these paths if necessary.
- Update TLSv1.3 Ciphers (Applicable only to APM version less than 170000)
- Open the server.xml file in the AppManager/working/apache/tomcat/conf/backup directory.
- Locate the <Connector> element(s) with SSLEnabled="true".
- Update the ciphers attribute to TOMCAT_CIPHERS. This will apply a default, secure set of ciphers.
Note: You can skip this step if you prefer to configure your own custom ciphers. - Use TOMCAT_CIPHERS Variable (Applicable only when upgrading to APM version 176600) - Optional
- Open the server.xml file in the AppManager/working/apache/tomcat/conf/backup directory.
- Locate the <Connector> element(s) with SSLEnabled="true".
- Update the ciphers attribute to TOMCAT_CIPHERS. This will apply a default, secure set of ciphers.
Note: You can skip this step if you prefer to configure your own custom ciphers.
New to ADSelfService Plus?
Related Articles
Add Amazon Monitor with Required IAM Permissions
This article explains how to add Amazon monitors using only the required APIs (Custom IAM Policy - second method ↓) Methods to Configure IAM Permissions for Amazon Monitoring Read Only Access (AWS Managed Policy - Recommended) This predefined policy ...