Private JXTA Rendezvous

From the JXTA mailing list…

If you use ext:config (http://wiki.java.net/bin/view/Jxta/ExtConfig) you can specify alternative “seed list bootstraps.” The bulk of this is explained in the “My MyJXTA” blog entry:

http://weblogs.java.net/blog/gonzo/archive/2005/02/my_myjxta.html

Here’s a recap:

create your own profile(.xml)

in it, override the following values:

/jxta/network/rendezVous/@bootstrap
/jxta/network/relays/@bootstrap

the bootstrap value can be any valid URL, eg:

http://rdv.jxtahosts.net/cgi-bin/rendezvous.cgi?2
http://rdv.jxtahosts.net/cgi-bin/relays.cgi?2

note: the above are the pubnet defaults

you can use file URLS, which are nice for testing:

file:///tmp/rdv.txt
file:///tmp/rly.txt

the format of the bootstrap seed list is a newline delimited
list of URIs that map to the associated JXTA service, eg:

http://209.128.126.108:9700
tcp://209.128.126.108:9701

note: the above are derived from the default bootstrap

to close the loop, host a bootstrap.txt file on your server
and add the bootstrap address to your profile as described
above.

you can test your jxta instances via telnet, eg:

# tcp:
% telent IP PORT

# http
% telnet IP PORT
GET / HTTP/1.0

You can set the bootstraps via the the Configurator api as well but I recommend going w/ the profile.

Lastly, if you choose not to use ext:config you can bake the seed lists into a PlatformConfig template or use the JXTA doc/adv APIs.

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

Comments are closed.