commande |
jxta version JXTA_2_2_00 1245121503 JXTA_2_2_00-12-15-03 |
cat | displays on the stdout the
content of a jxta object stored in a environment variable,
currently limited to jxta types
jxta> mkadv -p apipe JXTA>cat consin |
send |
|
man
command |
jxta version JXTA_2_2_00 1245121503 JXTA_2_2_00-12-15-03 |
cat |
Concatanate and
display a Shell object JXTA>man cat NAME cat - Concatanate and display a Shell object SYNOPSIS cat [-p] <objectName> DESCRIPTION 'cat' is the Shell command that displays on stdout the content of objects stored in environment variables. 'cat' knows how to display a limited (but growing) set of JXTA objects Advertisement, Message and StructuredDocument) If you are not sure, try to cat the object anyway: the command will let you know if it can or not display that object. OPTIONS -p Pretty display EXAMPLE JXTA> importfile -f /home/tra/myfile myfile JXTA> cat -p myfile This command imports the file '/home/tra/myfile' into the 'myfile' environment variable and displays it on stdout SEE ALSO |
chpgrp |
Change the
current peer group JXTA>man chpgrp NAME chpgrp - change the current peer group SYNOPSIS chpgrp <name> DESCRIPTION The 'chpgrp' command is used to switch the default Shell peer group 'stdgroup' variable to another group that was previously joined via a 'join' command. The 'join' command is used to join a peergroup. After changing group, the Shell 'stdgroup' variable is set to the value of the new peer group joined. EXAMPLE JXTA>mygroupadv = mewpgrp mygroup JXTA>mkpgrp -d mygroupadv JXTA>join mygroup JXTA>chpgrp moi This creates a new peergroup which is cloning the services of the parent peer group. You can find the services of the current peer group via the command 'whoami -g'. The new group is given the name 'mygroup'. Before you can do anything with the group you need to join the group via the 'join' command. The 'chpgrp' command is used to change the default group to the new group 'moi'. SEE ALSO mkadv mkpgrp join |
clear |
Clear
the shell's screen JXTA>man clear NAME clear - clear the shell's screen. SYNOPSIS clear DESCRIPTION 'clear' clears the shell's screen. The command is implemented internally within the shell, and might not be available for all shell implementations. |
cms |
No
description available for this ShellApp JXTA>man cms NAME cms SYNOPSIS cms DESCRIPTION Initialize cms and show its status OPTIONS EXAMPLE SEE ALSO share unshare ls rcp |
dumpcm |
Dump the
content of the local cache (CM) JXTA>man dumpcm NAME dumpcm - Dump the content of the local cache (CM) SYNOPSIS dumpcm -type type of file being dumped (index|offsets|db) -dir the directory to dump -file the file to dump DESCRIPTION dumpcm allows to dump onto the screen the content of the local cache (CM). |
env |
Display
environment variable JXTA>man env NAME env - display environment variable SYNOPSIS env DESCRIPTION 'env' displays all the defined environment variables in the Shell seesion. The following environment variables are defined by default: consin = Default Console InputPipe consout = Default Console OutputPipe stdout = Default OutputPipe stdin = Default InputPipe Shell = Root Shell stdgroup = current peer group rootgroup = parent group of current group netgroup = Default Net PeerGroup worldgroup = Default World PeerGroup Shell environement variables are defined as a result of executing Shell commands. The '=' operator can be used to assign value to a particular variable. For example `myenv = mkmsg` will assign a new message object to the 'myenv' environment variable EXAMPLE JXTA> env This command will display all environment variables SEE ALSO setenv Shell |
exit |
Exit the Shell JXTA>man exit NAME exit - exit the Shell SYNOPSIS exit DESCRIPTION 'exit' command is used to exit the Shell SEE ALSO Shell |
exportfile |
Export to an
external file JXTA>man exportfile NAME exportfile - export to an external file SYNOPSIS exportfile -f <filename> [<env>] DESCRIPTION 'exportfile' exports the content of a Shell environment variable into an external file. The exported object is stored in the supplied filename argument. If no variable name is given, the 'stdin' pipe is used to read data and saved them into the file. 'exportfile' is the reverse operation of 'importfile' The Shell environment variable is not deleted after the the file is created EXAMPLE JXTA> exportfile -f /home/tra/myfile myfile This command saves into the file '/home/tra/myfile' the content of the 'myfile' environment variable SEE ALSO importfile |
flush |
flush a jxta
advertisement JXTA>man flush NAME flush - flush a jxta advertisement SYNOPSIS flush [-d document] advertisement to remove DESCRIPTION use "flush" to flush an advertisement from cache OPTIONS -d document env advertisement to remove EXAMPLE JXTA>flush -d peer10 removes the peer advertisement peer10 |
get |
Get data from a
pipe message JXTA>man get NAME get - get data from a pipe message SYNOPSIS get <msg> <tag> DESCRIPTION 'get' retrieve the tag body of a message. JXTA messages are composed a set of tag body, each identified with an unique tag name A message tag name is supplied to command to specify which tag body to extract. EXAMPLE JXTA> pipeadv = newpipe -n mypipe JXTA> inpipe = mkpipe -i pipeadv JXTA> msg = recv inpipe JXTA> data = get msg mytag This example creates a pipe advertisement 'pipeadv', creates an input pipe 'inpipe', and receives a message 'msg'. The tag body of the message associated with the tag 'mytag' is retreived from the message via the 'get' command. SEE ALSO mkmsg put send recv mkadv newpipe mkpipe |
grep |
Search for
matching patterns JXTA>man grep NAME grep - search for matching patterns. SYNOPSIS grep [-c -i -n -v] searchPattern [<objectName>] DESCRIPTION 'grep' searches the named shell object for lines containing a match to the given search pattern. Matching lines are written to output. Regular expressions are not currently supported. If no object is specifed on the command line, grep will read from stdin. If stdin is the console, you may type in lines of text. Enter a '.' all by itself at the beginning of a line to finish. OPTIONS -c Just print count of matching lines. With -v, count non-matching. -i Ignore case when comparing text with search pattern. -n Show line numbers of matches found. -v Invert the sense of matching, to select non-matching lines. EXAMPLES JXTA>grep -i -n dog GroceryList 3:Hot dogs 7:Dog food JXTA>cat GroceryList | grep -c dog 2 |
groups |
Discover peer
groups JXTA>man groups groups - discover peer groups SYNOPSIS groups [-p peerid name attribute] [-n n] limit the number of responses to n from a single peer [-r] discovers peer groups using remote propagation [-l] displays group id as a hex string [-a] specify Attribute name to limit discovery to [-v] specify Attribute value to limit discovery to. wild card is allowed [-f] flush group advertisements DESCRIPTION use to discover peer groups by propagation or at a specified peer location. By default "groups" lists all the peer groups known (cached) by the local peer. The '-r' option is used to send a propagate request to find new peer groups. "groups" stores results in the local cache, and inserts advertisement(s) into the environment, using the default naming: groupX where X is a growing integer number. OPTIONS -p peerid discovers groups at a given peer location -r discovers groups by propagation -l displays group id as a hex string -a specify Attribute name to limit discovery to -v specify Attribute value to limit discovery to -n limit the number of responses to n from a single peer -f flush group advertisements no option returns known peer group advertisements EXAMPLE JXTA>groups -r or JXTA>groups -r -aName -vsocce* or JXTA>groups -r -aName -v*occer SEE ALSO whoami chpgrp join peers |
help |
No description
available for this ShellApp JXTA>man help No help available for this ShellApp |
history |
No description
available for this ShellApp JXTA>man history NAME history - prints out a list of previous commands SYNOPSIS history DESCRIPTION Lists the commands previously typed. Commands can be recalled in two ways: Use the up and down arrow keys to navigate through the list of commands. Use !<number>, where number is the number of the command as shown in the list displayed by history. SEE ALSO |
importfile |
Import an
external file JXTA>man importfile NAME importfile - import an external file SYNOPSIS importfile -f <filename> [<env>] DESCRIPTION 'importfile' imports an external file into a StructuredDocument object stored in a Shell environment variable. The name of the environment variable is specified as an argument. 'importfile' is the reverse operation of 'exportfile' EXAMPLE JXTA> importfile -f /home/tra/myfile myfile JXTA> cat myfile This command imports the file '/home/tra/myfile' into the 'myfile' environment variable SEE ALSO exportfile |
info |
flush a jxta
advertisement JXTA>man info NAME info - display info about an jxta advertisement SYNOPSIS info [-d document] DESCRIPTION use "info" to display info about an advertisement OPTIONS -d document env advertisement EXAMPLE JXTA>info -d peer10 displays Lifetime and expiration about peer10 |
instjar |
Installs
jar-files containing additional Shell commands JXTA>man instjar NAME instjar - installs one or more jar-files containing additional Shell commands. SYNOPSIS instjar [<jar-file> [...]] DESCRIPTION This command installs jar-files containing additional Shell commands. An arbirtary number of paths to jar-files can be supplied. If this command is invoked with no arguments it lists all installed jar-files. Use the given indices to uninstall jar-files with the 'uninstjar' command. The class-files of a command 'xxx' must be in the package 'net.jxta.impl.shell.bin.xxx' and the main-class must be named 'net.jxta.impl.shell.bin.xxx.xxx'. Accordingly the class-files must be placed in a directory 'net/jxta/impl/shell/bin/xxx/' within the jar-file, and must extend the ShellApp class. The list of installed jar-files is stored in the environment variable 'instjars'. EXAMPLE To install two jar-files 'c:/userlib/usrcmds.jar' and 'c:/userlib/toolscmds.jar: JXTA>instjar c:/userlib/usrcmds.jar c:/userlib/toolcmds.jar To list all installed jar-files with their indices: JXTA> instjar 0 c:/userlib/usrcmds.jar 1 c:/userlib/toolcmds.jar These indeces can be used to uninstall some jar-files with the 'uninstjar' command. SEE ALSO uninstjar JXTA> |
join |
Instantiate and
join peer group JXTA>man join NAME join - Instantiate and join peer group SYNOPSIS join [-d <adv> [-A]| [-a] <name>] [-r] [-c <credential>] DESCRIPTION The 'join' command is used to instantiate and join a peergroup that was created via the 'newpgrp' command or using an advertisement that was previously discovered. If no argument is given, join lists all the existing groups and their status (join, unjoined) and the current group on the local peer. After a group was joined successfully, the 'PG@<group name>' environment variable is created. This variable holds the group object. Upon joining the peer group depending on the membership authentication required, the user will be asked for the identity he/she wants to have in the peer group. An identity is used to assign credentials to users when accessing peer group ressouces. Each peer group can define their own set of identities available in the peer group. For example JXTA> join mygroup identity:tra passwd:XXXXX JXTA> OPTIONS [-r] Act as a rendezvous for the joined group. [-A] Instantiate, but do not authenticate (join) this peer group. [-a] Authenticate with an already joined peer group. [-d <adv>] Specify a shell variable holding a peergroup advertisement [-c <credential>] Specify a credential to join the peer group EXAMPLE JXTA>mygroupadv = newpgrp -n mygroup JXTA>join -d mygroupadv This creates a new peer group which is cloning the services of the parent peer group. You can find the services of the current peergroup via the command 'whoami -g'. The new group is given the name 'mygroup'. SEE ALSO newpgrp mkadv login leave chpgrp who |
kdb |
run the httpd JXTA>man kdb NAME kdb - a JXTA J2SE debugger SYNOPSIS kdb DESCRIPTION kdb allows the user to change LOG priorities and debug components. |
leave |
Leave a peer
group JXTA>man leave NAME leave - Leave a peer group SYNOPSIS leave [-k] OPTIONS [-k] The group will be stopped and deleted. DESCRIPTION The 'leave' command is used to leave a group that was previously joined via a 'join' or 'login' command. The 'join' command is used to join a peergroup. After leaving the group, the Shell 'stdgroup' variable is reset to the value of the default 'rootgroup' variable (NetPeerGroup). If the -k option was used, then this instance of the group is stopped and deleted. Before a user can use the group again, the user will have to rejoin the group via the 'join' command. EXAMPLE JXTA>mygroupadv = newpgrp -n mygroup JXTA>join -d mygroupadv JXTA>leave This creates a new peer group which is cloning the services of the parent peer group. You can find the services of the current peergroup via the command 'whoami -g'. The new group is given the name 'mygroup'. Finally, the group is left using the 'leave' command. SEE ALSO newpgrp join login who chpgrp |
login |
Authenticate
with the group's membership service. JXTA>man login NAME login - Authenticate with the group's membership service. SYNOPSIS login [-c <creddoc>] [-s <command>] [-- [args]] DESCRIPTION login prompts for authentication. If the authentication is completed then the specified command, if any is started. OPTIONS [-c <creddoc>] Authentication credential to provide to authenticator. [-s <command>] The shell command to start. [-- [args]] Arguments to be passed to <command>. SEE ALSO rshd rsh join |
man |
An on-line help
command that displays information about a specific Shell command JXTA>man man NAME man - get man page info about a command SYNOPSIS man <command> DESCRIPTION 'man' is an on-line help command that displays information about a specific Shell command. EXAMPLE JXTA> man mkpgrp This will display information about the mkpgrp command SEE ALSO |
mem |
Display memory informatiion JXTA>man mem NAME Display memory information SYNOPSIS mem [-g] DESCRIPTION use "mem" to display memory information OPTIONS -g Garbage collect prior to displaying memory |
mkadv |
Make an
advertisement from a document JXTA>man mkadv NAME mkadv - make an advertisement from a document SYNOPSIS mkadv [-d <doc>] DESCRIPTION 'mkadv' creates an advertisement from a document stored in a shell environment variable. A symbolic name can be associated with the advertisement. This name can be used to search for the advertisement. OPTIONS -d specifies a Shell environment variable that contains a document containing an advertisement EXAMPLE JXTA>importfile -f saveadv pipeadv JXTA>mypipeadv = mkadv -d pipeadv JXTA>inpipe = mkpipe -i mypipeadv This creates a pipe using an advertisement stored in a file. The file is imported as a document using the 'importfile' command. An advertisement is created from the document using 'mkadv' and finally an input pipe is instantiated using 'mkpipe'. SEE ALSO newpgrp mkpipe join whoami |
mkmsg |
Make a pipe
message JXTA>man mkmsg NAME mkmsg - make a pipe message SYNOPSIS mkmsg DESCRIPTION 'mkmsg' creates a new message to send/receive data from a pipe. The message object is stored in a Shell environment variable. If no name is assigned via the '=' operator, a default environment variable is created 'env#' for holding the message object (# is a growing integer number). JXTA messages are composed of multiple tag body parts. Each tag body is uniquely identified via a unique tag name. The tag name is used to insert ('put' command) a new tag body in a message, or to retrieve ('get' command) a tag body from a message EXAMPLE JXTA>mkmsg This creates a message object and puts it in the environment variable 'env#' where # is an integer number (ex. env4) You can assign a specific name to the message variable by assigning it a name via the '=' Shell operator. See below for example: JXTA>mymsg = mkmsg JXAT>put mymsg mytag data JXTA>send outpipe mymsg This create a new msg 'mymsg', stored data in the message body tag 'mytag'. The message is then sent via the output pipe 'outpipe' SEE ALSO send recv get put mkpipe mkadv |
mkpipe |
Create a pipe JXTA>man mkpipe NAME mkpipe - create a pipe SYNOPSIS mkpipe -i|o <pipe advertisement> DESCRIPTION 'mkpipe' creates an input pipe or an output pipe from a given pipe advertisement document. In order for pipes to communicate an input and output pipe needs to be created with the same pipe advertisement. PipeServiceService advertisements are structured documents that contains at least the unique pipe Id. The pipe Id uniquely identifies a pipe in the JXTA world. Pipes are not localized or binded to a physical peer. PipeServiceService connections are established by searching for pipe advertisements and resolving dynamically the location of an input pipe object binded to that advertisement. An input pipe can be binded to the same pipe advertisement on multiple peers transparently to the output pipe. The output pipe does not need to known on which physical peer the input pipe is located. To communicate with the pipe, the output pipe needs to search for the input pipe that binds that advertisement. OPTIONS -i create an input pipe -o create an output pipe EXAMPLE JXTA> pipeadv = newpipe -n mypipe JXTA> inpipe = mkpipe -i pipeadv JXTA> msg = recv inpipe JXTA> data = get msg mytag This example creates a pipe advertisement 'pipeadv' create an input pipe 'inpipe' and receive a message 'msg' The body of the message associated with the tag 'mytag' is retreived from the message via the 'get' command. SEE ALSO mkmsg put get send recv mkadv |
more |
Page through a
Shell object JXTA>man more NAME more - Page through a Shell object SYNOPSIS more [<doc>] DESCRIPTION 'more' is a Shell command that pages through the content of an object stored in environment variable. The name of the is provided as an argument. If no argument is supplied, the command takes its inputs from the 'stdin' shell pipe. EXAMPLE JXTA> cat myfile | more This command pipes the content of the variable 'myfile' into the 'more' command and displays it to the Shell console. SEE ALSO cat env |
newpgrp |
Create a new
peer group advertisement JXTA>man newpgrp NAME newpgrp - Create a new peer group advertisement SYNOPSIS newpgrp [-p | -i <idformat>] [-n <name>] OPTIONS [-i <idformat>] The ID Format to use for the group and default for all IDs created in group. [-p] The parent group should be explicit in the new peer group's ID. [-n <name>] Optional name for the peer group DESCRIPTION newpgrp creates a new peer group advertisement with a random group id which uses the same implementataion as the current peer group. You can find the services of the current peergroup via the command 'whoami -g'. EXAMPLE JXTA>mygroupadv = newpgrp mygroup This creates a new peergroup advertisement with the name 'mygroup'. Before you can do anything with the peergroup you need to join the group via the 'join' command. SEE ALSO whoami join leave peers chpgrp |
newpipe |
Create a new
pipe advertisment JXTA>man newpipe NAME newpipe - Create a new pipe advertisment SYNOPSIS newpipe [-p | -s] [-n <name>] OPTIONS [-s] Use a secure pipe. [-p] Use a propagate pipe. [-n <name>] Optional name for the pipe DESCRIPTION newpipe creates a new pipe advertisement with a random pipe id. EXAMPLE JXTA>mypipeadv = newpipe -n mypipe This creates a new pipe advertisement of the default type. The new pipe is given the name 'mypipe'. Before you can do anything with the pipe you need to instantiate it via the 'mkpipe' command. SEE ALSO mkpipe |
peerconfig |
Peer
Configuration JXTA>man peerconfig NAME peerconfig - Peer Configuration SYNOPSIS peerconfig DESCRIPTION peerconfig is used to re-configure a peer. The command forces the platform to show a configuration dialog the next time it starts. After the command is run the shell needs to be restarted in order to display the configuration dialog. FILES PlatformPeerGroup - Platform Advertisement |
peerinfo |
Get information
about peers JXTA>man peerinfo NAME peerinfo - get information about peers SYNOPSIS peerinfo [-p <peerEnv variable>] DESCRIPTION Use this to get monitoring information about this peer or remote peers in this group OPTIONS -p peerid gets peer info for a remote peer EXAMPLE JXTA>peerinfo -p peer2 Get info about peer2 SEE ALSO |
peers |
Discover peers JXTA>man peers NAME peers - discover peers SYNOPSIS peers [-p peerid name attribute] [-n n] limit the number of responses to n from a single peer [-r] discovers peers using propagate [-l] displays peer id as a hex string [-a] specify Attribute name to limit discovery to [-v] specify Attribute value to limit discovery to. wild card is allowed [-f] flush peer advertisements DESCRIPTION use "peers" to discover other peers within a peer group or at a specified peer location. Running "peers" command with no options lists only the peers already known by the peer (cached). The '-r' option is used to send a propagate request to find new peers. peers stores results in the local cache, and inserts advertisement(s) into the environment, using the default naming: peerX where X is a growing integer number. OPTIONS -p peerid discovers peers at a given peer location -r discovers peers using remote propagation -l displays peer id as a hex string -a specify Attribute name to limit discovery to -v specify Attribute value to limit discovery to -n limit the number of responses to n from a single peer -f flush peer advertisements EXAMPLE JXTA>peers -r or JXTA>peers -r -aName -vluxor* SEE ALSO whoami chpgrp join groups |
publish |
publish a jxta
advertisement JXTA>man publish NAME publish - publish a jxta advertisement SYNOPSIS publish [-d document] advertisement to publish DESCRIPTION use "publish" to publish an advertisement into cache OPTIONS -d document env advertisement to publish EXAMPLE JXTA>publish -d peer10 publish the peer advertisement peer10 |
put |
Put data into a
pipe message JXTA>man put NAME put - put data into a pipe message SYNOPSIS put <msg> <tag> <document> DESCRIPTION 'put' store a document into the body of message.JXTA messages are composed a set of tag body, each identified with an unique tag name A message tag name is supplied to specify which tag name is used to store the document. On the receiving end the document can be retrieved via the 'get' command. EXAMPLE JXTA> importfile -f /home/tra/myfile mydata JXTA> msg = mkmsg JXTA> put msg mytag mydata This example creates a document 'mydata' by importing data from the file '/home/tra/myfile'. Then, we create a pipe message 'msg' and store the document 'mydata' into the message 'msg' with the associated tag name 'mytag'. SEE ALSO mkmsg get send recv mkadv mkpipe |
rdv |
JXTA>man rdv NAME rdv - use the Walking Rendezvous Service SYNOPSIS Usage: rdv -search rdv -rpv rdv -start rdv -stop rdv -add <string> rdv -remove <string> rdv -list rdv -test <string> rdv -rdv rdv -edge rdv -connect <address> rdv -disconnect DESCRIPTION rdv is a Shell command that allows interactive operation with Rendezvous Peer walking API of the Rendezvous Service. -start: rdv command will start running in background, allowing to run the string indexing service. The background rdv program also displays responses to search queries. -stop: stops the background program. -rpv: displays the local view of the Rendezvous Peers -add <string>: insert a string in the local table of strings. -remove <string>: remove a string from the local table of strings. -list: list all the string in the local table of strings. -search <string>: walk the rendezvous peer search for the provided string. -test <string>: test if a string is in the local table of strings. -rdv forces the peer to become a rendezvous peer (for the current PeerGroup). -edge forces the peer to become an edge peer (for the current PeerGroup). -connect <address> makes the peer to try and use <address> as a rendezvous peer (for the current PeerGroup). -disconnect makes the peer disconnect from all its rendezvous peers (for the current PeerGroup). SEE ALSO |
rdvserver |
No description
available for this ShellApp JXTA>man rdvserver No help available for this ShellApp |
rdvstatus |
Display
information about rendezvous JXTA>man rdvstatus NAME rdvstatus - display information about rendezvous SYNOPSIS rdvstatus [-v] [-v] print verbose information DESCRIPTION rdvstatus displays information about the peer rendezvous.The command shows how many rendezvous peers the peer is connected to. OPTIONS -v print verbose information EXAMPLE JXTA>rdvstatus SEE ALSO whoami peers |
recv |
Receive a
message from a pipe JXTA>man recv NAME recv - receive a message from a pipe SYNOPSIS recv [-t timeout] <input pipe> DESCRIPTION 'recv' receives a message from an input pipe. The input pipe needs to have been previously created. A timeout in seconds can be given. If no timeout is given, the call will block until a message is received. A timeout of zero corresponds to a non-blocking call. EXAMPLE JXTA> pipeadv = newpipe -n mypipe JXTA> inpipe = mkpipe -i pipeadv JXTA> msg = recv inpipe JXTA> data = get msg mytag This example creates a pipe advertisement 'pipeadv' create an input pipe 'inpipe' and receive a message 'msg' The body of the message associated with the tag 'mytag' is retreived from the message via the 'get' command. SEE ALSO mkmsg put get send mkadv newpipe mkpipe |
relaystatus |
Display
information about existing relay JXTA>man relaystatus NAME relaystatus - display the of relays the peer is connected with SYNOPSIS relaystatus [-l] DESCRIPTION relaystatus displays information about the existing relay connection. Options: -l: prints result in long format List the relays the peer has a connection with. OPTIONS EXAMPLE JXTA>relaystatus This example displays all the relays the peer is connected with SEE ALSO whoami peers route rvstatus |
route |
Display
information about existing route JXTA>man route NAME route - display information about a peer route info SYNOPSIS route [info|add|delete|status|enableCM|disableCM|enableResolver|disableResolver] [PeerID] [RouteAdv] DESCRIPTION route displays and manipulates information about the peer route information. Direct routes are routes which the peer has a direct connection with. Gateway routes are routes that involved intermediary gateways (hops). OPTIONS status : Router status info local : Print local peer route info info peerID : Obtain route information about a specific destination add env1 : Add new route information specified as a route advertisement stored in the environment variable env1 delete peerId : Delete route information for that destination enableCM : enable persistent route CM cache disableCM : disable persistent route CM cache enableResolver : enable dynamic route resolution disableResolver : disable dynamic route resolution EXAMPLE JXTA>route JXTA>route del urn:jxta:uuid-59616261646162614A787461503250330F5CE9DD8DE84079AA6F8C2C0F8B16DA03 Delete route succeeded This example displays all the route information SEE ALSO whoami peers |
rsh |
No description
available for this ShellApp JXTA>man rsh NAME rsh - connects to a remote JXTA Shell SYNOPSIS rsh [-p <peeradv> [-unsecure] | -r <endpointaddress>] [-user <user name>] [-password <password>] [-f <filename>] DESCRIPTION rsh connects to a JXTA peer that runs the command rshd. The remote peer can be refered by its peer advertisement, using by default a TLS connection. The remote peer can also be refered by one of its endpoint address. In that case the given transport is used. Security: the default normal mode to use rsh is to use the option -p. Since the connection then uses the JXTA TLS Endpoint Transport, the connection is guaranteed to be secure. Otherwise, text will go clear onto the wire, which is not secure. The normal way to exit rsh is to type at the begining of a line '~.' OPTIONS -p set the peer advertismeent of the remote host -unsecure force the connection to NOT be secure -r set the endpoint address (URL) of the remote host -user set the user name to use of the remote host -user set the password to use of the remote host -f specifies a shell script to run on the remote host EXAMPLE JXTA> peers peer0: remote RSHD peer JXTA> rsh -p peer0 or JXTA> rsh -r tcp://192.168.1.10:9701 SEE ALSO rshd login |
rshd |
Remote JXTA
Shell Deamon JXTA>man rshd NAME rshd - Remote Shell Deamon SYNOPSIS rshd DESCRIPTION Runs the Remote Shell server. rshd runs in background, allowing incoming connections using the command rsh. The shell command login is used in order to authentified the user: the user and password of the peer running rshd will have to be provided by the user. SEE ALSO login rsh |
search |
Discover jxta
advertisements JXTA>man search NAME search - discover jxta advertisements SYNOPSIS search [-p peerid name attribute] [-n n] limit the number of responses to n from a single peer [-r] discovers advertisements using propagate [-a] specify Attribute name to limit search to [-v] specify Attribute value to limit search to. wild card is allowed [-f] flush jxta advertisements DESCRIPTION use "search" to search for advertisements within a peer group or at a specified peer location. Running "search" command with no options lists only the advertisements already known by the peer (cached). The '-r' option is used to send a propagate request to find new advertisements. search stores results in the local cache, and inserts advertisement(s) into the environment, using the default naming: advX where X is a growing integer number. OPTIONS -p peerid searchs for advertisements at a given peer location -r search advertisements using remote propagation -a specify Attribute name to limit search to -v specify Attribute value to limit discovery to -n limit the number of responses to n from a single peer -f flush jxta advertisements EXAMPLE JXTA>search -r search for new advertisements in the current peer group SEE ALSO whoami chpgrp join groups |
send |
Send a message
into a pipe JXTA>man send NAME send - send a message into a pipe SYNOPSIS send <output pipe> <msg> DESCRIPTION 'send' sends a message into an output pipe. The output pipe needs to have been previously created via a pipe advertisement. EXAMPLE JXTA> pipeadv = newpipe -n mypipe JXTA> outpipe = mkpipe -o pipeadv JXTA> send outpipe msg This example creates a pipe advertisement 'pipeadv', creates an output pipe 'outpipe' and sends the message 'msg' through the pipe. SEE ALSO mkmsg put get recv mkadv newpipe mkpipe |
set |
Set an
environment variable JXTA>man set NAME set - set an environment variable SYNOPSIS set <env to> <env from DESCRIPTION Assign a value to a Shell environment variable. EXAMPLE JXTA>set var1 doc This example assigns the value 'doc' to the environment variable 'var1' SEE ALSO Shell env |
setenv |
Set an
environment variable JXTA>man setenv NAME setenv - set an environment variable SYNOPSIS setenv <env to> <env from DESCRIPTION Assign a value to a Shell environment variable. EXAMPLE JXTA>setenv var1 doc This example assigns the value 'doc' to the environment variable 'var1' SEE ALSO Shell env |
sftp |
Send a file to
another peer JXTA>man sftp NAME sftp - send a file to another peer SYNOPSIS sftp -register <userName> sftp -login <userName> sftp -logout <userName> sftp -s <user> <userName> <fileName> DESCRIPTION The 'sftp command implements a secure file transfer where one peer can send a file to a second. to use 'sftp'. The user needs to register himself. This is done via the following steps: Step 1: Register via 'sftp -register <username>' command. This command creates a secure sftp advertisement for that user. This has to be done only once, the first time the user registers with sftp. The system remembers it across reboot. Step 2: Login via 'sftp -login <username>' command. This command login the user and start a listener daemon. This has to to be done everytime the peer is restarted. Step 3: User can securely send a file to another user via the command 'sftp -s <myusername> <destusername> <filename>'. This will send the file <filename> to the dest. The file is written on the sftp subdirectory of the directory where the shell is started. JXTA>sftp -s moi mike photo.gif sftp is connected to user mike Sending file photo.gif, size = 55692 bytes To stop receiving any more files the user can stop the sftp listener daemon by entering the command 'sftp -logout <username>' OPTIONS -register register a new user name -login log user and set default user -logout logout -s specify current user, and file names EXAMPLE JXTA>sftp -register me JXTA>sftp -login me JXTA>sftp -s me you /tmp/nihow.jpg This example shows how a new user 'me' can register and log into sftp, and send a file to the user 'you'. User 'you' needs to be similarly registered and logged on. The above file is written as sftp/nihow.jpg SEE ALSO |
share |
Share an
advertisement JXTA>man share NAME share - share an advertisement SYNOPSIS share <advertisement> DESCRIPTION share an advertisement document in the current peer group. The document is made visible to all the members of the peer group. Advertisements are XML documents that can represent any JXTA objects advertisement, environment variables). Documents are searched either in the local peer cache or remotely via the 'search' command. OPTIONS EXAMPLE JXTA>share mydoc This example shares the document 'mydoc' into the current peer group. SEE ALSO peers search JXTA> |
Shell |
JXTA Shell
command interpreter JXTA>man Shell NAME Shell - JXTA Shell command interpreter SYNOPSIS Shell [Shell [-f filename] [-e cmds] [-s] [-x] DESCRIPTION The JXTA Shell provides an interactive environment to the JXTA platform. The Shell provides basic commands to discover peers and peergroups, to join and resign from peergroups, to create pipes between peers, and to send pipe messages. The Shell provides environment variables that permit binding symbolic names to Jxta platform objects. Environment variables allow Shell commands to exchange data between themselves. The shell command 'env' displays all defined environment variables in the current Shell session. The Shell creates a Jxta InputPipe (stdin) for reading input from the keyboard, and a Jxta OutputPipe (stdout) to display information on the Shell console. All commands executed by the Shell have their initial 'stdin' and 'stdout' set up to the Shell's stdin and stdout pipes. The Shell also creates the environment variable 'stdgroup' that contains the current JXTA PeerGroup in which the Shell and commands are executed. A new Shell can be forked within a Shell. The 'Shell -s' command starts a new Shell with a new Shell window. The Shell can also read a command script file via the 'Shell -f myfile'. 'Shell -e cmd1;cmd2;cmd3' allows execution of multiple cmds within a single command line. A 'man' command is available to list the commands available. Type 'man <command>' to get help about a particular command. To exit the Shell, use the 'exit' command. Every Shell command is of the form <cmd>;..;<cmd>. The ';' is used as command separator. Multiple commands can be entered in one line. Pipelines can be created by combining the pipe stdout of a command into the pipe stdin of another command using the pipe '|' operator. For example the following command: JXTA> cat env1 | more Pipe the output of the command 'cat' into the stdin of the command 'more'. Arbitrary number of commands can be pipelined together within a single Shell command. Currently '|' is the only pipe operator supported. The '=' operator can be used to assign the value of a command output to an environment variable. For example : JXTA> myadv = newpipe -n mypipe This command creates a new pipe advertisement and stores it in the 'myadv' environment variable. COMMANDS The Shell provides the following built-in commands: clear Clear the shell's screen The additional commands available may be discovered by : man OPTIONS [-f <filename>] Execute the script file [-e <commands>] Execute the commands [-s] Fork a new Shell console in a new window [-x] Skip execution of .jshrc EXAMPLE JXTA> Shell -f /home/tra/batch This command executes the commands stored in the Shell script file '/home/tra/myfile' in the current Shell environment. ENVIRONMENT The Java implementation of 'Shell' uses two system properties to configure the use of graphics: SHELLNOWINDOW - if 'true' then no AWT window is created. SHELLFONTSIZE - Size in points for the font used in graphics window. The following environment variables are defined by default: consin = Default Console InputPipe consout = Default Console OutputPipe stdout = Default OutputPipe stdin = Default InputPipe SHELL = This Shell object stdgroup = Default peer group rootgroup = Default NetPeerGroup echo = if defined then echo all commands before executing them FILES $HOME/.jshrc a default startup script can be setup that is executed when the Shell is invoked SEE ALSO |
sleep |
Sleep for a
specified amount of milliseconds JXTA>man sleep NAME Sleep for a specified amount of milliseconds SYNOPSIS sleep milliseconds DESCRIPTION sleep sleeps for the specified amount of milliseconds |
socketbridge |
socketbridge:
bridges sockets to bidirectional pipes JXTA>man socketbridge NAME SYNOPSIS socketbridge -register proxyName <filename> socketbridge -register proxyName <filename> -secure socketbridge -register proxyName <filename> -propagate socketbridge -server <filename> addr port socketbridge -client <filename> addr port -peer peeradv socketbridge -stopserver proxyName socketbridge -stopclient proxyName DESCRIPTION socketbridges allows to create a bridge between a Socket or a Server Socket and JXTA pipes. This command is typically used in order to establish a TCP/IP - socket, communication over a network of JXTA peers using pipes. socketbridge associates a named JXTA advertisement. For security reasons, the advertisement is NOT published, and therefore is not searchable. The advertisement is stored onto the local filesystem. The publication of the socketbridge avdertisement is let up to the user, whom can decide to the appropriate publication mechanism. socketbridge implements a connection protocol, as as a keep-alive protocol, allowing both ends of the socketbridge to be notified of connections, disconnections and failures. Security note: establishing tunnels may compromise the security of the local network. socketbridge is provided as a tool to demonstrate bridging capiblities between JXTA and non JXTA peers. Use at your own risk. OPTIONS socketbridge -register proxyName <filename> Creates an unsecure socketbridge advertisement. proxyName is the name of the advertisment which is stored into the specified file. Unsecure, unicast pipes are used to carry data. socketbridge -register proxyName <filename> -secure Creates a secure socketbridge advertisement. proxyName is the name of the advertisment which is stored into the specified file. Secure (TLS) , unicast pipes are used to carry data. socketbridge -register proxyName <filename> -propagate Creates a propagated socketbridge advertisement. proxyName is the name of the advertisment which is stored into the specified file. Propagated pipes are used to carry data. socketbridge -server <filename> addr port Binds one end of the socketbridge specified by the advertisement contained in the specified file, to the specified ip_address:port of a reachable service. socketbridge listens to incoming requests from the pipe, and forwards it to the specified ip:port. socketbridge -client <filename> addr port -peer peeradv Binds one end of the socketbridge specified by the advertisement contained in the specified file, to the specified ip_address:port. socketbridge listens to incoming requests from the specified ip:port and forwards them to the pipe. socketbridge -stopserver proxyName stops the specified socketbridge server. socketbridge -stopclient proxyName stops the specified socketbridge client. EXAMPLE JXTA> socketpipe -register mybridge /private/mybridge.adv -secure JXTA> socketpipe -server /private/mybridge.adv www.jxta.org 80 JXTA> socketpipe -client /private/mybridge.adv localhost 8400 Establishes a secure socketbridge to the web server of www.jxta.org. A web browser accessing localhost:8400 will in fact be connected to www.jxta.org:80. Secure pipes are used to transfert data. SEE ALSO socketbridge uses the platform package net.jxta.util.socket. |
talk | Talk to another
peer JXTA>man talk NAME talk - Talk to another peer SYNOPSIS talk -register <userName> [-secure | -propagate] talk -login <userName> talk -logout <userName> talk -search talk [-u <user>] <userName> DESCRIPTION The 'talk command implements a simple instant messaging command where two users on two remote peers can exchange messages. Messages are displayed on the Shell stdout. In order to use 'talk'. The user needs to register himself. This is done via the following steps: Step 1: Register via 'talk -register <username>' command. This command creates a Talk advertisement for that user. This has to be done only once, the first time the user registers with talk. The system remembers it accross reboot. -secure can be added in order to establish a secure talk session. -propagate can be added in order to establish a chatroom style talk session. Step 2: Login via 'talk -login <username>' command. This command logs the user and starts a listener daemon. This has to to be done everytime the peer is restarted. Step 3: User can talk to another user via the command 'talk -u <myusername> <destusername>'. This command will prompt the user to enter the message he/she wants to send JXTA>talk -u moi mike # talk : Connected to user mike Type your message. To exit, type '.' at begining of line To stop receiving any more talk messages. The user can stop the talk listener daemon by entering the command 'talk -logout <username>' OPTIONS -register register a new user name. -login log user and set default user. -logout logout. -search search for talk users. -u specify current user name EXAMPLES JXTA>talk -register me JXTA>talk -login me JXTA>talk -search JXTA>talk -u me you This example shows how a new user 'me' can register and log into talk, an talk to the user 'you'. User 'you' needs to be registered and logged on. SEE ALSO xfer sftp mkpipe JXTA> |
transports | Display
information about the message transports in the current group JXTA>man transports NAME transports - display information about the messge transports in the current group SYNOPSIS transports DESCRIPTION Display information about the messge transports in the current group EXAMPLE JXTA>transports This example displays the current message transports in this group. |
uninstjar | Uninstalls
jar-files previously installed with 'instjar' JXTA>man instjar NAME instjar - installs one or more jar-files containing additional Shell commands. SYNOPSIS instjar [<jar-file> [...]] DESCRIPTION This command installs jar-files containing additional Shell commands. An arbirtary number of paths to jar-files can be supplied. If this command is invoked with no arguments it lists all installed jar-files. Use the given indices to uninstall jar-files with the 'uninstjar' command. The class-files of a command 'xxx' must be in the package 'net.jxta.impl.shell.bin.xxx' and the main-class must be named 'net.jxta.impl.shell.bin.xxx.xxx'. Accordingly the class-files must be placed in a directory 'net/jxta/impl/shell/bin/xxx/' within the jar-file, and must extend the ShellApp class. The list of installed jar-files is stored in the environment variable 'instjars'. EXAMPLE To install two jar-files 'c:/userlib/usrcmds.jar' and 'c:/userlib/toolscmds.jar: JXTA>instjar c:/userlib/usrcmds.jar c:/userlib/toolcmds.jar To list all installed jar-files with their indices: JXTA> instjar 0 c:/userlib/usrcmds.jar 1 c:/userlib/toolcmds.jar These indeces can be used to uninstall some jar-files with the 'uninstjar' command. SEE ALSO uninstjar |
version | No description
available for this ShellApp JXTA>version jxta version JXTA_2_2_00 1245121503 |
wc | Count the
number of lines, words, and chars in an object JXTA>man wc NAME wc - count the number of lines, words, and chars in an object SYNOPSIS wc [-c -l -w] [<objectName>] DESCRIPTION 'wc' counts the number of newlines, whitespace-separated words, and characters in the given shell object, or in the standard input pipe if no object is specified. It writes one line of counts to the output pipe. The counts are written in the order: lines, words, characters. By default, wc writes all three counts. Options can specify that only certain counts be written. Options do not undo others previously given, so 'wc -c -l' writes both the character count and the line count. If no object is specifed on the command line, wc will read from stdin. If stdin is the console, you may type in lines of text. Enter a '.' all by itself at the beginning of a line to finish. OPTIONS -c Write the character count. -l Write the line count. -w Write the word count. EXAMPLES JXTA>wc myfile 18 52 675 JXTA>cat myfile | wc -w 52 The first example displays the number of lines, words, and chars in myfile. The second displays only the number of lines. |
who | Display
credential information JXTA>man who NAME who - display credential identity information SYNOPSIS who [-p] DESCRIPTION who displays the set of credentials associated with this peer for the current peer group. OPTIONS [-p] pretty print credential information EXAMPLE JXTA>who -p This example displays a pretty printed credential SEE ALSO join, leave, set, info |
whoami | Display
information about a peer or peergroup JXTA>man whoami NAME whoami - display information about a peer or peergroup SYNOPSIS whoami [-l] [-g] DESCRIPTION whoami displays information about a peer or a peergroup. With no option, whoami returns information about the local peer. The '-g' option returns information about the current peer group joined. By default the Shell is brought up in the 'NetPeerGroup' group. Peers do not have name. A user can assign a symbolic name to a peer via the 'setinfo' command. There is no guarantee that the name is unique. Only the peerId and the peerGroup ID are guaranteed to be unique. OPTIONS [-g] return info about the current peergroup [-l] return a long version of the advertisement EXAMPLE JXTA>whoami -l This example displays a long version of the peer group information SEE ALSO setinfo peers |
xfer | Send a file to
another peer JXTA>man xfer NAME xfer - send a file to another peer SYNOPSIS xfer ( ("register" [-s|-p] userName) | ( ("login" [-e] userName) | ( ("logout" userName) | ( ("send" [-b blockSize] [-d destAddr] [-s userName] [-a] destUserName filename) | ( ("search") ) DESCRIPTION The 'xfer' command implements a file transfer between peers. The file transfer can be completed using either pipes or via direct endpoint communication. OPTIONS register Register a new user name [-s] Use a secure pipe. [-p] Use a propagate pipe. username The name of the new user. login Login user [-e] Create an Endpoint Listener rather than an Input Pipe Listener. username The name of the user. logout Logout user username The name of the user. send Send a file [-b blockSize] Chunk size in bytes to break file into. [-d destAddr] Destination endpoint. [[-p peerID]] Destination peer id for pipe. Can be repeated. [-s userName] Source user name. Receiver will see this user as the sender. [-a] Asynchronously send file. Used with Endpoint Listener mode. destUserName The name of the intended recipient. filename The path of a local file to be sent. get Get a file [-b blockSize] Chunk size in bytes to break file into. [-s userName] Source user name. Receiver will see this user as the sender. destUserName The name of the intended recipient. filename The path of a local file to be sent. search Search for users. EXAMPLE JXTA>xfer register me JXTA>xfer login me JXTA>xfer send -s me you /tmp/nihow.jpg This example shows how a new user 'me' can register and log into xfer, and send a file to the user 'you'. User 'you' needs to be similarly registered and logged on. The above file is written as /xfer/nihow.jpg SEE ALSO talk, sftp |
Date
: |
jeu avr 8 15:16:16 CEST 2004 |
Auteur
: |
ERNEST Duarte |
Auteur
: |
KONAN |