Changeset 515

Show
Ignore:
Timestamp:
08/05/09 16:24:19 (3 years ago)
Author:
david
Message:

updating migration docs

Location:
enpraxis.educommons/trunk/enpraxis/educommons/docs
Files:
2 added
9 modified

Legend:

Unmodified
Added
Removed

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/CHANGES.html

    r8 r515  
    253253<hr class="footer" /> 
    254254<a class="reference external" href="CHANGES.txt">View document source</a>. 
    255 Generated on: 2009-01-14 23:51 UTC. 
     255Generated on: 2009-08-05 22:23 UTC. 
    256256Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    257257 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/IMSContentPackaging.html

    r8 r515  
    1212 
    1313 
    14 <div class="section" id="ims-content-packaging-and-educommons-3-1-1-final"> 
    15 <h1>IMS Content Packaging and eduCommons 3.1.1-final</h1> 
     14<div class="section" id="ims-content-packaging-and-educommons-3-2-1"> 
     15<h1>IMS Content Packaging and eduCommons 3.2.1</h1> 
    1616<p>This document details how to write IMS Content packages that are compatible with 
    17 eduCommons 3.1.1-final.</p> 
     17eduCommons 3.2.1.</p> 
    1818<p>eduCommons uses version 1.2 of the IMS Content Packaging Specification. XML Schemas 
    1919for the specification can be found at <a class="reference external" href="http://imsglobal.org/xsd/imscp_v1p2.xsd">http://imsglobal.org/xsd/imscp_v1p2.xsd</a> and 
    … …  
    475475<hr class="footer" /> 
    476476<a class="reference external" href="IMSContentPackaging.txt">View document source</a>. 
    477 Generated on: 2009-01-14 23:51 UTC. 
     477Generated on: 2009-08-05 22:23 UTC. 
    478478Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    479479 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/INSTALL.html

    r8 r515  
    55<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    66<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 
    7 <title>eduCommons 3.1.1-final Installation</title> 
     7<title>eduCommons 3.2.1 Installation</title> 
    88<link rel="stylesheet" href="./default.css" type="text/css" /> 
    99</head> 
    1010<body> 
    11 <div class="document" id="educommons-3-1-1-final-installation"> 
    12 <h1 class="title">eduCommons 3.1.1-final Installation</h1> 
     11<div class="document" id="educommons-3-2-1-installation"> 
     12<h1 class="title">eduCommons 3.2.1 Installation</h1> 
    1313<h2 class="subtitle" id="installation-instructions">Installation Instructions</h2> 
    1414 
    … …  
    245245<pre class="literal-block"> 
    246246cd /opt/Zope-2.10.5/web/Products 
    247 sudo tar -zxvf ~/eduCommons-3.1.1-final.tar.gz 
     247sudo tar -zxvf ~/eduCommons-3.2.1.tar.gz 
    248248</pre> 
    249249<p>eduCommons includes a number of products which need to be put in the root 
    … …  
    251251<pre class="literal-block"> 
    252252cd /opt/Zope-2.10.5/web/Products 
    253 sudo mv eduCommons-3.1.1-final/* . 
    254 sudo rm -rf eduCommons-3.1.1-final 
     253sudo mv eduCommons-3.2.1/* . 
     254sudo rm -rf eduCommons-3.2.1 
    255255</pre> 
    256256<p>The products that now ship with eduCommons are as follows:</p> 
    … …  
    453453<hr class="footer" /> 
    454454<a class="reference external" href="INSTALL.txt">View document source</a>. 
    455 Generated on: 2009-01-14 23:51 UTC. 
     455Generated on: 2009-08-05 22:23 UTC. 
    456456Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    457457 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/LOCALIZATION.html

    r8 r515  
    2525setting from neutral to the appropriate setting for your instance.</p> 
    2626</div> 
    27 <div class="section" id="localization-with-educommons-3-1-1-final"> 
    28 <h1>Localization with eduCommons 3.1.1-final</h1> 
     27<div class="section" id="localization-with-educommons-3-2-1"> 
     28<h1>Localization with eduCommons 3.2.1</h1> 
    2929<div class="section" id="overview"> 
    3030<h2>Overview</h2> 
    … …  
    155155<hr class="footer" /> 
    156156<a class="reference external" href="LOCALIZATION.txt">View document source</a>. 
    157 Generated on: 2009-01-14 23:51 UTC. 
     157Generated on: 2009-08-05 22:23 UTC. 
    158158Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    159159 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/MIGRATION.html

    r8 r515  
    55<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    66<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 
    7 <title>Migrating to eduCommons 3.1.1-final</title> 
     7<title>Migrating to eduCommons 3.2.1</title> 
    88<link rel="stylesheet" href="./default.css" type="text/css" /> 
    99</head> 
    1010<body> 
    11 <div class="document" id="migrating-to-educommons-3-1-1-final"> 
    12 <h1 class="title">Migrating to eduCommons 3.1.1-final</h1> 
     11<div class="document" id="migrating-to-educommons-3-2-1"> 
     12<h1 class="title">Migrating to eduCommons 3.2.1</h1> 
    1313 
    1414<div class="section" id="preparation"> 
    … …  
    1818<ol class="arabic simple"> 
    1919<li>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.)</li> 
    20 <li>Using the Zope Management Interface (ZMI), export any customizations you have made in your [old site] --&gt; portal_skins --&gt; custom folder and then delete all files in the custom folder. You can re-import these customizations once you have migrated the site.</li> 
    21 <li>Verify that your current instance is eduCommons-3.0.2-final.</li> 
     20<li>Verify that your current instance is eduCommons-3.1.1-final.</li> 
    2221</ol> 
    2322</blockquote> 
    2423</div> 
    25 <div class="section" id="migration-of-educommons-3-0-2-final-to-3-1-1-final"> 
    26 <h1>Migration of eduCommons 3.0.2-final to 3.1.1-final</h1> 
    27 <p>The migration eduCommons from version 3.0.2-final to version 3.1.1-final 
     24<div class="section" id="migration-of-educommons-3-1-1-final-to-3-2-1"> 
     25<h1>Migration of eduCommons 3.1.1-final to 3.2.1</h1> 
     26<p>The migration eduCommons from version 3.1.1-final to version 3.2.1 
    2827includes the following:</p> 
    2928<blockquote> 
    3029<ol class="arabic simple"> 
    31 <li>Movement of Data.fs file to a new 3.1.1-final instance</li> 
    32 <li>Migration to Plone 3.0.6</li> 
    33 <li>Migration to the eduCommons 3.1.1-final instance</li> 
     30<li>Pre-migration of Data.fs in version 3.1.1-final</li> 
     31<li>Movement of Data.fs file to a new 3.2.1 instance</li> 
     32<li>Migration to the eduCommons 3.2.1 instance</li> 
     33<li>Export/Import of eduCommons site to a new 3.2.1 instance</li> 
    3434<li>Final steps</li> 
    3535</ol> 
    3636</blockquote> 
    3737</div> 
    38 <div class="section" id="movement-of-data-fs-file-to-a-new-3-1-1-final-instance"> 
    39 <h1>Movement of Data.fs file to a new 3.1.1-final instance</h1> 
    40 <p>For the first step, you will move the Data.fs file from the old instance to 
    41 the new instance. First of all, install an eduCommons-3.1.1-final 
    42 instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
    43 copy the Data.fs file from the var directory of the old site to the 
    44 var directory of the new site:</p> 
    45 <pre class="literal-block"> 
    46 sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/ 
    47 </pre> 
    48 </div> 
    49 <div class="section" id="migration-of-plone"> 
    50 <h1>Migration of Plone</h1> 
    51 <p>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:</p> 
     38<div class="section" id="pre-migration-of-data-fs-in-version-3-1-1-final"> 
     39<h1>Pre-migration of Data.fs in version 3.1.1-final</h1> 
     40<p>For this step, you will need:</p> 
     41<ul class="simple"> 
     42<li>contentmigration Plone Add-on Product, available at <a class="reference external" href="http://pypi.python.org/packages/source/P/Products.contentmigration/Products.contentmigration-1.1.zip">http://pypi.python.org/packages/source/P/Products.contentmigration/Products.contentmigration-1.1.zip</a></li> 
     43<li>to copy the migration source code found in version 3.2.1.  The file is located at eduCommons/extras/PreMigrate.py<ul> 
     44<li>Copy this into [old instance]/Products/eduCommons/Extensions</li> 
     45</ul> 
     46</li> 
     47</ul> 
     48<p>Add contentmigration product by following these steps:</p> 
    5249<blockquote> 
    5350<ol class="arabic simple"> 
    54 <li>Open your 3.1.1-final eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.)</li> 
    55 <li>Run portal_migration migration (click the upgrade button on the migrate tab)</li> 
     51<li>Download the product from the aforementioned URL</li> 
     52<li>Unzip the product into [old_instance]/Products</li> 
     53<li>Restart zope</li> 
     54</ol> 
     55</blockquote> 
     56<p>Run the migration script by following these steps:</p> 
     57<blockquote> 
     58<ol class="arabic simple"> 
     59<li>Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
     60<li>From the drop down menu, select &quot;External method&quot; and click the Add button.</li> 
     61<li>Enter the following parameters:<ul> 
     62<li>Id: PreMigrate</li> 
     63<li>Title: PreMigrate</li> 
     64<li>Module Name: PreMigrate</li> 
     65<li>Function Name: pre_migrate_3_1_1_to_3_2_1</li> 
     66</ul> 
     67</li> 
     68<li>Click Add</li> 
     69<li>Click on the PreMigrate script you just added</li> 
     70<li>Click the test tab.</li> 
     71<li>Verify that the method ran successfully. (It should give you feedback.)</li> 
    5672</ol> 
    5773</blockquote> 
    5874</div> 
    59 <div class="section" id="installation-of-filesystemstorage-product"> 
    60 <h1>Installation of FileSystemStorage Product</h1> 
    61 <p>At this point in time, we need to ensure that the FileSystemStorage AddOn Product is installed:</p> 
     75<div class="section" id="movement-of-data-fs-file-to-a-new-3-2-1-instance"> 
     76<h1>Movement of Data.fs file to a new 3.2.1 instance</h1> 
     77<p>For this step, you will move the Data.fs file from the old instance to 
     78the new instance. First of all, install an eduCommons-3.2.1 
     79instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
     80copy the Data.fs file from the var directory of the old site to the 
     81var/filestorage directory of the new site:</p> 
     82<pre class="literal-block"> 
     83sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/filestorage 
     84</pre> 
     85</div> 
     86<div class="section" id="migration-to-educommons-3-2-1-instance"> 
     87<h1>Migration to eduCommons 3.2.1 instance</h1> 
     88<p>eduCommons 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:</p> 
    6289<blockquote> 
    6390<ol class="arabic simple"> 
    64 <li>Open your 3.1.1-final eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.)</li> 
    65 <li>Navigate to portal_quickinstaller</li> 
    66 <li>Select FileSystemStorage</li> 
    67 <li>Press Install</li> 
     91<li>Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321</li> 
     92<li>Open your new 3.2.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
     93<li>Navigate to portal_setup</li> 
     94<li>Press the 'Upgrades' tab</li> 
     95<li>From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button.</li> 
     96<li>Choose the 'Migration :: 3.1.1 to 3.2.1' option</li> 
     97<li>Press Upgrade</li> 
    6898</ol> 
    6999</blockquote> 
    70100</div> 
    71 <div class="section" id="migration-of-the-educommons-3-1-1-final-instance"> 
    72 <h1>Migration of the eduCommons 3.1.1-final instance</h1> 
    73 <p>eduCommons 3.1.1-final uses the portal_setup tool to perform the necessary upgrade from 3.0.2 to 3.1.1-final:</p> 
     101<div class="section" id="export-import-of-educommons-site-to-a-new-3-2-1-instance"> 
     102<h1>Export/Import of eduCommons site to a new 3.2.1 instance</h1> 
     103<p>You are now ready to transfer your migrated instance to the production environment.</p> 
    74104<blockquote> 
    75105<ol class="arabic simple"> 
    76 <li>Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
    77 <li>Navigate to portal_setup</li> 
    78 <li>Press the 'Upgrades' tab</li> 
    79 <li>From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button.</li> 
    80 <li>Choose the 'Migration :: 3.0.2 to 3.1.0' option</li> 
    81 <li>Press Upgrade</li> 
     106<li>Navigate to the root of your ZMI instance</li> 
     107<li>Select the checkbox next to your new 3.2.1 eduCommons site</li> 
     108<li>Press Import/Export</li> 
     109<li>If your production environment is on the same server as your migration environment, choose 'Save file to server', else 
     110Download the file to your local machine. Dependent on the size of your site, this process may take a long time.</li> 
     111<li>Move the .zexp into the import directory of your production site [production_site]parts/instance/import</li> 
     112<li>Navigate to the ZMI of your production site</li> 
     113<li>Press Import/Export</li> 
     114<li>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.</li> 
     115<li>If desired, rename your imported eduCommons321 site.</li> 
    82116</ol> 
    83117</blockquote> 
    … …  
    92126<hr class="footer" /> 
    93127<a class="reference external" href="MIGRATION.txt">View document source</a>. 
    94 Generated on: 2009-01-14 23:51 UTC. 
     128Generated on: 2009-08-05 22:23 UTC. 
    95129Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    96130 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/MIGRATIONS_OLD.html

    r8 r515  
    55<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    66<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 
    7 <title>Migrating to eduCommons 3.0.2</title> 
     7<title></title> 
    88<link rel="stylesheet" href="./default.css" type="text/css" /> 
    99</head> 
    1010<body> 
    11 <div class="document" id="migrating-to-educommons-3-0-2"> 
    12 <h1 class="title">Migrating to eduCommons 3.0.2</h1> 
     11<div class="document"> 
    1312 
     13 
     14<div class="section" id="migrating-to-educommons-3-1-1"> 
     15<h1>Migrating to eduCommons 3.1.1</h1> 
    1416<div class="section" id="preparation"> 
    15 <h1>Preparation</h1> 
     17<h2>Preparation</h2> 
     18<p>A few things you should do before beginning the migration:</p> 
     19<blockquote> 
     20<ol class="arabic simple"> 
     21<li>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.)</li> 
     22<li>Using the Zope Management Interface (ZMI), export any customizations you have made in your [old site] --&gt; portal_skins --&gt; custom folder and then delete all files in the custom folder. You can re-import these customizations once you have migrated the site.</li> 
     23<li>Verify that your current instance is eduCommons-3.0.2-final.</li> 
     24</ol> 
     25</blockquote> 
     26</div> 
     27<div class="section" id="migration-of-educommons-3-0-2-final-to-3-1-1"> 
     28<h2>Migration of eduCommons 3.0.2-final to 3.1.1</h2> 
     29<p>The migration eduCommons from version 3.0.2-final to version 3.1.1 
     30includes the following:</p> 
     31<blockquote> 
     32<ol class="arabic simple"> 
     33<li>Movement of Data.fs file to a new 3.1.1 instance</li> 
     34<li>Migration to Plone 3.0.6</li> 
     35<li>Migration to the eduCommons 3.1.1 instance</li> 
     36<li>Final steps</li> 
     37</ol> 
     38</blockquote> 
     39</div> 
     40<div class="section" id="movement-of-data-fs-file-to-a-new-3-1-1-instance"> 
     41<h2>Movement of Data.fs file to a new 3.1.1 instance</h2> 
     42<p>For the first step, you will move the Data.fs file from the old instance to 
     43the new instance. First of all, install an eduCommons-3.1.1 
     44instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
     45copy the Data.fs file from the var directory of the old site to the 
     46var directory of the new site:</p> 
     47<pre class="literal-block"> 
     48sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/ 
     49</pre> 
     50</div> 
     51<div class="section" id="migration-of-plone"> 
     52<h2>Migration of Plone</h2> 
     53<p>The following steps need to be performed in the ZMI, as eduCommons-3.1.1 utlizes Plone 3.0.6, instead of 3.0.4:</p> 
     54<blockquote> 
     55<ol class="arabic simple"> 
     56<li>Open your 3.1.1 eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.)</li> 
     57<li>Run portal_migration migration (click the upgrade button on the migrate tab)</li> 
     58</ol> 
     59</blockquote> 
     60</div> 
     61<div class="section" id="installation-of-filesystemstorage-product"> 
     62<h2>Installation of FileSystemStorage Product</h2> 
     63<p>At this point in time, we need to ensure that the FileSystemStorage AddOn Product is installed:</p> 
     64<blockquote> 
     65<ol class="arabic simple"> 
     66<li>Open your 3.1.1 eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.)</li> 
     67<li>Navigate to portal_quickinstaller</li> 
     68<li>Select FileSystemStorage</li> 
     69<li>Press Install</li> 
     70</ol> 
     71</blockquote> 
     72</div> 
     73<div class="section" id="migration-of-the-educommons-3-1-1-instance"> 
     74<h2>Migration of the eduCommons 3.1.1 instance</h2> 
     75<p>eduCommons 3.1.1 uses the portal_setup tool to perform the necessary upgrade from 3.0.2 to 3.1.1:</p> 
     76<blockquote> 
     77<ol class="arabic simple"> 
     78<li>Open your 3.1.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
     79<li>Navigate to portal_setup</li> 
     80<li>Press the 'Upgrades' tab</li> 
     81<li>From the drop down menu, select 'Products.eduCommons:default' and click Choose Profile button.</li> 
     82<li>Choose the 'Migration :: 3.0.2 to 3.1.0' option</li> 
     83<li>Press Upgrade</li> 
     84</ol> 
     85</blockquote> 
     86</div> 
     87<div class="section" id="final-steps"> 
     88<h2>Final Steps</h2> 
     89<blockquote> 
     90Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated.</blockquote> 
     91</div> 
     92</div> 
     93<div class="section" id="migrating-to-educommons-3-0-2"> 
     94<h1>Migrating to eduCommons 3.0.2</h1> 
     95<div class="section" id="id1"> 
     96<h2>Preparation</h2> 
    1697<p>A few things you should do before beginning the migration:</p> 
    1798<blockquote> 
    … …  
    24105</div> 
    25106<div class="section" id="migration-of-educommons-2-3-1-final-to-3-0-2"> 
    26 <h1>Migration of eduCommons 2.3.1-final to 3.0.2</h1> 
    27 <p>The migration eduCommons from version 2.3.1-final to version 3.1.1-final 
     107<h2>Migration of eduCommons 2.3.1-final to 3.0.2</h2> 
     108<p>The migration eduCommons from version 2.3.1-final to version 3.1.1 
    28109includes the following:</p> 
    29110<blockquote> 
    … …  
    32113<li>Movement of Data.fs file to a new 3.0.2 instance</li> 
    33114<li>Migration of Plone 3.0.4</li> 
    34 <li>Migration of the eduCommons 3.1.1-final instance</li> 
     115<li>Migration of the eduCommons 3.1.1 instance</li> 
    35116<li>Final steps</li> 
    36117</ol> 
    … …  
    38119</div> 
    39120<div class="section" id="pre-migration-of-data-fs-in-version-2-3-1-final"> 
    40 <h1>Pre-migration of Data.fs in version 2.3.1-final</h1> 
    41 <p>For this step, you will need to copy the migration source code found in version 3.1.1-final.  The file is located at eduCommons/extras/PreMigrate.py . 
     121<h2>Pre-migration of Data.fs in version 2.3.1-final</h2> 
     122<p>For this step, you will need to copy the migration source code found in version 3.1.1.  The file is located at eduCommons/extras/PreMigrate.py . 
    42123Copy this into [old instance]/Products/eduCommons/Extensions.</p> 
    43124<p>Run the migration script by following these steps:</p> 
    … …  
    61142</div> 
    62143<div class="section" id="movement-of-data-fs-file-to-a-new-3-0-2-instance"> 
    63 <h1>Movement of Data.fs file to a new 3.0.2 instance</h1> 
     144<h2>Movement of Data.fs file to a new 3.0.2 instance</h2> 
    64145<p>For the next step you will move the Data.fs file from the old instance to 
    65146the new instance. First of all, install an eduCommons-3.0.2 
    … …  
    71152</pre> 
    72153</div> 
    73 <div class="section" id="migration-of-plone"> 
    74 <h1>Migration of Plone</h1> 
    75 <p>The following steps need to be performed in the ZMI, as eduCommons-3.1.1-final utlizes Plone 3.0.4, instead of 2.5.x:</p> 
     154<div class="section" id="id2"> 
     155<h2>Migration of Plone</h2> 
     156<p>The following steps need to be performed in the ZMI, as eduCommons-3.1.1 utlizes Plone 3.0.4, instead of 2.5.x:</p> 
    76157<blockquote> 
    77158<ol class="arabic simple"> 
    … …  
    84165</div> 
    85166<div class="section" id="migration-of-the-educommons-3-0-2-instance"> 
    86 <h1>Migration of the eduCommons 3.0.2 instance</h1> 
    87 <p>Run the migration script included with the 3.1.1-final instance by following these steps:</p> 
     167<h2>Migration of the eduCommons 3.0.2 instance</h2> 
     168<p>Run the migration script included with the 3.1.1 instance by following these steps:</p> 
    88169<blockquote> 
    89170<ol class="arabic simple"> 
    90171<li>Copy the migration script found in Products/eduCommons/extras/Migrate.py to [new_instance]/Extensions/</li> 
    91 <li>Open your 3.1.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
     172<li>Open your 3.1.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
    92173<li>Navigate to the root of the ZMI (click the Root Folder link located in the upper left portion of the page)</li> 
    93174<li>From the drop down menu, select &quot;External method&quot; and click the Add button.</li> 
    … …  
    108189</blockquote> 
    109190</div> 
    110 <div class="section" id="final-steps"> 
    111 <h1>Final Steps</h1> 
     191<div class="section" id="id3"> 
     192<h2>Final Steps</h2> 
    112193<blockquote> 
    113194<p>Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated. 
    … …  
    138219</div> 
    139220</div> 
     221</div> 
    140222<div class="footer"> 
    141223<hr class="footer" /> 
    142224<a class="reference external" href="MIGRATIONS_OLD.txt">View document source</a>. 
    143 Generated on: 2009-01-14 23:51 UTC. 
     225Generated on: 2009-08-05 22:23 UTC. 
    144226Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    145227 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/PORTLETS.html

    r8 r515  
    158158<hr class="footer" /> 
    159159<a class="reference external" href="PORTLETS.txt">View document source</a>. 
    160 Generated on: 2009-01-14 23:51 UTC. 
     160Generated on: 2009-08-05 22:23 UTC. 
    161161Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    162162 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/MIGRATIONS_OLD.txt

    r8 r515  
     1=================================== 
     2Migrating to eduCommons 3.1.1 
     3=================================== 
     4 
     5 
     6Preparation 
     7----------- 
     8A few things you should do before beginning the migration: 
     9 
     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 
     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. 
     15 
     16 
     17Migration of eduCommons 3.0.2-final to 3.1.1 
     18-------------------------------------------------- 
     19 
     20The migration eduCommons from version 3.0.2-final to version 3.1.1 
     21includes the following: 
     22 
     23  1. Movement of Data.fs file to a new 3.1.1 instance 
     24 
     25  2. Migration to Plone 3.0.6 
     26 
     27  3. Migration to the eduCommons 3.1.1 instance 
     28 
     29  4. Final steps 
     30 
     31Movement of Data.fs file to a new 3.1.1 instance 
     32------------------------------------------------------ 
     33 
     34For the first step, you will move the Data.fs file from the old instance to 
     35the new instance. First of all, install an eduCommons-3.1.1 
     36instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
     37copy the Data.fs file from the var directory of the old site to the 
     38var directory of the new site: 
     39:: 
     40 
     41  sudo cp -rvfp [old instance home]/var/Data.fs [new instance home]/var/ 
     42 
     43 
     44Migration of Plone 
     45------------------ 
     46The following steps need to be performed in the ZMI, as eduCommons-3.1.1 utlizes Plone 3.0.6, instead of 3.0.4: 
     47 
     48  1. Open your 3.1.1 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) 
     51 
     52 
     53Installation of FileSystemStorage Product 
     54----------------------------------------- 
     55At this point in time, we need to ensure that the FileSystemStorage AddOn Product is installed: 
     56 
     57  1. Open your 3.1.1 eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) 
     58 
     59  2. Navigate to portal_quickinstaller 
     60  
     61  3. Select FileSystemStorage 
     62 
     63  4. Press Install 
     64 
     65Migration of the eduCommons 3.1.1 instance 
     66------------------------------------------------ 
     67eduCommons 3.1.1 uses the portal_setup tool to perform the necessary upgrade from 3.0.2 to 3.1.1: 
     68 
     69  1. Open your 3.1.1 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 
     76 
     77Final Steps 
     78----------- 
     79 
     80  Your site should now be migrated. Navigate to your site in the browser and ensure it has migrated. 
     81 
     82 
    183=================================== 
    284Migrating to eduCommons 3.0.2 
    … …  
    18100-------------------------------------------------- 
    19101 
    20 The migration eduCommons from version 2.3.1-final to version $$version$$ 
     102The migration eduCommons from version 2.3.1-final to version 3.1.1 
    21103includes the following: 
    22104 
    … …  
    27109  3. Migration of Plone 3.0.4 
    28110 
    29   4. Migration of the eduCommons $$version$$ instance 
     111  4. Migration of the eduCommons 3.1.1 instance 
    30112 
    31113  5. Final steps 
    … …  
    34116----------------------------------------------- 
    35117 
    36 For this step, you will need to copy the migration source code found in version $$version$$.  The file is located at eduCommons/extras/PreMigrate.py . 
     118For this step, you will need to copy the migration source code found in version 3.1.1.  The file is located at eduCommons/extras/PreMigrate.py . 
    37119Copy this into [old instance]/Products/eduCommons/Extensions. 
    38120 
    … …  
    74156Migration of Plone 
    75157------------------ 
    76 The following steps need to be performed in the ZMI, as eduCommons-$$version$$ utlizes Plone 3.0.4, instead of 2.5.x: 
     158The following steps need to be performed in the ZMI, as eduCommons-3.1.1 utlizes Plone 3.0.4, instead of 2.5.x: 
    77159 
    78160  1. Open your 3.0.2 eduCommons site in the ZMI. (click educommons setup, then click Zope Management Interface.) 
    … …  
    83165Migration of the eduCommons 3.0.2 instance 
    84166------------------------------------------------ 
    85 Run the migration script included with the $$version$$ instance by following these steps: 
     167Run the migration script included with the 3.1.1 instance by following these steps: 
    86168 
    87169  1. Copy the migration script found in Products/eduCommons/extras/Migrate.py to [new_instance]/Extensions/ 
    88   2. Open your $$version$$ eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
     170  2. Open your 3.1.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
    89171  3. Navigate to the root of the ZMI (click the Root Folder link located in the upper left portion of the page) 
    90172  4. From the drop down menu, select "External method" and click the Add button. 

  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/MIGRATION.txt

    r8 r515  
    1010  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.) 
    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. 
     12  2. Verify that your current instance is eduCommons-3.1.1-final. 
    1513 
    1614 
    17 Migration of eduCommons 3.0.2-final to $$version$$ 
     15Migration of eduCommons 3.1.1-final to $$version$$ 
    1816-------------------------------------------------- 
    1917 
    20 The migration eduCommons from version 3.0.2-final to version $$version$$ 
     18The migration eduCommons from version 3.1.1-final to version $$version$$ 
    2119includes the following: 
    2220 
    23   1. Movement of Data.fs file to a new $$version$$ instance 
     21  1. Pre-migration of Data.fs in version 3.1.1-final 
    2422 
    25   2. Migration to Plone 3.0.6 
     23  2. Movement of Data.fs file to a new $$version$$ instance 
    2624 
    2725  3. Migration to the eduCommons $$version$$ instance 
    2826 
    29   4. Final steps 
     27  4. Export/Import of eduCommons site to a new $$version$$ instance 
     28 
     29  5. 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 
     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 
     50Run 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 
    3071 
    3172Movement of Data.fs file to a new $$version$$ instance 
    3273------------------------------------------------------ 
    3374 
    34 For the first step, you will move the Data.fs file from the old instance to 
     75For this step, you will move the Data.fs file from the old instance to 
    3576the new instance. First of all, install an eduCommons-$$version$$ 
    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-$$version$$ utlizes Plone 3.0.6, instead of 3.0.4: 
     85Migration to eduCommons $$version$$ instance 
     86------------------------------------------------ 
     87eduCommons $$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: 
    4788 
    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 
    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 $$version$$ instance 
     99-------------------------------------------------------------- 
    56100 
    57   1. Open your $$version$$ 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 $$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. 
    76113 
    77114Final Steps