Table of Contents
- 5.1. Introduction
- 5.2. Configuration Store Location
- 5.3. 'Initial Configuration' Location
- 5.4. Creating an 'Initial Configuration' JSON File
- 5.5. Configuration Store Type
- 5.6. Customising Configuration using Configuration Properties
- 5.7. Example of JSON 'Initial Configuration'
- 5.8. Virtualhost Initial Configuration
This section describes how to perform initial configuration on the command line. Once the Broker is started, subsequent management is performed using the Management interfaces
The configuration for each component is stored as an entry in the broker configuration store, currently implemented as a JSON file which persists changes to disk, BDB or Derby database or an in-memory store which does not. The following components configuration is stored there:
Broker
Virtual Host Nodes
Loggers
Ports
Authentication Providers (optionally with Users for managing users Authentication Providers)
Access Control Providers
User Connection Limit Providers
Group Providers (optionally with Groups and GroupMembers for managing groups Group Providers)
Key stores
Trust stores
Plugins
Broker startup involves two configuration related items, the 'Initial Configuration' and the Configuration Store. When the broker is started, if a Configuration Store does not exist at the current store location then one will be initialised with the current 'Initial Configuration'. Subsequent broker restarts will use the existing configuration store and ignore the contents of the 'Initial Configuration'.
Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners