2 xmlns="http://www.springframework.org/schema/beans"
3 xmlns:amq="http://activemq.apache.org/schema/core"
4 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
5 xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
6 http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd
7 http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
9 <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
10 <property name="locations">
11 <value>file:${activemq.base}/conf/credentials.properties</value>
16 For more information about what MCollective requires in this file,
17 see http://docs.puppetlabs.com/mcollective/deploy/middleware/activemq.html
21 WARNING: The elements that are direct children of <broker> MUST BE IN
22 ALPHABETICAL ORDER. This is fixed in ActiveMQ 5.6.0, but affects
23 previous versions back to 5.4.
24 https://issues.apache.org/jira/browse/AMQ-3570
27 <!-- In a network of brokers, the brokerName attribute must be unique. -->
28 <broker xmlns="http://activemq.apache.org/schema/core" brokerName="broker3" useJmx="true" schedulePeriodForDestinationPurge="60000">
30 MCollective generally expects producer flow control to be turned off.
31 It will also generate a limitless number of single-use reply queues,
32 which should be garbage-collected after about five minutes to conserve
35 For more information, see:
36 http://activemq.apache.org/producer-flow-control.html
41 <policyEntry topic=">" producerFlowControl="false"/>
42 <policyEntry queue="*.reply.>" gcInactiveDestinations="true" inactiveTimoutBeforeGC="300000" />
48 <managementContext createConnector="false"/>
52 Configure message persistence for the broker. MCollective only
53 requires this in a network of brokers, where it's used to prevent
56 The default persistence mechanism is the KahaDB store (identified by
57 the kahaDB tag). For more information, see:
59 http://activemq.apache.org/persistence.html
62 <kahaDB directory="${activemq.base}/data/kahadb"/>
66 <statisticsBrokerPlugin/>
69 This configures the users and groups used by this broker. Groups
70 are referenced below, in the write/read/admin attributes
71 of each authorizationEntry element.
73 <simpleAuthenticationPlugin>
75 <authenticationUser username="amq" password="secret" groups="admins,everyone"/>
76 <authenticationUser username="mcollective" password="marionette" groups="mcollective,everyone"/>
77 <authenticationUser username="admin" password="secret" groups="mcollective,admins,everyone"/>
79 </simpleAuthenticationPlugin>
82 Configure which users are allowed to read and write where. Permissions
83 are organized by group; groups are configured above, in the
84 authentication plugin.
86 With the rules below, both servers and admin users belong to group
87 mcollective, which can both issue and respond to commands. For an
88 example that splits permissions and doesn't allow servers to issue
90 http://docs.puppetlabs.com/mcollective/deploy/middleware/activemq.html#detailed-restrictions
95 <authorizationEntries>
96 <authorizationEntry queue=">" write="admins" read="admins" admin="admins" />
97 <authorizationEntry topic=">" write="admins" read="admins" admin="admins" />
98 <authorizationEntry topic="mcollective.>" write="mcollective" read="mcollective" admin="mcollective" />
99 <authorizationEntry queue="mcollective.>" write="mcollective" read="mcollective" admin="mcollective" />
101 The advisory topics are part of ActiveMQ, and all users need access to them.
102 The "everyone" group is not special; you need to ensure every user is a member.
104 <authorizationEntry topic="ActiveMQ.Advisory.>" read="everyone" write="everyone" admin="everyone"/>
105 </authorizationEntries>
108 </authorizationPlugin>
112 The systemUsage controls the maximum amount of space the broker will
113 use for messages. For more information, see:
114 http://docs.puppetlabs.com/mcollective/deploy/middleware/activemq.html#memory-and-temp-usage-for-messages-systemusage
119 <memoryUsage limit="20 mb"/>
122 <storeUsage limit="1 gb" name="foo"/>
125 <tempUsage limit="100 mb"/>
131 The transport connectors allow ActiveMQ to listen for connections over
132 a given protocol. MCollective uses Stomp, and other ActiveMQ brokers
133 use OpenWire. You'll need different URLs depending on whether you are
134 using TLS. For more information, see:
136 http://docs.puppetlabs.com/mcollective/deploy/middleware/activemq.html#transport-connectors
138 <transportConnectors>
139 <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/>
140 <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:61613"/>
141 <!-- If using TLS, uncomment this and comment out the previous connector:
142 <transportConnector name="stomp+ssl" uri="stomp+ssl://0.0.0.0:61614?needClientAuth=true"/>
144 </transportConnectors>
148 Enable web consoles, REST and Ajax APIs and demos.
149 It also includes Camel (with its web console); see ${ACTIVEMQ_HOME}/conf/camel.xml for more info.
151 See ${ACTIVEMQ_HOME}/conf/jetty.xml for more details.
153 <import resource="jetty.xml"/>