Manually Upgrading Jamf Pro on Linux

Jamf Pro Installation and Configuration Guide for Linux 11.16.0

Solution

Application

Content Type

Technical Documentation

Utilities & Services

version

11.16.0

ft:locale

en-US

vrm_version

11.16.0

The following instructions explain how to use the ROOT.war file to manually upgrade Jamf Pro on Linux.

Requirements

Ensure you have the latest version of the Jamf Pro Server Tools command-line interface. For download and installation instructions, see the The Jamf Pro Server Tools Command-Line Interface article.
On your Linux server, create a backup of the current database. For instructions, see Backing Up and Restoring the Database Using the Jamf Pro Server Tools Command-Line Interface.

Note:

Jamf recommends that you enable HTTP Strict Transfer Security (HSTS). To enable HSTS, you must make one-time changes to the Apache Tomcat web.xml file. For instructions, see the Enabling HSTS for Jamf Pro article.

To obtain the installer, go to the Jamf Pro Download page in the Jamf Account portal.
Use the Jamf Pro Server Tools CLI to stop Tomcat. For instructions, see the Starting and Stopping Tomcat article.
Alternatively, you can execute the following command:
```
sudo systemctl stop jamf.tomcat.service
```
If you need to upgrade to Java 21, see the Migrating to Java 21 on Jamf Pro Servers article.
Move the existing ROOT.war file and ROOT folder from /usr/local/jss/tomcat/webapps/ to a location outside of that directory. Keep the older ROOT.war file and ROOT folder until the upgrade is complete.
Open the Jamf Pro Manual Installation ZIP file, and copy the ROOT.war file to /usr/local/jss/tomcat/webapps.
Use the Jamf Pro Server Tools CLI to start Tomcat. For instructions, see the Starting and Stopping Tomcat article.
Alternatively, you can execute the following command:
```
sudo systemctl start jamf.tomcat.service
```
The ROOT.war unpacks, which may take several minutes.
Stop Tomcat again.
Go to the /ROOT/WEB-INF/xml/ directory in the ROOT folder that you moved earlier, and copy the DataBase.xml file to /usr/local/jss/tomcat/webapps/ROOT/WEB-INF/xml.
When prompted, choose to overwrite the existing DataBase.xml file.
Go to the /ROOT/WEB-INF/classes/ directory in the ROOT folder that you moved earlier, and copy the ESAPI.properties and log4j2.xml files to /usr/local/jss/tomcat/webapps/ROOT/WEB-INF/classes.
If you are using memcached in your environment, also copy the cache.properties and memcached.properties files from /ROOT/WEB-INF/classes/dal/ in the ROOT folder that you moved earlier to /usr/local/jss/tomcat/webapps/ROOT/WEB-INF/classes/dal.
Start Tomcat again.

Important:

If you customized the log4j.properties file in Jamf Pro 10.30.x or earlier, you must edit the log4j2.xml file and reapply your customizations.