You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by gm...@apache.org on 2016/11/23 14:59:15 UTC
[1/6] qpid-site git commit: NO-JIRA - Updating documentation for Qpid
Dispatch Router version 0.7.0
Repository: qpid-site
Updated Branches:
refs/heads/asf-site 12921fae6 -> 09f4ae2e1
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console_charts.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console_charts.png b/input/releases/qpid-dispatch-0.7.0/book/console_charts.png
new file mode 100644
index 0000000..169c2ca
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console_charts.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console_entity.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console_entity.png b/input/releases/qpid-dispatch-0.7.0/book/console_entity.png
new file mode 100644
index 0000000..130c7e7
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console_entity.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console_login.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console_login.png b/input/releases/qpid-dispatch-0.7.0/book/console_login.png
new file mode 100644
index 0000000..63e22c6
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console_login.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console_overview.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console_overview.png b/input/releases/qpid-dispatch-0.7.0/book/console_overview.png
new file mode 100644
index 0000000..af25f36
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console_overview.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console_schema.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console_schema.png b/input/releases/qpid-dispatch-0.7.0/book/console_schema.png
new file mode 100644
index 0000000..ba56c7b
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console_schema.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console_topology.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console_topology.png b/input/releases/qpid-dispatch-0.7.0/book/console_topology.png
new file mode 100644
index 0000000..ae4b22a
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console_topology.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/index.md
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/index.md b/input/releases/qpid-dispatch-0.7.0/index.md
new file mode 100644
index 0000000..b53f21f
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/index.md
@@ -0,0 +1,66 @@
+;;
+;; Licensed to the Apache Software Foundation (ASF) under one
+;; or more contributor license agreements. See the NOTICE file
+;; distributed with this work for additional information
+;; regarding copyright ownership. The ASF licenses this file
+;; to you under the Apache License, Version 2.0 (the
+;; "License"); you may not use this file except in compliance
+;; with the License. You may obtain a copy of the License at
+;;
+;; http://www.apache.org/licenses/LICENSE-2.0
+;;
+;; Unless required by applicable law or agreed to in writing,
+;; software distributed under the License is distributed on an
+;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+;; KIND, either express or implied. See the License for the
+;; specific language governing permissions and limitations
+;; under the License.
+;;
+
+# Qpid Dispatch 0.7.0
+
+Dispatch is a lightweight AMQP message router library. More about
+[Qpid
+Dispatch]({{site_url}}/components/dispatch-router/index.html).
+
+For a detailed list of the changes in this release, see the [release
+notes](release-notes.html).
+
+## Downloads
+
+It's important to [verify the
+integrity]({{site_url}}/download.html#verify-what-you-download) of
+the files you download.
+
+| Content | Download | Verify |
+|---------|----------|--------|
+| Dispatch router | [qpid-dispatch-0.7.0.tar.gz](http://archive.apache.org/dist/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz) | [PGP](http://archive.apache.org/dist/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz.asc) |
+
+## Documentation
+
+
+<div class="two-column" markdown="1">
+
+ - [Installing Qpid Dispatch](https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;a=blob_plain;f=README;hb=0.7.x)
+ - [Dispatch Router User Guide](book/book.html)
+ - [qdrouterd](man/qdrouterd.html) - Router daemon
+ - [qdrouterd.conf](man/qdrouterd.conf.html) - Daemon configuration
+ - [qdstat](man/qdstat.html) - Get router statistics
+ - [qdmanage](man/qdmanage.html) - Manage the router
+
+</div>
+
+
+## More information
+
+ - [All release artefacts](http://archive.apache.org/dist/qpid/dispatch/0.7.0)
+ - [Resolved issues in JIRA](https://issues.apache.org/jira/issues/?jql=project+%3D+DISPATCH+AND+fixVersion+%3D+%270.7.0%27+AND+resolution+%3D+%27fixed%27+ORDER+BY+priority+DESC)
+ - [Source repository tag](https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git/tree/refs/tags/0.7.0)
+
+<script type="text/javascript">
+ _deferredFunctions.push(function() {
+ if ("0.7.0" === "{{current_dispatch_release}}") {
+ _modifyCurrentReleaseLinks();
+ }
+ });
+</script>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/man/qdmanage.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/man/qdmanage.html.in b/input/releases/qpid-dispatch-0.7.0/man/qdmanage.html.in
new file mode 100644
index 0000000..384c8f7
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/man/qdmanage.html.in
@@ -0,0 +1,245 @@
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdmanage</strong> [<em>OPTIONS</em>] <em>OPERATION</em> [<em>ARGUMENTS</em>]</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>An AMQP management client for use with qdrouterd. Sends AMQP management
+operations requests and prints the response in JSON format. This is a
+generic AMQP management tool and can be used with any standard AMQP
+managed endpoint, not just with qdrouter.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options">OPTIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>-h, --help
+: show this help message and exit</p></div>
+<div class="paragraph"><p>--version
+: Print version and exit.</p></div>
+<div class="paragraph"><p>--type=TYPE
+: Type of entity to operate on.</p></div>
+<div class="paragraph"><p>--name=NAME
+: Name of entity to operate on.</p></div>
+<div class="paragraph"><p>--identity=ID
+: Identity of entity to operate on.</p></div>
+<div class="paragraph"><p>--indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print</p></div>
+<div class="paragraph"><p>--stdin
+: Read attributes as JSON map or list of maps from</p></div>
+<div class="paragraph"><p>--body=BODY
+: JSON value to use as body of a non-standard operation</p></div>
+<div class="paragraph"><p>--properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p></div>
+<div class="sect2">
+<h3 id="_connection_options">Connection Options</h3>
+<div class="paragraph"><p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default</p></div>
+<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p></div>
+<div class="paragraph"><p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p></div>
+<div class="paragraph"><p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--ssl-password-file=SSL-PASSWORD-FILE
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--sasl-mechanisms=SASL-MECHANISMS
+: Allowed sasl mechanisms to be supplied during the sasl handshake.</p></div>
+<div class="paragraph"><p>--sasl-username=SASL-USERNAME
+: User name for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password=SASL-PASSWORD
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password-file=SASL-PASSWORD-FILE
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--ssl-disable-peer-name-verify
+: Disables SSL peer name verification. WARNING - This option is insecure and must not be used in production environments</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_operations">OPERATIONS</h2>
+<div class="sectionbody">
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<code>query</code> [<em>ATTR</em>…]
+</dt>
+<dd>
+<p>
+ Print attributes for multiple entities. Prints all entities by default, use
+ --type, --name or --identity options to restrict which entities are printed.
+ Prints the attributes named in the ATTR list, or all attributes if none are
+ listed.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>create</code> [<em>ATTR=VALUE</em>…]
+</dt>
+<dd>
+<p>
+ Create a new entity with the specified attributes. With the --stdin
+ option, read attributes from stdin. This can be a JSON map of
+ attributes to create a single entity, or a JSON list of maps to create
+ multiple entities.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>read</code>
+</dt>
+<dd>
+<p>
+ Print all the attributes of a single entity, specified by the --name or
+ --identity options.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>update</code> [<em>ATTR=VALUE</em>…]
+</dt>
+<dd>
+<p>
+ Update the attributes of an existing entity. If an ATTR name is listed with
+ no =VALUE, that attribute will be deleted from the entity. With the --stdin
+ option, read attributes from stdin. This can be a JSON map of attributes to
+ update a single entity, or a JSON list of maps to update multiple entities.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>delete</code>
+</dt>
+<dd>
+<p>
+ Delete an entity specified by the --name or --identity options.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-types</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their base types. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-operations</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their operations. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-attributes</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their attributes. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-annotations</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their annotations. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-mgmt-nodes</code>
+</dt>
+<dd>
+<p>
+ List all other known management nodes connected to this one.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-json-schema</code> [<em>INDENT</em>]
+</dt>
+<dd>
+<p>
+ Get the router schema in JSON format. Optional integer indent for
+ formatted output.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-log</code> [<em>INDENT</em>]
+</dt>
+<dd>
+<p>
+ Get recent log entries from the router.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_files">FILES</h2>
+<div class="sectionbody">
+<div class="dlist"><dl>
+<dt class="hdlist1">
+/usr/local/share/doc/qpid-dispatch/qdrouter.json
+</dt>
+<dd>
+<p>
+ Management schema for qdrouterd.
+</p>
+</dd>
+<dt class="hdlist1">
+/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt
+</dt>
+<dd>
+<p>
+ Explanation of the management schema.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_examples">EXAMPLES</h2>
+<div class="sectionbody">
+<div class="listingblock">
+<div class="title">Show the logging configuration</div>
+<div class="content">
+<pre><code>qdmanage query --type=log</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Enable debug and higher log messages by default:</div>
+<div class="content">
+<pre><code>qdmanage update name=log/DEFAULT enable=debug+</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Enable trace log messages only for the MESSAGE module and direct MESSAGE logs to the file "test.log"</div>
+<div class="content">
+<pre><code>qdmanage update name=log/MESSAGE enable=trace output=test.log</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Set MESSAGE logging back to the default</div>
+<div class="content">
+<pre><code>qdmanage update name=log/MESSAGE enable=default</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Disable MESSAGE logging</div>
+<div class="content">
+<pre><code>qdmanage update name=log/MESSAGE enable=none</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html.in b/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html.in
new file mode 100644
index 0000000..fa47d38
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html.in
@@ -0,0 +1,1020 @@
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Provides the initial configuration when <em>qdrouterd(8)</em> starts. The configuration
+of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The configuration file is made up of sections with this syntax:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>sectionName {
+ attributeName: attributeValue
+ attributeName: attributeValue
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>For example you can define a router using the <em>router</em> section</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>router {
+ mode: standalone
+ id: Router.A
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>or define a listener using the <em>listener</em> section</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>listener {
+ host: 0.0.0.0
+ port: 20102
+ saslMechanisms: ANONYMOUS
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>or define a connector using the <em>connector</em> section</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ role: inter-router
+ host: 0.0.0.0
+ port: 20003
+ saslMechanisms: ANONYMOUS
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>An <em>sslProfile</em> section with SSL credentials can be included in multiple <em>listener</em> or <em>connector</em> entities. Here’s an example, note
+how the <em>sslProfile</em> attribute of <em>listener</em> sections references the <em>name</em>
+attribute of <em>sslProfile</em> sections.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>sslProfile {
+ name: my-ssl
+ certDb: ca-certificate-1.pem
+ certFile: server-certificate-1.pem
+ keyFile: server-private-key.pem
+}
+
+listener {
+ sslProfile: my-ssl
+ host: 0.0.0.0
+ port: 20102
+ saslMechanisms: ANONYMOUS
+}</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration_sections">Configuration Sections</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_router">router</h3>
+<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>id</em> (string)
+</dt>
+<dd>
+<p>
+ Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>)
+</dt>
+<dd>
+<p>
+ In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloInterval</em> (integer, default=1)
+</dt>
+<dd>
+<p>
+ Interval in seconds between HELLO messages sent to neighbor routers.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloMaxAge</em> (integer, default=3)
+</dt>
+<dd>
+<p>
+ Time in seconds after which a neighbor is declared lost if no HELLO is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raInterval</em> (integer, default=30)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers in a stable network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raIntervalFlux</em> (integer, default=4)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>remoteLsMaxAge</em> (integer, default=60)
+</dt>
+<dd>
+<p>
+ Time in seconds after which link state is declared stale if no RA is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>workerThreads</em> (integer, default=4)
+</dt>
+<dd>
+<p>
+ The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
+</p>
+</dd>
+<dt class="hdlist1">
+<em>debugDump</em> (path)
+</dt>
+<dd>
+<p>
+ A file to dump debugging information that can’t be logged normally.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigPath</em> (path)
+</dt>
+<dd>
+<p>
+ Absolute path to the SASL configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigName</em> (string, default=<em>qdrouterd</em>)
+</dt>
+<dd>
+<p>
+ Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>routerId</em> (string)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mobileAddrMaxAge</em> (integer, default=60)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This value is no longer used in the router.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_sslprofile">sslProfile</h3>
+<div class="paragraph"><p>Attributes for setting TLS/SSL configuration for connections.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>certDb</em> (path)
+</dt>
+<dd>
+<p>
+ The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>certFile</em> (path)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>keyFile</em> (path)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the PEM-formatted private key for the above certificate.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>passwordFile</em> (path)
+</dt>
+<dd>
+<p>
+ If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>password</em> (string)
+</dt>
+<dd>
+<p>
+ An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>uidFormat</em> (string)
+</dt>
+<dd>
+<p>
+ A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>displayNameFile</em> (string)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the unique id to dispay name mapping
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_listener">listener</h3>
+<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>host</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ IP address: ipv4 or ipv6 literal or a host name
+</p>
+</dd>
+<dt class="hdlist1">
+<em>port</em> (string, default=<em>amqp</em>)
+</dt>
+<dd>
+<p>
+ Port number or symbolic service name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+</dt>
+<dd>
+<p>
+ [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>], default=<em>normal</em>)
+</dt>
+<dd>
+<p>
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>cost</em> (integer, default=<em>1</em>)
+</dt>
+<dd>
+<p>
+ For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>sslProfile</em> (string)
+</dt>
+<dd>
+<p>
+ Name of the sslProfile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslMechanisms</em> (string)
+</dt>
+<dd>
+<p>
+ Space separated list of accepted SASL authentication mechanisms.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>authenticatePeer</em> (boolean)
+</dt>
+<dd>
+<p>
+ yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>requireEncryption</em> (boolean)
+</dt>
+<dd>
+<p>
+ yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
+</p>
+</dd>
+<dt class="hdlist1">
+<em>requireSsl</em> (boolean)
+</dt>
+<dd>
+<p>
+ yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>trustedCerts</em> (path)
+</dt>
+<dd>
+<p>
+ This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxFrameSize</em> (integer, default=16384)
+</dt>
+<dd>
+<p>
+ Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>idleTimeoutSeconds</em> (integer, default=16)
+</dt>
+<dd>
+<p>
+ The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+</dt>
+<dd>
+<p>
+ [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+</p>
+</dd>
+<dt class="hdlist1">
+<em>linkCapacity</em> (integer)
+</dt>
+<dd>
+<p>
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>addr</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ (DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowNoSasl</em> (boolean)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>requirePeerAuth</em> (boolean)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowUnsecured</em> (boolean)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_connector">connector</h3>
+<div class="paragraph"><p>Establishes an outgoing connection from the router.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>host</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ IP address: ipv4 or ipv6 literal or a host name
+</p>
+</dd>
+<dt class="hdlist1">
+<em>port</em> (string, default=<em>amqp</em>)
+</dt>
+<dd>
+<p>
+ Port number or symbolic service name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+</dt>
+<dd>
+<p>
+ [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>], default=<em>normal</em>)
+</dt>
+<dd>
+<p>
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>cost</em> (integer, default=<em>1</em>)
+</dt>
+<dd>
+<p>
+ For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>sslProfile</em> (string)
+</dt>
+<dd>
+<p>
+ Name of the sslProfile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslMechanisms</em> (string)
+</dt>
+<dd>
+<p>
+ Space separated list of accepted SASL authentication mechanisms.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowRedirect</em> (boolean, default=True)
+</dt>
+<dd>
+<p>
+ Allow the peer to redirect this connection to another address.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxFrameSize</em> (integer, default=65536)
+</dt>
+<dd>
+<p>
+ Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>idleTimeoutSeconds</em> (integer, default=16)
+</dt>
+<dd>
+<p>
+ The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+</dt>
+<dd>
+<p>
+ [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+</p>
+</dd>
+<dt class="hdlist1">
+<em>linkCapacity</em> (integer)
+</dt>
+<dd>
+<p>
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>verifyHostName</em> (boolean, default=True)
+</dt>
+<dd>
+<p>
+ yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslUsername</em> (string)
+</dt>
+<dd>
+<p>
+ The user name that the connector is using to connect to a peer.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslPassword</em> (string)
+</dt>
+<dd>
+<p>
+ The password that the connector is using to connect to a peer.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>addr</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ (DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_log">log</h3>
+<div class="paragraph"><p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>module</em> (One of [<em>ROUTER</em>, <em>ROUTER_CORE</em>, <em>ROUTER_HELLO</em>, <em>ROUTER_LS</em>, <em>ROUTER_MA</em>, <em>MESSAGE</em>, <em>SERVER</em>, <em>AGENT</em>, <em>CONTAINER</em>, <em>ERROR</em>, <em>POLICY</em>, <em>DEFAULT</em>], required)
+</dt>
+<dd>
+<p>
+ Module to configure. The special module <em>DEFAULT</em> specifies defaults for all modules.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>enable</em> (string)
+</dt>
+<dd>
+<p>
+ Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <em>+</em> to enable that level and above. For example <em>trace,debug,warning+</em> means enable trace, debug, warning, error and critical. The value <em>none</em> means disable logging for the module.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>timestamp</em> (boolean)
+</dt>
+<dd>
+<p>
+ Include timestamp in log messages.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>source</em> (boolean)
+</dt>
+<dd>
+<p>
+ Include source file and line number in log messages.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>output</em> (string)
+</dt>
+<dd>
+<p>
+ Where to send log messages. Can be <em>stderr</em>, <em>stdout</em>, <em>syslog</em> or a file name.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_address">address</h3>
+<div class="paragraph"><p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address prefix for the configured settings
+</p>
+</dd>
+<dt class="hdlist1">
+<em>distribution</em> (One of [<em>multicast</em>, <em>closest</em>, <em>balanced</em>], default=<em>balanced</em>)
+</dt>
+<dd>
+<p>
+ Treatment of traffic associated with the address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>waypoint</em> (boolean)
+</dt>
+<dd>
+<p>
+ Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>ingressPhase</em> (integer)
+</dt>
+<dd>
+<p>
+ Advanced - Override the ingress phase for this address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>egressPhase</em> (integer)
+</dt>
+<dd>
+<p>
+ Advanced - Override the egress phase for this address
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_linkroute">linkRoute</h3>
+<div class="paragraph"><p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address prefix for the configured settings
+</p>
+</dd>
+<dt class="hdlist1">
+<em>containerId</em> (string)
+</dt>
+<dd>
+<p>
+ ContainerID for the target container
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connection</em> (string)
+</dt>
+<dd>
+<p>
+ The name from a connector or listener
+</p>
+</dd>
+<dt class="hdlist1">
+<em>distribution</em> (One of [<em>linkBalanced</em>], default=<em>linkBalanced</em>)
+</dt>
+<dd>
+<p>
+ Treatment of traffic associated with the address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+</dt>
+<dd>
+<p>
+ The permitted direction of links: <em>in</em> means client senders; <em>out</em> means client receivers
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_autolink">autoLink</h3>
+<div class="paragraph"><p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>addr</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address of the provisioned object
+</p>
+</dd>
+<dt class="hdlist1">
+<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+</dt>
+<dd>
+<p>
+ The direction of the link to be created. In means into the router, out means out of the router.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>phase</em> (integer)
+</dt>
+<dd>
+<p>
+ The address phase for this link. Defaults to <em>0</em> for <em>out</em> links and <em>1</em> for <em>in</em> links.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>containerId</em> (string)
+</dt>
+<dd>
+<p>
+ ContainerID for the target container
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connection</em> (string)
+</dt>
+<dd>
+<p>
+ The name from a connector or listener
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_console">console</h3>
+<div class="paragraph"><p>Start a websocket/tcp proxy and http file server to serve the web console</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>listener</em> (string)
+</dt>
+<dd>
+<p>
+ The name of the listener to send the proxied tcp traffic to.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>wsport</em> (integer, default=5673)
+</dt>
+<dd>
+<p>
+ port on which to listen for websocket traffic
+</p>
+</dd>
+<dt class="hdlist1">
+<em>proxy</em> (string)
+</dt>
+<dd>
+<p>
+ The full path to the proxy program to run.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>home</em> (string)
+</dt>
+<dd>
+<p>
+ The full path to the html/css/js files for the console.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>args</em> (string)
+</dt>
+<dd>
+<p>
+ Optional args to pass the proxy program for logging, authentication, etc.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_policy">policy</h3>
+<div class="paragraph"><p>Defines global connection limit</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>maxConnections</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Global maximum number of concurrent client connections allowed. This limit is always enforced even if no other policy settings have been defined.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>enableVhostPolicy</em> (boolean)
+</dt>
+<dd>
+<p>
+ Enable vhost policy user groups, connection denial, and resource limit enforcement
+</p>
+</dd>
+<dt class="hdlist1">
+<em>policyDir</em> (path)
+</dt>
+<dd>
+<p>
+ Absolute path to a directory that holds vhost definition .json files. All vhost definitions in all .json files in this directory are processed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>defaultVhost</em> (string)
+</dt>
+<dd>
+<p>
+ Vhost rule set name to use for connections with a vhost that is otherwise not defined. Default vhost processing may be disabled either by erasing the definition of defaultVhost or by not defining a vhost object named <em>$default</em>.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_vhost">vhost</h3>
+<div class="paragraph"><p>AMQP virtual host policy definition of users, user groups, allowed remote hosts, and AMQP restrictions.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>id</em> (string, required)
+</dt>
+<dd>
+<p>
+ The vhost name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxConnections</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Maximum number of concurrent client connections allowed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxConnectionsPerUser</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Maximum number of concurrent client connections allowed for any single user.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxConnectionsPerHost</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Maximum number of concurrent client connections allowed for any remote host.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowUnknownUser</em> (boolean)
+</dt>
+<dd>
+<p>
+ Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <em>default</em> user group and receive <em>default</em> settings.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>groups</em> (map)
+</dt>
+<dd>
+<p>
+ A map where each key is a user group name and the value is a map of the corresponding settings for that group.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_container">container</h3>
+<div class="paragraph"><p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>containerName</em> (string)
+</dt>
+<dd>
+<p>
+ The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>workerThreads</em> (integer, default=4)
+</dt>
+<dd>
+<p>
+ The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
+</p>
+</dd>
+<dt class="hdlist1">
+<em>debugDump</em> (path)
+</dt>
+<dd>
+<p>
+ A file to dump debugging information that can’t be logged normally.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigPath</em> (path)
+</dt>
+<dd>
+<p>
+ Absolute path to the SASL configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigName</em> (string)
+</dt>
+<dd>
+<p>
+ Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_waypoint">waypoint</h3>
+<div class="paragraph"><p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>address</em> (string, required)
+</dt>
+<dd>
+<p>
+ The AMQP address of the waypoint.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connector</em> (string, required)
+</dt>
+<dd>
+<p>
+ The name of the on-demand connector used to reach the waypoint’s container.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>inPhase</em> (integer, default=-1)
+</dt>
+<dd>
+<p>
+ The phase of the address as it is routed <em>to</em> the waypoint.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>outPhase</em> (integer, default=-1)
+</dt>
+<dd>
+<p>
+ The phase of the address as it is routed <em>from</em> the waypoint.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_fixedaddress">fixedAddress</h3>
+<div class="paragraph"><p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address prefix (always starting with <em>/</em>).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>phase</em> (integer)
+</dt>
+<dd>
+<p>
+ The phase of a multi-hop address passing through one or more waypoints.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>fanout</em> (One of [<em>multiple</em>, <em>single</em>], default=<em>multiple</em>)
+</dt>
+<dd>
+<p>
+ One of <em>multiple</em> or <em>single</em>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>bias</em> (One of [<em>closest</em>, <em>spread</em>], default=<em>closest</em>)
+</dt>
+<dd>
+<p>
+ Only if fanout is single. One of <em>closest</em> or <em>spread</em>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_linkroutepattern">linkRoutePattern</h3>
+<div class="paragraph"><p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ An address prefix to match against target and source addresses. This pattern must be of the form <em><text>.<text1>.<textN></em> or <em><text></em> or <em><text>.</em> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <em>org.apache</em> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>dir</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>], default=<em>both</em>)
+</dt>
+<dd>
+<p>
+ Link direction for match: <em>in</em> matches only links inbound to the client; <em>out</em> matches only links outbound from the client; <em>both</em> matches any link.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connector</em> (string)
+</dt>
+<dd>
+<p>
+ The name of the on-demand connector used to reach the target node’s container. If this value is not provided, it means that the target container is expected to be connected to a different router in the network. This prevents links to a link-routable address from being misinterpreted as message-routing links when there is no route to a valid destination available.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.html.in b/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.html.in
new file mode 100644
index 0000000..0b85b2e
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/man/qdrouterd.html.in
@@ -0,0 +1,55 @@
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdrouterd</strong> [<em>OPTIONS</em>]</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
+AMQP 1.0 messages between endpoints, such as messaging clients and
+servers.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options">OPTIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
+: Load configuration from file at PATH</p></div>
+<div class="paragraph"><p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
+: Location of Dispatch’s Python library</p></div>
+<div class="paragraph"><p>-d, --daemon
+: Run process as a SysV-style daemon</p></div>
+<div class="paragraph"><p>-P, --pidfile
+: If daemon, the file for the stored daemon pid</p></div>
+<div class="paragraph"><p>-U, --user
+: If daemon, the username to run as</p></div>
+<div class="paragraph"><p>-v, --version
+: Print the version of Qpid Dispatch Router</p></div>
+<div class="paragraph"><p>-h, --help
+: Print this help</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_files">FILES</h2>
+<div class="sectionbody">
+<div class="dlist"><dl>
+<dt class="hdlist1">
+/usr/local/etc/qdrouterd.conf
+</dt>
+<dd>
+<p>
+ Configuration flie.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/man/qdstat.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/man/qdstat.html.in b/input/releases/qpid-dispatch-0.7.0/man/qdstat.html.in
new file mode 100644
index 0000000..b444964
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/man/qdstat.html.in
@@ -0,0 +1,738 @@
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdstat</strong> [<em>OPTIONS</em>]</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Shows status information about networks of Dispatch routers. It can display
+connections, network nodes and links, and router stats such as memory use.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options">OPTIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>-h, --help
+: show this help message and exit</p></div>
+<div class="paragraph"><p>--version
+: Print version and exit.</p></div>
+<div class="paragraph"><p>-g, --general
+: Show General Router Stats</p></div>
+<div class="paragraph"><p>-c, --connections
+: Show Connections</p></div>
+<div class="paragraph"><p>-l, --links
+: Show Router Links</p></div>
+<div class="paragraph"><p>-n, --nodes
+: Show Router Nodes</p></div>
+<div class="paragraph"><p>-a, --address
+: Show Router Addresses</p></div>
+<div class="paragraph"><p>-m, --memory
+: Show Router Memory Stats</p></div>
+<div class="paragraph"><p>--autolinks
+: Show Auto Links</p></div>
+<div class="paragraph"><p>--linkroutes
+: Show Link Routes</p></div>
+<div class="paragraph"><p>-v, --verbose
+: Show maximum detail</p></div>
+<div class="paragraph"><p>--log
+: Show recent log entries</p></div>
+<div class="paragraph"><p>--limit=LIMIT
+: Limit number of log entries</p></div>
+<div class="sect2">
+<h3 id="_connection_options">Connection Options</h3>
+<div class="paragraph"><p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default</p></div>
+<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p></div>
+<div class="paragraph"><p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p></div>
+<div class="paragraph"><p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--ssl-password-file=SSL-PASSWORD-FILE
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--sasl-mechanisms=SASL-MECHANISMS
+: Allowed sasl mechanisms to be supplied during the sasl handshake.</p></div>
+<div class="paragraph"><p>--sasl-username=SASL-USERNAME
+: User name for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password=SASL-PASSWORD
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password-file=SASL-PASSWORD-FILE
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--ssl-disable-peer-name-verify
+: Disables SSL peer name verification. WARNING - This option is insecure and must not be used in production environments</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_output_columns">OUTPUT COLUMNS</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_qdstat_c">qdstat -c</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+id
+</dt>
+<dd>
+<p>
+Unique connection identifier
+</p>
+</dd>
+<dt class="hdlist1">
+host
+</dt>
+<dd>
+<p>
+The hostname or internet address of the remotely connected AMQP container
+</p>
+</dd>
+<dt class="hdlist1">
+container
+</dt>
+<dd>
+<p>
+The container-name of the remotely connected AMQP container
+</p>
+</dd>
+<dt class="hdlist1">
+role
+</dt>
+<dd>
+<p>
+The configured role of the connection
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+normal - Normal connections from client to router
+</p>
+</li>
+<li>
+<p>
+inter-router - Connection between routers to form a network
+</p>
+</li>
+<li>
+<p>
+route-container - Connection to/from a Broker or other host to receive link-routes and waypoints
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction of connection establishment
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+in - The connection was initiated by the remote container
+</p>
+</li>
+<li>
+<p>
+out - The connection was initiated by this router
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+security
+</dt>
+<dd>
+<p>
+A description of the security/encryption in effect for this
+connection
+</p>
+</dd>
+<dt class="hdlist1">
+authentication
+</dt>
+<dd>
+<p>
+The method and user-id of the authenticated user for
+this connection
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_qdstat_l">qdstat -l</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+type
+</dt>
+<dd>
+<p>
+Type of link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+router-control - An inter-router link that is reserved for control messages exchanged between routers
+</p>
+</li>
+<li>
+<p>
+inter-router - An inter-router link that is used for normal message-routed deliveries
+</p>
+</li>
+<li>
+<p>
+endpoint - A normal link to an external endpoint container
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction of message flow on the link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+in - Deliveries flow inbound to the router
+</p>
+</li>
+<li>
+<p>
+out - Deliveries flow outbound from the router
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+conn id
+</dt>
+<dd>
+<p>
+Unique identifier of the connection over which this link is
+attached
+</p>
+</dd>
+<dt class="hdlist1">
+id
+</dt>
+<dd>
+<p>
+Unique identifier of this link
+</p>
+</dd>
+<dt class="hdlist1">
+peer
+</dt>
+<dd>
+<p>
+For link-routed links, the unique identifier of the peer link. In
+link routing, an inbound link is paired with an outbound link
+</p>
+</dd>
+<dt class="hdlist1">
+class
+</dt>
+<dd>
+<p>
+Class of the address bound to the link
+</p>
+</dd>
+<dt class="hdlist1">
+addr
+</dt>
+<dd>
+<p>
+The address bound to the link
+</p>
+</dd>
+<dt class="hdlist1">
+phs
+</dt>
+<dd>
+<p>
+The phase of the address bound to the link
+</p>
+</dd>
+<dt class="hdlist1">
+cap
+</dt>
+<dd>
+<p>
+The capacity, in deliveries, of the link
+</p>
+</dd>
+<dt class="hdlist1">
+undel
+</dt>
+<dd>
+<p>
+The number of undelivered messages stored on the link’s FIFO
+</p>
+</dd>
+<dt class="hdlist1">
+unsett
+</dt>
+<dd>
+<p>
+The number of unsettled deliveries being tracked by the link
+</p>
+</dd>
+<dt class="hdlist1">
+del
+</dt>
+<dd>
+<p>
+The total number of deliveries that have transited this link
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>presett:
+The number of pre-settled deliveries that transited this link</p></div>
+<div class="paragraph"><p>acc:
+The number of deliveries on this link that were accepted</p></div>
+<div class="paragraph"><p>rej:
+The number of deliveries on this link that were rejected</p></div>
+<div class="paragraph"><p>rel:
+The number of deliveries on this link that were released</p></div>
+<div class="paragraph"><p>mod:
+The number of deliveries on this link that were modified</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+admin
+</dt>
+<dd>
+<p>
+The administrative status of the link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+enabled - The link is enabled for normal operation
+</p>
+</li>
+<li>
+<p>
+disabled - The link is disabled and should be quiescing or stopped (not yet supported)
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+oper
+</dt>
+<dd>
+<p>
+The operational status of the link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+up - The link is operational
+</p>
+</li>
+<li>
+<p>
+down - The link is not attached
+</p>
+</li>
+<li>
+<p>
+quiescing - The link is in the process of quiescing (not yet supported)
+</p>
+</li>
+<li>
+<p>
+idle - The link has completed quiescing and is idle (not yet supported)
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+name
+</dt>
+<dd>
+<p>
+The link name (only shown if the -v option is provided)
+</p>
+</dd>
+</dl></div>
+<div class="sect3">
+<h4 id="_qdstat_n">qdstat -n</h4>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+router-id
+</dt>
+<dd>
+<p>
+Identifier of the router
+</p>
+</dd>
+<dt class="hdlist1">
+next-hop
+</dt>
+<dd>
+<p>
+If this router is not a neighbor, identifies the next-hop neighbor used to reach this router
+</p>
+</dd>
+<dt class="hdlist1">
+link
+</dt>
+<dd>
+<p>
+Unique identifier of the link to the neighbor router
+</p>
+</dd>
+<dt class="hdlist1">
+cost
+</dt>
+<dd>
+<p>
+The topology cost to this remote router (with -v option only)
+</p>
+</dd>
+<dt class="hdlist1">
+neighbors
+</dt>
+<dd>
+<p>
+The list of neighbor routers (the router’s link-state) (with -v option only)
+</p>
+</dd>
+<dt class="hdlist1">
+valid-origins
+</dt>
+<dd>
+<p>
+The list of origin routers for which the best path to the listed router passes through this router (with -v option only)
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_qdstat_a">qdstat -a</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+class
+</dt>
+<dd>
+<p>
+The class of the listed address
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+local - Address that is local to this router
+</p>
+</li>
+<li>
+<p>
+topo - Topological address used for router control messages
+</p>
+</li>
+<li>
+<p>
+router - A summary router address used to route messages to a remote router’s local addresses
+</p>
+</li>
+<li>
+<p>
+mobile - A mobile address for an attached consumer or producer
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+addr
+</dt>
+<dd>
+<p>
+The address text
+</p>
+</dd>
+<dt class="hdlist1">
+phs
+</dt>
+<dd>
+<p>
+For mobile addresses only, the phase of the address. Direct addresses have only a phase 0. Waypoint addresses have multiple phases, normally 0 and 1.
+</p>
+</dd>
+<dt class="hdlist1">
+distrib
+</dt>
+<dd>
+<p>
+Distribution method used for this address
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+multicast - A copy of each message is delivered once to each consumer for the address
+</p>
+</li>
+<li>
+<p>
+closest - Each message is delivered to only one consumer for the address. The closest (lowest cost) consumer will be chosen. If there are multiple lowest-cost consumers, deliveries will be spread across those consumers.
+</p>
+</li>
+<li>
+<p>
+balanced - Each message is delivered to only one consumer for the address. The consumer with the fewest outstanding (unsettled) deliveries will be chosen. The cost of the route to the consumer is a threshold for delivery (i.e. higher cost consumers will only receive deliveries if closer consumers are backed up).
+</p>
+</li>
+<li>
+<p>
+flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+in-proc
+</dt>
+<dd>
+<p>
+The number of in-process consumers for this address
+</p>
+</dd>
+<dt class="hdlist1">
+local
+</dt>
+<dd>
+<p>
+The number of local (on this router) consumers for this address
+</p>
+</dd>
+<dt class="hdlist1">
+remote
+</dt>
+<dd>
+<p>
+The number of remote routers that have at least one consumer for this address
+</p>
+</dd>
+<dt class="hdlist1">
+cntnr
+</dt>
+<dd>
+<p>
+The number of locally attached containers that are destinations for link-routes on this address
+</p>
+</dd>
+<dt class="hdlist1">
+in
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that entered the network on this router
+</p>
+</dd>
+<dt class="hdlist1">
+out
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that exited the network on this router
+</p>
+</dd>
+<dt class="hdlist1">
+thru
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that were forwarded to other routers
+</p>
+</dd>
+<dt class="hdlist1">
+to-proc
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that were delivered to an in-process consumer
+</p>
+</dd>
+<dt class="hdlist1">
+from-proc
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that were received from an in-process producer
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_qdstat_linkroutes">qdstat --linkroutes</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+prefix
+</dt>
+<dd>
+<p>
+The prefix for matching addresses of routed links
+</p>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction (from the router’s perspective) of matching links
+</p>
+</dd>
+<dt class="hdlist1">
+distrib
+</dt>
+<dd>
+<p>
+The distribution method used for routed links
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+linkBalanced - the only supported distribution for routed links
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+status
+</dt>
+<dd>
+<p>
+Operational status of the link route
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+active - Route is actively routing attaches (i.e. ready for use)
+</p>
+</li>
+<li>
+<p>
+inactive - Route is inactive because there is no local destination connected
+</p>
+</li>
+</ul></div>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_qstat_autolinks">qstat --autolinks</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+addr
+</dt>
+<dd>
+<p>
+The address of the auto link
+</p>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction of message flow for the auto link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+in - Messages flow in from the route-container to the router network
+</p>
+</li>
+<li>
+<p>
+out - Messages flow out to the route-container from the router network
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+phs
+</dt>
+<dd>
+<p>
+Phase of the address for this auto link
+</p>
+</dd>
+<dt class="hdlist1">
+link
+</dt>
+<dd>
+<p>
+Unique identifier of the link managed by this auto link
+</p>
+</dd>
+<dt class="hdlist1">
+status
+</dt>
+<dd>
+<p>
+The operational status of this auto link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+inactive - There is no connected container for this auto link
+</p>
+</li>
+<li>
+<p>
+attaching - The link is attaching to the container
+</p>
+</li>
+<li>
+<p>
+failed - The link-attach failed
+</p>
+</li>
+<li>
+<p>
+active - The link is operational
+</p>
+</li>
+<li>
+<p>
+quiescing - The link is quiescing (not yet supported)
+</p>
+</li>
+<li>
+<p>
+idle - The link is idle (not yet supported)
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+lastErr
+</dt>
+<dd>
+<p>
+The description of the last attach failure that occurred on this auto link
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/release-notes.md
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/release-notes.md b/input/releases/qpid-dispatch-0.7.0/release-notes.md
new file mode 100644
index 0000000..3aead5e
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/release-notes.md
@@ -0,0 +1,152 @@
+;;
+;; Licensed to the Apache Software Foundation (ASF) under one
+;; or more contributor license agreements. See the NOTICE file
+;; distributed with this work for additional information
+;; regarding copyright ownership. The ASF licenses this file
+;; to you under the Apache License, Version 2.0 (the
+;; "License"); you may not use this file except in compliance
+;; with the License. You may obtain a copy of the License at
+;;
+;; http://www.apache.org/licenses/LICENSE-2.0
+;;
+;; Unless required by applicable law or agreed to in writing,
+;; software distributed under the License is distributed on an
+;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+;; KIND, either express or implied. See the License for the
+;; specific language governing permissions and limitations
+;; under the License.
+;;
+
+# Qpid Dispatch 0.7.0 Release Notes
+
+Dispatch is a lightweight AMQP message router library. More about
+[Qpid
+Dispatch]({{site_url}}/components/dispatch-router/index.html).
+
+For more information about this release, including download links and
+documentation, see the [release overview](index.html).
+
+
+## New features and improvements
+
+ - [DISPATCH-204](https://issues.apache.org/jira/browse/DISPATCH-204) - Identity mapping from X.509 certificate data to a descriptive nickname
+ - [DISPATCH-211](https://issues.apache.org/jira/browse/DISPATCH-211) - Expose connection properties in management response
+ - [DISPATCH-233](https://issues.apache.org/jira/browse/DISPATCH-233) - Allow client side saslMechanisms to be specified for qdstat and qdmanage
+ - [DISPATCH-311](https://issues.apache.org/jira/browse/DISPATCH-311) - [Policy] schema object names could be improved
+ - [DISPATCH-348](https://issues.apache.org/jira/browse/DISPATCH-348) - Don't show deprecated entities and attributes
+ - [DISPATCH-349](https://issues.apache.org/jira/browse/DISPATCH-349) - Modify the client icon on the topology page to indicate when there are multiple clients.
+ - [DISPATCH-350](https://issues.apache.org/jira/browse/DISPATCH-350) - Display list of links for client connections. Allow acquiesce of links
+ - [DISPATCH-388](https://issues.apache.org/jira/browse/DISPATCH-388) - Add deprecated flag to schema entities and attributes
+ - [DISPATCH-395](https://issues.apache.org/jira/browse/DISPATCH-395) - Add Links to overview page
+ - [DISPATCH-399](https://issues.apache.org/jira/browse/DISPATCH-399) - Convert documentation to asciidoc format
+ - [DISPATCH-400](https://issues.apache.org/jira/browse/DISPATCH-400) - Remember last entity expanded on overview page
+ - [DISPATCH-407](https://issues.apache.org/jira/browse/DISPATCH-407) - Tweeks to Links on overview page
+ - [DISPATCH-412](https://issues.apache.org/jira/browse/DISPATCH-412) - Support 'stdout' as log destination as well as 'stderr'
+ - [DISPATCH-427](https://issues.apache.org/jira/browse/DISPATCH-427) - Implement expand/collapse all to the Overview and Entities tabs
+ - [DISPATCH-428](https://issues.apache.org/jira/browse/DISPATCH-428) - Connecting the dispatch-console to wrong port throws JS exception and freezes console
+ - [DISPATCH-434](https://issues.apache.org/jira/browse/DISPATCH-434) - Remember all entities expanded on overview and entities pages
+ - [DISPATCH-440](https://issues.apache.org/jira/browse/DISPATCH-440) - Use the placeholder HTML attribute to communicate default values in the Connect form
+ - [DISPATCH-446](https://issues.apache.org/jira/browse/DISPATCH-446) - Make sslProfile an entity and remove all annotations
+ - [DISPATCH-447](https://issues.apache.org/jira/browse/DISPATCH-447) - Modify cmake to optionally Install stand-alone and hawtio console
+ - [DISPATCH-464](https://issues.apache.org/jira/browse/DISPATCH-464) - Change plugin name from dispatch-plugin to dispatch-hawtio-console to match the artifact name
+ - [DISPATCH-468](https://issues.apache.org/jira/browse/DISPATCH-468) - Display-name for identity in x.509 certificates
+ - [DISPATCH-471](https://issues.apache.org/jira/browse/DISPATCH-471) - server.c needs refactoring around qd_connection_t allocation
+ - [DISPATCH-477](https://issues.apache.org/jira/browse/DISPATCH-477) - Drop pre-settled under congestion
+ - [DISPATCH-483](https://issues.apache.org/jira/browse/DISPATCH-483) - Display links per address and connection on overview page
+ - [DISPATCH-511](https://issues.apache.org/jira/browse/DISPATCH-511) - Remove performance problems from locks and memory allocation
+ - [DISPATCH-513](https://issues.apache.org/jira/browse/DISPATCH-513) - Add a typed iterator to parsed field (qd_parsed_field_t)
+ - [DISPATCH-514](https://issues.apache.org/jira/browse/DISPATCH-514) - Add link statistics for different dispositions
+ - [DISPATCH-515](https://issues.apache.org/jira/browse/DISPATCH-515) - Add example config file for auto starting webbroxy
+ - [DISPATCH-517](https://issues.apache.org/jira/browse/DISPATCH-517) - Expose new link statistics on overview page
+ - [DISPATCH-518](https://issues.apache.org/jira/browse/DISPATCH-518) - Use eventfd instead of a pipe for poll wakeup.
+ - [DISPATCH-520](https://issues.apache.org/jira/browse/DISPATCH-520) - Remove qpidd references from dispatch system_test.py
+ - [DISPATCH-521](https://issues.apache.org/jira/browse/DISPATCH-521) - Switch to verify qdrouterd installation
+ - [DISPATCH-522](https://issues.apache.org/jira/browse/DISPATCH-522) - Performance: Defer activation and driver-awakening
+
+## Bugs fixed
+
+ - [DISPATCH-8](https://issues.apache.org/jira/browse/DISPATCH-8) - Message:user-id must be authenticated on ingress
+ - [DISPATCH-160](https://issues.apache.org/jira/browse/DISPATCH-160) - Dispatch router does not propagate custom message annotations
+ - [DISPATCH-224](https://issues.apache.org/jira/browse/DISPATCH-224) - Tools fail with no useful error in some SASL configurations
+ - [DISPATCH-280](https://issues.apache.org/jira/browse/DISPATCH-280) - Management tools do not send AMQP Open.hostname with new proton
+ - [DISPATCH-313](https://issues.apache.org/jira/browse/DISPATCH-313) - Tree on left side of entity page scrolls back to top after data is updated
+ - [DISPATCH-316](https://issues.apache.org/jira/browse/DISPATCH-316) - Refector javascript so the common code between hawtio and standalone is not duplicated
+ - [DISPATCH-317](https://issues.apache.org/jira/browse/DISPATCH-317) - Show tooltip for long values on left panel on topology page
+ - [DISPATCH-318](https://issues.apache.org/jira/browse/DISPATCH-318) - Don't allow router nodes to be moved off of the screen on topology page
+ - [DISPATCH-336](https://issues.apache.org/jira/browse/DISPATCH-336) - Very high latency for fire-and-forget sender
+ - [DISPATCH-345](https://issues.apache.org/jira/browse/DISPATCH-345) - Initialize current node on entity page when logged into a different router network
+ - [DISPATCH-346](https://issues.apache.org/jira/browse/DISPATCH-346) - Don't attempt to load non-existant css file when hawtio plugin loads
+ - [DISPATCH-353](https://issues.apache.org/jira/browse/DISPATCH-353) - segfault in qd_entity_refresh_connection
+ - [DISPATCH-354](https://issues.apache.org/jira/browse/DISPATCH-354) - qdstat general statistics broken
+ - [DISPATCH-362](https://issues.apache.org/jira/browse/DISPATCH-362) - Handwritten paragraphs of man qdrouterd.conf are out of sync with autogenerated parts
+ - [DISPATCH-363](https://issues.apache.org/jira/browse/DISPATCH-363) - Autogenerated part of man page qdrouterd.conf and output of `qdmanage print-json-schema` leave out the `name:` attribute in annotation sections
+ - [DISPATCH-370](https://issues.apache.org/jira/browse/DISPATCH-370) - qdmanage tool hangs if --type option is "linkRoute" or "address"
+ - [DISPATCH-373](https://issues.apache.org/jira/browse/DISPATCH-373) - qdmanage : no clear error message when "read" type linkRoute, address and autoLink
+ - [DISPATCH-375](https://issues.apache.org/jira/browse/DISPATCH-375) - Console instalation instructions do not work
+ - [DISPATCH-379](https://issues.apache.org/jira/browse/DISPATCH-379) - Missing default route indication on topology page
+ - [DISPATCH-381](https://issues.apache.org/jira/browse/DISPATCH-381) - qdstat -g causes segfault
+ - [DISPATCH-384](https://issues.apache.org/jira/browse/DISPATCH-384) - qdrouter.conf manual : saslMechanisms as "Space separated list ..."
+ - [DISPATCH-389](https://issues.apache.org/jira/browse/DISPATCH-389) - Removing CONFIG and DISPATCH as modules for logging
+ - [DISPATCH-391](https://issues.apache.org/jira/browse/DISPATCH-391) - Attributes missing for listener and connector and trustedCerts still there
+ - [DISPATCH-392](https://issues.apache.org/jira/browse/DISPATCH-392) - "attributeName is undefined error" when showing "address", "linkRoute" and "autoLink"
+ - [DISPATCH-393](https://issues.apache.org/jira/browse/DISPATCH-393) - Download router configuration doesn't work
+ - [DISPATCH-394](https://issues.apache.org/jira/browse/DISPATCH-394) - Chart just added isn't shown in the dashboard
+ - [DISPATCH-396](https://issues.apache.org/jira/browse/DISPATCH-396) - The "console" entity attributes aren't shown in the qdrouterd.conf
+ - [DISPATCH-397](https://issues.apache.org/jira/browse/DISPATCH-397) - Error creating a new connector on a router with same name but on another router
+ - [DISPATCH-398](https://issues.apache.org/jira/browse/DISPATCH-398) - For Dispatch 0.7 release move up the minimum required version of qpid proton to 0.13.0
+ - [DISPATCH-401](https://issues.apache.org/jira/browse/DISPATCH-401) - qdstat and qdmanage client tools do not verify host name when using SSL
+ - [DISPATCH-402](https://issues.apache.org/jira/browse/DISPATCH-402) - Remove deprecated hyphen-separated config and entity names
+ - [DISPATCH-405](https://issues.apache.org/jira/browse/DISPATCH-405) - Chart data should be cleared when the console disconnects
+ - [DISPATCH-406](https://issues.apache.org/jira/browse/DISPATCH-406) - Area charts only show the top line in Firefox.
+ - [DISPATCH-414](https://issues.apache.org/jira/browse/DISPATCH-414) - Deleting a ProxyListener from dispatch-console segfaults the router
+ - [DISPATCH-416](https://issues.apache.org/jira/browse/DISPATCH-416) - Connecting the dispatch-console to wrong host displays incomplete error message
+ - [DISPATCH-417](https://issues.apache.org/jira/browse/DISPATCH-417) - "There are no policyStatss" in dispatch-console
+ - [DISPATCH-418](https://issues.apache.org/jira/browse/DISPATCH-418) - Deleting an address in the dispatch-console does not work
+ - [DISPATCH-425](https://issues.apache.org/jira/browse/DISPATCH-425) - Tree on the left side gets rerendered when navigating in dispatch-console preferences
+ - [DISPATCH-426](https://issues.apache.org/jira/browse/DISPATCH-426) - The left tree view in Overview tab allows opening multiple branches at once. Tree view in Entities tab behives like accordeon.
+ - [DISPATCH-431](https://issues.apache.org/jira/browse/DISPATCH-431) - Do not link to http://127.0.0.1:8080/dispatch-plugin
+ - [DISPATCH-435](https://issues.apache.org/jira/browse/DISPATCH-435) - Dragging a node to a corner on the topology screen leads to a visual disconnect between the node and its link
+ - [DISPATCH-436](https://issues.apache.org/jira/browse/DISPATCH-436) - Releasing the mouse button outside of the Topology SVG when dragging a node causes the node follow the mouse even if the mouse button is not pressed
+ - [DISPATCH-439](https://issues.apache.org/jira/browse/DISPATCH-439) - Connect form cannot be submitted using only keyboard
+ - [DISPATCH-442](https://issues.apache.org/jira/browse/DISPATCH-442) - system_tests_sasl_plain and system_tests_deprecated failing on Ubuntu
+ - [DISPATCH-444](https://issues.apache.org/jira/browse/DISPATCH-444) - Add full entity type to schema
+ - [DISPATCH-445](https://issues.apache.org/jira/browse/DISPATCH-445) - Use fullyQualifiedType from the schema when calling methods
+ - [DISPATCH-449](https://issues.apache.org/jira/browse/DISPATCH-449) - Link-leak for attach-routed links
+ - [DISPATCH-452](https://issues.apache.org/jira/browse/DISPATCH-452) - Prevent javascript alerts on Entities and Topology pages when new routers join network
+ - [DISPATCH-453](https://issues.apache.org/jira/browse/DISPATCH-453) - Reserve the right column on the topology page for the legend
+ - [DISPATCH-454](https://issues.apache.org/jira/browse/DISPATCH-454) - Legend on topology page is too tall
+ - [DISPATCH-455](https://issues.apache.org/jira/browse/DISPATCH-455) - When autostart is checked and there is no router listening, FF generates a stream of error popups
+ - [DISPATCH-456](https://issues.apache.org/jira/browse/DISPATCH-456) - Redirect back to connect page as soon as connection is dropped
+ - [DISPATCH-457](https://issues.apache.org/jira/browse/DISPATCH-457) - Overview page does not update after router is added/removed from network
+ - [DISPATCH-458](https://issues.apache.org/jira/browse/DISPATCH-458) - Batching of settlement can cause credit to be not issued to senders
+ - [DISPATCH-461](https://issues.apache.org/jira/browse/DISPATCH-461) - [Policy] policyStats object missed being renamed to vhostStats
+ - [DISPATCH-462](https://issues.apache.org/jira/browse/DISPATCH-462) - [Policy] Policy and vhost objects not named correctly by agent
+ - [DISPATCH-463](https://issues.apache.org/jira/browse/DISPATCH-463) - [Policy] Remove wildcard user name description from policy doc
+ - [DISPATCH-473](https://issues.apache.org/jira/browse/DISPATCH-473) - Deleting an SSL Profile used by a listener sometimes causes the router to crash
+ - [DISPATCH-479](https://issues.apache.org/jira/browse/DISPATCH-479) - Use atomic operations for ref counts
+ - [DISPATCH-482](https://issues.apache.org/jira/browse/DISPATCH-482) - trace level log messages are printing out as null
+ - [DISPATCH-484](https://issues.apache.org/jira/browse/DISPATCH-484) - Update tree icons on overview and entities pages
+ - [DISPATCH-485](https://issues.apache.org/jira/browse/DISPATCH-485) - All routers table on overview page is missing data
+ - [DISPATCH-486](https://issues.apache.org/jira/browse/DISPATCH-486) - Data table on entities page has no left margin
+ - [DISPATCH-487](https://issues.apache.org/jira/browse/DISPATCH-487) - Missing header on Quiesce button column
+ - [DISPATCH-488](https://issues.apache.org/jira/browse/DISPATCH-488) - Provide a notification system for stand-alone console
+ - [DISPATCH-489](https://issues.apache.org/jira/browse/DISPATCH-489) - Fetching logs entries on Entities page no longer works
+ - [DISPATCH-491](https://issues.apache.org/jira/browse/DISPATCH-491) - Frequent skipped HELLO message from route engine
+ - [DISPATCH-494](https://issues.apache.org/jira/browse/DISPATCH-494) - Policy objects do not support management update and delete directives
+ - [DISPATCH-495](https://issues.apache.org/jira/browse/DISPATCH-495) - Autolinks to non-existent nodes cause problems in the router
+ - [DISPATCH-496](https://issues.apache.org/jira/browse/DISPATCH-496) - Activation of an autolink does not result in issuing credit to a blocked sender
+ - [DISPATCH-498](https://issues.apache.org/jira/browse/DISPATCH-498) - memory leak in _configure_ssl_profile error path
+ - [DISPATCH-499](https://issues.apache.org/jira/browse/DISPATCH-499) - in propagating link detach the info field is dropped
+ - [DISPATCH-500](https://issues.apache.org/jira/browse/DISPATCH-500) - name in conf file is not sent in response to management query
+ - [DISPATCH-501](https://issues.apache.org/jira/browse/DISPATCH-501) - router segfaults if you sent a management query with an empty body
+ - [DISPATCH-502](https://issues.apache.org/jira/browse/DISPATCH-502) - Seeing unexpected values in management query response
+ - [DISPATCH-505](https://issues.apache.org/jira/browse/DISPATCH-505) - Eventual loss of credit on inter-router control links when the topology changes
+ - [DISPATCH-507](https://issues.apache.org/jira/browse/DISPATCH-507) - Switching between hawtio console and stand-alone causes problems
+ - [DISPATCH-508](https://issues.apache.org/jira/browse/DISPATCH-508) - Self tests use deprecated configuration objects
+ - [DISPATCH-523](https://issues.apache.org/jira/browse/DISPATCH-523) - Topology changes can cause in-flight deliveries to be stuck in the ingress router
+ - [DISPATCH-524](https://issues.apache.org/jira/browse/DISPATCH-524) - Unfair handling of multiple connections to the router
+ - [DISPATCH-532](https://issues.apache.org/jira/browse/DISPATCH-532) - man pages installed in wrong directory (man.X)
+ - [DISPATCH-533](https://issues.apache.org/jira/browse/DISPATCH-533) - Router crash in the 6-node example
+ - [DISPATCH-535](https://issues.apache.org/jira/browse/DISPATCH-535) - Use correct lifecycle management for Proton objects
+ - [DISPATCH-550](https://issues.apache.org/jira/browse/DISPATCH-550) - Assertion failure in router in larger scale networks
+ - [DISPATCH-558](https://issues.apache.org/jira/browse/DISPATCH-558) - Remove assertions in the core agent that fail due to malformed requests
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/scripts/gen-dispatch-release-books
----------------------------------------------------------------------
diff --git a/scripts/gen-dispatch-release-books b/scripts/gen-dispatch-release-books
index b48f29c..2284859 100755
--- a/scripts/gen-dispatch-release-books
+++ b/scripts/gen-dispatch-release-books
@@ -29,15 +29,21 @@ def gen_books_and_man(release, source_dir, output_dir):
call("make")
call("make doc")
- book_build_dir = join(build_dir, "doc", "html", "book")
+ book_build_dir = join(build_dir, "doc", "book")
- for f in list_dir(book_build_dir, "*.html"):
+ for f in list_dir(book_build_dir, "*.html.in"):
input_file = join(book_build_dir, f)
- output_file = join(output_dir, "book", "{}.in".format(f))
+ output_file = join(output_dir, "book", f)
copy(input_file, output_file)
- book_image_dir = join(build_dir, "doc", "html", "_images")
+ for f in list_dir(book_build_dir, "*.png"):
+ input_file = join(book_build_dir, f)
+ output_file = join(output_dir, "book", f)
+
+ copy(input_file, output_file)
+
+ book_image_dir = join(build_dir, "doc", "_images")
for f in list_dir(book_image_dir, "*"):
input_file = join(book_image_dir, f)
@@ -45,11 +51,11 @@ def gen_books_and_man(release, source_dir, output_dir):
copy(input_file, output_file)
- man_build_dir = join(build_dir, "doc", "html", "man")
+ man_build_dir = join(build_dir, "doc", "man")
- for f in list_dir(man_build_dir, "*.html"):
+ for f in list_dir(man_build_dir, "*.html.in"):
input_file = join(man_build_dir, f)
- output_file = join(output_dir, "man", "{}.in".format(f))
+ output_file = join(output_dir, "man", f)
copy(input_file, output_file)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[2/6] qpid-site git commit: NO-JIRA - Updating documentation for Qpid
Dispatch Router version 0.7.0
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/book.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/book.html.in b/input/releases/qpid-dispatch-0.7.0/book/book.html.in
new file mode 100644
index 0000000..4432a71
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.7.0/book/book.html.in
@@ -0,0 +1,4160 @@
+<div class="sect1">
+<h2 id="introduction">1. Introduction</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="overview">1.1. Overview</h3>
+<div class="paragraph"><p>The Dispatch router is an AMQP message router that provides
+advanced interconnect capabilities. It allows flexible routing of
+messages between any AMQP-enabled endpoints, whether they be clients,
+servers, brokers or any other entity that can send or receive standard
+AMQP messages.</p></div>
+<div class="paragraph"><p>A messaging client can make a single AMQP connection into a messaging
+bus built of Dispatch routers and, over that connection, exchange
+messages with one or more message brokers, and at the same time exchange
+messages directly with other endpoints without involving a broker at
+all.</p></div>
+<div class="paragraph"><p>The router is an intermediary for messages but it is <em>not</em> a broker. It
+does not <em>take responsibility for</em> messages. It will, however, propagate
+settlement and disposition across a network such that delivery
+guarantees are met. In other words: the router network will deliver the
+message, possibly via several intermediate routers, <em>and</em> it will route
+the acknowledgement of that message by the ultimate receiver back across
+the same path. This means that <em>responsibility</em> for the message is
+transfered from the original sender to the ultimate receiver <em>as if
+they were directly connected</em>. However this is done via a flexible
+network that allows highly configurable routing of the message
+transparent to both sender and receiver.</p></div>
+<div class="paragraph"><p>There are some patterns where this enables "brokerless messaging"
+approaches that are preferable to brokered approaches. In other cases a
+broker is essential (in particular where you need the separation of
+responsibility and/or the buffering provided by store-and-forward) but a
+dispatch network can still be useful to tie brokers and clients together
+into patterns that are difficult with a single broker.</p></div>
+<div class="paragraph"><p>For a "brokerless" example, consider the common brokered implementation
+of the request-response pattern, a client puts a request on a queue and
+then waits for a reply on another queue. In this case the broker can be
+a hindrance - the client may want to know immediatly if there is nobody
+to serve the request, but typically it can only wait for a timeout to
+discover this. With a dispatch network, the client can be informed
+immediately if its message cannot be delivered because nobody is
+listening. When the client receives acknowledgement of the request it
+knows not just that it is sitting on a queue, but that it has actually
+been received by the server.</p></div>
+<div class="paragraph"><p>For an exampe of using dispatch to enhance the use of brokers, consider
+using an array of brokers to implement a scalable distributed work
+queue. A dispatch network can make this appear as a single queue, with
+senders publishing to a single address and receivers subscribing to a
+single address. The dispatch network can distribute work to any broker
+in the array and collect work from any broker for any receiver. Brokers
+can be shut down or added without affecting clients. This elegantly
+solves the common difficulty of "stuck messages" when implementing this
+pattern with brokers alone. If a receiver is connected to a broker that
+has no messages, but there are messages on another broker, you have to
+somehow transfer them or leave them "stuck". With a dispatch network,
+<em>all</em> the receivers are connected to <em>all</em> the brokers. If there is a
+message anywhere it can be delivered to any receiver.</p></div>
+<div class="paragraph"><p>The router is meant to be deployed in topologies of multiple routers,
+preferably with redundant paths. It uses link-state routing protocols
+and algorithms (similar to OSPF or IS-IS from the networking world) to
+calculate the best path from every point to every other point and to
+recover quickly from failures. It does not need to use clustering for
+high availability; rather, it relies on redundant paths to provide
+continued connectivity in the face of system or network failure. Because
+it never takes responsibility for messages it is effectively stateless.
+Messages not delivered to their final destination will not be
+acknowledged to the sender and therefore the sender can re-send such
+messages if it is disconnected from the network.</p></div>
+</div>
+<div class="sect2">
+<h3 id="benefits">1.2. Benefits</h3>
+<div class="paragraph"><p>Simplifies connectivity</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+An endpoint can do all of its messaging through a single transport
+connection
+</p>
+</li>
+<li>
+<p>
+Avoid opening holes in firewalls for incoming connections
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Provides messaging connectivity where there is no TCP/IP connectivity</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+A server or broker can be in a private IP network (behind a NAT
+firewall) and be accessible by messaging endpoints in other networks
+(learn more).
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Simplifies reliability</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Reliability and availability are provided using redundant topology,
+not server clustering
+</p>
+</li>
+<li>
+<p>
+Reliable end-to-end messaging without persistent stores
+</p>
+</li>
+<li>
+<p>
+Use a message broker only when you need store-and-forward semantics
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="features">1.3. Features</h3>
+<div class="ulist"><ul>
+<li>
+<p>
+Can be deployed stand-alone or in a network of routers
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Supports arbitrary network topology - no restrictions on redundancy
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Automatic route computation - adjusts quickly to changes in topology
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+Provides remote access to brokers or other AMQP servers
+</p>
+</li>
+<li>
+<p>
+Security
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="using-qpid-dispatch">2. Using Qpid Dispatch</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="configuration">2.1. Configuration</h3>
+<div class="paragraph"><p>The default configuration file is installed in
+<em>/usr/local/etc/qpid-dispatch/qdrouterd.conf</em>. This configuration file will
+cause the router to run in standalone mode, listening on the standard
+AMQP port (5672). Dispatch Router looks for the configuration file in
+the installed location by default. If you wish to use a different path,
+the "-c" command line option will instruct Dispatch Router as to which
+configuration to load.</p></div>
+<div class="paragraph"><p>To run the router, invoke the executable: <code>qdrouterd [-c my-config-file]</code></p></div>
+<div class="paragraph"><p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
+page.</p></div>
+</div>
+<div class="sect2">
+<h3 id="tools">2.2. Tools</h3>
+<div class="sect3">
+<h4 id="qdstat">2.2.1. qdstat</h4>
+<div class="paragraph"><p><em>qdstat</em> is a command line tool that lets you view the status of a
+Dispatch Router. The following options are useful for seeing what the
+router is doing:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="17%" />
+<col width="83%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Option</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">-l</p></td>
+<td align="left" valign="top"><p class="table">Print a list of AMQP links attached to the router. Links are
+unidirectional. Outgoing links are usually associated with a
+subscription address. The tool distinguishes between <em>endpoint</em> links
+and <em>router</em> links. Endpoint links are attached to clients using the
+router. Router links are attached to other routers in a network of
+routbers.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">-a</p></td>
+<td align="left" valign="top"><p class="table">Print a list of addresses known to the router.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">-n</p></td>
+<td align="left" valign="top"><p class="table">Print a list of known routers in the network.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">-c</p></td>
+<td align="left" valign="top"><p class="table">Print a list of connections to the router.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">--autolinks</p></td>
+<td align="left" valign="top"><p class="table">Print a list of configured auto-links.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">--linkroutes</p></td>
+<td align="left" valign="top"><p class="table">Print a list of configures link-routes.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="paragraph"><p>For complete details see the <em>qdstat(8)</em> man page and the output of
+<code>qdstat --help</code>.</p></div>
+</div>
+<div class="sect3">
+<h4 id="qdmanage">2.2.2. qdmanage</h4>
+<div class="paragraph"><p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
+to not only view but modify the configuration of a running dispatch
+router.</p></div>
+<div class="paragraph"><p>For example you can query all the connection entities in the router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage query --type connection</code></pre>
+</div></div>
+<div class="paragraph"><p>To enable logging debug and higher level messages by default:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage update log/DEFAULT enable=debug+</code></pre>
+</div></div>
+<div class="paragraph"><p>In fact, everything that can be configured in the configuration file can
+also be created in a running router via management. For example to
+create a new listener in a running router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage create type=listener port=5555</code></pre>
+</div></div>
+<div class="paragraph"><p>Now you can connect to port 5555, for exampple:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage query -b localhost:5555 --type listener</code></pre>
+</div></div>
+<div class="paragraph"><p>For complete details see the <em>qdmanage(8)</em> man page and the output of
+<code>qdmanage --help</code>. Also for details of what can be configured see the
+<em>qdrouterd.conf(5)</em> man page.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="basic-usage-and-examples">2.3. Basic Usage and Examples</h3>
+<div class="sect3">
+<h4 id="standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</h4>
+<div class="paragraph"><p>The router can operate stand-alone or as a node in a network of routers.
+The mode is configured in the <em>router</em> section of the configuration
+file. In stand-alone mode, the router does not attempt to collaborate
+with any other routers and only routes messages among directly connected
+endpoints.</p></div>
+<div class="paragraph"><p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
+like the following:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ===============================================================================================================
+ local $_management_internal closest 1 0 0 0 0 0 0 0 0
+ local $displayname closest 1 0 0 0 0 0 0 0 0
+ mobile $management 0 closest 1 0 0 0 1 0 0 1 0
+ local $management closest 1 0 0 0 0 0 0 0 0
+ local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>Note that there are a number of known addresses. <em>$management</em> is the
+address of the router’s embedded management agent.
+<em>temp.1GThUllfR7N+BDP</em> is the temporary reply-to address of the <em>qdstat</em>
+client making requests to the agent.</p></div>
+<div class="paragraph"><p>If you change the mode to interior and restart the processs, the same
+command will yield additional addresses which are used for inter-router
+communication:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ =================================================================================================================
+ local $_management_internal closest 1 0 0 0 0 0 0 0 0
+ local $displayname closest 1 0 0 0 0 0 0 0 0
+ mobile $management 0 closest 1 0 0 0 1 0 0 1 0
+ local $management closest 1 0 0 0 0 0 0 0 0
+ local qdhello flood 1 0 0 0 0 0 0 0 10
+ local qdrouter flood 1 0 0 0 0 0 0 0 0
+ topo qdrouter flood 1 0 0 0 0 0 0 0 1
+ local qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
+ topo qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
+ local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0</code></pre>
+</div></div>
+</div>
+<div class="sect3">
+<h4 id="mobile-subscribers">2.3.2. Mobile Subscribers</h4>
+<div class="paragraph"><p>The term "mobile subscriber" simply refers to the fact that a client may
+connect to the router and subscribe to an address to receive messages
+sent to that address. No matter where in the network the subscriber
+attaches, the messages will be routed to the appropriate destination.</p></div>
+<div class="paragraph"><p>To illustrate a subscription on a stand-alone router, you can use the
+examples that are provided with Qpid Proton. Using the <em>simple_recv.py</em>
+example receiver:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python ./simple_recv.py -a 127.0.0.1/my-address</code></pre>
+</div></div>
+<div class="paragraph"><p>This command creates a receiving link subscribed to the specified
+address. To verify the subscription:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ===============================================================================================================
+ local $_management_internal closest 1 0 0 0 0 0 0 0 0
+ local $displayname closest 1 0 0 0 0 0 0 0 0
+ mobile $management 0 closest 1 0 0 0 2 0 0 2 0
+ local $management closest 1 0 0 0 0 0 0 0 0
+ mobile my-address 0 closest 0 1 0 0 0 0 0 0 0
+ local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>You can then, in a separate command window, run a sender to produce
+messages to that address:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python ./simple_send.py -a 127.0.0.1/my-address</code></pre>
+</div></div>
+</div>
+<div class="sect3">
+<h4 id="dynamic-reply-to">2.3.3. Dynamic Reply-To</h4>
+<div class="paragraph"><p>Dynamic reply-to can be used to obtain a reply-to address that routes
+back to a client’s receiving link regardless of how many hops it has to
+take to get there. To illustrate this feature, see below a simple
+program (written in C++ against the qpid::messaging API) that queries
+the management agent of the attached router for a list of other known
+routers' management addresses.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>#include <qpid/messaging/Address.h>
+#include <qpid/messaging/Connection.h>
+#include <qpid/messaging/Message.h>
+#include <qpid/messaging/Receiver.h>
+#include <qpid/messaging/Sender.h>
+#include <qpid/messaging/Session.h>
+
+using namespace qpid::messaging;
+using namespace qpid::types;
+
+using std::stringstream;
+using std::string;
+
+int main() {
+ const char* url = "amqp:tcp:127.0.0.1:5672";
+ std::string connectionOptions = "{protocol:amqp1.0}";
+
+ Connection connection(url, connectionOptions);
+ connection.open();
+ Session session = connection.createSession();
+ Sender sender = session.createSender("mgmt");
+
+ // create reply receiver and get the reply-to address
+ Receiver receiver = session.createReceiver("#");
+ Address responseAddress = receiver.getAddress();
+
+ Message request;
+ request.setReplyTo(responseAddress);
+ request.setProperty("x-amqp-to", "amqp:/_local/$management");
+ request.setProperty("operation", "DISCOVER-MGMT-NODES");
+ request.setProperty("type", "org.amqp.management");
+ request.setProperty("name, "self");
+
+ sender.send(request);
+ Message response = receiver.fetch();
+ Variant content(response.getContentObject());
+ std::cout << "Response: " << content << std::endl << std::endl;
+
+ connection.close();
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The equivalent program written in Python against the Proton Messenger
+API:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>from proton import Messenger, Message
+
+def main():
+ host = "0.0.0.0:5672"
+
+ messenger = Messenger()
+ messenger.start()
+ messenger.route("amqp:/*", "amqp://%s/$1" % host)
+ reply_subscription = messenger.subscribe("amqp:/#")
+ reply_address = reply_subscription.address
+
+ request = Message()
+ response = Message()
+
+ request.address = "amqp:/_local/$management"
+ request.reply_to = reply_address
+ request.properties = {u'operation' : u'DISCOVER-MGMT-NODES',
+ u'type' : u'org.amqp.management',
+ u'name' : u'self'}
+
+ messenger.put(request)
+ messenger.send()
+ messenger.recv()
+ messenger.get(response)
+
+ print "Response: %r" % response.body
+
+ messenger.stop()
+
+main()</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="link-routing">2.4. Link Routing</h3>
+<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.4. This feature was
+significantly updated in Qpid Dispatch 0.6.</p></div>
+<div class="paragraph"><p>Link-routing is an alternative strategy for routing messages across a
+network of routers. With the existing message-routing strategy, each
+router makes a routing decision on a per-message basis when the message
+is delivered. Link-routing is different because it makes routing
+decisions when link-attach frames arrive. A link is effectively chained
+across the network of routers from the establishing node to the
+destination node. Once the link is established, the transfer of message
+deliveries, flow frames, and dispositions is performed across the routed
+link.</p></div>
+<div class="paragraph"><p>The main benefit to link-routing is that endpoints can use the full link
+protocol to interact with other endpoints in far-flung parts of the
+network. For example, a client can establish a receiver across the
+network to a queue on a remote broker and use link credit to control
+the flow of messages from the broker. Similarly, a receiver can
+establish a link to a topic on a remote broker using a server-side
+filter.</p></div>
+<div class="paragraph"><p>Why would one want to do this? One reason is to provide client
+isolation. A network like the following can be deployed:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> Public Network
+ +-----------------+
+ | +-----+ |
+ | B1 | Rp | |
+ | +/--\-+ |
+ | / \ |
+ | / \ |
+ +----/--------\---+
+ / \
+ / \
+ / \
+ Private Net A / \ Private Net B
+ +--------------/--+ +---\-------------+
+ | +---/-+ | | +--\--+ |
+ | B2 | Ra | | | | Rb | C1 |
+ | +-----+ | | +-----+ |
+ | | | |
+ | | | |
+ +-----------------+ +-----------------+</code></pre>
+</div></div>
+<div class="paragraph"><p>The clients in Private Net B can be constrained (by firewall policy)
+to only connect to the Router in their own network. Using
+link-routing, these clients can access queues, topics, and other AMQP
+services that are in the Public Network or even in Private Net A.</p></div>
+<div class="paragraph"><p>For example, The router Ra can be configured to expose queues in
+broker B2 to the network. Client C1 can then establish a connection
+to Rb, the local router, open a subscribing link to "b2.event-queue",
+and receive messages stored on that queue in broker B2.</p></div>
+<div class="paragraph"><p>C1 is unable to create a TCP/IP connection to B1 because of its
+isolation (and because B2 is itself in a private network). However, with
+link routing, C1 can interact with B2 using the AMQP link protocol.</p></div>
+<div class="paragraph"><p>Note that in this case, neither C1 nor B2 have been modified in any way
+and neither need be aware of the fact that there is a message-router
+network between them.</p></div>
+<div class="sect3">
+<h4 id="link-routing-configuration">2.4.1. Configuration</h4>
+<div class="paragraph"><p>Starting with the configured topology shown above, how is link-routing
+configured to support the example described above?</p></div>
+<div class="paragraph"><p>First, router Ra needs to be told how to make a connection to the broker
+B2:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ name: broker
+ role: route-container
+ host: <B2-url>
+ port: <B2-port>
+ saslMechanisms: ANONYMOUS
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>This <em>route-container</em> connector tells the router how to connect to an
+external AMQP container when it is needed. The name "broker" will be
+used later to refer to this connection.</p></div>
+<div class="paragraph"><p>Now, the router must be configured to route certain addresses to B2:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>linkRoute {
+ prefix: b2
+ dir: in
+ connection: broker
+}
+
+linkRoute {
+ prefix: b2
+ dir: out
+ connection: broker
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The linkRoute tells router Ra that any sender or receiver that is
+attached with a target or source (respectively) whos address begins with
+"b2", should be routed to the broker B2 (via the route-container
+connector).</p></div>
+<div class="paragraph"><p>Note that receiving and sending links are configured and routed
+separately. This allows configuration of link routes for listeners only
+or senders only. A direction of "in" matches client senders (i.e. links
+that carry messages inbound to the router network). Direction "out"
+matches client receivers.</p></div>
+<div class="paragraph"><p>Examples of addresses that "begin with <em>b2</em>" include:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+b2
+</p>
+</li>
+<li>
+<p>
+b2.queues
+</p>
+</li>
+<li>
+<p>
+b2.queues.app1
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>When the route-container connector is configured, router Ra establishes
+a connection to the broker. Once the connection is open, Ra tells the
+other routers (Rp and Rb) that it is a valid destination for link-routes
+to the "b2" prefix. This means that sender or receiver links attached to
+Rb or Rp will be routed via the shortest path to Ra where they are then
+routed outbound to the broker B2.</p></div>
+<div class="paragraph"><p>On Rp and Rb, it is advisable to add the identical configuration. It is
+permissible for a linkRoute configuration to reference a connection that
+does not exist.</p></div>
+<div class="paragraph"><p>This configuration tells the routers that link-routing is intended to be
+available for targets and sources starting with "b2". This is important
+because it is possible that B2 might be unavailable or shut off. If B2
+is unreachable, Ra will not advertize itself as a destination for "b2"
+and the other routers might never know that "b2" was intended for
+link-routing.</p></div>
+<div class="paragraph"><p>The above configuration allows Rb and Rp to reject attaches that should
+be routed to B2 with an error message that indicates that there is no
+route available to the destination.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="indirect-waypoints-and-auto-links">2.5. Indirect Waypoints and Auto-Links</h3>
+<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
+improvement on an earlier somewhat experimental feature called
+Waypoints.</p></div>
+<div class="paragraph"><p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
+actively attach a link to a node on an external AMQP container. The
+obvious application for this feature is to route messages through a
+queue on a broker, but other applications are possible as well.</p></div>
+<div class="paragraph"><p>An auto-link manages the lifecycle of one AMQP link. If messages are to
+be routed to and from a queue on a broker, then two auto-links are
+needed: one for sending messages to the queue and another for receiving
+messages from the queue. The container to which an auto-link attempts to
+attach may be identified in one of two ways:</p></div>
+<div class="quoteblock">
+<div class="content">
+<div class="ulist"><ul>
+<li>
+<p>
+The name of the connector/listener that resulted in the connection of
+the container, or
+</p>
+</li>
+<li>
+<p>
+The AMQP container-id of the remote container.
+</p>
+</li>
+</ul></div>
+</div>
+<div class="attribution">
+</div></div>
+<div class="sect3">
+<h4 id="queue-waypoint-example">2.5.1. Queue Waypoint Example</h4>
+<div class="paragraph"><p>Here is an example configuration for routing messages deliveries through
+a pair of queues on a broker:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ name: broker
+ role: route-container
+ host: <hostname>
+ port: <port>
+ saslMechanisms: ANONYMOUS
+}
+
+address {
+ prefix: queue
+ waypoint: yes
+}
+
+autoLink {
+ addr: queue.first
+ dir: in
+ connection: broker
+}
+
+autoLink {
+ addr: queue.first
+ dir: out
+ connection: broker
+}
+
+autoLink {
+ addr: queue.second
+ dir: in
+ connection: broker
+}
+
+autoLink {
+ addr: queue.second
+ dir: out
+ connection: broker
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
+for routing messages through queues via autolinks. The four <code>autoLink</code> entities
+identify the head and tail of two queues on the broker that will be connected
+via auto-links.</p></div>
+<div class="paragraph"><p>If there is no broker connected, the auto-links shall remain
+<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat --autolinks
+AutoLinks
+ addr dir phase link status lastErr
+ ===================================================
+ queue.first in 1 inactive
+ queue.first out 0 inactive
+ queue.second in 1 inactive
+ queue.second out 0 inactive</code></pre>
+</div></div>
+<div class="paragraph"><p>If a broker comes online with a queue called <em>queue.first</em>, the
+auto-links will attempt to activate:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat --autolinks
+AutoLinks
+ addr dir phase link status lastErr
+ ======================================================================
+ queue.first in 1 6 active
+ queue.first out 0 7 active
+ queue.second in 1 failed Node not found: queue.second
+ queue.second out 0 failed Node not found: queue.second</code></pre>
+</div></div>
+<div class="paragraph"><p>Note that two of the auto-links are in <em>failed</em> state because the queue
+does not exist on the broker.</p></div>
+<div class="paragraph"><p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
+three messages to <em>queue.first</em> via the router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python simple_send.py -a 127.0.0.1/queue.first -m3
+all messages confirmed</code></pre>
+</div></div>
+<div class="paragraph"><p>and then look at the address statistics on the router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ========================================================================================================
+ mobile queue.first 1 balanced 0 0 0 0 0 0 0 0 0
+ mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>we see that <em>queue.first</em> appears twice in the list of addresses. The
+<code>phs</code>, or phase column shows that there are two phases for the
+address. Phase <em>0</em> is for routing message deliveries from producers to
+the tail of the queue (the <code>out</code> auto-link associated with the queue).
+Phase 1 is for routing deliveries from the head of the queue to
+subscribed consumers.</p></div>
+<div class="paragraph"><p>Note that three deliveries have been counted in the "in" and "out"
+columns for phase <em>0</em>. The "in" column represents the three messages
+that arrived from <code>simple_send.py</code> and the <code>out</code> column represents the three
+deliveries to the queue on the broker.</p></div>
+<div class="paragraph"><p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python simple_recv.py -a 127.0.0.1:5672/queue.first -m3
+{u'sequence': int32(1)}
+{u'sequence': int32(2)}
+{u'sequence': int32(3)}</code></pre>
+</div></div>
+<div class="paragraph"><p>We receive the three queued messages. Looking at the addresses again, we
+see that phase 1 was used to deliver those messages from the queue to
+the consumer.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ========================================================================================================
+ mobile queue.first 1 balanced 0 0 0 0 3 3 0 0 0
+ mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>Note that even in a multi-router network, and with multiple producers
+and consumers for <em>queue.first</em>, all deliveries will be routed through
+the queue on the connected broker.</p></div>
+</div>
+<div class="sect3">
+<h4 id="sharded-queue-example">2.5.2. Sharded Queue Example</h4>
+<div class="paragraph"><p>Here is an extension of the above example to illustrate how Qpid
+Dispatch Router can be used to create a distributed queue in which
+multiple brokers share the message-queueing load.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ name: broker1
+ role: route-container
+ host: <hostname>
+ port: <port>
+ saslMechanisms: ANONYMOUS
+}
+
+connector {
+ name: broker2
+ role: route-container
+ host: <hostname>
+ port: <port>
+ saslMechanisms: ANONYMOUS
+}
+
+address {
+ prefix: queue
+ waypoint: yes
+}
+
+autoLink {
+ addr: queue.first
+ dir: in
+ connection: broker1
+}
+
+autoLink {
+ addr: queue.first
+ dir: out
+ connection: broker1
+}
+
+autoLink {
+ addr: queue.first
+ dir: in
+ connection: broker2
+}
+
+autoLink {
+ addr: queue.first
+ dir: out
+ connection: broker2
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>In the above configuration, there are two instances of <em>queue.first</em> on
+brokers 1 and 2. Message traffic from producers to address <em>queue.first</em>
+shall be balanced between the two instance and messages from the queues
+shall be balanced across the collection of subscribers to the same
+address.</p></div>
+</div>
+<div class="sect3">
+<h4 id="dynamically-adding-shards">2.5.3. Dynamically Adding Shards</h4>
+<div class="paragraph"><p>Since configurable entities in the router can also be accessed via the
+management protocol, we can remotely add a shard to the above example
+using <code>qdmanage</code>:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>qdmanage create --type org.apache.qpid.dispatch.connector host=<host> port=<port> name=broker3
+qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=in connection=broker3
+qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=out connection=broker3</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="policy">2.6. Policy</h3>
+<div class="paragraph"><p>The Policy module is an optional authorization mechanism enforcing
+user connection restrictions and AMQP resource access control.</p></div>
+<div class="paragraph"><p>Policy is assigned when a connection is created. The connection
+properties <strong>AMQP virtual host</strong>, <strong>authenticated user name</strong>, and <strong>connection
+remote host</strong> are passed to the policy engine for a connection
+allow/deny decision. If the connection is allowed then the user is
+assigned to a group that names a set of AMQP resource limits that are
+enforced for the lifetime of the connection.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+<div class="paragraph"><p>Policy limits are applied only to incoming user network connections.
+Policy limits are not applied to interrouter connections nor are they
+applied to router connections outbound to waypoints.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="sect3">
+<h4 id="_definitions">2.6.1. Definitions</h4>
+<div class="sect4">
+<h5 id="_vhost">vhost</h5>
+<div class="paragraph"><p>A <em>vhost</em> is typically the name of the host to which the client AMQP
+connection is directed. For example, suppose a client application opens
+connection URL:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>amqp://bigbroker.example.com:5672/favorite_subject</code></pre>
+</div></div>
+<div class="paragraph"><p>The client will signal virtual host name <em>bigbroker.example.com</em> to
+the router during AMQP connection startup. Router Policy intercepts
+the virtual host <em>bigbroker.example.com</em> and applies a vhost policy
+with that name to the connection.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_policy_features">2.6.2. Policy Features</h4>
+<div class="sect4">
+<h5 id="_total_connection_limit">Total Connection Limit</h5>
+<div class="paragraph"><p>A router may be configured with a total connection limit. This limit
+controls the maximum number of simultaneous incoming user connections
+that are allowed at any time. It protects the router from file
+descriptor resource exhaustion in the face of many incoming client
+connections. This limit is specified and enforced independently of
+any other Policy settings.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_vhost_policy">Vhost Policy</h5>
+<div class="paragraph"><p>Vhost policy defines users and assigns them to user groups. Each
+user group defines the remote hosts from which the members may connect
+to the router network, and what resources in the router network the
+group members are allowed to access.</p></div>
+<div class="paragraph"><p>Vhost policy also defines connection count limits to control the
+number of users that may be simultaneously connected to the vhost.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+<div class="paragraph"><p>A vhost user may be assigned to one user group only.</p></div>
+</td>
+</tr></table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_default_vhost">Default Vhost</h5>
+<div class="paragraph"><p>A default vhost may be defined. The default vhost policy is used for
+connections whose vhost is otherwise not defined in the policy database.</p></div>
+<div class="paragraph"><p><a href="#example2">Example 2</a> illustrates how the default vhost feature can
+be used to apply a single vhost policy set of restrictions to any
+number of vhost connections.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_policy_schema">2.6.3. Policy Schema</h4>
+<div class="paragraph"><p>Policy configuration is specified in two schema objects.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>policy = {
+ <global settings>
+}
+
+vhost = {
+ id: vhost-name
+ <connection limits>
+ groups: {
+ group-name: {
+ <user group settings>
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The <em>policy</em> object is a singleton. Multiple <em>vhost</em> objects may be
+created as needed.</p></div>
+<div class="sect4">
+<h5 id="_global_policy">Global Policy</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="35%" />
+<col width="15%" />
+<col width="50%" />
+<thead>
+<tr>
+<th align="left" valign="top"> attribute </th>
+<th align="left" valign="top"> default </th>
+<th align="left" valign="top"> description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnections</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Global maximum number of concurrent client connections allowed. This limit is always enforced even if no other policy settings have been defined. This limit is applied to all incoming connections regardless of remote host, authenticated user, or targeted vhost.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">enableVhostPolicy</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">Enable vhost policy connection denial, and resource limit enforcement.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">policyDir</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">Absolute path to a directory that holds vhost definition .json files. All vhost definitions in all .json files in this directory are processed.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">defaultVhost</p></td>
+<td align="left" valign="top"><p class="table">"$default"</p></td>
+<td align="left" valign="top"><p class="table">Vhost rule set name to use for connections with a vhost that is otherwise not defined. Default vhost processing may be disabled either by erasing the definition of <em>defaultVhost</em> or by not defining a <em>vhost</em> object named <em>$default</em>.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_vhost_policy_2">Vhost Policy</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="35%" />
+<col width="15%" />
+<col width="50%" />
+<thead>
+<tr>
+<th align="left" valign="top"> attribute </th>
+<th align="left" valign="top"> default </th>
+<th align="left" valign="top"> description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">id</p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table">Vhost name must be unique.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnections</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of concurrent client connections allowed.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnectionsPerUser</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of concurrent client connections allowed for any user.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnectionsPerRemoteHost</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of concurrent client connections allowed for any remote host.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowUnknownUser</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">Allow unknown users who are not members of a defined user group. Unknown users are assigned to the <em>$default</em> user group and receive <em>$default</em> settings.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">groups</p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table">A map where each key is a user group name and the value is a Vhost User Group Settings map.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_vhost_user_group_settings_map">Vhost User Group Settings Map</h5>
+<div class="paragraph"><p>This object is the data value contained in entries in the policy/groups map.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="35%" />
+<col width="15%" />
+<col width="50%" />
+<thead>
+<tr>
+<th align="left" valign="top"> Section/Attribute </th>
+<th align="left" valign="top"> default </th>
+<th align="left" valign="top"> description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>Group Membership</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">users</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of authenticated users in this group.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>Connection Restrictions</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">remoteHosts</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of remote hosts from which the users may connect. List values may be host names, numeric IP addresses, numeric IP address ranges, or the wildcard <em>*</em>. An empty list denies all access.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>AMQP Connection Open Limits</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxFrameSize</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Largest frame that may be sent on this connection. (AMQP Open, max-frame-size)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxSessions</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of sessions that may be created on this connection. (AMQP Open, channel-max)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>AMQP Session Begin Limits</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxSessionWindow</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Incoming capacity for new sessions. (AMQP Begin, incoming-window)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>AMQP Link Attach</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxMessageSize</p></td>
+<td align="left" valign="top"><p class="table">0</p></td>
+<td align="left" valign="top"><p class="table">Largest message size supported by links created on this connection. If this field is zero there is no maximum size imposed by the link endpoint. (AMQP Attach, max-message-size)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxSenders</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of sending links that may be created on this connection.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxReceivers</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of receiving links that may be created on this connection.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowDynamicSource</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">This connection is allowed to create receiving links using the Dynamic Link Source feature.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowAnonymousSender</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">This connection is allowed to create sending links using the Anonymous Sender feature.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowUserIdProxy</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">This connection is allowed to send messages with a user_id property that differs from the connection’s authenticated user id.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">sources</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of Source addresses allowed when creating receiving links. This list may be expressed as a CSV string or as a list of strings. An empty list denies all access.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">targets</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of Target addresses allowed when creating sending links. This list may be expressed as a CSV string or as a list of strings. An empty list denies all access.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_policy_wildcard_and_user_name_substitution">2.6.4. Policy Wildcard and User Name Substitution</h4>
+<div class="paragraph"><p>Policy provides several conventions to make writing rules easier.</p></div>
+<div class="sect4">
+<h5 id="_remote_host_wildcard">Remote Host Wildcard</h5>
+<div class="paragraph"><p>Remote host rules may consist of a single asterisk character to
+specify all hosts.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> remoteHosts: *</code></pre>
+</div></div>
+<div class="paragraph"><p>The asterisk must stand alone and cannot be appended to a host name
+or to an IP address fragment.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_amqp_source_and_target_wildcard_and_name_substitution">AMQP Source and Target Wildcard and Name Substitution</h5>
+<div class="paragraph"><p>The rule definitions for <code>sources</code> and <code>targets</code> may include the username
+substitution token</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> {user}</code></pre>
+</div></div>
+<div class="paragraph"><p>or a trailing asterisk.</p></div>
+<div class="paragraph"><p>The username substitution token is replaced with the authenticated user name for
+the connection. Using this token, an administrator may allow access to
+some resources specific to each user without having to name each user
+individually. This token is substituted once for the leftmost
+occurrence in the link name.</p></div>
+<div class="paragraph"><p>The asterisk is recognized only if it is the last character in the
+link name.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> sources: tmp_{user}, temp*, {user}-home-*</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_composing_policies">2.6.5. Composing Policies</h4>
+<div class="paragraph"><p>This section shows policy examples designed to illustrate some common use cases.</p></div>
+<div class="sect4">
+<h5 id="_example_1_user_policy_disabled">Example 1. User Policy Disabled</h5>
+<div class="paragraph"><p>Policy is disabled when no policy configuation objects are defined.
+Any number of connections are allowed and all users have
+access to all AMQP resources in the network.</p></div>
+</div>
+<div class="sect4">
+<h5 id="example2">Example 2. All Users Have Simple Connection Limits</h5>
+<div class="paragraph"><p>This example shows how to keep users from overwhelming the router with
+connections. Any user can create up to ten connections and the router
+will limit the aggregated user connection count to 100 connections
+total. No other restrictions apply.</p></div>
+<div class="paragraph"><p>This example also shows how to use a default vhost policy effectively.
+Only one vhost policy is defined and all user connections regardless
+of the requested vhost use that policy.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>policy {
+ maxConnections: 100 <b><1></b>
+}
+
+vhost {
+ name: $default <b><2></b>
+ maxConnectionsPerUser: 10 <b><3></b>
+ allowUnknownUser: true <b><4></b>
+ groups: {
+ $default: {
+ remoteHosts: * <b><5></b>
+ sources: * <b><6></b>
+ targets: * <b><6></b>
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="colist arabic"><ol>
+<li>
+<p>
+The global maxConnections limit of 100 is enforced.
+</p>
+</li>
+<li>
+<p>
+No normal vhost names are defined; user is assigned to default vhost <em>$default</em>.
+</p>
+</li>
+<li>
+<p>
+The vhost maxConnectionsPerUser limit of 10 is enforced.
+</p>
+</li>
+<li>
+<p>
+No groups are defined to have any users but allowUnknownUser is true so all users are assigned to group $default.
+</p>
+</li>
+<li>
+<p>
+The user is allowed to connect from any remote host.
+</p>
+</li>
+<li>
+<p>
+The user is allowed to connect to any source or target in the AMQP network. Router system-wide values are used for the other AMQP settings that are unspecified in the vhost rules.
+</p>
+</li>
+</ol></div>
+</div>
+<div class="sect4">
+<h5 id="_example_3_admins_must_connect_from_localhost">Example 3. Admins Must Connect From Localhost</h5>
+<div class="paragraph"><p>This example shows how an admin group may be created and restricted
+to accessing a vhost only from localhost. The admin users are allowed
+to connect to any AMQP resources while normal users are restricted.</p></div>
+<div class="paragraph"><p>In this example a user connects to vhost <em>example.com</em>.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>vhost {
+ name: example.com <b><1></b>
+ allowUnknownUser: true <b><3></b>
+ groups: {
+ admin: {
+ users: alice, bob <b><2></b>
+ remoteHosts: 127.0.0.1, ::1 <b><4></b>
+ sources: * <b><5></b>
+ targets: * <b><5></b>
+ },
+ $default: {
+ remoteHosts: * <b><6></b>
+ sources: news*, sports*, chat* <b><7></b>
+ targets: chat* <b><7></b>
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="colist arabic"><ol>
+<li>
+<p>
+A connection to vhost <em>example.com</em> locates this vhost rule set.
+</p>
+</li>
+<li>
+<p>
+If one of users <em>alice</em> or <em>bob</em> is connecting then she or he is assigned to the <em>admin</em> user group.
+</p>
+</li>
+<li>
+<p>
+Any other user is not defined by a user group. However, since the <em>allowUnknownUser</em> setting is true then this user is assigned to the <em>$default</em> user group.
+</p>
+</li>
+<li>
+<p>
+Users in the <em>admin</em> user group must connect from localhost. Connections for an <em>admin</em> user from other hosts on the network are denied.
+</p>
+</li>
+<li>
+<p>
+Users in the <em>admin</em> user group are allowed to access any resource offered by the vhost service.
+</p>
+</li>
+<li>
+<p>
+Other users are allowed to connect from any host.
+</p>
+</li>
+<li>
+<p>
+Other users have source and target name lists that restrict the resources they are allowed to access.
+</p>
+</li>
+</ol></div>
+</div>
+<div class="sect4">
+<h5 id="_example_4_limiting_possible_memory_consumption">Example 4. Limiting Possible Memory Consumption</h5>
+<div class="paragraph"><p>Policy provides a mechanism to control how much system buffer memory a
+user connection can potentially consume. The formula for computing
+buffer memory consumption for each session is</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> potential buffer usage = maxFrameSize * maxSessionWindow</code></pre>
+</div></div>
+<div class="paragraph"><p>By adjusting <em>maxFrameSize</em>, <em>maxSessions</em>, and <em>maxSessionWindow</em> an
+administrator can prevent a user from consuming too much memory by
+buffering messages in flight.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+<div class="paragraph"><p>The settings passed into the AMQP protocol connection and session
+negotiations. Normal AMQP session flow control limits buffer
+consumption in due course with no processing cycles required by the
+router.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>In this example normal users, the traders, are given smaller buffer
+allocations while high-capacity, automated data feeds are given a
+higher buffer allocation. This example skips the details of settings
+unrelated to buffer allocation.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>vhost {
+ name: traders.com <b><1></b>
+ groups: {
+ traders: {
+ users: trader-1, trader-2, ... <b><2></b>
+ maxFrameSize: 10000 <b><3></b>
+ maxSessionWindow: 500 <b><3></b>
+ maxSessions: 1 <b><4></b>
+ ...
+ },
+ feeds: {
+ users: nyse-feed, nasdaq-feed <b><5></b>
+ maxFrameSize: 60000 <b><6></b>
+ maxSessionWindow: 20000 <b><6></b>
+ maxSessions: 3 <b><7></b>
+ ...
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="colist arabic"><ol>
+<li>
+<p>
+These rules are for vhost traders.com.
+</p>
+</li>
+<li>
+<p>
+The <em>traders</em> group includes trader-1, trader-2, and any other user defined in the list.
+</p>
+</li>
+<li>
+<p>
+<em>maxFrameSize</em> and <em>maxSessionWindow</em> allow for at most 5,000,000 bytes of data to be in flight on each session.
+</p>
+</li>
+<li>
+<p>
+Only one session per connection is allowed.
+</p>
+</li>
+<li>
+<p>
+In the <em>feeds</em> group two users are defined.
+</p>
+</li>
+<li>
+<p>
+<em>maxFrameSize</em> and <em>maxSessionWindow</em> allow for at most 1,200,000,000 bytes of data to be in flight on each session.
+</p>
+</li>
+<li>
+<p>
+Up to three sessions per connection are allowed.
+</p>
+</li>
+</ol></div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="technical-details-and-specifications">3. Technical Details and Specifications</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="client-compatibility">3.1. Client Compatibility</h3>
+<div class="paragraph"><p>Dispatch Router should, in theory, work with any client that is
+compatible with AMQP 1.0. The following clients have been tested:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="22%" />
+<col width="78%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Client</em> </th>
+<th align="left" valign="top"><em>Notes</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">qpid::messaging</p></td>
+<td align="left" valign="top"><p class="table">The Qpid messaging clients work with Dispatch Router
+as long as they are configured to use the 1.0 version of the protocol.
+To enable AMQP 1.0 in the C++ client, use the {protocol:amqp1.0}
+connection option.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Proton Reactor</p></td>
+<td align="left" valign="top"><p class="table">The Proton Reactor API is compatible with Dispatch
+Router.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Proton Messenger</p></td>
+<td align="left" valign="top"><p class="table">Messenger works with Dispatch Router.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="addressing">3.2. Addressing</h3>
+<div class="paragraph"><p>AMQP addresses are used to control the flow of messages across a network
+of routers. Addresses are used in a number of different places in the
+AMQP 1.0 protocol. They can be used in a specific message in the <code>to</code>
+and <code>reply-to</code> fields of a message’s properties. They are also used
+during the creation of links in the <code>address</code> field of a <code>source</code> or
+a <code>target</code>.</p></div>
+<div class="paragraph"><p>Addresses designate various kinds of entities in a messaging network:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Endpoint processes that consume data or offer a service
+</p>
+</li>
+<li>
+<p>
+Topics that match multiple consumers to multiple producers
+</p>
+</li>
+<li>
+<p>
+Entities within a messaging broker:
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Queues
+</p>
+</li>
+<li>
+<p>
+Durable Topics
+</p>
+</li>
+<li>
+<p>
+Exchanges
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+<div class="paragraph"><p>The syntax of an AMQP address is opaque as far as the router network is
+concerned. A syntactical structure may be used by the administrator that
+creates addresses, but the router treats them as opaque strings. Routers
+consider addresses to be mobile such that any address may be directly
+connected to any router in a network and may move around the topology.
+In cases where messages are broadcast to or balanced across multiple
+consumers, an address may be connected to multiple routers in the
+network.</p></div>
+<div class="paragraph"><p>Addresses have semantics associated with them. When an address is
+created in the network, it is assigned a set of semantics (and access
+rules) during a process called provisioning. The semantics of an address
+control how routers behave when they see the address being used.</p></div>
+<div class="paragraph"><p>Address semantics include the following considerations:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Routing pattern</em> - direct, multicast, balanced
+</p>
+</li>
+<li>
+<p>
+<em>Undeliverable action</em> - drop, hold and retry, redirect
+</p>
+</li>
+<li>
+<p>
+<em>Reliability</em> - N destinations, etc.
+</p>
+</li>
+</ul></div>
+<div class="sect3">
+<h4 id="routing-patterns">3.2.1. Routing patterns</h4>
+<div class="paragraph"><p>Routing patterns constrain the paths that a message can take across a
+network.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="18%" />
+<col width="82%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Pattern</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><em>Direct</em></p></td>
+<td align="left" valign="top"><p class="table">Direct routing allows for only one consumer to use an address
+at a time. Messages (or links) follow the lowest cost path across the
+network from the sender to the one receiver.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><em>Multicast</em></p></td>
+<td align="left" valign="top"><p class="table">Multicast routing allows multiple consumers to use the
+same address at the same time. Messages are routed such that each
+consumer receives a copy of the message.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><em>Balanced</em></p></td>
+<td align="left" valign="top"><p class="table">Balanced routing also allows multiple consumers to use the
+same address. In this case, messages are routed to exactly one of the
+consumers, and the network attempts to balance the traffic load across
+the set of consumers using the same address.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="routing-mechanisms">3.2.2. Routing mechanisms</h4>
+<div class="paragraph"><p>The fact that addresses can be used in different ways suggests that
+message routing can be accomplished in different ways. Before going into
+the specifics of the different routing mechanisms, it would be good to
+first define what is meant by the term <em>routing</em>:</p></div>
+<div class="quoteblock">
+<div class="content">
+<div class="paragraph"><p>In a network built of multiple routers connected by connections (i.e.,
+nodes and edges in a graph), <em>routing</em> determines which connection to
+use to send a message directly to its destination or one step closer to
+its destination.</p></div>
+</div>
+<div class="attribution">
+</div></div>
+<div class="paragraph"><p>Each router serves as the terminus of a collection of incoming and
+outgoing links. The links either connect directly to endpoints that
+produce and consume messages, or they connect to other routers in the
+network along previously established connections.</p></div>
+<div class="sect4">
+<h5 id="message-routing">Message routing</h5>
+<div class="paragraph"><p>Message routing occurs upon delivery of a message and is done based on
+the address in the message’s <code>to</code> field.</p></div>
+<div class="paragraph"><p>When a delivery arrives on an incoming link, the router extracts the
+address from the delivered message’s <code>to</code> field and looks the address up
+in its routing table. The lookup results in zero or more outgoing links
+onto which the message shall be resent.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="20%" />
+<col width="80%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Delivery</em> </th>
+<th align="left" valign="top"><em>Handling</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><em>pre-settled</em></p></td>
+<td align="left" valign="top"><p class="table">If the arriving delivery is pre-settled (i.e., fire and
+forget), the incoming delivery shall be settled by the router, and the
+outgoing deliveries shall also be pre-settled. In other words, the
+pre-settled nature of the message delivery is propagated across the
+network to the message’s destination.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><em>unsettled</em></p></td>
+<td align="left" valign="top"><p class="table">Unsettled delivery is also propagated across the network.
+Because unsettled delivery records cannot be discarded, the router
+tracks the incoming deliveries and keeps the association of the incoming
+deliveries to the resulting outgoing deliveries. This kept association
+allows the router to continue to propagate changes in delivery state
+(settlement and disposition) back and forth along the path which the
+message traveled.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="amqp-mapping">3.3. AMQP Mapping</h3>
+<div class="paragraph"><p>Dispatch Router is an AMQP router and as such, it provides extensions,
+code-points, and semantics for routing over AMQP. This page documents the
+details of Dispatch Router’s use of AMQP.</p></div>
+<div class="sect3">
+<h4 id="message-annotations">3.3.1. Message Annotations</h4>
+<div class="paragraph"><p>The following Message Annotation fields are defined by Dispatch Router:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="23%" />
+<col width="19%" />
+<col width="58%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Field</em> </th>
+<th align="left" valign="top"><em>Type</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.ingress</p></td>
+<td align="left" valign="top"><p class="table">string</p></td>
+<td align="left" valign="top"><p class="table">The identity of the ingress router for a
+message-routed message. The ingress router is the first router
+encountered by a transiting message. The router will, if this field is
+present, leave it unaltered. If the field is not present, the router
+shall insert the field with its own identity.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.trace</p></td>
+<td align="left" valign="top"><p class="table">list of string</p></td>
+<td align="left" valign="top"><p class="table">The list of routers through which this
+message-routed message has transited. If this field is not present, the
+router shall do nothing. If the field is present, the router shall
+append its own identity to the end of the list.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.to</p></td>
+<td align="left" valign="top"><p class="table">string</p></td>
+<td align="left" valign="top"><p class="table">To-Override for message-routed messages. If this
+field is present, the address in this field shall be used for routing in
+lieu of the <em>to</em> field in the message properties. A router may append,
+remove, or modify this annotation field depending on the policy in place
+for routing the message.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.phase</p></td>
+<td align="left" valign="top"><p class="table">integer</p></td>
+<td align="left" valign="top"><p class="table">The address-phase, if not zero, for messages
+flowing between routers.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="sourcetarget-capabilities">3.3.2. Source/Target Capabilities</h4>
+<div class="paragraph"><p>The following Capability values are used in Sources and Targets.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="19%" />
+<col width="81%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Capability</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">qd.router</p></td>
+<td align="left" valign="top"><p class="table">This capability is added to sources and targets that are
+used for inter-router message exchange. This capability denotes a link
+used for router-control messages flowing between routers.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">qd.router-data</p></td>
+<td align="left" valign="top"><p class="table">This capability is added to sources and targets that
+are used for inter-router message exchange. This capability denotes a
+link used for user messages being message-routed across an inter-router
+connection.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="dynamic-node-properties">3.3.3. Dynamic-Node-Properties</h4>
+<div class="paragraph"><p>The following dynamic-node-properties are used by Dispatch in Sources.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="23%" />
+<col width="77%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Property</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.address</p></td>
+<td align="left" valign="top"><p class="table">The node address describing the destination desired
+for a dynamic source. If this is absent, the router will terminate any
+dynamic receivers. If this address is present, the router will use the
+address to route the dynamic link attach to the proper destination
+container.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="addresses-and-address-formats">3.3.4. Addresses and Address Formats</h4>
+<div class="paragraph"><p>The following AMQP addresses and address patterns are used within
+Dispatch Router.</p></div>
+<div class="sect4">
+<h5 id="address-patterns">Address Patterns</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="38%" />
+<col width="62%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Pattern</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_local/<addr></code></p></td>
+<td align="left" valign="top"><p class="table">An address that references a locally attached endpoint.
+Messages using this address pattern shall not be routed over more than
+one link.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_topo/0/<router>/<addr></code></p></td>
+<td align="left" valign="top"><p class="table">An address that references an endpoint attached to a specific router
+node in the network topology. Messages with addresses that follow this
+pattern shall be routed along the shortest path to the specified router.
+Note that addresses of this form are a-priori routable in that the
+address itself contains enough information to route the message to its
+destination.</p>
+<p class="table">The <em>0</em> component immediately preceding the router-id is a placeholder
+for an <em>area</em> which may be used in the future if area routing is
+implemented.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code><addr></code></p></td>
+<td align="left" valign="top"><p class="table">A mobile address. An address of this format represents an
+endpoint or a set of distinct endpoints that are attached to the network
+in arbitrary locations. It is the responsibility of the router network
+to determine which router nodes are valid destinations for mobile
+addresses.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="supported-addresses">Supported Addresses</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="36%" />
+<col width="64%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Address</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><code>$management</code></p></td>
+<td align="left" valign="top"><p class="table">The management agent on the attached router/container.
+This address would be used by an endpoint that is a management
+client/console/tool wishing to access management data from the attached
+container.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/$management</code></p></td>
+<td align="left" valign="top"><p class="table">The management agent at Router.E in area
+0. This address would be used by a management client wishing to access
+management data from a specific container that is reachable within the
+network.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_local/qdhello</code></p></td>
+<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+This address is used to communicate with neighbor routers and is
+exclusively for the HELLO discovery protocol.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_local/qdrouter</code></p></td>
+<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+This address is used by a router to communicate with other routers in
+the network.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/qdrouter</code></p></td>
+<td align="left" valign="top"><p class="table">The router entity at the specifically
+indicated router. This address form is used by a router to communicate
+with a specific router that may or may not be a neighbor.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</h4>
+<div class="paragraph"><p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
+emerging AMQP Management specification (draft 9).</p></div>
+<div class="paragraph"><p>Differences from the specification:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+The <code>name</code> attribute is not required when an entity is created. If
+ not supplied it will be set to the same value as the system-generated
+ "identity" attribute. Otherwise it is treated as per the standard.
+</p>
+</li>
+<li>
+<p>
+The <code>REGISTER</code> and <code>DEREGISTER</code> operations are not implemented. The router
+ automatically discovers peer routers via the router network and makes
+ their management addresses available via the standard <code>GET-MGMT-NODES</code>
+ operation.
+= Management Schema
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>This chapter documents the set of <strong>management entity types</strong> that define
+configuration and management of a Dispatch Router. A management entity type has
+a set of <strong>attributes</strong> that can be read, some attributes can also be
+updated. Some entity types also support <strong>operations</strong> that can be called.</p></div>
+<div class="paragraph"><p>All management entity types have the following standard attributes:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+type
+</dt>
+<dd>
+<p>
+ The fully qualified type of the entity,
+ e.g. <code>org.apache.qpid.dispatch.router</code>. This document uses the short name
+ without the <code>org.apache.qpid.dispatch</code> prefix e.g. <code>router</code>. The dispatch
+ tools will accept the short or long name.
+</p>
+</dd>
+<dt class="hdlist1">
+name
+</dt>
+<dd>
+<p>
+ A user-generated identity for the entity. This can be used in other entities
+ that need to refer to the named entity.
+</p>
+</dd>
+<dt class="hdlist1">
+identity
+</dt>
+<dd>
+<p>
+ A system-generated identity of the entity. It includes
+ the short type name and some identifying information. E.g. <code>log/AGENT</code> or
+ <code>listener/localhost:amqp</code>
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>There are two main categories of management entity type.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+Configuration Entities
+</dt>
+<dd>
+<p>
+ Parameters that can be set in the configuration file
+ (see <code>qdrouterd.conf(5)</code> man page) or set at run-time with the <code>qdmanage(8)</code>
+ tool.
+</p>
+</dd>
+<dt class="hdlist1">
+Operational Entities
+</dt>
+<dd>
+<p>
+ Run-time status values that can be queried using <code>qdstat(8)</code> or <code>qdmanage(8)</code> tools.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuration_entities">3.4. Configuration Entities</h3>
+<div class="paragraph"><p>Configuration entities define the attributes allowed in the configuration file
+(see <code>qdrouterd.conf(5)</code>) but you can also create entities once the router is
+running using the <code>qdrouterd(8)</code> tool’s <code>create</code> operation. Some entities can also
+be modified using the <code>update</code> operation, see the entity descriptions below.</p></div>
+<div class="sect3">
+<h4 id="_router">3.4.1. router</h4>
+<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
+<div class="paragraph"><p>Operations allowed: <code>READ</code></p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>id</em> (string, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>area</em> (string)
+</dt>
+<dd>
+<p>
+ Unused placeholder.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloInterval</em> (integer, default=1, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Interval in seconds between HELLO messages sent to neighbor routers.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloMaxAge</em> (integer, default=3, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Time in seconds after which a neighbor is declared lost if no HELLO is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raInterval</em> (integer, default=30, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers in a stable network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raIntervalFlux</em> (integer, default=4, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>remoteLsMaxAge</em> (integer, default=60, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Time in seconds after which link state is declared stale if no RA is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>addrCount</em> (integer)
+</dt>
+<dd>
+<p>
+ Number of addresses known to the router.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>linkCount</em> (integer)
+</dt>
+<dd>
+<p>
+ Number of links attached to the router node.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>nodeCount</em> (integer)
+</dt>
+<dd>
+<p>
+ Number of known peer router nodes.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>workerThreads</em> (integer, default=4, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
+</p>
+</dd>
+<dt class="hdlist1">
+<em>debugDump</em> (path, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ A file to dump debugging information that can’t be logged normally.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigPath</em> (path, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Absolute path to the SASL configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigName</em> (string, default=<em>qdrouterd</em>, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>routerId</em> (string, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mobileAddrMaxAge</em> (integer, default=60, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This value is no longer used in the router.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect3">
+<h4 id="_sslprofile">3.4.2. sslProfile</h4>
+<div class="paragraph"><p>Attributes for setting TLS/SSL configuration for connections.</p></div>
+<div class="paragraph"><p>Operations allowed: <code>CREATE</code>, <code>DELETE</code>, <code>READ</code></p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>certDb</em> (path, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>certFile</em> (path, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>keyFile</em> (path, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the PEM-formatted private key for the above certificate.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>passwordFile</em> (path, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>password</em> (string, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>uidFormat</em> (string, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>displayNameFile</em> (string, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the unique id to dispay name mapping
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect3">
+<h4 id="_listener">3.4.3. listener</h4>
+<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
+<div class="paragraph"><p>Operations allowed: <code>CREATE</code>, <code>DELETE</code>, <code>READ</code></p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>host</em> (string, default=<em>127.0.0.1</em>, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ IP address: ipv4 or ipv6 literal or a host name
+</p>
+</dd>
+<dt class="hdlist1">
+<em>port</em> (string, default=<em>amqp</em>, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Port number or symbolic service name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>protocolFamily</em> (One
<TRUNCATED>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/book/console1.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/book/console1.png b/input/releases/qpid-dispatch-0.7.0/book/console1.png
new file mode 100644
index 0000000..f131884
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/book/console1.png differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[5/6] qpid-site git commit: NO-JIRA - Updating documentation for Qpid
Dispatch Router version 0.7.0
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/book.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/book.html b/content/releases/qpid-dispatch-0.7.0/book/book.html
new file mode 100644
index 0000000..e4a108d
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/book/book.html
@@ -0,0 +1,4304 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>1. Introduction - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.7.0/index.html">Qpid Dispatch 0.7.0</a></li><li>1. Introduction</li></ul>
+
+ <div id="-middle-content">
+ <div class="sect1">
+<h2 id="introduction">1. Introduction</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="overview">1.1. Overview</h3>
+<div class="paragraph"><p>The Dispatch router is an AMQP message router that provides
+advanced interconnect capabilities. It allows flexible routing of
+messages between any AMQP-enabled endpoints, whether they be clients,
+servers, brokers or any other entity that can send or receive standard
+AMQP messages.</p></div>
+<div class="paragraph"><p>A messaging client can make a single AMQP connection into a messaging
+bus built of Dispatch routers and, over that connection, exchange
+messages with one or more message brokers, and at the same time exchange
+messages directly with other endpoints without involving a broker at
+all.</p></div>
+<div class="paragraph"><p>The router is an intermediary for messages but it is <em>not</em> a broker. It
+does not <em>take responsibility for</em> messages. It will, however, propagate
+settlement and disposition across a network such that delivery
+guarantees are met. In other words: the router network will deliver the
+message, possibly via several intermediate routers, <em>and</em> it will route
+the acknowledgement of that message by the ultimate receiver back across
+the same path. This means that <em>responsibility</em> for the message is
+transfered from the original sender to the ultimate receiver <em>as if
+they were directly connected</em>. However this is done via a flexible
+network that allows highly configurable routing of the message
+transparent to both sender and receiver.</p></div>
+<div class="paragraph"><p>There are some patterns where this enables "brokerless messaging"
+approaches that are preferable to brokered approaches. In other cases a
+broker is essential (in particular where you need the separation of
+responsibility and/or the buffering provided by store-and-forward) but a
+dispatch network can still be useful to tie brokers and clients together
+into patterns that are difficult with a single broker.</p></div>
+<div class="paragraph"><p>For a "brokerless" example, consider the common brokered implementation
+of the request-response pattern, a client puts a request on a queue and
+then waits for a reply on another queue. In this case the broker can be
+a hindrance - the client may want to know immediatly if there is nobody
+to serve the request, but typically it can only wait for a timeout to
+discover this. With a dispatch network, the client can be informed
+immediately if its message cannot be delivered because nobody is
+listening. When the client receives acknowledgement of the request it
+knows not just that it is sitting on a queue, but that it has actually
+been received by the server.</p></div>
+<div class="paragraph"><p>For an exampe of using dispatch to enhance the use of brokers, consider
+using an array of brokers to implement a scalable distributed work
+queue. A dispatch network can make this appear as a single queue, with
+senders publishing to a single address and receivers subscribing to a
+single address. The dispatch network can distribute work to any broker
+in the array and collect work from any broker for any receiver. Brokers
+can be shut down or added without affecting clients. This elegantly
+solves the common difficulty of "stuck messages" when implementing this
+pattern with brokers alone. If a receiver is connected to a broker that
+has no messages, but there are messages on another broker, you have to
+somehow transfer them or leave them "stuck". With a dispatch network,
+<em>all</em> the receivers are connected to <em>all</em> the brokers. If there is a
+message anywhere it can be delivered to any receiver.</p></div>
+<div class="paragraph"><p>The router is meant to be deployed in topologies of multiple routers,
+preferably with redundant paths. It uses link-state routing protocols
+and algorithms (similar to OSPF or IS-IS from the networking world) to
+calculate the best path from every point to every other point and to
+recover quickly from failures. It does not need to use clustering for
+high availability; rather, it relies on redundant paths to provide
+continued connectivity in the face of system or network failure. Because
+it never takes responsibility for messages it is effectively stateless.
+Messages not delivered to their final destination will not be
+acknowledged to the sender and therefore the sender can re-send such
+messages if it is disconnected from the network.</p></div>
+</div>
+<div class="sect2">
+<h3 id="benefits">1.2. Benefits</h3>
+<div class="paragraph"><p>Simplifies connectivity</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+An endpoint can do all of its messaging through a single transport
+connection
+</p>
+</li>
+<li>
+<p>
+Avoid opening holes in firewalls for incoming connections
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Provides messaging connectivity where there is no TCP/IP connectivity</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+A server or broker can be in a private IP network (behind a NAT
+firewall) and be accessible by messaging endpoints in other networks
+(learn more).
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Simplifies reliability</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Reliability and availability are provided using redundant topology,
+not server clustering
+</p>
+</li>
+<li>
+<p>
+Reliable end-to-end messaging without persistent stores
+</p>
+</li>
+<li>
+<p>
+Use a message broker only when you need store-and-forward semantics
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="features">1.3. Features</h3>
+<div class="ulist"><ul>
+<li>
+<p>
+Can be deployed stand-alone or in a network of routers
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Supports arbitrary network topology - no restrictions on redundancy
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Automatic route computation - adjusts quickly to changes in topology
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+Provides remote access to brokers or other AMQP servers
+</p>
+</li>
+<li>
+<p>
+Security
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="using-qpid-dispatch">2. Using Qpid Dispatch</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="configuration">2.1. Configuration</h3>
+<div class="paragraph"><p>The default configuration file is installed in
+<em>/usr/local/etc/qpid-dispatch/qdrouterd.conf</em>. This configuration file will
+cause the router to run in standalone mode, listening on the standard
+AMQP port (5672). Dispatch Router looks for the configuration file in
+the installed location by default. If you wish to use a different path,
+the "-c" command line option will instruct Dispatch Router as to which
+configuration to load.</p></div>
+<div class="paragraph"><p>To run the router, invoke the executable: <code>qdrouterd [-c my-config-file]</code></p></div>
+<div class="paragraph"><p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
+page.</p></div>
+</div>
+<div class="sect2">
+<h3 id="tools">2.2. Tools</h3>
+<div class="sect3">
+<h4 id="qdstat">2.2.1. qdstat</h4>
+<div class="paragraph"><p><em>qdstat</em> is a command line tool that lets you view the status of a
+Dispatch Router. The following options are useful for seeing what the
+router is doing:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="17%" />
+<col width="83%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Option</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">-l</p></td>
+<td align="left" valign="top"><p class="table">Print a list of AMQP links attached to the router. Links are
+unidirectional. Outgoing links are usually associated with a
+subscription address. The tool distinguishes between <em>endpoint</em> links
+and <em>router</em> links. Endpoint links are attached to clients using the
+router. Router links are attached to other routers in a network of
+routbers.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">-a</p></td>
+<td align="left" valign="top"><p class="table">Print a list of addresses known to the router.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">-n</p></td>
+<td align="left" valign="top"><p class="table">Print a list of known routers in the network.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">-c</p></td>
+<td align="left" valign="top"><p class="table">Print a list of connections to the router.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">--autolinks</p></td>
+<td align="left" valign="top"><p class="table">Print a list of configured auto-links.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">--linkroutes</p></td>
+<td align="left" valign="top"><p class="table">Print a list of configures link-routes.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="paragraph"><p>For complete details see the <em>qdstat(8)</em> man page and the output of
+<code>qdstat --help</code>.</p></div>
+</div>
+<div class="sect3">
+<h4 id="qdmanage">2.2.2. qdmanage</h4>
+<div class="paragraph"><p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
+to not only view but modify the configuration of a running dispatch
+router.</p></div>
+<div class="paragraph"><p>For example you can query all the connection entities in the router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage query --type connection</code></pre>
+</div></div>
+<div class="paragraph"><p>To enable logging debug and higher level messages by default:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage update log/DEFAULT enable=debug+</code></pre>
+</div></div>
+<div class="paragraph"><p>In fact, everything that can be configured in the configuration file can
+also be created in a running router via management. For example to
+create a new listener in a running router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage create type=listener port=5555</code></pre>
+</div></div>
+<div class="paragraph"><p>Now you can connect to port 5555, for exampple:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdmanage query -b localhost:5555 --type listener</code></pre>
+</div></div>
+<div class="paragraph"><p>For complete details see the <em>qdmanage(8)</em> man page and the output of
+<code>qdmanage --help</code>. Also for details of what can be configured see the
+<em>qdrouterd.conf(5)</em> man page.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="basic-usage-and-examples">2.3. Basic Usage and Examples</h3>
+<div class="sect3">
+<h4 id="standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</h4>
+<div class="paragraph"><p>The router can operate stand-alone or as a node in a network of routers.
+The mode is configured in the <em>router</em> section of the configuration
+file. In stand-alone mode, the router does not attempt to collaborate
+with any other routers and only routes messages among directly connected
+endpoints.</p></div>
+<div class="paragraph"><p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
+like the following:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ===============================================================================================================
+ local $_management_internal closest 1 0 0 0 0 0 0 0 0
+ local $displayname closest 1 0 0 0 0 0 0 0 0
+ mobile $management 0 closest 1 0 0 0 1 0 0 1 0
+ local $management closest 1 0 0 0 0 0 0 0 0
+ local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>Note that there are a number of known addresses. <em>$management</em> is the
+address of the router’s embedded management agent.
+<em>temp.1GThUllfR7N+BDP</em> is the temporary reply-to address of the <em>qdstat</em>
+client making requests to the agent.</p></div>
+<div class="paragraph"><p>If you change the mode to interior and restart the processs, the same
+command will yield additional addresses which are used for inter-router
+communication:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ =================================================================================================================
+ local $_management_internal closest 1 0 0 0 0 0 0 0 0
+ local $displayname closest 1 0 0 0 0 0 0 0 0
+ mobile $management 0 closest 1 0 0 0 1 0 0 1 0
+ local $management closest 1 0 0 0 0 0 0 0 0
+ local qdhello flood 1 0 0 0 0 0 0 0 10
+ local qdrouter flood 1 0 0 0 0 0 0 0 0
+ topo qdrouter flood 1 0 0 0 0 0 0 0 1
+ local qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
+ topo qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
+ local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0</code></pre>
+</div></div>
+</div>
+<div class="sect3">
+<h4 id="mobile-subscribers">2.3.2. Mobile Subscribers</h4>
+<div class="paragraph"><p>The term "mobile subscriber" simply refers to the fact that a client may
+connect to the router and subscribe to an address to receive messages
+sent to that address. No matter where in the network the subscriber
+attaches, the messages will be routed to the appropriate destination.</p></div>
+<div class="paragraph"><p>To illustrate a subscription on a stand-alone router, you can use the
+examples that are provided with Qpid Proton. Using the <em>simple_recv.py</em>
+example receiver:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python ./simple_recv.py -a 127.0.0.1/my-address</code></pre>
+</div></div>
+<div class="paragraph"><p>This command creates a receiving link subscribed to the specified
+address. To verify the subscription:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ===============================================================================================================
+ local $_management_internal closest 1 0 0 0 0 0 0 0 0
+ local $displayname closest 1 0 0 0 0 0 0 0 0
+ mobile $management 0 closest 1 0 0 0 2 0 0 2 0
+ local $management closest 1 0 0 0 0 0 0 0 0
+ mobile my-address 0 closest 0 1 0 0 0 0 0 0 0
+ local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>You can then, in a separate command window, run a sender to produce
+messages to that address:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python ./simple_send.py -a 127.0.0.1/my-address</code></pre>
+</div></div>
+</div>
+<div class="sect3">
+<h4 id="dynamic-reply-to">2.3.3. Dynamic Reply-To</h4>
+<div class="paragraph"><p>Dynamic reply-to can be used to obtain a reply-to address that routes
+back to a client’s receiving link regardless of how many hops it has to
+take to get there. To illustrate this feature, see below a simple
+program (written in C++ against the qpid::messaging API) that queries
+the management agent of the attached router for a list of other known
+routers' management addresses.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>#include <qpid/messaging/Address.h>
+#include <qpid/messaging/Connection.h>
+#include <qpid/messaging/Message.h>
+#include <qpid/messaging/Receiver.h>
+#include <qpid/messaging/Sender.h>
+#include <qpid/messaging/Session.h>
+
+using namespace qpid::messaging;
+using namespace qpid::types;
+
+using std::stringstream;
+using std::string;
+
+int main() {
+ const char* url = "amqp:tcp:127.0.0.1:5672";
+ std::string connectionOptions = "{protocol:amqp1.0}";
+
+ Connection connection(url, connectionOptions);
+ connection.open();
+ Session session = connection.createSession();
+ Sender sender = session.createSender("mgmt");
+
+ // create reply receiver and get the reply-to address
+ Receiver receiver = session.createReceiver("#");
+ Address responseAddress = receiver.getAddress();
+
+ Message request;
+ request.setReplyTo(responseAddress);
+ request.setProperty("x-amqp-to", "amqp:/_local/$management");
+ request.setProperty("operation", "DISCOVER-MGMT-NODES");
+ request.setProperty("type", "org.amqp.management");
+ request.setProperty("name, "self");
+
+ sender.send(request);
+ Message response = receiver.fetch();
+ Variant content(response.getContentObject());
+ std::cout << "Response: " << content << std::endl << std::endl;
+
+ connection.close();
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The equivalent program written in Python against the Proton Messenger
+API:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>from proton import Messenger, Message
+
+def main():
+ host = "0.0.0.0:5672"
+
+ messenger = Messenger()
+ messenger.start()
+ messenger.route("amqp:/*", "amqp://%s/$1" % host)
+ reply_subscription = messenger.subscribe("amqp:/#")
+ reply_address = reply_subscription.address
+
+ request = Message()
+ response = Message()
+
+ request.address = "amqp:/_local/$management"
+ request.reply_to = reply_address
+ request.properties = {u'operation' : u'DISCOVER-MGMT-NODES',
+ u'type' : u'org.amqp.management',
+ u'name' : u'self'}
+
+ messenger.put(request)
+ messenger.send()
+ messenger.recv()
+ messenger.get(response)
+
+ print "Response: %r" % response.body
+
+ messenger.stop()
+
+main()</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="link-routing">2.4. Link Routing</h3>
+<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.4. This feature was
+significantly updated in Qpid Dispatch 0.6.</p></div>
+<div class="paragraph"><p>Link-routing is an alternative strategy for routing messages across a
+network of routers. With the existing message-routing strategy, each
+router makes a routing decision on a per-message basis when the message
+is delivered. Link-routing is different because it makes routing
+decisions when link-attach frames arrive. A link is effectively chained
+across the network of routers from the establishing node to the
+destination node. Once the link is established, the transfer of message
+deliveries, flow frames, and dispositions is performed across the routed
+link.</p></div>
+<div class="paragraph"><p>The main benefit to link-routing is that endpoints can use the full link
+protocol to interact with other endpoints in far-flung parts of the
+network. For example, a client can establish a receiver across the
+network to a queue on a remote broker and use link credit to control
+the flow of messages from the broker. Similarly, a receiver can
+establish a link to a topic on a remote broker using a server-side
+filter.</p></div>
+<div class="paragraph"><p>Why would one want to do this? One reason is to provide client
+isolation. A network like the following can be deployed:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> Public Network
+ +-----------------+
+ | +-----+ |
+ | B1 | Rp | |
+ | +/--\-+ |
+ | / \ |
+ | / \ |
+ +----/--------\---+
+ / \
+ / \
+ / \
+ Private Net A / \ Private Net B
+ +--------------/--+ +---\-------------+
+ | +---/-+ | | +--\--+ |
+ | B2 | Ra | | | | Rb | C1 |
+ | +-----+ | | +-----+ |
+ | | | |
+ | | | |
+ +-----------------+ +-----------------+</code></pre>
+</div></div>
+<div class="paragraph"><p>The clients in Private Net B can be constrained (by firewall policy)
+to only connect to the Router in their own network. Using
+link-routing, these clients can access queues, topics, and other AMQP
+services that are in the Public Network or even in Private Net A.</p></div>
+<div class="paragraph"><p>For example, The router Ra can be configured to expose queues in
+broker B2 to the network. Client C1 can then establish a connection
+to Rb, the local router, open a subscribing link to "b2.event-queue",
+and receive messages stored on that queue in broker B2.</p></div>
+<div class="paragraph"><p>C1 is unable to create a TCP/IP connection to B1 because of its
+isolation (and because B2 is itself in a private network). However, with
+link routing, C1 can interact with B2 using the AMQP link protocol.</p></div>
+<div class="paragraph"><p>Note that in this case, neither C1 nor B2 have been modified in any way
+and neither need be aware of the fact that there is a message-router
+network between them.</p></div>
+<div class="sect3">
+<h4 id="link-routing-configuration">2.4.1. Configuration</h4>
+<div class="paragraph"><p>Starting with the configured topology shown above, how is link-routing
+configured to support the example described above?</p></div>
+<div class="paragraph"><p>First, router Ra needs to be told how to make a connection to the broker
+B2:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ name: broker
+ role: route-container
+ host: <B2-url>
+ port: <B2-port>
+ saslMechanisms: ANONYMOUS
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>This <em>route-container</em> connector tells the router how to connect to an
+external AMQP container when it is needed. The name "broker" will be
+used later to refer to this connection.</p></div>
+<div class="paragraph"><p>Now, the router must be configured to route certain addresses to B2:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>linkRoute {
+ prefix: b2
+ dir: in
+ connection: broker
+}
+
+linkRoute {
+ prefix: b2
+ dir: out
+ connection: broker
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The linkRoute tells router Ra that any sender or receiver that is
+attached with a target or source (respectively) whos address begins with
+"b2", should be routed to the broker B2 (via the route-container
+connector).</p></div>
+<div class="paragraph"><p>Note that receiving and sending links are configured and routed
+separately. This allows configuration of link routes for listeners only
+or senders only. A direction of "in" matches client senders (i.e. links
+that carry messages inbound to the router network). Direction "out"
+matches client receivers.</p></div>
+<div class="paragraph"><p>Examples of addresses that "begin with <em>b2</em>" include:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+b2
+</p>
+</li>
+<li>
+<p>
+b2.queues
+</p>
+</li>
+<li>
+<p>
+b2.queues.app1
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>When the route-container connector is configured, router Ra establishes
+a connection to the broker. Once the connection is open, Ra tells the
+other routers (Rp and Rb) that it is a valid destination for link-routes
+to the "b2" prefix. This means that sender or receiver links attached to
+Rb or Rp will be routed via the shortest path to Ra where they are then
+routed outbound to the broker B2.</p></div>
+<div class="paragraph"><p>On Rp and Rb, it is advisable to add the identical configuration. It is
+permissible for a linkRoute configuration to reference a connection that
+does not exist.</p></div>
+<div class="paragraph"><p>This configuration tells the routers that link-routing is intended to be
+available for targets and sources starting with "b2". This is important
+because it is possible that B2 might be unavailable or shut off. If B2
+is unreachable, Ra will not advertize itself as a destination for "b2"
+and the other routers might never know that "b2" was intended for
+link-routing.</p></div>
+<div class="paragraph"><p>The above configuration allows Rb and Rp to reject attaches that should
+be routed to B2 with an error message that indicates that there is no
+route available to the destination.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="indirect-waypoints-and-auto-links">2.5. Indirect Waypoints and Auto-Links</h3>
+<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
+improvement on an earlier somewhat experimental feature called
+Waypoints.</p></div>
+<div class="paragraph"><p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
+actively attach a link to a node on an external AMQP container. The
+obvious application for this feature is to route messages through a
+queue on a broker, but other applications are possible as well.</p></div>
+<div class="paragraph"><p>An auto-link manages the lifecycle of one AMQP link. If messages are to
+be routed to and from a queue on a broker, then two auto-links are
+needed: one for sending messages to the queue and another for receiving
+messages from the queue. The container to which an auto-link attempts to
+attach may be identified in one of two ways:</p></div>
+<div class="quoteblock">
+<div class="content">
+<div class="ulist"><ul>
+<li>
+<p>
+The name of the connector/listener that resulted in the connection of
+the container, or
+</p>
+</li>
+<li>
+<p>
+The AMQP container-id of the remote container.
+</p>
+</li>
+</ul></div>
+</div>
+<div class="attribution">
+</div></div>
+<div class="sect3">
+<h4 id="queue-waypoint-example">2.5.1. Queue Waypoint Example</h4>
+<div class="paragraph"><p>Here is an example configuration for routing messages deliveries through
+a pair of queues on a broker:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ name: broker
+ role: route-container
+ host: <hostname>
+ port: <port>
+ saslMechanisms: ANONYMOUS
+}
+
+address {
+ prefix: queue
+ waypoint: yes
+}
+
+autoLink {
+ addr: queue.first
+ dir: in
+ connection: broker
+}
+
+autoLink {
+ addr: queue.first
+ dir: out
+ connection: broker
+}
+
+autoLink {
+ addr: queue.second
+ dir: in
+ connection: broker
+}
+
+autoLink {
+ addr: queue.second
+ dir: out
+ connection: broker
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
+for routing messages through queues via autolinks. The four <code>autoLink</code> entities
+identify the head and tail of two queues on the broker that will be connected
+via auto-links.</p></div>
+<div class="paragraph"><p>If there is no broker connected, the auto-links shall remain
+<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat --autolinks
+AutoLinks
+ addr dir phase link status lastErr
+ ===================================================
+ queue.first in 1 inactive
+ queue.first out 0 inactive
+ queue.second in 1 inactive
+ queue.second out 0 inactive</code></pre>
+</div></div>
+<div class="paragraph"><p>If a broker comes online with a queue called <em>queue.first</em>, the
+auto-links will attempt to activate:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat --autolinks
+AutoLinks
+ addr dir phase link status lastErr
+ ======================================================================
+ queue.first in 1 6 active
+ queue.first out 0 7 active
+ queue.second in 1 failed Node not found: queue.second
+ queue.second out 0 failed Node not found: queue.second</code></pre>
+</div></div>
+<div class="paragraph"><p>Note that two of the auto-links are in <em>failed</em> state because the queue
+does not exist on the broker.</p></div>
+<div class="paragraph"><p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
+three messages to <em>queue.first</em> via the router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python simple_send.py -a 127.0.0.1/queue.first -m3
+all messages confirmed</code></pre>
+</div></div>
+<div class="paragraph"><p>and then look at the address statistics on the router:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ========================================================================================================
+ mobile queue.first 1 balanced 0 0 0 0 0 0 0 0 0
+ mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>we see that <em>queue.first</em> appears twice in the list of addresses. The
+<code>phs</code>, or phase column shows that there are two phases for the
+address. Phase <em>0</em> is for routing message deliveries from producers to
+the tail of the queue (the <code>out</code> auto-link associated with the queue).
+Phase 1 is for routing deliveries from the head of the queue to
+subscribed consumers.</p></div>
+<div class="paragraph"><p>Note that three deliveries have been counted in the "in" and "out"
+columns for phase <em>0</em>. The "in" column represents the three messages
+that arrived from <code>simple_send.py</code> and the <code>out</code> column represents the three
+deliveries to the queue on the broker.</p></div>
+<div class="paragraph"><p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ python simple_recv.py -a 127.0.0.1:5672/queue.first -m3
+{u'sequence': int32(1)}
+{u'sequence': int32(2)}
+{u'sequence': int32(3)}</code></pre>
+</div></div>
+<div class="paragraph"><p>We receive the three queued messages. Looking at the addresses again, we
+see that phase 1 was used to deliver those messages from the queue to
+the consumer.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>$ qdstat -a
+Router Addresses
+ class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
+ ========================================================================================================
+ mobile queue.first 1 balanced 0 0 0 0 3 3 0 0 0
+ mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
+</div></div>
+<div class="paragraph"><p>Note that even in a multi-router network, and with multiple producers
+and consumers for <em>queue.first</em>, all deliveries will be routed through
+the queue on the connected broker.</p></div>
+</div>
+<div class="sect3">
+<h4 id="sharded-queue-example">2.5.2. Sharded Queue Example</h4>
+<div class="paragraph"><p>Here is an extension of the above example to illustrate how Qpid
+Dispatch Router can be used to create a distributed queue in which
+multiple brokers share the message-queueing load.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ name: broker1
+ role: route-container
+ host: <hostname>
+ port: <port>
+ saslMechanisms: ANONYMOUS
+}
+
+connector {
+ name: broker2
+ role: route-container
+ host: <hostname>
+ port: <port>
+ saslMechanisms: ANONYMOUS
+}
+
+address {
+ prefix: queue
+ waypoint: yes
+}
+
+autoLink {
+ addr: queue.first
+ dir: in
+ connection: broker1
+}
+
+autoLink {
+ addr: queue.first
+ dir: out
+ connection: broker1
+}
+
+autoLink {
+ addr: queue.first
+ dir: in
+ connection: broker2
+}
+
+autoLink {
+ addr: queue.first
+ dir: out
+ connection: broker2
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>In the above configuration, there are two instances of <em>queue.first</em> on
+brokers 1 and 2. Message traffic from producers to address <em>queue.first</em>
+shall be balanced between the two instance and messages from the queues
+shall be balanced across the collection of subscribers to the same
+address.</p></div>
+</div>
+<div class="sect3">
+<h4 id="dynamically-adding-shards">2.5.3. Dynamically Adding Shards</h4>
+<div class="paragraph"><p>Since configurable entities in the router can also be accessed via the
+management protocol, we can remotely add a shard to the above example
+using <code>qdmanage</code>:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>qdmanage create --type org.apache.qpid.dispatch.connector host=<host> port=<port> name=broker3
+qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=in connection=broker3
+qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=out connection=broker3</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="policy">2.6. Policy</h3>
+<div class="paragraph"><p>The Policy module is an optional authorization mechanism enforcing
+user connection restrictions and AMQP resource access control.</p></div>
+<div class="paragraph"><p>Policy is assigned when a connection is created. The connection
+properties <strong>AMQP virtual host</strong>, <strong>authenticated user name</strong>, and <strong>connection
+remote host</strong> are passed to the policy engine for a connection
+allow/deny decision. If the connection is allowed then the user is
+assigned to a group that names a set of AMQP resource limits that are
+enforced for the lifetime of the connection.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+<div class="paragraph"><p>Policy limits are applied only to incoming user network connections.
+Policy limits are not applied to interrouter connections nor are they
+applied to router connections outbound to waypoints.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="sect3">
+<h4 id="_definitions">2.6.1. Definitions</h4>
+<div class="sect4">
+<h5 id="_vhost">vhost</h5>
+<div class="paragraph"><p>A <em>vhost</em> is typically the name of the host to which the client AMQP
+connection is directed. For example, suppose a client application opens
+connection URL:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>amqp://bigbroker.example.com:5672/favorite_subject</code></pre>
+</div></div>
+<div class="paragraph"><p>The client will signal virtual host name <em>bigbroker.example.com</em> to
+the router during AMQP connection startup. Router Policy intercepts
+the virtual host <em>bigbroker.example.com</em> and applies a vhost policy
+with that name to the connection.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_policy_features">2.6.2. Policy Features</h4>
+<div class="sect4">
+<h5 id="_total_connection_limit">Total Connection Limit</h5>
+<div class="paragraph"><p>A router may be configured with a total connection limit. This limit
+controls the maximum number of simultaneous incoming user connections
+that are allowed at any time. It protects the router from file
+descriptor resource exhaustion in the face of many incoming client
+connections. This limit is specified and enforced independently of
+any other Policy settings.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_vhost_policy">Vhost Policy</h5>
+<div class="paragraph"><p>Vhost policy defines users and assigns them to user groups. Each
+user group defines the remote hosts from which the members may connect
+to the router network, and what resources in the router network the
+group members are allowed to access.</p></div>
+<div class="paragraph"><p>Vhost policy also defines connection count limits to control the
+number of users that may be simultaneously connected to the vhost.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+<div class="paragraph"><p>A vhost user may be assigned to one user group only.</p></div>
+</td>
+</tr></table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_default_vhost">Default Vhost</h5>
+<div class="paragraph"><p>A default vhost may be defined. The default vhost policy is used for
+connections whose vhost is otherwise not defined in the policy database.</p></div>
+<div class="paragraph"><p><a href="#example2">Example 2</a> illustrates how the default vhost feature can
+be used to apply a single vhost policy set of restrictions to any
+number of vhost connections.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_policy_schema">2.6.3. Policy Schema</h4>
+<div class="paragraph"><p>Policy configuration is specified in two schema objects.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>policy = {
+ <global settings>
+}
+
+vhost = {
+ id: vhost-name
+ <connection limits>
+ groups: {
+ group-name: {
+ <user group settings>
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>The <em>policy</em> object is a singleton. Multiple <em>vhost</em> objects may be
+created as needed.</p></div>
+<div class="sect4">
+<h5 id="_global_policy">Global Policy</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="35%" />
+<col width="15%" />
+<col width="50%" />
+<thead>
+<tr>
+<th align="left" valign="top"> attribute </th>
+<th align="left" valign="top"> default </th>
+<th align="left" valign="top"> description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnections</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Global maximum number of concurrent client connections allowed. This limit is always enforced even if no other policy settings have been defined. This limit is applied to all incoming connections regardless of remote host, authenticated user, or targeted vhost.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">enableVhostPolicy</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">Enable vhost policy connection denial, and resource limit enforcement.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">policyDir</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">Absolute path to a directory that holds vhost definition .json files. All vhost definitions in all .json files in this directory are processed.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">defaultVhost</p></td>
+<td align="left" valign="top"><p class="table">"$default"</p></td>
+<td align="left" valign="top"><p class="table">Vhost rule set name to use for connections with a vhost that is otherwise not defined. Default vhost processing may be disabled either by erasing the definition of <em>defaultVhost</em> or by not defining a <em>vhost</em> object named <em>$default</em>.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_vhost_policy_2">Vhost Policy</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="35%" />
+<col width="15%" />
+<col width="50%" />
+<thead>
+<tr>
+<th align="left" valign="top"> attribute </th>
+<th align="left" valign="top"> default </th>
+<th align="left" valign="top"> description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">id</p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table">Vhost name must be unique.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnections</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of concurrent client connections allowed.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnectionsPerUser</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of concurrent client connections allowed for any user.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxConnectionsPerRemoteHost</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of concurrent client connections allowed for any remote host.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowUnknownUser</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">Allow unknown users who are not members of a defined user group. Unknown users are assigned to the <em>$default</em> user group and receive <em>$default</em> settings.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">groups</p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table">A map where each key is a user group name and the value is a Vhost User Group Settings map.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_vhost_user_group_settings_map">Vhost User Group Settings Map</h5>
+<div class="paragraph"><p>This object is the data value contained in entries in the policy/groups map.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="35%" />
+<col width="15%" />
+<col width="50%" />
+<thead>
+<tr>
+<th align="left" valign="top"> Section/Attribute </th>
+<th align="left" valign="top"> default </th>
+<th align="left" valign="top"> description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>Group Membership</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">users</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of authenticated users in this group.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>Connection Restrictions</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">remoteHosts</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of remote hosts from which the users may connect. List values may be host names, numeric IP addresses, numeric IP address ranges, or the wildcard <em>*</em>. An empty list denies all access.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>AMQP Connection Open Limits</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxFrameSize</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Largest frame that may be sent on this connection. (AMQP Open, max-frame-size)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxSessions</p></td>
+<td align="left" valign="top"><p class="table">65535</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of sessions that may be created on this connection. (AMQP Open, channel-max)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>AMQP Session Begin Limits</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxSessionWindow</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Incoming capacity for new sessions. (AMQP Begin, incoming-window)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>AMQP Link Attach</strong></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+<td align="left" valign="top"><p class="table"></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxMessageSize</p></td>
+<td align="left" valign="top"><p class="table">0</p></td>
+<td align="left" valign="top"><p class="table">Largest message size supported by links created on this connection. If this field is zero there is no maximum size imposed by the link endpoint. (AMQP Attach, max-message-size)</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxSenders</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of sending links that may be created on this connection.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">maxReceivers</p></td>
+<td align="left" valign="top"><p class="table">2^31-1</p></td>
+<td align="left" valign="top"><p class="table">Maximum number of receiving links that may be created on this connection.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowDynamicSource</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">This connection is allowed to create receiving links using the Dynamic Link Source feature.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowAnonymousSender</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">This connection is allowed to create sending links using the Anonymous Sender feature.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">allowUserIdProxy</p></td>
+<td align="left" valign="top"><p class="table">false</p></td>
+<td align="left" valign="top"><p class="table">This connection is allowed to send messages with a user_id property that differs from the connection’s authenticated user id.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">sources</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of Source addresses allowed when creating receiving links. This list may be expressed as a CSV string or as a list of strings. An empty list denies all access.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">targets</p></td>
+<td align="left" valign="top"><p class="table">""</p></td>
+<td align="left" valign="top"><p class="table">List of Target addresses allowed when creating sending links. This list may be expressed as a CSV string or as a list of strings. An empty list denies all access.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_policy_wildcard_and_user_name_substitution">2.6.4. Policy Wildcard and User Name Substitution</h4>
+<div class="paragraph"><p>Policy provides several conventions to make writing rules easier.</p></div>
+<div class="sect4">
+<h5 id="_remote_host_wildcard">Remote Host Wildcard</h5>
+<div class="paragraph"><p>Remote host rules may consist of a single asterisk character to
+specify all hosts.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> remoteHosts: *</code></pre>
+</div></div>
+<div class="paragraph"><p>The asterisk must stand alone and cannot be appended to a host name
+or to an IP address fragment.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_amqp_source_and_target_wildcard_and_name_substitution">AMQP Source and Target Wildcard and Name Substitution</h5>
+<div class="paragraph"><p>The rule definitions for <code>sources</code> and <code>targets</code> may include the username
+substitution token</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> {user}</code></pre>
+</div></div>
+<div class="paragraph"><p>or a trailing asterisk.</p></div>
+<div class="paragraph"><p>The username substitution token is replaced with the authenticated user name for
+the connection. Using this token, an administrator may allow access to
+some resources specific to each user without having to name each user
+individually. This token is substituted once for the leftmost
+occurrence in the link name.</p></div>
+<div class="paragraph"><p>The asterisk is recognized only if it is the last character in the
+link name.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> sources: tmp_{user}, temp*, {user}-home-*</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_composing_policies">2.6.5. Composing Policies</h4>
+<div class="paragraph"><p>This section shows policy examples designed to illustrate some common use cases.</p></div>
+<div class="sect4">
+<h5 id="_example_1_user_policy_disabled">Example 1. User Policy Disabled</h5>
+<div class="paragraph"><p>Policy is disabled when no policy configuation objects are defined.
+Any number of connections are allowed and all users have
+access to all AMQP resources in the network.</p></div>
+</div>
+<div class="sect4">
+<h5 id="example2">Example 2. All Users Have Simple Connection Limits</h5>
+<div class="paragraph"><p>This example shows how to keep users from overwhelming the router with
+connections. Any user can create up to ten connections and the router
+will limit the aggregated user connection count to 100 connections
+total. No other restrictions apply.</p></div>
+<div class="paragraph"><p>This example also shows how to use a default vhost policy effectively.
+Only one vhost policy is defined and all user connections regardless
+of the requested vhost use that policy.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>policy {
+ maxConnections: 100 <b><1></b>
+}
+
+vhost {
+ name: $default <b><2></b>
+ maxConnectionsPerUser: 10 <b><3></b>
+ allowUnknownUser: true <b><4></b>
+ groups: {
+ $default: {
+ remoteHosts: * <b><5></b>
+ sources: * <b><6></b>
+ targets: * <b><6></b>
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="colist arabic"><ol>
+<li>
+<p>
+The global maxConnections limit of 100 is enforced.
+</p>
+</li>
+<li>
+<p>
+No normal vhost names are defined; user is assigned to default vhost <em>$default</em>.
+</p>
+</li>
+<li>
+<p>
+The vhost maxConnectionsPerUser limit of 10 is enforced.
+</p>
+</li>
+<li>
+<p>
+No groups are defined to have any users but allowUnknownUser is true so all users are assigned to group $default.
+</p>
+</li>
+<li>
+<p>
+The user is allowed to connect from any remote host.
+</p>
+</li>
+<li>
+<p>
+The user is allowed to connect to any source or target in the AMQP network. Router system-wide values are used for the other AMQP settings that are unspecified in the vhost rules.
+</p>
+</li>
+</ol></div>
+</div>
+<div class="sect4">
+<h5 id="_example_3_admins_must_connect_from_localhost">Example 3. Admins Must Connect From Localhost</h5>
+<div class="paragraph"><p>This example shows how an admin group may be created and restricted
+to accessing a vhost only from localhost. The admin users are allowed
+to connect to any AMQP resources while normal users are restricted.</p></div>
+<div class="paragraph"><p>In this example a user connects to vhost <em>example.com</em>.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>vhost {
+ name: example.com <b><1></b>
+ allowUnknownUser: true <b><3></b>
+ groups: {
+ admin: {
+ users: alice, bob <b><2></b>
+ remoteHosts: 127.0.0.1, ::1 <b><4></b>
+ sources: * <b><5></b>
+ targets: * <b><5></b>
+ },
+ $default: {
+ remoteHosts: * <b><6></b>
+ sources: news*, sports*, chat* <b><7></b>
+ targets: chat* <b><7></b>
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="colist arabic"><ol>
+<li>
+<p>
+A connection to vhost <em>example.com</em> locates this vhost rule set.
+</p>
+</li>
+<li>
+<p>
+If one of users <em>alice</em> or <em>bob</em> is connecting then she or he is assigned to the <em>admin</em> user group.
+</p>
+</li>
+<li>
+<p>
+Any other user is not defined by a user group. However, since the <em>allowUnknownUser</em> setting is true then this user is assigned to the <em>$default</em> user group.
+</p>
+</li>
+<li>
+<p>
+Users in the <em>admin</em> user group must connect from localhost. Connections for an <em>admin</em> user from other hosts on the network are denied.
+</p>
+</li>
+<li>
+<p>
+Users in the <em>admin</em> user group are allowed to access any resource offered by the vhost service.
+</p>
+</li>
+<li>
+<p>
+Other users are allowed to connect from any host.
+</p>
+</li>
+<li>
+<p>
+Other users have source and target name lists that restrict the resources they are allowed to access.
+</p>
+</li>
+</ol></div>
+</div>
+<div class="sect4">
+<h5 id="_example_4_limiting_possible_memory_consumption">Example 4. Limiting Possible Memory Consumption</h5>
+<div class="paragraph"><p>Policy provides a mechanism to control how much system buffer memory a
+user connection can potentially consume. The formula for computing
+buffer memory consumption for each session is</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code> potential buffer usage = maxFrameSize * maxSessionWindow</code></pre>
+</div></div>
+<div class="paragraph"><p>By adjusting <em>maxFrameSize</em>, <em>maxSessions</em>, and <em>maxSessionWindow</em> an
+administrator can prevent a user from consuming too much memory by
+buffering messages in flight.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+<div class="paragraph"><p>The settings passed into the AMQP protocol connection and session
+negotiations. Normal AMQP session flow control limits buffer
+consumption in due course with no processing cycles required by the
+router.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>In this example normal users, the traders, are given smaller buffer
+allocations while high-capacity, automated data feeds are given a
+higher buffer allocation. This example skips the details of settings
+unrelated to buffer allocation.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>vhost {
+ name: traders.com <b><1></b>
+ groups: {
+ traders: {
+ users: trader-1, trader-2, ... <b><2></b>
+ maxFrameSize: 10000 <b><3></b>
+ maxSessionWindow: 500 <b><3></b>
+ maxSessions: 1 <b><4></b>
+ ...
+ },
+ feeds: {
+ users: nyse-feed, nasdaq-feed <b><5></b>
+ maxFrameSize: 60000 <b><6></b>
+ maxSessionWindow: 20000 <b><6></b>
+ maxSessions: 3 <b><7></b>
+ ...
+ }
+ }
+}</code></pre>
+</div></div>
+<div class="colist arabic"><ol>
+<li>
+<p>
+These rules are for vhost traders.com.
+</p>
+</li>
+<li>
+<p>
+The <em>traders</em> group includes trader-1, trader-2, and any other user defined in the list.
+</p>
+</li>
+<li>
+<p>
+<em>maxFrameSize</em> and <em>maxSessionWindow</em> allow for at most 5,000,000 bytes of data to be in flight on each session.
+</p>
+</li>
+<li>
+<p>
+Only one session per connection is allowed.
+</p>
+</li>
+<li>
+<p>
+In the <em>feeds</em> group two users are defined.
+</p>
+</li>
+<li>
+<p>
+<em>maxFrameSize</em> and <em>maxSessionWindow</em> allow for at most 1,200,000,000 bytes of data to be in flight on each session.
+</p>
+</li>
+<li>
+<p>
+Up to three sessions per connection are allowed.
+</p>
+</li>
+</ol></div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="technical-details-and-specifications">3. Technical Details and Specifications</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="client-compatibility">3.1. Client Compatibility</h3>
+<div class="paragraph"><p>Dispatch Router should, in theory, work with any client that is
+compatible with AMQP 1.0. The following clients have been tested:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="22%" />
+<col width="78%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Client</em> </th>
+<th align="left" valign="top"><em>Notes</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">qpid::messaging</p></td>
+<td align="left" valign="top"><p class="table">The Qpid messaging clients work with Dispatch Router
+as long as they are configured to use the 1.0 version of the protocol.
+To enable AMQP 1.0 in the C++ client, use the {protocol:amqp1.0}
+connection option.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Proton Reactor</p></td>
+<td align="left" valign="top"><p class="table">The Proton Reactor API is compatible with Dispatch
+Router.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Proton Messenger</p></td>
+<td align="left" valign="top"><p class="table">Messenger works with Dispatch Router.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="addressing">3.2. Addressing</h3>
+<div class="paragraph"><p>AMQP addresses are used to control the flow of messages across a network
+of routers. Addresses are used in a number of different places in the
+AMQP 1.0 protocol. They can be used in a specific message in the <code>to</code>
+and <code>reply-to</code> fields of a message’s properties. They are also used
+during the creation of links in the <code>address</code> field of a <code>source</code> or
+a <code>target</code>.</p></div>
+<div class="paragraph"><p>Addresses designate various kinds of entities in a messaging network:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Endpoint processes that consume data or offer a service
+</p>
+</li>
+<li>
+<p>
+Topics that match multiple consumers to multiple producers
+</p>
+</li>
+<li>
+<p>
+Entities within a messaging broker:
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Queues
+</p>
+</li>
+<li>
+<p>
+Durable Topics
+</p>
+</li>
+<li>
+<p>
+Exchanges
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+<div class="paragraph"><p>The syntax of an AMQP address is opaque as far as the router network is
+concerned. A syntactical structure may be used by the administrator that
+creates addresses, but the router treats them as opaque strings. Routers
+consider addresses to be mobile such that any address may be directly
+connected to any router in a network and may move around the topology.
+In cases where messages are broadcast to or balanced across multiple
+consumers, an address may be connected to multiple routers in the
+network.</p></div>
+<div class="paragraph"><p>Addresses have semantics associated with them. When an address is
+created in the network, it is assigned a set of semantics (and access
+rules) during a process called provisioning. The semantics of an address
+control how routers behave when they see the address being used.</p></div>
+<div class="paragraph"><p>Address semantics include the following considerations:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Routing pattern</em> - direct, multicast, balanced
+</p>
+</li>
+<li>
+<p>
+<em>Undeliverable action</em> - drop, hold and retry, redirect
+</p>
+</li>
+<li>
+<p>
+<em>Reliability</em> - N destinations, etc.
+</p>
+</li>
+</ul></div>
+<div class="sect3">
+<h4 id="routing-patterns">3.2.1. Routing patterns</h4>
+<div class="paragraph"><p>Routing patterns constrain the paths that a message can take across a
+network.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="18%" />
+<col width="82%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Pattern</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><em>Direct</em></p></td>
+<td align="left" valign="top"><p class="table">Direct routing allows for only one consumer to use an address
+at a time. Messages (or links) follow the lowest cost path across the
+network from the sender to the one receiver.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><em>Multicast</em></p></td>
+<td align="left" valign="top"><p class="table">Multicast routing allows multiple consumers to use the
+same address at the same time. Messages are routed such that each
+consumer receives a copy of the message.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><em>Balanced</em></p></td>
+<td align="left" valign="top"><p class="table">Balanced routing also allows multiple consumers to use the
+same address. In this case, messages are routed to exactly one of the
+consumers, and the network attempts to balance the traffic load across
+the set of consumers using the same address.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="routing-mechanisms">3.2.2. Routing mechanisms</h4>
+<div class="paragraph"><p>The fact that addresses can be used in different ways suggests that
+message routing can be accomplished in different ways. Before going into
+the specifics of the different routing mechanisms, it would be good to
+first define what is meant by the term <em>routing</em>:</p></div>
+<div class="quoteblock">
+<div class="content">
+<div class="paragraph"><p>In a network built of multiple routers connected by connections (i.e.,
+nodes and edges in a graph), <em>routing</em> determines which connection to
+use to send a message directly to its destination or one step closer to
+its destination.</p></div>
+</div>
+<div class="attribution">
+</div></div>
+<div class="paragraph"><p>Each router serves as the terminus of a collection of incoming and
+outgoing links. The links either connect directly to endpoints that
+produce and consume messages, or they connect to other routers in the
+network along previously established connections.</p></div>
+<div class="sect4">
+<h5 id="message-routing">Message routing</h5>
+<div class="paragraph"><p>Message routing occurs upon delivery of a message and is done based on
+the address in the message’s <code>to</code> field.</p></div>
+<div class="paragraph"><p>When a delivery arrives on an incoming link, the router extracts the
+address from the delivered message’s <code>to</code> field and looks the address up
+in its routing table. The lookup results in zero or more outgoing links
+onto which the message shall be resent.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="20%" />
+<col width="80%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Delivery</em> </th>
+<th align="left" valign="top"><em>Handling</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><em>pre-settled</em></p></td>
+<td align="left" valign="top"><p class="table">If the arriving delivery is pre-settled (i.e., fire and
+forget), the incoming delivery shall be settled by the router, and the
+outgoing deliveries shall also be pre-settled. In other words, the
+pre-settled nature of the message delivery is propagated across the
+network to the message’s destination.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><em>unsettled</em></p></td>
+<td align="left" valign="top"><p class="table">Unsettled delivery is also propagated across the network.
+Because unsettled delivery records cannot be discarded, the router
+tracks the incoming deliveries and keeps the association of the incoming
+deliveries to the resulting outgoing deliveries. This kept association
+allows the router to continue to propagate changes in delivery state
+(settlement and disposition) back and forth along the path which the
+message traveled.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="amqp-mapping">3.3. AMQP Mapping</h3>
+<div class="paragraph"><p>Dispatch Router is an AMQP router and as such, it provides extensions,
+code-points, and semantics for routing over AMQP. This page documents the
+details of Dispatch Router’s use of AMQP.</p></div>
+<div class="sect3">
+<h4 id="message-annotations">3.3.1. Message Annotations</h4>
+<div class="paragraph"><p>The following Message Annotation fields are defined by Dispatch Router:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="23%" />
+<col width="19%" />
+<col width="58%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Field</em> </th>
+<th align="left" valign="top"><em>Type</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.ingress</p></td>
+<td align="left" valign="top"><p class="table">string</p></td>
+<td align="left" valign="top"><p class="table">The identity of the ingress router for a
+message-routed message. The ingress router is the first router
+encountered by a transiting message. The router will, if this field is
+present, leave it unaltered. If the field is not present, the router
+shall insert the field with its own identity.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.trace</p></td>
+<td align="left" valign="top"><p class="table">list of string</p></td>
+<td align="left" valign="top"><p class="table">The list of routers through which this
+message-routed message has transited. If this field is not present, the
+router shall do nothing. If the field is present, the router shall
+append its own identity to the end of the list.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.to</p></td>
+<td align="left" valign="top"><p class="table">string</p></td>
+<td align="left" valign="top"><p class="table">To-Override for message-routed messages. If this
+field is present, the address in this field shall be used for routing in
+lieu of the <em>to</em> field in the message properties. A router may append,
+remove, or modify this annotation field depending on the policy in place
+for routing the message.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.phase</p></td>
+<td align="left" valign="top"><p class="table">integer</p></td>
+<td align="left" valign="top"><p class="table">The address-phase, if not zero, for messages
+flowing between routers.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="sourcetarget-capabilities">3.3.2. Source/Target Capabilities</h4>
+<div class="paragraph"><p>The following Capability values are used in Sources and Targets.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="19%" />
+<col width="81%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Capability</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">qd.router</p></td>
+<td align="left" valign="top"><p class="table">This capability is added to sources and targets that are
+used for inter-router message exchange. This capability denotes a link
+used for router-control messages flowing between routers.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">qd.router-data</p></td>
+<td align="left" valign="top"><p class="table">This capability is added to sources and targets that
+are used for inter-router message exchange. This capability denotes a
+link used for user messages being message-routed across an inter-router
+connection.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="dynamic-node-properties">3.3.3. Dynamic-Node-Properties</h4>
+<div class="paragraph"><p>The following dynamic-node-properties are used by Dispatch in Sources.</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="23%" />
+<col width="77%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Property</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table">x-opt-qd.address</p></td>
+<td align="left" valign="top"><p class="table">The node address describing the destination desired
+for a dynamic source. If this is absent, the router will terminate any
+dynamic receivers. If this address is present, the router will use the
+address to route the dynamic link attach to the proper destination
+container.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="addresses-and-address-formats">3.3.4. Addresses and Address Formats</h4>
+<div class="paragraph"><p>The following AMQP addresses and address patterns are used within
+Dispatch Router.</p></div>
+<div class="sect4">
+<h5 id="address-patterns">Address Patterns</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="38%" />
+<col width="62%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Pattern</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_local/<addr></code></p></td>
+<td align="left" valign="top"><p class="table">An address that references a locally attached endpoint.
+Messages using this address pattern shall not be routed over more than
+one link.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_topo/0/<router>/<addr></code></p></td>
+<td align="left" valign="top"><p class="table">An address that references an endpoint attached to a specific router
+node in the network topology. Messages with addresses that follow this
+pattern shall be routed along the shortest path to the specified router.
+Note that addresses of this form are a-priori routable in that the
+address itself contains enough information to route the message to its
+destination.</p>
+<p class="table">The <em>0</em> component immediately preceding the router-id is a placeholder
+for an <em>area</em> which may be used in the future if area routing is
+implemented.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code><addr></code></p></td>
+<td align="left" valign="top"><p class="table">A mobile address. An address of this format represents an
+endpoint or a set of distinct endpoints that are attached to the network
+in arbitrary locations. It is the responsibility of the router network
+to determine which router nodes are valid destinations for mobile
+addresses.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="supported-addresses">Supported Addresses</h5>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="36%" />
+<col width="64%" />
+<thead>
+<tr>
+<th align="left" valign="top"><em>Address</em> </th>
+<th align="left" valign="top"><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><code>$management</code></p></td>
+<td align="left" valign="top"><p class="table">The management agent on the attached router/container.
+This address would be used by an endpoint that is a management
+client/console/tool wishing to access management data from the attached
+container.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/$management</code></p></td>
+<td align="left" valign="top"><p class="table">The management agent at Router.E in area
+0. This address would be used by a management client wishing to access
+management data from a specific container that is reachable within the
+network.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_local/qdhello</code></p></td>
+<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+This address is used to communicate with neighbor routers and is
+exclusively for the HELLO discovery protocol.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_local/qdrouter</code></p></td>
+<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+This address is used by a router to communicate with other routers in
+the network.</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/qdrouter</code></p></td>
+<td align="left" valign="top"><p class="table">The router entity at the specifically
+indicated router. This address form is used by a router to communicate
+with a specific router that may or may not be a neighbor.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</h4>
+<div class="paragraph"><p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
+emerging AMQP Management specification (draft 9).</p></div>
+<div class="paragraph"><p>Differences from the specification:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+The <code>name</code> attribute is not required when an entity is created. If
+ not supplied it will be set to the same value as the system-generated
+ "identity" attribute. Otherwise it is treated as per the standard.
+</p>
+</li>
+<li>
+<p>
+The <code>REGISTER</code> and <code>DEREGISTER</code> operations are not implemented. The router
+ automatically discovers peer routers via the router network and makes
+ their management addresses available via the standard <code>GET-MGMT-NODES</code>
+ operation.
+= Management Schema
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>This chapter documents the set of <strong>management entity types</strong> that define
+configuration and management of a Dispatch Router. A management entity type has
+a set of <strong>attributes</strong> that can be read, some attributes can also be
+updated. Some entity types also support <strong>operations</strong> that can be called.</p></div>
+<div class="paragraph"><p>All management entity types have the following standard attributes:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+type
+</dt>
+<dd>
+<p>
+ The fully qualified type of the entity,
+ e.g. <code>org.apache.qpid.dispatch.router</code>. This document uses the short name
+ without the <code>org.apache.qpid.dispatch</code> prefix e.g. <code>router</code>. The dispatch
+ tools will accept the short or long name.
+</p>
+</dd>
+<dt class="hdlist1">
+name
+</dt>
+<dd>
+<p>
+ A user-generated identity for the entity. This can be used in other entities
+ that need to refer to the named entity.
+</p>
+</dd>
+<dt class="hdlist1">
+identity
+</dt>
+<dd>
+<p>
+ A system-generated identity of the entity. It includes
+ the short type name and some identifying information. E.g. <code>log/AGENT</code> or
+ <code>listener/localhost:amqp</code>
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>There are two main categories of management entity type.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+Configuration Entities
+</dt>
+<dd>
+<p>
+ Parameters that can be set in the configuration file
+ (see <code>qdrouterd.conf(5)</code> man page) or set at run-time with the <code>qdmanage(8)</code>
+ tool.
+</p>
+</dd>
+<dt class="hdlist1">
+Operational Entities
+</dt>
+<dd>
+<p>
+ Run-time status values that can be queried using <code>qdstat(8)</code> or <code>qdmanage(8)</code> tools.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuration_entities">3.4. Configuration Entities</h3>
+<div class="paragraph"><p>Configuration entities define the attributes allowed in the configuration file
+(see <code>qdrouterd.conf(5)</code>) but you can also create entities once the router is
+running using the <code>qdrouterd(8)</code> tool’s <code>create</code> operation. Some entities can also
+be modified using the <code>update</code> operation, see the entity descriptions below.</p></div>
+<div class="sect3">
+<h4 id="_router">3.4.1. router</h4>
+<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
+<div class="paragraph"><p>Operations allowed: <code>READ</code></p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>id</em> (string, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>area</em> (string)
+</dt>
+<dd>
+<p>
+ Unused placeholder.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloInterval</em> (integer, default=1, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Interval in seconds between HELLO messages sent to neighbor routers.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloMaxAge</em> (integer, default=3, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Time in seconds after which a neighbor is declared lost if no HELLO is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raInterval</em> (integer, default=30, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers in a stable network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raIntervalFlux</em> (integer, default=4, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>remoteLsMaxAge</em> (integer, default=60, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ Time in seconds after which link state is declared stale if no RA is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>addrCount</em> (integer)
+</dt>
+<dd>
+<p>
+ Number of addresses known to the router.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>linkCount</em> (integer)
+</dt>
+<dd>
+<p>
+ Number of links attached to the router node.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>nodeCount</em> (integer)
+</dt>
+<dd>
+<p>
+ Number of known peer router nodes.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>workerThreads</em> (integer, default=4, <code>CREATE</code>)
+</dt>
+<dd>
+<p>
+ The number of threads that w
<TRUNCATED>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console1.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console1.png b/content/releases/qpid-dispatch-0.7.0/book/console1.png
new file mode 100755
index 0000000..f131884
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console1.png differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[3/6] qpid-site git commit: NO-JIRA - Updating documentation for Qpid
Dispatch Router version 0.7.0
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/man/qdstat.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/man/qdstat.html b/content/releases/qpid-dispatch-0.7.0/man/qdstat.html
new file mode 100644
index 0000000..86c2a42
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/man/qdstat.html
@@ -0,0 +1,882 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>SYNOPSIS - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.7.0/index.html">Qpid Dispatch 0.7.0</a></li><li>SYNOPSIS</li></ul>
+
+ <div id="-middle-content">
+ <div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdstat</strong> [<em>OPTIONS</em>]</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Shows status information about networks of Dispatch routers. It can display
+connections, network nodes and links, and router stats such as memory use.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options">OPTIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>-h, --help
+: show this help message and exit</p></div>
+<div class="paragraph"><p>--version
+: Print version and exit.</p></div>
+<div class="paragraph"><p>-g, --general
+: Show General Router Stats</p></div>
+<div class="paragraph"><p>-c, --connections
+: Show Connections</p></div>
+<div class="paragraph"><p>-l, --links
+: Show Router Links</p></div>
+<div class="paragraph"><p>-n, --nodes
+: Show Router Nodes</p></div>
+<div class="paragraph"><p>-a, --address
+: Show Router Addresses</p></div>
+<div class="paragraph"><p>-m, --memory
+: Show Router Memory Stats</p></div>
+<div class="paragraph"><p>--autolinks
+: Show Auto Links</p></div>
+<div class="paragraph"><p>--linkroutes
+: Show Link Routes</p></div>
+<div class="paragraph"><p>-v, --verbose
+: Show maximum detail</p></div>
+<div class="paragraph"><p>--log
+: Show recent log entries</p></div>
+<div class="paragraph"><p>--limit=LIMIT
+: Limit number of log entries</p></div>
+<div class="sect2">
+<h3 id="_connection_options">Connection Options</h3>
+<div class="paragraph"><p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default</p></div>
+<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p></div>
+<div class="paragraph"><p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p></div>
+<div class="paragraph"><p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--ssl-password-file=SSL-PASSWORD-FILE
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--sasl-mechanisms=SASL-MECHANISMS
+: Allowed sasl mechanisms to be supplied during the sasl handshake.</p></div>
+<div class="paragraph"><p>--sasl-username=SASL-USERNAME
+: User name for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password=SASL-PASSWORD
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password-file=SASL-PASSWORD-FILE
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--ssl-disable-peer-name-verify
+: Disables SSL peer name verification. WARNING - This option is insecure and must not be used in production environments</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_output_columns">OUTPUT COLUMNS</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_qdstat_c">qdstat -c</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+id
+</dt>
+<dd>
+<p>
+Unique connection identifier
+</p>
+</dd>
+<dt class="hdlist1">
+host
+</dt>
+<dd>
+<p>
+The hostname or internet address of the remotely connected AMQP container
+</p>
+</dd>
+<dt class="hdlist1">
+container
+</dt>
+<dd>
+<p>
+The container-name of the remotely connected AMQP container
+</p>
+</dd>
+<dt class="hdlist1">
+role
+</dt>
+<dd>
+<p>
+The configured role of the connection
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+normal - Normal connections from client to router
+</p>
+</li>
+<li>
+<p>
+inter-router - Connection between routers to form a network
+</p>
+</li>
+<li>
+<p>
+route-container - Connection to/from a Broker or other host to receive link-routes and waypoints
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction of connection establishment
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+in - The connection was initiated by the remote container
+</p>
+</li>
+<li>
+<p>
+out - The connection was initiated by this router
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+security
+</dt>
+<dd>
+<p>
+A description of the security/encryption in effect for this
+connection
+</p>
+</dd>
+<dt class="hdlist1">
+authentication
+</dt>
+<dd>
+<p>
+The method and user-id of the authenticated user for
+this connection
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_qdstat_l">qdstat -l</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+type
+</dt>
+<dd>
+<p>
+Type of link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+router-control - An inter-router link that is reserved for control messages exchanged between routers
+</p>
+</li>
+<li>
+<p>
+inter-router - An inter-router link that is used for normal message-routed deliveries
+</p>
+</li>
+<li>
+<p>
+endpoint - A normal link to an external endpoint container
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction of message flow on the link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+in - Deliveries flow inbound to the router
+</p>
+</li>
+<li>
+<p>
+out - Deliveries flow outbound from the router
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+conn id
+</dt>
+<dd>
+<p>
+Unique identifier of the connection over which this link is
+attached
+</p>
+</dd>
+<dt class="hdlist1">
+id
+</dt>
+<dd>
+<p>
+Unique identifier of this link
+</p>
+</dd>
+<dt class="hdlist1">
+peer
+</dt>
+<dd>
+<p>
+For link-routed links, the unique identifier of the peer link. In
+link routing, an inbound link is paired with an outbound link
+</p>
+</dd>
+<dt class="hdlist1">
+class
+</dt>
+<dd>
+<p>
+Class of the address bound to the link
+</p>
+</dd>
+<dt class="hdlist1">
+addr
+</dt>
+<dd>
+<p>
+The address bound to the link
+</p>
+</dd>
+<dt class="hdlist1">
+phs
+</dt>
+<dd>
+<p>
+The phase of the address bound to the link
+</p>
+</dd>
+<dt class="hdlist1">
+cap
+</dt>
+<dd>
+<p>
+The capacity, in deliveries, of the link
+</p>
+</dd>
+<dt class="hdlist1">
+undel
+</dt>
+<dd>
+<p>
+The number of undelivered messages stored on the link’s FIFO
+</p>
+</dd>
+<dt class="hdlist1">
+unsett
+</dt>
+<dd>
+<p>
+The number of unsettled deliveries being tracked by the link
+</p>
+</dd>
+<dt class="hdlist1">
+del
+</dt>
+<dd>
+<p>
+The total number of deliveries that have transited this link
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>presett:
+The number of pre-settled deliveries that transited this link</p></div>
+<div class="paragraph"><p>acc:
+The number of deliveries on this link that were accepted</p></div>
+<div class="paragraph"><p>rej:
+The number of deliveries on this link that were rejected</p></div>
+<div class="paragraph"><p>rel:
+The number of deliveries on this link that were released</p></div>
+<div class="paragraph"><p>mod:
+The number of deliveries on this link that were modified</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+admin
+</dt>
+<dd>
+<p>
+The administrative status of the link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+enabled - The link is enabled for normal operation
+</p>
+</li>
+<li>
+<p>
+disabled - The link is disabled and should be quiescing or stopped (not yet supported)
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+oper
+</dt>
+<dd>
+<p>
+The operational status of the link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+up - The link is operational
+</p>
+</li>
+<li>
+<p>
+down - The link is not attached
+</p>
+</li>
+<li>
+<p>
+quiescing - The link is in the process of quiescing (not yet supported)
+</p>
+</li>
+<li>
+<p>
+idle - The link has completed quiescing and is idle (not yet supported)
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+name
+</dt>
+<dd>
+<p>
+The link name (only shown if the -v option is provided)
+</p>
+</dd>
+</dl></div>
+<div class="sect3">
+<h4 id="_qdstat_n">qdstat -n</h4>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+router-id
+</dt>
+<dd>
+<p>
+Identifier of the router
+</p>
+</dd>
+<dt class="hdlist1">
+next-hop
+</dt>
+<dd>
+<p>
+If this router is not a neighbor, identifies the next-hop neighbor used to reach this router
+</p>
+</dd>
+<dt class="hdlist1">
+link
+</dt>
+<dd>
+<p>
+Unique identifier of the link to the neighbor router
+</p>
+</dd>
+<dt class="hdlist1">
+cost
+</dt>
+<dd>
+<p>
+The topology cost to this remote router (with -v option only)
+</p>
+</dd>
+<dt class="hdlist1">
+neighbors
+</dt>
+<dd>
+<p>
+The list of neighbor routers (the router’s link-state) (with -v option only)
+</p>
+</dd>
+<dt class="hdlist1">
+valid-origins
+</dt>
+<dd>
+<p>
+The list of origin routers for which the best path to the listed router passes through this router (with -v option only)
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_qdstat_a">qdstat -a</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+class
+</dt>
+<dd>
+<p>
+The class of the listed address
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+local - Address that is local to this router
+</p>
+</li>
+<li>
+<p>
+topo - Topological address used for router control messages
+</p>
+</li>
+<li>
+<p>
+router - A summary router address used to route messages to a remote router’s local addresses
+</p>
+</li>
+<li>
+<p>
+mobile - A mobile address for an attached consumer or producer
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+addr
+</dt>
+<dd>
+<p>
+The address text
+</p>
+</dd>
+<dt class="hdlist1">
+phs
+</dt>
+<dd>
+<p>
+For mobile addresses only, the phase of the address. Direct addresses have only a phase 0. Waypoint addresses have multiple phases, normally 0 and 1.
+</p>
+</dd>
+<dt class="hdlist1">
+distrib
+</dt>
+<dd>
+<p>
+Distribution method used for this address
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+multicast - A copy of each message is delivered once to each consumer for the address
+</p>
+</li>
+<li>
+<p>
+closest - Each message is delivered to only one consumer for the address. The closest (lowest cost) consumer will be chosen. If there are multiple lowest-cost consumers, deliveries will be spread across those consumers.
+</p>
+</li>
+<li>
+<p>
+balanced - Each message is delivered to only one consumer for the address. The consumer with the fewest outstanding (unsettled) deliveries will be chosen. The cost of the route to the consumer is a threshold for delivery (i.e. higher cost consumers will only receive deliveries if closer consumers are backed up).
+</p>
+</li>
+<li>
+<p>
+flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+in-proc
+</dt>
+<dd>
+<p>
+The number of in-process consumers for this address
+</p>
+</dd>
+<dt class="hdlist1">
+local
+</dt>
+<dd>
+<p>
+The number of local (on this router) consumers for this address
+</p>
+</dd>
+<dt class="hdlist1">
+remote
+</dt>
+<dd>
+<p>
+The number of remote routers that have at least one consumer for this address
+</p>
+</dd>
+<dt class="hdlist1">
+cntnr
+</dt>
+<dd>
+<p>
+The number of locally attached containers that are destinations for link-routes on this address
+</p>
+</dd>
+<dt class="hdlist1">
+in
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that entered the network on this router
+</p>
+</dd>
+<dt class="hdlist1">
+out
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that exited the network on this router
+</p>
+</dd>
+<dt class="hdlist1">
+thru
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that were forwarded to other routers
+</p>
+</dd>
+<dt class="hdlist1">
+to-proc
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that were delivered to an in-process consumer
+</p>
+</dd>
+<dt class="hdlist1">
+from-proc
+</dt>
+<dd>
+<p>
+The number of deliveries for this address that were received from an in-process producer
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_qdstat_linkroutes">qdstat --linkroutes</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+prefix
+</dt>
+<dd>
+<p>
+The prefix for matching addresses of routed links
+</p>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction (from the router’s perspective) of matching links
+</p>
+</dd>
+<dt class="hdlist1">
+distrib
+</dt>
+<dd>
+<p>
+The distribution method used for routed links
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+linkBalanced - the only supported distribution for routed links
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+status
+</dt>
+<dd>
+<p>
+Operational status of the link route
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+active - Route is actively routing attaches (i.e. ready for use)
+</p>
+</li>
+<li>
+<p>
+inactive - Route is inactive because there is no local destination connected
+</p>
+</li>
+</ul></div>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_qstat_autolinks">qstat --autolinks</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+addr
+</dt>
+<dd>
+<p>
+The address of the auto link
+</p>
+</dd>
+<dt class="hdlist1">
+dir
+</dt>
+<dd>
+<p>
+The direction of message flow for the auto link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+in - Messages flow in from the route-container to the router network
+</p>
+</li>
+<li>
+<p>
+out - Messages flow out to the route-container from the router network
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+phs
+</dt>
+<dd>
+<p>
+Phase of the address for this auto link
+</p>
+</dd>
+<dt class="hdlist1">
+link
+</dt>
+<dd>
+<p>
+Unique identifier of the link managed by this auto link
+</p>
+</dd>
+<dt class="hdlist1">
+status
+</dt>
+<dd>
+<p>
+The operational status of this auto link
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+inactive - There is no connected container for this auto link
+</p>
+</li>
+<li>
+<p>
+attaching - The link is attaching to the container
+</p>
+</li>
+<li>
+<p>
+failed - The link-attach failed
+</p>
+</li>
+<li>
+<p>
+active - The link is operational
+</p>
+</li>
+<li>
+<p>
+quiescing - The link is quiescing (not yet supported)
+</p>
+</li>
+<li>
+<p>
+idle - The link is idle (not yet supported)
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+lastErr
+</dt>
+<dd>
+<p>
+The description of the last attach failure that occurred on this auto link
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="/security.html">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="-apache-feather" width="48" height="14" src="" alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2015
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; 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
+ </p>
+ </div>
+ </div>
+ </div>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/release-notes.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/release-notes.html b/content/releases/qpid-dispatch-0.7.0/release-notes.html
new file mode 100644
index 0000000..d6b9406
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/release-notes.html
@@ -0,0 +1,280 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>Qpid Dispatch 0.7.0 Release Notes - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.7.0/index.html">Qpid Dispatch 0.7.0</a></li><li>Qpid Dispatch 0.7.0 Release Notes</li></ul>
+
+ <div id="-middle-content">
+ <h1 id="qpid-dispatch-070-release-notes">Qpid Dispatch 0.7.0 Release Notes</h1>
+
+<p>Dispatch is a lightweight AMQP message router library. More about
+<a href="/components/dispatch-router/index.html">Qpid
+Dispatch</a>.</p>
+
+<p>For more information about this release, including download links and
+documentation, see the <a href="index.html">release overview</a>.</p>
+
+<h2 id="new-features-and-improvements">New features and improvements</h2>
+
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-204">DISPATCH-204</a> - Identity mapping from X.509 certificate data to a descriptive nickname</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-211">DISPATCH-211</a> - Expose connection properties in management response</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-233">DISPATCH-233</a> - Allow client side saslMechanisms to be specified for qdstat and qdmanage</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-311">DISPATCH-311</a> - [Policy] schema object names could be improved</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-348">DISPATCH-348</a> - Don't show deprecated entities and attributes</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-349">DISPATCH-349</a> - Modify the client icon on the topology page to indicate when there are multiple clients.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-350">DISPATCH-350</a> - Display list of links for client connections. Allow acquiesce of links</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-388">DISPATCH-388</a> - Add deprecated flag to schema entities and attributes</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-395">DISPATCH-395</a> - Add Links to overview page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-399">DISPATCH-399</a> - Convert documentation to asciidoc format</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-400">DISPATCH-400</a> - Remember last entity expanded on overview page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-407">DISPATCH-407</a> - Tweeks to Links on overview page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-412">DISPATCH-412</a> - Support 'stdout' as log destination as well as 'stderr'</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-427">DISPATCH-427</a> - Implement expand/collapse all to the Overview and Entities tabs</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-428">DISPATCH-428</a> - Connecting the dispatch-console to wrong port throws JS exception and freezes console</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-434">DISPATCH-434</a> - Remember all entities expanded on overview and entities pages</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-440">DISPATCH-440</a> - Use the placeholder HTML attribute to communicate default values in the Connect form</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-446">DISPATCH-446</a> - Make sslProfile an entity and remove all annotations</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-447">DISPATCH-447</a> - Modify cmake to optionally Install stand-alone and hawtio console</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-464">DISPATCH-464</a> - Change plugin name from dispatch-plugin to dispatch-hawtio-console to match the artifact name</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-468">DISPATCH-468</a> - Display-name for identity in x.509 certificates</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-471">DISPATCH-471</a> - server.c needs refactoring around qd_connection_t allocation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-477">DISPATCH-477</a> - Drop pre-settled under congestion</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-483">DISPATCH-483</a> - Display links per address and connection on overview page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-511">DISPATCH-511</a> - Remove performance problems from locks and memory allocation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-513">DISPATCH-513</a> - Add a typed iterator to parsed field (qd_parsed_field_t) </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-514">DISPATCH-514</a> - Add link statistics for different dispositions</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-515">DISPATCH-515</a> - Add example config file for auto starting webbroxy</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-517">DISPATCH-517</a> - Expose new link statistics on overview page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-518">DISPATCH-518</a> - Use eventfd instead of a pipe for poll wakeup.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-520">DISPATCH-520</a> - Remove qpidd references from dispatch system_test.py</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-521">DISPATCH-521</a> - Switch to verify qdrouterd installation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-522">DISPATCH-522</a> - Performance: Defer activation and driver-awakening</li>
+</ul>
+
+<h2 id="bugs-fixed">Bugs fixed</h2>
+
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-8">DISPATCH-8</a> - Message:user-id must be authenticated on ingress</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-160">DISPATCH-160</a> - Dispatch router does not propagate custom message annotations</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-224">DISPATCH-224</a> - Tools fail with no useful error in some SASL configurations</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-280">DISPATCH-280</a> - Management tools do not send AMQP Open.hostname with new proton</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-313">DISPATCH-313</a> - Tree on left side of entity page scrolls back to top after data is updated </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-316">DISPATCH-316</a> - Refector javascript so the common code between hawtio and standalone is not duplicated</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-317">DISPATCH-317</a> - Show tooltip for long values on left panel on topology page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-318">DISPATCH-318</a> - Don't allow router nodes to be moved off of the screen on topology page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-336">DISPATCH-336</a> - Very high latency for fire-and-forget sender</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-345">DISPATCH-345</a> - Initialize current node on entity page when logged into a different router network </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-346">DISPATCH-346</a> - Don't attempt to load non-existant css file when hawtio plugin loads</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-353">DISPATCH-353</a> - segfault in qd_entity_refresh_connection</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-354">DISPATCH-354</a> - qdstat general statistics broken</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-362">DISPATCH-362</a> - Handwritten paragraphs of man qdrouterd.conf are out of sync with autogenerated parts</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-363">DISPATCH-363</a> - Autogenerated part of man page qdrouterd.conf and output of <code>qdmanage print-json-schema</code> leave out the <code>name:</code> attribute in annotation sections</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-370">DISPATCH-370</a> - qdmanage tool hangs if --type option is "linkRoute" or "address"</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-373">DISPATCH-373</a> - qdmanage : no clear error message when "read" type linkRoute, address and autoLink</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-375">DISPATCH-375</a> - Console instalation instructions do not work</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-379">DISPATCH-379</a> - Missing default route indication on topology page</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-381">DISPATCH-381</a> - qdstat -g causes segfault</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-384">DISPATCH-384</a> - qdrouter.conf manual : saslMechanisms as "Space separated list ..."</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-389">DISPATCH-389</a> - Removing CONFIG and DISPATCH as modules for logging</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-391">DISPATCH-391</a> - Attributes missing for listener and connector and trustedCerts still there</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-392">DISPATCH-392</a> - "attributeName is undefined error" when showing "address", "linkRoute" and "autoLink"</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-393">DISPATCH-393</a> - Download router configuration doesn't work</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-394">DISPATCH-394</a> - Chart just added isn't shown in the dashboard</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-396">DISPATCH-396</a> - The "console" entity attributes aren't shown in the qdrouterd.conf</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-397">DISPATCH-397</a> - Error creating a new connector on a router with same name but on another router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-398">DISPATCH-398</a> - For Dispatch 0.7 release move up the minimum required version of qpid proton to 0.13.0</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-401">DISPATCH-401</a> - qdstat and qdmanage client tools do not verify host name when using SSL</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-402">DISPATCH-402</a> - Remove deprecated hyphen-separated config and entity names</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-405">DISPATCH-405</a> - Chart data should be cleared when the console disconnects</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-406">DISPATCH-406</a> - Area charts only show the top line in Firefox.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-414">DISPATCH-414</a> - Deleting a ProxyListener from dispatch-console segfaults the router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-416">DISPATCH-416</a> - Connecting the dispatch-console to wrong host displays incomplete error message</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-417">DISPATCH-417</a> - "There are no policyStatss" in dispatch-console</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-418">DISPATCH-418</a> - Deleting an address in the dispatch-console does not work</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-425">DISPATCH-425</a> - Tree on the left side gets rerendered when navigating in dispatch-console preferences</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-426">DISPATCH-426</a> - The left tree view in Overview tab allows opening multiple branches at once. Tree view in Entities tab behives like accordeon.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-431">DISPATCH-431</a> - Do not link to http://127.0.0.1:8080/dispatch-plugin</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-435">DISPATCH-435</a> - Dragging a node to a corner on the topology screen leads to a visual disconnect between the node and its link</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-436">DISPATCH-436</a> - Releasing the mouse button outside of the Topology SVG when dragging a node causes the node follow the mouse even if the mouse button is not pressed</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-439">DISPATCH-439</a> - Connect form cannot be submitted using only keyboard</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-442">DISPATCH-442</a> - system_tests_sasl_plain and system_tests_deprecated failing on Ubuntu</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-444">DISPATCH-444</a> - Add full entity type to schema</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-445">DISPATCH-445</a> - Use fullyQualifiedType from the schema when calling methods</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-449">DISPATCH-449</a> - Link-leak for attach-routed links</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-452">DISPATCH-452</a> - Prevent javascript alerts on Entities and Topology pages when new routers join network </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-453">DISPATCH-453</a> - Reserve the right column on the topology page for the legend </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-454">DISPATCH-454</a> - Legend on topology page is too tall</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-455">DISPATCH-455</a> - When autostart is checked and there is no router listening, FF generates a stream of error popups</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-456">DISPATCH-456</a> - Redirect back to connect page as soon as connection is dropped</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-457">DISPATCH-457</a> - Overview page does not update after router is added/removed from network</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-458">DISPATCH-458</a> - Batching of settlement can cause credit to be not issued to senders</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-461">DISPATCH-461</a> - [Policy] policyStats object missed being renamed to vhostStats</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-462">DISPATCH-462</a> - [Policy] Policy and vhost objects not named correctly by agent</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-463">DISPATCH-463</a> - [Policy] Remove wildcard user name description from policy doc</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-473">DISPATCH-473</a> - Deleting an SSL Profile used by a listener sometimes causes the router to crash</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-479">DISPATCH-479</a> - Use atomic operations for ref counts</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-482">DISPATCH-482</a> - trace level log messages are printing out as null</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-484">DISPATCH-484</a> - Update tree icons on overview and entities pages</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-485">DISPATCH-485</a> - All routers table on overview page is missing data</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-486">DISPATCH-486</a> - Data table on entities page has no left margin</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-487">DISPATCH-487</a> - Missing header on Quiesce button column</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-488">DISPATCH-488</a> - Provide a notification system for stand-alone console</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-489">DISPATCH-489</a> - Fetching logs entries on Entities page no longer works</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-491">DISPATCH-491</a> - Frequent skipped HELLO message from route engine</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-494">DISPATCH-494</a> - Policy objects do not support management update and delete directives</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-495">DISPATCH-495</a> - Autolinks to non-existent nodes cause problems in the router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-496">DISPATCH-496</a> - Activation of an autolink does not result in issuing credit to a blocked sender</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-498">DISPATCH-498</a> - memory leak in _configure_ssl_profile error path</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-499">DISPATCH-499</a> - in propagating link detach the info field is dropped</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-500">DISPATCH-500</a> - name in conf file is not sent in response to management query</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-501">DISPATCH-501</a> - router segfaults if you sent a management query with an empty body</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-502">DISPATCH-502</a> - Seeing unexpected values in management query response</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-505">DISPATCH-505</a> - Eventual loss of credit on inter-router control links when the topology changes</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-507">DISPATCH-507</a> - Switching between hawtio console and stand-alone causes problems</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-508">DISPATCH-508</a> - Self tests use deprecated configuration objects</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-523">DISPATCH-523</a> - Topology changes can cause in-flight deliveries to be stuck in the ingress router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-524">DISPATCH-524</a> - Unfair handling of multiple connections to the router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-532">DISPATCH-532</a> - man pages installed in wrong directory (man.X)</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-533">DISPATCH-533</a> - Router crash in the 6-node example</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-535">DISPATCH-535</a> - Use correct lifecycle management for Proton objects</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-550">DISPATCH-550</a> - Assertion failure in router in larger scale networks</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-558">DISPATCH-558</a> - Remove assertions in the core agent that fail due to malformed requests</li>
+</ul>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="/security.html">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="-apache-feather" width="48" height="14" src="" alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2015
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; 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
+ </p>
+ </div>
+ </div>
+ </div>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-master/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/index.html b/content/releases/qpid-dispatch-master/index.html
index 4898dc5..254725f 100644
--- a/content/releases/qpid-dispatch-master/index.html
+++ b/content/releases/qpid-dispatch-master/index.html
@@ -121,7 +121,7 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<h2 id="warning-this-is-a-snapshot-of-work-in-progress">Warning! This is a snapshot of work in progress</h2>
<p>Code and documentation found here may be unstable, incorrect, or
-incomplete. For a smoother experience, see the <a href="/releases/qpid-dispatch-0.6.1/index.html">current stable
+incomplete. For a smoother experience, see the <a href="/releases/qpid-dispatch-0.7.0/index.html">current stable
release</a>.</p>
<p>This content was generated at 09:51 on Monday, 08 August 2016.</p>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/_transom_config.py
----------------------------------------------------------------------
diff --git a/input/_transom_config.py b/input/_transom_config.py
index bd55584..6691fb5 100644
--- a/input/_transom_config.py
+++ b/input/_transom_config.py
@@ -21,7 +21,7 @@ qpid_release = _Release("Qpid", "qpid", "0.32")
cpp_release = _Release("Qpid C++", "qpid-cpp", "1.35.0")
python_release = _Release("Qpid Python", "qpid-python", "1.35.0")
-dispatch_release = _Release("Qpid Dispatch", "qpid-dispatch", "0.6.1")
+dispatch_release = _Release("Qpid Dispatch", "qpid-dispatch", "0.7.0")
java_release = _Release("Qpid for Java", "qpid-java", "6.1.0")
jms_release = _Release("Qpid JMS", "qpid-jms", "0.11.1")
proton_release = _Release("Qpid Proton", "qpid-proton", "0.15.0")
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console1.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console1.png b/input/releases/qpid-dispatch-0.7.0/_images/console1.png
new file mode 100644
index 0000000..f131884
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console1.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console_charts.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console_charts.png b/input/releases/qpid-dispatch-0.7.0/_images/console_charts.png
new file mode 100644
index 0000000..169c2ca
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console_charts.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console_entity.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console_entity.png b/input/releases/qpid-dispatch-0.7.0/_images/console_entity.png
new file mode 100644
index 0000000..130c7e7
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console_entity.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console_login.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console_login.png b/input/releases/qpid-dispatch-0.7.0/_images/console_login.png
new file mode 100644
index 0000000..63e22c6
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console_login.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console_overview.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console_overview.png b/input/releases/qpid-dispatch-0.7.0/_images/console_overview.png
new file mode 100644
index 0000000..af25f36
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console_overview.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console_schema.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console_schema.png b/input/releases/qpid-dispatch-0.7.0/_images/console_schema.png
new file mode 100644
index 0000000..ba56c7b
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console_schema.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/input/releases/qpid-dispatch-0.7.0/_images/console_topology.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.7.0/_images/console_topology.png b/input/releases/qpid-dispatch-0.7.0/_images/console_topology.png
new file mode 100644
index 0000000..ae4b22a
Binary files /dev/null and b/input/releases/qpid-dispatch-0.7.0/_images/console_topology.png differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[4/6] qpid-site git commit: NO-JIRA - Updating documentation for Qpid
Dispatch Router version 0.7.0
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console_charts.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console_charts.png b/content/releases/qpid-dispatch-0.7.0/book/console_charts.png
new file mode 100755
index 0000000..169c2ca
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console_charts.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console_entity.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console_entity.png b/content/releases/qpid-dispatch-0.7.0/book/console_entity.png
new file mode 100755
index 0000000..130c7e7
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console_entity.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console_login.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console_login.png b/content/releases/qpid-dispatch-0.7.0/book/console_login.png
new file mode 100755
index 0000000..63e22c6
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console_login.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console_overview.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console_overview.png b/content/releases/qpid-dispatch-0.7.0/book/console_overview.png
new file mode 100755
index 0000000..af25f36
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console_overview.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console_schema.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console_schema.png b/content/releases/qpid-dispatch-0.7.0/book/console_schema.png
new file mode 100755
index 0000000..ba56c7b
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console_schema.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/book/console_topology.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/book/console_topology.png b/content/releases/qpid-dispatch-0.7.0/book/console_topology.png
new file mode 100755
index 0000000..ae4b22a
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/book/console_topology.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/index.html b/content/releases/qpid-dispatch-0.7.0/index.html
new file mode 100644
index 0000000..8a7767c
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/index.html
@@ -0,0 +1,206 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>Qpid Dispatch 0.7.0 - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li>Qpid Dispatch 0.7.0</li></ul>
+
+ <div id="-middle-content">
+ <h1 id="qpid-dispatch-070">Qpid Dispatch 0.7.0</h1>
+
+<p>Dispatch is a lightweight AMQP message router library. More about
+<a href="/components/dispatch-router/index.html">Qpid
+Dispatch</a>.</p>
+
+<p>For a detailed list of the changes in this release, see the <a href="release-notes.html">release
+notes</a>.</p>
+
+<h2 id="downloads">Downloads</h2>
+
+<p>It's important to <a href="/download.html#verify-what-you-download">verify the
+integrity</a> of
+the files you download.</p>
+
+<table>
+<thead>
+<tr>
+ <th>Content</th>
+ <th>Download</th>
+ <th>Verify</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+ <td>Dispatch router</td>
+ <td><a href="http://archive.apache.org/dist/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz">qpid-dispatch-0.7.0.tar.gz</a></td>
+ <td><a href="http://archive.apache.org/dist/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz.asc">PGP</a></td>
+</tr>
+</tbody>
+</table>
+
+<h2 id="documentation">Documentation</h2>
+
+<div class="two-column">
+
+<ul>
+<li><a href="https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;a=blob_plain;f=README;hb=0.7.x">Installing Qpid Dispatch</a></li>
+<li><a href="book/book.html">Dispatch Router User Guide</a></li>
+<li><a href="man/qdrouterd.html">qdrouterd</a> - Router daemon</li>
+<li><a href="man/qdrouterd.conf.html">qdrouterd.conf</a> - Daemon configuration</li>
+<li><a href="man/qdstat.html">qdstat</a> - Get router statistics</li>
+<li><a href="man/qdmanage.html">qdmanage</a> - Manage the router</li>
+</ul>
+
+</div>
+
+<h2 id="more-information">More information</h2>
+
+<ul>
+<li><a href="http://archive.apache.org/dist/qpid/dispatch/0.7.0">All release artefacts</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project+%3D+DISPATCH+AND+fixVersion+%3D+%270.7.0%27+AND+resolution+%3D+%27fixed%27+ORDER+BY+priority+DESC">Resolved issues in JIRA</a></li>
+<li><a href="https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git/tree/refs/tags/0.7.0">Source repository tag</a></li>
+</ul>
+
+<script type="text/javascript">
+ _deferredFunctions.push(function() {
+ if ("0.7.0" === "0.7.0") {
+ _modifyCurrentReleaseLinks();
+ }
+ });
+</script>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="/security.html">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="-apache-feather" width="48" height="14" src="" alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2015
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; 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
+ </p>
+ </div>
+ </div>
+ </div>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/man/qdmanage.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/man/qdmanage.html b/content/releases/qpid-dispatch-0.7.0/man/qdmanage.html
new file mode 100644
index 0000000..1f1ec27
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/man/qdmanage.html
@@ -0,0 +1,389 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>SYNOPSIS - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.7.0/index.html">Qpid Dispatch 0.7.0</a></li><li>SYNOPSIS</li></ul>
+
+ <div id="-middle-content">
+ <div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdmanage</strong> [<em>OPTIONS</em>] <em>OPERATION</em> [<em>ARGUMENTS</em>]</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>An AMQP management client for use with qdrouterd. Sends AMQP management
+operations requests and prints the response in JSON format. This is a
+generic AMQP management tool and can be used with any standard AMQP
+managed endpoint, not just with qdrouter.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options">OPTIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>-h, --help
+: show this help message and exit</p></div>
+<div class="paragraph"><p>--version
+: Print version and exit.</p></div>
+<div class="paragraph"><p>--type=TYPE
+: Type of entity to operate on.</p></div>
+<div class="paragraph"><p>--name=NAME
+: Name of entity to operate on.</p></div>
+<div class="paragraph"><p>--identity=ID
+: Identity of entity to operate on.</p></div>
+<div class="paragraph"><p>--indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print</p></div>
+<div class="paragraph"><p>--stdin
+: Read attributes as JSON map or list of maps from</p></div>
+<div class="paragraph"><p>--body=BODY
+: JSON value to use as body of a non-standard operation</p></div>
+<div class="paragraph"><p>--properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p></div>
+<div class="sect2">
+<h3 id="_connection_options">Connection Options</h3>
+<div class="paragraph"><p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default</p></div>
+<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p></div>
+<div class="paragraph"><p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p></div>
+<div class="paragraph"><p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p></div>
+<div class="paragraph"><p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--ssl-password-file=SSL-PASSWORD-FILE
+: Certificate password, will be prompted if not specifed.</p></div>
+<div class="paragraph"><p>--sasl-mechanisms=SASL-MECHANISMS
+: Allowed sasl mechanisms to be supplied during the sasl handshake.</p></div>
+<div class="paragraph"><p>--sasl-username=SASL-USERNAME
+: User name for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password=SASL-PASSWORD
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--sasl-password-file=SASL-PASSWORD-FILE
+: Password for SASL plain authentication</p></div>
+<div class="paragraph"><p>--ssl-disable-peer-name-verify
+: Disables SSL peer name verification. WARNING - This option is insecure and must not be used in production environments</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_operations">OPERATIONS</h2>
+<div class="sectionbody">
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<code>query</code> [<em>ATTR</em>…]
+</dt>
+<dd>
+<p>
+ Print attributes for multiple entities. Prints all entities by default, use
+ --type, --name or --identity options to restrict which entities are printed.
+ Prints the attributes named in the ATTR list, or all attributes if none are
+ listed.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>create</code> [<em>ATTR=VALUE</em>…]
+</dt>
+<dd>
+<p>
+ Create a new entity with the specified attributes. With the --stdin
+ option, read attributes from stdin. This can be a JSON map of
+ attributes to create a single entity, or a JSON list of maps to create
+ multiple entities.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>read</code>
+</dt>
+<dd>
+<p>
+ Print all the attributes of a single entity, specified by the --name or
+ --identity options.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>update</code> [<em>ATTR=VALUE</em>…]
+</dt>
+<dd>
+<p>
+ Update the attributes of an existing entity. If an ATTR name is listed with
+ no =VALUE, that attribute will be deleted from the entity. With the --stdin
+ option, read attributes from stdin. This can be a JSON map of attributes to
+ update a single entity, or a JSON list of maps to update multiple entities.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>delete</code>
+</dt>
+<dd>
+<p>
+ Delete an entity specified by the --name or --identity options.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-types</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their base types. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-operations</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their operations. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-attributes</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their attributes. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-annotations</code> [<em>TYPE</em>]
+</dt>
+<dd>
+<p>
+ List entity types with their annotations. With no arguments list all
+ types.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-mgmt-nodes</code>
+</dt>
+<dd>
+<p>
+ List all other known management nodes connected to this one.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-json-schema</code> [<em>INDENT</em>]
+</dt>
+<dd>
+<p>
+ Get the router schema in JSON format. Optional integer indent for
+ formatted output.
+</p>
+</dd>
+<dt class="hdlist1">
+<code>get-log</code> [<em>INDENT</em>]
+</dt>
+<dd>
+<p>
+ Get recent log entries from the router.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_files">FILES</h2>
+<div class="sectionbody">
+<div class="dlist"><dl>
+<dt class="hdlist1">
+/usr/local/share/doc/qpid-dispatch/qdrouter.json
+</dt>
+<dd>
+<p>
+ Management schema for qdrouterd.
+</p>
+</dd>
+<dt class="hdlist1">
+/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt
+</dt>
+<dd>
+<p>
+ Explanation of the management schema.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_examples">EXAMPLES</h2>
+<div class="sectionbody">
+<div class="listingblock">
+<div class="title">Show the logging configuration</div>
+<div class="content">
+<pre><code>qdmanage query --type=log</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Enable debug and higher log messages by default:</div>
+<div class="content">
+<pre><code>qdmanage update name=log/DEFAULT enable=debug+</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Enable trace log messages only for the MESSAGE module and direct MESSAGE logs to the file "test.log"</div>
+<div class="content">
+<pre><code>qdmanage update name=log/MESSAGE enable=trace output=test.log</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Set MESSAGE logging back to the default</div>
+<div class="content">
+<pre><code>qdmanage update name=log/MESSAGE enable=default</code></pre>
+</div></div>
+<div class="listingblock">
+<div class="title">Disable MESSAGE logging</div>
+<div class="content">
+<pre><code>qdmanage update name=log/MESSAGE enable=none</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="/security.html">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="-apache-feather" width="48" height="14" src="" alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2015
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; 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
+ </p>
+ </div>
+ </div>
+ </div>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html b/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html
new file mode 100644
index 0000000..5a8c0f5
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html
@@ -0,0 +1,1164 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>SYNOPSIS - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.7.0/index.html">Qpid Dispatch 0.7.0</a></li><li>SYNOPSIS</li></ul>
+
+ <div id="-middle-content">
+ <div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Provides the initial configuration when <em>qdrouterd(8)</em> starts. The configuration
+of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The configuration file is made up of sections with this syntax:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>sectionName {
+ attributeName: attributeValue
+ attributeName: attributeValue
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>For example you can define a router using the <em>router</em> section</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>router {
+ mode: standalone
+ id: Router.A
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>or define a listener using the <em>listener</em> section</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>listener {
+ host: 0.0.0.0
+ port: 20102
+ saslMechanisms: ANONYMOUS
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>or define a connector using the <em>connector</em> section</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>connector {
+ role: inter-router
+ host: 0.0.0.0
+ port: 20003
+ saslMechanisms: ANONYMOUS
+ ...
+}</code></pre>
+</div></div>
+<div class="paragraph"><p>An <em>sslProfile</em> section with SSL credentials can be included in multiple <em>listener</em> or <em>connector</em> entities. Here’s an example, note
+how the <em>sslProfile</em> attribute of <em>listener</em> sections references the <em>name</em>
+attribute of <em>sslProfile</em> sections.</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>sslProfile {
+ name: my-ssl
+ certDb: ca-certificate-1.pem
+ certFile: server-certificate-1.pem
+ keyFile: server-private-key.pem
+}
+
+listener {
+ sslProfile: my-ssl
+ host: 0.0.0.0
+ port: 20102
+ saslMechanisms: ANONYMOUS
+}</code></pre>
+</div></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration_sections">Configuration Sections</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_router">router</h3>
+<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>id</em> (string)
+</dt>
+<dd>
+<p>
+ Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>)
+</dt>
+<dd>
+<p>
+ In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloInterval</em> (integer, default=1)
+</dt>
+<dd>
+<p>
+ Interval in seconds between HELLO messages sent to neighbor routers.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>helloMaxAge</em> (integer, default=3)
+</dt>
+<dd>
+<p>
+ Time in seconds after which a neighbor is declared lost if no HELLO is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raInterval</em> (integer, default=30)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers in a stable network.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>raIntervalFlux</em> (integer, default=4)
+</dt>
+<dd>
+<p>
+ Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>remoteLsMaxAge</em> (integer, default=60)
+</dt>
+<dd>
+<p>
+ Time in seconds after which link state is declared stale if no RA is received.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>workerThreads</em> (integer, default=4)
+</dt>
+<dd>
+<p>
+ The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
+</p>
+</dd>
+<dt class="hdlist1">
+<em>debugDump</em> (path)
+</dt>
+<dd>
+<p>
+ A file to dump debugging information that can’t be logged normally.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigPath</em> (path)
+</dt>
+<dd>
+<p>
+ Absolute path to the SASL configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigName</em> (string, default=<em>qdrouterd</em>)
+</dt>
+<dd>
+<p>
+ Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>routerId</em> (string)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
+</p>
+</dd>
+<dt class="hdlist1">
+<em>mobileAddrMaxAge</em> (integer, default=60)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This value is no longer used in the router.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_sslprofile">sslProfile</h3>
+<div class="paragraph"><p>Attributes for setting TLS/SSL configuration for connections.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>certDb</em> (path)
+</dt>
+<dd>
+<p>
+ The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>certFile</em> (path)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>keyFile</em> (path)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the PEM-formatted private key for the above certificate.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>passwordFile</em> (path)
+</dt>
+<dd>
+<p>
+ If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>password</em> (string)
+</dt>
+<dd>
+<p>
+ An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>uidFormat</em> (string)
+</dt>
+<dd>
+<p>
+ A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>displayNameFile</em> (string)
+</dt>
+<dd>
+<p>
+ The absolute path to the file containing the unique id to dispay name mapping
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_listener">listener</h3>
+<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>host</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ IP address: ipv4 or ipv6 literal or a host name
+</p>
+</dd>
+<dt class="hdlist1">
+<em>port</em> (string, default=<em>amqp</em>)
+</dt>
+<dd>
+<p>
+ Port number or symbolic service name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+</dt>
+<dd>
+<p>
+ [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>], default=<em>normal</em>)
+</dt>
+<dd>
+<p>
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>cost</em> (integer, default=<em>1</em>)
+</dt>
+<dd>
+<p>
+ For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>sslProfile</em> (string)
+</dt>
+<dd>
+<p>
+ Name of the sslProfile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslMechanisms</em> (string)
+</dt>
+<dd>
+<p>
+ Space separated list of accepted SASL authentication mechanisms.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>authenticatePeer</em> (boolean)
+</dt>
+<dd>
+<p>
+ yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>requireEncryption</em> (boolean)
+</dt>
+<dd>
+<p>
+ yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
+</p>
+</dd>
+<dt class="hdlist1">
+<em>requireSsl</em> (boolean)
+</dt>
+<dd>
+<p>
+ yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>trustedCerts</em> (path)
+</dt>
+<dd>
+<p>
+ This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxFrameSize</em> (integer, default=16384)
+</dt>
+<dd>
+<p>
+ Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>idleTimeoutSeconds</em> (integer, default=16)
+</dt>
+<dd>
+<p>
+ The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+</dt>
+<dd>
+<p>
+ [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+</p>
+</dd>
+<dt class="hdlist1">
+<em>linkCapacity</em> (integer)
+</dt>
+<dd>
+<p>
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>addr</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ (DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowNoSasl</em> (boolean)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>requirePeerAuth</em> (boolean)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowUnsecured</em> (boolean)
+</dt>
+<dd>
+<p>
+ (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_connector">connector</h3>
+<div class="paragraph"><p>Establishes an outgoing connection from the router.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>host</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ IP address: ipv4 or ipv6 literal or a host name
+</p>
+</dd>
+<dt class="hdlist1">
+<em>port</em> (string, default=<em>amqp</em>)
+</dt>
+<dd>
+<p>
+ Port number or symbolic service name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+</dt>
+<dd>
+<p>
+ [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>], default=<em>normal</em>)
+</dt>
+<dd>
+<p>
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>cost</em> (integer, default=<em>1</em>)
+</dt>
+<dd>
+<p>
+ For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>sslProfile</em> (string)
+</dt>
+<dd>
+<p>
+ Name of the sslProfile.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslMechanisms</em> (string)
+</dt>
+<dd>
+<p>
+ Space separated list of accepted SASL authentication mechanisms.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowRedirect</em> (boolean, default=True)
+</dt>
+<dd>
+<p>
+ Allow the peer to redirect this connection to another address.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxFrameSize</em> (integer, default=65536)
+</dt>
+<dd>
+<p>
+ Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>idleTimeoutSeconds</em> (integer, default=16)
+</dt>
+<dd>
+<p>
+ The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+</dt>
+<dd>
+<p>
+ [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+</p>
+</dd>
+<dt class="hdlist1">
+<em>linkCapacity</em> (integer)
+</dt>
+<dd>
+<p>
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>verifyHostName</em> (boolean, default=True)
+</dt>
+<dd>
+<p>
+ yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslUsername</em> (string)
+</dt>
+<dd>
+<p>
+ The user name that the connector is using to connect to a peer.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslPassword</em> (string)
+</dt>
+<dd>
+<p>
+ The password that the connector is using to connect to a peer.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>addr</em> (string, default=<em>127.0.0.1</em>)
+</dt>
+<dd>
+<p>
+ (DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_log">log</h3>
+<div class="paragraph"><p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>module</em> (One of [<em>ROUTER</em>, <em>ROUTER_CORE</em>, <em>ROUTER_HELLO</em>, <em>ROUTER_LS</em>, <em>ROUTER_MA</em>, <em>MESSAGE</em>, <em>SERVER</em>, <em>AGENT</em>, <em>CONTAINER</em>, <em>ERROR</em>, <em>POLICY</em>, <em>DEFAULT</em>], required)
+</dt>
+<dd>
+<p>
+ Module to configure. The special module <em>DEFAULT</em> specifies defaults for all modules.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>enable</em> (string)
+</dt>
+<dd>
+<p>
+ Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <em>+</em> to enable that level and above. For example <em>trace,debug,warning+</em> means enable trace, debug, warning, error and critical. The value <em>none</em> means disable logging for the module.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>timestamp</em> (boolean)
+</dt>
+<dd>
+<p>
+ Include timestamp in log messages.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>source</em> (boolean)
+</dt>
+<dd>
+<p>
+ Include source file and line number in log messages.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>output</em> (string)
+</dt>
+<dd>
+<p>
+ Where to send log messages. Can be <em>stderr</em>, <em>stdout</em>, <em>syslog</em> or a file name.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_address">address</h3>
+<div class="paragraph"><p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address prefix for the configured settings
+</p>
+</dd>
+<dt class="hdlist1">
+<em>distribution</em> (One of [<em>multicast</em>, <em>closest</em>, <em>balanced</em>], default=<em>balanced</em>)
+</dt>
+<dd>
+<p>
+ Treatment of traffic associated with the address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>waypoint</em> (boolean)
+</dt>
+<dd>
+<p>
+ Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>ingressPhase</em> (integer)
+</dt>
+<dd>
+<p>
+ Advanced - Override the ingress phase for this address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>egressPhase</em> (integer)
+</dt>
+<dd>
+<p>
+ Advanced - Override the egress phase for this address
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_linkroute">linkRoute</h3>
+<div class="paragraph"><p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address prefix for the configured settings
+</p>
+</dd>
+<dt class="hdlist1">
+<em>containerId</em> (string)
+</dt>
+<dd>
+<p>
+ ContainerID for the target container
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connection</em> (string)
+</dt>
+<dd>
+<p>
+ The name from a connector or listener
+</p>
+</dd>
+<dt class="hdlist1">
+<em>distribution</em> (One of [<em>linkBalanced</em>], default=<em>linkBalanced</em>)
+</dt>
+<dd>
+<p>
+ Treatment of traffic associated with the address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+</dt>
+<dd>
+<p>
+ The permitted direction of links: <em>in</em> means client senders; <em>out</em> means client receivers
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_autolink">autoLink</h3>
+<div class="paragraph"><p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>addr</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address of the provisioned object
+</p>
+</dd>
+<dt class="hdlist1">
+<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+</dt>
+<dd>
+<p>
+ The direction of the link to be created. In means into the router, out means out of the router.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>phase</em> (integer)
+</dt>
+<dd>
+<p>
+ The address phase for this link. Defaults to <em>0</em> for <em>out</em> links and <em>1</em> for <em>in</em> links.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>containerId</em> (string)
+</dt>
+<dd>
+<p>
+ ContainerID for the target container
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connection</em> (string)
+</dt>
+<dd>
+<p>
+ The name from a connector or listener
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_console">console</h3>
+<div class="paragraph"><p>Start a websocket/tcp proxy and http file server to serve the web console</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>listener</em> (string)
+</dt>
+<dd>
+<p>
+ The name of the listener to send the proxied tcp traffic to.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>wsport</em> (integer, default=5673)
+</dt>
+<dd>
+<p>
+ port on which to listen for websocket traffic
+</p>
+</dd>
+<dt class="hdlist1">
+<em>proxy</em> (string)
+</dt>
+<dd>
+<p>
+ The full path to the proxy program to run.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>home</em> (string)
+</dt>
+<dd>
+<p>
+ The full path to the html/css/js files for the console.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>args</em> (string)
+</dt>
+<dd>
+<p>
+ Optional args to pass the proxy program for logging, authentication, etc.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_policy">policy</h3>
+<div class="paragraph"><p>Defines global connection limit</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>maxConnections</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Global maximum number of concurrent client connections allowed. This limit is always enforced even if no other policy settings have been defined.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>enableVhostPolicy</em> (boolean)
+</dt>
+<dd>
+<p>
+ Enable vhost policy user groups, connection denial, and resource limit enforcement
+</p>
+</dd>
+<dt class="hdlist1">
+<em>policyDir</em> (path)
+</dt>
+<dd>
+<p>
+ Absolute path to a directory that holds vhost definition .json files. All vhost definitions in all .json files in this directory are processed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>defaultVhost</em> (string)
+</dt>
+<dd>
+<p>
+ Vhost rule set name to use for connections with a vhost that is otherwise not defined. Default vhost processing may be disabled either by erasing the definition of defaultVhost or by not defining a vhost object named <em>$default</em>.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_vhost">vhost</h3>
+<div class="paragraph"><p>AMQP virtual host policy definition of users, user groups, allowed remote hosts, and AMQP restrictions.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>id</em> (string, required)
+</dt>
+<dd>
+<p>
+ The vhost name.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxConnections</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Maximum number of concurrent client connections allowed.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxConnectionsPerUser</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Maximum number of concurrent client connections allowed for any single user.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>maxConnectionsPerHost</em> (integer, default=65535)
+</dt>
+<dd>
+<p>
+ Maximum number of concurrent client connections allowed for any remote host.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>allowUnknownUser</em> (boolean)
+</dt>
+<dd>
+<p>
+ Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <em>default</em> user group and receive <em>default</em> settings.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>groups</em> (map)
+</dt>
+<dd>
+<p>
+ A map where each key is a user group name and the value is a map of the corresponding settings for that group.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_container">container</h3>
+<div class="paragraph"><p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>containerName</em> (string)
+</dt>
+<dd>
+<p>
+ The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>workerThreads</em> (integer, default=4)
+</dt>
+<dd>
+<p>
+ The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
+</p>
+</dd>
+<dt class="hdlist1">
+<em>debugDump</em> (path)
+</dt>
+<dd>
+<p>
+ A file to dump debugging information that can’t be logged normally.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigPath</em> (path)
+</dt>
+<dd>
+<p>
+ Absolute path to the SASL configuration file.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>saslConfigName</em> (string)
+</dt>
+<dd>
+<p>
+ Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_waypoint">waypoint</h3>
+<div class="paragraph"><p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>address</em> (string, required)
+</dt>
+<dd>
+<p>
+ The AMQP address of the waypoint.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connector</em> (string, required)
+</dt>
+<dd>
+<p>
+ The name of the on-demand connector used to reach the waypoint’s container.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>inPhase</em> (integer, default=-1)
+</dt>
+<dd>
+<p>
+ The phase of the address as it is routed <em>to</em> the waypoint.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>outPhase</em> (integer, default=-1)
+</dt>
+<dd>
+<p>
+ The phase of the address as it is routed <em>from</em> the waypoint.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_fixedaddress">fixedAddress</h3>
+<div class="paragraph"><p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ The address prefix (always starting with <em>/</em>).
+</p>
+</dd>
+<dt class="hdlist1">
+<em>phase</em> (integer)
+</dt>
+<dd>
+<p>
+ The phase of a multi-hop address passing through one or more waypoints.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>fanout</em> (One of [<em>multiple</em>, <em>single</em>], default=<em>multiple</em>)
+</dt>
+<dd>
+<p>
+ One of <em>multiple</em> or <em>single</em>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>bias</em> (One of [<em>closest</em>, <em>spread</em>], default=<em>closest</em>)
+</dt>
+<dd>
+<p>
+ Only if fanout is single. One of <em>closest</em> or <em>spread</em>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_linkroutepattern">linkRoutePattern</h3>
+<div class="paragraph"><p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>prefix</em> (string, required)
+</dt>
+<dd>
+<p>
+ An address prefix to match against target and source addresses. This pattern must be of the form <em><text>.<text1>.<textN></em> or <em><text></em> or <em><text>.</em> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <em>org.apache</em> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
+</p>
+</dd>
+<dt class="hdlist1">
+<em>dir</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>], default=<em>both</em>)
+</dt>
+<dd>
+<p>
+ Link direction for match: <em>in</em> matches only links inbound to the client; <em>out</em> matches only links outbound from the client; <em>both</em> matches any link.
+</p>
+</dd>
+<dt class="hdlist1">
+<em>connector</em> (string)
+</dt>
+<dd>
+<p>
+ The name of the on-demand connector used to reach the target node’s container. If this value is not provided, it means that the target container is expected to be connected to a different router in the network. This prevents links to a link-routable address from being misinterpreted as message-routing links when there is no route to a valid destination available.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="/security.html">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="-apache-feather" width="48" height="14" src="" alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2015
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; 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
+ </p>
+ </div>
+ </div>
+ </div>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.html b/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.html
new file mode 100644
index 0000000..9d6897a
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.7.0/man/qdrouterd.html
@@ -0,0 +1,199 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>SYNOPSIS - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ <!-- Redirects for `go get` and godoc.org -->
+ <meta name="go-import"
+ content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/>
+ <meta name="go-source"
+ content="qpid.apache.org
+https://github.com/apache/qpid-proton/blob/go1/README.md
+https://github.com/apache/qpid-proton/tree/go1{/dir}
+https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <div class="flex">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Broker for Java</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index">Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search" method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/>
+ <button type="submit">Search</button>
+ <a href="/search.html">More ways to search</a>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.7.0/index.html">Qpid Dispatch 0.7.0</a></li><li>SYNOPSIS</li></ul>
+
+ <div id="-middle-content">
+ <div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>qdrouterd</strong> [<em>OPTIONS</em>]</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
+AMQP 1.0 messages between endpoints, such as messaging clients and
+servers.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_options">OPTIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
+: Load configuration from file at PATH</p></div>
+<div class="paragraph"><p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
+: Location of Dispatch’s Python library</p></div>
+<div class="paragraph"><p>-d, --daemon
+: Run process as a SysV-style daemon</p></div>
+<div class="paragraph"><p>-P, --pidfile
+: If daemon, the file for the stored daemon pid</p></div>
+<div class="paragraph"><p>-U, --user
+: If daemon, the username to run as</p></div>
+<div class="paragraph"><p>-v, --version
+: Print the version of Qpid Dispatch Router</p></div>
+<div class="paragraph"><p>-h, --help
+: Print this help</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_files">FILES</h2>
+<div class="sectionbody">
+<div class="dlist"><dl>
+<dt class="hdlist1">
+/usr/local/etc/qdrouterd.conf
+</dt>
+<dd>
+<p>
+ Configuration flie.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p></div>
+<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
+</div>
+</div>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="/security.html">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="-apache-feather" width="48" height="14" src="" alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2015
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; 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
+ </p>
+ </div>
+ </div>
+ </div>
+ </body>
+</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[6/6] qpid-site git commit: NO-JIRA - Updating documentation for Qpid
Dispatch Router version 0.7.0
Posted by gm...@apache.org.
NO-JIRA - Updating documentation for Qpid Dispatch Router version 0.7.0
Project: http://git-wip-us.apache.org/repos/asf/qpid-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-site/commit/09f4ae2e
Tree: http://git-wip-us.apache.org/repos/asf/qpid-site/tree/09f4ae2e
Diff: http://git-wip-us.apache.org/repos/asf/qpid-site/diff/09f4ae2e
Branch: refs/heads/asf-site
Commit: 09f4ae2e1a1d3ba47a5ae5e12254d7dc18a9ba97
Parents: 12921fa
Author: Ganesh Murthy <gm...@redhat.com>
Authored: Wed Nov 23 09:59:05 2016 -0500
Committer: Ganesh Murthy <gm...@redhat.com>
Committed: Wed Nov 23 09:59:05 2016 -0500
----------------------------------------------------------------------
content/components/dispatch-router/index.html | 14 +-
content/documentation.html | 2 +-
content/download.html | 6 +-
content/releases/qpid-dispatch-0.3/index.html | 2 +-
content/releases/qpid-dispatch-0.4/index.html | 2 +-
content/releases/qpid-dispatch-0.5/index.html | 2 +-
content/releases/qpid-dispatch-0.6.0/index.html | 2 +-
content/releases/qpid-dispatch-0.6.1/index.html | 2 +-
.../qpid-dispatch-0.7.0/_images/console1.png | Bin 0 -> 40412 bytes
.../_images/console_charts.png | Bin 0 -> 70070 bytes
.../_images/console_entity.png | Bin 0 -> 69319 bytes
.../_images/console_login.png | Bin 0 -> 39915 bytes
.../_images/console_overview.png | Bin 0 -> 87960 bytes
.../_images/console_schema.png | Bin 0 -> 68025 bytes
.../_images/console_topology.png | Bin 0 -> 67338 bytes
.../releases/qpid-dispatch-0.7.0/book/book.html | 4304 ++++++++++++++++++
.../qpid-dispatch-0.7.0/book/console1.png | Bin 0 -> 40412 bytes
.../qpid-dispatch-0.7.0/book/console_charts.png | Bin 0 -> 70070 bytes
.../qpid-dispatch-0.7.0/book/console_entity.png | Bin 0 -> 69319 bytes
.../qpid-dispatch-0.7.0/book/console_login.png | Bin 0 -> 39915 bytes
.../book/console_overview.png | Bin 0 -> 87960 bytes
.../qpid-dispatch-0.7.0/book/console_schema.png | Bin 0 -> 68025 bytes
.../book/console_topology.png | Bin 0 -> 67338 bytes
content/releases/qpid-dispatch-0.7.0/index.html | 206 +
.../qpid-dispatch-0.7.0/man/qdmanage.html | 389 ++
.../qpid-dispatch-0.7.0/man/qdrouterd.conf.html | 1164 +++++
.../qpid-dispatch-0.7.0/man/qdrouterd.html | 199 +
.../qpid-dispatch-0.7.0/man/qdstat.html | 882 ++++
.../qpid-dispatch-0.7.0/release-notes.html | 280 ++
.../releases/qpid-dispatch-master/index.html | 2 +-
input/_transom_config.py | 2 +-
.../qpid-dispatch-0.7.0/_images/console1.png | Bin 0 -> 40412 bytes
.../_images/console_charts.png | Bin 0 -> 70070 bytes
.../_images/console_entity.png | Bin 0 -> 69319 bytes
.../_images/console_login.png | Bin 0 -> 39915 bytes
.../_images/console_overview.png | Bin 0 -> 87960 bytes
.../_images/console_schema.png | Bin 0 -> 68025 bytes
.../_images/console_topology.png | Bin 0 -> 67338 bytes
.../qpid-dispatch-0.7.0/book/book.html.in | 4160 +++++++++++++++++
.../qpid-dispatch-0.7.0/book/console1.png | Bin 0 -> 40412 bytes
.../qpid-dispatch-0.7.0/book/console_charts.png | Bin 0 -> 70070 bytes
.../qpid-dispatch-0.7.0/book/console_entity.png | Bin 0 -> 69319 bytes
.../qpid-dispatch-0.7.0/book/console_login.png | Bin 0 -> 39915 bytes
.../book/console_overview.png | Bin 0 -> 87960 bytes
.../qpid-dispatch-0.7.0/book/console_schema.png | Bin 0 -> 68025 bytes
.../book/console_topology.png | Bin 0 -> 67338 bytes
input/releases/qpid-dispatch-0.7.0/index.md | 66 +
.../qpid-dispatch-0.7.0/man/qdmanage.html.in | 245 +
.../man/qdrouterd.conf.html.in | 1020 +++++
.../qpid-dispatch-0.7.0/man/qdrouterd.html.in | 55 +
.../qpid-dispatch-0.7.0/man/qdstat.html.in | 738 +++
.../qpid-dispatch-0.7.0/release-notes.md | 152 +
scripts/gen-dispatch-release-books | 20 +-
53 files changed, 13891 insertions(+), 25 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/components/dispatch-router/index.html
----------------------------------------------------------------------
diff --git a/content/components/dispatch-router/index.html b/content/components/dispatch-router/index.html
index df51591..4fafbbe 100644
--- a/content/components/dispatch-router/index.html
+++ b/content/components/dispatch-router/index.html
@@ -145,8 +145,8 @@ they be clients, brokers or other AMQP-enabled services. More about
<div class="column">
<ul>
-<li><a href="/releases/qpid-dispatch-0.6.1/book/book.html">Dispatch router book</a></li>
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;a=blob_plain;f=README;hb=0.6.1">Installing Qpid Dispatch</a></li>
+<li><a href="/releases/qpid-dispatch-0.7.0/book/book.html">Dispatch router book</a></li>
+<li><a href="https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;a=blob_plain;f=README;hb=0.7.0">Installing Qpid Dispatch</a></li>
</ul>
</div>
@@ -154,10 +154,10 @@ they be clients, brokers or other AMQP-enabled services. More about
<div class="column">
<ul>
-<li><a href="/releases/qpid-dispatch-0.6.1/man/qdrouterd.html">qdrouterd</a> - Router daemon</li>
-<li><a href="/releases/qpid-dispatch-0.6.1/man/qdrouterd.conf.html">qdrouterd.conf</a> - Daemon configuration</li>
-<li><a href="/releases/qpid-dispatch-0.6.1/man/qdstat.html">qdstat</a> - Get router statistics</li>
-<li><a href="/releases/qpid-dispatch-0.6.1/man/qdmanage.html">qdmanage</a> - Manage the router</li>
+<li><a href="/releases/qpid-dispatch-0.7.0/man/qdrouterd.html">qdrouterd</a> - Router daemon</li>
+<li><a href="/releases/qpid-dispatch-0.7.0/man/qdrouterd.conf.html">qdrouterd.conf</a> - Daemon configuration</li>
+<li><a href="/releases/qpid-dispatch-0.7.0/man/qdstat.html">qdstat</a> - Get router statistics</li>
+<li><a href="/releases/qpid-dispatch-0.7.0/man/qdmanage.html">qdmanage</a> - Manage the router</li>
</ul>
</div>
@@ -171,7 +171,7 @@ they be clients, brokers or other AMQP-enabled services. More about
<h2 id="releases">Releases</h2>
<ul>
-<li><a href="/releases/qpid-dispatch-0.6.1">Qpid Dispatch 0.6.1</a></li>
+<li><a href="/releases/qpid-dispatch-0.7.0">Qpid Dispatch 0.7.0</a></li>
<li><a href="/releases/index.html#past-releases">Past releases</a></li>
<li><a href="/releases/qpid-dispatch-master/index.html">Work in progress</a></li>
</ul>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/documentation.html
----------------------------------------------------------------------
diff --git a/content/documentation.html b/content/documentation.html
index d036c0e..d68a270 100644
--- a/content/documentation.html
+++ b/content/documentation.html
@@ -203,7 +203,7 @@ You can find older versions with our
<ul>
<li><a href="/components/dispatch-router/index.html">Overview</a></li>
-<li><a href="/releases/qpid-dispatch-0.6.1/book/book.html">Dispatch router book</a></li>
+<li><a href="/releases/qpid-dispatch-0.7.0/book/book.html">Dispatch router book</a></li>
</ul>
</section>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/download.html
----------------------------------------------------------------------
diff --git a/content/download.html b/content/download.html
index e62afc2..6016397 100644
--- a/content/download.html
+++ b/content/download.html
@@ -121,7 +121,7 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<p>Qpid's source artefacts are produced as part of our community release
process. The downloads on this page are from our current releases, <a href="/releases/qpid-proton-0.15.0">Qpid Proton 0.15.0</a>,
-<a href="/releases/qpid-dispatch-0.6.1">Qpid Dispatch 0.6.1</a>, <a href="/releases/qpid-jms-0.11.1">Qpid JMS 0.11.1</a>, <a href="/releases/qpid-java-6.1.0">Qpid for Java 6.1.0</a> and <a href="/releases/qpid-cpp-1.35.0">Qpid C++ 1.35.0</a>. You can also see our
+<a href="/releases/qpid-dispatch-0.7.0">Qpid Dispatch 0.7.0</a>, <a href="/releases/qpid-jms-0.11.1">Qpid JMS 0.11.1</a>, <a href="/releases/qpid-java-6.1.0">Qpid for Java 6.1.0</a> and <a href="/releases/qpid-cpp-1.35.0">Qpid C++ 1.35.0</a>. You can also see our
<a href="/releases/index.html#past-releases">past releases</a>.</p>
<p>It is important to <a href="#verify-what-you-download">verify the integrity</a> of the files you download.</p>
@@ -188,8 +188,8 @@ process. The downloads on this page are from our current releases, <a href="/rel
</tr>
<tr>
<td><a href="/components/dispatch-router/index.html">Dispatch router</a></td>
- <td><a href="http://www.apache.org/dyn/closer.lua/qpid/dispatch/0.6.1/qpid-dispatch-0.6.1.tar.gz">qpid-dispatch-0.6.1.tar.gz</a></td>
- <td><a href="http://www.apache.org/dist/qpid/dispatch/0.6.1/qpid-dispatch-0.6.1.tar.gz.asc">ASC</a>, <a href="http://www.apache.org/dist/qpid/dispatch/0.6.1/qpid-dispatch-0.6.1.tar.gz.sha1">SHA1</a></td>
+ <td><a href="http://www.apache.org/dyn/closer.lua/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz">qpid-dispatch-0.7.0.tar.gz</a></td>
+ <td><a href="http://www.apache.org/dist/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz.asc">ASC</a>, <a href="http://www.apache.org/dist/qpid/dispatch/0.7.0/qpid-dispatch-0.7.0.tar.gz.sha1">SHA1</a></td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.3/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.3/index.html b/content/releases/qpid-dispatch-0.3/index.html
index f21430e..1cfe97e 100644
--- a/content/releases/qpid-dispatch-0.3/index.html
+++ b/content/releases/qpid-dispatch-0.3/index.html
@@ -116,7 +116,7 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<div id="-middle-content">
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.3" === "0.6.1") {
+ if ("0.3" === "0.7.0") {
_modifyCurrentReleaseLinks();
}
});
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.4/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.4/index.html b/content/releases/qpid-dispatch-0.4/index.html
index f4d339e..dcca07d 100644
--- a/content/releases/qpid-dispatch-0.4/index.html
+++ b/content/releases/qpid-dispatch-0.4/index.html
@@ -116,7 +116,7 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<div id="-middle-content">
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.4" === "0.6.1") {
+ if ("0.4" === "0.7.0") {
_modifyCurrentReleaseLinks();
}
});
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.5/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.5/index.html b/content/releases/qpid-dispatch-0.5/index.html
index eb15a80..5b01819 100644
--- a/content/releases/qpid-dispatch-0.5/index.html
+++ b/content/releases/qpid-dispatch-0.5/index.html
@@ -171,7 +171,7 @@ the files you download.</p>
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.5" === "0.6.1") {
+ if ("0.5" === "0.7.0") {
_modifyCurrentReleaseLinks();
}
});
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.6.0/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/index.html b/content/releases/qpid-dispatch-0.6.0/index.html
index d25228d..8985796 100644
--- a/content/releases/qpid-dispatch-0.6.0/index.html
+++ b/content/releases/qpid-dispatch-0.6.0/index.html
@@ -171,7 +171,7 @@ the files you download.</p>
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.6.0" === "0.6.1") {
+ if ("0.6.0" === "0.7.0") {
_modifyCurrentReleaseLinks();
}
});
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.6.1/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.1/index.html b/content/releases/qpid-dispatch-0.6.1/index.html
index 68b15a9..e60eb9a 100644
--- a/content/releases/qpid-dispatch-0.6.1/index.html
+++ b/content/releases/qpid-dispatch-0.6.1/index.html
@@ -171,7 +171,7 @@ the files you download.</p>
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.6.1" === "0.6.1") {
+ if ("0.6.1" === "0.7.0") {
_modifyCurrentReleaseLinks();
}
});
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console1.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console1.png b/content/releases/qpid-dispatch-0.7.0/_images/console1.png
new file mode 100755
index 0000000..f131884
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console1.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console_charts.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console_charts.png b/content/releases/qpid-dispatch-0.7.0/_images/console_charts.png
new file mode 100755
index 0000000..169c2ca
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console_charts.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console_entity.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console_entity.png b/content/releases/qpid-dispatch-0.7.0/_images/console_entity.png
new file mode 100755
index 0000000..130c7e7
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console_entity.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console_login.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console_login.png b/content/releases/qpid-dispatch-0.7.0/_images/console_login.png
new file mode 100755
index 0000000..63e22c6
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console_login.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console_overview.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console_overview.png b/content/releases/qpid-dispatch-0.7.0/_images/console_overview.png
new file mode 100755
index 0000000..af25f36
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console_overview.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console_schema.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console_schema.png b/content/releases/qpid-dispatch-0.7.0/_images/console_schema.png
new file mode 100755
index 0000000..ba56c7b
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console_schema.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/09f4ae2e/content/releases/qpid-dispatch-0.7.0/_images/console_topology.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.7.0/_images/console_topology.png b/content/releases/qpid-dispatch-0.7.0/_images/console_topology.png
new file mode 100755
index 0000000..ae4b22a
Binary files /dev/null and b/content/releases/qpid-dispatch-0.7.0/_images/console_topology.png differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org