Author: mmcallis Date: 2008-04-13 22:08:44 -0400 (Sun, 13 Apr 2008) New Revision: 10567 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml Log: minor corrections to 4.1. Manual Upgrade (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 01:50:31 UTC (rev 10566) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-04-14 02:08:44 UTC (rev 10567) @@ -23,7 +23,7 @@ <sect1 id="manual_migration"> <title>Manual Upgrade</title> <para> - 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. + 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> The upgrade procedure can be straightforward: @@ -53,7 +53,7 @@ <sect2> <title>Themes</title> <para> - In JBoss Portal 2.6, portal pages contain additional areas, such as the <guiicon>Login</guiicon>, <guiicon>Admin</guiicon>, and <guiicon>Dashboard</guiicon> links, on the top right-hand corner: + In JBoss Portal 2.6, portal pages contain additional areas, such as the <guiicon>Login</guiicon>, <guiicon>Admin</guiicon>, and <guiicon>Dashboard</guiicon> links, on the top right-hand corner of portal pages: </para> <para> <mediaobject> @@ -63,7 +63,7 @@ </mediaobject> </para> <para> - Since portal pages now contain additional areas, certain themes have changed. If a default theme that exists in JBoss Portal 2.6 is used, such as renaissance, no configuration should be necessary. Using old themes from JBoss Portal 2.4 may make JBoss Portal 2.6 unusable, for example, not being able to log in. To update custom themes, refer to themes bundled with JBoss Portal 2.6 as an example. + Since portal pages now contain additional areas, certain themes have changed. If a default theme that exists in JBoss Portal 2.6 is used, such as renaissance, no configuration should be necessary. Using old themes from JBoss Portal 2.4 may make JBoss Portal 2.6 unusable, for example, not being able to log in. To update custom themes, refer to the bundled JBoss Portal 2.6 themes as an example. </para> </sect2> <sect2 id="upgrade_portal_database"> @@ -91,15 +91,12 @@ </itemizedlist> </para> <para> - When running JBoss Portal 2.6 with a database created by JBoss Portal 2.4, a non-existing portlet will try to display, resulting in a <computeroutput>404</computeroutput>, <computeroutput>The requested resource() is not available</computeroutput>, error. + All procedures described in the following sections can performed using the JBoss Portal 2.4 <guiicon>Admin</guiicon> Portlet. Treat these directions as guidelines when migrating a large JBoss Portal deployment. Database data can be updated manually using the correct tools for your RDBMS. For example, if you are using a MySQL database, use the <ulink url="http://www.mysql.com/products/tools/query-browser/">MySQL Query Browser</ulink>. </para> <para> - All procedures described in the following sections can performed using the <guiicon>Admin</guiicon> Portlet. Treat these directions as guidelines when migrating a large JBoss Portal deployment. Database data can be updated manually using the correct tools for your RDBMS. For example, if you are using a MySQL database, use the <ulink url="http://www.mysql.com/products/tools/query-browser/">MySQL Query Browser</ulink>. + During the upgrade process, legacy references have to be cleaned up, to either remove them, or to allow JBoss Portal 2.6 to recreate them correctly. Remove all references (instances and windows) to the portlets listed below, as they are not present in JBoss Portal 2.6. These can be done using the JBoss Portal 2.4 <guiicon>Admin</guiicon> portlet: </para> <para> - During the upgrade process, legacy references have to be cleaned up, to either remove them, or to allow JBoss Portal 2.6 to recreate them correctly. Remove all references (instances and windows) to the portlets listed below, as they are not present in JBoss Portal 2.6. These can be done using the JBoss Portal 2.6 <guiicon>Admin</guiicon> portlet: - </para> - <para> <itemizedlist> <listitem> <para> @@ -173,6 +170,14 @@ </imageobject> </mediaobject> </para> + <para> + <note> + <title>Request Resource Error</title> + <para> + When running JBoss Portal 2.6 with a database created by JBoss Portal 2.4, a non-existing portlet will try to display, resulting in a <computeroutput>404</computeroutput>, <computeroutput>The requested resource() is not available</computeroutput>, error. + </para> + </note> + </para> </sect2> <sect2> <title>Portlet Names</title>