Difference between revisions of "OCR Service"

From Gcube Wiki
Jump to: navigation, search
(Created page with 'to be completed')
 
Line 1: Line 1:
to be completed
+
This is a stateful Web Service that serves as a wrapper to Optical Character Recognition application developed by the INSPIRE team.
 +
 
 +
 
 +
'''Notes to administrator:
 +
'''
 +
 
 +
In order for the OCR service to work in a scope, a Scientifil Linux 5 execution node with ocropus software installed must exist in that scope. An SL5 node that can execute OCR must:
 +
a) be a SL5 node and declare it in $GLOBUS_LOCATION/conf/GHNLabels.xml file with the following
 +
xml elements:
 +
        <Variable>
 +
        <Key>other.GlueHostOperatingSystemName</Key>
 +
        <Value>ScientificSL</Value>
 +
        </Variable>
 +
        <Variable>
 +
        <Key>other.GlueHostOperatingSystemRelease</Key>
 +
        <Value>5.0</Value>
 +
        </Variable>
 +
        <Variable>
 +
     
 +
 
 +
b) have ocropus-0.3.1-i386 directory under $GLOBUS_LOCATION and declare it in $GLOBUS_LOCATION/conf/GHNLabels.xml file with the following
 +
xml element:
 +
 
 +
        <Variable>
 +
        <Key>software.ocropus</Key>
 +
        <Value>true</Value>
 +
        </Variable>
 +
     
 +
In addition, it is expected that the following ocrjob.sh script exists under $GLOBUS_LOCATION directory
 +
of the node on which OCRService service is running, so that it can be sent to the execution node.
 +
 
 +
 
 +
 
 +
'''Notes to developer:
 +
'''
 +
 
 +
When OCR service factory receives a call from a user, it tries to find a
 +
Workflow Engine instance in that scope which will use to submit a new job using JDL adaptor.
 +
In case of success, it will create a Web Service resource for that job that will contain
 +
information of that job such as job name,execution id,workflow engine endpoint etc.
 +
A background thread operates periodically and is in charge of collecting all WS-resources,
 +
polling the workflow engine for the jobs that are still running and updating the corresponding WS-resources.
 +
 
 +
 
 +
 
 +
'''Notes to user:
 +
'''

Revision as of 14:17, 10 June 2011

This is a stateful Web Service that serves as a wrapper to Optical Character Recognition application developed by the INSPIRE team.


Notes to administrator:

In order for the OCR service to work in a scope, a Scientifil Linux 5 execution node with ocropus software installed must exist in that scope. An SL5 node that can execute OCR must: a) be a SL5 node and declare it in $GLOBUS_LOCATION/conf/GHNLabels.xml file with the following xml elements:

       <Variable>
       <Key>other.GlueHostOperatingSystemName</Key>
       <Value>ScientificSL</Value>
       </Variable>
       <Variable>
       <Key>other.GlueHostOperatingSystemRelease</Key>
       <Value>5.0</Value>
       </Variable>
       <Variable>
      

b) have ocropus-0.3.1-i386 directory under $GLOBUS_LOCATION and declare it in $GLOBUS_LOCATION/conf/GHNLabels.xml file with the following xml element:

       <Variable>
       <Key>software.ocropus</Key>
       <Value>true</Value>
       </Variable>
      

In addition, it is expected that the following ocrjob.sh script exists under $GLOBUS_LOCATION directory of the node on which OCRService service is running, so that it can be sent to the execution node.


Notes to developer:

When OCR service factory receives a call from a user, it tries to find a Workflow Engine instance in that scope which will use to submit a new job using JDL adaptor. In case of success, it will create a Web Service resource for that job that will contain information of that job such as job name,execution id,workflow engine endpoint etc. A background thread operates periodically and is in charge of collecting all WS-resources, polling the workflow engine for the jobs that are still running and updating the corresponding WS-resources.


Notes to user: