isistest(1) ISIS Test

DESCRIPTION

The isistest command is for managing information stored in the distributed P2P Grid information cloud of ISIS services.

SYNOPSIS

isistest [options]

OPTIONS

-b, --bootstrap=url
the URL of the Bootstrap ISIS
-i, --isis=url
the URL of the ISIS to connect directly
-n, --neighbors
get neighbors list from the BootstrapISIS or directly from the ISIS defined
-m, --method=method_name
the method to use on the ISIS (method_name can be 'Query', 'Register', or 'RemoveRegistration')
-z, --conffile=filename
configuration file (default ~/.arc/client.conf)
-d, --debug=debuglevel
FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG
-?, --help
print help

USAGE

isistest -m Query query_string

isistest -m Register service_id,endpoint_reference
[,type[,expiration_time]] [service_id,endpoint_reference[,type [,expiration_time]] [...]]"

isistest -m RemoveRegistration service_id
[service_id [...]]"

EXTENDED DESCRIPTION

The test ISIS client is for the following operations:
Query
for querying remote ISIS with an attribute: guery_string
Register
for sending test Register messages with one or more set of different number of arguments.
  • A ServiceID and an Endpoint reference.
  • A ServiceID, an Endpoint reference and a Service type.
  • A ServiceID, an Endpoint reference, a Service type and an Expiration period.

RemoveRegistration
for sending test RemoveRegistration messages. The arguments are a list of ServiceIDs to be removed.
It is also possible to define the BootstrapISIS with the -b or --bootstrap command line option. The isistest command gets the list of ISISes from the BootstrapISIS (with the GetISISList operation), then chooses a random ISIS from that list.
It's also possible to define the isis url directly with the -i or --isis option. If there is such an option defined the GetISISList operation will be skipped even if there is also a BootstrapISIS defined. (The GetISISList operation will be used in every other cases impicitly.)
If there is not a bootstrap either a direct url of an isis given then the first isis url stored in the user configuration will be used directly.
If -n or --neighbors options are used without any parameters, then the neighbors of the ISIS or the BootstrapISIS will also be printed.

FILES

~/.arc/client.conf
Some options can be given default values by specifying them in the ARC client configuration file. By using the -z or --conffile option a different configuration file can be used than the default.

ENVIRONMENT VARIABLES

X509_USER_PROXY
The location of the user's grid proxy file. It should be set only if the proxy is in a non-standard location.

ARC_LOCATION
The location where ARC is installed can be specified by this variable. If not specified the install location will be determined from the path to the command being executed, and if this fails a WARNING will be given stating the location which will be used.

ARC_PLUGIN_PATH
The location of ARC plugins can be specified by this variable. Multiple locations can be specified by separating them by : (; in Windows). The default location is $ARC_LOCATION/lib/arc (\ in Windows).

EXAMPLES

isistest -m Register ServiceID1,EPR1
isistest -m Register ServiceID1,EPR1,org.nordugrid.tests.echo,PT1M
isistest -m Query "/*"
isistest -m Query /RegEntry/MetaSrcAdv/ServiceID[text()='ServiceID1']
isistest -m RemoveRegistration ServiceID1
isistest -b https://your.domain.com/infosys -m
RemoveRegistration ServiceID1"
isistest -i https://your.domain.com/infosys -m Query /RegEntry

COPYRIGHT

APACHE LICENSE Version 2.0

AUTHOR

Ivan Marton<[email protected]>