Copy the Necessary URLs

1. In a web browser, open the Tomcat 8 download page:
   https://tomcat.apache.org/download-80.cgi

2. If you need the latest version of Tomcat:

   1. On the Tomcat 8 download page, navigate to Tomcat 8.5.x > Binary Distributions > Core.

   2. Right-click the "tar.gz" link, and choose Copy Link to copy the URL.

   3. Paste the copied URL into a document for reference, or paste it directly into the download command (see below).

   4. On the Tomcat 8 download page, right-click the "sha512" link, and choose Copy Link to copy the URL.

   5. Paste the copied URL into a document for reference, or paste it directly into the download command (see below).

3. If you need a previous version of Tomcat:

   1. On the Tomcat 8 download page, navigate to the Quick Navigation section and click Archives.

   2. Click the folder for the version of Tomcat that you want.

   3. Click the bin/ folder.

   4. Right-click the "apache-tomcat-8.5.x.tar.gz" link, and choose Copy Link to copy the URL.

   5. Paste the copied URL into a document for reference, or paste it directly into the download command (see below).

   6. 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.

   7. Paste the copied URL into a document for reference, or paste it directly into the download command (see below).

Prepare the System for Tomcat

Step 3: Create 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

Complete the following steps to create a Tomcat service:

1. Using your preferred text editor, create a tomcat systemd service file with a command similar to:

   sudo vi /etc/systemd/system/tomcat.service

2. Paste the following into the tomcat.service file:

   [Unit]
   Description=Jamf Pro Web Application Container
   Wants=network.target
   After=syslog.target network.target

   [Service]
   Type=forking

   Environment=JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
   Environment=CATALINA_PID=/opt/tomcat/temp/tomcat.pid
   Environment=CATALINA_HOME=/opt/tomcat
   Environment=CATALINA_BASE=/opt/tomcat
   Environment='CATALINA_OPTS=-server -XX:+UseParallelGC'
   Environment='JAVA_OPTS=-Djava.awt.headless=true -Djava.net.preferIPv4Stack=true'

   ExecStart=/opt/tomcat/bin/startup.sh
   ExecStop=/opt/tomcat/bin/shutdown.sh

   User=tomcat
   Group=tomcat
   UMask=0007
   RestartSec=10
   Restart=always

   [Install]
   WantedBy=multi-user.target 

3. Ensure the JAVA_HOME value in the tomcat.service file matches the path to the JDK installed on the system, not including /bin/java at the end (see above for guidance on finding this path).

4. Save the tomcat.service file.

5. Restart the systemd daemon by executing:

   sudo systemctl daemon-reload

6. Start the Tomcat service by executing:

   sudo systemctl start tomcat

7. To check the status of Tomcat, execute:

   systemctl status tomcat

   Note: You need to press the Q key to exit from the status reporting.

8. Enable auto startup of the Tomcat service at boot by executing:

   sudo systemctl enable tomcat

Step 4: Install the Jamf Pro Server Tools CLI

1. Download the Jamf Pro Server Tools CLI. For instructions, see the following article:
   The Jamf Pro Server Tools Command-Line Interface

2. Configure the Tomcat directory by executing a command similar to the following:

   jamf-pro config set --tomcat-dir /opt/tomcat

3. Configure the Tomcat service by executing a command similar to the following:

   jamf-pro config set --tomcat-service tomcat.service

It is highly recommended that you regularly create backups as you work toward a fully configured and operational Jamf Pro. For instructions, see Backing Up the Database.

Step 5: Create 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: Allocate Additional Memory to Tomcat

1. Open Terminal.

2. Set the minimum Tomcat memory by executing the following command:

   jamf-pro server config set --min-memory 256M

3. Set the maximum Tomcat memory by executing the following command:

   jamf-pro server config set --max-memory 512M

Step 7: Configure 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.

1. Check to see if the firewall is running by executing the following command:

   sudo ufw status

2. If the firewall is not running, enable it by executing the following command:

   sudo ufw enable

3. Edit the firewall configuration to allow access to port 8443 by executing the following commands:

   sudo ufw allow 8443/tcp

   sudo ufw reload

For more information, see the following webpage:
https://ubuntu.com/server/docs/security-firewall

Step 8: Install Jamf Pro

1. (Optional) Create a /tmp/jamf directory in which to temporarily store downloads, tools, and scripts for Jamf Pro by executing:

   mkdir /tmp/jamf

2. (Optional) Copy the ROOT.war file from the Jamf Pro manual download archive to the /tmp/jamf directory that you just created.

3. Stop the Tomcat service by executing:

   sudo systemctl stop tomcat

   or

   sudo service tomcat stop

4. Move the default Tomcat web app out of the way by executing:

   sudo mv /opt/tomcat/webapps/ROOT /opt/tomcat/webapps/TOMCAT

5. Copy the Jamf Pro web app archive to the Tomcat webapps directory by executing a command similar to the following:

   sudo cp /tmp/jamf/ROOT.war /opt/tomcat/webapps/

