As of Jamf Pro 11.6.0, Memcached and Java 21 are required for all Jamf Pro environments, and Ehcache is no longer supported. Previously, Memcached was only required for clustered environments, and Ehcache could be used as an alternative.
This article explains how to install and configure Memcached on a Linux server to enable caching on on-premise installations of Jamf Pro. Jamf recommends using Memcached on a Linux server when Jamf Pro is installed on either a Linux or Windows server. Memcached installation steps are provided below for Red Hat Enterprise Linux and Ubuntu.
Memcached is generally used to support distributed caching across any number of Jamf Pro instances or dedicated Memcached servers. Distributed caching ensures that clustered environments do not have stale cached information.
Consider the following recommendations when configuring Memcached for use with Jamf Pro:
Configure Memcached to run on a separate server from Tomcat to maximize resource allocation. Memcached can, however, be configured on a server alongside Tomcat if necessary. There is no limit to the number of Memcached instances which may be used.
Configure Memcached instances within your network to not be publicly accessible, thus limiting access to only the Jamf Pro servers.
Utilize at least two instances of Memcached to maximize fault tolerance. If an instance becomes unavailable, the client will remove it from the pool. When the instance becomes available, the client then returns it to the pool. Each Memcached instance becomes a part of the whole. For example, having two 1 GB instances gives your entire cache 2 GB of memory.
Unless you are configuring Memcached for a multi-context Jamf Pro environment, do not specify a unique ID using the memcached.uniqueId property in the memcached.properties file. Jamf Pro will generate a unique ID automatically. If you specify a unique ID, the value must be unique for each Jamf Pro context and common to all nodes with each context.