--- SEED_administration_issues.html 2004/07/28 22:42:21 1.8 +++ SEED_administration_issues.html 2004/07/30 19:21:08 1.9 @@ -233,10 +233,26 @@ can flip back to the old system. The actual steps are as follows:
    -
  1. First make a copy of the Code Distribution Environment (from a DVD + +
  2. First, make sure that you are in the BASH shell by typing "echo $SHELL"; + if the result is not "bash", type "bash" to enter the BASH shell. + +
  3. Next, check that the result of typing "which perl" is the version + of perl owned by the SEED; it should look something like +
    +       /Users/fig/FIGdisk/env/mac/bin/perl
    +   
    + although the exact results will depend on where your existing copy + of the SEED is installed, whether your platform is a Macintosh or LINUX, + etc. If the result does not look similar to the above, type: +
    +       source Path_to_FIGdisk/config/fig-user-env.sh
    +   
    + to setup your FIG environment properly. + +
  4. Next, make a copy of the Code Distribution Environment (from a DVD or via the network). Suppose that we have made such a directory in CodeDistEnv. Then use, -
     	cd CodeDistEnv
     	./install-code TargetDirectory
    @@ -249,28 +265,27 @@
          You do this by clicking on the "Seed Control Panel" link,
          and then entering an explanatory message in the text box 
          and clicking on the "Disable SEED server" button.
    +
     
  5. You now need to capture the assignments, annotations and subsystems work that has been done on the production machine. To do this, you need to know when the last production release was installed. Suppose that it was July 1, 2004. - If that was the date, we recommend that you run

    + If that was the date, we recommend that you run
             extract_data_for_syncing_after_update 7/1/2004 /tmp/sync.data.july.1.2004
          
    -

    + This will capture your updates and save them in the directory - /tmp/sync.data.july.1.2004. + /tmp/sync.data.july.1.2004.
    +
  6. Now, you need to stop the existing production system using -
     	~/FIGdisk/bin/stop-servers
     
    -
  7. Now, you need to configure the runtime environment for the system you are running on. To do this, use -
     	cd TargetDirectory
     	./configure MacOrLinux
    @@ -282,19 +297,18 @@
     
     
  8. Now, you need to insert the new Data directory into the newly constructed version of the SEED. To do this use -
    +	chmod -R 777 TheNewData
     	cd TargetDirectory/FIG
    -	chmod -R 777 Data
     	ln -s TheNewData Data
     
    where TheNewData is the new Data directory, which normally comes from the update system. If you acquired a new Data directory via Data DVDs, you will need to unpack them using the README instructions, but what results is a new version of the Data directory. +
  9. Now, you need to start the servers in order to load the databases with the new release using -
     	cd TargetDirectory/bin
     	./start-servers
    @@ -303,31 +317,29 @@
     	init_FIG
     	fig load_all
     
    -
    This last command will run for several hours. +
  10. Now, you need to capture the changes made to the old production version using something like -
              sync_new_system /tmp/sync.data.july.1.2004 make-assignments
          
    -
  11. Run -
     	index_annotations
     	index_subsystems
     	make_indexes
     
    -
  12. Now, finally, you should alter the symbolic link in ~fig to + +
  13. Now, finally, you should alter the symbolic link in ~fig to the current FIGdisk using something like: -
     	cd ~fig
     	rm FIGdisk     # should be removing a symbolic link to the current SEED
     	ln -s TargetDirectory FIGdisk
     
    That should make the new SEED the one available through the Web interface. +
  14. You should now bring your update system to the same state as the production system. This can be done by making sure that /tmp/sync.data.july.1.2004 is accessible to the update system.