<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0">
 <channel>
  <title>Zero Configuration Networking</title>
  <link>http://docs.openlinksw.com/mt/UDAZeroConf.html</link>
  <description>Multi-Tier User Guide</description>
  <managingEditor />
  <pubDate>Wed, 09 Apr 2008 14:37:12 GMT</pubDate>
  <generator />
  <webMaster>webmaster@openlinksw.com</webMaster>
  <image>
    <title>Multi-Tier User Guide</title>
    <url>http://docs.openlinksw.com/mt/../images/mt/misc/logo.jpg</url>
    <link>http://docs.openlinksw.com/mt/UDAZeroConf.html</link>
    <description>Multi-Tier User Guide</description>
  </image>
  <item>
    <guid>http://docs.openlinksw.com/mt/zeroconfintro.html</guid>
    <author />
    <category>Introduction</category>
    <link>http://docs.openlinksw.com/mt/zeroconfintro.html</link>
    <pubDate>Wed, 09 Apr 2008 14:37:12 GMT</pubDate>
    <title>Introduction</title>
    <description>Zero Configuration Networking, also known as ZeroConf, is networking that 
 needs nothing to be pre-configured and no administration to operate.  Zero 
 Configuration Networking uses industry standard IP protocols to allow devices 
 to automatically find each other without the need to enter IP addresses or 
 configure DNS servers.

ZeroConf enables services on a network built with this support to be 
 automatically discovered, thereby requiring no knowledge on the part of the 
 end user attempting to use this service about the specifics of its configuration, 
 just that it is available for use if selected.

Using ZeroConfig for installation rollouts or for site maintenance 
  can significantly reduce administration overhead.  Because the client ODBC 
  Driver is bound to a service name only, should the details of that service change 
  the client will automatically re-acquire the new details (this does not include changes 
  to the name of the service).  For example, 200 client installations configured to 
  use the service &quot;SalesDB1&quot;,  moving the &quot;Sales&quot; database to another server, 
  perhaps even a different database does not required any further client 
  configuration, they will automatically connect to the new server.

ZeroConf configuration on the server is kept to a minimum.  The 
  host and port number of the Request Broker are automatically supplied to the 
  ZeroConf service descriptions on the server when they are broadcast over 
  the network.  Furthermore, ZeroConf service descriptions can be based 
  directly on a Server Type that maps to a Database Agent.  
  If we consider the above example again, moving the &quot;Sales&quot; 
  database to another machine will not need any ZeroConf adjustment on the
  server either, the new host and port and automatically discovered and 
  broadcast with no administrator intervention other than to start the 
  new Broker and Database.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/mt/zerosrvconf.html</guid>
    <author />
    <category>Server Configuration</category>
    <link>http://docs.openlinksw.com/mt/zerosrvconf.html</link>
    <pubDate>Wed, 09 Apr 2008 14:37:12 GMT</pubDate>
    <title>Server Configuration</title>
    <description>The OpenLink Multi-Tier Request Broker now has the ability to Broadcast 
  ZeroConf services of available Database agent connections on the network.  
  These can be discovered by the the OpenLink Multi-Tier ODBC client.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/mt/zeroclientconf.html</guid>
    <author />
    <category>Client Configuration</category>
    <link>http://docs.openlinksw.com/mt/zeroclientconf.html</link>
    <pubDate>Wed, 09 Apr 2008 14:37:12 GMT</pubDate>
    <title>Client Configuration</title>
    <description />
  </item>
 </channel>
</rss>
