Employing External Instances of Apache ActiveMQ Artemis on the Jamf Pro Server 9.98—10.0.0
Disclaimer: This article is no longer being updated. The Apache ActiveMQ Artemis message broker integration was removed as of Jamf Pro 10.1.0.
The Jamf Pro server (formerly the JSS) uses a message broker, Apache ActiveMQ Artemis, to handle asynchronous workflows. By default, the message broker runs embedded in Tomcat. This article explains how to use an external instance of Apache ActiveMQ Artemis for on-premise instances of the Jamf Pro server. Using an external instance of Apache ActiveMQ Artemis frees up resources on the Jamf Pro server nodes.
Employ an External Instance of Apache ActiveMQ Artemis
- Customize the /path/to/Tomcat/ROOT/WEB-INF/classes/mq/mq.properties file with the following, entering your broker URI, broker port, username, and password:
Note: Ensure the URI and port specified here are applicable to the Jamf Pro server.
mq.uri=tcp://<broker URI>:<broker port>
- Save the file, and restart the Jamf Pro server.
Warning: If you plan to upgrade to the latest Jamf Pro and have modified the /path/to/Tomcat/ROOT/WEB-INF/classes/mq/mq.properties file, back up your file before upgrading. After upgrading, re-upload your file before starting Jamf Pro.