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/06/14 18:12:36 UTC
[1/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Repository: qpid-site
Updated Branches:
refs/heads/asf-site 80d07ca33 -> ac1c16638
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in
new file mode 100644
index 0000000..6e8b211
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in
@@ -0,0 +1,405 @@
+
+
+ <div class="section" id="qdrouterd-conf-manual-page">
+<h1>qdrouterd.conf manual page<a class="headerlink" href="#qdrouterd-conf-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdroutered.conf is the configuration file for the dispatch router.</p>
+</div>
+<div class="section" id="description">
+<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<p>The configuration file is made up of sections with this syntax:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>SECTION-NAME {
+ ATTRIBUTE-NAME: ATTRIBUTE-VALUE
+ ATTRIBUTE-NAME: ATTRIBUTE-VALUE
+ ...
+}
+</pre></div>
+</div>
+<p>There are two types of sections:</p>
+<p><em>Configuration sections</em> correspond to configuration entities. They can be queried and
+configured via management tools as well as via the configuration file.</p>
+<p><em>Annotation sections</em> define a group of attribute values that can be included in
+one or more entity sections.</p>
+<p>For example you can define an “ssl-profile” annotation section with SSL credentials
+that can be included in multiple “listener” entities. Here’s an example, note
+how the ‘ssl-profile’ attribute of ‘listener’ sections references the ‘name’
+attribute of ‘ssl-profile’ sections.</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>ssl-profile {
+ name: ssl-profile-one
+ cert-db: ca-certificate-1.pem
+ cert-file: server-certificate-1.pem
+ key-file: server-private-key.pem
+}
+
+listener {
+ ssl-profile: ssl-profile-one
+ host: 0.0.0.0
+ port: 20102
+ sasl-mechanisms: ANONYMOUS
+}
+</pre></div>
+</div>
+</div>
+<div class="section" id="annotation-sections">
+<h2>Annotation Sections<a class="headerlink" href="#annotation-sections" title="Permalink to this headline">.</a></h2>
+<div class="section" id="addrport">
+<h3>addrPort<a class="headerlink" href="#addrport" title="Permalink to this headline">.</a></h3>
+<p>Attributes for internet address and port.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+</dl>
+</div>
+<div class="section" id="connectionrole">
+<h3>connectionRole<a class="headerlink" href="#connectionrole" title="Permalink to this headline">.</a></h3>
+<p>Attribute for the role of a connection.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl class="docutils">
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+</dl>
+</div>
+<div class="section" id="sslprofile">
+<h3>sslProfile<a class="headerlink" href="#sslprofile" title="Permalink to this headline">.</a></h3>
+<p>Attributes for setting TLS/SSL configuration for connections.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl class="docutils">
+<dt><em>certDb</em> (path)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="configuration-sections">
+<h2>Configuration Sections<a class="headerlink" href="#configuration-sections" title="Permalink to this headline">.</a></h2>
+<div class="section" id="container">
+<h3>container<a class="headerlink" href="#container" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p>
+<dl class="docutils">
+<dt><em>containerName</em> (string)</dt>
+<dd>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.</dd>
+<dt><em>workerThreads</em> (integer, default=4)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="router">
+<h3>router<a class="headerlink" href="#router" title="Permalink to this headline">.</a></h3>
+<p>Tracks peer routers and computes routes to destinations.</p>
+<dl class="docutils">
+<dt><em>routerId</em> (string)</dt>
+<dd>(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead</dd>
+<dt><em>id</em> (string)</dt>
+<dd>Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId</dd>
+<dt><em>mode</em> (One of [‘standalone’, ‘interior’], default=’standalone’)</dt>
+<dd>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.</dd>
+<dt><em>helloInterval</em> (integer, default=1)</dt>
+<dd>Interval in seconds between HELLO messages sent to neighbor routers.</dd>
+<dt><em>helloMaxAge</em> (integer, default=3)</dt>
+<dd>Time in seconds after which a neighbor is declared lost if no HELLO is received.</dd>
+<dt><em>raInterval</em> (integer, default=30)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers in a stable network.</dd>
+<dt><em>raIntervalFlux</em> (integer, default=4)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.</dd>
+<dt><em>remoteLsMaxAge</em> (integer, default=60)</dt>
+<dd>Time in seconds after which link state is declared stale if no RA is received.</dd>
+<dt><em>mobileAddrMaxAge</em> (integer, default=60)</dt>
+<dd>(DEPRECATED) This value is no longer used in the router.</dd>
+<dt><em>workerThreads</em> (integer, default=4)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string, default=’qdrouterd’)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="listener">
+<h3>listener<a class="headerlink" href="#listener" title="Permalink to this headline">.</a></h3>
+<p>Listens for incoming connections to the router.</p>
+<p>Annotations: <strong>addrPort</strong>, <strong>connectionRole</strong>, <strong>sslProfile</strong>.</p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>saslMechanisms</em> (string)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>authenticatePeer</em> (boolean)</dt>
+<dd>yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.</dd>
+<dt><em>requireEncryption</em> (boolean)</dt>
+<dd>yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer</dd>
+<dt><em>requireSsl</em> (boolean)</dt>
+<dd>yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.</dd>
+<dt><em>trustedCerts</em> (path)</dt>
+<dd>This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide a path to a PEM file that contains the trusted certificates.</dd>
+<dt><em>maxFrameSize</em> (integer, default=16384)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16)</dt>
+<dd>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.</dd>
+<dt><em>requirePeerAuth</em> (boolean)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>allowUnsecured</em> (boolean)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the requireEncryption attribute.</dd>
+<dt><em>allowNoSasl</em> (boolean)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="connector">
+<h3>connector<a class="headerlink" href="#connector" title="Permalink to this headline">.</a></h3>
+<p>Establishes an outgoing connection from the router.</p>
+<p>Annotations: <strong>addrPort</strong>, <strong>connectionRole</strong>, <strong>sslProfile</strong>.</p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>saslMechanisms</em> (string)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>allowRedirect</em> (boolean, default=True)</dt>
+<dd>Allow the peer to redirect this connection to another address.</dd>
+<dt><em>maxFrameSize</em> (integer, default=65536)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16)</dt>
+<dd>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.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer)</dt>
+<dd>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.</dd>
+<dt><em>verifyHostName</em> (boolean, default=True)</dt>
+<dd>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</dd>
+<dt><em>saslUsername</em> (string)</dt>
+<dd>The user name that the connector is using to connect to a peer.</dd>
+<dt><em>saslPassword</em> (string)</dt>
+<dd>The password that the connector is using to connect to a peer.</dd>
+</dl>
+</div>
+<div class="section" id="log">
+<h3>log<a class="headerlink" href="#log" title="Permalink to this headline">.</a></h3>
+<p>Configure logging for a particular module. You can use the <cite>UPDATE</cite> operation to change log settings while the router is running.</p>
+<dl class="docutils">
+<dt><em>module</em> (One of [‘ROUTER’, ‘ROUTER_CORE’, ‘ROUTER_HELLO’, ‘ROUTER_LS’, ‘ROUTER_MA’, ‘MESSAGE’, ‘SERVER’, ‘AGENT’, ‘CONTAINER’, ‘CONFIG’, ‘ERROR’, ‘DISPATCH’, ‘POLICY’, ‘DEFAULT’], required)</dt>
+<dd>Module to configure. The special module ‘DEFAULT’ specifies defaults for all modules.</dd>
+<dt><em>enable</em> (string, default=’default’, required)</dt>
+<dd>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 ‘+’ to enable that level and above. For example ‘trace,debug,warning+’ means enable trace, debug, warning, error and critical. The value ‘none’ means disable logging for the module. The value ‘default’ means use the value from the DEFAULT module.</dd>
+<dt><em>timestamp</em> (boolean)</dt>
+<dd>Include timestamp in log messages.</dd>
+<dt><em>source</em> (boolean)</dt>
+<dd>Include source file and line number in log messages.</dd>
+<dt><em>output</em> (string)</dt>
+<dd>Where to send log messages. Can be ‘stderr’, ‘syslog’ or a file name.</dd>
+</dl>
+</div>
+<div class="section" id="fixedaddress">
+<h3>fixedAddress<a class="headerlink" href="#fixedaddress" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>The address prefix (always starting with ‘/’).</dd>
+<dt><em>phase</em> (integer)</dt>
+<dd>The phase of a multi-hop address passing through one or more waypoints.</dd>
+<dt><em>fanout</em> (One of [‘multiple’, ‘single’], default=’multiple’)</dt>
+<dd>One of ‘multiple’ or ‘single’. 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.</dd>
+<dt><em>bias</em> (One of [‘closest’, ‘spread’], default=’closest’)</dt>
+<dd>Only if fanout is single. One of ‘closest’ or ‘spread’. 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.</dd>
+</dl>
+</div>
+<div class="section" id="waypoint">
+<h3>waypoint<a class="headerlink" href="#waypoint" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p>
+<dl class="docutils">
+<dt><em>address</em> (string, required)</dt>
+<dd>The AMQP address of the waypoint.</dd>
+<dt><em>connector</em> (string, required)</dt>
+<dd>The name of the on-demand connector used to reach the waypoint’s container.</dd>
+<dt><em>inPhase</em> (integer, default=-1)</dt>
+<dd>The phase of the address as it is routed _to_ the waypoint.</dd>
+<dt><em>outPhase</em> (integer, default=-1)</dt>
+<dd>The phase of the address as it is routed _from_ the waypoint.</dd>
+</dl>
+</div>
+<div class="section" id="linkroutepattern">
+<h3>linkRoutePattern<a class="headerlink" href="#linkroutepattern" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>An address prefix to match against target and source addresses. This pattern must be of the form ‘<text>.<text1>.<textN>’ or ‘<text>’ or ‘<text>.’ 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 ‘org.apache’ (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</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’, ‘both’], default=’both’)</dt>
+<dd>Link direction for match: ‘in’ matches only links inbound to the client; ‘out’ matches only links outbound from the client; ‘both’ matches any link.</dd>
+<dt><em>connector</em> (string)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="address">
+<h3>address<a class="headerlink" href="#address" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>distribution</em> (One of [‘multicast’, ‘closest’, ‘balanced’], default=’balanced’)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>waypoint</em> (boolean)</dt>
+<dd>Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.</dd>
+<dt><em>ingressPhase</em> (integer)</dt>
+<dd>Advanced - Override the ingress phase for this address</dd>
+<dt><em>egressPhase</em> (integer)</dt>
+<dd>Advanced - Override the egress phase for this address</dd>
+</dl>
+</div>
+<div class="section" id="linkroute">
+<h3>linkRoute<a class="headerlink" href="#linkroute" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>containerId</em> (string)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string)</dt>
+<dd>The name from a connector or listener</dd>
+<dt><em>distribution</em> (One of [‘linkBalanced’], default=’linkBalanced’)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required)</dt>
+<dd>The permitted direction of links: ‘in’ means client senders; ‘out’ means client receivers</dd>
+</dl>
+</div>
+<div class="section" id="autolink">
+<h3>autoLink<a class="headerlink" href="#autolink" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>addr</em> (string, required)</dt>
+<dd>The address of the provisioned object</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required)</dt>
+<dd>The direction of the link to be created. In means into the router, out means out of the router.</dd>
+<dt><em>phase</em> (integer)</dt>
+<dd>The address phase for this link. Defaults to ‘0’ for ‘out’ links and ‘1’ for ‘in’ links.</dd>
+<dt><em>containerId</em> (string)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string)</dt>
+<dd>The name from a connector or listener</dd>
+</dl>
+</div>
+<div class="section" id="console">
+<h3>console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h3>
+<p>Start a websocket/tcp proxy and http file server to serve the web console</p>
+</div>
+<div class="section" id="policy">
+<h3>policy<a class="headerlink" href="#policy" title="Permalink to this headline">.</a></h3>
+<p>Defines global connection limit</p>
+<dl class="docutils">
+<dt><em>maximumConnections</em> (integer)</dt>
+<dd>Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.</dd>
+<dt><em>enableAccessRules</em> (boolean)</dt>
+<dd>Enable user rule set processing and connection denial.</dd>
+<dt><em>policyFolder</em> (path)</dt>
+<dd>The path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.</dd>
+<dt><em>defaultApplication</em> (string)</dt>
+<dd>Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.</dd>
+<dt><em>defaultApplicationEnabled</em> (boolean)</dt>
+<dd>Enable defaultApplication policy fallback logic.</dd>
+</dl>
+</div>
+<div class="section" id="policyruleset">
+<h3>policyRuleset<a class="headerlink" href="#policyruleset" title="Permalink to this headline">.</a></h3>
+<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p>
+<dl class="docutils">
+<dt><em>maxConnections</em> (integer)</dt>
+<dd>Maximum number of concurrent client connections allowed. Zero implies no limit.</dd>
+<dt><em>maxConnPerUser</em> (integer)</dt>
+<dd>Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.</dd>
+<dt><em>maxConnPerHost</em> (integer)</dt>
+<dd>Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.</dd>
+<dt><em>userGroups</em> (map)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed ‘restricted’. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.</dd>
+<dt><em>ingressHostGroups</em> (map)</dt>
+<dd>A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address ‘*’ represents any host address.</dd>
+<dt><em>ingressPolicies</em> (map)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.</dd>
+<dt><em>connectionAllowDefault</em> (boolean)</dt>
+<dd>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 ‘default’ user group and receive ‘default’ settings.</dd>
+<dt><em>settings</em> (map)</dt>
+<dd>A map where each key is a user group name and the value is a map of the corresponding settings for that group.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="see-also">
+<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in
new file mode 100644
index 0000000..e45fe2c
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in
@@ -0,0 +1,43 @@
+
+
+ <div class="section" id="qdrouterd-manual-page">
+<h1>qdrouterd manual page<a class="headerlink" href="#qdrouterd-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>SYNOPSIS<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdrouterd [<em>options</em>]</p>
+</div>
+<div class="section" id="description">
+<h2>DESCRIPTION<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<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 class="section" id="options">
+<h2>OPTIONS<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
+<p>-c, –config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
+: Load configuration from file at PATH</p>
+<p>-I, –include=PATH (/usr/local/lib/qpid-dispatch/python)
+: Location of Dispatch’s Python library</p>
+<p>-d, –daemon
+: Run process as a SysV-style daemon</p>
+<p>-P, –pidfile
+: If daemon, the file for the stored daemon pid</p>
+<p>-U, –user
+: If daemon, the username to run as</p>
+<p>-h, –help
+: Print this help</p>
+</div>
+<div class="section" id="files">
+<h2>FILES<a class="headerlink" href="#files" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt>/usr/local/etc/qdrouterd.conf</dt>
+<dd>Configuration flie.</dd>
+</dl>
+</div>
+<div class="section" id="see-also">
+<h2>SEE ALSO<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in
new file mode 100644
index 0000000..99cd510
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in
@@ -0,0 +1,273 @@
+
+
+ <div class="section" id="qdstat-manual-page">
+<h1>qdstat manual page<a class="headerlink" href="#qdstat-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdstat [options]</p>
+</div>
+<div class="section" id="description">
+<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<p><em>qdstat</em> 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 class="section" id="options">
+<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
+<p>-h, –help
+: show this help message and exit</p>
+<p>–version
+: Print version and exit.</p>
+<p>-g, –general
+: Show General Router Stats</p>
+<p>-c, –connections
+: Show Connections</p>
+<p>-l, –links
+: Show Router Links</p>
+<p>-n, –nodes
+: Show Router Nodes</p>
+<p>-a, –address
+: Show Router Addresses</p>
+<p>-m, –memory
+: Show Router Memory Stats</p>
+<p>–autolinks
+: Show Auto Links</p>
+<p>–linkroutes
+: Show Link Routes</p>
+<p>-v, –verbose
+: Show maximum detail</p>
+<p>–log
+: Show recent log entries</p>
+<p>–limit=LIMIT
+: Limit number of log entries</p>
+<div class="section" id="connection-options">
+<h3>Connection Options<a class="headerlink" href="#connection-options" title="Permalink to this headline">.</a></h3>
+<p>-b URL, –bus=URL
+: URL of the messaging bus to connect to (default</p>
+<p>-r ROUTER-ID, –router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, –timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>–ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>–ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>–ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>–ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+</div>
+</div>
+<div class="section" id="output-columns">
+<h2>Output Columns<a class="headerlink" href="#output-columns" title="Permalink to this headline">.</a></h2>
+<div class="section" id="qdstat-c">
+<h3>qdstat -c<a class="headerlink" href="#qdstat-c" title="Permalink to this headline">.</a></h3>
+<p>Id
+: Unique connection identifier</p>
+<p>host
+: The hostname or internet address of the remotely connected AMQP container</p>
+<p>container
+: The container-name of the remotely connected AMQP container</p>
+<p>role
+: The configured role of the connection</p>
+<blockquote>
+<div><ul class="simple">
+<li>normal - Normal connections from client to router</li>
+<li>inter-router - Connection between routers to form a network</li>
+<li>route-container - Connection to/from a Broker or other host to receive link-routes and waypoints</li>
+</ul>
+</div></blockquote>
+<p>dir
+: The direction of connection establishment</p>
+<blockquote>
+<div><ul class="simple">
+<li>in - The connection was initiated by the remote container</li>
+<li>out - The connection was initiated by this router</li>
+</ul>
+</div></blockquote>
+<p>security
+: A description of the security/encryption in effect for this connection</p>
+<p>authentication
+: The method and user-id of the authenticated user for this connection</p>
+</div>
+<div class="section" id="qdstat-l">
+<h3>qdstat -l<a class="headerlink" href="#qdstat-l" title="Permalink to this headline">.</a></h3>
+<p>type
+: Type of link</p>
+<blockquote>
+<div><ul class="simple">
+<li>router-control - An inter-router link that is reserved for control messages exchanged between routers</li>
+<li>inter-router - An inter-router link that is used for normal message-routed deliveries</li>
+<li>endpoint - A normal link to an external endpoint container</li>
+</ul>
+</div></blockquote>
+<p>dir
+: The direction of message flow on the link</p>
+<blockquote>
+<div><ul class="simple">
+<li>in - Deliveries flow inbound to the router</li>
+<li>out - Deliveries flow outbound from the router</li>
+</ul>
+</div></blockquote>
+<p>conn id
+: Unique identifier of the connection over which this link is attached</p>
+<p>id
+: Unique identifier of this link</p>
+<p>peer
+: For link-routed links, the unique identifier of the peer link. In link routing, an inbound link is paired with an outbound link</p>
+<p>class
+: Class of the address bound to the link</p>
+<p>addr
+: The address bound to the link</p>
+<p>phs
+: The phase of the address bound to the link</p>
+<p>cap
+: The capacity, in deliveries, of the link</p>
+<p>undel
+: The number of undelivered messages stored on the link’s FIFO</p>
+<p>unsettled
+: The number of unsettled deliveries being tracked by the link</p>
+<p>deliveries
+: The total number of deliveries that have transited this link</p>
+<p>admin
+: The administrative status of the link</p>
+<blockquote>
+<div><ul class="simple">
+<li>enabled - The link is enabled for normal operation</li>
+<li>disabled - The link is disabled and should be quiescing or stopped (not yet supported)</li>
+</ul>
+</div></blockquote>
+<p>oper
+: The operational status of the link</p>
+<blockquote>
+<div><ul class="simple">
+<li>up - The link is operational</li>
+<li>down - The link is not attached</li>
+<li>quiescing - The link is in the process of quiescing (not yet supported)</li>
+<li>idle - The link has completed quiescing and is idle (not yet supported)</li>
+</ul>
+</div></blockquote>
+<p>name
+: The link name (only shown if the -v option is provided)</p>
+</div>
+<div class="section" id="qdstat-n">
+<h3>qdstat -n<a class="headerlink" href="#qdstat-n" title="Permalink to this headline">.</a></h3>
+<p>router-id
+: Identifier of the router</p>
+<p>next-hop
+: If this router is not a neighbor, identifies the next-hop neighbor used to reach this router</p>
+<p>link
+: Unique identifier of the link to the neighbor router</p>
+<p>cost
+: The topology cost to this remote router (with -v option only)</p>
+<p>neighbors
+: The list of neighbor routers (the router’s link-state) (with -v option only)</p>
+<p>valid-origins
+: The list of origin routers for which the best path to the listed router passes through this router (with -v option only)</p>
+</div>
+<div class="section" id="qdstat-a">
+<h3>qdstat -a<a class="headerlink" href="#qdstat-a" title="Permalink to this headline">.</a></h3>
+<p>class
+: The class of the listed address</p>
+<blockquote>
+<div><ul class="simple">
+<li>local - Address that is local to this router</li>
+<li>topo - Topological address used for router control messages</li>
+<li>router - A summary router address used to route messages to a remote router’s local addresses</li>
+<li>mobile - A mobile address for an attached consumer or producer</li>
+</ul>
+</div></blockquote>
+<p>addr
+: The address text</p>
+<p>phs
+: 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>
+<p>distrib
+: Distribution method used for this address</p>
+<blockquote>
+<div><ul class="simple">
+<li>multicast - A copy of each message is delivered once to each consumer for the address</li>
+<li>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.</li>
+<li>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).</li>
+<li>flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.</li>
+</ul>
+</div></blockquote>
+<p>in-proc
+: The number of in-process consumers for this address</p>
+<p>local
+: The number of local (on this router) consumers for this address</p>
+<p>remote
+: The number of remote routers that have at least one consumer for this address</p>
+<p>cntnr
+: The number of locally attached containers that are destinations for link-routes on this address</p>
+<p>in
+: The number of deliveries for this address that entered the network on this router</p>
+<p>out
+: The number of deliveries for this address that exited the network on this router</p>
+<p>thru
+: The number of deliveries for this address that were forwarded to other routers</p>
+<p>to-proc
+: The number of deliveries for this address that were delivered to an in-process consumer</p>
+<p>from-proc
+: The number of deliveries for this address that were received from an in-process producer</p>
+</div>
+<div class="section" id="qdstat-linkroutes">
+<h3>qdstat –linkroutes<a class="headerlink" href="#qdstat-linkroutes" title="Permalink to this headline">.</a></h3>
+<p>prefix
+: The prefix for matching addresses of routed links</p>
+<p>dir
+: The direction (from the router’s perspective) of matching links</p>
+<p>distrib
+: The distribution method used for routed links</p>
+<blockquote>
+<div><ul class="simple">
+<li>linkBalanced - the only supported distribution for routed links</li>
+</ul>
+</div></blockquote>
+<p>status
+: Operational status of the link route</p>
+<blockquote>
+<div><ul class="simple">
+<li>active - Route is actively routing attaches (i.e. ready for use)</li>
+<li>inactive - Route is inactive because there is no local destination connected</li>
+</ul>
+</div></blockquote>
+</div>
+<div class="section" id="qstat-autolinks">
+<h3>qstat –autolinks<a class="headerlink" href="#qstat-autolinks" title="Permalink to this headline">.</a></h3>
+<p>addr
+: The address of the auto link</p>
+<p>dir
+: The direction of message flow for the auto link</p>
+<blockquote>
+<div><ul class="simple">
+<li>in - Messages flow in from the route-container to the router network</li>
+<li>out - Messages flow out to the route-container from the router network</li>
+</ul>
+</div></blockquote>
+<p>phs
+: Phase of the address for this auto link</p>
+<p>link
+: Unique identifier of the link managed by this auto link</p>
+<p>status
+: The operational status of this auto link</p>
+<blockquote>
+<div><ul class="simple">
+<li>inactive - There is no connected container for this auto link</li>
+<li>attaching - The link is attaching to the container</li>
+<li>failed - The link-attach failed</li>
+<li>active - The link is operational</li>
+<li>quiescing - The link is quiescing (not yet supported)</li>
+<li>idle - The link is idle (not yet supported)</li>
+</ul>
+</div></blockquote>
+<p>lastErr
+: The description of the last attach failure that occurred on this auto link</p>
+</div>
+</div>
+<div class="section" id="see-also">
+<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/release-notes.md
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/release-notes.md b/input/releases/qpid-dispatch-0.6.0/release-notes.md
new file mode 100644
index 0000000..31388fe
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/release-notes.md
@@ -0,0 +1,160 @@
+;;
+;; 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.6.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-10](https://issues.apache.org/jira/browse/DISPATCH-10) - Add link-cost for route computation
+ - [DISPATCH-57](https://issues.apache.org/jira/browse/DISPATCH-57) - Balance deliveries adaptively across all competing consumers in the network
+ - [DISPATCH-144](https://issues.apache.org/jira/browse/DISPATCH-144) - Configurable heartbeats for listeners and connectors
+ - [DISPATCH-148](https://issues.apache.org/jira/browse/DISPATCH-148) - Strip qpid-dispatch-specific message annotations on ingress/egress
+ - [DISPATCH-159](https://issues.apache.org/jira/browse/DISPATCH-159) - Enhance the address prefix used for link routing to support different patterns
+ - [DISPATCH-163](https://issues.apache.org/jira/browse/DISPATCH-163) - Add username and password for authentication of connectors
+ - [DISPATCH-164](https://issues.apache.org/jira/browse/DISPATCH-164) - Remove connector state-machine from the server module
+ - [DISPATCH-165](https://issues.apache.org/jira/browse/DISPATCH-165) - Discriminate between sending and receiving links when matching link-route patterns
+ - [DISPATCH-166](https://issues.apache.org/jira/browse/DISPATCH-166) - Use test-controlled SASL configuration for system tests
+ - [DISPATCH-170](https://issues.apache.org/jira/browse/DISPATCH-170) - qdrouterd should not require a restart after the destination broker restarts
+ - [DISPATCH-178](https://issues.apache.org/jira/browse/DISPATCH-178) - Route proton trace messages to the dispatch router log file instead of console
+ - [DISPATCH-179](https://issues.apache.org/jira/browse/DISPATCH-179) - Refactor Router Core
+ - [DISPATCH-180](https://issues.apache.org/jira/browse/DISPATCH-180) - Add a system test to test the 'linkRoutePattern' attribute of qdrouterd.conf
+ - [DISPATCH-188](https://issues.apache.org/jira/browse/DISPATCH-188) - Dispatch needs a policy mechanism to limit user connections and activity
+ - [DISPATCH-190](https://issues.apache.org/jira/browse/DISPATCH-190) - Expose the Protocol Family for the configuration of listeners and connectors
+ - [DISPATCH-193](https://issues.apache.org/jira/browse/DISPATCH-193) - Updates to the Container API
+ - [DISPATCH-194](https://issues.apache.org/jira/browse/DISPATCH-194) - Move libqpid-dispatch.so out of /lib
+ - [DISPATCH-197](https://issues.apache.org/jira/browse/DISPATCH-197) - Provide list of current link routing
+ - [DISPATCH-199](https://issues.apache.org/jira/browse/DISPATCH-199) - Add Dockerfiles that launches the dispatch router inside a container for RHEL and Debian based systems
+ - [DISPATCH-200](https://issues.apache.org/jira/browse/DISPATCH-200) - Flexible mapping from x.509 certificates to an identity
+ - [DISPATCH-203](https://issues.apache.org/jira/browse/DISPATCH-203) - Improve loop-prevention to drop messages before they are improperly forwarded
+ - [DISPATCH-217](https://issues.apache.org/jira/browse/DISPATCH-217) - Make the UI more consistant with other hawtio plugins
+ - [DISPATCH-228](https://issues.apache.org/jira/browse/DISPATCH-228) - In ctools, add a variant of DEQ_* to allow membership in multiple lists
+ - [DISPATCH-230](https://issues.apache.org/jira/browse/DISPATCH-230) - New connection role: route-container
+ - [DISPATCH-232](https://issues.apache.org/jira/browse/DISPATCH-232) - Add capability to delete listeners and connectors via the qdmanage DELETE operation
+ - [DISPATCH-242](https://issues.apache.org/jira/browse/DISPATCH-242) - Add options to qdstat to display autoLinks and linkRoutes
+ - [DISPATCH-253](https://issues.apache.org/jira/browse/DISPATCH-253) - Configurable link-capacity
+ - [DISPATCH-256](https://issues.apache.org/jira/browse/DISPATCH-256) - Documentation Updates for 0.6
+ - [DISPATCH-265](https://issues.apache.org/jira/browse/DISPATCH-265) - Improvements to Detecting Routers with Duplicate IDs
+ - [DISPATCH-277](https://issues.apache.org/jira/browse/DISPATCH-277) - Improve defaults for router configuration
+ - [DISPATCH-286](https://issues.apache.org/jira/browse/DISPATCH-286) - Prefix delimiters: allow slashes as well as periods
+ - [DISPATCH-300](https://issues.apache.org/jira/browse/DISPATCH-300) - Deprecate the ContainerEntity and move its attributes to RouterEntity
+ - [DISPATCH-303](https://issues.apache.org/jira/browse/DISPATCH-303) - Block all remote access to the "console" entity
+ - [DISPATCH-305](https://issues.apache.org/jira/browse/DISPATCH-305) - Don't tie inter-router flow credit to unsettled deliveries
+ - [DISPATCH-306](https://issues.apache.org/jira/browse/DISPATCH-306) - Deprecate addr and routerId attributes in qdrouter schema and replace them with host and id respectively
+ - [DISPATCH-331](https://issues.apache.org/jira/browse/DISPATCH-331) - Allow for a default policy to apply when open.hostname doesn't match an existing policy
+
+## Bugs fixed
+
+ - [DISPATCH-32](https://issues.apache.org/jira/browse/DISPATCH-32) - Undeliverable messages should get released.
+ - [DISPATCH-43](https://issues.apache.org/jira/browse/DISPATCH-43) - Router control messages delayed by inter-router message traffic
+ - [DISPATCH-47](https://issues.apache.org/jira/browse/DISPATCH-47) - qdrouterd doesn't know where its libraries are
+ - [DISPATCH-53](https://issues.apache.org/jira/browse/DISPATCH-53) - waypoints are not robust if targets not set up in advance.
+ - [DISPATCH-58](https://issues.apache.org/jira/browse/DISPATCH-58) - Router/Broker interaction - Unroutable/released messages are continually resent
+ - [DISPATCH-111](https://issues.apache.org/jira/browse/DISPATCH-111) - helloworld example hangs when run against a broker via link-routing
+ - [DISPATCH-126](https://issues.apache.org/jira/browse/DISPATCH-126) - Link-route behavior doesn't honor the semantics assigned to the address prefix
+ - [DISPATCH-127](https://issues.apache.org/jira/browse/DISPATCH-127) - Messages from waypoints to remote routers are not delivered
+ - [DISPATCH-155](https://issues.apache.org/jira/browse/DISPATCH-155) - Allow multiple connectors to the same broker
+ - [DISPATCH-168](https://issues.apache.org/jira/browse/DISPATCH-168) - A message sent to $management without a reply-to field causes a crash
+ - [DISPATCH-171](https://issues.apache.org/jira/browse/DISPATCH-171) - SSL Domain objects are leaked.
+ - [DISPATCH-172](https://issues.apache.org/jira/browse/DISPATCH-172) - QDStat system test never tests SASL EXTERNAL
+ - [DISPATCH-173](https://issues.apache.org/jira/browse/DISPATCH-173) - Half-closed connections spin on "writable" until they close
+ - [DISPATCH-174](https://issues.apache.org/jira/browse/DISPATCH-174) - Improper use of ref-counted object references in container
+ - [DISPATCH-175](https://issues.apache.org/jira/browse/DISPATCH-175) - Router continues to forward messages to the broker even when the broker is not available
+ - [DISPATCH-176](https://issues.apache.org/jira/browse/DISPATCH-176) - Messages sent got lost when one of the brokers went down
+ - [DISPATCH-183](https://issues.apache.org/jira/browse/DISPATCH-183) - plaintext sasl password being written to the dispatch router log
+ - [DISPATCH-191](https://issues.apache.org/jira/browse/DISPATCH-191) - router not replying to detach frame
+ - [DISPATCH-196](https://issues.apache.org/jira/browse/DISPATCH-196) - Remove endpoint mode from router documentation
+ - [DISPATCH-198](https://issues.apache.org/jira/browse/DISPATCH-198) - Message module doesn't parse AMQP-Value bodies that are strings or symbols
+ - [DISPATCH-207](https://issues.apache.org/jira/browse/DISPATCH-207) - When a message body of [ ] is sent from rhea it is rejected as an invalid body
+ - [DISPATCH-208](https://issues.apache.org/jira/browse/DISPATCH-208) - Closest semantics forwards improperly in multi-router network
+ - [DISPATCH-215](https://issues.apache.org/jira/browse/DISPATCH-215) - The topology diagram initially draws off the bottom of the visible page.
+ - [DISPATCH-218](https://issues.apache.org/jira/browse/DISPATCH-218) - Dispatch system tests run very slowly if connected to a VPN
+ - [DISPATCH-219](https://issues.apache.org/jira/browse/DISPATCH-219) - System test security configuration for installed/built tests.
+ - [DISPATCH-222](https://issues.apache.org/jira/browse/DISPATCH-222) - For Dispatch 0.6 release move up the minimum required version of qpid proton to 0.12.0
+ - [DISPATCH-223](https://issues.apache.org/jira/browse/DISPATCH-223) - Unknown connector name is not properly printed in error messages
+ - [DISPATCH-225](https://issues.apache.org/jira/browse/DISPATCH-225) - Sending UPDATE log request with relative path crashes router
+ - [DISPATCH-226](https://issues.apache.org/jira/browse/DISPATCH-226) - The default role is not applied when creating a connector
+ - [DISPATCH-231](https://issues.apache.org/jira/browse/DISPATCH-231) - Router should not issue credit for unavailable targets
+ - [DISPATCH-234](https://issues.apache.org/jira/browse/DISPATCH-234) - undeliverable-here set to true for messages from waypoints if there is no receiver
+ - [DISPATCH-237](https://issues.apache.org/jira/browse/DISPATCH-237) - Dispatch Router overwrites delivery tag for link-routed deliveries
+ - [DISPATCH-238](https://issues.apache.org/jira/browse/DISPATCH-238) - Need more documentation for qdstat output
+ - [DISPATCH-240](https://issues.apache.org/jira/browse/DISPATCH-240) - qdstat : leading "/" character effects a wrong showed address
+ - [DISPATCH-241](https://issues.apache.org/jira/browse/DISPATCH-241) - Bias "spread" config with leading "/" on address has a "multicast" behavior
+ - [DISPATCH-245](https://issues.apache.org/jira/browse/DISPATCH-245) - Various Bugs found by Coverity
+ - [DISPATCH-247](https://issues.apache.org/jira/browse/DISPATCH-247) - Policy gets username from transport
+ - [DISPATCH-248](https://issues.apache.org/jira/browse/DISPATCH-248) - Policy self test uses python features not supported by RHEL 6 (python 2.6)
+ - [DISPATCH-250](https://issues.apache.org/jira/browse/DISPATCH-250) - Router crash when deleting connector
+ - [DISPATCH-254](https://issues.apache.org/jira/browse/DISPATCH-254) - Router crash after several management requests
+ - [DISPATCH-259](https://issues.apache.org/jira/browse/DISPATCH-259) - qdstat man-page doc is no good
+ - [DISPATCH-261](https://issues.apache.org/jira/browse/DISPATCH-261) - Bind error on one port causes bind error on other ports
+ - [DISPATCH-262](https://issues.apache.org/jira/browse/DISPATCH-262) - oslo.messaging RPC fanout crashes qdrouterd
+ - [DISPATCH-263](https://issues.apache.org/jira/browse/DISPATCH-263) - Router crash when requesting log
+ - [DISPATCH-264](https://issues.apache.org/jira/browse/DISPATCH-264) - printf formats for 64-bit quantities need to be 64/32-bit safe
+ - [DISPATCH-267](https://issues.apache.org/jira/browse/DISPATCH-267) - Policy does not increment denial statistics
+ - [DISPATCH-268](https://issues.apache.org/jira/browse/DISPATCH-268) - Delivery from waypoint queue can stall when messages are released
+ - [DISPATCH-269](https://issues.apache.org/jira/browse/DISPATCH-269) - Policy denial logs at wrong level
+ - [DISPATCH-271](https://issues.apache.org/jira/browse/DISPATCH-271) - Handle single router
+ - [DISPATCH-272](https://issues.apache.org/jira/browse/DISPATCH-272) - Re-enable the connection cross-section popup
+ - [DISPATCH-273](https://issues.apache.org/jira/browse/DISPATCH-273) - The entity view is missing information for some entities
+ - [DISPATCH-275](https://issues.apache.org/jira/browse/DISPATCH-275) - Prevent javascript alert errors when navigating to console from a bookmark
+ - [DISPATCH-278](https://issues.apache.org/jira/browse/DISPATCH-278) - Deleting amqp listener using qdmanage crashes the router
+ - [DISPATCH-279](https://issues.apache.org/jira/browse/DISPATCH-279) - Policy crash when application name is null
+ - [DISPATCH-281](https://issues.apache.org/jira/browse/DISPATCH-281) - Hostname not sent in open frame on connectors
+ - [DISPATCH-282](https://issues.apache.org/jira/browse/DISPATCH-282) - Prevent topology updates when adding a new router node
+ - [DISPATCH-283](https://issues.apache.org/jira/browse/DISPATCH-283) - Start the overview page with the Router tree node expanded
+ - [DISPATCH-284](https://issues.apache.org/jira/browse/DISPATCH-284) - The management schema no longer exposes a way to associate links with their connections
+ - [DISPATCH-285](https://issues.apache.org/jira/browse/DISPATCH-285) - qdmanage returns an empty list when you QUERY for certain entities
+ - [DISPATCH-287](https://issues.apache.org/jira/browse/DISPATCH-287) - Policy does not allow configuration for unspecified Open hostname
+ - [DISPATCH-288](https://issues.apache.org/jira/browse/DISPATCH-288) - Driver - Wakeup pipe was seen to block on read, deadlocking the driver.
+ - [DISPATCH-289](https://issues.apache.org/jira/browse/DISPATCH-289) - Unit tests failing on Solaris
+ - [DISPATCH-290](https://issues.apache.org/jira/browse/DISPATCH-290) - Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris
+ - [DISPATCH-292](https://issues.apache.org/jira/browse/DISPATCH-292) - some router.link attributes should be graphable
+ - [DISPATCH-293](https://issues.apache.org/jira/browse/DISPATCH-293) - The $ character can't be used inside a prefix for linkRoute
+ - [DISPATCH-294](https://issues.apache.org/jira/browse/DISPATCH-294) - Crash in the core-thread due to an address referencing a link on a closed connection
+ - [DISPATCH-295](https://issues.apache.org/jira/browse/DISPATCH-295) - Router aborted on assertion failed after socker closing by client
+ - [DISPATCH-298](https://issues.apache.org/jira/browse/DISPATCH-298) - router spinning on shutdown (in qdr_del_connection_ref)
+ - [DISPATCH-299](https://issues.apache.org/jira/browse/DISPATCH-299) - After policy rejects a connection queued Begin causes a crash
+ - [DISPATCH-304](https://issues.apache.org/jira/browse/DISPATCH-304) - Console PNG images not showing up in documentation
+ - [DISPATCH-309](https://issues.apache.org/jira/browse/DISPATCH-309) - Mobile addresses get the wrong distribution when mapped to remote routers
+ - [DISPATCH-310](https://issues.apache.org/jira/browse/DISPATCH-310) - Use router.id instead of container.containerName
+ - [DISPATCH-312](https://issues.apache.org/jira/browse/DISPATCH-312) - Closest distribution fails to react to loss of a remote destination
+ - [DISPATCH-319](https://issues.apache.org/jira/browse/DISPATCH-319) - Discrepancy between origin router's path and other routers' valid-origins
+ - [DISPATCH-320](https://issues.apache.org/jira/browse/DISPATCH-320) - SSL enabled connector does not do hostname verification
+ - [DISPATCH-321](https://issues.apache.org/jira/browse/DISPATCH-321) - Dispatch does not send out SASL-OUTCOME frame on sasl failure
+ - [DISPATCH-334](https://issues.apache.org/jira/browse/DISPATCH-334) - Proton sequence error during backpressure with balanced distribution
+ - [DISPATCH-335](https://issues.apache.org/jira/browse/DISPATCH-335) - link routes aren't balanced over remote routers
+ - [DISPATCH-338](https://issues.apache.org/jira/browse/DISPATCH-338) - Incorrect default distribution for addresses
+ - [DISPATCH-339](https://issues.apache.org/jira/browse/DISPATCH-339) - The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible
+ - [DISPATCH-340](https://issues.apache.org/jira/browse/DISPATCH-340) - Test inter_router_plain_over_ssl fails to find SSL connection
+ - [DISPATCH-342](https://issues.apache.org/jira/browse/DISPATCH-342) - qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}
+ - [DISPATCH-343](https://issues.apache.org/jira/browse/DISPATCH-343) - Router stops accepting connections after load from parallel senders
+ - [DISPATCH-356](https://issues.apache.org/jira/browse/DISPATCH-356) - Creating and deleting a listener on already listening port causes router to crash
+ - [DISPATCH-368](https://issues.apache.org/jira/browse/DISPATCH-368) - Router in bad state in two inter-connected routers
+
+## Tasks
+
+ - [DISPATCH-307](https://issues.apache.org/jira/browse/DISPATCH-307) - misc fixups for console plugin build
+ - [DISPATCH-308](https://issues.apache.org/jira/browse/DISPATCH-308) - console documentation needs updated
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[3/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/basic_usage.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/basic_usage.html.in b/input/releases/qpid-dispatch-0.6.0/book/basic_usage.html.in
new file mode 100644
index 0000000..323fdbf
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/basic_usage.html.in
@@ -0,0 +1,166 @@
+
+
+ <div class="section" id="basic-usage-and-examples">
+<h1>2.3. Basic Usage and Examples<a class="headerlink" href="#basic-usage-and-examples" title="Permalink to this headline">.</a></h1>
+<div class="section" id="standalone-and-interior-modes">
+<h2>2.3.1. Standalone and Interior Modes<a class="headerlink" href="#standalone-and-interior-modes" title="Permalink to this headline">.</a></h2>
+<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>
+<p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
+like the following:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<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>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+</div>
+<div class="section" id="mobile-subscribers">
+<h2>2.3.2. Mobile Subscribers<a class="headerlink" href="#mobile-subscribers" title="Permalink to this headline">.</a></h2>
+<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>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ python ./simple_recv.py -a 127.0.0.1/my-address
+</pre></div>
+</div>
+<p>This command creates a receiving link subscribed to the specified
+address. To verify the subscription:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>You can then, in a separate command window, run a sender to produce
+messages to that address:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python ./simple_send.py -a 127.0.0.1/my-address
+</pre></div>
+</div>
+</div>
+<div class="section" id="dynamic-reply-to">
+<h2>2.3.3. Dynamic Reply-To<a class="headerlink" href="#dynamic-reply-to" title="Permalink to this headline">.</a></h2>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>#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();
+}
+</pre></div>
+</div>
+<p>The equivalent program written in Python against the Proton Messenger
+API:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">proton</span> <span class="kn">import</span> <span class="n">Messenger</span><span class="p">,</span> <span class="n">Message</span>
+
+<span class="k">def</span> <span class="nf">main</span><span class="p">():</span>
+ <span class="n">host</span> <span class="o">=</span> <span class="s2">"0.0.0.0:5672"</span>
+
+ <span class="n">messenger</span> <span class="o">=</span> <span class="n">Messenger</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">start</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">route</span><span class="p">(</span><span class="s2">"amqp:/*"</span><span class="p">,</span> <span class="s2">"amqp://</span><span class="si">%s</span><span class="s2">/$1"</span> <span class="o">%</span> <span class="n">host</span><span class="p">)</span>
+ <span class="n">reply_subscription</span> <span class="o">=</span> <span class="n">messenger</span><span class="o">.</span><span class="n">subscribe</span><span class="p">(</span><span class="s2">"amqp:/#"</span><span class="p">)</span>
+ <span class="n">reply_address</span> <span class="o">=</span> <span class="n">reply_subscription</span><span class="o">.</span><span class="n">address</span>
+
+ <span class="n">request</span> <span class="o">=</span> <span class="n">Message</span><span class="p">()</span>
+ <span class="n">response</span> <span class="o">=</span> <span class="n">Message</span><span class="p">()</span>
+
+ <span class="n">request</span><span class="o">.</span><span class="n">address</span> <span class="o">=</span> <span class="s2">"amqp:/_local/$management"</span>
+ <span class="n">request</span><span class="o">.</span><span class="n">reply_to</span> <span class="o">=</span> <span class="n">reply_address</span>
+ <span class="n">request</span><span class="o">.</span><span class="n">properties</span> <span class="o">=</span> <span class="p">{</span><span class="s1">u'operation'</span> <span class="p">:</span> <span class="s1">u'DISCOVER-MGMT-NODES'</span><span class="p">,</span>
+ <span class="s1">u'type'</span> <span class="p">:</span> <span class="s1">u'org.amqp.management'</span><span class="p">,</span>
+ <span class="s1">u'name'</span> <span class="p">:</span> <span class="s1">u'self'</span><span class="p">}</span>
+
+ <span class="n">messenger</span><span class="o">.</span><span class="n">put</span><span class="p">(</span><span class="n">request</span><span class="p">)</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">send</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">recv</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">get</span><span class="p">(</span><span class="n">response</span><span class="p">)</span>
+
+ <span class="k">print</span> <span class="s2">"Response: </span><span class="si">%r</span><span class="s2">"</span> <span class="o">%</span> <span class="n">response</span><span class="o">.</span><span class="n">body</span>
+
+ <span class="n">messenger</span><span class="o">.</span><span class="n">stop</span><span class="p">()</span>
+
+<span class="n">main</span><span class="p">()</span>
+</pre></div>
+</div>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/book.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/book.html.in b/input/releases/qpid-dispatch-0.6.0/book/book.html.in
new file mode 100644
index 0000000..1f1fe66
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/book.html.in
@@ -0,0 +1,82 @@
+
+
+ <div class="section" id="qpid-dispatch-router-book">
+<h1>Qpid Dispatch Router Book<a class="headerlink" href="#qpid-dispatch-router-book" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="introduction.html">1. Introduction</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="introduction.html#overview">1.1. Overview</a></li>
+<li class="toctree-l2"><a class="reference internal" href="introduction.html#benefits">1.2. Benefits</a></li>
+<li class="toctree-l2"><a class="reference internal" href="introduction.html#features">1.3. Features</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="using.html">2. Using Qpid Dispatch</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="default_config.html">2.1. Configuration</a></li>
+<li class="toctree-l2"><a class="reference internal" href="tools.html">2.2. Tools</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="tools.html#qdstat">2.2.1. qdstat</a></li>
+<li class="toctree-l3"><a class="reference internal" href="tools.html#qdmanage">2.2.2. qdmanage</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html">2.3. Basic Usage and Examples</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="basic_usage.html#standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</a></li>
+<li class="toctree-l3"><a class="reference internal" href="basic_usage.html#mobile-subscribers">2.3.2. Mobile Subscribers</a></li>
+<li class="toctree-l3"><a class="reference internal" href="basic_usage.html#dynamic-reply-to">2.3.3. Dynamic Reply-To</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="link_routing.html">2.4. Link Routing</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="link_routing.html#configuration">2.4.1. Configuration</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html">2.5. Indirect Waypoints and Auto-Links</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="auto_links.html#queue-waypoint-example">2.5.1. Queue Waypoint Example</a></li>
+<li class="toctree-l3"><a class="reference internal" href="auto_links.html#sharded-queue-example">2.5.2. Sharded Queue Example</a></li>
+<li class="toctree-l3"><a class="reference internal" href="auto_links.html#dynamically-adding-shards">2.5.3. Dynamically Adding Shards</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="technical_details.html">3. Technical Details and Specifications</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="client_compatibility.html">3.1. Client Compatibility</a></li>
+<li class="toctree-l2"><a class="reference internal" href="addressing.html">3.2. Addressing</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="addressing.html#routing-patterns">3.2.1. Routing patterns</a></li>
+<li class="toctree-l3"><a class="reference internal" href="addressing.html#routing-mechanisms">3.2.2. Routing mechanisms</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html">3.3. AMQP Mapping</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#message-annotations">3.3.1. Message Annotations</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#source-target-capabilities">3.3.2. Source/Target Capabilities</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#dynamic-node-properties">3.3.3. Dynamic-Node-Properties</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#addresses-and-address-formats">3.3.4. Addresses and Address Formats</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="schema.html">3.4. Management Schema</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#configuration-entities">3.4.1. Configuration Entities</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operational-entities">3.4.2. Operational Entities</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#management-operations">3.4.3. Management Operations</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="console.html">4. Console</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="console_overview.html">4.1. Console overview</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_installation.html">4.2. Console installation</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="console_installation.html#prerequisites">4.2.1. Prerequisites</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_installation.html#the-console-files">4.2.2. The console files</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html">4.3. Console operation</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#logging-in-to-a-router-network">4.3.1. Logging in to a router network</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#overview-page">4.3.2. Overview page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#topology-page">4.3.3. Topology page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#list-page">4.3.4. List page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#charts-page">4.3.5. Charts page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#schema-page">4.3.6. Schema page</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/client_compatibility.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/client_compatibility.html.in b/input/releases/qpid-dispatch-0.6.0/book/client_compatibility.html.in
new file mode 100644
index 0000000..95ba509
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/client_compatibility.html.in
@@ -0,0 +1,33 @@
+
+
+ <div class="section" id="client-compatibility">
+<h1>3.1. Client Compatibility<a class="headerlink" href="#client-compatibility" title="Permalink to this headline">.</a></h1>
+<p>Dispatch Router should, in theory, work with any client that is
+compatible with AMQP 1.0. The following clients have been tested:</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="20%" />
+<col width="80%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Client</em></th>
+<th class="head"><em>Notes</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>qpid::messaging</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>Proton Reactor</td>
+<td>The Proton Reactor API is compatible with Dispatch Router.</td>
+</tr>
+<tr class="row-even"><td>Proton Messenger</td>
+<td>Messenger works with Dispatch Router.</td>
+</tr>
+</tbody>
+</table>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/console.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/console.html.in b/input/releases/qpid-dispatch-0.6.0/book/console.html.in
new file mode 100644
index 0000000..58d31d9
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/console.html.in
@@ -0,0 +1,25 @@
+
+
+ <div class="section" id="console">
+<h1>4. Console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="console_overview.html">4.1. Console overview</a></li>
+<li class="toctree-l1"><a class="reference internal" href="console_installation.html">4.2. Console installation</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="console_installation.html#prerequisites">4.2.1. Prerequisites</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_installation.html#the-console-files">4.2.2. The console files</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="console_operation.html">4.3. Console operation</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#logging-in-to-a-router-network">4.3.1. Logging in to a router network</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#overview-page">4.3.2. Overview page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#topology-page">4.3.3. Topology page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#list-page">4.3.4. List page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#charts-page">4.3.5. Charts page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#schema-page">4.3.6. Schema page</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/console_installation.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/console_installation.html.in b/input/releases/qpid-dispatch-0.6.0/book/console_installation.html.in
new file mode 100644
index 0000000..001b9a3
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/console_installation.html.in
@@ -0,0 +1,40 @@
+
+
+ <div class="section" id="console-installation">
+<h1>4.2. Console installation<a class="headerlink" href="#console-installation" title="Permalink to this headline">.</a></h1>
+<div class="section" id="prerequisites">
+<h2>4.2.1. Prerequisites<a class="headerlink" href="#prerequisites" title="Permalink to this headline">.</a></h2>
+<p>The following need to be installed before running a console:</p>
+<ul class="simple">
+<li>One or more dispatch routers. See the documentation for the dispatch router for help in starting a router network.</li>
+<li>A websockets to tcp proxy.</li>
+<li>A web server. This can be any server capable of serving static html/js/css/image files.</li>
+</ul>
+<p>To install a websockets to tcp proxy:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>sudo dnf install python-websockify
+websockify localhost:5673 localhost:5672
+</pre></div>
+</div>
+<p>This will start the proxy listening to ws traffic on port 5673 and translating it to tcp on port 5672.
+One of the routers in the network needs to have a listener configured on port 5672. That listener’s role should be ‘normal’. For example:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>listener {
+ host: 0.0.0.0
+ role: normal
+ port: amqp
+ saslMechanisms: ANONYMOUS
+}
+</pre></div>
+</div>
+</div>
+<div class="section" id="the-console-files">
+<h2>4.2.2. The console files<a class="headerlink" href="#the-console-files" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt>The files for the console are located under the console/stand-alone directory in the source tree.::</dt>
+<dd>index.html
+plugin/</dd>
+<dt>Copy these files to a directory under the the html or webapps directory of your web server. For example, for apache tomcat the files should be under webapps/dispatch. Then the console is available as::</dt>
+<dd><a class="reference external" href="http://localhost:8080/dispatch">http://localhost:8080/dispatch</a></dd>
+</dl>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/console_operation.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/console_operation.html.in b/input/releases/qpid-dispatch-0.6.0/book/console_operation.html.in
new file mode 100644
index 0000000..2058f78
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/console_operation.html.in
@@ -0,0 +1,37 @@
+
+
+ <div class="section" id="console-operation">
+<h1>4.3. Console operation<a class="headerlink" href="#console-operation" title="Permalink to this headline">.</a></h1>
+<div class="section" id="logging-in-to-a-router-network">
+<h2>4.3.1. Logging in to a router network<a class="headerlink" href="#logging-in-to-a-router-network" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_login.png" src="../_images/console_login.png" />
+<p>Enter the address of the websockets to tcp proxy that is connected to a router in the network.</p>
+<p>The Autostart checkbox, when checked, will automatically log in with the previous host:port the next time you start the console.</p>
+</div>
+<div class="section" id="overview-page">
+<h2>4.3.2. Overview page<a class="headerlink" href="#overview-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_overview.png" src="../_images/console_overview.png" />
+<p>On the overview page, aggregate information about routers, addresses, and connections is displayed.</p>
+</div>
+<div class="section" id="topology-page">
+<h2>4.3.3. Topology page<a class="headerlink" href="#topology-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_topology.png" src="../_images/console_topology.png" />
+<p>This page displays the router network in a graphical form showing how the routers are connected and information about the individual routers and links.</p>
+</div>
+<div class="section" id="list-page">
+<h2>4.3.4. List page<a class="headerlink" href="#list-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_entity.png" src="../_images/console_entity.png" />
+<p>Displays detailed information about entities such as routers, links, addresses, memory.</p>
+</div>
+<div class="section" id="charts-page">
+<h2>4.3.5. Charts page<a class="headerlink" href="#charts-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_charts.png" src="../_images/console_charts.png" />
+<p>This page displays graphs of numeric values that are on the list page.</p>
+</div>
+<div class="section" id="schema-page">
+<h2>4.3.6. Schema page<a class="headerlink" href="#schema-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_schema.png" src="../_images/console_schema.png" />
+<p>This page displays the json schema that is used to manage the router network.</p>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/console_overview.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/console_overview.html.in b/input/releases/qpid-dispatch-0.6.0/book/console_overview.html.in
new file mode 100644
index 0000000..e7b95f0
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/console_overview.html.in
@@ -0,0 +1,9 @@
+
+
+ <div class="section" id="console-overview">
+<h1>4.1. Console overview<a class="headerlink" href="#console-overview" title="Permalink to this headline">.</a></h1>
+<p>The console is an HTML based web site that displays information about a qpid dispatch router network.</p>
+<p>The console requires an HTML web server that can serve static html, javascript, style sheets, and images.</p>
+<p>The console only provides limited information about the clients that are attached to the router network and is therfore more appropriate for administrators needing to know the layout and health of the router network.</p>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/default_config.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/default_config.html.in b/input/releases/qpid-dispatch-0.6.0/book/default_config.html.in
new file mode 100644
index 0000000..edbf413
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/default_config.html.in
@@ -0,0 +1,16 @@
+
+
+ <div class="section" id="configuration">
+<h1>2.1. Configuration<a class="headerlink" href="#configuration" title="Permalink to this headline">.</a></h1>
+<p>The default configuration file is installed in
+<cite>install-prefix</cite>/etc/qpid/qdrouterd.conf. 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>
+<p>To run the router, invoke the executable: qdrouterd [-c my-config-file]</p>
+<p>For more details of the configuration file see the <cite>qdrouterd.conf(5)</cite>
+man page.</p>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/introduction.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/introduction.html.in b/input/releases/qpid-dispatch-0.6.0/book/introduction.html.in
new file mode 100644
index 0000000..45dbc25
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/introduction.html.in
@@ -0,0 +1,98 @@
+
+
+ <div class="section" id="introduction">
+<h1>1. Introduction<a class="headerlink" href="#introduction" title="Permalink to this headline">.</a></h1>
+<div class="section" id="overview">
+<h2>1.1. Overview<a class="headerlink" href="#overview" title="Permalink to this headline">.</a></h2>
+<p>The Dispatch router is an AMQP message 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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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 class="section" id="benefits">
+<h2>1.2. Benefits<a class="headerlink" href="#benefits" title="Permalink to this headline">.</a></h2>
+<p>Simplifies connectivity</p>
+<ul class="simple">
+<li>An endpoint can do all of its messaging through a single transport connection</li>
+<li>Avoid opening holes in firewalls for incoming connections</li>
+</ul>
+<p>Provides messaging connectivity where there is no TCP/IP connectivity</p>
+<ul class="simple">
+<li>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).</li>
+</ul>
+<p>Simplifies reliability</p>
+<ul class="simple">
+<li>Reliability and availability are provided using redundant topology, not server clustering</li>
+<li>Reliable end-to-end messaging without persistent stores</li>
+<li>Use a message broker only when you need store-and-forward semantics</li>
+</ul>
+</div>
+<div class="section" id="features">
+<h2>1.3. Features<a class="headerlink" href="#features" title="Permalink to this headline">.</a></h2>
+<ul class="simple">
+<li>Can be deployed stand-alone or in a network of routers
+- Supports arbitrary network topology - no restrictions on redundancy
+- Automatic route computation - adjusts quickly to changes in topology</li>
+<li>Provides remote access to brokers or other AMQP servers</li>
+<li>Security</li>
+</ul>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/link_routing.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/link_routing.html.in b/input/releases/qpid-dispatch-0.6.0/book/link_routing.html.in
new file mode 100644
index 0000000..a770baa
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/link_routing.html.in
@@ -0,0 +1,131 @@
+
+
+ <div class="section" id="link-routing">
+<h1>2.4. Link Routing<a class="headerlink" href="#link-routing" title="Permalink to this headline">.</a></h1>
+<p>This feature was introduced in Qpid Dispatch 0.4.
+This feature was significantly updated in Qpid Dispatch 0.6.</p>
+<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>
+<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>
+<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 class="highlight-python"><div class="highlight"><pre><span></span> Public Network
+ +-----------------+
+ | +-----+ |
+ | B1 | Rp | |
+ | +/--\-+ |
+ | / \ |
+ | / \ |
+ +----/--------\---+
+ / \
+ / \
+ / \
+ Private Net A / \ Private Net B
++--------------/--+ +---\-------------+
+| +---/-+ | | +--\--+ |
+| B2 | Ra | | | | Rb | C1 |
+| +-----+ | | +-----+ |
+| | | |
+| | | |
++-----------------+ +-----------------+
+</pre></div>
+</div>
+<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>
+<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>
+<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>
+<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 class="section" id="configuration">
+<h2>2.4.1. Configuration<a class="headerlink" href="#configuration" title="Permalink to this headline">.</a></h2>
+<p>Starting with the configured topology shown above, how is link-routing
+configured to support the example described above?</p>
+<p>First, router Ra needs to be told how to make a connection to the
+broker B2:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>connector {
+ name: broker
+ role: route-container
+ host: <B2-url>
+ port: <B2-port>
+ sasl-mechanisms: ANONYMOUS
+}
+</pre></div>
+</div>
+<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>
+<p>Now, the router must be configured to route certain addresses to B2:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>linkRoute {
+ prefix: b2
+ dir: in
+ connection: broker
+}
+
+linkRoute {
+ prefix: b2
+ dir: out
+ connection: broker
+}
+</pre></div>
+</div>
+<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>
+<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>
+<dl class="docutils">
+<dt>Examples of addresses that “begin with ‘b2’” include:</dt>
+<dd><ul class="first last simple">
+<li>b2</li>
+<li>b2.queues</li>
+<li>b2.queues.app1</li>
+</ul>
+</dd>
+</dl>
+<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>
+<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>
+<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>
+<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>
+
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[8/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
NO-JIRA - Adding Qpid Dispatch Router 0.6.0 release docs
Project: http://git-wip-us.apache.org/repos/asf/qpid-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-site/commit/ac1c1663
Tree: http://git-wip-us.apache.org/repos/asf/qpid-site/tree/ac1c1663
Diff: http://git-wip-us.apache.org/repos/asf/qpid-site/diff/ac1c1663
Branch: refs/heads/asf-site
Commit: ac1c166383571b3d55d8c06301cffdeca5203d40
Parents: 80d07ca
Author: Ganesh Murthy <gm...@redhat.com>
Authored: Tue Jun 14 14:12:15 2016 -0400
Committer: Ganesh Murthy <gm...@redhat.com>
Committed: Tue Jun 14 14:12:15 2016 -0400
----------------------------------------------------------------------
.../_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.6.0/book/addressing.html | 271 +++++
.../qpid-dispatch-0.6.0/book/amqp-mapping.html | 358 +++++++
.../qpid-dispatch-0.6.0/book/auto_links.html | 357 ++++++
.../qpid-dispatch-0.6.0/book/basic_usage.html | 310 ++++++
.../releases/qpid-dispatch-0.6.0/book/book.html | 226 ++++
.../book/client_compatibility.html | 177 +++
.../qpid-dispatch-0.6.0/book/console.html | 169 +++
.../book/console_installation.html | 184 ++++
.../book/console_operation.html | 181 ++++
.../book/console_overview.html | 153 +++
.../book/default_config.html | 160 +++
.../qpid-dispatch-0.6.0/book/introduction.html | 242 +++++
.../qpid-dispatch-0.6.0/book/link_routing.html | 275 +++++
.../qpid-dispatch-0.6.0/book/schema.html | 1012 ++++++++++++++++++
.../book/technical_details.html | 212 ++++
.../qpid-dispatch-0.6.0/book/tools.html | 220 ++++
.../qpid-dispatch-0.6.0/book/using.html | 176 +++
content/releases/qpid-dispatch-0.6.0/index.html | 206 ++++
.../qpid-dispatch-0.6.0/man/qdmanage.html | 283 +++++
.../qpid-dispatch-0.6.0/man/qdrouterd.conf.html | 549 ++++++++++
.../qpid-dispatch-0.6.0/man/qdrouterd.html | 187 ++++
.../qpid-dispatch-0.6.0/man/qdstat.html | 417 ++++++++
.../qpid-dispatch-0.6.0/release-notes.html | 290 +++++
.../_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.6.0/book/addressing.html.in | 127 +++
.../book/amqp-mapping.html.in | 214 ++++
.../qpid-dispatch-0.6.0/book/auto_links.html.in | 213 ++++
.../book/basic_usage.html.in | 166 +++
.../qpid-dispatch-0.6.0/book/book.html.in | 82 ++
.../book/client_compatibility.html.in | 33 +
.../qpid-dispatch-0.6.0/book/console.html.in | 25 +
.../book/console_installation.html.in | 40 +
.../book/console_operation.html.in | 37 +
.../book/console_overview.html.in | 9 +
.../book/default_config.html.in | 16 +
.../book/introduction.html.in | 98 ++
.../book/link_routing.html.in | 131 +++
.../qpid-dispatch-0.6.0/book/schema.html.in | 868 +++++++++++++++
.../book/technical_details.html.in | 68 ++
.../qpid-dispatch-0.6.0/book/tools.html.in | 76 ++
.../qpid-dispatch-0.6.0/book/using.html.in | 32 +
input/releases/qpid-dispatch-0.6.0/index.md | 66 ++
.../qpid-dispatch-0.6.0/man/qdmanage.html.in | 139 +++
.../man/qdrouterd.conf.html.in | 405 +++++++
.../qpid-dispatch-0.6.0/man/qdrouterd.html.in | 43 +
.../qpid-dispatch-0.6.0/man/qdstat.html.in | 273 +++++
.../qpid-dispatch-0.6.0/release-notes.md | 160 +++
58 files changed, 9936 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/_images/console_charts.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/_images/console_charts.png b/content/releases/qpid-dispatch-0.6.0/_images/console_charts.png
new file mode 100755
index 0000000..169c2ca
Binary files /dev/null and b/content/releases/qpid-dispatch-0.6.0/_images/console_charts.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/_images/console_entity.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/_images/console_entity.png b/content/releases/qpid-dispatch-0.6.0/_images/console_entity.png
new file mode 100755
index 0000000..130c7e7
Binary files /dev/null and b/content/releases/qpid-dispatch-0.6.0/_images/console_entity.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/_images/console_login.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/_images/console_login.png b/content/releases/qpid-dispatch-0.6.0/_images/console_login.png
new file mode 100755
index 0000000..63e22c6
Binary files /dev/null and b/content/releases/qpid-dispatch-0.6.0/_images/console_login.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/_images/console_overview.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/_images/console_overview.png b/content/releases/qpid-dispatch-0.6.0/_images/console_overview.png
new file mode 100755
index 0000000..af25f36
Binary files /dev/null and b/content/releases/qpid-dispatch-0.6.0/_images/console_overview.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/_images/console_schema.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/_images/console_schema.png b/content/releases/qpid-dispatch-0.6.0/_images/console_schema.png
new file mode 100755
index 0000000..ba56c7b
Binary files /dev/null and b/content/releases/qpid-dispatch-0.6.0/_images/console_schema.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/_images/console_topology.png
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/_images/console_topology.png b/content/releases/qpid-dispatch-0.6.0/_images/console_topology.png
new file mode 100755
index 0000000..ae4b22a
Binary files /dev/null and b/content/releases/qpid-dispatch-0.6.0/_images/console_topology.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/addressing.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/addressing.html b/content/releases/qpid-dispatch-0.6.0/book/addressing.html
new file mode 100644
index 0000000..8ea3add
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/addressing.html
@@ -0,0 +1,271 @@
+<!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>3.2. Addressing. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>3.2. Addressing.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="addressing">
+<h1>3.2. Addressing<a class="headerlink" href="#addressing" title="Permalink to this headline">.</a></h1>
+<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 <cite>to</cite>
+and <cite>reply-to</cite> fields of a message’s properties. They are also used
+during the creation of links in the <cite>address</cite> field of a <cite>source</cite> or
+a <cite>target</cite>.</p>
+<p>Addresses designate various kinds of entities in a messaging network:</p>
+<ul class="simple">
+<li>Endpoint processes that consume data or offer a service</li>
+<li>Topics that match multiple consumers to multiple producers</li>
+<li>Entities within a messaging broker:
+- Queues
+- Durable Topics
+- Exchanges</li>
+</ul>
+<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>
+<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>
+<p>Address semantics include the following considerations:</p>
+<ul class="simple">
+<li><em>Routing pattern</em> - direct, multicast, balanced</li>
+<li><em>Undeliverable action</em> - drop, hold and retry, redirect</li>
+<li><em>Reliability</em> - N destinations, etc.</li>
+</ul>
+<div class="section" id="routing-patterns">
+<h2>3.2.1. Routing patterns<a class="headerlink" href="#routing-patterns" title="Permalink to this headline">.</a></h2>
+<p>Routing patterns constrain the paths that a message can take across a
+network.</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="17%" />
+<col width="83%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Pattern</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><em>Direct</em></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><em>Multicast</em></td>
+<td>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.</td>
+</tr>
+<tr class="row-even"><td><em>Balanced</em></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="routing-mechanisms">
+<h2>3.2.2. Routing mechanisms<a class="headerlink" href="#routing-mechanisms" title="Permalink to this headline">.</a></h2>
+<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>
+<blockquote>
+<div>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.</div></blockquote>
+<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 class="section" id="message-routing">
+<h3>3.2.2.1. Message routing<a class="headerlink" href="#message-routing" title="Permalink to this headline">.</a></h3>
+<p>Message routing occurs upon delivery of a message and is done based on
+the address in the message’s <cite>to</cite> field.</p>
+<p>When a delivery arrives on an incoming link, the router extracts the
+address from the delivered message’s <cite>to</cite> 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>
+<table border="1" class="docutils">
+<colgroup>
+<col width="19%" />
+<col width="81%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Delivery</em></th>
+<th class="head"><em>Handling</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><em>pre-settled</em></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><em>unsettled</em></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html b/content/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html
new file mode 100644
index 0000000..fba0674
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html
@@ -0,0 +1,358 @@
+<!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>3.3. AMQP Mapping. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>3.3. AMQP Mapping.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="amqp-mapping">
+<h1>3.3. AMQP Mapping<a class="headerlink" href="#amqp-mapping" title="Permalink to this headline">.</a></h1>
+<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 class="section" id="message-annotations">
+<h2>3.3.1. Message Annotations<a class="headerlink" href="#message-annotations" title="Permalink to this headline">.</a></h2>
+<p>The following Message Annotation fields are defined by Dispatch Router:</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="22%" />
+<col width="19%" />
+<col width="59%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Field</em></th>
+<th class="head"><em>Type</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>x-opt-qd.ingress</td>
+<td>string</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>x-opt-qd.trace</td>
+<td>list of string</td>
+<td>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.</td>
+</tr>
+<tr class="row-even"><td>x-opt-qd.to</td>
+<td>string</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>x-opt-qd.phase</td>
+<td>integer</td>
+<td>The address-phase, if not zero, for messages flowing
+between routers.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="source-target-capabilities">
+<h2>3.3.2. Source/Target Capabilities<a class="headerlink" href="#source-target-capabilities" title="Permalink to this headline">.</a></h2>
+<p>The following Capability values are used in Sources and Targets.</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="17%" />
+<col width="83%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Capability</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>qd.router</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>qd.router-data</td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="dynamic-node-properties">
+<h2>3.3.3. Dynamic-Node-Properties<a class="headerlink" href="#dynamic-node-properties" title="Permalink to this headline">.</a></h2>
+<p>The following dynamic-node-properties are used by Dispatch in Sources.</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="22%" />
+<col width="78%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Property</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>x-opt-qd.address</td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="addresses-and-address-formats">
+<h2>3.3.4. Addresses and Address Formats<a class="headerlink" href="#addresses-and-address-formats" title="Permalink to this headline">.</a></h2>
+<p>The following AMQP addresses and address patterns are used within
+Dispatch Router.</p>
+<div class="section" id="address-patterns">
+<h3>3.3.4.1. Address Patterns<a class="headerlink" href="#address-patterns" title="Permalink to this headline">.</a></h3>
+<table border="1" class="docutils">
+<colgroup>
+<col width="37%" />
+<col width="63%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Pattern</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><cite>_local/<addr></cite></td>
+<td>An address that references a locally attached
+endpoint. Messages using this address pattern shall not
+be routed over more than one link.</td>
+</tr>
+<tr class="row-odd"><td><cite>_topo/0/<router>/<addr></cite></td>
+<td><p class="first">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="last">The ‘0’ component immediately preceding the router-id
+is a placeholder for an _area_ which may be used in
+the future if area routing is implemented.</p>
+</td>
+</tr>
+<tr class="row-even"><td><cite><addr></cite></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="supported-addresses">
+<h3>3.3.4.2. Supported Addresses<a class="headerlink" href="#supported-addresses" title="Permalink to this headline">.</a></h3>
+<table border="1" class="docutils">
+<colgroup>
+<col width="35%" />
+<col width="65%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Address</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><cite>$management</cite></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><cite>_topo/0/Router.E/$management</cite></td>
+<td>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.</td>
+</tr>
+<tr class="row-even"><td><cite>_local/qdhello</cite></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><cite>_local/qdrouter</cite></td>
+<td>The router entity in each of the connected routers. This
+address is used by a router to communicate with other
+routers in the network.</td>
+</tr>
+<tr class="row-even"><td><cite>_topo/0/Router.E/qdrouter</cite></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="section" id="implementation-of-the-amqp-management-specification">
+<h2>3.3.5. Implementation of the AMQP Management Specification<a class="headerlink" href="#implementation-of-the-amqp-management-specification" title="Permalink to this headline">.</a></h2>
+<p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
+emerging AMQP Management specification (draft 9).</p>
+<p>Differences from the specification:</p>
+<ul class="simple">
+<li>The <cite>name</cite> 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.</li>
+<li>The <cite>REGISTER</cite> and <cite>DEREGISTER</cite> operations are not implemented. The router
+automatically discovers peer routers via the router network and makes
+their management addresses available via the standard GET-MGMT-NODES
+operation.</li>
+</ul>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/auto_links.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/auto_links.html b/content/releases/qpid-dispatch-0.6.0/book/auto_links.html
new file mode 100644
index 0000000..8d6e2cc
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/auto_links.html
@@ -0,0 +1,357 @@
+<!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>2.5. Indirect Waypoints and Auto-Links. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>2.5. Indirect Waypoints and Auto-Links.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="indirect-waypoints-and-auto-links">
+<h1>2.5. Indirect Waypoints and Auto-Links<a class="headerlink" href="#indirect-waypoints-and-auto-links" title="Permalink to this headline">.</a></h1>
+<p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
+improvement on an earlier somewhat experimental feature called
+Waypoints.</p>
+<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>
+<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>
+<blockquote>
+<div><ul class="simple">
+<li>The name of the connector/listener that resulted in the connection
+of the container, or</li>
+<li>The AMQP container-id of the remote container.</li>
+</ul>
+</div></blockquote>
+<div class="section" id="queue-waypoint-example">
+<h2>2.5.1. Queue Waypoint Example<a class="headerlink" href="#queue-waypoint-example" title="Permalink to this headline">.</a></h2>
+<p>Here is an example configuration for routing messages deliveries
+through a pair of queues on a broker:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>connector {
+ name: broker
+ role: route-container
+ host: <hostname>
+ port: <port>
+ sasl-mechanisms: 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
+}
+</pre></div>
+</div>
+<p>The <em>address</em> entity identifies a namespace (queue.*) that will be
+used for routing messages through queues via autolinks. The four
+<em>autoLink</em> entities identify the head and tail of two queues on the
+broker that will be connected via auto-links.</p>
+<p>If there is no broker connected, the auto-links shall remain
+<em>inactive</em>. This can be observed by using the <em>qdstat</em> tool:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>If a broker comes online with a queue called <em>queue.first</em>, the
+auto-links will attempt to activate:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>Note that two of the auto-links are in <em>failed</em> state because the
+queue does not exist on the broker.</p>
+<p>If we now use the Qpid Proton example application <em>simple_send</em> to
+send three messages to queue.first via the router:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python simple_send.py -a 127.0.0.1/queue.first -m3
+all messages confirmed
+</pre></div>
+</div>
+<p>and then look at the address statistics on the router:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>we see that <em>queue.first</em> appears twice in the list of addresses. The
+<em>phs</em>, or phase column shows that there are two phases for the
+address. Phase ‘0’ is for routing message deliveries from producers
+to the tail of the queue (the <em>out</em> auto-link associated with the
+queue). Phase ‘1’ is for routing deliveries from the head of the
+queue to subscribed consumers.</p>
+<p>Note that three deliveries have been counted in the “in” and “out”
+columns for phase ‘0’. The “in” column represents the three messages
+that arrived from simple_send and the “out” column represents the
+three deliveries to the queue on the broker.</p>
+<p>If we now use <em>simple_recv</em> to receive three messages from this
+address:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python simple_recv_noignore.py -a 127.0.0.1:5672/queue.first -m3
+{u'sequence': int32(1)}
+{u'sequence': int32(2)}
+{u'sequence': int32(3)}
+</pre></div>
+</div>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<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 class="section" id="sharded-queue-example">
+<h2>2.5.2. Sharded Queue Example<a class="headerlink" href="#sharded-queue-example" title="Permalink to this headline">.</a></h2>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>connector {
+ name: broker1
+ role: route-container
+ host: <hostname>
+ port: <port>
+ sasl-mechanisms: ANONYMOUS
+}
+
+connector {
+ name: broker2
+ role: route-container
+ host: <hostname>
+ port: <port>
+ sasl-mechanisms: 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
+}
+</pre></div>
+</div>
+<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 class="section" id="dynamically-adding-shards">
+<h2>2.5.3. Dynamically Adding Shards<a class="headerlink" href="#dynamically-adding-shards" title="Permalink to this headline">.</a></h2>
+<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 <em>qdmanage</em>:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>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
+</pre></div>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/basic_usage.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/basic_usage.html b/content/releases/qpid-dispatch-0.6.0/book/basic_usage.html
new file mode 100644
index 0000000..60ba249
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/basic_usage.html
@@ -0,0 +1,310 @@
+<!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>2.3. Basic Usage and Examples. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>2.3. Basic Usage and Examples.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="basic-usage-and-examples">
+<h1>2.3. Basic Usage and Examples<a class="headerlink" href="#basic-usage-and-examples" title="Permalink to this headline">.</a></h1>
+<div class="section" id="standalone-and-interior-modes">
+<h2>2.3.1. Standalone and Interior Modes<a class="headerlink" href="#standalone-and-interior-modes" title="Permalink to this headline">.</a></h2>
+<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>
+<p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
+like the following:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<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>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+</div>
+<div class="section" id="mobile-subscribers">
+<h2>2.3.2. Mobile Subscribers<a class="headerlink" href="#mobile-subscribers" title="Permalink to this headline">.</a></h2>
+<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>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ python ./simple_recv.py -a 127.0.0.1/my-address
+</pre></div>
+</div>
+<p>This command creates a receiving link subscribed to the specified
+address. To verify the subscription:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>You can then, in a separate command window, run a sender to produce
+messages to that address:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python ./simple_send.py -a 127.0.0.1/my-address
+</pre></div>
+</div>
+</div>
+<div class="section" id="dynamic-reply-to">
+<h2>2.3.3. Dynamic Reply-To<a class="headerlink" href="#dynamic-reply-to" title="Permalink to this headline">.</a></h2>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>#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();
+}
+</pre></div>
+</div>
+<p>The equivalent program written in Python against the Proton Messenger
+API:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">proton</span> <span class="kn">import</span> <span class="n">Messenger</span><span class="p">,</span> <span class="n">Message</span>
+
+<span class="k">def</span> <span class="nf">main</span><span class="p">():</span>
+ <span class="n">host</span> <span class="o">=</span> <span class="s2">"0.0.0.0:5672"</span>
+
+ <span class="n">messenger</span> <span class="o">=</span> <span class="n">Messenger</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">start</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">route</span><span class="p">(</span><span class="s2">"amqp:/*"</span><span class="p">,</span> <span class="s2">"amqp://</span><span class="si">%s</span><span class="s2">/$1"</span> <span class="o">%</span> <span class="n">host</span><span class="p">)</span>
+ <span class="n">reply_subscription</span> <span class="o">=</span> <span class="n">messenger</span><span class="o">.</span><span class="n">subscribe</span><span class="p">(</span><span class="s2">"amqp:/#"</span><span class="p">)</span>
+ <span class="n">reply_address</span> <span class="o">=</span> <span class="n">reply_subscription</span><span class="o">.</span><span class="n">address</span>
+
+ <span class="n">request</span> <span class="o">=</span> <span class="n">Message</span><span class="p">()</span>
+ <span class="n">response</span> <span class="o">=</span> <span class="n">Message</span><span class="p">()</span>
+
+ <span class="n">request</span><span class="o">.</span><span class="n">address</span> <span class="o">=</span> <span class="s2">"amqp:/_local/$management"</span>
+ <span class="n">request</span><span class="o">.</span><span class="n">reply_to</span> <span class="o">=</span> <span class="n">reply_address</span>
+ <span class="n">request</span><span class="o">.</span><span class="n">properties</span> <span class="o">=</span> <span class="p">{</span><span class="s1">u'operation'</span> <span class="p">:</span> <span class="s1">u'DISCOVER-MGMT-NODES'</span><span class="p">,</span>
+ <span class="s1">u'type'</span> <span class="p">:</span> <span class="s1">u'org.amqp.management'</span><span class="p">,</span>
+ <span class="s1">u'name'</span> <span class="p">:</span> <span class="s1">u'self'</span><span class="p">}</span>
+
+ <span class="n">messenger</span><span class="o">.</span><span class="n">put</span><span class="p">(</span><span class="n">request</span><span class="p">)</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">send</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">recv</span><span class="p">()</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">get</span><span class="p">(</span><span class="n">response</span><span class="p">)</span>
+
+ <span class="k">print</span> <span class="s2">"Response: </span><span class="si">%r</span><span class="s2">"</span> <span class="o">%</span> <span class="n">response</span><span class="o">.</span><span class="n">body</span>
+
+ <span class="n">messenger</span><span class="o">.</span><span class="n">stop</span><span class="p">()</span>
+
+<span class="n">main</span><span class="p">()</span>
+</pre></div>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/book.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/book.html b/content/releases/qpid-dispatch-0.6.0/book/book.html
new file mode 100644
index 0000000..8c1fa05
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/book.html
@@ -0,0 +1,226 @@
+<!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 Router Book. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>Qpid Dispatch Router Book.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="qpid-dispatch-router-book">
+<h1>Qpid Dispatch Router Book<a class="headerlink" href="#qpid-dispatch-router-book" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="introduction.html">1. Introduction</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="introduction.html#overview">1.1. Overview</a></li>
+<li class="toctree-l2"><a class="reference internal" href="introduction.html#benefits">1.2. Benefits</a></li>
+<li class="toctree-l2"><a class="reference internal" href="introduction.html#features">1.3. Features</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="using.html">2. Using Qpid Dispatch</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="default_config.html">2.1. Configuration</a></li>
+<li class="toctree-l2"><a class="reference internal" href="tools.html">2.2. Tools</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="tools.html#qdstat">2.2.1. qdstat</a></li>
+<li class="toctree-l3"><a class="reference internal" href="tools.html#qdmanage">2.2.2. qdmanage</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html">2.3. Basic Usage and Examples</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="basic_usage.html#standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</a></li>
+<li class="toctree-l3"><a class="reference internal" href="basic_usage.html#mobile-subscribers">2.3.2. Mobile Subscribers</a></li>
+<li class="toctree-l3"><a class="reference internal" href="basic_usage.html#dynamic-reply-to">2.3.3. Dynamic Reply-To</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="link_routing.html">2.4. Link Routing</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="link_routing.html#configuration">2.4.1. Configuration</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html">2.5. Indirect Waypoints and Auto-Links</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="auto_links.html#queue-waypoint-example">2.5.1. Queue Waypoint Example</a></li>
+<li class="toctree-l3"><a class="reference internal" href="auto_links.html#sharded-queue-example">2.5.2. Sharded Queue Example</a></li>
+<li class="toctree-l3"><a class="reference internal" href="auto_links.html#dynamically-adding-shards">2.5.3. Dynamically Adding Shards</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="technical_details.html">3. Technical Details and Specifications</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="client_compatibility.html">3.1. Client Compatibility</a></li>
+<li class="toctree-l2"><a class="reference internal" href="addressing.html">3.2. Addressing</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="addressing.html#routing-patterns">3.2.1. Routing patterns</a></li>
+<li class="toctree-l3"><a class="reference internal" href="addressing.html#routing-mechanisms">3.2.2. Routing mechanisms</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html">3.3. AMQP Mapping</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#message-annotations">3.3.1. Message Annotations</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#source-target-capabilities">3.3.2. Source/Target Capabilities</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#dynamic-node-properties">3.3.3. Dynamic-Node-Properties</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#addresses-and-address-formats">3.3.4. Addresses and Address Formats</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="schema.html">3.4. Management Schema</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#configuration-entities">3.4.1. Configuration Entities</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operational-entities">3.4.2. Operational Entities</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#management-operations">3.4.3. Management Operations</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="console.html">4. Console</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="console_overview.html">4.1. Console overview</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_installation.html">4.2. Console installation</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="console_installation.html#prerequisites">4.2.1. Prerequisites</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_installation.html#the-console-files">4.2.2. The console files</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html">4.3. Console operation</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#logging-in-to-a-router-network">4.3.1. Logging in to a router network</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#overview-page">4.3.2. Overview page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#topology-page">4.3.3. Topology page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#list-page">4.3.4. List page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#charts-page">4.3.5. Charts page</a></li>
+<li class="toctree-l3"><a class="reference internal" href="console_operation.html#schema-page">4.3.6. Schema page</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</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
[2/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/schema.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/schema.html.in b/input/releases/qpid-dispatch-0.6.0/book/schema.html.in
new file mode 100644
index 0000000..5bd1239
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/schema.html.in
@@ -0,0 +1,868 @@
+
+
+ <div class="section" id="management-schema">
+<h1>3.4. Management Schema<a class="headerlink" href="#management-schema" title="Permalink to this headline">.</a></h1>
+<p>This chapter documents the set of <em>management entity types</em> that define
+configuration and management of a Dispatch Router. A management entity type has
+a set of <em>attributes</em> that can be read, some attributes can also be
+updated. Some entity types also support <em>operations</em> that can be called.</p>
+<p>All management entity types have the following standard attributes:</p>
+<dl class="docutils">
+<dt><em>type</em></dt>
+<dd>The fully qualified type of the entity,
+e.g. <cite>org.apache.qpid.dispatch.router</cite>. This document uses the short name
+without the <cite>org.apache.qpid.dispatch</cite> prefix e.g. <cite>router</cite>. The dispatch
+tools will accept the short or long name.</dd>
+<dt><em>name</em></dt>
+<dd>A user-generated identity for the entity. This can be used in other entities
+that need to refer to the named entity.</dd>
+<dt><em>identity</em></dt>
+<dd>A system-generated identity of the entity. It includes
+the short type name and some identifying information. E.g. <cite>log/AGENT</cite> or
+<cite>listener/localhost:amqp</cite></dd>
+</dl>
+<p>There are two main categories of management entity type.</p>
+<dl class="docutils">
+<dt><em>Configuration</em> Entities</dt>
+<dd>Parameters that can be set in the configuration file
+(see <cite>qdrouterd.conf(5)</cite> man page) or set at run-time with the <cite>qdmanage(8)</cite>
+tool.</dd>
+<dt><em>Operational</em> Entities</dt>
+<dd>Run-time status values that can be queried using <cite>qdstat(8)</cite> or <cite>qdmanage(8)</cite> tools.</dd>
+</dl>
+<div class="section" id="configuration-entities">
+<h2>3.4.1. Configuration Entities<a class="headerlink" href="#configuration-entities" title="Permalink to this headline">.</a></h2>
+<p>Configuration entities define the attributes allowed in the configuration file
+(see <cite>qdrouterd.conf(5)</cite>) but you can also create entities once the router is
+running using the <cite>qdrouterd(8)</cite> tool’s <cite>create</cite> operation. Some entities can also
+be modified using the <cite>update</cite> operation, see the entity descriptions below.</p>
+<div class="section" id="container">
+<h3>3.4.1.1. container<a class="headerlink" href="#container" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>containerName</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>workerThreads</em> (integer, default=4, <cite>CREATE</cite>)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path, <cite>CREATE</cite>)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path, <cite>CREATE</cite>)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="router">
+<h3>3.4.1.2. router<a class="headerlink" href="#router" title="Permalink to this headline">.</a></h3>
+<p>Tracks peer routers and computes routes to destinations.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>routerId</em> (string, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead</dd>
+<dt><em>id</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId</dd>
+<dt><em>mode</em> (One of [‘standalone’, ‘interior’], default=’standalone’, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>area</em> (string)</dt>
+<dd>Unused placeholder.</dd>
+<dt><em>helloInterval</em> (integer, default=1, <cite>CREATE</cite>)</dt>
+<dd>Interval in seconds between HELLO messages sent to neighbor routers.</dd>
+<dt><em>helloMaxAge</em> (integer, default=3, <cite>CREATE</cite>)</dt>
+<dd>Time in seconds after which a neighbor is declared lost if no HELLO is received.</dd>
+<dt><em>raInterval</em> (integer, default=30, <cite>CREATE</cite>)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers in a stable network.</dd>
+<dt><em>raIntervalFlux</em> (integer, default=4, <cite>CREATE</cite>)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.</dd>
+<dt><em>remoteLsMaxAge</em> (integer, default=60, <cite>CREATE</cite>)</dt>
+<dd>Time in seconds after which link state is declared stale if no RA is received.</dd>
+<dt><em>mobileAddrMaxAge</em> (integer, default=60, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This value is no longer used in the router.</dd>
+<dt><em>addrCount</em> (integer)</dt>
+<dd>Number of addresses known to the router.</dd>
+<dt><em>linkCount</em> (integer)</dt>
+<dd>Number of links attached to the router node.</dd>
+<dt><em>nodeCount</em> (integer)</dt>
+<dd>Number of known peer router nodes.</dd>
+<dt><em>workerThreads</em> (integer, default=4, <cite>CREATE</cite>)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path, <cite>CREATE</cite>)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path, <cite>CREATE</cite>)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string, default=’qdrouterd’, <cite>CREATE</cite>)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="listener">
+<h3>3.4.1.3. listener<a class="headerlink" href="#listener" title="Permalink to this headline">.</a></h3>
+<p>Listens for incoming connections to the router.</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’, <cite>CREATE</cite>)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’], <cite>CREATE</cite>)</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’, <cite>CREATE</cite>)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>sslProfileName</em> (string)</dt>
+<dd>The name of the ssl profile</dd>
+<dt><em>saslMechanisms</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>authenticatePeer</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.</dd>
+<dt><em>requireEncryption</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer</dd>
+<dt><em>requireSsl</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.</dd>
+<dt><em>trustedCerts</em> (path, <cite>CREATE</cite>)</dt>
+<dd>This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide a path to a PEM file that contains the trusted certificates.</dd>
+<dt><em>maxFrameSize</em> (integer, default=16384, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>requirePeerAuth</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>allowUnsecured</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the requireEncryption attribute.</dd>
+<dt><em>allowNoSasl</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’, <cite>CREATE</cite>)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="connector">
+<h3>3.4.1.4. connector<a class="headerlink" href="#connector" title="Permalink to this headline">.</a></h3>
+<p>Establishes an outgoing connection from the router.</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’, <cite>CREATE</cite>)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’], <cite>CREATE</cite>)</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’, <cite>CREATE</cite>)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>sslProfileName</em> (string)</dt>
+<dd>The name of the ssl profile</dd>
+<dt><em>saslMechanisms</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>allowRedirect</em> (boolean, default=True, <cite>CREATE</cite>)</dt>
+<dd>Allow the peer to redirect this connection to another address.</dd>
+<dt><em>maxFrameSize</em> (integer, default=65536, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’, <cite>CREATE</cite>)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>verifyHostName</em> (boolean, default=True, <cite>CREATE</cite>)</dt>
+<dd>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</dd>
+<dt><em>saslUsername</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The user name that the connector is using to connect to a peer.</dd>
+<dt><em>saslPassword</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The password that the connector is using to connect to a peer.</dd>
+</dl>
+</div>
+<div class="section" id="log">
+<h3>3.4.1.5. log<a class="headerlink" href="#log" title="Permalink to this headline">.</a></h3>
+<p>Configure logging for a particular module. You can use the <cite>UPDATE</cite> operation to change log settings while the router is running.</p>
+<p>Operations allowed: <cite>UPDATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>module</em> (One of [‘ROUTER’, ‘ROUTER_CORE’, ‘ROUTER_HELLO’, ‘ROUTER_LS’, ‘ROUTER_MA’, ‘MESSAGE’, ‘SERVER’, ‘AGENT’, ‘CONTAINER’, ‘CONFIG’, ‘ERROR’, ‘DISPATCH’, ‘POLICY’, ‘DEFAULT’], required, <cite>UPDATE</cite>)</dt>
+<dd>Module to configure. The special module ‘DEFAULT’ specifies defaults for all modules.</dd>
+<dt><em>enable</em> (string, default=’default’, required, <cite>UPDATE</cite>)</dt>
+<dd>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 ‘+’ to enable that level and above. For example ‘trace,debug,warning+’ means enable trace, debug, warning, error and critical. The value ‘none’ means disable logging for the module. The value ‘default’ means use the value from the DEFAULT module.</dd>
+<dt><em>timestamp</em> (boolean, <cite>UPDATE</cite>)</dt>
+<dd>Include timestamp in log messages.</dd>
+<dt><em>source</em> (boolean, <cite>UPDATE</cite>)</dt>
+<dd>Include source file and line number in log messages.</dd>
+<dt><em>output</em> (string, <cite>UPDATE</cite>)</dt>
+<dd>Where to send log messages. Can be ‘stderr’, ‘syslog’ or a file name.</dd>
+</dl>
+</div>
+<div class="section" id="fixedaddress">
+<h3>3.4.1.6. fixedAddress<a class="headerlink" href="#fixedaddress" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address prefix (always starting with ‘/’).</dd>
+<dt><em>phase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>The phase of a multi-hop address passing through one or more waypoints.</dd>
+<dt><em>fanout</em> (One of [‘multiple’, ‘single’], default=’multiple’, <cite>CREATE</cite>)</dt>
+<dd>One of ‘multiple’ or ‘single’. 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.</dd>
+<dt><em>bias</em> (One of [‘closest’, ‘spread’], default=’closest’, <cite>CREATE</cite>)</dt>
+<dd>Only if fanout is single. One of ‘closest’ or ‘spread’. 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.</dd>
+</dl>
+</div>
+<div class="section" id="waypoint">
+<h3>3.4.1.7. waypoint<a class="headerlink" href="#waypoint" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>address</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The AMQP address of the waypoint.</dd>
+<dt><em>connector</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The name of the on-demand connector used to reach the waypoint’s container.</dd>
+<dt><em>inPhase</em> (integer, default=-1, <cite>CREATE</cite>)</dt>
+<dd>The phase of the address as it is routed _to_ the waypoint.</dd>
+<dt><em>outPhase</em> (integer, default=-1, <cite>CREATE</cite>)</dt>
+<dd>The phase of the address as it is routed _from_ the waypoint.</dd>
+</dl>
+</div>
+<div class="section" id="linkroutepattern">
+<h3>3.4.1.8. linkRoutePattern<a class="headerlink" href="#linkroutepattern" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>An address prefix to match against target and source addresses. This pattern must be of the form ‘<text>.<text1>.<textN>’ or ‘<text>’ or ‘<text>.’ 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 ‘org.apache’ (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</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’, ‘both’], default=’both’, <cite>CREATE</cite>)</dt>
+<dd>Link direction for match: ‘in’ matches only links inbound to the client; ‘out’ matches only links outbound from the client; ‘both’ matches any link.</dd>
+<dt><em>connector</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="address">
+<h3>3.4.1.9. address<a class="headerlink" href="#address" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>distribution</em> (One of [‘multicast’, ‘closest’, ‘balanced’], default=’balanced’, <cite>CREATE</cite>)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>waypoint</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.</dd>
+<dt><em>ingressPhase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Advanced - Override the ingress phase for this address</dd>
+<dt><em>egressPhase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Advanced - Override the egress phase for this address</dd>
+</dl>
+</div>
+<div class="section" id="linkroute">
+<h3>3.4.1.10. linkRoute<a class="headerlink" href="#linkroute" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>containerId</em> (string, <cite>CREATE</cite>)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The name from a connector or listener</dd>
+<dt><em>distribution</em> (One of [‘linkBalanced’], default=’linkBalanced’, <cite>CREATE</cite>)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required, <cite>CREATE</cite>)</dt>
+<dd>The permitted direction of links: ‘in’ means client senders; ‘out’ means client receivers</dd>
+<dt><em>operStatus</em> (One of [‘inactive’, ‘active’])</dt>
+<dd>The operational status of this linkRoute: inactive - The remote container is not connected; active - the remote container is connected and ready to accept link routed attachments.</dd>
+</dl>
+</div>
+<div class="section" id="autolink">
+<h3>3.4.1.11. autoLink<a class="headerlink" href="#autolink" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>addr</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address of the provisioned object</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required, <cite>CREATE</cite>)</dt>
+<dd>The direction of the link to be created. In means into the router, out means out of the router.</dd>
+<dt><em>phase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>The address phase for this link. Defaults to ‘0’ for ‘out’ links and ‘1’ for ‘in’ links.</dd>
+<dt><em>containerId</em> (string, <cite>CREATE</cite>)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The name from a connector or listener</dd>
+<dt><em>linkRef</em> (string)</dt>
+<dd>Reference to the org.apache.qpid.dispatch.router.link if the link exists</dd>
+<dt><em>operStatus</em> (One of [‘inactive’, ‘attaching’, ‘failed’, ‘active’, ‘quiescing’, ‘idle’])</dt>
+<dd>The operational status of this autoLink: inactive - The remote container is not connected; attaching - the link is attaching to the remote node; failed - the link attach failed; active - the link is attached and operational; quiescing - the link is transitioning to idle state; idle - the link is attached but there are no deliveries flowing and no unsettled deliveries.</dd>
+<dt><em>lastError</em> (string)</dt>
+<dd>The error description from the last attach failure</dd>
+</dl>
+</div>
+<div class="section" id="console">
+<h3>3.4.1.12. console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h3>
+<p>Start a websocket/tcp proxy and http file server to serve the web console</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>listener</em> (string)</dt>
+<dd>The name of the listener to send the proxied tcp traffic to.</dd>
+<dt><em>wsport</em> (integer, default=5673)</dt>
+<dd>port on which to listen for websocket traffic</dd>
+<dt><em>proxy</em> (string)</dt>
+<dd>The full path to the proxy program to run.</dd>
+<dt><em>home</em> (string)</dt>
+<dd>The full path to the html/css/js files for the console.</dd>
+<dt><em>args</em> (string)</dt>
+<dd>Optional args to pass the proxy program for logging, authentication, etc.</dd>
+</dl>
+</div>
+<div class="section" id="policy">
+<h3>3.4.1.13. policy<a class="headerlink" href="#policy" title="Permalink to this headline">.</a></h3>
+<p>Defines global connection limit</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>maximumConnections</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.</dd>
+<dt><em>enableAccessRules</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>Enable user rule set processing and connection denial.</dd>
+<dt><em>policyFolder</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.</dd>
+<dt><em>defaultApplication</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.</dd>
+<dt><em>defaultApplicationEnabled</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>Enable defaultApplication policy fallback logic.</dd>
+</dl>
+<p><em>connectionsProcessed</em> (integer)</p>
+<p><em>connectionsDenied</em> (integer)</p>
+<p><em>connectionsCurrent</em> (integer)</p>
+</div>
+<div class="section" id="policyruleset">
+<h3>3.4.1.14. policyRuleset<a class="headerlink" href="#policyruleset" title="Permalink to this headline">.</a></h3>
+<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>applicationName</em> (string, required)</dt>
+<dd>The application name.</dd>
+<dt><em>maxConnections</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Maximum number of concurrent client connections allowed. Zero implies no limit.</dd>
+<dt><em>maxConnPerUser</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.</dd>
+<dt><em>maxConnPerHost</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.</dd>
+<dt><em>userGroups</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed ‘restricted’. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.</dd>
+<dt><em>ingressHostGroups</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address ‘*’ represents any host address.</dd>
+<dt><em>ingressPolicies</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.</dd>
+<dt><em>connectionAllowDefault</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>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 ‘default’ user group and receive ‘default’ settings.</dd>
+<dt><em>settings</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is a user group name and the value is a map of the corresponding settings for that group.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="operational-entities">
+<h2>3.4.2. Operational Entities<a class="headerlink" href="#operational-entities" title="Permalink to this headline">.</a></h2>
+<p>Operational entities provide statistics and other run-time attributes of the router.
+The <cite>qdstat(8)</cite> tool provides a convenient way to query run-time statistics.
+You can also use the general-purpose management tool <cite>qdmanage(8)</cite> to query
+operational attributes.</p>
+<div class="section" id="org-amqp-management">
+<h3>3.4.2.1. org.amqp.management<a class="headerlink" href="#org-amqp-management" title="Permalink to this headline">.</a></h3>
+<p>The standard AMQP management node interface.</p>
+<p>Operations allowed: <cite>QUERY</cite>, <cite>GET-TYPES</cite>, <cite>GET-ANNOTATIONS</cite>, <cite>GET-OPERATIONS</cite>, <cite>GET-ATTRIBUTES</cite>, <cite>GET-MGMT-NODES</cite>, <cite>READ</cite></p>
+<div class="section" id="operation-get-types">
+<h4>3.4.2.1.1. Operation GET-TYPES<a class="headerlink" href="#operation-get-types" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and their inheritance relationships</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of the entity types (strings) that it extends.</p>
+</div>
+<div class="section" id="operation-get-attributes">
+<h4>3.4.2.1.2. Operation GET-ATTRIBUTES<a class="headerlink" href="#operation-get-attributes" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the annotations they implement</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is a list (of strings) of attributes on that entity type.</p>
+</div>
+<div class="section" id="operation-get-operations">
+<h4>3.4.2.1.3. Operation GET-OPERATIONS<a class="headerlink" href="#operation-get-operations" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the operations they support</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of operation names (strings) that it supports.</p>
+</div>
+<div class="section" id="operation-get-annotations">
+<h4>3.4.2.1.4. Operation GET-ANNOTATIONS<a class="headerlink" href="#operation-get-annotations" title="Permalink to this headline">.</a></h4>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of annotations (strings) that it implements.</p>
+</div>
+<div class="section" id="operation-query">
+<h4>3.4.2.1.5. Operation QUERY<a class="headerlink" href="#operation-query" title="Permalink to this headline">.</a></h4>
+<p>Query for attribute values of multiple entities.</p>
+<p><strong>Request body</strong> (map)A map containing the key <cite>attributeNames</cite> with value a list of (string) attribute names to return. If the list or the map is empty or the body is missing all attributes are returned.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>If set, specifies the number of entries from the result set to return. If not set return all from <cite>offset</cite></dd>
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+<dt><em>offset</em> (integer)</dt>
+<dd>If set, specifies the number of the first element of the result set to be returned.</dd>
+</dl>
+<p><strong>Response body</strong> (map)A map with two entries. <cite>attributeNames</cite> is a list of the attribute names returned. <cite>results</cite> is a list of lists each containing the attribute values for a single entity in the same order as the names in the <cite>attributeNames</cite> entry. If an attribute name is not applicable for an entity then the corresponding value is <cite>null</cite></p>
+<p><strong>Response properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>Number of results returned</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+</div>
+<div class="section" id="operation-get-mgmt-nodes">
+<h4>3.4.2.1.6. Operation GET-MGMT-NODES<a class="headerlink" href="#operation-get-mgmt-nodes" title="Permalink to this headline">.</a></h4>
+<p>Get the addresses of all management nodes known to this router</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (list)A list of addresses (strings) of management nodes known to this management node.</p>
+</div>
+</div>
+<div class="section" id="management">
+<h3>3.4.2.2. management<a class="headerlink" href="#management" title="Permalink to this headline">.</a></h3>
+<p>Qpid dispatch router extensions to the standard org.amqp.management interface.</p>
+<p>Operations allowed: <cite>GET-SCHEMA</cite>, <cite>GET-JSON-SCHEMA</cite>, <cite>GET-LOG</cite>, <cite>PROFILE</cite>, <cite>QUERY</cite>, <cite>GET-TYPES</cite>, <cite>GET-ANNOTATIONS</cite>, <cite>GET-OPERATIONS</cite>, <cite>GET-ATTRIBUTES</cite>, <cite>GET-MGMT-NODES</cite>, <cite>READ</cite></p>
+<div class="section" id="operation-get-schema-json">
+<h4>3.4.2.2.1. Operation GET-SCHEMA-JSON<a class="headerlink" href="#operation-get-schema-json" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in JSON format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>indent</em> (integer)</dt>
+<dd>Number of spaces to indent the formatted result. If not specified, the result is in minimal format, no unnecessary spaces or newlines.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)The qdrouter schema as a JSON string.</p>
+</div>
+<div class="section" id="operation-get-log">
+<h4>3.4.2.2.2. Operation GET-LOG<a class="headerlink" href="#operation-get-log" title="Permalink to this headline">.</a></h4>
+<p>Get recent log entries from the router.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>limit</em> (integer)</dt>
+<dd>Maximum number of log entries to get.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)A list of log entries where each entry is a list of: module name(string), level name(string), message text(string), file name(string or None), line number(integer or None) , timestamp(integer)</p>
+</div>
+<div class="section" id="operation-get-schema">
+<h4>3.4.2.2.3. Operation GET-SCHEMA<a class="headerlink" href="#operation-get-schema" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in AMQP map format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)The qdrouter schema as a map.</p>
+</div>
+</div>
+<div class="section" id="router-link">
+<h3>3.4.2.3. router.link<a class="headerlink" href="#router-link" title="Permalink to this headline">.</a></h3>
+<p>Link to another AMQP endpoint: router node, client or other AMQP process.</p>
+<p>Operations allowed: <cite>UPDATE</cite>, <cite>READ</cite></p>
+<p><em>adminStatus</em> (One of [‘enabled’, ‘disabled’], default=’enabled’, <cite>UPDATE</cite>)</p>
+<p><em>operStatus</em> (One of [‘up’, ‘down’, ‘quiescing’, ‘idle’])</p>
+<dl class="docutils">
+<dt><em>linkName</em> (string)</dt>
+<dd>Name assigned to the link in the Attach.</dd>
+<dt><em>linkType</em> (One of [‘endpoint’, ‘router-control’, ‘inter-router’])</dt>
+<dd>Type of link: endpoint: a link to a normally connected endpoint; inter-router: a link to another router in the network.</dd>
+<dt><em>linkDir</em> (One of [‘in’, ‘out’])</dt>
+<dd>Direction of delivery flow over the link, inbound or outbound to or from the router.</dd>
+<dt><em>owningAddr</em> (string)</dt>
+<dd>Address assigned to this link during attach: The target for inbound links or the source for outbound links.</dd>
+<dt><em>capacity</em> (integer)</dt>
+<dd>The capacity, in deliveries, for the link. The number of undelivered plus unsettled deliveries shall not exceed the capacity. This is enforced by link flow control.</dd>
+<dt><em>peer</em> (string)</dt>
+<dd>Identifier of the paired link if this is an attach-routed link.</dd>
+<dt><em>undeliveredCount</em> (integer)</dt>
+<dd>The number of undelivered messages pending for the link.</dd>
+<dt><em>unsettledCount</em> (integer)</dt>
+<dd>The number of unsettled deliveries awaiting settlement on the link</dd>
+<dt><em>deliveryCount</em> (integer)</dt>
+<dd>The total number of deliveries that have traversed this link.</dd>
+</dl>
+</div>
+<div class="section" id="router-address">
+<h3>3.4.2.4. router.address<a class="headerlink" href="#router-address" title="Permalink to this headline">.</a></h3>
+<p>AMQP address managed by the router.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>distribution</em> (One of [‘flood’, ‘multicast’, ‘closest’, ‘balanced’, ‘linkBalanced’])</dt>
+<dd>Forwarding treatment for the address: flood - messages delivered to all subscribers along all available paths (this will cause duplicate deliveries if there are redundant paths); multi - one copy of each message delivered to all subscribers; anyClosest - messages delivered to only the closest subscriber; anyBalanced - messages delivered to one subscriber with load balanced across subscribers; linkBalanced - for link-routing, link attaches balanced across destinations.</dd>
+<dt><em>inProcess</em> (integer)</dt>
+<dd>The number of in-process subscribers for this address</dd>
+<dt><em>subscriberCount</em> (integer)</dt>
+<dd>The number of local subscribers for this address (i.e. attached to this router)</dd>
+<dt><em>remoteCount</em> (integer)</dt>
+<dd>The number of remote routers that have at least one subscriber to this address</dd>
+<dt><em>containerCount</em> (integer)</dt>
+<dd>The number of attached containers that serve this route address</dd>
+<dt><em>deliveriesIngress</em> (integer)</dt>
+<dd>The number of deliveries to this address that entered the router network on this router</dd>
+<dt><em>deliveriesEgress</em> (integer)</dt>
+<dd>The number of deliveries to this address that exited the router network on this router</dd>
+<dt><em>deliveriesTransit</em> (integer)</dt>
+<dd>The number of deliveries to this address that transited this router to another router</dd>
+<dt><em>deliveriesToContainer</em> (integer)</dt>
+<dd>The number of deliveries to this address that were given to an in-process subscriber</dd>
+<dt><em>deliveriesFromContainer</em> (integer)</dt>
+<dd>The number of deliveries to this address that were originated from an in-process entity</dd>
+<dt><em>key</em> (string)</dt>
+<dd>Internal unique (to this router) key to identify the address</dd>
+<dt><em>remoteHostRouters</em> (list)</dt>
+<dd>List of remote routers on which there is a destination for this address.</dd>
+<dt><em>transitOutstanding</em> (list)</dt>
+<dd>List of numbers of outstanding deliveries across a transit (inter-router) link for this address. This is for balanced distribution only.</dd>
+<dt><em>trackedDeliveries</em> (integer)</dt>
+<dd>Number of transit deliveries being tracked for this address (for balanced distribution).</dd>
+</dl>
+</div>
+<div class="section" id="router-node">
+<h3>3.4.2.5. router.node<a class="headerlink" href="#router-node" title="Permalink to this headline">.</a></h3>
+<p>Remote router node connected to this router.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>id</em> (string)</dt>
+<dd>Remote node identifier.</dd>
+<dt><em>instance</em> (integer)</dt>
+<dd>Remote node boot number.</dd>
+<dt><em>linkState</em> (list)</dt>
+<dd>List of remote node’s neighbours.</dd>
+<dt><em>nextHop</em> (string)</dt>
+<dd>Neighbour ID of next hop to remote node from here.</dd>
+<dt><em>validOrigins</em> (list)</dt>
+<dd>List of valid origin nodes for messages arriving via the re mote node, used for duplicate elimination in redundant networks.</dd>
+<dt><em>address</em> (string)</dt>
+<dd>Address of the remote node</dd>
+<dt><em>routerLink</em> (entityId)</dt>
+<dd>Local link to remote node</dd>
+<dt><em>cost</em> (integer)</dt>
+<dd>Reachability cost</dd>
+</dl>
+</div>
+<div class="section" id="connection">
+<h3>3.4.2.6. connection<a class="headerlink" href="#connection" title="Permalink to this headline">.</a></h3>
+<p>Connections to the router’s container.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>container</em> (string)</dt>
+<dd>The container for this connection</dd>
+<dt><em>opened</em> (boolean)</dt>
+<dd>The connection has been opened (i.e. AMQP OPEN)</dd>
+<dt><em>host</em> (string)</dt>
+<dd>IP address and port number in the form addr:port.</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’])</dt>
+<dd>Direction of connection establishment in or out of the router.</dd>
+</dl>
+<p><em>role</em> (string)</p>
+<dl class="docutils">
+<dt><em>isAuthenticated</em> (boolean)</dt>
+<dd>Indicates whether the identity of the connection’s user is authentic.</dd>
+<dt><em>isEncrypted</em> (boolean)</dt>
+<dd>Indicates whether the connection content is encrypted.</dd>
+<dt><em>sasl</em> (string)</dt>
+<dd>SASL mechanism in effect for authentication.</dd>
+<dt><em>user</em> (string)</dt>
+<dd>Identity of the authenticated user.</dd>
+<dt><em>ssl</em> (boolean)</dt>
+<dd>True iff SSL/TLS is in effect for this connection.</dd>
+<dt><em>sslProto</em> (string)</dt>
+<dd>SSL protocol name</dd>
+<dt><em>sslCipher</em> (string)</dt>
+<dd>SSL cipher name</dd>
+<dt><em>sslSsf</em> (integer)</dt>
+<dd>SSL strength factor in effect</dd>
+<dt><em>properties</em> (map)</dt>
+<dd>Connection properties supplied by the peer.</dd>
+</dl>
+</div>
+<div class="section" id="allocator">
+<h3>3.4.2.7. allocator<a class="headerlink" href="#allocator" title="Permalink to this headline">.</a></h3>
+<p>Memory allocation pool.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<p><em>typeName</em> (string)</p>
+<p><em>typeSize</em> (integer)</p>
+<p><em>transferBatchSize</em> (integer)</p>
+<p><em>localFreeListMax</em> (integer)</p>
+<p><em>globalFreeListMax</em> (integer)</p>
+<p><em>totalAllocFromHeap</em> (integer)</p>
+<p><em>totalFreeToHeap</em> (integer)</p>
+<p><em>heldByThreads</em> (integer)</p>
+<p><em>batchesRebalancedToThreads</em> (integer)</p>
+<p><em>batchesRebalancedToGlobal</em> (integer)</p>
+</div>
+<div class="section" id="policystats">
+<h3>3.4.2.8. policyStats<a class="headerlink" href="#policystats" title="Permalink to this headline">.</a></h3>
+<p>Per application connection and access statistics.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>applicationName</em> (string)</dt>
+<dd>The application name.</dd>
+</dl>
+<p><em>connectionsApproved</em> (integer)</p>
+<p><em>connectionsDenied</em> (integer)</p>
+<p><em>connectionsCurrent</em> (integer)</p>
+<dl class="docutils">
+<dt><em>perUserState</em> (map)</dt>
+<dd>A map where the key is the authenticated user name and the value is a list of the user’s connections.</dd>
+<dt><em>perHostState</em> (map)</dt>
+<dd>A map where the key is the host name and the value is a list of the host’s connections.</dd>
+</dl>
+<p><em>sessionDenied</em> (integer)</p>
+<p><em>senderDenied</em> (integer)</p>
+<p><em>receiverDenied</em> (integer)</p>
+</div>
+</div>
+<div class="section" id="management-operations">
+<h2>3.4.3. Management Operations<a class="headerlink" href="#management-operations" title="Permalink to this headline">.</a></h2>
+<p>The <cite>qdstat(8)</cite> and <cite>qdmanage(8)</cite> tools allow you to view or modify management entity
+attributes. They work by invoking <em>management operations</em>. You can invoke these operations
+from any AMQP client by sending a message with the appropriate properties and body to the
+<cite>$management</cite> address. The message should have a <cite>reply-to</cite> address indicating where the
+response should be sent.</p>
+<div class="section" id="operations-for-all-entity-types">
+<h3>3.4.3.1. Operations for all entity types<a class="headerlink" href="#operations-for-all-entity-types" title="Permalink to this headline">.</a></h3>
+<div class="section" id="operation-read">
+<h4>3.4.3.1.1. Operation READ<a class="headerlink" href="#operation-read" title="Permalink to this headline">.</a></h4>
+<p>Read attributes of an entity</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string)</dt>
+<dd>Type of desired entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of desired entity. Must supply name or identity.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Identity of desired entity. Must supply name or identity.</dd>
+</dl>
+<p><strong>Response body</strong> (map)Attributes of the entity</p>
+</div>
+<div class="section" id="operation-create">
+<h4>3.4.3.1.2. Operation CREATE<a class="headerlink" href="#operation-create" title="Permalink to this headline">.</a></h4>
+<p>Create a new entity.</p>
+<p><strong>Request body</strong> (map, required)Attributes for the new entity. Can include name and/or type.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string, required)</dt>
+<dd>Type of new entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of new entity. Optional, defaults to identity.</dd>
+</dl>
+<p><strong>Response body</strong> (map)Attributes of the entity</p>
+</div>
+<div class="section" id="operation-update">
+<h4>3.4.3.1.3. Operation UPDATE<a class="headerlink" href="#operation-update" title="Permalink to this headline">.</a></h4>
+<p>Update attributes of an entity</p>
+<p><strong>Request body</strong> (map)Attributes to update for the entity. Can include name or identity.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string)</dt>
+<dd>Type of desired entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of desired entity. Must supply name or identity.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Identity of desired entity. Must supply name or identity.</dd>
+</dl>
+<p><strong>Response body</strong> (map)Updated attributes of the entity</p>
+</div>
+<div class="section" id="operation-delete">
+<h4>3.4.3.1.4. Operation DELETE<a class="headerlink" href="#operation-delete" title="Permalink to this headline">.</a></h4>
+<p>Delete an entity</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string)</dt>
+<dd>Type of desired entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of desired entity. Must supply name or identity.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Identity of desired entity. Must supply name or identity.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="operations-for-org-amqp-management-entity-type">
+<h3>3.4.3.2. Operations for <cite>org.amqp.management</cite> entity type<a class="headerlink" href="#operations-for-org-amqp-management-entity-type" title="Permalink to this headline">.</a></h3>
+<div class="section" id="id1">
+<h4>3.4.3.2.1. Operation GET-TYPES<a class="headerlink" href="#id1" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and their inheritance relationships</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of the entity types (strings) that it extends.</p>
+</div>
+<div class="section" id="id2">
+<h4>3.4.3.2.2. Operation GET-ATTRIBUTES<a class="headerlink" href="#id2" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the annotations they implement</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is a list (of strings) of attributes on that entity type.</p>
+</div>
+<div class="section" id="id3">
+<h4>3.4.3.2.3. Operation GET-OPERATIONS<a class="headerlink" href="#id3" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the operations they support</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of operation names (strings) that it supports.</p>
+</div>
+<div class="section" id="id4">
+<h4>3.4.3.2.4. Operation GET-ANNOTATIONS<a class="headerlink" href="#id4" title="Permalink to this headline">.</a></h4>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of annotations (strings) that it implements.</p>
+</div>
+<div class="section" id="id5">
+<h4>3.4.3.2.5. Operation QUERY<a class="headerlink" href="#id5" title="Permalink to this headline">.</a></h4>
+<p>Query for attribute values of multiple entities.</p>
+<p><strong>Request body</strong> (map)A map containing the key <cite>attributeNames</cite> with value a list of (string) attribute names to return. If the list or the map is empty or the body is missing all attributes are returned.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>If set, specifies the number of entries from the result set to return. If not set return all from <cite>offset</cite></dd>
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+<dt><em>offset</em> (integer)</dt>
+<dd>If set, specifies the number of the first element of the result set to be returned.</dd>
+</dl>
+<p><strong>Response body</strong> (map)A map with two entries. <cite>attributeNames</cite> is a list of the attribute names returned. <cite>results</cite> is a list of lists each containing the attribute values for a single entity in the same order as the names in the <cite>attributeNames</cite> entry. If an attribute name is not applicable for an entity then the corresponding value is <cite>null</cite></p>
+<p><strong>Response properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>Number of results returned</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+</div>
+<div class="section" id="id6">
+<h4>3.4.3.2.6. Operation GET-MGMT-NODES<a class="headerlink" href="#id6" title="Permalink to this headline">.</a></h4>
+<p>Get the addresses of all management nodes known to this router</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (list)A list of addresses (strings) of management nodes known to this management node.</p>
+</div>
+</div>
+<div class="section" id="operations-for-management-entity-type">
+<h3>3.4.3.3. Operations for <cite>management</cite> entity type<a class="headerlink" href="#operations-for-management-entity-type" title="Permalink to this headline">.</a></h3>
+<div class="section" id="id7">
+<h4>3.4.3.3.1. Operation GET-SCHEMA-JSON<a class="headerlink" href="#id7" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in JSON format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>indent</em> (integer)</dt>
+<dd>Number of spaces to indent the formatted result. If not specified, the result is in minimal format, no unnecessary spaces or newlines.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)The qdrouter schema as a JSON string.</p>
+</div>
+<div class="section" id="id8">
+<h4>3.4.3.3.2. Operation GET-LOG<a class="headerlink" href="#id8" title="Permalink to this headline">.</a></h4>
+<p>Get recent log entries from the router.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>limit</em> (integer)</dt>
+<dd>Maximum number of log entries to get.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)A list of log entries where each entry is a list of: module name(string), level name(string), message text(string), file name(string or None), line number(integer or None) , timestamp(integer)</p>
+</div>
+<div class="section" id="id9">
+<h4>3.4.3.3.3. Operation GET-SCHEMA<a class="headerlink" href="#id9" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in AMQP map format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)The qdrouter schema as a map.</p>
+</div>
+</div>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/technical_details.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/technical_details.html.in b/input/releases/qpid-dispatch-0.6.0/book/technical_details.html.in
new file mode 100644
index 0000000..139ea56
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/technical_details.html.in
@@ -0,0 +1,68 @@
+
+
+ <div class="section" id="technical-details-and-specifications">
+<h1>3. Technical Details and Specifications<a class="headerlink" href="#technical-details-and-specifications" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="client_compatibility.html">3.1. Client Compatibility</a></li>
+<li class="toctree-l1"><a class="reference internal" href="addressing.html">3.2. Addressing</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="addressing.html#routing-patterns">3.2.1. Routing patterns</a></li>
+<li class="toctree-l2"><a class="reference internal" href="addressing.html#routing-mechanisms">3.2.2. Routing mechanisms</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="addressing.html#message-routing">3.2.2.1. Message routing</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="amqp-mapping.html">3.3. AMQP Mapping</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#message-annotations">3.3.1. Message Annotations</a></li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#source-target-capabilities">3.3.2. Source/Target Capabilities</a></li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#dynamic-node-properties">3.3.3. Dynamic-Node-Properties</a></li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#addresses-and-address-formats">3.3.4. Addresses and Address Formats</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#address-patterns">3.3.4.1. Address Patterns</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#supported-addresses">3.3.4.2. Supported Addresses</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="schema.html">3.4. Management Schema</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="schema.html#configuration-entities">3.4.1. Configuration Entities</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#container">3.4.1.1. container</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router">3.4.1.2. router</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#listener">3.4.1.3. listener</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#connector">3.4.1.4. connector</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#log">3.4.1.5. log</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#fixedaddress">3.4.1.6. fixedAddress</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#waypoint">3.4.1.7. waypoint</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#linkroutepattern">3.4.1.8. linkRoutePattern</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#address">3.4.1.9. address</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#linkroute">3.4.1.10. linkRoute</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#autolink">3.4.1.11. autoLink</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#console">3.4.1.12. console</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#policy">3.4.1.13. policy</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#policyruleset">3.4.1.14. policyRuleset</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="schema.html#operational-entities">3.4.2. Operational Entities</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#org-amqp-management">3.4.2.1. org.amqp.management</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#management">3.4.2.2. management</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router-link">3.4.2.3. router.link</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router-address">3.4.2.4. router.address</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router-node">3.4.2.5. router.node</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#connection">3.4.2.6. connection</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#allocator">3.4.2.7. allocator</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#policystats">3.4.2.8. policyStats</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="schema.html#management-operations">3.4.3. Management Operations</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-all-entity-types">3.4.3.1. Operations for all entity types</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-org-amqp-management-entity-type">3.4.3.2. Operations for <cite>org.amqp.management</cite> entity type</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-management-entity-type">3.4.3.3. Operations for <cite>management</cite> entity type</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/tools.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/tools.html.in b/input/releases/qpid-dispatch-0.6.0/book/tools.html.in
new file mode 100644
index 0000000..cb7aefb
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/tools.html.in
@@ -0,0 +1,76 @@
+
+
+ <div class="section" id="tools">
+<h1>2.2. Tools<a class="headerlink" href="#tools" title="Permalink to this headline">.</a></h1>
+<div class="section" id="qdstat">
+<h2>2.2.1. qdstat<a class="headerlink" href="#qdstat" title="Permalink to this headline">.</a></h2>
+<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>
+<table border="1" class="docutils">
+<colgroup>
+<col width="15%" />
+<col width="85%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Option</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>-l</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>-a</td>
+<td>Print a list of addresses known to the router.</td>
+</tr>
+<tr class="row-even"><td>-n</td>
+<td>Print a list of known routers in the network.</td>
+</tr>
+<tr class="row-odd"><td>-c</td>
+<td>Print a list of connections to the router.</td>
+</tr>
+<tr class="row-even"><td>–autolinks</td>
+<td>Print a list of configured auto-links.</td>
+</tr>
+<tr class="row-odd"><td>–linkroutes</td>
+<td>Print a list of configures link-routes.</td>
+</tr>
+</tbody>
+</table>
+<p>For complete details see the <cite>qdstat(8)</cite> man page and the output of
+<cite>qdstat –help</cite>.</p>
+</div>
+<div class="section" id="qdmanage">
+<h2>2.2.2. qdmanage<a class="headerlink" href="#qdmanage" title="Permalink to this headline">.</a></h2>
+<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>
+<p>For example you can query all the connection entities in the router:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage query --type connection
+</pre></div>
+</div>
+<p>To enable logging debug and higher level messages by default:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage update log/DEFAULT enable=debug+
+</pre></div>
+</div>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage create type=listener port=5555
+</pre></div>
+</div>
+<p>Now you can connect to port 5555, for exampple:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage query -b localhost:5555 --type listener
+</pre></div>
+</div>
+<p>For complete details see the <cite>qdmanage(8)</cite> man page and the output of
+<cite>qdmanage –help</cite>. Also for details of what can be configured see the
+<cite>qdrouterd.conf(5)</cite> man page.</p>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/using.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/using.html.in b/input/releases/qpid-dispatch-0.6.0/book/using.html.in
new file mode 100644
index 0000000..de46f1d
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/using.html.in
@@ -0,0 +1,32 @@
+
+
+ <div class="section" id="using-qpid-dispatch">
+<h1>2. Using Qpid Dispatch<a class="headerlink" href="#using-qpid-dispatch" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="default_config.html">2.1. Configuration</a></li>
+<li class="toctree-l1"><a class="reference internal" href="tools.html">2.2. Tools</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="tools.html#qdstat">2.2.1. qdstat</a></li>
+<li class="toctree-l2"><a class="reference internal" href="tools.html#qdmanage">2.2.2. qdmanage</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="basic_usage.html">2.3. Basic Usage and Examples</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</a></li>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#mobile-subscribers">2.3.2. Mobile Subscribers</a></li>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#dynamic-reply-to">2.3.3. Dynamic Reply-To</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="link_routing.html">2.4. Link Routing</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="link_routing.html#configuration">2.4.1. Configuration</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="auto_links.html">2.5. Indirect Waypoints and Auto-Links</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html#queue-waypoint-example">2.5.1. Queue Waypoint Example</a></li>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html#sharded-queue-example">2.5.2. Sharded Queue Example</a></li>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html#dynamically-adding-shards">2.5.3. Dynamically Adding Shards</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/index.md
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/index.md b/input/releases/qpid-dispatch-0.6.0/index.md
new file mode 100644
index 0000000..60a350e
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.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.6.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.6.0.tar.gz](http://archive.apache.org/dist/qpid/dispatch/0.6.0/qpid-dispatch-0.6.0.tar.gz) | [PGP](http://archive.apache.org/dist/qpid/dispatch/0.6.0/qpid-dispatch-0.6.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.6.0)
+ - [Dispatch router book](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.6.0)
+ - [Resolved issues in JIRA](https://issues.apache.org/jira/issues/?jql=project+%3D+DISPATCH+AND+fixVersion+%3D+%270.6.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.6.0)
+
+<script type="text/javascript">
+ _deferredFunctions.push(function() {
+ if ("0.6.0" === "{{current_dispatch_release}}") {
+ _modifyCurrentReleaseLinks();
+ }
+ });
+</script>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdmanage.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdmanage.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdmanage.html.in
new file mode 100644
index 0000000..865ef61
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/man/qdmanage.html.in
@@ -0,0 +1,139 @@
+
+
+ <div class="section" id="qdmanage-manual-page">
+<h1>qdmanage manual page<a class="headerlink" href="#qdmanage-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdmanage <em>operation</em> [<em>options...</em>] [<em>arguments...</em>]</p>
+</div>
+<div class="section" id="description">
+<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<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 class="section" id="operations">
+<h2>Operations<a class="headerlink" href="#operations" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt><cite>query</cite> [<em>ATTR</em>...]</dt>
+<dd>Print the attributes named in the ATTR list or all attributes if
+none are listed. Print attributes for all entities by default, use
+–type, –name and –identity options to restrict what is printed.</dd>
+<dt><cite>create</cite> [<em>ATTR=VALUE</em>...]</dt>
+<dd>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 entitiees.</dd>
+<dt><cite>read</cite></dt>
+<dd>Print the attributes of an entity specified by the –name or
+–identity options. With the –stdin option, create entities based
+on data from stdin. This can be a JSON map of attributes to create a
+single entity, or a JSON list of maps to create multiple entitiees.</dd>
+<dt><cite>update</cite> [<em>ATTR=VALUE</em>...]</dt>
+<dd>Update the attributes of an existing 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 entitiees. If an ATTR name is listed with no =VALUE,
+that attribute will be deleted from the entity.</dd>
+<dt><cite>delete</cite></dt>
+<dd>Delete an entity specified by the –name or –identity options.</dd>
+<dt><cite>get-types</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their base types. With no arguments list all
+types.</dd>
+<dt><cite>get-operations</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their operations. With no arguments list all
+types.</dd>
+<dt><cite>get-attributes</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their attributes. With no arguments list all
+types.</dd>
+<dt><cite>get-annotations</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their annotations. With no arguments list all
+types.</dd>
+<dt><cite>get-mgmt-nodes</cite></dt>
+<dd>List all other known management nodes connected to this one.</dd>
+<dt><cite>get-json-schema</cite> [<em>INDENT</em>]</dt>
+<dd>Get the router schema in JSON format. Optional integer indent for
+formatted output.</dd>
+<dt><cite>get-log</cite> [<em>INDENT</em>]</dt>
+<dd>Get recent log entries from the router.</dd>
+</dl>
+</div>
+<div class="section" id="options">
+<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
+<p>-h, –help
+: show this help message and exit</p>
+<p>–version
+: Print version and exit.</p>
+<p>–type=TYPE
+: Type of entity to operate on.</p>
+<p>–name=NAME
+: Name of entity to operate on.</p>
+<p>–identity=ID
+: Identity of entity to operate on.</p>
+<p>–indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print</p>
+<p>–stdin
+: Read attributes as JSON map or list of maps from</p>
+<p>–body=BODY
+: JSON value to use as body of a non-standard operation</p>
+<p>–properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p>
+<div class="section" id="connection-options">
+<h3>Connection Options<a class="headerlink" href="#connection-options" title="Permalink to this headline">.</a></h3>
+<p>-b URL, –bus=URL
+: URL of the messaging bus to connect to (default</p>
+<p>-r ROUTER-ID, –router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, –timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>–ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>–ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>–ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>–ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+</div>
+</div>
+<div class="section" id="files">
+<h2>Files<a class="headerlink" href="#files" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt>/usr/local/share/doc/qpid-dispatch/qdrouter.json</dt>
+<dd>Management schema for qdrouterd.</dd>
+<dt>/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt</dt>
+<dd>Explanation of the management schema.</dd>
+</dl>
+</div>
+<div class="section" id="examples">
+<h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">.</a></h2>
+<p>Show the logging configuration</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage query --type=log
+</pre></div>
+</div>
+<p>Enable debug and higher log messages by default:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/DEFAULT enable=debug+
+</pre></div>
+</div>
+<p>Enable trace log messages only for the MESSAGE moudle and direct MESSAGE
+logs to the file “test.log”</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log
+</pre></div>
+</div>
+<p>Set MESSAGE logging back to the default:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=default
+</pre></div>
+</div>
+<p>Disable MESSAGE logging:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=none
+</pre></div>
+</div>
+</div>
+<div class="section" id="see-also">
+<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</div>
+</div>
+
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[7/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/client_compatibility.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/client_compatibility.html b/content/releases/qpid-dispatch-0.6.0/book/client_compatibility.html
new file mode 100644
index 0000000..826c7f4
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/client_compatibility.html
@@ -0,0 +1,177 @@
+<!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>3.1. Client Compatibility. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>3.1. Client Compatibility.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="client-compatibility">
+<h1>3.1. Client Compatibility<a class="headerlink" href="#client-compatibility" title="Permalink to this headline">.</a></h1>
+<p>Dispatch Router should, in theory, work with any client that is
+compatible with AMQP 1.0. The following clients have been tested:</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="20%" />
+<col width="80%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Client</em></th>
+<th class="head"><em>Notes</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>qpid::messaging</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>Proton Reactor</td>
+<td>The Proton Reactor API is compatible with Dispatch Router.</td>
+</tr>
+<tr class="row-even"><td>Proton Messenger</td>
+<td>Messenger works with Dispatch Router.</td>
+</tr>
+</tbody>
+</table>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/console.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/console.html b/content/releases/qpid-dispatch-0.6.0/book/console.html
new file mode 100644
index 0000000..d00913d
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/console.html
@@ -0,0 +1,169 @@
+<!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>4. Console. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>4. Console.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="console">
+<h1>4. Console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="console_overview.html">4.1. Console overview</a></li>
+<li class="toctree-l1"><a class="reference internal" href="console_installation.html">4.2. Console installation</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="console_installation.html#prerequisites">4.2.1. Prerequisites</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_installation.html#the-console-files">4.2.2. The console files</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="console_operation.html">4.3. Console operation</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#logging-in-to-a-router-network">4.3.1. Logging in to a router network</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#overview-page">4.3.2. Overview page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#topology-page">4.3.3. Topology page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#list-page">4.3.4. List page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#charts-page">4.3.5. Charts page</a></li>
+<li class="toctree-l2"><a class="reference internal" href="console_operation.html#schema-page">4.3.6. Schema page</a></li>
+</ul>
+</li>
+</ul>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/console_installation.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/console_installation.html b/content/releases/qpid-dispatch-0.6.0/book/console_installation.html
new file mode 100644
index 0000000..38a0a17
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/console_installation.html
@@ -0,0 +1,184 @@
+<!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>4.2. Console installation. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>4.2. Console installation.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="console-installation">
+<h1>4.2. Console installation<a class="headerlink" href="#console-installation" title="Permalink to this headline">.</a></h1>
+<div class="section" id="prerequisites">
+<h2>4.2.1. Prerequisites<a class="headerlink" href="#prerequisites" title="Permalink to this headline">.</a></h2>
+<p>The following need to be installed before running a console:</p>
+<ul class="simple">
+<li>One or more dispatch routers. See the documentation for the dispatch router for help in starting a router network.</li>
+<li>A websockets to tcp proxy.</li>
+<li>A web server. This can be any server capable of serving static html/js/css/image files.</li>
+</ul>
+<p>To install a websockets to tcp proxy:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>sudo dnf install python-websockify
+websockify localhost:5673 localhost:5672
+</pre></div>
+</div>
+<p>This will start the proxy listening to ws traffic on port 5673 and translating it to tcp on port 5672.
+One of the routers in the network needs to have a listener configured on port 5672. That listener’s role should be ‘normal’. For example:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>listener {
+ host: 0.0.0.0
+ role: normal
+ port: amqp
+ saslMechanisms: ANONYMOUS
+}
+</pre></div>
+</div>
+</div>
+<div class="section" id="the-console-files">
+<h2>4.2.2. The console files<a class="headerlink" href="#the-console-files" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt>The files for the console are located under the console/stand-alone directory in the source tree.::</dt>
+<dd>index.html
+plugin/</dd>
+<dt>Copy these files to a directory under the the html or webapps directory of your web server. For example, for apache tomcat the files should be under webapps/dispatch. Then the console is available as::</dt>
+<dd><a class="reference external" href="http://localhost:8080/dispatch">http://localhost:8080/dispatch</a></dd>
+</dl>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/console_operation.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/console_operation.html b/content/releases/qpid-dispatch-0.6.0/book/console_operation.html
new file mode 100644
index 0000000..c7bee19
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/console_operation.html
@@ -0,0 +1,181 @@
+<!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>4.3. Console operation. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>4.3. Console operation.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="console-operation">
+<h1>4.3. Console operation<a class="headerlink" href="#console-operation" title="Permalink to this headline">.</a></h1>
+<div class="section" id="logging-in-to-a-router-network">
+<h2>4.3.1. Logging in to a router network<a class="headerlink" href="#logging-in-to-a-router-network" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_login.png" src="../_images/console_login.png" />
+<p>Enter the address of the websockets to tcp proxy that is connected to a router in the network.</p>
+<p>The Autostart checkbox, when checked, will automatically log in with the previous host:port the next time you start the console.</p>
+</div>
+<div class="section" id="overview-page">
+<h2>4.3.2. Overview page<a class="headerlink" href="#overview-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_overview.png" src="../_images/console_overview.png" />
+<p>On the overview page, aggregate information about routers, addresses, and connections is displayed.</p>
+</div>
+<div class="section" id="topology-page">
+<h2>4.3.3. Topology page<a class="headerlink" href="#topology-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_topology.png" src="../_images/console_topology.png" />
+<p>This page displays the router network in a graphical form showing how the routers are connected and information about the individual routers and links.</p>
+</div>
+<div class="section" id="list-page">
+<h2>4.3.4. List page<a class="headerlink" href="#list-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_entity.png" src="../_images/console_entity.png" />
+<p>Displays detailed information about entities such as routers, links, addresses, memory.</p>
+</div>
+<div class="section" id="charts-page">
+<h2>4.3.5. Charts page<a class="headerlink" href="#charts-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_charts.png" src="../_images/console_charts.png" />
+<p>This page displays graphs of numeric values that are on the list page.</p>
+</div>
+<div class="section" id="schema-page">
+<h2>4.3.6. Schema page<a class="headerlink" href="#schema-page" title="Permalink to this headline">.</a></h2>
+<img alt="../_images/console_schema.png" src="../_images/console_schema.png" />
+<p>This page displays the json schema that is used to manage the router network.</p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/console_overview.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/console_overview.html b/content/releases/qpid-dispatch-0.6.0/book/console_overview.html
new file mode 100644
index 0000000..074bd9a
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/console_overview.html
@@ -0,0 +1,153 @@
+<!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>4.1. Console overview. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>4.1. Console overview.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="console-overview">
+<h1>4.1. Console overview<a class="headerlink" href="#console-overview" title="Permalink to this headline">.</a></h1>
+<p>The console is an HTML based web site that displays information about a qpid dispatch router network.</p>
+<p>The console requires an HTML web server that can serve static html, javascript, style sheets, and images.</p>
+<p>The console only provides limited information about the clients that are attached to the router network and is therfore more appropriate for administrators needing to know the layout and health of the router network.</p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/default_config.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/default_config.html b/content/releases/qpid-dispatch-0.6.0/book/default_config.html
new file mode 100644
index 0000000..3fbaeeb
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/default_config.html
@@ -0,0 +1,160 @@
+<!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>2.1. Configuration. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>2.1. Configuration.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="configuration">
+<h1>2.1. Configuration<a class="headerlink" href="#configuration" title="Permalink to this headline">.</a></h1>
+<p>The default configuration file is installed in
+<cite>install-prefix</cite>/etc/qpid/qdrouterd.conf. 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>
+<p>To run the router, invoke the executable: qdrouterd [-c my-config-file]</p>
+<p>For more details of the configuration file see the <cite>qdrouterd.conf(5)</cite>
+man page.</p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/introduction.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/introduction.html b/content/releases/qpid-dispatch-0.6.0/book/introduction.html
new file mode 100644
index 0000000..ce25feb
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/introduction.html
@@ -0,0 +1,242 @@
+<!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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>1. Introduction.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="introduction">
+<h1>1. Introduction<a class="headerlink" href="#introduction" title="Permalink to this headline">.</a></h1>
+<div class="section" id="overview">
+<h2>1.1. Overview<a class="headerlink" href="#overview" title="Permalink to this headline">.</a></h2>
+<p>The Dispatch router is an AMQP message 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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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 class="section" id="benefits">
+<h2>1.2. Benefits<a class="headerlink" href="#benefits" title="Permalink to this headline">.</a></h2>
+<p>Simplifies connectivity</p>
+<ul class="simple">
+<li>An endpoint can do all of its messaging through a single transport connection</li>
+<li>Avoid opening holes in firewalls for incoming connections</li>
+</ul>
+<p>Provides messaging connectivity where there is no TCP/IP connectivity</p>
+<ul class="simple">
+<li>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).</li>
+</ul>
+<p>Simplifies reliability</p>
+<ul class="simple">
+<li>Reliability and availability are provided using redundant topology, not server clustering</li>
+<li>Reliable end-to-end messaging without persistent stores</li>
+<li>Use a message broker only when you need store-and-forward semantics</li>
+</ul>
+</div>
+<div class="section" id="features">
+<h2>1.3. Features<a class="headerlink" href="#features" title="Permalink to this headline">.</a></h2>
+<ul class="simple">
+<li>Can be deployed stand-alone or in a network of routers
+- Supports arbitrary network topology - no restrictions on redundancy
+- Automatic route computation - adjusts quickly to changes in topology</li>
+<li>Provides remote access to brokers or other AMQP servers</li>
+<li>Security</li>
+</ul>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/link_routing.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/link_routing.html b/content/releases/qpid-dispatch-0.6.0/book/link_routing.html
new file mode 100644
index 0000000..76de42f
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/link_routing.html
@@ -0,0 +1,275 @@
+<!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>2.4. Link Routing. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>2.4. Link Routing.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="link-routing">
+<h1>2.4. Link Routing<a class="headerlink" href="#link-routing" title="Permalink to this headline">.</a></h1>
+<p>This feature was introduced in Qpid Dispatch 0.4.
+This feature was significantly updated in Qpid Dispatch 0.6.</p>
+<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>
+<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>
+<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 class="highlight-python"><div class="highlight"><pre><span></span> Public Network
+ +-----------------+
+ | +-----+ |
+ | B1 | Rp | |
+ | +/--\-+ |
+ | / \ |
+ | / \ |
+ +----/--------\---+
+ / \
+ / \
+ / \
+ Private Net A / \ Private Net B
++--------------/--+ +---\-------------+
+| +---/-+ | | +--\--+ |
+| B2 | Ra | | | | Rb | C1 |
+| +-----+ | | +-----+ |
+| | | |
+| | | |
++-----------------+ +-----------------+
+</pre></div>
+</div>
+<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>
+<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>
+<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>
+<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 class="section" id="configuration">
+<h2>2.4.1. Configuration<a class="headerlink" href="#configuration" title="Permalink to this headline">.</a></h2>
+<p>Starting with the configured topology shown above, how is link-routing
+configured to support the example described above?</p>
+<p>First, router Ra needs to be told how to make a connection to the
+broker B2:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>connector {
+ name: broker
+ role: route-container
+ host: <B2-url>
+ port: <B2-port>
+ sasl-mechanisms: ANONYMOUS
+}
+</pre></div>
+</div>
+<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>
+<p>Now, the router must be configured to route certain addresses to B2:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>linkRoute {
+ prefix: b2
+ dir: in
+ connection: broker
+}
+
+linkRoute {
+ prefix: b2
+ dir: out
+ connection: broker
+}
+</pre></div>
+</div>
+<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>
+<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>
+<dl class="docutils">
+<dt>Examples of addresses that “begin with ‘b2’” include:</dt>
+<dd><ul class="first last simple">
+<li>b2</li>
+<li>b2.queues</li>
+<li>b2.queues.app1</li>
+</ul>
+</dd>
+</dl>
+<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>
+<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>
+<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>
+<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>
+
+
+
+ <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
[5/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/tools.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/tools.html b/content/releases/qpid-dispatch-0.6.0/book/tools.html
new file mode 100644
index 0000000..2e43915
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/tools.html
@@ -0,0 +1,220 @@
+<!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>2.2. Tools. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>2.2. Tools.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="tools">
+<h1>2.2. Tools<a class="headerlink" href="#tools" title="Permalink to this headline">.</a></h1>
+<div class="section" id="qdstat">
+<h2>2.2.1. qdstat<a class="headerlink" href="#qdstat" title="Permalink to this headline">.</a></h2>
+<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>
+<table border="1" class="docutils">
+<colgroup>
+<col width="15%" />
+<col width="85%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Option</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>-l</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>-a</td>
+<td>Print a list of addresses known to the router.</td>
+</tr>
+<tr class="row-even"><td>-n</td>
+<td>Print a list of known routers in the network.</td>
+</tr>
+<tr class="row-odd"><td>-c</td>
+<td>Print a list of connections to the router.</td>
+</tr>
+<tr class="row-even"><td>–autolinks</td>
+<td>Print a list of configured auto-links.</td>
+</tr>
+<tr class="row-odd"><td>–linkroutes</td>
+<td>Print a list of configures link-routes.</td>
+</tr>
+</tbody>
+</table>
+<p>For complete details see the <cite>qdstat(8)</cite> man page and the output of
+<cite>qdstat –help</cite>.</p>
+</div>
+<div class="section" id="qdmanage">
+<h2>2.2.2. qdmanage<a class="headerlink" href="#qdmanage" title="Permalink to this headline">.</a></h2>
+<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>
+<p>For example you can query all the connection entities in the router:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage query --type connection
+</pre></div>
+</div>
+<p>To enable logging debug and higher level messages by default:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage update log/DEFAULT enable=debug+
+</pre></div>
+</div>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage create type=listener port=5555
+</pre></div>
+</div>
+<p>Now you can connect to port 5555, for exampple:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage query -b localhost:5555 --type listener
+</pre></div>
+</div>
+<p>For complete details see the <cite>qdmanage(8)</cite> man page and the output of
+<cite>qdmanage –help</cite>. Also for details of what can be configured see the
+<cite>qdrouterd.conf(5)</cite> man page.</p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/using.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/using.html b/content/releases/qpid-dispatch-0.6.0/book/using.html
new file mode 100644
index 0000000..b74bae3
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/using.html
@@ -0,0 +1,176 @@
+<!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>2. Using Qpid Dispatch. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>2. Using Qpid Dispatch.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="using-qpid-dispatch">
+<h1>2. Using Qpid Dispatch<a class="headerlink" href="#using-qpid-dispatch" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="default_config.html">2.1. Configuration</a></li>
+<li class="toctree-l1"><a class="reference internal" href="tools.html">2.2. Tools</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="tools.html#qdstat">2.2.1. qdstat</a></li>
+<li class="toctree-l2"><a class="reference internal" href="tools.html#qdmanage">2.2.2. qdmanage</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="basic_usage.html">2.3. Basic Usage and Examples</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</a></li>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#mobile-subscribers">2.3.2. Mobile Subscribers</a></li>
+<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#dynamic-reply-to">2.3.3. Dynamic Reply-To</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="link_routing.html">2.4. Link Routing</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="link_routing.html#configuration">2.4.1. Configuration</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="auto_links.html">2.5. Indirect Waypoints and Auto-Links</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html#queue-waypoint-example">2.5.1. Queue Waypoint Example</a></li>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html#sharded-queue-example">2.5.2. Sharded Queue Example</a></li>
+<li class="toctree-l2"><a class="reference internal" href="auto_links.html#dynamically-adding-shards">2.5.3. Dynamically Adding Shards</a></li>
+</ul>
+</li>
+</ul>
+</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/ac1c1663/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
new file mode 100644
index 0000000..53cd7a8
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.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.6.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">Java broker</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.6.0</li></ul>
+
+ <div id="-middle-content">
+ <h1 id="qpid-dispatch-060">Qpid Dispatch 0.6.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.6.0/qpid-dispatch-0.6.0.tar.gz">qpid-dispatch-0.6.0.tar.gz</a></td>
+ <td><a href="http://archive.apache.org/dist/qpid/dispatch/0.6.0/qpid-dispatch-0.6.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.6.0">Installing Qpid Dispatch</a></li>
+<li><a href="book/book.html">Dispatch router book</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.6.0">All release artefacts</a></li>
+<li><a href="https://issues.apache.org/jira/issues/?jql=project+%3D+DISPATCH+AND+fixVersion+%3D+%270.6.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.6.0">Source repository tag</a></li>
+</ul>
+
+<script type="text/javascript">
+ _deferredFunctions.push(function() {
+ if ("0.6.0" === "0.5") {
+ _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/ac1c1663/content/releases/qpid-dispatch-0.6.0/man/qdmanage.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/man/qdmanage.html b/content/releases/qpid-dispatch-0.6.0/man/qdmanage.html
new file mode 100644
index 0000000..f753641
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/man/qdmanage.html
@@ -0,0 +1,283 @@
+<!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>qdmanage manual page. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>qdmanage manual page.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="qdmanage-manual-page">
+<h1>qdmanage manual page<a class="headerlink" href="#qdmanage-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdmanage <em>operation</em> [<em>options...</em>] [<em>arguments...</em>]</p>
+</div>
+<div class="section" id="description">
+<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<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 class="section" id="operations">
+<h2>Operations<a class="headerlink" href="#operations" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt><cite>query</cite> [<em>ATTR</em>...]</dt>
+<dd>Print the attributes named in the ATTR list or all attributes if
+none are listed. Print attributes for all entities by default, use
+–type, –name and –identity options to restrict what is printed.</dd>
+<dt><cite>create</cite> [<em>ATTR=VALUE</em>...]</dt>
+<dd>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 entitiees.</dd>
+<dt><cite>read</cite></dt>
+<dd>Print the attributes of an entity specified by the –name or
+–identity options. With the –stdin option, create entities based
+on data from stdin. This can be a JSON map of attributes to create a
+single entity, or a JSON list of maps to create multiple entitiees.</dd>
+<dt><cite>update</cite> [<em>ATTR=VALUE</em>...]</dt>
+<dd>Update the attributes of an existing 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 entitiees. If an ATTR name is listed with no =VALUE,
+that attribute will be deleted from the entity.</dd>
+<dt><cite>delete</cite></dt>
+<dd>Delete an entity specified by the –name or –identity options.</dd>
+<dt><cite>get-types</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their base types. With no arguments list all
+types.</dd>
+<dt><cite>get-operations</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their operations. With no arguments list all
+types.</dd>
+<dt><cite>get-attributes</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their attributes. With no arguments list all
+types.</dd>
+<dt><cite>get-annotations</cite> [<em>TYPE</em>]</dt>
+<dd>List entity types with their annotations. With no arguments list all
+types.</dd>
+<dt><cite>get-mgmt-nodes</cite></dt>
+<dd>List all other known management nodes connected to this one.</dd>
+<dt><cite>get-json-schema</cite> [<em>INDENT</em>]</dt>
+<dd>Get the router schema in JSON format. Optional integer indent for
+formatted output.</dd>
+<dt><cite>get-log</cite> [<em>INDENT</em>]</dt>
+<dd>Get recent log entries from the router.</dd>
+</dl>
+</div>
+<div class="section" id="options">
+<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
+<p>-h, –help
+: show this help message and exit</p>
+<p>–version
+: Print version and exit.</p>
+<p>–type=TYPE
+: Type of entity to operate on.</p>
+<p>–name=NAME
+: Name of entity to operate on.</p>
+<p>–identity=ID
+: Identity of entity to operate on.</p>
+<p>–indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print</p>
+<p>–stdin
+: Read attributes as JSON map or list of maps from</p>
+<p>–body=BODY
+: JSON value to use as body of a non-standard operation</p>
+<p>–properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p>
+<div class="section" id="connection-options">
+<h3>Connection Options<a class="headerlink" href="#connection-options" title="Permalink to this headline">.</a></h3>
+<p>-b URL, –bus=URL
+: URL of the messaging bus to connect to (default</p>
+<p>-r ROUTER-ID, –router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, –timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>–ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>–ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>–ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>–ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+</div>
+</div>
+<div class="section" id="files">
+<h2>Files<a class="headerlink" href="#files" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt>/usr/local/share/doc/qpid-dispatch/qdrouter.json</dt>
+<dd>Management schema for qdrouterd.</dd>
+<dt>/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt</dt>
+<dd>Explanation of the management schema.</dd>
+</dl>
+</div>
+<div class="section" id="examples">
+<h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">.</a></h2>
+<p>Show the logging configuration</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage query --type=log
+</pre></div>
+</div>
+<p>Enable debug and higher log messages by default:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/DEFAULT enable=debug+
+</pre></div>
+</div>
+<p>Enable trace log messages only for the MESSAGE moudle and direct MESSAGE
+logs to the file “test.log”</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log
+</pre></div>
+</div>
+<p>Set MESSAGE logging back to the default:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=default
+</pre></div>
+</div>
+<p>Disable MESSAGE logging:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=none
+</pre></div>
+</div>
+</div>
+<div class="section" id="see-also">
+<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html b/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html
new file mode 100644
index 0000000..5fe680f
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html
@@ -0,0 +1,549 @@
+<!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>qdrouterd.conf manual page. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>qdrouterd.conf manual page.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="qdrouterd-conf-manual-page">
+<h1>qdrouterd.conf manual page<a class="headerlink" href="#qdrouterd-conf-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdroutered.conf is the configuration file for the dispatch router.</p>
+</div>
+<div class="section" id="description">
+<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<p>The configuration file is made up of sections with this syntax:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>SECTION-NAME {
+ ATTRIBUTE-NAME: ATTRIBUTE-VALUE
+ ATTRIBUTE-NAME: ATTRIBUTE-VALUE
+ ...
+}
+</pre></div>
+</div>
+<p>There are two types of sections:</p>
+<p><em>Configuration sections</em> correspond to configuration entities. They can be queried and
+configured via management tools as well as via the configuration file.</p>
+<p><em>Annotation sections</em> define a group of attribute values that can be included in
+one or more entity sections.</p>
+<p>For example you can define an “ssl-profile” annotation section with SSL credentials
+that can be included in multiple “listener” entities. Here’s an example, note
+how the ‘ssl-profile’ attribute of ‘listener’ sections references the ‘name’
+attribute of ‘ssl-profile’ sections.</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>ssl-profile {
+ name: ssl-profile-one
+ cert-db: ca-certificate-1.pem
+ cert-file: server-certificate-1.pem
+ key-file: server-private-key.pem
+}
+
+listener {
+ ssl-profile: ssl-profile-one
+ host: 0.0.0.0
+ port: 20102
+ sasl-mechanisms: ANONYMOUS
+}
+</pre></div>
+</div>
+</div>
+<div class="section" id="annotation-sections">
+<h2>Annotation Sections<a class="headerlink" href="#annotation-sections" title="Permalink to this headline">.</a></h2>
+<div class="section" id="addrport">
+<h3>addrPort<a class="headerlink" href="#addrport" title="Permalink to this headline">.</a></h3>
+<p>Attributes for internet address and port.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+</dl>
+</div>
+<div class="section" id="connectionrole">
+<h3>connectionRole<a class="headerlink" href="#connectionrole" title="Permalink to this headline">.</a></h3>
+<p>Attribute for the role of a connection.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl class="docutils">
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+</dl>
+</div>
+<div class="section" id="sslprofile">
+<h3>sslProfile<a class="headerlink" href="#sslprofile" title="Permalink to this headline">.</a></h3>
+<p>Attributes for setting TLS/SSL configuration for connections.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl class="docutils">
+<dt><em>certDb</em> (path)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="configuration-sections">
+<h2>Configuration Sections<a class="headerlink" href="#configuration-sections" title="Permalink to this headline">.</a></h2>
+<div class="section" id="container">
+<h3>container<a class="headerlink" href="#container" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p>
+<dl class="docutils">
+<dt><em>containerName</em> (string)</dt>
+<dd>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.</dd>
+<dt><em>workerThreads</em> (integer, default=4)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="router">
+<h3>router<a class="headerlink" href="#router" title="Permalink to this headline">.</a></h3>
+<p>Tracks peer routers and computes routes to destinations.</p>
+<dl class="docutils">
+<dt><em>routerId</em> (string)</dt>
+<dd>(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead</dd>
+<dt><em>id</em> (string)</dt>
+<dd>Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId</dd>
+<dt><em>mode</em> (One of [‘standalone’, ‘interior’], default=’standalone’)</dt>
+<dd>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.</dd>
+<dt><em>helloInterval</em> (integer, default=1)</dt>
+<dd>Interval in seconds between HELLO messages sent to neighbor routers.</dd>
+<dt><em>helloMaxAge</em> (integer, default=3)</dt>
+<dd>Time in seconds after which a neighbor is declared lost if no HELLO is received.</dd>
+<dt><em>raInterval</em> (integer, default=30)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers in a stable network.</dd>
+<dt><em>raIntervalFlux</em> (integer, default=4)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.</dd>
+<dt><em>remoteLsMaxAge</em> (integer, default=60)</dt>
+<dd>Time in seconds after which link state is declared stale if no RA is received.</dd>
+<dt><em>mobileAddrMaxAge</em> (integer, default=60)</dt>
+<dd>(DEPRECATED) This value is no longer used in the router.</dd>
+<dt><em>workerThreads</em> (integer, default=4)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string, default=’qdrouterd’)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="listener">
+<h3>listener<a class="headerlink" href="#listener" title="Permalink to this headline">.</a></h3>
+<p>Listens for incoming connections to the router.</p>
+<p>Annotations: <strong>addrPort</strong>, <strong>connectionRole</strong>, <strong>sslProfile</strong>.</p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>saslMechanisms</em> (string)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>authenticatePeer</em> (boolean)</dt>
+<dd>yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.</dd>
+<dt><em>requireEncryption</em> (boolean)</dt>
+<dd>yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer</dd>
+<dt><em>requireSsl</em> (boolean)</dt>
+<dd>yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.</dd>
+<dt><em>trustedCerts</em> (path)</dt>
+<dd>This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide a path to a PEM file that contains the trusted certificates.</dd>
+<dt><em>maxFrameSize</em> (integer, default=16384)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16)</dt>
+<dd>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.</dd>
+<dt><em>requirePeerAuth</em> (boolean)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>allowUnsecured</em> (boolean)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the requireEncryption attribute.</dd>
+<dt><em>allowNoSasl</em> (boolean)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="connector">
+<h3>connector<a class="headerlink" href="#connector" title="Permalink to this headline">.</a></h3>
+<p>Establishes an outgoing connection from the router.</p>
+<p>Annotations: <strong>addrPort</strong>, <strong>connectionRole</strong>, <strong>sslProfile</strong>.</p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>saslMechanisms</em> (string)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>allowRedirect</em> (boolean, default=True)</dt>
+<dd>Allow the peer to redirect this connection to another address.</dd>
+<dt><em>maxFrameSize</em> (integer, default=65536)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16)</dt>
+<dd>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.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer)</dt>
+<dd>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.</dd>
+<dt><em>verifyHostName</em> (boolean, default=True)</dt>
+<dd>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</dd>
+<dt><em>saslUsername</em> (string)</dt>
+<dd>The user name that the connector is using to connect to a peer.</dd>
+<dt><em>saslPassword</em> (string)</dt>
+<dd>The password that the connector is using to connect to a peer.</dd>
+</dl>
+</div>
+<div class="section" id="log">
+<h3>log<a class="headerlink" href="#log" title="Permalink to this headline">.</a></h3>
+<p>Configure logging for a particular module. You can use the <cite>UPDATE</cite> operation to change log settings while the router is running.</p>
+<dl class="docutils">
+<dt><em>module</em> (One of [‘ROUTER’, ‘ROUTER_CORE’, ‘ROUTER_HELLO’, ‘ROUTER_LS’, ‘ROUTER_MA’, ‘MESSAGE’, ‘SERVER’, ‘AGENT’, ‘CONTAINER’, ‘CONFIG’, ‘ERROR’, ‘DISPATCH’, ‘POLICY’, ‘DEFAULT’], required)</dt>
+<dd>Module to configure. The special module ‘DEFAULT’ specifies defaults for all modules.</dd>
+<dt><em>enable</em> (string, default=’default’, required)</dt>
+<dd>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 ‘+’ to enable that level and above. For example ‘trace,debug,warning+’ means enable trace, debug, warning, error and critical. The value ‘none’ means disable logging for the module. The value ‘default’ means use the value from the DEFAULT module.</dd>
+<dt><em>timestamp</em> (boolean)</dt>
+<dd>Include timestamp in log messages.</dd>
+<dt><em>source</em> (boolean)</dt>
+<dd>Include source file and line number in log messages.</dd>
+<dt><em>output</em> (string)</dt>
+<dd>Where to send log messages. Can be ‘stderr’, ‘syslog’ or a file name.</dd>
+</dl>
+</div>
+<div class="section" id="fixedaddress">
+<h3>fixedAddress<a class="headerlink" href="#fixedaddress" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>The address prefix (always starting with ‘/’).</dd>
+<dt><em>phase</em> (integer)</dt>
+<dd>The phase of a multi-hop address passing through one or more waypoints.</dd>
+<dt><em>fanout</em> (One of [‘multiple’, ‘single’], default=’multiple’)</dt>
+<dd>One of ‘multiple’ or ‘single’. 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.</dd>
+<dt><em>bias</em> (One of [‘closest’, ‘spread’], default=’closest’)</dt>
+<dd>Only if fanout is single. One of ‘closest’ or ‘spread’. 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.</dd>
+</dl>
+</div>
+<div class="section" id="waypoint">
+<h3>waypoint<a class="headerlink" href="#waypoint" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p>
+<dl class="docutils">
+<dt><em>address</em> (string, required)</dt>
+<dd>The AMQP address of the waypoint.</dd>
+<dt><em>connector</em> (string, required)</dt>
+<dd>The name of the on-demand connector used to reach the waypoint’s container.</dd>
+<dt><em>inPhase</em> (integer, default=-1)</dt>
+<dd>The phase of the address as it is routed _to_ the waypoint.</dd>
+<dt><em>outPhase</em> (integer, default=-1)</dt>
+<dd>The phase of the address as it is routed _from_ the waypoint.</dd>
+</dl>
+</div>
+<div class="section" id="linkroutepattern">
+<h3>linkRoutePattern<a class="headerlink" href="#linkroutepattern" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>An address prefix to match against target and source addresses. This pattern must be of the form ‘<text>.<text1>.<textN>’ or ‘<text>’ or ‘<text>.’ 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 ‘org.apache’ (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</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’, ‘both’], default=’both’)</dt>
+<dd>Link direction for match: ‘in’ matches only links inbound to the client; ‘out’ matches only links outbound from the client; ‘both’ matches any link.</dd>
+<dt><em>connector</em> (string)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="address">
+<h3>address<a class="headerlink" href="#address" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>distribution</em> (One of [‘multicast’, ‘closest’, ‘balanced’], default=’balanced’)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>waypoint</em> (boolean)</dt>
+<dd>Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.</dd>
+<dt><em>ingressPhase</em> (integer)</dt>
+<dd>Advanced - Override the ingress phase for this address</dd>
+<dt><em>egressPhase</em> (integer)</dt>
+<dd>Advanced - Override the egress phase for this address</dd>
+</dl>
+</div>
+<div class="section" id="linkroute">
+<h3>linkRoute<a class="headerlink" href="#linkroute" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>containerId</em> (string)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string)</dt>
+<dd>The name from a connector or listener</dd>
+<dt><em>distribution</em> (One of [‘linkBalanced’], default=’linkBalanced’)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required)</dt>
+<dd>The permitted direction of links: ‘in’ means client senders; ‘out’ means client receivers</dd>
+</dl>
+</div>
+<div class="section" id="autolink">
+<h3>autoLink<a class="headerlink" href="#autolink" title="Permalink to this headline">.</a></h3>
+<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>
+<dl class="docutils">
+<dt><em>addr</em> (string, required)</dt>
+<dd>The address of the provisioned object</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required)</dt>
+<dd>The direction of the link to be created. In means into the router, out means out of the router.</dd>
+<dt><em>phase</em> (integer)</dt>
+<dd>The address phase for this link. Defaults to ‘0’ for ‘out’ links and ‘1’ for ‘in’ links.</dd>
+<dt><em>containerId</em> (string)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string)</dt>
+<dd>The name from a connector or listener</dd>
+</dl>
+</div>
+<div class="section" id="console">
+<h3>console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h3>
+<p>Start a websocket/tcp proxy and http file server to serve the web console</p>
+</div>
+<div class="section" id="policy">
+<h3>policy<a class="headerlink" href="#policy" title="Permalink to this headline">.</a></h3>
+<p>Defines global connection limit</p>
+<dl class="docutils">
+<dt><em>maximumConnections</em> (integer)</dt>
+<dd>Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.</dd>
+<dt><em>enableAccessRules</em> (boolean)</dt>
+<dd>Enable user rule set processing and connection denial.</dd>
+<dt><em>policyFolder</em> (path)</dt>
+<dd>The path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.</dd>
+<dt><em>defaultApplication</em> (string)</dt>
+<dd>Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.</dd>
+<dt><em>defaultApplicationEnabled</em> (boolean)</dt>
+<dd>Enable defaultApplication policy fallback logic.</dd>
+</dl>
+</div>
+<div class="section" id="policyruleset">
+<h3>policyRuleset<a class="headerlink" href="#policyruleset" title="Permalink to this headline">.</a></h3>
+<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p>
+<dl class="docutils">
+<dt><em>maxConnections</em> (integer)</dt>
+<dd>Maximum number of concurrent client connections allowed. Zero implies no limit.</dd>
+<dt><em>maxConnPerUser</em> (integer)</dt>
+<dd>Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.</dd>
+<dt><em>maxConnPerHost</em> (integer)</dt>
+<dd>Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.</dd>
+<dt><em>userGroups</em> (map)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed ‘restricted’. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.</dd>
+<dt><em>ingressHostGroups</em> (map)</dt>
+<dd>A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address ‘*’ represents any host address.</dd>
+<dt><em>ingressPolicies</em> (map)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.</dd>
+<dt><em>connectionAllowDefault</em> (boolean)</dt>
+<dd>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 ‘default’ user group and receive ‘default’ settings.</dd>
+<dt><em>settings</em> (map)</dt>
+<dd>A map where each key is a user group name and the value is a map of the corresponding settings for that group.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="see-also">
+<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</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/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/schema.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/schema.html b/content/releases/qpid-dispatch-0.6.0/book/schema.html
new file mode 100644
index 0000000..a806b54
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/schema.html
@@ -0,0 +1,1012 @@
+<!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>3.4. Management Schema. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>3.4. Management Schema.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="management-schema">
+<h1>3.4. Management Schema<a class="headerlink" href="#management-schema" title="Permalink to this headline">.</a></h1>
+<p>This chapter documents the set of <em>management entity types</em> that define
+configuration and management of a Dispatch Router. A management entity type has
+a set of <em>attributes</em> that can be read, some attributes can also be
+updated. Some entity types also support <em>operations</em> that can be called.</p>
+<p>All management entity types have the following standard attributes:</p>
+<dl class="docutils">
+<dt><em>type</em></dt>
+<dd>The fully qualified type of the entity,
+e.g. <cite>org.apache.qpid.dispatch.router</cite>. This document uses the short name
+without the <cite>org.apache.qpid.dispatch</cite> prefix e.g. <cite>router</cite>. The dispatch
+tools will accept the short or long name.</dd>
+<dt><em>name</em></dt>
+<dd>A user-generated identity for the entity. This can be used in other entities
+that need to refer to the named entity.</dd>
+<dt><em>identity</em></dt>
+<dd>A system-generated identity of the entity. It includes
+the short type name and some identifying information. E.g. <cite>log/AGENT</cite> or
+<cite>listener/localhost:amqp</cite></dd>
+</dl>
+<p>There are two main categories of management entity type.</p>
+<dl class="docutils">
+<dt><em>Configuration</em> Entities</dt>
+<dd>Parameters that can be set in the configuration file
+(see <cite>qdrouterd.conf(5)</cite> man page) or set at run-time with the <cite>qdmanage(8)</cite>
+tool.</dd>
+<dt><em>Operational</em> Entities</dt>
+<dd>Run-time status values that can be queried using <cite>qdstat(8)</cite> or <cite>qdmanage(8)</cite> tools.</dd>
+</dl>
+<div class="section" id="configuration-entities">
+<h2>3.4.1. Configuration Entities<a class="headerlink" href="#configuration-entities" title="Permalink to this headline">.</a></h2>
+<p>Configuration entities define the attributes allowed in the configuration file
+(see <cite>qdrouterd.conf(5)</cite>) but you can also create entities once the router is
+running using the <cite>qdrouterd(8)</cite> tool’s <cite>create</cite> operation. Some entities can also
+be modified using the <cite>update</cite> operation, see the entity descriptions below.</p>
+<div class="section" id="container">
+<h3>3.4.1.1. container<a class="headerlink" href="#container" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>containerName</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>workerThreads</em> (integer, default=4, <cite>CREATE</cite>)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path, <cite>CREATE</cite>)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path, <cite>CREATE</cite>)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="router">
+<h3>3.4.1.2. router<a class="headerlink" href="#router" title="Permalink to this headline">.</a></h3>
+<p>Tracks peer routers and computes routes to destinations.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>routerId</em> (string, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead</dd>
+<dt><em>id</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId</dd>
+<dt><em>mode</em> (One of [‘standalone’, ‘interior’], default=’standalone’, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>area</em> (string)</dt>
+<dd>Unused placeholder.</dd>
+<dt><em>helloInterval</em> (integer, default=1, <cite>CREATE</cite>)</dt>
+<dd>Interval in seconds between HELLO messages sent to neighbor routers.</dd>
+<dt><em>helloMaxAge</em> (integer, default=3, <cite>CREATE</cite>)</dt>
+<dd>Time in seconds after which a neighbor is declared lost if no HELLO is received.</dd>
+<dt><em>raInterval</em> (integer, default=30, <cite>CREATE</cite>)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers in a stable network.</dd>
+<dt><em>raIntervalFlux</em> (integer, default=4, <cite>CREATE</cite>)</dt>
+<dd>Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.</dd>
+<dt><em>remoteLsMaxAge</em> (integer, default=60, <cite>CREATE</cite>)</dt>
+<dd>Time in seconds after which link state is declared stale if no RA is received.</dd>
+<dt><em>mobileAddrMaxAge</em> (integer, default=60, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This value is no longer used in the router.</dd>
+<dt><em>addrCount</em> (integer)</dt>
+<dd>Number of addresses known to the router.</dd>
+<dt><em>linkCount</em> (integer)</dt>
+<dd>Number of links attached to the router node.</dd>
+<dt><em>nodeCount</em> (integer)</dt>
+<dd>Number of known peer router nodes.</dd>
+<dt><em>workerThreads</em> (integer, default=4, <cite>CREATE</cite>)</dt>
+<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd>
+<dt><em>debugDump</em> (path, <cite>CREATE</cite>)</dt>
+<dd>A file to dump debugging information that can’t be logged normally.</dd>
+<dt><em>saslConfigPath</em> (path, <cite>CREATE</cite>)</dt>
+<dd>Absolute path to the SASL configuration file.</dd>
+<dt><em>saslConfigName</em> (string, default=’qdrouterd’, <cite>CREATE</cite>)</dt>
+<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd>
+</dl>
+</div>
+<div class="section" id="listener">
+<h3>3.4.1.3. listener<a class="headerlink" href="#listener" title="Permalink to this headline">.</a></h3>
+<p>Listens for incoming connections to the router.</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’, <cite>CREATE</cite>)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’], <cite>CREATE</cite>)</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’, <cite>CREATE</cite>)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>sslProfileName</em> (string)</dt>
+<dd>The name of the ssl profile</dd>
+<dt><em>saslMechanisms</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>authenticatePeer</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.</dd>
+<dt><em>requireEncryption</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer</dd>
+<dt><em>requireSsl</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.</dd>
+<dt><em>trustedCerts</em> (path, <cite>CREATE</cite>)</dt>
+<dd>This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide a path to a PEM file that contains the trusted certificates.</dd>
+<dt><em>maxFrameSize</em> (integer, default=16384, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>requirePeerAuth</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>allowUnsecured</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the requireEncryption attribute.</dd>
+<dt><em>allowNoSasl</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’, <cite>CREATE</cite>)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="connector">
+<h3>3.4.1.4. connector<a class="headerlink" href="#connector" title="Permalink to this headline">.</a></h3>
+<p>Establishes an outgoing connection from the router.</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>addr</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd>
+<dt><em>host</em> (string, default=‘127.0.0.1’, <cite>CREATE</cite>)</dt>
+<dd>IP address: ipv4 or ipv6 literal or a host name</dd>
+<dt><em>port</em> (string, default=’amqp’, <cite>CREATE</cite>)</dt>
+<dd>Port number or symbolic service name.</dd>
+<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’], <cite>CREATE</cite>)</dt>
+<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
+<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>cost</em> (integer, default=‘1’, <cite>CREATE</cite>)</dt>
+<dd>For the ‘inter-router’ 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.</dd>
+<dt><em>certDb</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
+<dt><em>certFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd>
+<dt><em>keyFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd>
+<dt><em>passwordFile</em> (path, <cite>CREATE</cite>)</dt>
+<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd>
+<dt><em>password</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd>
+<dt><em>uidFormat</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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 ‘cou’ 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 ‘o2’ 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 comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi
th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd>
+<dt><em>displayNameFile</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The path to the file containing the unique id to dispay name mapping</dd>
+<dt><em>sslProfileName</em> (string)</dt>
+<dd>The name of the ssl profile</dd>
+<dt><em>saslMechanisms</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Comma separated list of accepted SASL authentication mechanisms.</dd>
+<dt><em>allowRedirect</em> (boolean, default=True, <cite>CREATE</cite>)</dt>
+<dd>Allow the peer to redirect this connection to another address.</dd>
+<dt><em>maxFrameSize</em> (integer, default=65536, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>idleTimeoutSeconds</em> (integer, default=16, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’, <cite>CREATE</cite>)</dt>
+<dd>[‘in’, ‘out’, ‘both’, ‘no’] 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</dd>
+<dt><em>linkCapacity</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+<dt><em>verifyHostName</em> (boolean, default=True, <cite>CREATE</cite>)</dt>
+<dd>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</dd>
+<dt><em>saslUsername</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The user name that the connector is using to connect to a peer.</dd>
+<dt><em>saslPassword</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The password that the connector is using to connect to a peer.</dd>
+</dl>
+</div>
+<div class="section" id="log">
+<h3>3.4.1.5. log<a class="headerlink" href="#log" title="Permalink to this headline">.</a></h3>
+<p>Configure logging for a particular module. You can use the <cite>UPDATE</cite> operation to change log settings while the router is running.</p>
+<p>Operations allowed: <cite>UPDATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>module</em> (One of [‘ROUTER’, ‘ROUTER_CORE’, ‘ROUTER_HELLO’, ‘ROUTER_LS’, ‘ROUTER_MA’, ‘MESSAGE’, ‘SERVER’, ‘AGENT’, ‘CONTAINER’, ‘CONFIG’, ‘ERROR’, ‘DISPATCH’, ‘POLICY’, ‘DEFAULT’], required, <cite>UPDATE</cite>)</dt>
+<dd>Module to configure. The special module ‘DEFAULT’ specifies defaults for all modules.</dd>
+<dt><em>enable</em> (string, default=’default’, required, <cite>UPDATE</cite>)</dt>
+<dd>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 ‘+’ to enable that level and above. For example ‘trace,debug,warning+’ means enable trace, debug, warning, error and critical. The value ‘none’ means disable logging for the module. The value ‘default’ means use the value from the DEFAULT module.</dd>
+<dt><em>timestamp</em> (boolean, <cite>UPDATE</cite>)</dt>
+<dd>Include timestamp in log messages.</dd>
+<dt><em>source</em> (boolean, <cite>UPDATE</cite>)</dt>
+<dd>Include source file and line number in log messages.</dd>
+<dt><em>output</em> (string, <cite>UPDATE</cite>)</dt>
+<dd>Where to send log messages. Can be ‘stderr’, ‘syslog’ or a file name.</dd>
+</dl>
+</div>
+<div class="section" id="fixedaddress">
+<h3>3.4.1.6. fixedAddress<a class="headerlink" href="#fixedaddress" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address prefix (always starting with ‘/’).</dd>
+<dt><em>phase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>The phase of a multi-hop address passing through one or more waypoints.</dd>
+<dt><em>fanout</em> (One of [‘multiple’, ‘single’], default=’multiple’, <cite>CREATE</cite>)</dt>
+<dd>One of ‘multiple’ or ‘single’. 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.</dd>
+<dt><em>bias</em> (One of [‘closest’, ‘spread’], default=’closest’, <cite>CREATE</cite>)</dt>
+<dd>Only if fanout is single. One of ‘closest’ or ‘spread’. 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.</dd>
+</dl>
+</div>
+<div class="section" id="waypoint">
+<h3>3.4.1.7. waypoint<a class="headerlink" href="#waypoint" title="Permalink to this headline">.</a></h3>
+<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>address</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The AMQP address of the waypoint.</dd>
+<dt><em>connector</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The name of the on-demand connector used to reach the waypoint’s container.</dd>
+<dt><em>inPhase</em> (integer, default=-1, <cite>CREATE</cite>)</dt>
+<dd>The phase of the address as it is routed _to_ the waypoint.</dd>
+<dt><em>outPhase</em> (integer, default=-1, <cite>CREATE</cite>)</dt>
+<dd>The phase of the address as it is routed _from_ the waypoint.</dd>
+</dl>
+</div>
+<div class="section" id="linkroutepattern">
+<h3>3.4.1.8. linkRoutePattern<a class="headerlink" href="#linkroutepattern" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>An address prefix to match against target and source addresses. This pattern must be of the form ‘<text>.<text1>.<textN>’ or ‘<text>’ or ‘<text>.’ 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 ‘org.apache’ (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</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’, ‘both’], default=’both’, <cite>CREATE</cite>)</dt>
+<dd>Link direction for match: ‘in’ matches only links inbound to the client; ‘out’ matches only links outbound from the client; ‘both’ matches any link.</dd>
+<dt><em>connector</em> (string, <cite>CREATE</cite>)</dt>
+<dd>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.</dd>
+</dl>
+</div>
+<div class="section" id="address">
+<h3>3.4.1.9. address<a class="headerlink" href="#address" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>distribution</em> (One of [‘multicast’, ‘closest’, ‘balanced’], default=’balanced’, <cite>CREATE</cite>)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>waypoint</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.</dd>
+<dt><em>ingressPhase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Advanced - Override the ingress phase for this address</dd>
+<dt><em>egressPhase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Advanced - Override the egress phase for this address</dd>
+</dl>
+</div>
+<div class="section" id="linkroute">
+<h3>3.4.1.10. linkRoute<a class="headerlink" href="#linkroute" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>prefix</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address prefix for the configured settings</dd>
+<dt><em>containerId</em> (string, <cite>CREATE</cite>)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The name from a connector or listener</dd>
+<dt><em>distribution</em> (One of [‘linkBalanced’], default=’linkBalanced’, <cite>CREATE</cite>)</dt>
+<dd>Treatment of traffic associated with the address</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required, <cite>CREATE</cite>)</dt>
+<dd>The permitted direction of links: ‘in’ means client senders; ‘out’ means client receivers</dd>
+<dt><em>operStatus</em> (One of [‘inactive’, ‘active’])</dt>
+<dd>The operational status of this linkRoute: inactive - The remote container is not connected; active - the remote container is connected and ready to accept link routed attachments.</dd>
+</dl>
+</div>
+<div class="section" id="autolink">
+<h3>3.4.1.11. autoLink<a class="headerlink" href="#autolink" title="Permalink to this headline">.</a></h3>
+<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>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>DELETE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>addr</em> (string, required, <cite>CREATE</cite>)</dt>
+<dd>The address of the provisioned object</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’], required, <cite>CREATE</cite>)</dt>
+<dd>The direction of the link to be created. In means into the router, out means out of the router.</dd>
+<dt><em>phase</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>The address phase for this link. Defaults to ‘0’ for ‘out’ links and ‘1’ for ‘in’ links.</dd>
+<dt><em>containerId</em> (string, <cite>CREATE</cite>)</dt>
+<dd>ContainerID for the target container</dd>
+<dt><em>connection</em> (string, <cite>CREATE</cite>)</dt>
+<dd>The name from a connector or listener</dd>
+<dt><em>linkRef</em> (string)</dt>
+<dd>Reference to the org.apache.qpid.dispatch.router.link if the link exists</dd>
+<dt><em>operStatus</em> (One of [‘inactive’, ‘attaching’, ‘failed’, ‘active’, ‘quiescing’, ‘idle’])</dt>
+<dd>The operational status of this autoLink: inactive - The remote container is not connected; attaching - the link is attaching to the remote node; failed - the link attach failed; active - the link is attached and operational; quiescing - the link is transitioning to idle state; idle - the link is attached but there are no deliveries flowing and no unsettled deliveries.</dd>
+<dt><em>lastError</em> (string)</dt>
+<dd>The error description from the last attach failure</dd>
+</dl>
+</div>
+<div class="section" id="console">
+<h3>3.4.1.12. console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h3>
+<p>Start a websocket/tcp proxy and http file server to serve the web console</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>listener</em> (string)</dt>
+<dd>The name of the listener to send the proxied tcp traffic to.</dd>
+<dt><em>wsport</em> (integer, default=5673)</dt>
+<dd>port on which to listen for websocket traffic</dd>
+<dt><em>proxy</em> (string)</dt>
+<dd>The full path to the proxy program to run.</dd>
+<dt><em>home</em> (string)</dt>
+<dd>The full path to the html/css/js files for the console.</dd>
+<dt><em>args</em> (string)</dt>
+<dd>Optional args to pass the proxy program for logging, authentication, etc.</dd>
+</dl>
+</div>
+<div class="section" id="policy">
+<h3>3.4.1.13. policy<a class="headerlink" href="#policy" title="Permalink to this headline">.</a></h3>
+<p>Defines global connection limit</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>maximumConnections</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.</dd>
+<dt><em>enableAccessRules</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>Enable user rule set processing and connection denial.</dd>
+<dt><em>policyFolder</em> (path, <cite>CREATE</cite>)</dt>
+<dd>The path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.</dd>
+<dt><em>defaultApplication</em> (string, <cite>CREATE</cite>)</dt>
+<dd>Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.</dd>
+<dt><em>defaultApplicationEnabled</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>Enable defaultApplication policy fallback logic.</dd>
+</dl>
+<p><em>connectionsProcessed</em> (integer)</p>
+<p><em>connectionsDenied</em> (integer)</p>
+<p><em>connectionsCurrent</em> (integer)</p>
+</div>
+<div class="section" id="policyruleset">
+<h3>3.4.1.14. policyRuleset<a class="headerlink" href="#policyruleset" title="Permalink to this headline">.</a></h3>
+<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p>
+<p>Operations allowed: <cite>CREATE</cite>, <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>applicationName</em> (string, required)</dt>
+<dd>The application name.</dd>
+<dt><em>maxConnections</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Maximum number of concurrent client connections allowed. Zero implies no limit.</dd>
+<dt><em>maxConnPerUser</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.</dd>
+<dt><em>maxConnPerHost</em> (integer, <cite>CREATE</cite>)</dt>
+<dd>Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.</dd>
+<dt><em>userGroups</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed ‘restricted’. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.</dd>
+<dt><em>ingressHostGroups</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address ‘*’ represents any host address.</dd>
+<dt><em>ingressPolicies</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.</dd>
+<dt><em>connectionAllowDefault</em> (boolean, <cite>CREATE</cite>)</dt>
+<dd>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 ‘default’ user group and receive ‘default’ settings.</dd>
+<dt><em>settings</em> (map, <cite>CREATE</cite>)</dt>
+<dd>A map where each key is a user group name and the value is a map of the corresponding settings for that group.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="operational-entities">
+<h2>3.4.2. Operational Entities<a class="headerlink" href="#operational-entities" title="Permalink to this headline">.</a></h2>
+<p>Operational entities provide statistics and other run-time attributes of the router.
+The <cite>qdstat(8)</cite> tool provides a convenient way to query run-time statistics.
+You can also use the general-purpose management tool <cite>qdmanage(8)</cite> to query
+operational attributes.</p>
+<div class="section" id="org-amqp-management">
+<h3>3.4.2.1. org.amqp.management<a class="headerlink" href="#org-amqp-management" title="Permalink to this headline">.</a></h3>
+<p>The standard AMQP management node interface.</p>
+<p>Operations allowed: <cite>QUERY</cite>, <cite>GET-TYPES</cite>, <cite>GET-ANNOTATIONS</cite>, <cite>GET-OPERATIONS</cite>, <cite>GET-ATTRIBUTES</cite>, <cite>GET-MGMT-NODES</cite>, <cite>READ</cite></p>
+<div class="section" id="operation-get-types">
+<h4>3.4.2.1.1. Operation GET-TYPES<a class="headerlink" href="#operation-get-types" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and their inheritance relationships</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of the entity types (strings) that it extends.</p>
+</div>
+<div class="section" id="operation-get-attributes">
+<h4>3.4.2.1.2. Operation GET-ATTRIBUTES<a class="headerlink" href="#operation-get-attributes" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the annotations they implement</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is a list (of strings) of attributes on that entity type.</p>
+</div>
+<div class="section" id="operation-get-operations">
+<h4>3.4.2.1.3. Operation GET-OPERATIONS<a class="headerlink" href="#operation-get-operations" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the operations they support</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of operation names (strings) that it supports.</p>
+</div>
+<div class="section" id="operation-get-annotations">
+<h4>3.4.2.1.4. Operation GET-ANNOTATIONS<a class="headerlink" href="#operation-get-annotations" title="Permalink to this headline">.</a></h4>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of annotations (strings) that it implements.</p>
+</div>
+<div class="section" id="operation-query">
+<h4>3.4.2.1.5. Operation QUERY<a class="headerlink" href="#operation-query" title="Permalink to this headline">.</a></h4>
+<p>Query for attribute values of multiple entities.</p>
+<p><strong>Request body</strong> (map)A map containing the key <cite>attributeNames</cite> with value a list of (string) attribute names to return. If the list or the map is empty or the body is missing all attributes are returned.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>If set, specifies the number of entries from the result set to return. If not set return all from <cite>offset</cite></dd>
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+<dt><em>offset</em> (integer)</dt>
+<dd>If set, specifies the number of the first element of the result set to be returned.</dd>
+</dl>
+<p><strong>Response body</strong> (map)A map with two entries. <cite>attributeNames</cite> is a list of the attribute names returned. <cite>results</cite> is a list of lists each containing the attribute values for a single entity in the same order as the names in the <cite>attributeNames</cite> entry. If an attribute name is not applicable for an entity then the corresponding value is <cite>null</cite></p>
+<p><strong>Response properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>Number of results returned</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+</div>
+<div class="section" id="operation-get-mgmt-nodes">
+<h4>3.4.2.1.6. Operation GET-MGMT-NODES<a class="headerlink" href="#operation-get-mgmt-nodes" title="Permalink to this headline">.</a></h4>
+<p>Get the addresses of all management nodes known to this router</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (list)A list of addresses (strings) of management nodes known to this management node.</p>
+</div>
+</div>
+<div class="section" id="management">
+<h3>3.4.2.2. management<a class="headerlink" href="#management" title="Permalink to this headline">.</a></h3>
+<p>Qpid dispatch router extensions to the standard org.amqp.management interface.</p>
+<p>Operations allowed: <cite>GET-SCHEMA</cite>, <cite>GET-JSON-SCHEMA</cite>, <cite>GET-LOG</cite>, <cite>PROFILE</cite>, <cite>QUERY</cite>, <cite>GET-TYPES</cite>, <cite>GET-ANNOTATIONS</cite>, <cite>GET-OPERATIONS</cite>, <cite>GET-ATTRIBUTES</cite>, <cite>GET-MGMT-NODES</cite>, <cite>READ</cite></p>
+<div class="section" id="operation-get-schema-json">
+<h4>3.4.2.2.1. Operation GET-SCHEMA-JSON<a class="headerlink" href="#operation-get-schema-json" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in JSON format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>indent</em> (integer)</dt>
+<dd>Number of spaces to indent the formatted result. If not specified, the result is in minimal format, no unnecessary spaces or newlines.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)The qdrouter schema as a JSON string.</p>
+</div>
+<div class="section" id="operation-get-log">
+<h4>3.4.2.2.2. Operation GET-LOG<a class="headerlink" href="#operation-get-log" title="Permalink to this headline">.</a></h4>
+<p>Get recent log entries from the router.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>limit</em> (integer)</dt>
+<dd>Maximum number of log entries to get.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)A list of log entries where each entry is a list of: module name(string), level name(string), message text(string), file name(string or None), line number(integer or None) , timestamp(integer)</p>
+</div>
+<div class="section" id="operation-get-schema">
+<h4>3.4.2.2.3. Operation GET-SCHEMA<a class="headerlink" href="#operation-get-schema" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in AMQP map format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)The qdrouter schema as a map.</p>
+</div>
+</div>
+<div class="section" id="router-link">
+<h3>3.4.2.3. router.link<a class="headerlink" href="#router-link" title="Permalink to this headline">.</a></h3>
+<p>Link to another AMQP endpoint: router node, client or other AMQP process.</p>
+<p>Operations allowed: <cite>UPDATE</cite>, <cite>READ</cite></p>
+<p><em>adminStatus</em> (One of [‘enabled’, ‘disabled’], default=’enabled’, <cite>UPDATE</cite>)</p>
+<p><em>operStatus</em> (One of [‘up’, ‘down’, ‘quiescing’, ‘idle’])</p>
+<dl class="docutils">
+<dt><em>linkName</em> (string)</dt>
+<dd>Name assigned to the link in the Attach.</dd>
+<dt><em>linkType</em> (One of [‘endpoint’, ‘router-control’, ‘inter-router’])</dt>
+<dd>Type of link: endpoint: a link to a normally connected endpoint; inter-router: a link to another router in the network.</dd>
+<dt><em>linkDir</em> (One of [‘in’, ‘out’])</dt>
+<dd>Direction of delivery flow over the link, inbound or outbound to or from the router.</dd>
+<dt><em>owningAddr</em> (string)</dt>
+<dd>Address assigned to this link during attach: The target for inbound links or the source for outbound links.</dd>
+<dt><em>capacity</em> (integer)</dt>
+<dd>The capacity, in deliveries, for the link. The number of undelivered plus unsettled deliveries shall not exceed the capacity. This is enforced by link flow control.</dd>
+<dt><em>peer</em> (string)</dt>
+<dd>Identifier of the paired link if this is an attach-routed link.</dd>
+<dt><em>undeliveredCount</em> (integer)</dt>
+<dd>The number of undelivered messages pending for the link.</dd>
+<dt><em>unsettledCount</em> (integer)</dt>
+<dd>The number of unsettled deliveries awaiting settlement on the link</dd>
+<dt><em>deliveryCount</em> (integer)</dt>
+<dd>The total number of deliveries that have traversed this link.</dd>
+</dl>
+</div>
+<div class="section" id="router-address">
+<h3>3.4.2.4. router.address<a class="headerlink" href="#router-address" title="Permalink to this headline">.</a></h3>
+<p>AMQP address managed by the router.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>distribution</em> (One of [‘flood’, ‘multicast’, ‘closest’, ‘balanced’, ‘linkBalanced’])</dt>
+<dd>Forwarding treatment for the address: flood - messages delivered to all subscribers along all available paths (this will cause duplicate deliveries if there are redundant paths); multi - one copy of each message delivered to all subscribers; anyClosest - messages delivered to only the closest subscriber; anyBalanced - messages delivered to one subscriber with load balanced across subscribers; linkBalanced - for link-routing, link attaches balanced across destinations.</dd>
+<dt><em>inProcess</em> (integer)</dt>
+<dd>The number of in-process subscribers for this address</dd>
+<dt><em>subscriberCount</em> (integer)</dt>
+<dd>The number of local subscribers for this address (i.e. attached to this router)</dd>
+<dt><em>remoteCount</em> (integer)</dt>
+<dd>The number of remote routers that have at least one subscriber to this address</dd>
+<dt><em>containerCount</em> (integer)</dt>
+<dd>The number of attached containers that serve this route address</dd>
+<dt><em>deliveriesIngress</em> (integer)</dt>
+<dd>The number of deliveries to this address that entered the router network on this router</dd>
+<dt><em>deliveriesEgress</em> (integer)</dt>
+<dd>The number of deliveries to this address that exited the router network on this router</dd>
+<dt><em>deliveriesTransit</em> (integer)</dt>
+<dd>The number of deliveries to this address that transited this router to another router</dd>
+<dt><em>deliveriesToContainer</em> (integer)</dt>
+<dd>The number of deliveries to this address that were given to an in-process subscriber</dd>
+<dt><em>deliveriesFromContainer</em> (integer)</dt>
+<dd>The number of deliveries to this address that were originated from an in-process entity</dd>
+<dt><em>key</em> (string)</dt>
+<dd>Internal unique (to this router) key to identify the address</dd>
+<dt><em>remoteHostRouters</em> (list)</dt>
+<dd>List of remote routers on which there is a destination for this address.</dd>
+<dt><em>transitOutstanding</em> (list)</dt>
+<dd>List of numbers of outstanding deliveries across a transit (inter-router) link for this address. This is for balanced distribution only.</dd>
+<dt><em>trackedDeliveries</em> (integer)</dt>
+<dd>Number of transit deliveries being tracked for this address (for balanced distribution).</dd>
+</dl>
+</div>
+<div class="section" id="router-node">
+<h3>3.4.2.5. router.node<a class="headerlink" href="#router-node" title="Permalink to this headline">.</a></h3>
+<p>Remote router node connected to this router.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>id</em> (string)</dt>
+<dd>Remote node identifier.</dd>
+<dt><em>instance</em> (integer)</dt>
+<dd>Remote node boot number.</dd>
+<dt><em>linkState</em> (list)</dt>
+<dd>List of remote node’s neighbours.</dd>
+<dt><em>nextHop</em> (string)</dt>
+<dd>Neighbour ID of next hop to remote node from here.</dd>
+<dt><em>validOrigins</em> (list)</dt>
+<dd>List of valid origin nodes for messages arriving via the re mote node, used for duplicate elimination in redundant networks.</dd>
+<dt><em>address</em> (string)</dt>
+<dd>Address of the remote node</dd>
+<dt><em>routerLink</em> (entityId)</dt>
+<dd>Local link to remote node</dd>
+<dt><em>cost</em> (integer)</dt>
+<dd>Reachability cost</dd>
+</dl>
+</div>
+<div class="section" id="connection">
+<h3>3.4.2.6. connection<a class="headerlink" href="#connection" title="Permalink to this headline">.</a></h3>
+<p>Connections to the router’s container.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>container</em> (string)</dt>
+<dd>The container for this connection</dd>
+<dt><em>opened</em> (boolean)</dt>
+<dd>The connection has been opened (i.e. AMQP OPEN)</dd>
+<dt><em>host</em> (string)</dt>
+<dd>IP address and port number in the form addr:port.</dd>
+<dt><em>dir</em> (One of [‘in’, ‘out’])</dt>
+<dd>Direction of connection establishment in or out of the router.</dd>
+</dl>
+<p><em>role</em> (string)</p>
+<dl class="docutils">
+<dt><em>isAuthenticated</em> (boolean)</dt>
+<dd>Indicates whether the identity of the connection’s user is authentic.</dd>
+<dt><em>isEncrypted</em> (boolean)</dt>
+<dd>Indicates whether the connection content is encrypted.</dd>
+<dt><em>sasl</em> (string)</dt>
+<dd>SASL mechanism in effect for authentication.</dd>
+<dt><em>user</em> (string)</dt>
+<dd>Identity of the authenticated user.</dd>
+<dt><em>ssl</em> (boolean)</dt>
+<dd>True iff SSL/TLS is in effect for this connection.</dd>
+<dt><em>sslProto</em> (string)</dt>
+<dd>SSL protocol name</dd>
+<dt><em>sslCipher</em> (string)</dt>
+<dd>SSL cipher name</dd>
+<dt><em>sslSsf</em> (integer)</dt>
+<dd>SSL strength factor in effect</dd>
+<dt><em>properties</em> (map)</dt>
+<dd>Connection properties supplied by the peer.</dd>
+</dl>
+</div>
+<div class="section" id="allocator">
+<h3>3.4.2.7. allocator<a class="headerlink" href="#allocator" title="Permalink to this headline">.</a></h3>
+<p>Memory allocation pool.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<p><em>typeName</em> (string)</p>
+<p><em>typeSize</em> (integer)</p>
+<p><em>transferBatchSize</em> (integer)</p>
+<p><em>localFreeListMax</em> (integer)</p>
+<p><em>globalFreeListMax</em> (integer)</p>
+<p><em>totalAllocFromHeap</em> (integer)</p>
+<p><em>totalFreeToHeap</em> (integer)</p>
+<p><em>heldByThreads</em> (integer)</p>
+<p><em>batchesRebalancedToThreads</em> (integer)</p>
+<p><em>batchesRebalancedToGlobal</em> (integer)</p>
+</div>
+<div class="section" id="policystats">
+<h3>3.4.2.8. policyStats<a class="headerlink" href="#policystats" title="Permalink to this headline">.</a></h3>
+<p>Per application connection and access statistics.</p>
+<p>Operations allowed: <cite>READ</cite></p>
+<dl class="docutils">
+<dt><em>applicationName</em> (string)</dt>
+<dd>The application name.</dd>
+</dl>
+<p><em>connectionsApproved</em> (integer)</p>
+<p><em>connectionsDenied</em> (integer)</p>
+<p><em>connectionsCurrent</em> (integer)</p>
+<dl class="docutils">
+<dt><em>perUserState</em> (map)</dt>
+<dd>A map where the key is the authenticated user name and the value is a list of the user’s connections.</dd>
+<dt><em>perHostState</em> (map)</dt>
+<dd>A map where the key is the host name and the value is a list of the host’s connections.</dd>
+</dl>
+<p><em>sessionDenied</em> (integer)</p>
+<p><em>senderDenied</em> (integer)</p>
+<p><em>receiverDenied</em> (integer)</p>
+</div>
+</div>
+<div class="section" id="management-operations">
+<h2>3.4.3. Management Operations<a class="headerlink" href="#management-operations" title="Permalink to this headline">.</a></h2>
+<p>The <cite>qdstat(8)</cite> and <cite>qdmanage(8)</cite> tools allow you to view or modify management entity
+attributes. They work by invoking <em>management operations</em>. You can invoke these operations
+from any AMQP client by sending a message with the appropriate properties and body to the
+<cite>$management</cite> address. The message should have a <cite>reply-to</cite> address indicating where the
+response should be sent.</p>
+<div class="section" id="operations-for-all-entity-types">
+<h3>3.4.3.1. Operations for all entity types<a class="headerlink" href="#operations-for-all-entity-types" title="Permalink to this headline">.</a></h3>
+<div class="section" id="operation-read">
+<h4>3.4.3.1.1. Operation READ<a class="headerlink" href="#operation-read" title="Permalink to this headline">.</a></h4>
+<p>Read attributes of an entity</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string)</dt>
+<dd>Type of desired entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of desired entity. Must supply name or identity.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Identity of desired entity. Must supply name or identity.</dd>
+</dl>
+<p><strong>Response body</strong> (map)Attributes of the entity</p>
+</div>
+<div class="section" id="operation-create">
+<h4>3.4.3.1.2. Operation CREATE<a class="headerlink" href="#operation-create" title="Permalink to this headline">.</a></h4>
+<p>Create a new entity.</p>
+<p><strong>Request body</strong> (map, required)Attributes for the new entity. Can include name and/or type.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string, required)</dt>
+<dd>Type of new entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of new entity. Optional, defaults to identity.</dd>
+</dl>
+<p><strong>Response body</strong> (map)Attributes of the entity</p>
+</div>
+<div class="section" id="operation-update">
+<h4>3.4.3.1.3. Operation UPDATE<a class="headerlink" href="#operation-update" title="Permalink to this headline">.</a></h4>
+<p>Update attributes of an entity</p>
+<p><strong>Request body</strong> (map)Attributes to update for the entity. Can include name or identity.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string)</dt>
+<dd>Type of desired entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of desired entity. Must supply name or identity.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Identity of desired entity. Must supply name or identity.</dd>
+</dl>
+<p><strong>Response body</strong> (map)Updated attributes of the entity</p>
+</div>
+<div class="section" id="operation-delete">
+<h4>3.4.3.1.4. Operation DELETE<a class="headerlink" href="#operation-delete" title="Permalink to this headline">.</a></h4>
+<p>Delete an entity</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>type</em> (string)</dt>
+<dd>Type of desired entity.</dd>
+<dt><em>name</em> (string)</dt>
+<dd>Name of desired entity. Must supply name or identity.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Identity of desired entity. Must supply name or identity.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="operations-for-org-amqp-management-entity-type">
+<h3>3.4.3.2. Operations for <cite>org.amqp.management</cite> entity type<a class="headerlink" href="#operations-for-org-amqp-management-entity-type" title="Permalink to this headline">.</a></h3>
+<div class="section" id="id1">
+<h4>3.4.3.2.1. Operation GET-TYPES<a class="headerlink" href="#id1" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and their inheritance relationships</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of the entity types (strings) that it extends.</p>
+</div>
+<div class="section" id="id2">
+<h4>3.4.3.2.2. Operation GET-ATTRIBUTES<a class="headerlink" href="#id2" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the annotations they implement</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is a list (of strings) of attributes on that entity type.</p>
+</div>
+<div class="section" id="id3">
+<h4>3.4.3.2.3. Operation GET-OPERATIONS<a class="headerlink" href="#id3" title="Permalink to this headline">.</a></h4>
+<p>Get the set of entity types and the operations they support</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of operation names (strings) that it supports.</p>
+</div>
+<div class="section" id="id4">
+<h4>3.4.3.2.4. Operation GET-ANNOTATIONS<a class="headerlink" href="#id4" title="Permalink to this headline">.</a></h4>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)A map where each key is an entity type name (string) and the corresponding value is the list of annotations (strings) that it implements.</p>
+</div>
+<div class="section" id="id5">
+<h4>3.4.3.2.5. Operation QUERY<a class="headerlink" href="#id5" title="Permalink to this headline">.</a></h4>
+<p>Query for attribute values of multiple entities.</p>
+<p><strong>Request body</strong> (map)A map containing the key <cite>attributeNames</cite> with value a list of (string) attribute names to return. If the list or the map is empty or the body is missing all attributes are returned.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>If set, specifies the number of entries from the result set to return. If not set return all from <cite>offset</cite></dd>
+<dt><em>entityType</em> (string)</dt>
+<dd>If set, restrict query results to entities that extend (directly or indirectly) this type</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+<dt><em>offset</em> (integer)</dt>
+<dd>If set, specifies the number of the first element of the result set to be returned.</dd>
+</dl>
+<p><strong>Response body</strong> (map)A map with two entries. <cite>attributeNames</cite> is a list of the attribute names returned. <cite>results</cite> is a list of lists each containing the attribute values for a single entity in the same order as the names in the <cite>attributeNames</cite> entry. If an attribute name is not applicable for an entity then the corresponding value is <cite>null</cite></p>
+<p><strong>Response properties:</strong></p>
+<dl class="docutils">
+<dt><em>count</em> (integer)</dt>
+<dd>Number of results returned</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+</div>
+<div class="section" id="id6">
+<h4>3.4.3.2.6. Operation GET-MGMT-NODES<a class="headerlink" href="#id6" title="Permalink to this headline">.</a></h4>
+<p>Get the addresses of all management nodes known to this router</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (list)A list of addresses (strings) of management nodes known to this management node.</p>
+</div>
+</div>
+<div class="section" id="operations-for-management-entity-type">
+<h3>3.4.3.3. Operations for <cite>management</cite> entity type<a class="headerlink" href="#operations-for-management-entity-type" title="Permalink to this headline">.</a></h3>
+<div class="section" id="id7">
+<h4>3.4.3.3.1. Operation GET-SCHEMA-JSON<a class="headerlink" href="#id7" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in JSON format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>indent</em> (integer)</dt>
+<dd>Number of spaces to indent the formatted result. If not specified, the result is in minimal format, no unnecessary spaces or newlines.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)The qdrouter schema as a JSON string.</p>
+</div>
+<div class="section" id="id8">
+<h4>3.4.3.3.2. Operation GET-LOG<a class="headerlink" href="#id8" title="Permalink to this headline">.</a></h4>
+<p>Get recent log entries from the router.</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>limit</em> (integer)</dt>
+<dd>Maximum number of log entries to get.</dd>
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (string)A list of log entries where each entry is a list of: module name(string), level name(string), message text(string), file name(string or None), line number(integer or None) , timestamp(integer)</p>
+</div>
+<div class="section" id="id9">
+<h4>3.4.3.3.3. Operation GET-SCHEMA<a class="headerlink" href="#id9" title="Permalink to this headline">.</a></h4>
+<p>Get the qdrouterd schema for this router in AMQP map format</p>
+<p><strong>Request properties:</strong></p>
+<dl class="docutils">
+<dt><em>identity</em> (string)</dt>
+<dd>Set to the value <cite>self</cite></dd>
+</dl>
+<p><strong>Response body</strong> (map)The qdrouter schema as a map.</p>
+</div>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/book/technical_details.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/book/technical_details.html b/content/releases/qpid-dispatch-0.6.0/book/technical_details.html
new file mode 100644
index 0000000..77799d0
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/book/technical_details.html
@@ -0,0 +1,212 @@
+<!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>3. Technical Details and Specifications. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>3. Technical Details and Specifications.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="technical-details-and-specifications">
+<h1>3. Technical Details and Specifications<a class="headerlink" href="#technical-details-and-specifications" title="Permalink to this headline">.</a></h1>
+<div class="toctree-wrapper compound">
+<ul>
+<li class="toctree-l1"><a class="reference internal" href="client_compatibility.html">3.1. Client Compatibility</a></li>
+<li class="toctree-l1"><a class="reference internal" href="addressing.html">3.2. Addressing</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="addressing.html#routing-patterns">3.2.1. Routing patterns</a></li>
+<li class="toctree-l2"><a class="reference internal" href="addressing.html#routing-mechanisms">3.2.2. Routing mechanisms</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="addressing.html#message-routing">3.2.2.1. Message routing</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="amqp-mapping.html">3.3. AMQP Mapping</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#message-annotations">3.3.1. Message Annotations</a></li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#source-target-capabilities">3.3.2. Source/Target Capabilities</a></li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#dynamic-node-properties">3.3.3. Dynamic-Node-Properties</a></li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#addresses-and-address-formats">3.3.4. Addresses and Address Formats</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#address-patterns">3.3.4.1. Address Patterns</a></li>
+<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#supported-addresses">3.3.4.2. Supported Addresses</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</a></li>
+</ul>
+</li>
+<li class="toctree-l1"><a class="reference internal" href="schema.html">3.4. Management Schema</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="schema.html#configuration-entities">3.4.1. Configuration Entities</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#container">3.4.1.1. container</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router">3.4.1.2. router</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#listener">3.4.1.3. listener</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#connector">3.4.1.4. connector</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#log">3.4.1.5. log</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#fixedaddress">3.4.1.6. fixedAddress</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#waypoint">3.4.1.7. waypoint</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#linkroutepattern">3.4.1.8. linkRoutePattern</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#address">3.4.1.9. address</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#linkroute">3.4.1.10. linkRoute</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#autolink">3.4.1.11. autoLink</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#console">3.4.1.12. console</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#policy">3.4.1.13. policy</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#policyruleset">3.4.1.14. policyRuleset</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="schema.html#operational-entities">3.4.2. Operational Entities</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#org-amqp-management">3.4.2.1. org.amqp.management</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#management">3.4.2.2. management</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router-link">3.4.2.3. router.link</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router-address">3.4.2.4. router.address</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#router-node">3.4.2.5. router.node</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#connection">3.4.2.6. connection</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#allocator">3.4.2.7. allocator</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#policystats">3.4.2.8. policyStats</a></li>
+</ul>
+</li>
+<li class="toctree-l2"><a class="reference internal" href="schema.html#management-operations">3.4.3. Management Operations</a><ul>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-all-entity-types">3.4.3.1. Operations for all entity types</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-org-amqp-management-entity-type">3.4.3.2. Operations for <cite>org.amqp.management</cite> entity type</a></li>
+<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-management-entity-type">3.4.3.3. Operations for <cite>management</cite> entity type</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</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
[4/8] qpid-site git commit: NO-JIRA - Adding Qpid Dispatch Router
0.6.0 release docs
Posted by gm...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.html b/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.html
new file mode 100644
index 0000000..2b59fdc
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/man/qdrouterd.html
@@ -0,0 +1,187 @@
+<!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>qdrouterd manual page. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>qdrouterd manual page.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="qdrouterd-manual-page">
+<h1>qdrouterd manual page<a class="headerlink" href="#qdrouterd-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>SYNOPSIS<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdrouterd [<em>options</em>]</p>
+</div>
+<div class="section" id="description">
+<h2>DESCRIPTION<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<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 class="section" id="options">
+<h2>OPTIONS<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
+<p>-c, –config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
+: Load configuration from file at PATH</p>
+<p>-I, –include=PATH (/usr/local/lib/qpid-dispatch/python)
+: Location of Dispatch’s Python library</p>
+<p>-d, –daemon
+: Run process as a SysV-style daemon</p>
+<p>-P, –pidfile
+: If daemon, the file for the stored daemon pid</p>
+<p>-U, –user
+: If daemon, the username to run as</p>
+<p>-h, –help
+: Print this help</p>
+</div>
+<div class="section" id="files">
+<h2>FILES<a class="headerlink" href="#files" title="Permalink to this headline">.</a></h2>
+<dl class="docutils">
+<dt>/usr/local/etc/qdrouterd.conf</dt>
+<dd>Configuration flie.</dd>
+</dl>
+</div>
+<div class="section" id="see-also">
+<h2>SEE ALSO<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/man/qdstat.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/man/qdstat.html b/content/releases/qpid-dispatch-0.6.0/man/qdstat.html
new file mode 100644
index 0000000..875cbca
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/man/qdstat.html
@@ -0,0 +1,417 @@
+<!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>qdstat manual page. - 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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>qdstat manual page.</li></ul>
+
+ <div id="-middle-content">
+
+
+ <div class="section" id="qdstat-manual-page">
+<h1>qdstat manual page<a class="headerlink" href="#qdstat-manual-page" title="Permalink to this headline">.</a></h1>
+<div class="section" id="synopsis">
+<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2>
+<p>qdstat [options]</p>
+</div>
+<div class="section" id="description">
+<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
+<p><em>qdstat</em> 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 class="section" id="options">
+<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
+<p>-h, –help
+: show this help message and exit</p>
+<p>–version
+: Print version and exit.</p>
+<p>-g, –general
+: Show General Router Stats</p>
+<p>-c, –connections
+: Show Connections</p>
+<p>-l, –links
+: Show Router Links</p>
+<p>-n, –nodes
+: Show Router Nodes</p>
+<p>-a, –address
+: Show Router Addresses</p>
+<p>-m, –memory
+: Show Router Memory Stats</p>
+<p>–autolinks
+: Show Auto Links</p>
+<p>–linkroutes
+: Show Link Routes</p>
+<p>-v, –verbose
+: Show maximum detail</p>
+<p>–log
+: Show recent log entries</p>
+<p>–limit=LIMIT
+: Limit number of log entries</p>
+<div class="section" id="connection-options">
+<h3>Connection Options<a class="headerlink" href="#connection-options" title="Permalink to this headline">.</a></h3>
+<p>-b URL, –bus=URL
+: URL of the messaging bus to connect to (default</p>
+<p>-r ROUTER-ID, –router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, –timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>–ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>–ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>–ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>–ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+</div>
+</div>
+<div class="section" id="output-columns">
+<h2>Output Columns<a class="headerlink" href="#output-columns" title="Permalink to this headline">.</a></h2>
+<div class="section" id="qdstat-c">
+<h3>qdstat -c<a class="headerlink" href="#qdstat-c" title="Permalink to this headline">.</a></h3>
+<p>Id
+: Unique connection identifier</p>
+<p>host
+: The hostname or internet address of the remotely connected AMQP container</p>
+<p>container
+: The container-name of the remotely connected AMQP container</p>
+<p>role
+: The configured role of the connection</p>
+<blockquote>
+<div><ul class="simple">
+<li>normal - Normal connections from client to router</li>
+<li>inter-router - Connection between routers to form a network</li>
+<li>route-container - Connection to/from a Broker or other host to receive link-routes and waypoints</li>
+</ul>
+</div></blockquote>
+<p>dir
+: The direction of connection establishment</p>
+<blockquote>
+<div><ul class="simple">
+<li>in - The connection was initiated by the remote container</li>
+<li>out - The connection was initiated by this router</li>
+</ul>
+</div></blockquote>
+<p>security
+: A description of the security/encryption in effect for this connection</p>
+<p>authentication
+: The method and user-id of the authenticated user for this connection</p>
+</div>
+<div class="section" id="qdstat-l">
+<h3>qdstat -l<a class="headerlink" href="#qdstat-l" title="Permalink to this headline">.</a></h3>
+<p>type
+: Type of link</p>
+<blockquote>
+<div><ul class="simple">
+<li>router-control - An inter-router link that is reserved for control messages exchanged between routers</li>
+<li>inter-router - An inter-router link that is used for normal message-routed deliveries</li>
+<li>endpoint - A normal link to an external endpoint container</li>
+</ul>
+</div></blockquote>
+<p>dir
+: The direction of message flow on the link</p>
+<blockquote>
+<div><ul class="simple">
+<li>in - Deliveries flow inbound to the router</li>
+<li>out - Deliveries flow outbound from the router</li>
+</ul>
+</div></blockquote>
+<p>conn id
+: Unique identifier of the connection over which this link is attached</p>
+<p>id
+: Unique identifier of this link</p>
+<p>peer
+: For link-routed links, the unique identifier of the peer link. In link routing, an inbound link is paired with an outbound link</p>
+<p>class
+: Class of the address bound to the link</p>
+<p>addr
+: The address bound to the link</p>
+<p>phs
+: The phase of the address bound to the link</p>
+<p>cap
+: The capacity, in deliveries, of the link</p>
+<p>undel
+: The number of undelivered messages stored on the link’s FIFO</p>
+<p>unsettled
+: The number of unsettled deliveries being tracked by the link</p>
+<p>deliveries
+: The total number of deliveries that have transited this link</p>
+<p>admin
+: The administrative status of the link</p>
+<blockquote>
+<div><ul class="simple">
+<li>enabled - The link is enabled for normal operation</li>
+<li>disabled - The link is disabled and should be quiescing or stopped (not yet supported)</li>
+</ul>
+</div></blockquote>
+<p>oper
+: The operational status of the link</p>
+<blockquote>
+<div><ul class="simple">
+<li>up - The link is operational</li>
+<li>down - The link is not attached</li>
+<li>quiescing - The link is in the process of quiescing (not yet supported)</li>
+<li>idle - The link has completed quiescing and is idle (not yet supported)</li>
+</ul>
+</div></blockquote>
+<p>name
+: The link name (only shown if the -v option is provided)</p>
+</div>
+<div class="section" id="qdstat-n">
+<h3>qdstat -n<a class="headerlink" href="#qdstat-n" title="Permalink to this headline">.</a></h3>
+<p>router-id
+: Identifier of the router</p>
+<p>next-hop
+: If this router is not a neighbor, identifies the next-hop neighbor used to reach this router</p>
+<p>link
+: Unique identifier of the link to the neighbor router</p>
+<p>cost
+: The topology cost to this remote router (with -v option only)</p>
+<p>neighbors
+: The list of neighbor routers (the router’s link-state) (with -v option only)</p>
+<p>valid-origins
+: The list of origin routers for which the best path to the listed router passes through this router (with -v option only)</p>
+</div>
+<div class="section" id="qdstat-a">
+<h3>qdstat -a<a class="headerlink" href="#qdstat-a" title="Permalink to this headline">.</a></h3>
+<p>class
+: The class of the listed address</p>
+<blockquote>
+<div><ul class="simple">
+<li>local - Address that is local to this router</li>
+<li>topo - Topological address used for router control messages</li>
+<li>router - A summary router address used to route messages to a remote router’s local addresses</li>
+<li>mobile - A mobile address for an attached consumer or producer</li>
+</ul>
+</div></blockquote>
+<p>addr
+: The address text</p>
+<p>phs
+: 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>
+<p>distrib
+: Distribution method used for this address</p>
+<blockquote>
+<div><ul class="simple">
+<li>multicast - A copy of each message is delivered once to each consumer for the address</li>
+<li>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.</li>
+<li>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).</li>
+<li>flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.</li>
+</ul>
+</div></blockquote>
+<p>in-proc
+: The number of in-process consumers for this address</p>
+<p>local
+: The number of local (on this router) consumers for this address</p>
+<p>remote
+: The number of remote routers that have at least one consumer for this address</p>
+<p>cntnr
+: The number of locally attached containers that are destinations for link-routes on this address</p>
+<p>in
+: The number of deliveries for this address that entered the network on this router</p>
+<p>out
+: The number of deliveries for this address that exited the network on this router</p>
+<p>thru
+: The number of deliveries for this address that were forwarded to other routers</p>
+<p>to-proc
+: The number of deliveries for this address that were delivered to an in-process consumer</p>
+<p>from-proc
+: The number of deliveries for this address that were received from an in-process producer</p>
+</div>
+<div class="section" id="qdstat-linkroutes">
+<h3>qdstat –linkroutes<a class="headerlink" href="#qdstat-linkroutes" title="Permalink to this headline">.</a></h3>
+<p>prefix
+: The prefix for matching addresses of routed links</p>
+<p>dir
+: The direction (from the router’s perspective) of matching links</p>
+<p>distrib
+: The distribution method used for routed links</p>
+<blockquote>
+<div><ul class="simple">
+<li>linkBalanced - the only supported distribution for routed links</li>
+</ul>
+</div></blockquote>
+<p>status
+: Operational status of the link route</p>
+<blockquote>
+<div><ul class="simple">
+<li>active - Route is actively routing attaches (i.e. ready for use)</li>
+<li>inactive - Route is inactive because there is no local destination connected</li>
+</ul>
+</div></blockquote>
+</div>
+<div class="section" id="qstat-autolinks">
+<h3>qstat –autolinks<a class="headerlink" href="#qstat-autolinks" title="Permalink to this headline">.</a></h3>
+<p>addr
+: The address of the auto link</p>
+<p>dir
+: The direction of message flow for the auto link</p>
+<blockquote>
+<div><ul class="simple">
+<li>in - Messages flow in from the route-container to the router network</li>
+<li>out - Messages flow out to the route-container from the router network</li>
+</ul>
+</div></blockquote>
+<p>phs
+: Phase of the address for this auto link</p>
+<p>link
+: Unique identifier of the link managed by this auto link</p>
+<p>status
+: The operational status of this auto link</p>
+<blockquote>
+<div><ul class="simple">
+<li>inactive - There is no connected container for this auto link</li>
+<li>attaching - The link is attaching to the container</li>
+<li>failed - The link-attach failed</li>
+<li>active - The link is operational</li>
+<li>quiescing - The link is quiescing (not yet supported)</li>
+<li>idle - The link is idle (not yet supported)</li>
+</ul>
+</div></blockquote>
+<p>lastErr
+: The description of the last attach failure that occurred on this auto link</p>
+</div>
+</div>
+<div class="section" id="see-also">
+<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
+<p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p>
+<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
+</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/ac1c1663/content/releases/qpid-dispatch-0.6.0/release-notes.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-0.6.0/release-notes.html b/content/releases/qpid-dispatch-0.6.0/release-notes.html
new file mode 100644
index 0000000..c5b62a9
--- /dev/null
+++ b/content/releases/qpid-dispatch-0.6.0/release-notes.html
@@ -0,0 +1,290 @@
+<!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.6.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">Java broker</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.6.0/index.html">Qpid Dispatch 0.6.0</a></li><li>Qpid Dispatch 0.6.0 Release Notes</li></ul>
+
+ <div id="-middle-content">
+ <h1 id="qpid-dispatch-060-release-notes">Qpid Dispatch 0.6.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-10">DISPATCH-10</a> - Add link-cost for route computation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-57">DISPATCH-57</a> - Balance deliveries adaptively across all competing consumers in the network</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-144">DISPATCH-144</a> - Configurable heartbeats for listeners and connectors</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-148">DISPATCH-148</a> - Strip qpid-dispatch-specific message annotations on ingress/egress</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-159">DISPATCH-159</a> - Enhance the address prefix used for link routing to support different patterns</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-163">DISPATCH-163</a> - Add username and password for authentication of connectors</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-164">DISPATCH-164</a> - Remove connector state-machine from the server module</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-165">DISPATCH-165</a> - Discriminate between sending and receiving links when matching link-route patterns</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-166">DISPATCH-166</a> - Use test-controlled SASL configuration for system tests</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-170">DISPATCH-170</a> - qdrouterd should not require a restart after the destination broker restarts</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-178">DISPATCH-178</a> - Route proton trace messages to the dispatch router log file instead of console</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-179">DISPATCH-179</a> - Refactor Router Core</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-180">DISPATCH-180</a> - Add a system test to test the 'linkRoutePattern' attribute of qdrouterd.conf</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-188">DISPATCH-188</a> - Dispatch needs a policy mechanism to limit user connections and activity</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-190">DISPATCH-190</a> - Expose the Protocol Family for the configuration of listeners and connectors</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-193">DISPATCH-193</a> - Updates to the Container API</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-194">DISPATCH-194</a> - Move libqpid-dispatch.so out of /lib</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-197">DISPATCH-197</a> - Provide list of current link routing</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-199">DISPATCH-199</a> - Add Dockerfiles that launches the dispatch router inside a container for RHEL and Debian based systems</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-200">DISPATCH-200</a> - Flexible mapping from x.509 certificates to an identity</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-203">DISPATCH-203</a> - Improve loop-prevention to drop messages before they are improperly forwarded</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-217">DISPATCH-217</a> - Make the UI more consistant with other hawtio plugins </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-228">DISPATCH-228</a> - In ctools, add a variant of DEQ_* to allow membership in multiple lists</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-230">DISPATCH-230</a> - New connection role: route-container</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-232">DISPATCH-232</a> - Add capability to delete listeners and connectors via the qdmanage DELETE operation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-242">DISPATCH-242</a> - Add options to qdstat to display autoLinks and linkRoutes</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-253">DISPATCH-253</a> - Configurable link-capacity</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-256">DISPATCH-256</a> - Documentation Updates for 0.6</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-265">DISPATCH-265</a> - Improvements to Detecting Routers with Duplicate IDs</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-277">DISPATCH-277</a> - Improve defaults for router configuration</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-286">DISPATCH-286</a> - Prefix delimiters: allow slashes as well as periods</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-300">DISPATCH-300</a> - Deprecate the ContainerEntity and move its attributes to RouterEntity</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-303">DISPATCH-303</a> - Block all remote access to the "console" entity</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-305">DISPATCH-305</a> - Don't tie inter-router flow credit to unsettled deliveries</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-306">DISPATCH-306</a> - Deprecate addr and routerId attributes in qdrouter schema and replace them with host and id respectively</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-331">DISPATCH-331</a> - Allow for a default policy to apply when open.hostname doesn't match an existing policy</li>
+</ul>
+
+<h2 id="bugs-fixed">Bugs fixed</h2>
+
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-32">DISPATCH-32</a> - Undeliverable messages should get released.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-43">DISPATCH-43</a> - Router control messages delayed by inter-router message traffic</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-47">DISPATCH-47</a> - qdrouterd doesn't know where its libraries are</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-53">DISPATCH-53</a> - waypoints are not robust if targets not set up in advance.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-58">DISPATCH-58</a> - Router/Broker interaction - Unroutable/released messages are continually resent</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-111">DISPATCH-111</a> - helloworld example hangs when run against a broker via link-routing</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-126">DISPATCH-126</a> - Link-route behavior doesn't honor the semantics assigned to the address prefix</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-127">DISPATCH-127</a> - Messages from waypoints to remote routers are not delivered</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-155">DISPATCH-155</a> - Allow multiple connectors to the same broker</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-168">DISPATCH-168</a> - A message sent to $management without a reply-to field causes a crash</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-171">DISPATCH-171</a> - SSL Domain objects are leaked.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-172">DISPATCH-172</a> - QDStat system test never tests SASL EXTERNAL</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-173">DISPATCH-173</a> - Half-closed connections spin on "writable" until they close</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-174">DISPATCH-174</a> - Improper use of ref-counted object references in container</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-175">DISPATCH-175</a> - Router continues to forward messages to the broker even when the broker is not available</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-176">DISPATCH-176</a> - Messages sent got lost when one of the brokers went down </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-183">DISPATCH-183</a> - plaintext sasl password being written to the dispatch router log</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-191">DISPATCH-191</a> - router not replying to detach frame</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-196">DISPATCH-196</a> - Remove endpoint mode from router documentation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-198">DISPATCH-198</a> - Message module doesn't parse AMQP-Value bodies that are strings or symbols</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-207">DISPATCH-207</a> - When a message body of [ ] is sent from rhea it is rejected as an invalid body </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-208">DISPATCH-208</a> - Closest semantics forwards improperly in multi-router network</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-215">DISPATCH-215</a> - The topology diagram initially draws off the bottom of the visible page.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-218">DISPATCH-218</a> - Dispatch system tests run very slowly if connected to a VPN</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-219">DISPATCH-219</a> - System test security configuration for installed/built tests.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-222">DISPATCH-222</a> - For Dispatch 0.6 release move up the minimum required version of qpid proton to 0.12.0</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-223">DISPATCH-223</a> - Unknown connector name is not properly printed in error messages</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-225">DISPATCH-225</a> - Sending UPDATE log request with relative path crashes router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-226">DISPATCH-226</a> - The default role is not applied when creating a connector</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-231">DISPATCH-231</a> - Router should not issue credit for unavailable targets</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-234">DISPATCH-234</a> - undeliverable-here set to true for messages from waypoints if there is no receiver</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-237">DISPATCH-237</a> - Dispatch Router overwrites delivery tag for link-routed deliveries</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-238">DISPATCH-238</a> - Need more documentation for qdstat output</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-240">DISPATCH-240</a> - qdstat : leading "/" character effects a wrong showed address</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-241">DISPATCH-241</a> - Bias "spread" config with leading "/" on address has a "multicast" behavior</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-245">DISPATCH-245</a> - Various Bugs found by Coverity</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-247">DISPATCH-247</a> - Policy gets username from transport</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-248">DISPATCH-248</a> - Policy self test uses python features not supported by RHEL 6 (python 2.6)</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-250">DISPATCH-250</a> - Router crash when deleting connector</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-254">DISPATCH-254</a> - Router crash after several management requests</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-259">DISPATCH-259</a> - qdstat man-page doc is no good</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-261">DISPATCH-261</a> - Bind error on one port causes bind error on other ports</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-262">DISPATCH-262</a> - oslo.messaging RPC fanout crashes qdrouterd</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-263">DISPATCH-263</a> - Router crash when requesting log</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-264">DISPATCH-264</a> - printf formats for 64-bit quantities need to be 64/32-bit safe</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-267">DISPATCH-267</a> - Policy does not increment denial statistics</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-268">DISPATCH-268</a> - Delivery from waypoint queue can stall when messages are released</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-269">DISPATCH-269</a> - Policy denial logs at wrong level</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-271">DISPATCH-271</a> - Handle single router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-272">DISPATCH-272</a> - Re-enable the connection cross-section popup</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-273">DISPATCH-273</a> - The entity view is missing information for some entities</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-275">DISPATCH-275</a> - Prevent javascript alert errors when navigating to console from a bookmark </li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-278">DISPATCH-278</a> - Deleting amqp listener using qdmanage crashes the router</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-279">DISPATCH-279</a> - Policy crash when application name is null</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-281">DISPATCH-281</a> - Hostname not sent in open frame on connectors</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-282">DISPATCH-282</a> - Prevent topology updates when adding a new router node</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-283">DISPATCH-283</a> - Start the overview page with the Router tree node expanded</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-284">DISPATCH-284</a> - The management schema no longer exposes a way to associate links with their connections</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-285">DISPATCH-285</a> - qdmanage returns an empty list when you QUERY for certain entities</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-287">DISPATCH-287</a> - Policy does not allow configuration for unspecified Open hostname</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-288">DISPATCH-288</a> - Driver - Wakeup pipe was seen to block on read, deadlocking the driver.</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-289">DISPATCH-289</a> - Unit tests failing on Solaris</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-290">DISPATCH-290</a> - Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-292">DISPATCH-292</a> - some router.link attributes should be graphable</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-293">DISPATCH-293</a> - The $ character can't be used inside a prefix for linkRoute</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-294">DISPATCH-294</a> - Crash in the core-thread due to an address referencing a link on a closed connection</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-295">DISPATCH-295</a> - Router aborted on assertion failed after socker closing by client</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-298">DISPATCH-298</a> - router spinning on shutdown (in qdr_del_connection_ref)</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-299">DISPATCH-299</a> - After policy rejects a connection queued Begin causes a crash</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-304">DISPATCH-304</a> - Console PNG images not showing up in documentation</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-309">DISPATCH-309</a> - Mobile addresses get the wrong distribution when mapped to remote routers</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-310">DISPATCH-310</a> - Use router.id instead of container.containerName</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-312">DISPATCH-312</a> - Closest distribution fails to react to loss of a remote destination</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-319">DISPATCH-319</a> - Discrepancy between origin router's path and other routers' valid-origins</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-320">DISPATCH-320</a> - SSL enabled connector does not do hostname verification</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-321">DISPATCH-321</a> - Dispatch does not send out SASL-OUTCOME frame on sasl failure</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-334">DISPATCH-334</a> - Proton sequence error during backpressure with balanced distribution</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-335">DISPATCH-335</a> - link routes aren't balanced over remote routers</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-338">DISPATCH-338</a> - Incorrect default distribution for addresses</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-339">DISPATCH-339</a> - The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-340">DISPATCH-340</a> - Test inter_router_plain_over_ssl fails to find SSL connection</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-342">DISPATCH-342</a> - qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink}</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-343">DISPATCH-343</a> - Router stops accepting connections after load from parallel senders</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-356">DISPATCH-356</a> - Creating and deleting a listener on already listening port causes router to crash</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-368">DISPATCH-368</a> - Router in bad state in two inter-connected routers</li>
+</ul>
+
+<h2 id="tasks">Tasks</h2>
+
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-307">DISPATCH-307</a> - misc fixups for console plugin build</li>
+<li><a href="https://issues.apache.org/jira/browse/DISPATCH-308">DISPATCH-308</a> - console documentation needs updated</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/ac1c1663/input/releases/qpid-dispatch-0.6.0/_images/console_charts.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/_images/console_charts.png b/input/releases/qpid-dispatch-0.6.0/_images/console_charts.png
new file mode 100644
index 0000000..169c2ca
Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.0/_images/console_charts.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/_images/console_entity.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/_images/console_entity.png b/input/releases/qpid-dispatch-0.6.0/_images/console_entity.png
new file mode 100644
index 0000000..130c7e7
Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.0/_images/console_entity.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/_images/console_login.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/_images/console_login.png b/input/releases/qpid-dispatch-0.6.0/_images/console_login.png
new file mode 100644
index 0000000..63e22c6
Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.0/_images/console_login.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/_images/console_overview.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/_images/console_overview.png b/input/releases/qpid-dispatch-0.6.0/_images/console_overview.png
new file mode 100644
index 0000000..af25f36
Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.0/_images/console_overview.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/_images/console_schema.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/_images/console_schema.png b/input/releases/qpid-dispatch-0.6.0/_images/console_schema.png
new file mode 100644
index 0000000..ba56c7b
Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.0/_images/console_schema.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/_images/console_topology.png
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/_images/console_topology.png b/input/releases/qpid-dispatch-0.6.0/_images/console_topology.png
new file mode 100644
index 0000000..ae4b22a
Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.0/_images/console_topology.png differ
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/addressing.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/addressing.html.in b/input/releases/qpid-dispatch-0.6.0/book/addressing.html.in
new file mode 100644
index 0000000..d472702
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/addressing.html.in
@@ -0,0 +1,127 @@
+
+
+ <div class="section" id="addressing">
+<h1>3.2. Addressing<a class="headerlink" href="#addressing" title="Permalink to this headline">.</a></h1>
+<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 <cite>to</cite>
+and <cite>reply-to</cite> fields of a message’s properties. They are also used
+during the creation of links in the <cite>address</cite> field of a <cite>source</cite> or
+a <cite>target</cite>.</p>
+<p>Addresses designate various kinds of entities in a messaging network:</p>
+<ul class="simple">
+<li>Endpoint processes that consume data or offer a service</li>
+<li>Topics that match multiple consumers to multiple producers</li>
+<li>Entities within a messaging broker:
+- Queues
+- Durable Topics
+- Exchanges</li>
+</ul>
+<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>
+<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>
+<p>Address semantics include the following considerations:</p>
+<ul class="simple">
+<li><em>Routing pattern</em> - direct, multicast, balanced</li>
+<li><em>Undeliverable action</em> - drop, hold and retry, redirect</li>
+<li><em>Reliability</em> - N destinations, etc.</li>
+</ul>
+<div class="section" id="routing-patterns">
+<h2>3.2.1. Routing patterns<a class="headerlink" href="#routing-patterns" title="Permalink to this headline">.</a></h2>
+<p>Routing patterns constrain the paths that a message can take across a
+network.</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="17%" />
+<col width="83%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Pattern</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><em>Direct</em></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><em>Multicast</em></td>
+<td>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.</td>
+</tr>
+<tr class="row-even"><td><em>Balanced</em></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="routing-mechanisms">
+<h2>3.2.2. Routing mechanisms<a class="headerlink" href="#routing-mechanisms" title="Permalink to this headline">.</a></h2>
+<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>
+<blockquote>
+<div>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.</div></blockquote>
+<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 class="section" id="message-routing">
+<h3>3.2.2.1. Message routing<a class="headerlink" href="#message-routing" title="Permalink to this headline">.</a></h3>
+<p>Message routing occurs upon delivery of a message and is done based on
+the address in the message’s <cite>to</cite> field.</p>
+<p>When a delivery arrives on an incoming link, the router extracts the
+address from the delivered message’s <cite>to</cite> 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>
+<table border="1" class="docutils">
+<colgroup>
+<col width="19%" />
+<col width="81%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Delivery</em></th>
+<th class="head"><em>Handling</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><em>pre-settled</em></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><em>unsettled</em></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html.in b/input/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html.in
new file mode 100644
index 0000000..051d754
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/amqp-mapping.html.in
@@ -0,0 +1,214 @@
+
+
+ <div class="section" id="amqp-mapping">
+<h1>3.3. AMQP Mapping<a class="headerlink" href="#amqp-mapping" title="Permalink to this headline">.</a></h1>
+<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 class="section" id="message-annotations">
+<h2>3.3.1. Message Annotations<a class="headerlink" href="#message-annotations" title="Permalink to this headline">.</a></h2>
+<p>The following Message Annotation fields are defined by Dispatch Router:</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="22%" />
+<col width="19%" />
+<col width="59%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Field</em></th>
+<th class="head"><em>Type</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>x-opt-qd.ingress</td>
+<td>string</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>x-opt-qd.trace</td>
+<td>list of string</td>
+<td>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.</td>
+</tr>
+<tr class="row-even"><td>x-opt-qd.to</td>
+<td>string</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>x-opt-qd.phase</td>
+<td>integer</td>
+<td>The address-phase, if not zero, for messages flowing
+between routers.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="source-target-capabilities">
+<h2>3.3.2. Source/Target Capabilities<a class="headerlink" href="#source-target-capabilities" title="Permalink to this headline">.</a></h2>
+<p>The following Capability values are used in Sources and Targets.</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="17%" />
+<col width="83%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Capability</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>qd.router</td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td>qd.router-data</td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="dynamic-node-properties">
+<h2>3.3.3. Dynamic-Node-Properties<a class="headerlink" href="#dynamic-node-properties" title="Permalink to this headline">.</a></h2>
+<p>The following dynamic-node-properties are used by Dispatch in Sources.</p>
+<table border="1" class="docutils">
+<colgroup>
+<col width="22%" />
+<col width="78%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Property</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td>x-opt-qd.address</td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="addresses-and-address-formats">
+<h2>3.3.4. Addresses and Address Formats<a class="headerlink" href="#addresses-and-address-formats" title="Permalink to this headline">.</a></h2>
+<p>The following AMQP addresses and address patterns are used within
+Dispatch Router.</p>
+<div class="section" id="address-patterns">
+<h3>3.3.4.1. Address Patterns<a class="headerlink" href="#address-patterns" title="Permalink to this headline">.</a></h3>
+<table border="1" class="docutils">
+<colgroup>
+<col width="37%" />
+<col width="63%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Pattern</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><cite>_local/<addr></cite></td>
+<td>An address that references a locally attached
+endpoint. Messages using this address pattern shall not
+be routed over more than one link.</td>
+</tr>
+<tr class="row-odd"><td><cite>_topo/0/<router>/<addr></cite></td>
+<td><p class="first">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="last">The ‘0’ component immediately preceding the router-id
+is a placeholder for an _area_ which may be used in
+the future if area routing is implemented.</p>
+</td>
+</tr>
+<tr class="row-even"><td><cite><addr></cite></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="section" id="supported-addresses">
+<h3>3.3.4.2. Supported Addresses<a class="headerlink" href="#supported-addresses" title="Permalink to this headline">.</a></h3>
+<table border="1" class="docutils">
+<colgroup>
+<col width="35%" />
+<col width="65%" />
+</colgroup>
+<thead valign="bottom">
+<tr class="row-odd"><th class="head"><em>Address</em></th>
+<th class="head"><em>Description</em></th>
+</tr>
+</thead>
+<tbody valign="top">
+<tr class="row-even"><td><cite>$management</cite></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><cite>_topo/0/Router.E/$management</cite></td>
+<td>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.</td>
+</tr>
+<tr class="row-even"><td><cite>_local/qdhello</cite></td>
+<td>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.</td>
+</tr>
+<tr class="row-odd"><td><cite>_local/qdrouter</cite></td>
+<td>The router entity in each of the connected routers. This
+address is used by a router to communicate with other
+routers in the network.</td>
+</tr>
+<tr class="row-even"><td><cite>_topo/0/Router.E/qdrouter</cite></td>
+<td>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.</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="section" id="implementation-of-the-amqp-management-specification">
+<h2>3.3.5. Implementation of the AMQP Management Specification<a class="headerlink" href="#implementation-of-the-amqp-management-specification" title="Permalink to this headline">.</a></h2>
+<p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
+emerging AMQP Management specification (draft 9).</p>
+<p>Differences from the specification:</p>
+<ul class="simple">
+<li>The <cite>name</cite> 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.</li>
+<li>The <cite>REGISTER</cite> and <cite>DEREGISTER</cite> operations are not implemented. The router
+automatically discovers peer routers via the router network and makes
+their management addresses available via the standard GET-MGMT-NODES
+operation.</li>
+</ul>
+</div>
+</div>
+
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/book/auto_links.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-0.6.0/book/auto_links.html.in b/input/releases/qpid-dispatch-0.6.0/book/auto_links.html.in
new file mode 100644
index 0000000..6a66f25
--- /dev/null
+++ b/input/releases/qpid-dispatch-0.6.0/book/auto_links.html.in
@@ -0,0 +1,213 @@
+
+
+ <div class="section" id="indirect-waypoints-and-auto-links">
+<h1>2.5. Indirect Waypoints and Auto-Links<a class="headerlink" href="#indirect-waypoints-and-auto-links" title="Permalink to this headline">.</a></h1>
+<p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
+improvement on an earlier somewhat experimental feature called
+Waypoints.</p>
+<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>
+<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>
+<blockquote>
+<div><ul class="simple">
+<li>The name of the connector/listener that resulted in the connection
+of the container, or</li>
+<li>The AMQP container-id of the remote container.</li>
+</ul>
+</div></blockquote>
+<div class="section" id="queue-waypoint-example">
+<h2>2.5.1. Queue Waypoint Example<a class="headerlink" href="#queue-waypoint-example" title="Permalink to this headline">.</a></h2>
+<p>Here is an example configuration for routing messages deliveries
+through a pair of queues on a broker:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>connector {
+ name: broker
+ role: route-container
+ host: <hostname>
+ port: <port>
+ sasl-mechanisms: 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
+}
+</pre></div>
+</div>
+<p>The <em>address</em> entity identifies a namespace (queue.*) that will be
+used for routing messages through queues via autolinks. The four
+<em>autoLink</em> entities identify the head and tail of two queues on the
+broker that will be connected via auto-links.</p>
+<p>If there is no broker connected, the auto-links shall remain
+<em>inactive</em>. This can be observed by using the <em>qdstat</em> tool:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>If a broker comes online with a queue called <em>queue.first</em>, the
+auto-links will attempt to activate:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>Note that two of the auto-links are in <em>failed</em> state because the
+queue does not exist on the broker.</p>
+<p>If we now use the Qpid Proton example application <em>simple_send</em> to
+send three messages to queue.first via the router:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python simple_send.py -a 127.0.0.1/queue.first -m3
+all messages confirmed
+</pre></div>
+</div>
+<p>and then look at the address statistics on the router:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<p>we see that <em>queue.first</em> appears twice in the list of addresses. The
+<em>phs</em>, or phase column shows that there are two phases for the
+address. Phase ‘0’ is for routing message deliveries from producers
+to the tail of the queue (the <em>out</em> auto-link associated with the
+queue). Phase ‘1’ is for routing deliveries from the head of the
+queue to subscribed consumers.</p>
+<p>Note that three deliveries have been counted in the “in” and “out”
+columns for phase ‘0’. The “in” column represents the three messages
+that arrived from simple_send and the “out” column represents the
+three deliveries to the queue on the broker.</p>
+<p>If we now use <em>simple_recv</em> to receive three messages from this
+address:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python simple_recv_noignore.py -a 127.0.0.1:5672/queue.first -m3
+{u'sequence': int32(1)}
+{u'sequence': int32(2)}
+{u'sequence': int32(3)}
+</pre></div>
+</div>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>$ 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
+</pre></div>
+</div>
+<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 class="section" id="sharded-queue-example">
+<h2>2.5.2. Sharded Queue Example<a class="headerlink" href="#sharded-queue-example" title="Permalink to this headline">.</a></h2>
+<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 class="highlight-python"><div class="highlight"><pre><span></span>connector {
+ name: broker1
+ role: route-container
+ host: <hostname>
+ port: <port>
+ sasl-mechanisms: ANONYMOUS
+}
+
+connector {
+ name: broker2
+ role: route-container
+ host: <hostname>
+ port: <port>
+ sasl-mechanisms: 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
+}
+</pre></div>
+</div>
+<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 class="section" id="dynamically-adding-shards">
+<h2>2.5.3. Dynamically Adding Shards<a class="headerlink" href="#dynamically-adding-shards" title="Permalink to this headline">.</a></h2>
+<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 <em>qdmanage</em>:</p>
+<div class="highlight-python"><div class="highlight"><pre><span></span>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
+</pre></div>
+</div>
+</div>
+</div>
+
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org