A clustered environment is one that has multiple instances of the Jamf Pro web app pointing to the same database. Clustering is useful in large environments that require multiple web apps, or environments with a web app in the DMZ. Starting with Jamf Pro 10.46.0, Memcached is required for clustered and multi-context environments. For more information on installing and configuring Memcached, see the Memcached Installation and Configuration for Jamf Pro Environments article.
When setting up a clustered environment, it is recommended that you configure the Clustering settings in Jamf Pro using the web app that you plan to make the primary, and then install other Jamf Pro web apps that point to the same database. However, if you already have multiple Jamf Pro web apps installed and pointed to the same database, you can configure the Clustering settings in Jamf Pro after the fact. For more information on setting up a clustered environment, contact your Jamf account representative.
The Clustering settings in Jamf Pro allow you to configure the frequency at which clustered web apps are synced with the database, and specify which web app should function as the primary.
The primary web app handles tasks such as upgrading the database schema and flushing logs from the database.
Jamf Pro also allows you to view a list of web apps that are pointed to the same database and information about them.
To cluster web apps that are not in the DMZ, you need a load balancer with the address of the Jamf Pro server. For example: https://JAMF_PRO_URL.com:8443
The load balancer should route traffic to the servers running the web app.
Memcached installed and configured
- In Jamf Pro, click Settings in the sidebar.
- In the System section, click Clustering .
- Click Edit .
- Configure the settings on the pane. To specify which web app should function as the primary, select the Primary option for the web app.
- Click Save .
- If you already have multiple Jamf Pro web apps pointed to the same database, restart Tomcat on any of the web apps for the changes to take effect. For instructions on how to restart Tomcat, see the Starting and Stopping Tomcat article.