Installing Jamf Pro Using the Installer
Installing Jamf Pro using the installer involves the following steps:
Install the prerequisite software (if you haven't already).
Configure the firewall.
Run the Jamf Pro Installer.
Create the Jamf Pro database.
Connect to the Jamf Pro server.
(Optional) Disable TLS 1.0 and 1.1 in Java 11.
Secure your Jamf Pro server.
Jamf recommends that you install Jamf Pro before creating the Jamf Pro database. The advantage is that the Jamf Pro Server Tools CLI is installed with the Jamf Pro installer. The CLI simplifies the process of creating the database as opposed to creating the database manually. In addition, while the Jamf Pro database can be created and configured before Jamf Pro is installed, the Jamf Pro-to-MySQL connection information cannot be configured until after Jamf Pro is installed.
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
-
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 the Prerequisite Software
Java must be installed on the server where you will install Jamf Pro. MySQL must be installed on a server before you can create the Jamf Pro database.
For instructions, see the Installing Java and MySQL for Jamf Pro 10.14.0 or Later article.
MySQL is not required to be installed on the same server as the Jamf Pro web application. For more information, see Configuring Clustering Settings.
Step 2: Configuring the Firewall
The following instructions will assist you in configuring the firewall to allow inbound access on port 8443, which provides access to the Jamf Pro web application.
Red Hat Enterprise Linux
The firewall is enabled by default on Red Hat Enterprise Linux. However, the firewall must be configured to allow traffic through the port used by Jamf Pro (typically 8443).
For more information, see the following documentation from Red Hat:
Ubuntu
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 3: Running the Jamf Pro Installer
The Jamf Pro Installer for Linux installs Apache Tomcat, the Jamf Pro web app, and Jamf Pro Server Tools.
Step 4: Creating the Jamf Pro Database
You must create a MySQL database before you can use Jamf Pro. For instructions, see the Creating the Jamf Pro Database Using the Jamf Pro Server Tools Command-Line Interface article.
Step 5: Connecting to the Jamf Pro Server
Step 6: (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 because they are deprecated. For instructions, see the Disabling TLS 1.0 and 1.1 in Java 11 article.
Step 7: Securing Your Jamf Pro Server
Secure your Jamf Pro server by following the recommendations in the Jamf Pro Security Recommendations article.
Installed Files and Folders
The following files and folders are installed when you run the Jamf Pro Installer:
- Jamf Pro web app
The files that make up the Jamf Pro web app are stored in the following location:
/usr/local/jss/tomcat/webapps/ROOT/
- Apache Tomcat
Tomcat is the web application server that runs the Jamf Pro web app. A directory named tomcat is installed in the following location:
/usr/local/jss/
For more information about the version of Tomcat installed by the Jamf Pro Installer, see the Apache Tomcat Versions Installed by the Jamf Pro Installer article.
- jamf.tomcat8
This is the service file for Tomcat. It is installed in the following location:
/etc/systemd/system/jamf.tomcat8.service
- server.xml
The Jamf Pro Installer installs a modified copy of Tomcat's server.xml file. This file enables SSL, ensures that Jamf Pro appears in the
root
context, and enables database connection pooling. It is installed in the following location:/usr/local/jss/tomcat/conf/
- keystore
Tomcat requires a keystore file to provide connections over SSL. The Jamf Pro Installer creates a default .keystore file and stores it in the following location:
/usr/local/jss/tomcat/
- Jamf Pro Server Tools
Jamf Pro Server Tools, filename server-tools-gui.jar, is installed in the following location:
/usr/local/jss/bin/
Jamf Pro Server Tools also has a command-line interface (CLI), filename jamf-pro, that is installed in the same location.
Note:The Jamf Pro installer for Linux includes only the 64-bit version of the CLI. If you are using 32-bit Linux, you must manually download and use the 32-bit version of the CLI. For instructions, see the Using the Jamf Pro Server Tools Command-Line Interface article.
- Database backup location
By default, Jamf Pro Server Tools stores database backups in the following location:
/usr/local/jss/backups/database/
- Logs
Logs for the installation and for the Jamf Pro server are stored in the following location:
/usr/local/jss/logs/