User Tools

Site Tools







  • Basic components
  • Application support
  • Additional components
    • manual:restif

      REST interface for the 3G Bridge

      This manual describes the use and configuration of the 3G Bridge REST interface.

      User Guide

      The REST interface is an alternative to the SOAP based interface, with similar functionalities. The only limitation is that local files cannot be specified as input files when submitting a job; only remote file specifications are possible. Aside from this, the REST interface is a superset of the SOAP interface.

      In this manual, we assume that the project URL is, and the REST interface is deployed in download/wss/. That is, the base URL of the REST interface is

      General options

      A requested entity or collection will respond with a table (list of associative arrays). This response will be rendered according to the format argument, which can be plain, html or json. The hdr argument enables (1) or disables (0) the rendering of a header if applicable. If the Content-Type of the request is 'application/json' , the response will be in JSON format. Otherwise, the default response format is plain.

      • plain: The response will be rendered as plain text. Records are separated with '\n', attributes are separated with a single space. Separators can be overridden with the sep and rsep (record sepatator) arguments. A header is rendered if requested (hdr=1).
      • html: The response is rendered as a HTML table. A header is rendered by default.
      • json: The response is rendered as a JSON string.

      3G Bridge 1.9
      3G Bridge 1.9
      [{"version":"3G Bridge 1.9"}]

      For plain format, the field separator can be overridden with the sep argument. The record separator can be overridden with rsep.|
      093fd32b-4604-4c06-9ba9-d3aae7a6b80d|Cloud|cloud|CANCEL||--image=ami-00000021|||2012-09-11 11:20:06|

      For most entities (not collections), specific attributes can be selected in the URL:
      93fd32b-4604-4c06-9ba9-d3aae7a6b80d CANCEL 2012-09-11 11:20:06


      Most entities only support the GET verb. If not stated otherwise, the following output examples are the results of GET requests on the specified entities.

      Querying the version of the Bridge
      3G Bridge 1.9

      SOAP equivalent:

      wsclient -m version -e

      Querying queues

      Querying available queues
      Cloud audiveris 1
      edgidemo audiveris 1 
      edgidemo bwa-boinc 1
      NULL dsp
      MetaJob dsp

      SOAP equivalent: —

      Querying available grids

      SOAP equivalent: —

      Querying available algorithms for a grid
      1. All attributes:
      2. Only algorithm names:
      edgidemo audiveris 1 
      edgidemo bbgc 1 
      edgidemo Blender 1 
      edgidemo bwa-boinc 1

      SOAP equivalent for 2nd case:

      wsclient -m gridalgs -e -g edgidemo

      Managing jobs

      Querying all jobs
      id grid alg status gridid args griddata tag creation_time metajobid
      093fd32b-4604-4c06-9ba9-d3aae7a6b80d Cloud cloud CANCEL  --image=ami-00000021   2012-09-11 11:20:06 
      0bba95f9-38ea-4cf9-8125-6bc3e93af154 Cloud cloud CANCEL  --image=ami-00000021   2012-09-13 10:40:07

      SOAP equivalent: —

      Querying a single job
      093fd32b-4604-4c06-9ba9-d3aae7a6b80d Cloud cloud CANCEL  --image=ami-00000021   2012-09-11 11:20:06

      Any subset of the attributes can be selected. Consider the following SOAP commands:

      wsclient -m status -e -j 093fd32b-4604-4c06-9ba9-d3aae7a6b80d

      REST equivalent:
      093fd32b-4604-4c06-9ba9-d3aae7a6b80d CANCEL
      wsclient -m griddata -e -j 093fd32b-4604-4c06-9ba9-d3aae7a6b80d

      REST equivalent:
      093fd32b-4604-4c06-9ba9-d3aae7a6b80d d2048dd6-464e-47c9-a4d0-373a9de25bdb_e933a6f8-7365-4b58-846d-a38be7d4ba24_76a26b38-88fd-4ba3-912b-2b1e30ed74d6
      Querying finished jobs
      093fd32b-4604-4c06-9ba9-d3aae7a6b80d FINISHED
      0bba95f9-38ea-4cf9-8125-6bc3e93af154 ERROR
      0f25e8cb-45f6-4f7f-83b4-4525dc245b11 FINISHED

      SOAP equivalent:

      wsclient -m finished -e
      Cancelling a job or deleting a finished job

      To cancel a job, send a request to its URL with the DELETE verb.

      curl -X DELETE

      SOAP equivalent:

      wsclient -m delete -e -j 093fd32b-4604-4c06-9ba9-d3aae7a6b80d
      Submitting a job

      A job can be submitted to the Bridge by POSTing a job object to the jobs entity. Currently, there are two ways to do this; either by posting form-data (Content-Type: application/x-www-form-urlencoded) or by posting a JSON object (application/json). The following examples show how this can be achieved using curl.

      In both cases, by default, after a successful submission, the Bridge will respond with a redirect header to the newly created jobs (Location:<new_uuid>). The -L switch tells curl to follow this redirection.

      Another possibility is to specify 'redir=0' in the URL (…/wss/jobs?redir=0); in this case, no redirection occurs, only the unique id of the new job is printed. This is the same behaviour as that of the SOAP interface.

      To submit a job, the same information has to be supplied as in case of the SOAP interface. Notice that—unlike the SOAP interface—the URL, MD5 and size parts of a specification are specified separately, not in a single string joined with '=' .

      Submitting using form data
      Submitting a job using CURL
      curl \
          -d name=dsp \
          -d grid=NULL \
          -d args='-dpf=docking.dpf' \
          -d tag='Test job' \
          -d input[docking.dpf][url]= \
          -d input[docking.dpf][md5]=a7bac5a941a85660cd87bf83f93b852a \
          -d input[docking.dpf][size]=2933 \
          -d input[][url]= \
          -d input[][md5]=cbb8c0ada8e197d6db707e6ce4f03ca6 \
          -d input[][size]=3270896 \
          -d output[0]=log.dlg \
      id grid alg status gridid args griddata tag creation_time metajobid userid error_info
      022a9b75-8a08-4f5d-8188-c8687659e60d NULL dsp INIT  -dpf=docking.dpf  Test job 2013-01-22 13:30:32   


      Submitting a job using CURL
      curl \
          # [ same as above ] \

      Submitting using JSON

      This is an example job description in JSON:

              "name": "dsp",
              "grid": "NULL",
              "args": "-dpf=docking.dpf",
              "tag": "Test job",
              "input": {
                  "docking.dpf": {
                      "url": "",
                      "md5": "a7bac5a941a85660cd87bf83f93b852a",
                      "size": 2933
                  "": {
                      "url": "",
                      "md5": "cbb8c0ada8e197d6db707e6ce4f03ca6",
                      "size": 3270896
              "output": [

      This example job can be submitted with the following command.

      Submitting a JSON job
      curl \
          --header 'Content-Type: application/json' \
          --data @example-job.json \

      If plain text output is required
      curl \
          --header 'Content-Type: application/json' \
          --data @example-job.json \


      Admin Guide

      Follow these steps to deploy the REST interface for the Bridge:

      1. Create a directory that will be published by the project web server. For example, if you create a directory named wss in project/download, the directory will be available through http://<projecturl>/download/wss.
      2. Setup the project site to allow RewriteEngine and security overrides in .htaccess files.
      3. Allow write access to the Bridge output directory.
      4. Setup security.
      5. Copy the php scripts that constitute the interface to the directory just created.
      6. Configure the interface by setting the necessary values in 3gb.php.
      Create the directory
      mkdir $HOME/project/download/wss
      Setup Apache

      Setup Apache and the project site to support the Rewrite module and security overrides.

      Enabling the Rewrite engine as ''root''
      sudo a2enmod rewrite

      In the project site configuration ([project_home]/project/[project_name].httpd.conf), FileInfo and Limit has to be added to AllowOverride for directory …/user. This enables the use of RewriteEngine and security overrides in .htaccess.

      As output directories will be created upon submission, PHP must be allowed to access the 3G Bridge output directory (as configured in 3gbridge.conf/[wssubmitter]/output-dir). To do so, add this directory, delimited with a colon, to the open_basedir PHP admin value.

      <Directory "[project_home]/project/html/user">
          AllowOverride AuthConfig FileInfo Limit
          php_admin_value "open_basedir"    "...:[project_home]/3g-bridge/output"

      Restart Apache for these changes to take effect:

      sudo service apache2 restart
      Allow write access to the Bridge output directory

      Assuming the Bridge output directory is [project_home]/master/3g-bridge/output. The actual value can be found in the 3G Bridge configuration file, in the [wssubmitter] section.

      Make sure that the Apache process user (usually www-data) is added to the project user's default group

      getent group $USER

      If www-data is not listed next to the project user default group, you must correct this

      manual/restif.txt · Last modified: 2013/05/13 12:16 (external edit)