http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/content/releases/qpid-dispatch-0.6.1/man/qdrouterd.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-dispatch-0.6.1/man/qdrouterd.html b/content/releases/qpid-dispatch-0.6.1/man/qdrouterd.html new file mode 100644 index 0000000..0bbe6d2 --- /dev/null +++ b/content/releases/qpid-dispatch-0.6.1/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">Broker for Java</a></li> + <li><a href="/components/cpp-broker/index.html">C++ broker</a></li> + <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li> + </ul> + </section> + + <section> + <h3>Resources</h3> + + <ul> + <li><a href="/dashboard.html">Dashboard</a></li> + <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index";>Wiki</a></li> + <li><a href="/resources.html">More resources</a></li> + </ul> + </section> + </div> + </div> + + <div id="-search" class="panel" style="display: none;"> + <form action="http://www.google.com/search"; method="get"> + <input type="hidden" name="sitesearch" value="qpid.apache.org"/> + <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/> + <button type="submit">Search</button> + <a href="/search.html">More ways to search</a> + </form> + </div> + + <div id="-middle" class="panel"> + <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.6.1/index.html">Qpid Dispatch 0.6.1</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/48fa0554/content/releases/qpid-dispatch-0.6.1/man/qdstat.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-dispatch-0.6.1/man/qdstat.html b/content/releases/qpid-dispatch-0.6.1/man/qdstat.html new file mode 100644 index 0000000..a4d4ef5 --- /dev/null +++ b/content/releases/qpid-dispatch-0.6.1/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">Broker for Java</a></li> + <li><a href="/components/cpp-broker/index.html">C++ broker</a></li> + <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li> + </ul> + </section> + + <section> + <h3>Resources</h3> + + <ul> + <li><a href="/dashboard.html">Dashboard</a></li> + <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index";>Wiki</a></li> + <li><a href="/resources.html">More resources</a></li> + </ul> + </section> + </div> + </div> + + <div id="-search" class="panel" style="display: none;"> + <form action="http://www.google.com/search"; method="get"> + <input type="hidden" name="sitesearch" value="qpid.apache.org"/> + <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/> + <button type="submit">Search</button> + <a href="/search.html">More ways to search</a> + </form> + </div> + + <div id="-middle" class="panel"> + <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.6.1/index.html">Qpid Dispatch 0.6.1</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/48fa0554/content/releases/qpid-dispatch-0.6.1/release-notes.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-dispatch-0.6.1/release-notes.html b/content/releases/qpid-dispatch-0.6.1/release-notes.html new file mode 100644 index 0000000..75d37a1 --- /dev/null +++ b/content/releases/qpid-dispatch-0.6.1/release-notes.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>Qpid Dispatch 0.6.1 Release Notes - Apache Qpid™</title> + <meta http-equiv="X-UA-Compatible" content="IE=edge"/> + <meta name="viewport" content="width=device-width, initial-scale=1.0"/> + <link rel="stylesheet" href="/site.css" type="text/css" async="async"/> + <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/> + <script type="text/javascript">var _deferredFunctions = [];</script> + <script type="text/javascript" src="/deferred.js" defer="defer"></script> + <!--[if lte IE 8]> + <link rel="stylesheet" href="/ie.css" type="text/css"/> + <script type="text/javascript" src="/html5shiv.js"></script> + <![endif]--> + + <!-- Redirects for `go get` and godoc.org --> + <meta name="go-import" + content="qpid.apache.org git https://git-wip-us.apache.org/repos/asf/qpid-proton.git"/> + <meta name="go-source" + content="qpid.apache.org +https://github.com/apache/qpid-proton/blob/go1/README.md +https://github.com/apache/qpid-proton/tree/go1{/dir} +https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/> + </head> + <body> + <div id="-content"> + <div id="-top" class="panel"> + <a id="-menu-link"><img width="16" height="16" src="" alt="Menu"/></a> + + <a id="-search-link"><img width="22" height="16" src="" alt="Search"/></a> + + <ul id="-global-navigation"> + <li><a id="-logotype" href="/index.html">Apache Qpid<sup>™</sup></a></li> + <li><a href="/documentation.html">Documentation</a></li> + <li><a href="/download.html">Download</a></li> + <li><a href="/discussion.html">Discussion</a></li> + </ul> + </div> + + <div id="-menu" class="panel" style="display: none;"> + <div class="flex"> + <section> + <h3>Project</h3> + + <ul> + <li><a href="/overview.html">Overview</a></li> + <li><a href="/components/index.html">Components</a></li> + <li><a href="/releases/index.html">Releases</a></li> + </ul> + </section> + + <section> + <h3>Messaging APIs</h3> + + <ul> + <li><a href="/proton/index.html">Qpid Proton</a></li> + <li><a href="/components/jms/index.html">Qpid JMS</a></li> + <li><a href="/components/messaging-api/index.html">Qpid Messaging API</a></li> + </ul> + </section> + + <section> + <h3>Servers and tools</h3> + + <ul> + <li><a href="/components/java-broker/index.html">Broker for Java</a></li> + <li><a href="/components/cpp-broker/index.html">C++ broker</a></li> + <li><a href="/components/dispatch-router/index.html">Dispatch router</a></li> + </ul> + </section> + + <section> + <h3>Resources</h3> + + <ul> + <li><a href="/dashboard.html">Dashboard</a></li> + <li><a href="https://cwiki.apache.org/confluence/display/qpid/Index";>Wiki</a></li> + <li><a href="/resources.html">More resources</a></li> + </ul> + </section> + </div> + </div> + + <div id="-search" class="panel" style="display: none;"> + <form action="http://www.google.com/search"; method="get"> + <input type="hidden" name="sitesearch" value="qpid.apache.org"/> + <input type="text" name="q" maxlength="255" autofocus="autofocus" tabindex="1"/> + <button type="submit">Search</button> + <a href="/search.html">More ways to search</a> + </form> + </div> + + <div id="-middle" class="panel"> + <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-0.6.1/index.html">Qpid Dispatch 0.6.1</a></li><li>Qpid Dispatch 0.6.1 Release Notes</li></ul> + + <div id="-middle-content"> + <h1 id="qpid-dispatch-061-release-notes">Qpid Dispatch 0.6.1 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-367";>DISPATCH-367</a> - balanced distribution needs to be more... balanced.</li> +</ul> + +<h2 id="bugs-fixed">Bugs fixed</h2> + +<ul> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-341";>DISPATCH-341</a> - router did not respond to request to drain a message-routed consumers link credit</li> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-364";>DISPATCH-364</a> - Inter-router listeners should not permit normal endpoint traffic</li> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-365";>DISPATCH-365</a> - Standalone router crashes if an interior router attempts to connect to it</li> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-366";>DISPATCH-366</a> - When delivery fails the router sends the RELEASED disposition, not MODIFIED</li> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-387";>DISPATCH-387</a> - Router core dumps with misbehaving client</li> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-443";>DISPATCH-443</a> - Reverse name lookup on listener connections can hang the entire router</li> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-460";>DISPATCH-460</a> - Regression: Link-routed dynamic sources don't work</li> +</ul> + +<h2 id="tasks">Tasks</h2> + +<ul> +<li><a href="https://issues.apache.org/jira/browse/DISPATCH-410";>DISPATCH-410</a> - console build fixups</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/48fa0554/content/releases/qpid-dispatch-master/index.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-dispatch-master/index.html b/content/releases/qpid-dispatch-master/index.html index b96a0a5..4898dc5 100644 --- a/content/releases/qpid-dispatch-master/index.html +++ b/content/releases/qpid-dispatch-master/index.html @@ -121,7 +121,7 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/> <h2 id="warning-this-is-a-snapshot-of-work-in-progress">Warning! This is a snapshot of work in progress</h2> <p>Code and documentation found here may be unstable, incorrect, or -incomplete. For a smoother experience, see the <a href="/releases/qpid-dispatch-0.6.0/index.html">current stable +incomplete. For a smoother experience, see the <a href="/releases/qpid-dispatch-0.6.1/index.html">current stable release</a>.</p> <p>This content was generated at 09:51 on Monday, 08 August 2016.</p> http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/_images/console_charts.png ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/_images/console_charts.png b/input/releases/qpid-dispatch-0.6.1/_images/console_charts.png new file mode 100644 index 0000000..169c2ca Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.1/_images/console_charts.png differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/_images/console_entity.png ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/_images/console_entity.png b/input/releases/qpid-dispatch-0.6.1/_images/console_entity.png new file mode 100644 index 0000000..130c7e7 Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.1/_images/console_entity.png differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/_images/console_login.png ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/_images/console_login.png b/input/releases/qpid-dispatch-0.6.1/_images/console_login.png new file mode 100644 index 0000000..63e22c6 Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.1/_images/console_login.png differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/_images/console_overview.png ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/_images/console_overview.png b/input/releases/qpid-dispatch-0.6.1/_images/console_overview.png new file mode 100644 index 0000000..af25f36 Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.1/_images/console_overview.png differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/_images/console_schema.png ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/_images/console_schema.png b/input/releases/qpid-dispatch-0.6.1/_images/console_schema.png new file mode 100644 index 0000000..ba56c7b Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.1/_images/console_schema.png differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/_images/console_topology.png ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/_images/console_topology.png b/input/releases/qpid-dispatch-0.6.1/_images/console_topology.png new file mode 100644 index 0000000..ae4b22a Binary files /dev/null and b/input/releases/qpid-dispatch-0.6.1/_images/console_topology.png differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/book/addressing.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/addressing.html.in b/input/releases/qpid-dispatch-0.6.1/book/addressing.html.in new file mode 100644 index 0000000..d472702 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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/48fa0554/input/releases/qpid-dispatch-0.6.1/book/amqp-mapping.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/amqp-mapping.html.in b/input/releases/qpid-dispatch-0.6.1/book/amqp-mapping.html.in new file mode 100644 index 0000000..051d754 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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/48fa0554/input/releases/qpid-dispatch-0.6.1/book/auto_links.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/auto_links.html.in b/input/releases/qpid-dispatch-0.6.1/book/auto_links.html.in new file mode 100644 index 0000000..6a66f25 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/book/basic_usage.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/basic_usage.html.in b/input/releases/qpid-dispatch-0.6.1/book/basic_usage.html.in new file mode 100644 index 0000000..323fdbf --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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/48fa0554/input/releases/qpid-dispatch-0.6.1/book/book.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/book.html.in b/input/releases/qpid-dispatch-0.6.1/book/book.html.in new file mode 100644 index 0000000..1f1fe66 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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/48fa0554/input/releases/qpid-dispatch-0.6.1/book/client_compatibility.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/client_compatibility.html.in b/input/releases/qpid-dispatch-0.6.1/book/client_compatibility.html.in new file mode 100644 index 0000000..95ba509 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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/48fa0554/input/releases/qpid-dispatch-0.6.1/book/console.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/console.html.in b/input/releases/qpid-dispatch-0.6.1/book/console.html.in new file mode 100644 index 0000000..58d31d9 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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/48fa0554/input/releases/qpid-dispatch-0.6.1/book/console_installation.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/console_installation.html.in b/input/releases/qpid-dispatch-0.6.1/book/console_installation.html.in new file mode 100644 index 0000000..001b9a3 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/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> + --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
