Re: ExtConfig and Multi-homed machines

Hey Glen -

  Sorry about the delay in responding.

  You will likely want to "null out or change" the RendezVous and Relays 
Bootstrap entries, eg:

<jxta>
...
  <network>
    <rendezVous bootstrap="" ...
    <relays bootstrap="" ...

  This is so that the "default" bootstrap (aka seed) list will not be 
inlined during configuration
  generation.

  Alternatively, you can specify your own "bootstrap uri(s)" which 
simply point to a list of
  known|stable RendezVous and Relay peers. Often I use file URIs, eg:

...
    <rendezVous bootstrap="file:///tmp/rdv.txt" ...

  Further, you will likely want to turn multicast off, which is the 
default for Profile.EDGE.
  To turn it off, consider:

...
  <transport>
    <tcp>
      <address ...
        <multicast enabled="false" ...

  Lastly, you can add "known" RendezVous and/or Relay peers addresses as 
network attributes,
  eg:

...
  <network>
    <rendezVous bootstrap="file:///tmp/rdv.txt" ...
      <address>tcp://1.2.3.4:9701</address>
      <address>http://1.2.3.4:9700</address>
    </rendezVous

  Now, as to setting the TCP address via the Configurator API (vs 
declartively via a Profile)
  there is a jUnit test that does just this, IIRC, within the Platform 
project codebase:

    
platform/binding/java/test/src/net/jxta/ext/config/TransportTest.testTCP()

  Let's compare code and runtime results and see if indeed there is an 
issue we should
  work to address in this regard.

  I do recommend that folks consider using Profiles to manage their 
deployments, for a
  number of reasons, but you are most assuredly free to use the 
Configurator API (which
  the Profile simply drives) as it should work as advertised as well.

  hth,

- james

--

James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo

MyJXTA :: use it - learn it - do it

Java == platform independence
XML  == application independence
JXTA == network independence

Secure End-to-End Computing 



Glenn wrote:

>Hi,
>
>I have a few machines each is multi-homed with 3 network interfaces, my test network has 4 subnets with routers connecting them and no access to external networks. I have some machines on subnets 1,2,3, others on subnets 2,3,4. I want to configure them such that jxta discovery only occurs on subnets 1 and 2. Does anyone know how to specify that jxta use a specific ip address/interface for performing discovery.
>
>I have written some configuration code to programatically configure the machines, but it seems when I call tcpTransportAddress.setAddress(uri) the InterfaceAddress property in the PlatformConfig is not set.  So it appears that discovery is occurring on all subnets connected to the machine.
>
>Any ideas would be greatly appreciated.
>
>
>Thanks Glenn
>
>
>
>
>_______________________________________________
>Join Excite! - http://www.excite.com
>The most personalized portal on the Web!
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>  
>