Skip to main content
Jamf Nation, hosted by Jamf, is the largest Apple IT management community in the world. Dialog with your fellow IT professionals, gain insight about Apple device deployments, share best practices and bounce ideas off each other. Join the conversation.

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

  1. Customize the /path/to/Tomcat/ROOT/WEB-INF/classes/mq/ file with the following, entering your broker URI, broker port, username, and password:
    mq.uri=tcp://<broker URI>:<broker port>
    Note: Ensure the URI and port specified here are applicable to the Jamf Pro server.
  2. 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/ file, back up your file before upgrading. After upgrading, re-upload your file before starting Jamf Pro.

Like Comment