Author: mmcallis Date: 2008-04-14 01:47:45 -0400 (Mon, 14 Apr 2008) New Revision: 10570 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml Log: 4.1. Manual Upgrade adding content as per wiki (JBPORTAL-1972) Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-04-14 05:12:34 UTC (rev 10569) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-04-14 05:47:45 UTC (rev 10570) @@ -25,6 +25,9 @@ The database schema has not changed since JBoss Portal 2.4; however, there are several differences when using a database created by JBoss Portal 2.4, that prevent simply deploying the latest version of JBoss Portal. For example, some portlets are no longer present in JBoss Portal 2.6, and certain existing portlets are now packaged differently. This chapter describes updating a MySQL database created by JBoss Portal 2.4, for use with JBoss Portal 2.6. </para> <para> + Users, roles, and pages created in JBoss Portal 2.4 should be accessible in JBoss Portal 2.6 deployments. + </para> + <para> The upgrade procedure can be straightforward: </para> <para> @@ -511,6 +514,9 @@ </itemizedlist> </para> <para> + For CMS migrations, back up the <computeroutput>jbp_cms_*</computeroutput> tables, and recreate them in the JBoss Portal 2.6 database. There were no schema changes for the CMS between JBoss Portal 2.4 and JBoss Portal 2.6. + </para> + <para> <note> <title>Portlet Content Type and Path to the CMS Resource</title> <para>