- Timestamp:
- 08/06/09 10:50:39 (3 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/MIGRATION.txt
r515 r520 8 8 A few things you should do before beginning the migration: 9 9 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 12 2. Verify that your current instance is eduCommons-3.1.1-final. 13 13 14 14 … … 19 19 includes the following: 20 20 21 21 1. Pre-migration of Data.fs in version 3.1.1-final 22 22 23 23 2. Movement of Data.fs file to a new $$version$$ instance 24 24 25 25 3. Migration to the eduCommons $$version$$ instance 26 26 27 27 4. Export/Import of eduCommons site to a new $$version$$ instance 28 28 29 29 5. Final steps 30 30 31 31 Pre-migration of Data.fs in version 3.1.1-final … … 42 42 Add contentmigration product by following these steps: 43 43 44 44 1. Download the product from the aforementioned URL 45 45 46 46 2. Unzip the product into [old_instance]/Products 47 47 48 48 3. Restart zope 49 49 50 50 Run the migration script by following these steps: 51 51 52 52 1. Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 53 53 54 54 2. From the drop down menu, select "External method" and click the Add button. 55 55 56 56 3. Enter the following parameters: 57 57 58 59 60 61 58 * Id: PreMigrate 59 * Title: PreMigrate 60 * Module Name: PreMigrate 61 * Function Name: pre_migrate_3_1_1_to_3_2_1 62 62 63 63 4. Click Add 64 64 65 65 5. Click on the PreMigrate script you just added 66 66 67 67 6. Click the test tab. 68 68 69 69 7. Verify that the method ran successfully. (It should give you feedback.) 70 70 71 71 … … 87 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: 88 88 89 90 91 92 93 94 95 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 96 96 97 97 … … 101 101 You are now ready to transfer your migrated instance to the production environment. 102 102 103 104 105 106 107 108 109 110 111 112 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. 113 113 114 114 Final Steps 115 115 ----------- 116 116 117 117 Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated. 118 118 119 119
