Author: mmcallis Date: 2008-04-13 21:50:31 -0400 (Sun, 13 Apr 2008) New Revision: 10566 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml Log: -minor correction - this revision and r10565 are for Jira (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:36:59 UTC (rev 10565) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-04-14 01:50:31 UTC (rev 10566) @@ -94,10 +94,10 @@ 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> <para> - All procedures described in the following sections can performed using the <computeroutput>Admin</computeroutput> 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 <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> - 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 <computeroutput>Admin</computeroutput> 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. These can be done using the JBoss Portal 2.6 <guiicon>Admin</guiicon> portlet: </para> <para> <itemizedlist> @@ -177,7 +177,7 @@ <sect2> <title>Portlet Names</title> <para> - Names of certain core bundled-portlets have changed. Destroy the following instances and use the <computeroutput>Admin</computeroutput> 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_INSTANCES</emphasis> table as follows: </para> <para> <itemizedlist> @@ -511,7 +511,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 <computeroutput>Admin</computeroutput> Portlet. + using the <guiicon>Admin</guiicon> Portlet. </para> </note> </para>