summaryrefslogtreecommitdiff
path: root/qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml
diff options
context:
space:
mode:
authorKeith Wall <kwall@apache.org>2014-10-12 15:48:18 +0000
committerKeith Wall <kwall@apache.org>2014-10-12 15:48:18 +0000
commit39b5bc8a8456235540730c88922f60855a16e46b (patch)
treeed495f958ebe78b2559dbbbb0c4e292e1555250f /qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml
parent71c395d26e425571573b0bda06e23e5f84c1ca2c (diff)
downloadqpid-python-39b5bc8a8456235540730c88922f60855a16e46b.tar.gz
QPID-6108: [Java Broker Documentation] Rewrite HA documentation to reflect the new model and the include multi-node support.
* Correct many spelling errors * Improve web-console documentation around add/edit/delete entities, and the setting of context variables * Extract new top level section for backup/recovery git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1631195 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml')
-rw-r--r--qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml b/qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml
index ccdce918c6..ce461d32d7 100644
--- a/qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml
+++ b/qpid/doc/book/src/java-broker/Java-Broker-Initial-Configuration.xml
@@ -27,11 +27,11 @@
<section id="Java-Broker-Initial-Configuration-Introduction">
<title>Introduction</title>
<para>This section describes how to perform initial configuration on the command line. Once
- the Broker is started, subsequent management is perfomed using the <link
+ the Broker is started, subsequent management is performed using the <link
linkend="Java-Broker-Management-Channel">Management interfaces</link></para>
<para> 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 databadse or an in-memory store which does not. The following
+ disk, BDB or Derby database or an in-memory store which does not. The following
components configuration is stored there: <itemizedlist>
<listitem>
<para>Broker</para>
@@ -95,7 +95,7 @@ $ ./qpid-server -sp ./my-broker-configuration.json
<section id="Java-Broker-Initial-Configuration-Initial-Config-Location">
<title>'Initial Configuration' Location</title>
- <para> The 'Initial Configuration' JSON file is used when initialiasing new broker
+ <para> The 'Initial Configuration' JSON file is used when initialising new broker
configuration stores. The broker will default to using an internal file within its jar
unless otherwise instructed. </para>
<para> The command line argument <emphasis>-icp </emphasis> (or
@@ -177,7 +177,7 @@ $ ./qpid-server -os -icp ./my-initial-configuration.json
Configuration'</link> to provide the configuration to start the broker with. </para>
<para> The command line argument <emphasis>-st</emphasis> (or
<emphasis>--store-type</emphasis>) can be used to override the default
- <emphasis>json</emphasis>)configuration store type and allow choosing an alterative,
+ <emphasis>json</emphasis>)configuration store type and allow choosing an alternative,
such as <emphasis>memory</emphasis>) </para>
<screen>
$ ./qpid-server -st memory
@@ -190,7 +190,7 @@ $ ./qpid-server -st memory
<section id="Java-Broker-Initial-Configuration-Configuration-Properties">
<title>Customising Configuration using Configuration Properties</title>
- <para> It is posible for 'Initial Configuration' (and Configuration Store) files to contain
+ <para> It is possible for 'Initial Configuration' (and Configuration Store) files to contain
${properties} that can be resolved to String values at startup, allowing a degree of
customisation using a fixed file. Configuration Property values can be set either via
Java System Properties, or by specifying ConfigurationPproperties on the broker command
@@ -264,7 +264,7 @@ $ ./qpid-server -prop "qpid.amqp_port=10000" -prop "qpid.http_port=10001"
</screen>
<para> In the example above, property used to set the port number of the default AMQP port
is specified with the value 10000, overriding the default value of 5672, and similarly
- the vlaue 10001 is used to override the default HTTP port number of 8080. When using the
+ the value 10001 is used to override the default HTTP port number of 8080. When using the
'Initial Configuration' to initialise a new Configuration Store (either at first broker
startup, when requesting to <link linkend="Java-Broker-Initial-Configuration-Location"
>overwrite the configuration store</link>) these new values will be used for the
@@ -341,7 +341,7 @@ $ ./qpid-server -prop "qpid.amqp_port=10000" -prop "qpid.http_port=10001"
<listitem>
<para> Virtualhost Node called default. On initial startup, it
virtualHostInitialConfiguration will cause a virtualhost to be created
- with the same name. The confiuration will be stored in a
+ with the same name. The configuration will be stored in a
<emphasis>JSON</emphasis> configuration store, the message data will
be stored in a <emphasis>DERBY</emphasis> message store.</para>
</listitem>