Apache ActiveMQ ™ -- Complex Single Broker Configuration (STOMP only)

Using ActiveMQ > User Submitted Configurations > Complex Single Broker Configuration (STOMP only)

Example of an ActiveMQ configuration with predefined queues, simple destination security (could easily update it to JAAS), complex Web Console security with Jetty JAAS, and JMX security too.

While this is a fairly detailed configuration, it locks down every ActiveMQ service. It would be ideal if ActiveMQ shipped with a default closed configuration like this.

ActiveMQ is assumed to be installed in /usr/local/activemq/ in this example.

Add this XML snippet to the web.xml for the /admin/ app, in order to enable HTTP Authentication to match the activemq.xml configuration above.

Web Console</web-resource-name> /*</url-pattern> </web-resource-collection> admins</role-name> </auth-constraint> </security-constraint>

BASIC</auth-method> ActiveMQ</realm-name> </login-config>