This section provides the details about broker configuration store.

The Broker has a configuration store and provides management interfaces to manage the broker components. The configuration for each broker component is stored in the store as a configuration entry. The following configuration entries can be stored there: Broker Port Authentication Provider Virtual Host Access Control Provider Group Provider Key store Trust store Plugin When broker is started for a first time a configuration store is created automatically from the internal initial configuration. The created broker configuration is placed into broker working folder if the broker configuration store location is not specified. The predefined initial configuration can be overridden using command line argument -icp with path to the initial configuration as in the example below: $ ./qpid-server -icp ./my-initial-configuration.json In this example the initial configuration from file "./my-initial-configuration.json" is used to create the broker configuration store on the broker startup. If broker configuration store already exists the command line argument -icp with the path to a custom initial configuration is ignored. The command line argument -os can be used to force the (re)creation of broker configuration store from initial store even when broker configuration store exists. The example below demonstrates this: $ ./qpid-server -os -icp ./my-initial-configuration.json The default initial configuration can be retrieved from the broker and stored into a file using a command line argument -cic <path to file >, for example: $ ./qpid-server -cic ./initial-config.json In the example above the broker default initial configuration saved at "./initial-config.json". A custom initial configuration can be created from the default one by using this command line argument. The default initial configuration declares four ports: AMQP, the default port number is 5672. The port number can be overridden using configuration parameter qpid.amqp_port. HTTP, the default port number is 8080. The port number can be overridden using configuration parameter qpid.HTTP_port. RMI, the default port number is 8999. The port number can be overridden using configuration parameter qpid.rmi_port. JMX, the default port number is 9099. The port number can be overridden using configuration parameter qpid.jmx_port. It is also possible to override the port numbers in a default initial configuration using a command line argument -prop like in an example below: $ ./qpid-server -prop qpid.amqp_port=10000 -prop qpid.http_port=10001 -prop qpid.jmx_port=10002 -prop qpid.rmi_port=10003 In the example above, port number 10000 is specified for AMQP port, port number 10001 is specified for HTTP port, port number 10002 is specified for JMX port and port number 1003 is specified for RMI port. When specified, these port numbers will be used to create the broker configuration store from initial configuration on first broker start-up. If configuration store already exists the settings will not have any effect. The command line argument -os can be used to force (re)creation of broker configuration store from initial store. The command line argument -sp is used to specify a relative or absolute path to a broker configuration store to start broker with. If the store at specified location does not exist it will be created from the initial configuration. It is not required to provide the path to configuration store on broker on start-up. $ ./qpid-server -sp ./my-broker-configuration.json In the example above the broker is started with configuration store at "./my-broker-configuration.json".

The JSON configuration store is used as a default configuration store. An example of the JSON store is provided below: In the configuration above the following entries are stored: Authentication Provider of type PlainPasswordFile with name "passwordFile" Four Port entries: "AMQP", "HTTP", "RMI_REGISTRY", "JMX_CONNECTOR" Virtual Host with name "default" and DERBY message store type at location "${qpid.work_dir}/derbystore/default". Two management plugins: "jmxManagement" of type "MANAGEMENT-JMX" and "httpManagement" of type "MANAGEMENT-HTTP". Broker attributes are stored as a root entry.

The Broker Attributes can be configured using REST Management interfaces and Web Management Console. The Broker attributes can be changed from Web Management Console by clicking on "Edit" button on "Broker Attributes" panel from Broker tab.