[[PageOutline]]
= Remote job submission =

"Remote job submissions" means that jobs are submitted
by scripts or programs running on hosts other than the BOINC server.

BOINC doesn't include a generic remote job submission system,
but it provides a number of components that can be used to build such systems.
We'll list some example systems, then describe the components.

== Example: Science portal ==

Users submit jobs using forms on a web site other than the project web site:

[[Image(submit.png)]]

The scripts implementing these forms would use
[RemoteJobs Web RPCs] to create batches and jobs.

Input files can be handled in any of several ways:

 * Managing them using [RemoteInputFiles#Content-basedfilemanagement Web RPCs].
 * Using the [RemoteInputFiles#Per-userfilesandbox user file sandbox] mechanism.
 * Serving them from a remote server.

== Example: Condor/BOINC bridge ==

[[Image(condor.png)]]

In such systems, users submit jobs to a Condor system
using any a command-line or GUI-based interface.
The Condor system may, depending on load conditions, route the job to a BOINC project.
This system uses web RPCs for all functions.

== Components supplied by BOINC ==

=== Web RPCs for input file management ===

BOINC provides [RemoteInputFiles#Content-basedfilemanagement Web RPCs for remotely managing input files],
and a C++ binding of this API.

=== Web RPCs for job submission ===

BOINC provides [RemoteJobs Web RPCs for creating and managing jobs].

=== Per-user file sandbox ===

BOINC provides [RemoteInputFiles#Per-userfilesandbox a web-based system allowing users to remotely manage input files].