Documentations
This web site is the Web visible part of an XtremWeb installation.
This page is not intended to explain and detail the XtremWeb platform, but to present how to use this current Global Computing platform installation.
For further informations, please refer to the XtremWeb Web site.
Table of contents
Introduction
Registering
Logging in and out
Downloads
<$HOME/.xtremweb/>
and named "xwrc"
.<$HOME/.xtremweb/xwrc>
.
Downloading the worker
Up : Downloads | Previous : Downloading the worker | Table of contents | Next : Downloading the client configuration file |
Downloading the client
Downloading the client configuration file
Using the client
Providing common parameters to the client
$HOME/.xtremweb/xwrc
.
If such a file exists, this --xwconfig option is not necessary.
xwclient --xwconfig <myConfigFile>
Retrieving installed applications
--xwapps
to list installed applications on server side.
xwclient --xwapps
xwclient --xwconfig <configFile> --xwapps
xwapps
script :xwapps
encapsulates the needed arguments for you.
xwapps
xwapps --xwconfig <configFile>
You can see the installed application on the submission page. To list installed applications, you must log in first.
Retrieving workers list
--xwworkers
to retrieve known workers.
xwclient --xwworkers
xwclient --xwconfig <configFile> --xwworkers
xwworkers
script :xwworkers
encapsulates the needed arguments for you.
xwworkers
xwworkers --xwconfig <configFile>
You can retrieve the known workers on the workers stats page.
Submitting jobs
Job submission can only refer to installed applications (i.e. you can only run a job for applications that are already installed on server).
The client expects the parameters--xwsubmit appName
to submit a new job for the installed application which is registered on server side with its name as appName.
Three kinds of information can be provided to jobs (let suppose the application "ls"is installed on server side) :
The server keeps jobs until the user explicitly remove them. It is then the user responsability to ensure its jobs don't fill full the server. |
# | information types | using a shell | purpose |
a | arguments |
ls -l
|
command line arguments interpreted by the applications |
b | standard input |
ls < txtFile
|
standard input replaces the keyboard and is interpreted by the application |
c | environment |
( cd aDirectory && ls )
|
the environment is the directory structure from which the application is run |
d | all together |
( cd aDirectory && ls -l < txtFile )
|
|
information types | using the XtremWeb client | purpose | |
a | arguments |
xwclient --xwsubmit ls -l
|
command line arguments interpreted by the applications |
b | standard input |
xwclient --xwsubmit ls < txtFile
|
standard input replaces the keyboard and is interpreted by the application |
c | environment |
xwclient --xwsubmit ls --xwenv aDirectory
|
the environment is the directory structure from which the application is run |
d | all together |
xwclient --xwsubmit ls -l --xwenv aDirectory < txtFile
|
xwsubmit
script :xwsubmit
encapsulates the needed arguments for you.
xwsubmit etc.
xwsubmit --xwconfig <configFile> etc.
(right click to save as this file)
A dedicated page helps to submit job.
You first see the list of installed application in this server among which you have to choose the one you want to execute.
Accordingly to your needs, you have to fill the form shown in the next page ; please, read the provided examples carefully.
Click theSubmit
button to finally submit your job. To submit jobs, you must log in first.
Retrieving jobs status
The XtremWeb platform gives every object an unique identifier (Examples :UID
).
Every submitted job has then anUID
which is expected for any job manipulation.
The client expects the parameters--xwstatus [UID UID ...]
to retrieve user's jobs status
ProvidedUIDs
determine the jobs to retrieve status for.
Requesting status with noUID
retrieve all user's jobs status.
xwclient --xwstatus
xwclient --xwconfig <configFile> --xwstatus
xwstatus
script :xwstatus
encapsulates the needed arguments for you.
xwstatus
xwstatus --xwconfig <configFile>
A dedicated page helps to retrieve job status.
To retrieve your jobs status , you must log in first.
Retrieving jobs results
UID
).
UID
which is expected for any job manipulation.
--xwresult [UID UID ...]
to retrieve
user's jobs results.
Provided UIDs determine the jobs to retrieve results for.
Requesting results with no UID retrieve all user's jobs results.
|
xwclient --xwresult
xwclient --xwconfig <configFile> --xwresult
xwresult
script :xwresult
encapsulates the needed arguments for you.
xwresult
xwresult --xwconfig <configFile>
A dedicated page helps to retrieve job results.
To retrieve your jobs results , you must log in first.
Cancelling jobs
UID
).
UID
which is expected for any job manipulation.
--xwrm [UID UID ...]
to delete
user's jobs from the platform.
Provided UIDs determine the jobs to delete.
Requesting to delete jobs with no UID delete all user's jobs.
|
xwclient --xwrm
xwclient --xwconfig <configFile> --xwrm
xwrm
script :xwrm
encapsulates the needed arguments for you.
xwrm
xwrm --xwconfig <configFile>
A dedicated page helps to cancel jobs.
To cancel your jobs , you must log in first.