Using Rover Clients

There are two ways to start executing a Rover client: the Rover script and the Rover Access Manager binary.

rover file

The usual way to start the Rover Access Manager and the Rover chooser application client is use the rover script in the top level client directory (ClientDir/WWW). The script is a wrapper for the WWW binary that first determines the architecture of the client machine and then loads the architecture-appropriate binary to start the Rover chooser client application.

The script has one optional argument, the name of a file in which to write level 1 debugging output.

www options url

The actual binary for the Rover Client Access Manager is (mis)named www. The naming anomaly is due to the derivation of the Access Manager from CERN's LineMode WWW browser. The available command line arguments and options are:

www   [-C #] [-F dir] [-P #] [-S #] [-Z] [-c #] [-b #] [-f]
      [-l] [-n] [-p #] [-?] [-help] [-d #] [-t name] [-v trace]
      [-H #] [-N name] [-Q #] [-s #] [-m #] [-q #] [-R string]
      [-U url] [<url>] [-- [args ...]]

 [url]                Specify the URL of the initially loaded client application.
 [-- [args ...]]      Specify arguments for the client application.

 [-C 0/1]             Disable/enable automatic checking of network status.
 [-F dir]             Specify the Access Manager's logging directory.
 [-P prefetch]        Specify the HTTP prefetch depth.
 [-S 0/1]             Disable/enable the use of SMTP instead of TCP.
 [-Z]                 Reset all session message identifiers.
 [-c level]           Specify the zlib compression level.
 [-b 0/1]             Disable/enable batching of QRPCs.
 [-f]                 Enable synchronous flushing of QRPC log.
 [-l limit]           Specify the maximum in-core cache size.
 [-n]                 Disable logging of QRPCs to stable storage.
 [-p port]            Specify the Access Manager's HTTP port.

 [-?]                 Show this information.
 [-help]              Show this information.
 [-d level]           Specify the debugging level.
 [-t name]            Specify the trace file for HT events.
 [-v trace]           Enable tracing of HT events [disabled].

QRPC and HTTP timing tests:
 [-H count]           Specify the number of HTTP tests to be run.
 [-N name]            Specify the name used for timing tests.
 [-Q size]            Specify the size of each QRPC.
 [-s secs]            Specify delay (in seconds) after issuing each QRPC.
 [-m 0/1]             Disable/enable multiple outstanding QRPC requests.
 [-q count]           Specify the number of QRPCs to issue.
 [-R string]          Reset string to send to the server before running tests.
 [-U url]             URL to use for HTTP tests.
 [-r]                 Measure time to prepare QRPCs for transmission.
 [-e]                 Measure time to finish processing QRPCs.

Last updated by $Author: adj $ on $Date: 1997/12/02 19:44:13 $.
Copyright © 1995-1998 Anthony D. Joseph and Massachusetts Institute of Technology