- Timestamp:
- 08/05/09 16:24:19 (3 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/MIGRATION.txt
r8 r515 10 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.) 11 11 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. 12 2. Verify that your current instance is eduCommons-3.1.1-final. 15 13 16 14 17 Migration of eduCommons 3. 0.2-final to $$version$$15 Migration of eduCommons 3.1.1-final to $$version$$ 18 16 -------------------------------------------------- 19 17 20 The migration eduCommons from version 3. 0.2-final to version $$version$$18 The migration eduCommons from version 3.1.1-final to version $$version$$ 21 19 includes the following: 22 20 23 1. Movement of Data.fs file to a new $$version$$ instance21 1. Pre-migration of Data.fs in version 3.1.1-final 24 22 25 2. M igration to Plone 3.0.623 2. Movement of Data.fs file to a new $$version$$ instance 26 24 27 25 3. Migration to the eduCommons $$version$$ instance 28 26 29 4. Final steps 27 4. Export/Import of eduCommons site to a new $$version$$ instance 28 29 5. Final steps 30 31 Pre-migration of Data.fs in version 3.1.1-final 32 ----------------------------------------------- 33 34 For 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 42 Add contentmigration product by following these steps: 43 44 1. Download the product from the aforementioned URL 45 46 2. Unzip the product into [old_instance]/Products 47 48 3. Restart zope 49 50 Run the migration script by following these steps: 51 52 1. Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 53 54 2. From the drop down menu, select "External method" and click the Add button. 55 56 3. 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 63 4. Click Add 64 65 5. Click on the PreMigrate script you just added 66 67 6. Click the test tab. 68 69 7. Verify that the method ran successfully. (It should give you feedback.) 70 30 71 31 72 Movement of Data.fs file to a new $$version$$ instance 32 73 ------------------------------------------------------ 33 74 34 For th e firststep, you will move the Data.fs file from the old instance to75 For this step, you will move the Data.fs file from the old instance to 35 76 the new instance. First of all, install an eduCommons-$$version$$ 36 77 instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 37 78 copy the Data.fs file from the var directory of the old site to the 38 var directory of the new site:79 var/filestorage directory of the new site: 39 80 :: 40 81 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 42 83 43 84 44 Migration of Plone45 ------------------ 46 The following steps need to be performed in the ZMI, as eduCommons-$$version$$ utlizes Plone 3.0.6, instead of 3.0.4:85 Migration to eduCommons $$version$$ instance 86 ------------------------------------------------ 87 eduCommons $$version$$ uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to $$version$$. 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: 47 88 48 1. Open your $$version$$ 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) 89 1. Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321 90 2. Open your new $$version$$ eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 91 3. Navigate to portal_setup 92 4. Press the 'Upgrades' tab 93 5. From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button. 94 6. Choose the 'Migration :: 3.1.1 to 3.2.1' option 95 7. Press Upgrade 51 96 52 97 53 Installation of FileSystemStorage Product 54 ----------------------------------------- 55 At this point in time, we need to ensure that the FileSystemStorage AddOn Product is installed: 98 Export/Import of eduCommons site to a new $$version$$ instance 99 -------------------------------------------------------------- 56 100 57 1. Open your $$version$$ eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) 101 You are now ready to transfer your migrated instance to the production environment. 58 102 59 2. Navigate to portal_quickinstaller 60 61 3. Select FileSystemStorage 62 63 4. Press Install 64 65 Migration of the eduCommons $$version$$ instance 66 ------------------------------------------------ 67 eduCommons $$version$$ uses the portal_setup tool to perform the necessary upgrade from 3.0.2 to $$version$$: 68 69 1. Open your $$version$$ 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 103 1. Navigate to the root of your ZMI instance 104 2. Select the checkbox next to your new $$version$$ eduCommons site 105 3. Press Import/Export 106 4. 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. 108 5. Move the .zexp into the import directory of your production site [production_site]parts/instance/import 109 6. Navigate to the ZMI of your production site 110 7. Press Import/Export 111 8. 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. 112 9. If desired, rename your imported eduCommons321 site. 76 113 77 114 Final Steps