6. Assign appropriate access to the ROOT.war by executing:

   sudo chown tomcat:tomcat /opt/tomcat/webapps/ROOT.war
   sudo chmod 750 /opt/tomcat/webapps/ROOT.war

7. Generate a keystore to enable SSL for Tomcat by executing a command similar to the following with the keypass, storepass, dname, and validity values customized for your environment:

   sudo keytool -genkey -alias tomcat -keyalg RSA -keypass
   "changeit" -storepass "changeit" -dname "CN=jamf.mycompany.com,
   OU=Jamf IT, O=Jamf, L=Minneapolis, ST=MN, C=US"
   -keystore /opt/tomcat/keystore -validity <numdays>

   Make sure to enter the following attributes as appropriate to your site:

   Attribute	Value	Example
   CN=	Fully qualified domain name of the server	jamf.mycompany.com
   OU=	Organizational unit	Jamf IT
   O=	Organization	Jamf
   L=	Location (city or office)	Minneapolis
   ST=	State, province, or county	MN
   C=	Country or region	US

8. Back up the Tomcat server.xml configuration file by executing:

   sudo cp /opt/tomcat/conf/server.xml /opt/tomcat/conf/server.xml.bak

9. Open the server.xml configuration file in a text editor with a command similar to:

   sudo vi /opt/tomcat/conf/server.xml

10. Locate the following comment section in the file (note that this is the Connector on port 8443 not the Connector on port 8443 with HTTP/2 section):

    <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
            This connector uses the NIO implementation.
            ...
    -->

11. Replace the commented out (initial <!-- and trailing -->) Connector tag immediately following the comment (shown in "a" below) with the Connector tag text shown in "b" below:
    a.

    <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
         ...
    -->
    <!--
    <Connector port="8443" ...
      ...
    </Connector>
    -->

    b.

    <Connector URIEncoding="UTF-8"
               server="Apache Tomcat"
               port="8443"
               executor="tomcatThreadPool"
               SSLEnabled="true"
               maxPostSize="-1"
               scheme="https"
               protocol="org.apache.coyote.http11.Http11Nio2Protocol"
               sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"
               secure="true">
      <SSLHostConfig sslProtocol="TLS"
                     protocols="TLSv1.2"
                     honorCipherOrder="true"
                     certificateVerification="none"
                     ciphers="TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
                              TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
                              TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384,
                              TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384,
                              TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
                              TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
                              TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256,
                              TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256,
                              TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,
                              TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,
                              TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
                              TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,
                              TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384,
                              TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384,
                              TLS_ECDH_RSA_WITH_AES_256_CBC_SHA,
                              TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA,
                              TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,
                              TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,
                              TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,
                              TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,
                              TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256,
                              TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256,
                              TLS_ECDH_RSA_WITH_AES_128_CBC_SHA,
                              TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA" >
        <Certificate type="RSA"
                     certificateKeystoreFile="/opt/tomcat/keystore"
                     certificateKeystorePassword="changeit" />
      </SSLHostConfig>
    </Connector>

12. Before saving the file, ensure the keystorePass value is set to the value you used for storepass when creating the keystore.

13. Save the server.xml file.

14. Open the log4j2.xml file and change all of the log file paths from the following:

    fileName="/Library/JSS/Logs/[filename].log"
    filePattern="/Library/JSS/Logs/[filename].log.%i">

    to:

    fileName="/usr/local/jss/logs/[filename].log"
    filePattern="/usr/local/jss/logs/[filename].log.%i">

15. Start the Tomcat service by executing:

    sudo systemctl start tomcat

    or

    sudo service tomcat start

    The Tomcat service will automatically unpack the ROOT.war file into a ROOT directory in the webapps directory.

Step 9: (Optional) Disable 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 following article: Disabling TLS 1.0 and 1.1 in Java 11.

Step 10: Connect to the Jamf Pro Server

1. Configure the database connection settings using Jamf Pro Server Tools GUI or CLI. For instructions, see the Editing the Database Connection Using Jamf Pro Server Tools article.

2. Access Jamf Pro by opening a web browser and typing the protocol, IP address or hostname of the server, and port. For example: https://jamf.mycompany.com:8443/

   Note: Some web browsers may initially prevent access to Jamf Pro on port 8443 and may produce an "invalid certificate" error. If this error occurs, do the following:

   1. Enter your Jamf Pro server URL in the web browser's address bar using "http" and port 8080 (e.g., "http://jamf.mycompany.com:8080").

   2. When prompted by the Jamf Pro setup assistant for the Jamf Pro URL, enter your Jamf Pro server URL using "https" and port 8443 (e.g., https://jamf.mycompany.com:8443).

   You can begin using your Jamf Pro server URL to access Jamf Pro after you have uploaded a valid certificate and restarted Tomcat. For more information, see SSL Certificate in the Jamf Pro Administrator's Guide.

Step 11: Secure Your Jamf Pro Server

Secure your Jamf Pro server by following the recommendations in the Jamf Pro Security Recommendations article.