Manually Installing Jamf Pro: Ubuntu
This section provides a basic set of steps for manually installing and configuring Jamf Pro on Ubuntu LTS Server.
The supporting scripts and configuration used for manual installation differ from an installation using the Jamf Pro Installer for Linux. If you do not want to manually install Jamf Pro, you can use the Jamf Pro Installer for Linux. For information about obtaining the installer and installation instructions, see Installing Jamf Pro Using the Installer.
If you are upgrading to Tomcat 8.5, you will need to manually modify the server.xml file to make it compatible with Tomcat 8.5. For more information, see the Server.xml Changes for Tomcat 8.5 article.
Follow the step-by-step instructions in this section to install and configure Jamf Pro on Ubuntu LTS Server.
General Requirements
The Jamf Pro web app and the MySQL database can be installed on the same server or different servers. You may want to install the MySQL database on a different server if you have a larger environment that requires more resources. Additional configuration is required to implement this scenario. For more information, see Installing the Jamf Pro Web App and MySQL on Different Servers.
The server used to host Jamf Pro should meet the minimum requirements for operating system, Tomcat version, database configuration, and Java installation. For additional information on these Jamf Pro Server Environment requirements, see the Jamf Pro Release Notes for your version of Jamf Pro.
In addition, the following resources are recommended as the minimum allocation for a typical installation of Jamf Pro:
- Linux
A 64-bit capable Intel processor
8 GB of RAM
150 GB of disk space available
The "wget" utility installed
Ports 8443 and 8080 available
- Jamf Pro web app (ROOT.war)—To obtain this item in the Jamf Pro manual installation archive, log in to Jamf Account and navigate to the Products page for Jamf Pro.
- Jamf Pro Server Tools Command-Line Interface (CLI)—Instructions for obtaining this item are provided below.
Each installation of Jamf Pro and its required services is unique, and requirements, such as Jamf Pro web app memory, may vary depending on your implementation. For information about allocating additional memory to the Jamf Pro web app, see Jamf Pro Web App Memory.
If you have questions regarding scaling your environment's resources beyond the typical recommendations, contact Jamf Support.
Step 1: Installing Java and MySQL
Java and MySQL must be installed on the server before you can create the Jamf Pro database and install Jamf Pro. For instructions, see the Installing Java and MySQL for Jamf Pro 10.14.0 or Later article.
Step 2: Installing Tomcat
Apache Tomcat is the web application server that runs Jamf Pro.
Jamf tests each version of Jamf Pro with the corresponding version of Tomcat listed in the Apache Tomcat Versions Installed by the Jamf Pro Installer article. You are highly encouraged to install the version of Tomcat associated with the version of Jamf Pro you are installing.
You will need URLs to download and verify the Tomcat binary distribution that you intend to install. If you have access to a web browser on the Ubuntu system or if you are remotely connected to an Ubuntu shell session from your computer, you may want to copy these URLs just before executing the download commands. If not, you may want to copy the URLs into a text document for reference as you type them.
Copy the necessary URLs:
In a web browser, open the Tomcat 8 download page: https://tomcat.apache.org/download-80.cgi
If you need the latest version of Tomcat:
On the Tomcat 8 download page, navigate to
.Right-click the "tar.gz" link, and choose Copy Link to copy the URL.
Paste the copied URL into a document for reference, or paste it directly into the download command (see below).
On the Tomcat 8 download page, right-click the "sha512" link, and choose Copy Link to copy the URL.
Paste the copied URL into a document for reference, or paste it directly into the download command (see below).
If you need a previous version of Tomcat:
On the Tomcat 8 download page, navigate to the Quick Navigation section and click Archives.
Click the folder for the version of Tomcat that you want.
Click the bin/ folder.
Right-click the "apache-tomcat-8.5.x.tar.gz" link, and choose Copy Link to copy the URL.
Paste the copied URL into a document for reference, or paste it directly into the download command (see below).
On the Tomcat 8 webpage, right-click the "apache-tomcat-8.5.x.tar.gz.sha512" link, and choose Copy Link to copy the URL.
Paste the copied URL into a document for reference, or paste it directly into the download command (see below).
Additional notes:
Tomcat 8.5.42 is used in the commands in this section. When you execute the commands, substitute "8.5.42" with the specific version of Tomcat 8.5.x that you want to install. The most recent version of Tomcat 8.5.x can be downloaded from the following page: https://tomcat.apache.org/download-80.cgi
You may need to install the "wget" utility to execute the commands found in this guide. Install "wget" by executing:
sudo yum install wget
Step 3: Creating a Tomcat Management Service
You will need to know the path to the base Java folder (the path without /bin/java
at the end) to provide it as the JAVA_HOME
environment variable in the management service. The specific path to Java will vary depending on the platform, OS version, OpenJDK vs. Oracle JDK, etc.
Following are different methods that you can use to find the path to Java on your system:
Reference the
JAVA_HOME
environment variable:$ echo $JAVA_HOME /usr/lib/jvm/java-11-openjdk-amd64
Use
update-alternatives
:$ sudo update-alternatives --config java There is only one alternative in link group java (providing /usr/bin/java): /usr/lib/jvm/java-11-openjdk-amd64/bin/java Nothing to configure.
Use
whereis
to find "java" and follow the breadcrumbs:$ whereis java java: /usr/bin/java /usr/share/java /usr/share/man/man1/java.1.gz $ ls -la /usr/bin | grep java$ lrwxrwxrwx 1 root root 22 Jun 26 11:29 java -> /etc/alternatives/java $ ls -la /etc/alternatives | grep java$ lrwxrwxrwx 1 root root 43 Jun 26 11:32 java -> /usr/lib/jvm/java-11-openjdk-amd64/bin/java
Step 4: Installing the Jamf Pro Server Tools CLI
Jamf highly recommends that you regularly create backups as you work toward a fully configured and operational Jamf Pro. For instructions, see Backing Up the Database.
You can also download the Jamf Pro Server Tools GUI by clicking the following link: https://archive.services.jamfcloud.com/jamf-pro-server-tools/release/latest/gui/server-tools.jar
For more information, see the Jamf Pro Server Tools Overview article.
Step 5: Creating the Jamf Pro Database
You can create the Jamf Pro database using one of the following methods
- Method 1: Creating the Jamf Pro Database Using the Jamf Pro Server Tools CLI—
Follow the instructions in the Creating the Jamf Pro Database Using the Jamf Pro Server Tools Command-Line Interface article.
- Method 2: Manually Creating the Jamf Pro Database—
Follow the instructions in the Manually Creating the Jamf Pro Database article.
Step 6: Allocating Additional Memory to Tomcat
To accommodate a large number of computers in Jamf Pro, it may be necessary to allocate additional Java Virtual Machine (JVM) memory to Tomcat. If there are other services running on your server, make sure to leave enough memory to accommodate them when configuring the --max-memory
setting with Jamf Pro Server Tools.
Step 7: Configuring the Firewall
The firewall is not enabled by default in Ubuntu. However, it is highly recommended that you enable and configure the firewall on any production systems.
For more information, see Firewall in the Ubuntu Server Guide.
Step 8: Installing Jamf Pro
Step 9: (Optional) Disabling TLS 1.0 and 1.1 in Java 11
If you are using the TLS 1.0 or 1.1 protocols in Java 11 for any existing workflows, it is recommended that you disable them since they are deprecated. For instructions, see the Disabling TLS 1.0 and 1.1 in Java 11 article.
Step 10: Connecting to the Jamf Pro Server
Step 11: Securing Your Jamf Pro Server
Secure your Jamf Pro server by following the recommendations in the Jamf Pro Security Recommendations article.