Changeset 3345 for trunk/doc/src/docbook/admindoc/plugin_installation.xml
- Timestamp:
- May 16, 2007, 1:17:55 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/admindoc/plugin_installation.xml
r3339 r3345 44 44 <para> 45 45 The first step is to install the plug-in on the web server. To make 46 these instructions easier to read we assume the theplug-in comes as46 these instructions easier to read we assume the plug-in comes as 47 47 a single JAR file and that it doesn't depend on any other JAR files. 48 48 </para> … … 139 139 The maximum amount of memory the plug-in may use. This setting 140 140 only applies when the plug-in is executed with a job agent. If 141 the in ernal job queue is used this setting has no effect and the141 the internal job queue is used this setting has no effect and the 142 142 plug-in may use as much memory as it likes. 143 143 <nohelp>See <xref linkend="plugins.jobagents" /> later … … 155 155 When this becomes implemented in the future a 156 156 <guilabel>no</guilabel> value will apply security restrictions 157 to plug-ins similiar to those a web browser put on applets. 158 For example, the plug-in is not allowed to access the file 159 system, open ports, shut down the server, and a lot of 160 other nasty things. 161 </para> 162 </listitem> 163 </varlistentry> 164 <varlistentry> 165 <term><guilabel>Trusted</guilabel></term> 166 <listitem> 167 <para> 168 If the plug-in is trusted enough to be executed in an 169 unprotected environment. This setting has currently no 170 effect since BASE can't run in a protected environment. 171 When this becomes implemented in the future a 172 <guilabel>no</guilabel> value will apply security restrictions 173 to plug-ins similiar to those a web browser put on applets. 157 to plug-ins similar to those a web browser put on applets. 174 158 For example, the plug-in is not allowed to access the file 175 159 system, open ports, shut down the server, and a lot of … … 261 245 <para> 262 246 Upload the <filename>*.base</filename> file for the BASE 1 plug-in 263 to BASE 2. If you can't the file, you can let BASE 1 create one for you.247 to BASE 2. If you can't find the file, you can let BASE 1 create one for you. 264 248 In your BASE 1 installation go to 265 249 <menuchoice> … … 294 278 to have an experiment with some data. Go to the single-item 295 279 view for a bioassayset and click on the <guibutton>Run analysis</guibutton> 296 button. Select the <emphasis>Base1PluginExecut or</emphasis>280 button. Select the <emphasis>Base1PluginExecuter</emphasis> 297 281 plug-in. The list of configurations should include the newly 298 282 installed plug-in. Select it and click on <guibutton>Next</guibutton>. … … 303 287 <para> 304 288 This will enter regular plug-in execution wizard and you 305 will have to enter para ters needed by the plug-in.289 will have to enter parameters needed by the plug-in. 306 290 </para> 307 291 </listitem> … … 331 315 <para> 332 316 To limit this problem it is possible to tune the permissions for 333 a theplug-in so that it only has permission to do things that it317 a plug-in so that it only has permission to do things that it 334 318 is supposed to do. For example, a plug-in that import reporters 335 may only need permission to update and create new reporter and319 may only need permission to update and create new reporters and 336 320 nothing else. 337 321 </para> … … 447 431 <para> 448 432 A job agent will not execute a plug-in unless the admin has configured 449 t old the job agent to do so. This can be done either from the plug-in433 the job agent to do so. This can be done either from the plug-in 450 434 side or from the job agent side. To register a plug-in with one or more 451 job agents from the plug-in side go to the edit view the plug-in and435 job agents from the plug-in side go to the edit view of the plug-in and 452 436 select the <guilabel>Job agents</guilabel> tab. To do the same from 453 437 the job agent side go to the edit view of the job agent and select … … 831 815 832 816 <para> 833 The <guilabel>Test with file</guilabel> function is a very useful817 The <guilabel>Test with file</guilabel> function is a very useful 834 818 function for specifying import file formats. It is supported by 835 819 many of the import plug-ins that read data from a simple text … … 871 855 <para> 872 856 The window consists of two parts, the upper part where the file 873 to parse and the par meters used to parse it are entered, and857 to parse and the parameters used to parse it are entered, and 874 858 the lower part that displays information about the parsing. 875 859 </para> … … 894 878 <para> 895 879 Each data column must be separated by some special character or 896 character sequence not occur ing in the data, for example a tab or a comma.880 character sequence not occurring in the data, for example a tab or a comma. 897 881 Data in fixed-size columns cannot be parsed. 898 882 </para> … … 900 884 <listitem> 901 885 <para> 902 Data may optionally be prece eded by a data header, for example,886 Data may optionally be preceded by a data header, for example, 903 887 the names of the columns. 904 888 </para> … … 906 890 <listitem> 907 891 <para> 908 The data header may optionally be prece eded by file headers.892 The data header may optionally be preceded by file headers. 909 893 A file header is something that can be split into a name-value pair. 910 894 </para>
Note: See TracChangeset
for help on using the changeset viewer.
