renamed config to broker.xml

artemis-bootstrap/src/main/java/org/apache/activemq/artemis/cli/commands/Create.java

@@ -159,7 +159,7 @@ public class Create implements Action
 
       write("etc/logging.properties", null, false);
       write("etc/bootstrap.xml", null, false);
-      write("etc/activemq-configuration.xml", filters, false);
+      write("etc/broker.xml", filters, false);
       write("etc/activemq-roles.properties", null, false);
       write("etc/activemq-users.properties", null, false);
 

artemis-bootstrap/src/main/resources/org/apache/activemq/artemis/cli/commands/bin/activemq-service.xml

@@ -32,7 +32,7 @@
    <argument>-Xms512M</argument>
    <argument>-Xmx1024M</argument>
 
-   <!-- Cluster Properties: Used to pass arguments to ActiveMQ which can be referenced in activemq-configuration.xml
+   <!-- Cluster Properties: Used to pass arguments to ActiveMQ which can be referenced in broker.xml
    <argument>-Dactivemq.remoting.default.port=61617</argument>
    <argument>-Dactivemq.remoting.amqp.port=5673</argument>
    <argument>-Dactivemq.remoting.stomp.port=61614</argument>

artemis-bootstrap/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/activemq.profile

@@ -17,7 +17,7 @@
 
 ACTIVEMQ_HOME='${activemq.home}'
 
-# Cluster Properties: Used to pass arguments to ActiveMQ which can be referenced in activemq-configuration.xml
+# Cluster Properties: Used to pass arguments to ActiveMQ which can be referenced in broker.xml
 #ACTIVEMQ_CLUSTER_PROPS="-Dactivemq.remoting.default.port=61617 -Dactivemq.remoting.amqp.port=5673 -Dactivemq.remoting.stomp.port=61614 -Dactivemq.remoting.hornetq.port=5446"
 
 # Java Opts

artemis-bootstrap/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/activemq.profile.cmd

@@ -17,7 +17,7 @@ rem under the License.
 
 set ACTIVEMQ_HOME=${activemq.home}
 
-rem Cluster Properties: Used to pass arguments to ActiveMQ which can be referenced in activemq-configuration.xml
+rem Cluster Properties: Used to pass arguments to ActiveMQ which can be referenced in broker.xml
 rem set ACTIVEMQ_CLUSTER_PROPS=-Dactivemq.remoting.default.port=61617 -Dactivemq.remoting.amqp.port=5673 -Dactivemq.remoting.stomp.port=61614 -Dactivemq.remoting.hornetq.port=5446
 
 rem Java Opts

artemis-bootstrap/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/bootstrap.xml

@@ -24,7 +24,7 @@
            default-user="guest"
            />
 
-   <server configuration="file:${activemq.instance}/etc/activemq-configuration.xml"/>
+   <server configuration="file:${activemq.instance}/etc/broker.xml"/>
 
    <web bind="http://localhost:8161" path="web">
        <app url="jolokia" war="jolokia-war-1.2.3.war"/>

artemis-bootstrap/src/test/java/org/apache/activemq/artemis/test/FileBrokerTest.java

