This topic has not yet been written. The content below is from the topic description.
6.6. Configuration files The configuration directory is specified on the classpath in the run scripts run.sh and run.bat This directory can contain the following files. hornetq-beans.xml (or hornetq-jboss-beans.xml if you're running inside JBoss Application Server). This is the JBoss Microcontainer beans file which defines what beans the Microcontainer should create and what dependencies to enforce between them. Remember that HornetQ is just a set of POJOs. In the stand-alone server, it's the JBoss Microcontainer which instantiates these POJOs and enforces dependencies between them and other beans. hornetq-configuration.xml. This is the main HornetQ configuration file. All the parameters in this file are described in Chapter 47, Configuration Reference. Please see Section 6.9, “The main configuration file.� for more information on this file. hornetq-queues.xml. This file contains predefined queues, queue settings and security settings. The file is optional - all this configuration can also live in hornetq-configuration.xml. In fact, the default configuration sets do not have a hornetq-queues.xml file. The purpose of allowing queues to be configured in these files is to allow you to manage your queue configuration over many files instead of being forced to maintain it in a single file. There can be many hornetq-queues.xml files on the classpath. All will be loaded if found. hornetq-users.xml HornetQ ships with a basic security manager implementation which obtains user credentials from the hornetq-users.xml file. This file contains user, password and role information. For more information on security, please see Chapter 31, Security. hornetq-jms.xml The distro configuration by default includes a server side JMS service which mainly deploys JMS Queues, Topics and ConnectionFactorys from this file into JNDI. If you're not using JMS, or you don't need to deploy JMS objects on the server side, then you don't need this file. For more information on using JMS, please see Chapter 7, Using JMS. logging.properties This is used to configure the logging handlers used by the Java logger. For more information on configuring logging, please see Chapter 42, Logging. log4j.xml This is the Log4j configuration if the Log4j handler is configured. Note The property file-deployment-enabled in the hornetq-configuration.xml configuration when set to false means that the other configuration files are not loaded. This is true by default. It is also possible to use system property substitution in all the configuration files. by replacing a value with the name of a system property. Here is an example of this with a connector configuration: org.hornetq.core.remoting.impl.netty.NettyConnectorFactory Here you can see we have replaced 2 values with system properties hornetq.remoting.netty.host and hornetq.remoting.netty.port. These values will be replaced by the value found in the system property if there is one, if not they default back to localhost or 5445 respectively. It is also possible to not supply a default. i.e. ${hornetq.remoting.netty.host}, however the system property must be supplied in that case.