Changeset 4309 for trunk/doc/src/docbook/userdoc/jobs.xml
- Timestamp:
- May 22, 2008, 3:51:05 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/userdoc/jobs.xml
r4307 r4309 30 30 <?dbhtml dir="jobs"?> 31 31 <title>Jobs</title> 32 <param> 33 Job is a configured task performed by a plugin. Creating/configuring a job is done from a 34 context that is supported by the plugin you want to use. Some jobs can be configured to 35 execute immediately (for a few it is not even an option), but normally the jobs are placed 36 in a queue after they have been configured. The order, in which the queued jobs are 37 executed, is decided by the priority between the jobs and when there is a slot available to 38 execute the job on. The priority can not be changed by a user, this is something that is 39 specified by the plugin developer. 40 </param> 32 <para>Job is a configured task performed by a plugin.</para> 33 <para> 34 Creating/configuring a job is made from a context, which is supported by the plugin you want 35 to use. If no particularly context is needed, the job configuration is started from the 36 plugin's single item view. 37 </para> 38 <para> 39 Some jobs can be configured to execute immediately (for a few plugins it is mandatory that 40 the job runs immediately), but normally jobs are placed in the job queue after they have 41 been configured. The jobs will then be picked out for execution depending on their priority 42 and estimated execution time. 43 </para> 44 41 45 42 46 <sect1 id="jobs.properties"> 43 <title> View a job</title>44 Go to47 <title>Properties</title> 48 Click on 45 49 <menuchoice> 46 50 <guimenu>View</guimenu> … … 49 53 to list your jobs. 50 54 <para> 51 When viewing details of a single job, it is displayed in pop-up window. This window52 opens either if you click on a job's name from the list page of jobs or when a job53 configuration is finished. The window contains two tabs, one tab with information about54 the job and another with theparameters for the plugin used in the job.55 Details of a single job is displayed in a pop-up window. This window opens either if you 56 click on a job's name from the list page of jobs or when a job configuration is 57 finished. The window contain two tabs, one with information about the job and another 58 with the plugin-parameters for the plugin used in the job. 55 59 </para> 56 60 <helptext external_id="job.view.parameters" title="Job parameters"> 57 61 <para> 58 The values listed on the parameter-tab are used when running the job. Exactly which 59 parameters to find here, is decided by the plugin and what inputs it needs from the 60 user. 62 The values listed on the plugin-parameter-tab are depending on what inputs the 63 choosen plugin needs from the user. 61 64 </para> 62 65 </helptext> 63 66 <helptext external_id="job.view.properties" title="Job properties"> 64 67 <para> 65 Allparameters are set either when configuring the job or by the system. No68 Job-parameters are set either when configuring the job or by the system. No 66 69 parameters can be edit after a job is created. 67 70 <variablelist> … … 84 87 <listitem> 85 88 <para> 86 Description of the job. Like the name-property it can be set when 87 configuring a job. 89 A description of the job. Like the name-property it can be set in 90 the job configuration. 91 </para> 92 </listitem> 93 </varlistentry> 94 <varlistentry> 95 <term> 96 <guilabel>Type</guilabel> 97 </term> 98 <listitem> 99 <para> 100 The type of job, which is depending on the plugin that is used. It 101 can be one of these five: 102 <itemizedlist> 103 <listitem>Export</listitem> 104 <listitem>Import</listitem> 105 <listitem>Analysis</listitem> 106 <listitem>Intensity</listitem> 107 <listitem>Other</listitem> 108 </itemizedlist> 88 109 </para> 89 110 </listitem> … … 94 115 </term> 95 116 <listitem> 96 <para> 97 This is what priority the job should have in the job queue. It is 98 defined by the used plugin and can not be changed by the user. The 99 value is between 1 and 10, where 1 is the highest priority. 100 </para> 117 <para>Priority the job has in the job queue.</para> 101 118 </listitem> 102 119 </varlistentry> … … 107 124 <listitem> 108 125 <para> 109 This shows the status of the job, sometimes including a message from 110 the plugin. Status is one of the following: 126 Shows the status of the job. A job can have one of following status. 111 127 <itemizedlist> 112 128 <listitem> 113 129 <para> 114 130 <emphasis>Not configured</emphasis> 115 -The plugin has not been configured and is not placed in116 the job queue.131 -The plugin has not been configured properly and is not 132 placed in the job queue. 117 133 </para> 118 134 </listitem> … … 120 136 <para> 121 137 <emphasis>Waiting</emphasis> 122 - Waiting in the job queue138 -Job is waiting in the job queue. 123 139 </para> 124 140 </listitem> … … 160 176 <varlistentry> 161 177 <term> 178 <guilabel>Status message</guilabel> 179 </term> 180 <listitem> 181 <para> 182 A message, given by the plugin, with more information about the 183 status. 184 </para> 185 </listitem> 186 </varlistentry> 187 <varlistentry> 188 <term> 162 189 <guilabel>Percent complete</guilabel> 163 190 </term> 164 191 <listitem> 165 192 <para> 166 This shows the progress of the job. How detailed this is depends on167 how often theplugin reports it's progress.193 Progress of the job. How detailed this is depends on how often the 194 plugin reports it's progress. 168 195 </para> 169 196 </listitem> … … 174 201 </term> 175 202 <listitem> 176 <para>Time and date when the job was created.</para> 203 <para> 204 Date and time when the job was created and registerd in the database. 205 </para> 177 206 </listitem> 178 207 </varlistentry> … … 182 211 </term> 183 212 <listitem> 184 <para>Time when the job left the job queue and started to run.</para> 213 <para> 214 Date and time when execution of the job started. 215 </para> 185 216 </listitem> 186 217 </varlistentry> … … 191 222 <listitem> 192 223 <para> 193 Time when the job ended to run. Either cause of it was finished or194 an error.224 Date and time when the job stopped running. Either cause of it was 225 finished, aborted or interrupted by an error. 195 226 </para> 196 227 </listitem> … … 201 232 </term> 202 233 <listitem> 203 <para>Time between when the job was started and ended.</para>234 <para>Time the job has been running.</para> 204 235 </listitem> 205 236 </varlistentry> … … 214 245 <varlistentry> 215 246 <term> 216 <guilabel>User </guilabel>247 <guilabel>User/Owner</guilabel> 217 248 </term> 218 249 <listitem> … … 233 264 </term> 234 265 <listitem> 235 <para>The plugin to performthe job.</para>266 <para>The plugin to use in the job.</para> 236 267 </listitem> 237 268 </varlistentry>
Note: See TracChangeset
for help on using the changeset viewer.