@@ -30,7 +30,7 @@ public class FileBrokerTest
    public void startWithJMS() throws Exception
    {
       ServerDTO serverDTO = new ServerDTO();
-      serverDTO.configuration = "activemq-configuration.xml";
+      serverDTO.configuration = "broker.xml";
       FileBroker broker = null;
       try
       {

artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/Interceptor.java

@@ -22,7 +22,7 @@ import org.apache.activemq.artemis.core.protocol.core.Packet;
  * This is class is a simple way to intercepting calls on ActiveMQ client and servers.
  * <p>
  * To add an interceptor to ActiveMQ server, you have to modify the server configuration file
- * {@literal activemq-configuration.xml}.<br>
+ * {@literal broker.xml}.<br>
  * To add it to a client, use {@link org.apache.activemq.artemis.api.core.client.ServerLocator#addIncomingInterceptor(Interceptor)}
  */
 public interface Interceptor extends BaseInterceptor<Packet>

artemis-core-client/src/main/java/org/apache/activemq/artemis/core/protocol/core/impl/ActiveMQSessionContext.java

@@ -677,7 +677,7 @@ public class ActiveMQSessionContext extends SessionContext
       ClientSession.QueueQuery queueInfo = consumerInternal.getQueueInfo();
 
       // We try and recreate any non durable queues, since they probably won't be there unless
-      // they are defined in activemq-configuration.xml
+      // they are defined in broker.xml
       // This allows e.g. JMS non durable subs and temporary queues to continue to be used after failover
       if (!queueInfo.isDurable())
       {

artemis-maven-plugin/src/main/java/org/apache/activemq/artemis/server/ActiveMQBootstrap.java

@@ -96,7 +96,7 @@ public class ActiveMQBootstrap
          {
             //extendPluginClasspath(configurationDir);
             configuration = new FileConfiguration();
-            File file = new File(new File(configurationDir), "activemq-configuration.xml");
+            File file = new File(new File(configurationDir), "broker.xml");
             jmsFileConfiguration = new FileJMSConfiguration();
             FileDeploymentManager deploymentManager = new FileDeploymentManager(file.toURI().toString());
             deploymentManager.addDeployable((FileConfiguration)configuration);

artemis-protocols/artemis-stomp-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/stomp/StompFrameInterceptor.java

@@ -22,7 +22,7 @@ import org.apache.activemq.artemis.api.core.BaseInterceptor;
  * This class is a simple way to intercepting client calls on ActiveMQ using STOMP protocol.
  * <p>
  * To add an interceptor to ActiveMQ server, you have to modify the server configuration file
- * {@literal activemq-configuration.xml}.<br>
+ * {@literal broker.xml}.<br>
  */
 public interface StompFrameInterceptor extends BaseInterceptor<StompFrame>
 {

artemis-server/src/main/java/org/apache/activemq/artemis/core/config/FileDeploymentManager.java

@@ -37,7 +37,7 @@ import org.w3c.dom.NodeList;
  */
 public class FileDeploymentManager
 {
-   private static final String DEFAULT_CONFIGURATION_URL = "activemq-configuration.xml";
+   private static final String DEFAULT_CONFIGURATION_URL = "broker.xml";
 
    private final String configurationUrl;
 

artemis-server/src/main/java/org/apache/activemq/artemis/core/deployers/Deployable.java

@@ -24,7 +24,7 @@ import javax.management.MBeanServer;
 import java.util.Map;
 
 /**
- * A Deployable is an object that can be configured via an xml configuration element in the main configuration file "activemq-configuration.xml"
+ * A Deployable is an object that can be configured via an xml configuration element in the main configuration file "broker.xml"
  * It holds all the information needed by the FileDeploymentManager to parse the configuration and build the component
  */
 public interface Deployable

artemis-server/src/main/java/org/apache/activemq/artemis/core/server/embedded/EmbeddedActiveMQ.java

@@ -38,7 +38,7 @@ public class EmbeddedActiveMQ
    protected MBeanServer mbeanServer;
 
    /**
-    * Classpath resource for activemq server config.  Defaults to 'activemq-configuration.xml'.
+    * Classpath resource for activemq server config.  Defaults to 'broker.xml'.
     *
     * @param filename
     */
@@ -94,7 +94,7 @@ public class EmbeddedActiveMQ
    {
       if (configuration == null)
       {
-         if (configResourcePath == null) configResourcePath = "activemq-configuration.xml";
+         if (configResourcePath == null) configResourcePath = "broker.xml";
          FileDeploymentManager deploymentManager = new FileDeploymentManager(configResourcePath);
          FileConfiguration config = new FileConfiguration();
          deploymentManager.addDeployable(config);

docs/user-manual/en/clusters.md

@@ -8,7 +8,7 @@ the cluster is an active Apache ActiveMQ Artemis server which manages its own me
 and handles its own connections.
 
 The cluster is formed by each node declaring *cluster connections* to
-other nodes in the core configuration file `activemq-configuration.xml`.
+other nodes in the core configuration file `broker.xml`.
 When a node forms a cluster connection to another node, internally it
 creates a *core bridge* (as described in [Core Bridges](core-bridges.md)) connection between it and
 the other node, this is done transparently behind the scenes - you don't
@@ -84,12 +84,12 @@ broadcasting technique you configure the cluster, it uses either UDP or
 JGroups to broadcast connector pairs information.
 
 Broadcast groups are defined in the server configuration file
-`activemq-configuration.xml`. There can be many broadcast groups per
+`broker.xml`. There can be many broadcast groups per
 Apache ActiveMQ Artemis server. All broadcast groups must be defined in a
 `broadcast-groups` element.
 
 Let's take a look at an example broadcast group from
-`activemq-configuration.xml` that defines a UDP broadcast group:
+`broker.xml` that defines a UDP broadcast group:
 
     <broadcast-groups>
        <broadcast-group name="my-broadcast-group">
@@ -272,7 +272,7 @@ normal Apache ActiveMQ Artemis connections.
 #### Defining Discovery Groups on the Server
 
 For cluster connections, discovery groups are defined in the server side
-configuration file `activemq-configuration.xml`. All discovery groups
+configuration file `broker.xml`. All discovery groups
 must be defined inside a `discovery-groups` element. There can be many
 discovery groups defined by Apache ActiveMQ Artemis server. Let's look at an example:
 
@@ -362,7 +362,7 @@ take a look at an example:
     connectionFactory.myConnectionFactory=udp://231.7.7.7:9876
 
 The element `discovery-group-ref` specifies the name of a discovery
-group defined in `activemq-configuration.xml`.
+group defined in `broker.xml`.
 
 When this connection factory is downloaded from JNDI by a client
 application and JMS connections are created from it, those connections
@@ -550,7 +550,7 @@ connections in general.
 Cluster connections group servers into clusters so that messages can be
 load balanced between the nodes of the cluster. Let's take a look at a
 typical cluster connection. Cluster connections are always defined in
-`activemq-configuration.xml` inside a `cluster-connection` element.
+`broker.xml` inside a `cluster-connection` element.
 There can be zero or more cluster connections defined per Apache ActiveMQ Artemis
 server.
 
@@ -775,7 +775,7 @@ connection has been made.
 
 When creating connections between nodes of a cluster to form a cluster
 connection, Apache ActiveMQ Artemis uses a cluster user and cluster password which is
-defined in `activemq-configuration.xml`:
+defined in `broker.xml`:
 
     <cluster-user>ACTIVEMQ.CLUSTER.ADMIN.USER</cluster-user>
     <cluster-password>CHANGE ME!!</cluster-password>
@@ -925,7 +925,7 @@ Message redistribution can be configured on a per address basis, by
 specifying the redistribution delay in the address settings, for more
 information on configuring address settings, please see [Queue Attributes](queue-attributes.md).
 
-Here's an address settings snippet from `activemq-configuration.xml`
+Here's an address settings snippet from `broker.xml`
 showing how message redistribution is enabled for a set of queues:
 
     <address-settings>

docs/user-manual/en/configuration-index.md

@@ -7,7 +7,7 @@ element name to go to the specific chapter.
 Server Configuration
 ====================
 
-activemq-configuration.xml
+broker.xml
 --------------------------
 
 This is the main core server configuration file which contains to elements

docs/user-manual/en/configuring-transports.md

@@ -7,7 +7,7 @@ Apache ActiveMQ Artemis transports and where and how they're configured.
 
 One of the most important concepts in Apache ActiveMQ Artemis transports is the
 *acceptor*. Let's dive straight in and take a look at an acceptor
-defined in xml in the configuration file `activemq-configuration.xml`.
+defined in xml in the configuration file `broker.xml`.
 
     <acceptors>
        <acceptor name="netty">tcp://localhost:61617</acceptor>
@@ -45,7 +45,7 @@ Whereas acceptors are used on the server to define how we accept
 connections, connectors are used by a client to define how it connects
 to a server.
 
-Let's look at a connector defined in our `activemq-configuration.xml`
+Let's look at a connector defined in our `broker.xml`
 file:
 
     <connectors>

docs/user-manual/en/connection-ttl.md

@@ -190,5 +190,5 @@ thread adds a little more latency. These packets are:
 -   `org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionXARollbackMessage`
 
 To disable asynchronous connection execution, set the parameter
-`async-connection-execution-enabled` in `activemq-configuration.xml` to
+`async-connection-execution-enabled` in `broker.xml` to
 `false` (default value is `true`).

docs/user-manual/en/core-bridges.md

@@ -38,7 +38,7 @@ server. They do this by using duplicate detection (described in [Duplicate Detec
 
 ## Configuring Bridges
 
-Bridges are configured in `activemq-configuration.xml`. Let's kick off
+Bridges are configured in `broker.xml`. Let's kick off
 with an example (this is actually from the bridge example):
 
     <bridge name="my-bridge">
@@ -84,7 +84,7 @@ Let's take a look at all the parameters in turn:
     >
     > If you're using JMS then normally the JMS configuration
     > `activemq-jms.xml` is loaded after the core configuration file
-    > `activemq-configuration.xml` is loaded. If your bridge is
+    > `broker.xml` is loaded. If your bridge is
     > consuming from a JMS queue then you'll need to make sure the JMS
     > queue is also deployed as a core queue in the core configuration.
     > Take a look at the bridge example for an example of how this is
@@ -204,12 +204,12 @@ Let's take a look at all the parameters in turn:
 -   `user`. This optional parameter determines the user name to use when
     creating the bridge connection to the remote server. If it is not
     specified the default cluster user specified by `cluster-user` in
-    `activemq-configuration.xml` will be used.
+    `broker.xml` will be used.
 
 -   `password`. This optional parameter determines the password to use
     when creating the bridge connection to the remote server. If it is
     not specified the default cluster password specified by
-    `cluster-password` in `activemq-configuration.xml` will be used.
+    `cluster-password` in `broker.xml` will be used.
 
 -   `static-connectors` or `discovery-group-ref`. Pick either of these
     options to connect the bridge to the target server.

docs/user-manual/en/diverts.md

@@ -34,7 +34,7 @@ for messages. Combining diverts with bridges allows you to create a
 distributed network of reliable routing connections between multiple
 geographically distributed servers, creating your global messaging mesh.
 
-Diverts are defined as xml in the `activemq-configuration.xml` file.
+Diverts are defined as xml in the `broker.xml` file.
 There can be zero or more diverts in the file.
 
 Please see the examples for a full working example showing you how to

docs/user-manual/en/duplicate-detection.md

@@ -109,12 +109,12 @@ size of `n` elements, then the `n + 1`th id stored will overwrite the
 `0`th element in the cache.
 
 The maximum size of the cache is configured by the parameter
-`id-cache-size` in `activemq-configuration.xml`, the default value is
+`id-cache-size` in `broker.xml`, the default value is
 `2000` elements.
 
 The caches can also be configured to persist to disk or not. This is
 configured by the parameter `persist-id-cache`, also in
-`activemq-configuration.xml`. If this is set to `true` then each id will
+`broker.xml`. If this is set to `true` then each id will
 be persisted to permanent storage as they are received. The default
 value for this parameter is `true`.
 
@@ -135,7 +135,7 @@ will be ignored.
 
 To configure a core bridge to add the duplicate id header, simply set
 the `use-duplicate-detection` to `true` when configuring a bridge in
-`activemq-configuration.xml`.
+`broker.xml`.
 
 The default value for this parameter is `true`.
 
@@ -151,7 +151,7 @@ using their internal bridges.
 
 To configure a cluster connection to add the duplicate id header, simply
 set the `use-duplicate-detection` to `true` when configuring a cluster
-connection in `activemq-configuration.xml`.
+connection in `broker.xml`.
 
 The default value for this parameter is `true`.
 

docs/user-manual/en/embedding-activemq.md

@@ -27,7 +27,7 @@ using the Apache ActiveMQ Artemis Core API or JMS.
 
 For instantiating a core Apache ActiveMQ Artemis Server only, the steps are pretty
 simple. The example requires that you have defined a configuration file
-`activemq-configuration.xml` in your classpath:
+`broker.xml` in your classpath:
 
 ``` java
 import org.apache.activemq.artemis.core.server.embedded.EmbeddedActiveMQ;
@@ -72,7 +72,7 @@ properties. See the javadocs for this class for more details.
 ## JMS API
 
 JMS embedding is simple as well. This example requires that you have
-defined the config files `activemq-configuration.xml`,
+defined the config files `broker.xml`,
 `activemq-jms.xml`, and a `activemq-users.xml` if you have security
 enabled. Let's also assume that a queue and connection factory has been
 defined in the `activemq-jms.xml` config file.

docs/user-manual/en/filter-expressions.md

@@ -11,7 +11,7 @@ please the JMS javadoc for
 Filter expressions are used in several places in Apache ActiveMQ Artemis
 
 -   Predefined Queues. When pre-defining a queue, in
-    `activemq-configuration.xml` in either the core or jms configuration a filter
+    `broker.xml` in either the core or jms configuration a filter
     expression can be defined for a queue. Only messages that match the
     filter expression will enter the queue.
 

docs/user-manual/en/ha.md

@@ -52,7 +52,7 @@ which we will cover in a later chapter.
 > **Note**
 >
 > The `ha-policy` configurations replaces any current HA configuration
-> in the root of the `activemq-configuration.xml` configuration. All old
+> in the root of the `broker.xml` configuration. All old
 > configuration is now deprecated altho best efforts will be made to
 > honour it if configured this way.
 
@@ -140,7 +140,7 @@ live server to replicate from, these are:
 -   `specifying a node group`. You can specify a group of live servers
     that a backup server can connect to. This is done by configuring
     `group-name` in either the `master` or the `slave` element of the
-    `activemq-configuration.xml`. A Backup server will only connect to a
+    `broker.xml`. A Backup server will only connect to a
     live server that shares the same node group name
 
 -   `connecting to any live`. This will be the behaviour if `group-name`
@@ -200,7 +200,7 @@ reconnecting with the live. This avoids a split brain situation.
 #### Configuration
 
 To configure the live and backup servers to be a replicating pair,
-configure the live server in ' `activemq-configuration.xml` to have:
+configure the live server in ' `broker.xml` to have:
 
     <ha-policy>
        <replication>
@@ -351,7 +351,7 @@ on amount of data).
 #### Configuration
 
 To configure the live and backup servers to share their store, configure
-id via the `ha-policy` configuration in `activemq-configuration.xml`:
+id via the `ha-policy` configuration in `broker.xml`:
 
     <ha-policy>
        <shared-store>
@@ -426,7 +426,7 @@ other server (which it assumes it is a back that has assumed its duties)
 to shutdown for it to take over. This is necessary because otherwise the
 live server has no means to know whether there was a fail-over or not,
 and if there was if the server that took its duties is still running or
-not. To configure this option at your `activemq-configuration.xml`
+not. To configure this option at your `broker.xml`
 configuration file as follows:
 
     <ha-policy>
@@ -464,7 +464,7 @@ you can do this by using the management API as explained at [Management](managem
 You can also force the running live server to shutdown when the old live
 server comes back up allowing the original live server to take over
 automatically by setting the following property in the
-`activemq-configuration.xml` configuration file as follows:
+`broker.xml` configuration file as follows:
 
     <ha-policy>
        <shared-store>
@@ -566,7 +566,7 @@ its Connectors and Acceptors which are discussed later on in this
 chapter. A live server can also be configured to allow requests from
 backups and also how many backups a live server can start. this way you
 can evenly distribute backups around the cluster. This is configured via
-the `ha-policy` element in the `activemq-configuration.xml` file like
+the `ha-policy` element in the `broker.xml` file like
 so:
 
     <ha-policy>

docs/user-manual/en/intercepting-operations.md

@@ -42,7 +42,7 @@ The returned boolean value is important:
 ## Configuring The Interceptors
 
 Both incoming and outgoing interceptors are configured in
-`activemq-configuration.xml`:
+`broker.xml`:
 
     <remoting-incoming-interceptors>
        <class-name>org.apache.activemq.jms.example.LoginInterceptor</class-name>

docs/user-manual/en/management.md

@@ -504,7 +504,7 @@ proxies of the MBeans.
 
 By default, JMX is enabled to manage Apache ActiveMQ Artemis. It can be disabled by
 setting `jmx-management-enabled` to `false` in
-`activemq-configuration.xml`:
+`broker.xml`:
 
     <!-- false to disable JMX management for Apache ActiveMQ Artemis -->
     <jmx-management-enabled>false</jmx-management-enabled>
@@ -522,7 +522,7 @@ If JMX is enabled, Apache ActiveMQ Artemis can be managed locally using `jconsol
 By default, Apache ActiveMQ Artemis server uses the JMX domain "org.apache.activemq".
 To manage several Apache ActiveMQ Artemis servers from the *same* MBeanServer, the JMX
 domain can be configured for each individual Apache ActiveMQ Artemis server by setting
-`jmx-domain` in `activemq-configuration.xml`:
+`jmx-domain` in `broker.xml`:
 
     <!-- use a specific JMX domain for ActiveMQ MBeans -->
     <jmx-domain>my.org.apache.activemq</jmx-domain>
@@ -623,7 +623,7 @@ straightforward (`core.queue.exampleQueue` for the Core Queue
 ### Configuring Core Management
 
 The management address to send management messages is configured in
-`activemq-configuration.xml`:
+`broker.xml`:
 
     <management-address>jms.queue.activemq.management</management-address>
 
@@ -633,7 +633,7 @@ messages).
 
 The management address requires a *special* user permission `manage` to
 be able to receive and handle management messages. This is also
-configured in activemq-configuration.xml:
+configured in broker.xml:
 
     <!-- users with the admin role will be allowed to manage -->
     <!-- Apache ActiveMQ Artemis using management messages        -->
@@ -741,7 +741,7 @@ of all the notifications emitted by the server.
 #### Configuring The Core Management Notification Address
 
 The management notification address to receive management notifications
-is configured in `activemq-configuration.xml`:
+is configured in `broker.xml`:
 
     <management-notification-address>activemq.notifications</management-notification-address>
 
@@ -948,7 +948,7 @@ By default, message counters are disabled as it might have a small
 negative effect on memory.
 
 To enable message counters, you can set it to `true` in
-`activemq-configuration.xml`:
+`broker.xml`:
 
     <message-counter-enabled>true</message-counter-enabled>
 
@@ -956,7 +956,7 @@ Message counters keeps a history of the queue metrics (10 days by
 default) and samples all the queues at regular interval (10 seconds by
 default). If message counters are enabled, these values should be
 configured to suit your messaging use case in
-`activemq-configuration.xml`:
+`broker.xml`:
 
     <!-- keep history for a week -->
     <message-counter-max-day-history>7</message-counter-max-day-history>

docs/user-manual/en/message-expiry.md

@@ -61,7 +61,7 @@ A reaper thread will periodically inspect the queues to check if
 messages have expired.
 
 The reaper thread can be configured with the following properties in
-`activemq-configuration.xml`
+`broker.xml`
 
 -   `message-expiry-scan-period`
 

docs/user-manual/en/message-grouping.md

@@ -104,7 +104,7 @@ choose 1 node to have a local grouping handler and all the other nodes
 should have remote handlers- it's the local handler that actually makes
 the decision as to what route should be used, all the other remote
 handlers converse with this. Here is a sample config for both types of
-handler, this should be configured in the *activemq-configuration.xml*
+handler, this should be configured in the *broker.xml*
 file.
 
     <grouping-handler name="my-grouping-handler">

docs/user-manual/en/paging.md

@@ -41,7 +41,7 @@ Consumers with selectors will also navigate through the page-files and it will i
 You can configure the location of the paging folder
 
 Global paging parameters are specified on the main configuration file
-(`activemq-configuration.xml`).
+(`broker.xml`).
 
     <configuration xmlns="urn:activemq"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -72,7 +72,7 @@ that address alone goes into page mode.
 ## Configuration
 
 Configuration is done at the address settings, done at the main
-configuration file (`activemq-configuration.xml`).
+configuration file (`broker.xml`).
 
     <address-settings>
        <address-setting match="jms.someaddress">

docs/user-manual/en/perf-tuning.md

@@ -95,21 +95,21 @@ tuning:
 
 -   Disable security. You may get a small performance boost by disabling
     security by setting the `security-enabled` parameter to `false` in
-    `activemq-configuration.xml`.
+    `broker.xml`.
 
 -   Disable persistence. If you don't need message persistence, turn it
     off altogether by setting `persistence-enabled` to false in
-    `activemq-configuration.xml`.
+    `broker.xml`.
 
 -   Sync transactions lazily. Setting `journal-sync-transactional` to
-    `false` in `activemq-configuration.xml` can give you better
+    `false` in `broker.xml` can give you better
     transactional persistent performance at the expense of some
     possibility of loss of transactions on failure. See  [Guarantees of sends and commits](send-guarantees.md)
     for more information.
 
 -   Sync non transactional lazily. Setting
     `journal-sync-non-transactional` to `false` in
-    `activemq-configuration.xml` can give you better non-transactional
+    `broker.xml` can give you better non-transactional
     persistent performance at the expense of some possibility of loss of
     durable messages on failure. See  [Guarantees of sends and commits](send-guarantees.md)
     for more information.
@@ -176,7 +176,7 @@ tuning:
 -   Use `batch-delay` and set `direct-deliver` to false for the best
     throughput for very small messages. Apache ActiveMQ Artemis comes with a
     preconfigured connector/acceptor pair (`netty-throughput`) in
-    `activemq-configuration.xml` and JMS connection factory
+    `broker.xml` and JMS connection factory
     (`ThroughputConnectionFactory`) in `activemq-jms.xml`which can be
     used to give the very best throughput, especially for small
     messages. See the [Configuring the Transport](configuring-transports.md)

docs/user-manual/en/persistence.md

@@ -129,7 +129,7 @@ the broker for Zero Persistence section.
 ## Configuring the bindings journal
 
 The bindings journal is configured using the following attributes in
-`activemq-configuration.xml`
+`broker.xml`
 
 -   `bindings-directory`
 
@@ -150,7 +150,7 @@ The jms config shares its configuration with the bindings journal.
 ## Configuring the message journal
 
 The message journal is configured using the following attributes in
-`activemq-configuration.xml`
+`broker.xml`
 
 -   `journal-directory`
 
@@ -349,7 +349,7 @@ Using aptitude, (e.g. on Ubuntu or Debian system):
 In some situations, zero persistence is sometimes required for a
 messaging system. Configuring Apache ActiveMQ Artemis to perform zero persistence is
 straightforward. Simply set the parameter `persistence-enabled` in
-`activemq-configuration.xml` to `false`.
+`broker.xml` to `false`.
 
 Please note that if you set this parameter to false, then *zero*
 persistence will occur. That means no bindings data, message data, large

docs/user-manual/en/queue-attributes.md

@@ -10,7 +10,7 @@ attribute has.
 Queues can be predefined via configuration at a core level or at a JMS
 level. Firstly let's look at a JMS level.
 
-The following shows a queue predefined in the jms element of the `activemq-configuration.xml`
+The following shows a queue predefined in the jms element of the `broker.xml`
 configuration file.
 
     <queue name="selectorQueue">
@@ -36,7 +36,7 @@ The durable element specifies whether the queue will be persisted. This
 again is optional and defaults to true if omitted.
 
 Secondly a queue can be predefined at a core level in the
-`activemq-configuration.xml` file. The following is an example.
+`broker.xml` file. The following is an example.
 
     <queues>
        <queue name="jms.queue.selectorQueue">
@@ -78,7 +78,7 @@ queues.
 
 There are some attributes that are defined against an address wildcard
 rather than a specific queue. Here an example of an `address-setting`
-entry that would be found in the `activemq-configuration.xml` file.
+entry that would be found in the `broker.xml` file.
 
     <address-settings>
        <address-setting match="jms.queue.exampleQueue">

docs/user-manual/en/rest.md

@@ -190,7 +190,7 @@ The project structure should look this like:
     `-- src
        `-- main
            `-- resources
-               `-- activemq-configuration.xml
+               `-- broker.xml
            `-- webapp
                `-- WEB-INF
                    `-- web.xml

docs/user-manual/en/security.md

@@ -2,7 +2,7 @@
 
 This chapter describes how security works with Apache ActiveMQ Artemis and how you can
 configure it. To disable security completely simply set the
-`security-enabled` property to false in the `activemq-configuration.xml`
+`security-enabled` property to false in the `broker.xml`
 file.
 
 For performance reasons security is cached and invalidated every so
@@ -54,7 +54,7 @@ specified. If the user has any of those roles, he/she will be granted
 that permission for that set of addresses.
 
 Let's take a simple example, here's a security block from
-`activemq-configuration.xml` file:
+`broker.xml` file:
 
     <security-setting match="globalqueues.europe.#">
        <permission type="createDurableQueue" roles="admin"/>

docs/user-manual/en/send-guarantees.md

@@ -22,7 +22,7 @@ storage by the time the call to commit or rollback returns.
 Setting this parameter to `false` can improve performance at the expense
 of some loss of transaction durability.
 
-This parameter is set in `activemq-configuration.xml`
+This parameter is set in `broker.xml`
 
 ## Guarantees of Non Transactional Message Sends
 

docs/user-manual/en/spring-integration.md

@@ -4,7 +4,7 @@ Apache ActiveMQ Artemis provides a simple bootstrap class,
 `org.apache.activemq.integration.spring.SpringJmsBootstrap`, for
 integration with Spring. To use it, you configure Apache ActiveMQ Artemis as you always
 would, through its various configuration files like
-`activemq-configuration.xml`, `activemq-jms.xml`, and
+`broker.xml`, `activemq-jms.xml`, and
 `activemq-users.xml`. The Spring helper class starts the Apache ActiveMQ Artemis server
 and adds any factories or destinations configured within
 `activemq-jms.xml` directly into the namespace of the Spring context.

docs/user-manual/en/thread-pooling.md

@@ -52,7 +52,7 @@ internally to a `java.util.concurrent.ScheduledThreadPoolExecutor`
 instance.
 
 The maximum number of thread used by this pool is configure in
-`activemq-configuration.xml` with the `scheduled-thread-pool-max-size`
+`broker.xml` with the `scheduled-thread-pool-max-size`
 parameter. The default value is `5` threads. A small number of threads
 is usually sufficient for this pool.
 
@@ -63,7 +63,7 @@ on the server side. It maps internally to a
 `java.util.concurrent.ThreadPoolExecutor` instance.
 
 The maximum number of thread used by this pool is configure in
-`activemq-configuration.xml` with the `thread-pool-max-size` parameter.
+`broker.xml` with the `thread-pool-max-size` parameter.
 
 If a value of `-1` is used this signifies that the thread pool has no
 upper bound and new threads will be created on demand if there are not

docs/user-manual/en/transaction-config.md

@@ -11,7 +11,7 @@ To cope with this Apache ActiveMQ Artemis can, if configured, scan for old trans
 and rollback any it finds. The default for this is 3000000 milliseconds
 (5 minutes), i.e. any transactions older than 5 minutes are removed.
 This timeout can be changed by editing the `transaction-timeout`
-property in `activemq-configuration.xml` (value must be in
+property in `broker.xml` (value must be in
 milliseconds). The property `transaction-timeout-scan-period` configures
 how often, in milliseconds, to scan for old transactions.
 

docs/user-manual/en/undelivered-messages.md

@@ -165,6 +165,6 @@ delivery count before message delivery but this feature is disabled by default
 due to performance implications.
 
 To enable it, set `persist-delivery-count-before-delivery` to `true` in
-`activemq-configuration.xml`:
+`broker.xml`:
 
     <persist-delivery-count-before-delivery>true</persist-delivery-count-before-delivery>

docs/user-manual/en/using-server.md

@@ -115,7 +115,7 @@ The configuration file used to bootstrap the server (e.g.
 `bootstrap.xml` by default) references the specific broker configuration
 files.
 
--   `activemq-configuration.xml`. This is the main ActiveMQ
+-   `broker.xml`. This is the main ActiveMQ
     configuration file. All the parameters in this file are
     described [here](configuration-index.md)
 
@@ -142,7 +142,7 @@ The bootstrap file is very simple. Let's take a look at an example:
 
     <broker xmlns="http://activemq.org/schema">
 
-       <file:core configuration="${activemq.home}/config/stand-alone/non-clustered/activemq-configuration.xml"></core>
+       <file:core configuration="${activemq.home}/config/stand-alone/non-clustered/broker.xml"></core>
 
        <basic-security/>
 
@@ -156,7 +156,7 @@ The bootstrap file is very simple. Let's take a look at an example:
 ## The main configuration file.
 
 The configuration for the Apache ActiveMQ Artemis core server is contained in
-`activemq-configuration.xml`. This is what the FileConfiguration bean
+`broker.xml`. This is what the FileConfiguration bean
 uses to configure the messaging server.
 
 There are many attributes which you can configure Apache ActiveMQ Artemis. In most

docs/user-manual/en/wildcard-routing.md

@@ -13,7 +13,7 @@ messages which are sent to a *hierarchy* of addresses.
 > In JMS terminology this allows "topic hierarchies" to be created.
 
 To enable this functionality set the property
-`wild-card-routing-enabled` in the `activemq-configuration.xml` file to
+`wild-card-routing-enabled` in the `broker.xml` file to
 `true`. This is `true` by default.
 
 For more information on the wild card syntax take a look at [wildcard syntax](wildcard-syntax.md) chapter,

examples/jms/aerogear/readme.html

@@ -79,7 +79,7 @@ under the License.
      </ol>
    <p>And on your mobile app you should see a message from ActiveMQ</p>
 
-  <p>Now lets look a bit more closely at the configuration in activemq-configuration.xml</p>
+  <p>Now lets look a bit more closely at the configuration in broker.xml</p>
      <ol>
         <pre class="prettyprint">
            <code>

examples/jms/bridge/readme.html

@@ -54,7 +54,7 @@ under the License.
      want to reject those.</p>
      <p>Moreover it is known that Aardvarks normally wear blue hats, and it's important that we only make sausages using
      Aardvarks with green hats, so on the way we are going transform the property "hat" from "green" to "blue".</p>  
-     <p>Here's a snippet from <code>activemq-configuration.xml</code> showing the bridge configuration</p>
+     <p>Here's a snippet from <code>broker.xml</code> showing the bridge configuration</p>
      <pre class="prettyprint">
      <code>
      &lt;bridge name="my-bridge"&gt;

examples/jms/client-side-load-balancing/readme.html

@@ -38,7 +38,7 @@ under the License.
      to use UDP discovery to discover the list of servers over which to round-robin. This example will use UDP
      discovery to obtain the list.</p>
      <p>This example starts three servers which all broadcast their location using UDP discovery. The UDP broadcast configuration
-     can be seen in the <code>activemq-configuration.xml</code> file.</p>
+     can be seen in the <code>broker.xml</code> file.</p>
      <p>A JMS ConnectionFactory is deployed on each server specifying the discovery group that will be used by that
      connection factory.</p>      
      <p>For more information on ActiveMQ load balancing, and clustering in general, please see the clustering

examples/jms/dead-letter/readme.html

@@ -40,7 +40,7 @@ under the License.
          We will then consume this dead letter message.
      </p>
      <h2>Example setup</h2>
-     <p><em>Dead letter addresses</em> and <em>maximum delivery attempts</em> are defined in the configuration file <a href="src/main/resources/activemq/server0/activemq-configuration.xml">activemq-configuration.xml</a>:</p>
+     <p><em>Dead letter addresses</em> and <em>maximum delivery attempts</em> are defined in the configuration file <a href="src/main/resources/activemq/server0/broker.xml">broker.xml</a>:</p>
      <pre class="prettyprint">
          <code>&lt;address-setting match="jms.queue.exampleQueue"&gt;
             &lt;dead-letter-address&gt;jms.queue.deadLetterQueue&lt;/dead-letter-address&gt;

examples/jms/delayed-redelivery/readme.html

@@ -39,7 +39,7 @@ under the License.
      matching on the address settings.</p>
 
      <h2>Example setup</h2>
-     <p>Redelivery delay is specified in the configuration file <a href="src/main/resources/activemq/server0/activemq-configuration.xml">activemq-configuration.xml</a>:</p>
+     <p>Redelivery delay is specified in the configuration file <a href="src/main/resources/activemq/server0/broker.xml">broker.xml</a>:</p>
      <p>In this example we set the redelivery delay to 5 seconds for the specific example queue. We could set redelivery delay on
      on multiple queues by specifying a wild-card in the match, e.g. <code>match="jms.#"</code> would apply the settings
      to all JMS queues and topics.</p>

examples/jms/divert/readme.html

@@ -54,7 +54,7 @@ under the License.
      <p>We will create a topic, <code>spyTopic</code> on the London server, and there will be two subscribers both in London.</p>
      <p>We will create a <i>non-exclusive</i> divert on the London server which will siphon off a copy of each order
      received to the topic <code>spyTopic</code>.</p>
-     <p>Here's the xml config for that divert, from <code>activemq-configuration.xml</code></p>
+     <p>Here's the xml config for that divert, from <code>broker.xml</code></p>
      <pre class="prettyprint">
         <code>
      &lt;divert name="order-divert"&gt;                 

examples/jms/embedded-simple/readme.html

@@ -34,7 +34,7 @@ under the License.
 
       <ol>
          <li>Create ActiveMQ core configuration files and make sure they are within your classpath.  By default, ActiveMQ
-             expects the configuration file name to be "activemq-configuration.xml".</li>
+             expects the configuration file name to be "broker.xml".</li>
          <li>Create an embedded ActiveMQ JMS server</li>
          <pre class="prettyprint">
             <code>EmbeddedJMS jmsServer = new EmbeddedJMS();</code>

examples/jms/expiry/readme.html

@@ -38,7 +38,7 @@ under the License.
          We will instead consume it from an <em>expiry queue</em> where it was moved when it expired.
      </p>
      <h2>Example setup</h2>
-     <p>Expiry destinations are defined in the configuration file <a href="server0/activemq-configuration.xml">activemq-configuration.xml</a>:</p>
+     <p>Expiry destinations are defined in the configuration file <a href="server0/broker.xml">broker.xml</a>:</p>
      <pre class="prettyprint">
          <code>&lt;address-setting match="jms.queue.exampleQueue"&gt;
             &lt;expiry-address&gt;jms.queue.expiryQueue&lt;/expiry-address&gt;