| <div class="wiki-content maincontent"><h3 id="ZeroConfTransportReference-TheZeroConfTransport">The ZeroConf Transport</h3> |
| |
| <p>The ZeroConf transport works just like <a shape="rect" href="discovery-transport-reference.html">Discovery Transport</a>, except that it uses a <a shape="rect" href="zeroconf.html">ZeroConf</a> based discovery agent to locate the list of broker uris to connect to.</p> |
| |
| <h4 id="ZeroConfTransportReference-ConfigurationSyntax">Configuration Syntax</h4> |
| |
| <p><strong>zeroconf:serviceName?transportOptions</strong><br clear="none"> |
| or<br clear="none"> |
| <strong>zeroconf:serviceName</strong></p> |
| |
| |
| <p>where <em>serviceName</em> is the Zeroconf service name; which seems to start with an underscore (_) and must end with a dot (.). So we can use this service name to distinguish development, UAT & production brokers - or group them into domains etc.</p> |
| |
| <p>Note that to be able to use ZeroConf to find brokers, the brokers need to have <a shape="rect" href="discovery.html">Discovery</a> enabled. To configure discovery in a Broker you should use the <a shape="rect" href="xml-configuration.html">Xml Configuration</a>. Its basically something like...</p> |
| |
| <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> |
| <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;"> |
| <broker name="foo"> |
| <transportConnectors> |
| <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" discoveryUri="zeroconf:_activemq_development. /> |
| </transportConnectors> |
| ... |
| </broker> |
| </pre> |
| </div></div> |
| |
| <h5 id="ZeroConfTransportReference-ExampleclientURI">Example client URI</h5> |
| |
| <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> |
| <pre>zeroconf:_activemq_development. |
| </pre> |
| </div></div></div> |
| |