Tutorials

Jini Example
Jxta Example
Web Services

Related

Jxta
Jini
Web Services

For More Info

From P2P to Web Services and Grids: Peers in a Client/Server World
Ian J. Taylor, 2004
Publisher: Springer
ISBN: 1-85233-869-5

Configuring the Peer using the JXTA Configurator

A JXTA Peer can operate as a client, a server and a Rendezvous (JXTA’s lookup mechanism) at the same time and therefore all JXTA Peers are run in exactly the same way. When a JXTA Peer is started it launches a JXTA Configurator application which allows you to configure and bootstrap the Peer. Using the Configurator, you can specify which port the Peer listens on, where any Rendezvous Peers are, whether this Peer will be operating as a Rendezvous and also which username and password you will be using to access the JXTA network.

Peers are set up using the JXTA Configurator. There are 4 screens to configure. Screen one:

The Peer Name can be set to what ever you want to. If you are behind a firewall, then you need to specify your proxy server here also (there is no need in this tutorial).

SETTING:

  • type in your name here so others in the group can see you when they view other peers.

The Advanced Settings screen is used to set parameters about the environment in which the peer is running within:

  • TCP Settings: By default, TCP is enabled on the default network interface (port 9701). When TCP is enabled, each instance of a JXTA platform is bound to a specific TCP port number of a given peer. If you select Manual configuration an additional box "always manual" will be displayed. If you select this box, this configuration screen will always be displayed and the user will need to manually select the network interface for TCP each time a JXTA peer is booted (e.g. useful for nodes using DHCP where the IP address can change).

    A peer may have multiple network interfaces and so you can select which network interface should be used from the pull-down menu to the right. You can also change the port used for TCP (multiple instances of the JXTA platform can be run on a single peer by using different TCP port numbers.  Finally, if the JXTA peer is located behind NAT, you may need to specify the public NAT address for this node.

  • HTTP Settings: By default, HTTP is enabled on the default network interface (port 9700). HTTP must be enabled if the JXTA peer is located behind a firewall or NAT. If you want to use a different network interface for HTTP, use the pull-down menu to select the desired network interface (IP address). Use port, manual as in TCP/IP case. If you’re running JXTA on an intranet (i.e. with no internet connection) then this must be disabled.

SETTINGS:

Ø      TCP Setting: leave this to the default value. You are only running one peer on your machine so the setting is fine as it is.

Ø      HTTP Settings: leave as it is. We all have a connection to the internet so the JXTA web site can be contacted.  There is no reason therefore to change this setting.

The Rendezvous/Relay screen is used to specify the peer’s rendezvous connections (if any):

The Rendezvous/Router settings panel enables you to specify rendezvous and HTTP relay settings. By default, the JXTA peer does not act as a rendezvous node nor a relay, but is configured to use a relay peer. Peer to act as a Rendezvous. HTTP relaying is not required here since we are not connected behind a firewall.

Finally, the last screen allows you to enter your user name and password.  Enter a user name and password (you set this the first time the JXTA configurator is run so you can choose anything).


Back to Trail