Author: mmcallis Date: 2008-04-14 00:30:01 -0400 (Mon, 14 Apr 2008) New Revision: 10568 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml Log: period backup, 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 02:08:44 UTC (rev 10567) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-04-14 04:30:01 UTC (rev 10568) @@ -15,8 +15,7 @@ <para> <warning> <para> - Before performing any instructions or operations in this chapter, back up your database content and - the entire JBoss EAP or JBoss AS directory! + Before performing any instructions or operations in this chapter, back up your database and the entire JBoss EAP or JBoss AS directory! </para> </warning> </para> @@ -91,10 +90,10 @@ </itemizedlist> </para> <para> - 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>. + 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, you can use the <ulink url="http://www.mysql.com/products/tools/query-browser/">MySQL Query Browser</ulink>. </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.4 <guiicon>Admin</guiicon> portlet: + 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. This can be done using the JBoss Portal 2.4 <guiicon>Admin</guiicon> portlet: </para> <para> <itemizedlist> @@ -161,7 +160,7 @@ </itemizedlist> </para> <para> - The following instructions refer to a standard JBoss Portal 2.4 deployment. If you named core portlets, portlet instances, or portlet windows differently, you need to make the appropriate modifications. The following is an example of using the MySQL Query Browser: + The following instructions refer to a standard JBoss Portal 2.4 deployment. If core portlets, portlet instances, or portlet windows were renamed, make the appropriate modifications. The following is an example of the MySQL Query Browser: </para> <para> <mediaobject> @@ -172,9 +171,9 @@ </para> <para> <note> - <title>Request Resource Error</title> + <title>Requested 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. + When running JBoss Portal 2.6 with a database created by JBoss Portal 2.4, a non-existing portlet will try to be displayed, resulting in a <computeroutput>404</computeroutput>, <computeroutput>The requested resource() is not available</computeroutput>, error. </para> </note> </para> @@ -182,13 +181,13 @@ <sect2> <title>Portlet Names</title> <para> - Names of certain core bundled-portlets have changed. Destroy the following instances and use the <guiicon>Admin</guiicon> Portlet to recreate them, or, edit the <emphasis role="bold">JBP_INSTANCES</emphasis> table as follows: + Names of certain core bundled-portlets have changed. Destroy the following instances and use the <guiicon>Admin</guiicon> portlet to recreate them, or edit the <emphasis role="bold">JBP_INSTANCE</emphasis> table as follows: </para> <para> <itemizedlist> <listitem> <para> - Change <emphasis>local.samples.JSPPortlet'</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-jsp-samples.JSPPortlet</emphasis>. + Change <emphasis>local.samples.JSPPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column to <emphasis>local./portal-jsp-samples.JSPPortlet</emphasis>. </para> </listitem> <listitem> @@ -209,7 +208,7 @@ </itemizedlist> </para> <para> - Some portlets are no longer present in JBoss Portal 2.6, and certain existing portlets are now packaged differently. Remove the following entires in the <emphasis role="bold">JBP_INSTANCE</emphasis> table, so that JBoss Portal 2.6 can recreate them: + Some portlets are no longer present in JBoss Portal 2.6, and certain existing portlets are now packaged differently. Remove the following entries in the <emphasis role="bold">JBP_INSTANCE</emphasis> table, so that JBoss Portal 2.6 can recreate them: </para> <para> <itemizedlist> @@ -296,7 +295,7 @@ </itemizedlist> </para> <para> - Remove the following entires in the <emphasis role="bold">JBP_WINDOW</emphasis> table, so that JBoss Portal 2.6 can recreate them: + Remove the following entries in the <emphasis role="bold">JBP_WINDOW</emphasis> table, so that JBoss Portal 2.6 can recreate them: </para> <para> <itemizedlist> @@ -378,7 +377,7 @@ </itemizedlist> </para> <para> - Remove the following entires in the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table, so that JBoss Portal 2.6 can recreate them: + Remove the following entries in the <emphasis role="bold">JBP_OBJECT_NODE</emphasis> table, so that JBoss Portal 2.6 can recreate them: </para> <para> <itemizedlist> @@ -516,7 +515,7 @@ <title>Portlet Content Type and Path to the CMS Resource</title> <para> You can change the portlet window content type and configure the path to the CMS resource - using the <guiicon>Admin</guiicon> Portlet. + using the <guiicon>Admin</guiicon> portlet. </para> </note> </para> @@ -590,7 +589,7 @@ <sect2> <title>Portlet Names</title> <para> - Names of certain core bundled portlets have changed. Destroy the following instances and use the AdminPortlet to recreate them, or, edit the <emphasis role="bold">JBP_INSTANCES</emphasis> table as follows: + Names of certain core bundled portlets have changed. Destroy the following instances and use the AdminPortlet to recreate them, or, edit the <emphasis role="bold">JBP_INSTANCE</emphasis> table as follows: </para> <para> <orderedlist> @@ -618,7 +617,7 @@ <orderedlist> <listitem> <para> - In the <emphasis>JBP_INSTANCES</emphasis> table, rows containing <emphasis>local.portal.NavigationPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column. + In the <emphasis>JBP_INSTANCE</emphasis> table, rows containing <emphasis>local.portal.NavigationPortlet</emphasis> in the <emphasis>PORTLET_REF</emphasis> column. </para> </listitem> <listitem>