Page Comparison

...

1. Checkout and install DB from trunk

   No Format
   svn co https://source.sakaiproject.org/svn/db/trunk db mvn clean install sakai:deploy -f db/pom.xml

   • If you can, run maven und from 2.4.x db, otherwise removing the following from your tomcat:
     • tomcat/components/sakai-db-pack
     • tomcat/shared/lib/sakai-db-api
2. Checkout and install entity from trunk

   No Format
   svn co https://source.sakaiproject.org/svn/entity/trunk entity mvn clean install sakai:deploy -f entity/pom.xml

   • Again if you can't use maven und, manually remove the following:
     • tomcat/components/sakai-entity-pack
     • tomcat/shared/lib/sakai-entity-api
3. At this point there might be two versions of hibernate in tomcat/shared/lib
   Remove hibernate 3.1.3 and leave 3.2.5ga
4. Checkout and install the new content code

   No Format
   svn co https://source.sakaiproject.org/svn/content/branches/SAK-12105 mvn clean install sakai:deploy -f SAK-12105/pom.xml -PJCR

   • If you can, run maven und from 2.4.x content, otherwise removing the following from your tomcat:
     • tomcat/components/sakai-content-pack

Content Migration

stubUnlike some of the other data upgrades that have been performed on Content Hosting, the conversion to a JCR implementation requires copying all of the data over to another repository. Below is a description of the first algorithm are working on to perform the migration.

This first version:

• Doesn't try to do anything fancy.
• Is not parallelized in any way. It can only run on one node at a time.

Depending on how testing goes and the needs of other universities, this may be spiffed up a bit. Otherwise, if it runs in a reasonable amount of time and tests out, it may stand as is.

Migration algorithm in a Nutshell

1. Create a table to store path and migration status for each item. The migration will run through the table top to bottom, copying the items over and marking them finished when done.
2. Copy all the entries in CONTENT_COLLECTION to the migration table. Then copy all the entries in CONTENT_RESOURCE to the migration table. This means that we will copy all the collections/folders over first, so they exist when we try to copy the files over.
3. Start copying items over.
4. Listen for Content Events that create, edit, or delete content items, and append these to the end of the migration table.

Detailed Description of Algorithm

IN PROGRESS

Testing Migration Integrity

IN PROGRESS