From portal-commits at lists.jboss.org Wed Feb  6 21:04:14 2008
Content-Type: multipart/mixed; boundary="===============3649136115513575758=="
MIME-Version: 1.0
From: portal-commits at lists.jboss.org
To: portal-commits at lists.jboss.org
Subject: [portal-commits] JBoss Portal SVN: r9822 -
 docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
Date: Wed, 06 Feb 2008 21:04:13 -0500
Message-ID: <E1JMw7Z-0007Lf-SO@committer01.frg.pub.inap.atl.jboss.com>

--===============3649136115513575758==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: mmcallis
Date: 2008-02-06 21:04:13 -0500 (Wed, 06 Feb 2008)
New Revision: 9822

Modified:
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migratio=
n.xml
Log:
revising 4.1.2. Updating the Database


Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/m=
igration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migrati=
on.xml	2008-02-07 01:28:49 UTC (rev 9821)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migrati=
on.xml	2008-02-07 02:04:13 UTC (rev 9822)
@@ -68,23 +68,22 @@
       </sect2>
       <sect2 id=3D"upgrade_portal_database">
          <title>Updating the Database</title>
-         <note>All things described in this section can be done using Admi=
nPortlet. Treat this directions more as guideline
-         if you need to automate migration for big portal deployment.</not=
e>
          <para>
-            Database schema wasn't changed between 2.4 and 2.6 releases, b=
ut still content that is kept in it
-            changed slightly in few areas. You can easily update the data =
manually by using tools proper for your
-            RDBMS. If you use <emphasis>MySQL</emphasis> you can use <emph=
asis>MySQL Query Browser</emphasis> that can
-            be downloaded from <emphasis>MySQL</emphasis> website.
+		 All procedures described in the following sections can performed using =
the AdminPortlet. Treat the directions as guidelines if you need to automat=
e the migration of a large JBoss Portal deployment.
+	 </para>
+	 <para>
+		 Database schema has not changed between the JBoss Portal 2.4 and 2.6 re=
leases, but certain content that is kept in the databases has changed. Data=
 can be updated manually by using the correct tools for your RDBMS. For exa=
mple, if you are using a MySQL database, you can use the <ulink url=3D"http=
://www.mysql.com/products/tools/query-browser/">MySQL Query Browser</ulink>.
          </para>
-         <note>
-            Instructions below refer to standard JBoss Portal 2.4 deployme=
nt. If you named core portlets, portlet instances
-            or portlet windows differently you will need to make proper mo=
difications in those steps.
-         </note>
+	 <para>
+		 The following instructions refer to a standard JBoss Portal 2.4 deploym=
ent. If you named core portlets, portlet instances, or portlet windows diff=
erently, you will need to make the appropriate modifications. The following=
 is an example of using the MySQL Query Browser:
+         </para>
+	 <para>
          <mediaobject>
             <imageobject>
                <imagedata align=3D"center" valign=3D"middle" fileref=3D"im=
ages/migration/querybrowser1.png"/>
             </imageobject>
          </mediaobject>
+ 	</para>
          <sect3>
             <title>Portlet names</title>
             <para>Names of few core bundled portlets changed. To update th=
em you need to:</para>


--===============3649136115513575758==--