Show
Ignore:
Timestamp:
08/06/09 13:03:56 (3 years ago)
Author:
david
Message:

updating docs

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • enpraxis.educommons/trunk/enpraxis/educommons/MIGRATION.txt

    r8 r522  
    11=================================== 
    2 Migrating to eduCommons 3.1.1-final 
     2Migrating to eduCommons 3.2.1 
    33=================================== 
    44 
     
    88A few things you should do before beginning the migration: 
    99 
    10   1. VERY IMPORTANT: SAVE A BACKUP OF YOUR Data.fs FILE, which is located in the [old instance home]/var directory of your eduCommons site. This file contains all of the content for your site. (This way you will able to restore your file from this Data.fs file if anything goes wrong.) 
     101. VERY IMPORTANT: SAVE A BACKUP OF YOUR Data.fs FILE, which is located in the [old instance home]/var directory of your eduCommons site. This file contains all of the content for your site. (This way you will able to restore your file from this Data.fs file if anything goes wrong.) 
    1111 
    12   2. Using the Zope Management Interface (ZMI), export any customizations you have made in your [old site] --> portal_skins --> custom folder and then delete all files in the custom folder. You can re-import these customizations once you have migrated the site. 
    13  
    14   3. Verify that your current instance is eduCommons-3.0.2-final. 
     122. Verify that your current instance is eduCommons-3.1.1-final. 
    1513 
    1614 
    17 Migration of eduCommons 3.0.2-final to 3.1.1-final 
     15Migration of eduCommons 3.1.1-final to 3.2.1 
    1816-------------------------------------------------- 
    1917 
    20 The migration eduCommons from version 3.0.2-final to version 3.1.1-final 
     18The migration eduCommons from version 3.1.1-final to version 3.2.1 
    2119includes the following: 
    2220 
    23   1. Movement of Data.fs file to a new 3.1.1-final instance 
     211. Pre-migration of Data.fs in version 3.1.1-final 
    2422 
    25   2. Migration to Plone 3.0.6 
     232. Movement of Data.fs file to a new 3.2.1 instance 
    2624 
    27   3. Migration to the eduCommons 3.1.1-final instance 
     253. Migration to the eduCommons 3.2.1 instance 
    2826 
    29   4. Final steps 
     274. Export/Import of eduCommons site to a new 3.2.1 instance 
    3028 
    31 Movement of Data.fs file to a new 3.1.1-final instance 
     295. Final steps 
     30 
     31Pre-migration of Data.fs in version 3.1.1-final 
     32----------------------------------------------- 
     33 
     34For this step, you will need: 
     35 
     36* contentmigration Plone Add-on Product, available at http://pypi.python.org/packages/source/P/Products.contentmigration/Products.contentmigration-1.1.zip        
     37  
     38* to copy the migration source code found in version 3.2.1.  The file is located at eduCommons/extras/PreMigrate.py 
     39 
     40  * Copy this into [old instance]/Products/eduCommons/Extensions 
     41 
     42Add contentmigration product by following these steps: 
     43 
     441. Download the product from the aforementioned URL 
     45 
     462. Unzip the product into [old_instance]/Products 
     47 
     483. Restart zope 
     49 
     50Run the migration script by following these steps: 
     51 
     521. Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
     53 
     542. From the drop down menu, select "External method" and click the Add button. 
     55 
     563. Enter the following parameters: 
     57 
     58   * Id: PreMigrate 
     59   * Title: PreMigrate 
     60   * Module Name: PreMigrate 
     61   * Function Name: pre_migrate_3_1_1_to_3_2_1 
     62 
     634. Click Add 
     64 
     655. Click on the PreMigrate script you just added 
     66 
     676. Click the test tab. 
     68 
     697. Verify that the method ran successfully. (It should give you feedback.) 
     70 
     71 
     72Movement of Data.fs file to a new 3.2.1 instance 
    3273------------------------------------------------------ 
    3374 
    34 For the first step, you will move the Data.fs file from the old instance to 
    35 the new instance. First of all, install an eduCommons-3.1.1-final 
     75For this step, you will move the Data.fs file from the old instance to 
     76the new instance. First of all, install an eduCommons-3.2.1 
    3677instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
    3778copy the Data.fs file from the var directory of the old site to the 
    38 var directory of the new site: 
     79var/filestorage directory of the new site: 
    3980:: 
    4081 
    41   sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/ 
     82  sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/filestorage 
    4283 
    4384 
    44 Migration of Plone 
    45 ------------------ 
    46 The following steps need to be performed in the ZMI, as eduCommons-3.1.1-final utlizes Plone 3.0.6, instead of 3.0.4: 
     85Migration to eduCommons 3.2.1 instance 
     86------------------------------------------------ 
     87eduCommons 3.2.1 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation: 
    4788 
    48   1. Open your 3.1.1-final eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) 
    49  
    50   2. Run portal_migration migration (click the upgrade button on the migrate tab) 
     891. Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321 
     902. Open your new 3.2.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
     913. Navigate to portal_setup 
     924. Press the 'Upgrades' tab 
     935. From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button. 
     946. Choose the 'Migration :: 3.1.1 to 3.2.1' option 
     957. Press Upgrade 
    5196 
    5297 
    53 Installation of FileSystemStorage Product 
    54 ----------------------------------------- 
    55 At this point in time, we need to ensure that the FileSystemStorage AddOn Product is installed: 
     98Export/Import of eduCommons site to a new 3.2.1 instance 
     99-------------------------------------------------------------- 
    56100 
    57   1. Open your 3.1.1-final eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) 
     101You are now ready to transfer your migrated instance to the production environment.   
    58102 
    59   2. Navigate to portal_quickinstaller 
    60   
    61   3. Select FileSystemStorage 
    62  
    63   4. Press Install 
    64  
    65 Migration of the eduCommons 3.1.1-final instance 
    66 ------------------------------------------------ 
    67 eduCommons 3.1.1-final uses the portal_setup tool to perform the necessary upgrade from 3.0.2 to 3.1.1-final: 
    68  
    69   1. Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
    70   2. Navigate to portal_setup 
    71   3. Press the 'Upgrades' tab 
    72   4. From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button. 
    73   5. Choose the 'Migration :: 3.0.2 to 3.1.0' option 
    74   6. Press Upgrade 
    75  
     1031. Navigate to the root of your ZMI instance 
     1042. Select the checkbox next to your new 3.2.1 eduCommons site 
     1053. Press Import/Export 
     1064. If your production environment is on the same server as your migration environment, choose 'Save file to server', else 
     107   Download the file to your local machine. Dependent on the size of your site, this process may take a long time. 
     1085. Move the .zexp into the import directory of your production site [production_site]parts/instance/import 
     1096. Navigate to the ZMI of your production site 
     1107. Press Import/Export 
     1118. Select your .zexp from the drop down list, and press Import. Dependent on the size of your site, this process may take a long time. 
     1129. If desired, rename your imported eduCommons321 site. 
    76113 
    77114Final Steps 
    78115----------- 
    79116 
    80   Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated. 
     117Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated. 
    81118 
    82119