activemq.xml - mcollective version 2.12.5

<!–

    Licensed to the Apache Software Foundation (ASF) under one or more
    contributor license agreements.  See the NOTICE file distributed with
    this work for additional information regarding copyright ownership.
    The ASF licenses this file to You under the Apache License, Version 2.0
    (the "License"); you may not use this file except in compliance with
    the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

–> <!– START SNIPPET: example –> <beans

    xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
    http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">

      <!-- Allows us to use system properties as variables in this configuration file -->
      <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
          <property name="locations">
              <value>file:${activemq.conf}/credentials.properties</value>
          </property>
      </bean>

      <!--
          The <broker> element is used to configure the ActiveMQ broker.
      -->
      <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">

          <destinationPolicy>
              <policyMap>
                <policyEntries>
                  <policyEntry topic=">" >
                      <!-- The constantPendingMessageLimitStrategy is used to prevent
                           slow topic consumers to block producers and affect other consumers
                           by limiting the number of messages that are retained
                           For more information, see:

                           http://activemq.apache.org/slow-consumer-handling.html

                      -->
                    <pendingMessageLimitStrategy>
                      <constantPendingMessageLimitStrategy limit="1000"/>
                    </pendingMessageLimitStrategy>
                  </policyEntry>
                </policyEntries>
              </policyMap>
          </destinationPolicy>

          <!--
              The managementContext is used to configure how ActiveMQ is exposed in
              JMX. By default, ActiveMQ uses the MBean server that is started by
              the JVM. For more information, see:

              http://activemq.apache.org/jmx.html
          -->
          <managementContext>
              <managementContext createConnector="false"/>
          </managementContext>

          <!--
              Configure message persistence for the broker. The default persistence
              mechanism is the KahaDB store (identified by the kahaDB tag).
              For more information, see:

              http://activemq.apache.org/persistence.html
          -->
          <persistenceAdapter>
              <kahaDB directory="${activemq.data}/kahadb"/>
          </persistenceAdapter>

          <plugins>
            <statisticsBrokerPlugin/>

            <!--
              This configures the users and groups used by this broker. Groups
              are referenced below, in the write/read/admin attributes
              of each authorizationEntry element.
            -->
            <simpleAuthenticationPlugin>
              <users>
                <authenticationUser username="mcollective" password="marionette" groups="mcollective,everyone"/>
                <authenticationUser username="admin" password="secret" groups="mcollective,admins,everyone"/>
              </users>
            </simpleAuthenticationPlugin>

            <!--
              Configure which users are allowed to read and write where. Permissions
              are organized by group; groups are configured above, in the
              authentication plugin.

              With the rules below, both servers and admin users belong to group
              mcollective, which can both issue and respond to commands. For an
              example that splits permissions and doesn't allow servers to issue
              commands, see:
              https://docs.puppetlabs.com/mcollective/deploy/middleware/activemq.html#detailed-restrictions
            -->
            <authorizationPlugin>
              <map>
                <authorizationMap>
                  <authorizationEntries>
                    <authorizationEntry queue=">" write="admins" read="admins" admin="admins" />
                    <authorizationEntry topic=">" write="admins" read="admins" admin="admins" />
                    <authorizationEntry topic="mcollective.>" write="mcollective" read="mcollective" admin="mcollective" />
                    <authorizationEntry queue="mcollective.>" write="mcollective" read="mcollective" admin="mcollective" />
                    <!--
                      The advisory topics are part of ActiveMQ, and all users need access to them.
                      The "everyone" group is not special; you need to ensure every user is a member.
                    -->
                    <authorizationEntry topic="ActiveMQ.Advisory.>" read="everyone" write="everyone" admin="everyone"/>
                  </authorizationEntries>
                </authorizationMap>
              </map>
            </authorizationPlugin>
          </plugins>

          <sslContext>
            <sslContext
                keyStore="activemq.keystore" keyStorePassword="notsecret"
                trustStore="activemq.truststore" trustStorePassword="notsecret"
                />
          </sslContext>

            <!--
              The systemUsage controls the maximum amount of space the broker will
              use before disabling caching and/or slowing down producers. For more information, see:
              http://activemq.apache.org/producer-flow-control.html
            -->
            <systemUsage>
              <systemUsage>
                  <memoryUsage>
                      <memoryUsage percentOfJvmHeap="70" />
                  </memoryUsage>
                  <storeUsage>
                      <storeUsage limit="100 gb"/>
                  </storeUsage>
                  <tempUsage>
                      <tempUsage limit="50 gb"/>
                  </tempUsage>
              </systemUsage>
          </systemUsage>

          <!--
              The transport connectors expose ActiveMQ over a given protocol to
              clients and other brokers. For more information, see:

              http://activemq.apache.org/configuring-transports.html
          -->
          <transportConnectors>
              <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
              <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
              <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
              <transportConnector name="stomp+ssl" uri="stomp+ssl://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
              <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
              <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
          </transportConnectors>

          <!-- destroy the spring context on shutdown to stop jetty -->
          <shutdownHooks>
              <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
          </shutdownHooks>

      </broker>

      <!--
          Enable web consoles, REST and Ajax APIs and demos
          The web consoles requires by default login, you can disable this in the jetty.xml file

          Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
      -->
      <import resource="jetty.xml"/>

</beans> <!– END SNIPPET: example –>