[Bio] / FigTutorial / SEED_administration_issues.html Repository:
ViewVC logotype

Diff of /FigTutorial/SEED_administration_issues.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.9, Fri Jul 30 19:21:08 2004 UTC revision 1.10, Fri Jul 30 20:48:52 2004 UTC
# Line 236  Line 236 
236    
237  <li> First, make sure that you are in the BASH shell by typing "echo $SHELL";  <li> First, make sure that you are in the BASH shell by typing "echo $SHELL";
238     if the result is not "bash", type "bash" to enter the BASH shell.     if the result is not "bash", type "bash" to enter the BASH shell.
239    <p>
240    
241  <li> Next, check that the result of typing "which perl" is the version  <li> Next, check that the result of typing "which perl" is the version
242     of perl owned by the SEED; it should look something like     of perl owned by the SEED; it should look something like
# Line 249  Line 250 
250         source Path_to_FIGdisk/config/fig-user-env.sh         source Path_to_FIGdisk/config/fig-user-env.sh
251     </pre>     </pre>
252     to setup your FIG environment properly.     to setup your FIG environment properly.
253    <p>
254    
255  <li> Next, make a copy of the Code Distribution Environment (from a DVD  <li> Next, make a copy of the Code Distribution Environment (from a DVD
256  or via the network).  Suppose that we have made such a directory in  or via the network).  Suppose that we have made such a directory in
# Line 260  Line 262 
262  where <b>TargetDirectory</b> is where you wish to build the new  where <b>TargetDirectory</b> is where you wish to build the new
263  production version.  We recommend calling it something like  production version.  We recommend calling it something like
264  <b>FIGdisk.July24</b>.  <b>FIGdisk.July24</b>.
265    <p>
266    
267  <li> Stop all work on the production machine for the duration of the update.  <li> Stop all work on the production machine for the duration of the update.
268       You do this by clicking on the "Seed Control Panel" link,       You do this by clicking on the "Seed Control Panel" link,
269       and then entering an explanatory message in the text box       and then entering an explanatory message in the text box
270       and clicking on the "Disable SEED server" button.       and clicking on the "Disable SEED server" button.
271    <p>
272    
273  <li> You now need to capture the assignments, annotations and  <li> You now need to capture the assignments, annotations and
274       subsystems work that has been done on the production machine.       subsystems work that has been done on the production machine.
# Line 277  Line 281 
281    
282       This will capture your updates and save them in the directory       This will capture your updates and save them in the directory
283       /tmp/sync.data.july.1.2004.<br>       /tmp/sync.data.july.1.2004.<br>
284    <p>
285    
286  <li>Now, you need to stop the existing production system using  <li>Now, you need to stop the existing production system using
287  <pre>  <pre>
288          ~/FIGdisk/bin/stop-servers          ~/FIGdisk/bin/stop-servers
289  </pre>  </pre>
290    <p>
291    
292  <li>Now, you need to configure the runtime environment for the system  <li>Now, you need to configure the runtime environment for the system
293  you are running on.  you are running on.
# Line 294  Line 300 
300  Those that are supported on July 24, 2004 are <b>mac</b> for  Those that are supported on July 24, 2004 are <b>mac</b> for
301  Macintoshes running panther, <b>mac-jaguar</b> for those that have not  Macintoshes running panther, <b>mac-jaguar</b> for those that have not
302  upgraded to panther, and <b>linux-postgres</b>.  upgraded to panther, and <b>linux-postgres</b>.
303    <p>
304    
305  <li>Now, you need to insert the new Data directory into the newly  <li>Now, you need to insert the new Data directory into the newly
306  constructed version of the SEED.  To do this use  constructed version of the SEED.  To do this use
# Line 306  Line 313 
313  update system.  If you acquired a new Data directory via Data DVDs, you  update system.  If you acquired a new Data directory via Data DVDs, you
314  will need to unpack them using the README instructions, but what  will need to unpack them using the README instructions, but what
315  results is a new version of the <b>Data</b> directory.  results is a new version of the <b>Data</b> directory.
316    <p>
317    
318  <li>Now, you need to start the servers in order to load the databases  <li>Now, you need to start the servers in order to load the databases
319  with the new release using  with the new release using
# Line 318  Line 326 
326          fig load_all          fig load_all
327  </pre>  </pre>
328  This last command will run for several hours.  This last command will run for several hours.
329    <p>
330    
331  <li> Now, you need to capture the changes made to the old production  <li> Now, you need to capture the changes made to the old production
332       version using something like       version using something like
333       <pre>       <pre>
334           <b>sync_new_system /tmp/sync.data.july.1.2004 make-assignments</b>           <b>sync_new_system /tmp/sync.data.july.1.2004 make-assignments</b>
335       </pre>       </pre>
336    <p>
337    
338  <li>Run  <li>Run
339  <pre>  <pre>
340          index_annotations          index_annotations
341          index_subsystems          index_subsystems
342          make_indexes          make_indexes
343  </pre>  </pre>
344    <p>
345    
346  <li> Now, finally, you should alter the symbolic link in <i>~fig</i> to  <li> Now, finally, you should alter the symbolic link in <i>~fig</i> to
347  the current FIGdisk using something like:  the current FIGdisk using something like:
# Line 339  Line 351 
351          ln -s TargetDirectory FIGdisk          ln -s TargetDirectory FIGdisk
352  </pre>  </pre>
353  That should make the new SEED the one available through the Web interface.  That should make the new SEED the one available through the Web interface.
354    <p>
355    
356  <li> You should now bring your update system to the same state as the  <li> You should now bring your update system to the same state as the
357       production system.  This can be done by making sure that       production system.  This can be done by making sure that

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.10

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3