[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.8, Wed Jul 28 22:42:21 2004 UTC revision 1.9, Fri Jul 30 19:21:08 2004 UTC
# Line 233  Line 233 
233  can flip back to the old system.  can flip back to the old system.
234  The actual steps are as follows:  The actual steps are as follows:
235  <ol>  <ol>
236  <li>First make a copy of the Code Distribution Environment (from a DVD  
237    <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.
239    
240    <li> Next, check that the result of typing "which perl" is the version
241       of perl owned by the SEED; it should look something like
242       <pre>
243           /Users/fig/FIGdisk/env/mac/bin/perl
244       </pre>
245       although the exact results will depend on where your existing copy
246       of the SEED is installed, whether your platform is a Macintosh or LINUX,
247       etc. If the result does not look similar to the above, type:
248       <pre>
249           source Path_to_FIGdisk/config/fig-user-env.sh
250       </pre>
251       to setup your FIG environment properly.
252    
253    <li> Next, make a copy of the Code Distribution Environment (from a DVD
254  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
255  CodeDistEnv.  Then use,  CodeDistEnv.  Then use,
 <br>  
256  <pre>  <pre>
257          cd CodeDistEnv          cd CodeDistEnv
258          ./install-code TargetDirectory          ./install-code TargetDirectory
# Line 249  Line 265 
265       You do this by clicking on the "Seed Control Panel" link,       You do this by clicking on the "Seed Control Panel" link,
266       and then entering an explanatory message in the text box       and then entering an explanatory message in the text box
267       and clicking on the "Disable SEED server" button.       and clicking on the "Disable SEED server" button.
268    
269  <li> You now need to capture the assignments, annotations and  <li> You now need to capture the assignments, annotations and
270       subsystems work that has been done on the production machine.       subsystems work that has been done on the production machine.
271       To do this, you need to know when the last production release       To do this, you need to know when the last production release
272       was installed.  Suppose that it was July 1, 2004.       was installed.  Suppose that it was July 1, 2004.
273       If that was the date, we recommend that you run<br><br>       If that was the date, we recommend that you run
274       <pre>       <pre>
275          <b>extract_data_for_syncing_after_update 7/1/2004 /tmp/sync.data.july.1.2004</b>          <b>extract_data_for_syncing_after_update 7/1/2004 /tmp/sync.data.july.1.2004</b>
276       </pre>       </pre>
277       <br><br>  
278       This will capture your updates and save them in the directory       This will capture your updates and save them in the directory
279       /tmp/sync.data.july.1.2004.       /tmp/sync.data.july.1.2004.<br>
280    
281  <li>Now, you need to stop the existing production system using  <li>Now, you need to stop the existing production system using
 <br>  
282  <pre>  <pre>
283          ~/FIGdisk/bin/stop-servers          ~/FIGdisk/bin/stop-servers
284  </pre>  </pre>
 <br>  
285    
286  <li>Now, you need to configure the runtime environment for the system  <li>Now, you need to configure the runtime environment for the system
287  you are running on.  you are running on.
288  To do this, use  To do this, use
 <br>  
289  <pre>  <pre>
290          cd TargetDirectory          cd TargetDirectory
291          ./configure MacOrLinux          ./configure MacOrLinux
# Line 282  Line 297 
297    
298  <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
299  constructed version of the SEED.  To do this use  constructed version of the SEED.  To do this use
 <br>  
300  <pre>  <pre>
301            chmod -R 777 TheNewData
302          cd TargetDirectory/FIG          cd TargetDirectory/FIG
         chmod -R 777 Data  
303          ln -s TheNewData Data          ln -s TheNewData Data
304  </pre>  </pre>
305  where TheNewData is the new Data directory, which normally comes  from the  where TheNewData is the new Data directory, which normally comes  from the
306  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
307  will need to unpack them using the README instructions, but what  will need to unpack them using the README instructions, but what
308  results is a new version of the <b>Data</b> directory.  results is a new version of the <b>Data</b> directory.
309    
310  <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
311  with the new release using  with the new release using
 <br>  
312  <pre>  <pre>
313          cd TargetDirectory/bin          cd TargetDirectory/bin
314          ./start-servers          ./start-servers
# Line 303  Line 317 
317          init_FIG          init_FIG
318          fig load_all          fig load_all
319  </pre>  </pre>
 <br>  
320  This last command will run for several hours.  This last command will run for several hours.
321    
322  <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
323       version using something like       version using something like
      <br>  
324       <pre>       <pre>
325           <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>
326       </pre>       </pre>
      <br>  
327  <li>Run  <li>Run
 <br>  
328  <pre>  <pre>
329          index_annotations          index_annotations
330          index_subsystems          index_subsystems
331          make_indexes          make_indexes
332  </pre>  </pre>
333    
334  <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
335  the current FIGdisk using something like:  the current FIGdisk using something like:
 <br>  
336  <pre>  <pre>
337          cd ~fig          cd ~fig
338          rm FIGdisk     # should be removing a symbolic link to the current SEED          rm FIGdisk     # should be removing a symbolic link to the current SEED
339          ln -s TargetDirectory FIGdisk          ln -s TargetDirectory FIGdisk
340  </pre>  </pre>
341  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.
342    
343  <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
344       production system.  This can be done by making sure that       production system.  This can be done by making sure that
345       <b>/tmp/sync.data.july.1.2004</b> is accessible to the update system.       <b>/tmp/sync.data.july.1.2004</b> is accessible to the update system.

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

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3