From portal-commits at lists.jboss.org Thu Feb  7 00:22:15 2008
Content-Type: multipart/mixed; boundary="===============1045072684957916125=="
MIME-Version: 1.0
From: portal-commits at lists.jboss.org
To: portal-commits at lists.jboss.org
Subject: [portal-commits] JBoss Portal SVN: r9825 -
 docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
Date: Thu, 07 Feb 2008 00:22:15 -0500
Message-ID: <E1JMzDD-0006al-7r@committer01.frg.pub.inap.atl.jboss.com>

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

Author: mmcallis
Date: 2008-02-07 00:22:15 -0500 (Thu, 07 Feb 2008)
New Revision: 9825

Modified:
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migratio=
n.xml
Log:
revising 4.1.2.2. CMS


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 05:21:26 UTC (rev 9824)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migrati=
on.xml	2008-02-07 05:22:15 UTC (rev 9825)
@@ -134,15 +134,10 @@
          <sect3>
             <title>CMS</title>
             <para>
-               This is probably the less trival part to do directly in dat=
abase. In JBP 2.6 version the way that CMS
-               content is being displayed changed significantly. Please re=
fer to
-               <link linkend=3D"contentintegration">Content Integration</l=
ink> and <link linkend=3D"cmsPortlet">CMS Portlet</link>
-               chapters for more information. Basically currently there is=
 no need to have more than one instance of
-               <emphasis>CMSPortlet</emphasis> and the portlet window disp=
lays CMS content not by referring to that portlet instance
-               but by having proper <emphasis>content-type</emphasis> defi=
ned. In "<emphasis>default-object.xml</emphasis>
-               you will find following configuration:
-               <programlisting>
-                  <![CDATA[
+		    In JBoss Portal 2.6 versions, the way the CMS content is displayed c=
hanged significantly. For further information, please refer to <xref linken=
d=3D"contentintegration"/> and <xref linkend=3D"cmsPortlet"/>. Currently th=
ere is no need to have more than one instance of the <emphasis>CMSPortlet</=
emphasis>. The portlet window displays CMS content, not by referring to tha=
t portlet instance, but by having the proper <emphasis>content-type</emphas=
is> defined. The following configuration is in the <filename>jboss-portal.s=
ar/conf/data/default-object.xml</filename> file:
+	    </para>
+	    <para>
+<screen><![CDATA[
 <window>
    <window-name>CMSWindow</window-name>
    <content>
@@ -151,53 +146,54 @@
    </content>
    <region>center</region>
    <height>0</height>
-</window>
-                  ]]>
-               </programlisting>
-            </para>
+</window>]]>
+</screen>
+</para>
             <para>
-               Open <emphasis role=3D"bold">JBP_OBJECT_NODE</emphasis> tab=
le in your database schema. By looking at
-               <emphasis role=3D"bold">PATH</emphasis> column you will eas=
ily find any occurances of CMS in your portal
-               deployment
+		    The following example uses the MySQL Query Browser. Open the <emphas=
is role=3D"bold">JBP_OBJECT_NODE</emphasis> table in your database schema. =
Look at the <emphasis role=3D"bold">PATH</emphasis> column to identify any =
occurrences of CMS in your JBoss Portal deployment. Identify any row referr=
ing to <emphasis>CMSPortletWindow</emphasis>, and remember the number in <e=
mphasis role=3D"bold">PARENT_KEY</emphasis> column. The <emphasis role=3D"b=
old">PARENT_KEY</emphasis> number is needed in the following steps:
             </para>
+            <para>
             <mediaobject>
                <imageobject>
                   <imagedata align=3D"center" valign=3D"middle" fileref=3D=
"images/migration/querybrowser2.png"/>
                </imageobject>
             </mediaobject>
+           </para>
             <para>
-               For any row you will identify as referring to <emphasis>CMS=
PortletWindow</emphasis> in your system remember
-               the number in <emphasis role=3D"bold">PK</emphasis> column.=
 It will be needed in next steps
+		    Go to the <emphasis role=3D"bold">JBP_WINDOW</emphasis> table and fi=
nd a row with the same
+		    <emphasis role=3D"bold">PARENT_KEY</emphasis> value from the <emphas=
is role=3D"bold">JBP_OBJECT_NODE</emphasis> table. In such a row, replace <=
emphasis>CMSPortletInstance</emphasis> with a path to your CMS resource. Fo=
r example, by default, JBoss Portal displays <filename>/default/index.html<=
/filename>.
             </para>
-            <para> Go to <emphasis role=3D"bold">JBP_WINDOW</emphasis> tab=
le and find row with the same
-               <emphasis role=3D"bold">PK</emphasis> value like the one fr=
om
-               <emphasis role=3D"bold">JBP_OBJECT_NODE</emphasis> table. I=
n such row replace
-               "<emphasis>CMSPortletInstance</emphasis>" with a path to yo=
ur CMS resource. For example by default
-               portal is displaying "<emphasis>/default/index.html</emphas=
is>".
-            </para>
-            <para> Go to <emphasis role=3D"bold">JBP_PORTAL_OBJECT_PROPS</=
emphasis> table and add a row containing:
+            <para> Go to the <emphasis role=3D"bold">JBP_PORTAL_OBJECT_PRO=
PS</emphasis> table and add a row containing:
                <itemizedlist>
                   <listitem>
-                     The number you remembered in "<emphasis>OBJECT_KEY</e=
mphasis>" column.
-                  </listitem>
-                  <listitem>
-                     "<emphasis>portal.windowContentType</emphasis>" in "<=
emphasis>NAME</emphasis>" column.
-                  </listitem>
-                  <listitem>
-                     "<emphasis>cms</emphasis>" in "<emphasis>jbp_VALUE</e=
mphasis>" column.
-                  </listitem>
-               </itemizedlist>
-            </para>
+			  <para>
+				  The <emphasis role=3D"bold">PARENT_KEY</emphasis> number remembered =
from the <emphasis>OBJECT_KEY</emphasis> column.
+			  </para>
+		  </listitem>
+		  <listitem>
+			  <para>
+				  <emphasis>portal.windowContentType</emphasis> in the <emphasis>NAME<=
/emphasis> column.
+			  </para>
+		  </listitem>
+		  <listitem>
+			  <para>
+				  <emphasis>cms</emphasis> in the <emphasis>jbp_VALUE</emphasis> colum=
n.
+			  </para>
+		  </listitem>
+	    </itemizedlist>
+          </para>
             <para>
-            <note>Remember that you can also change portlet window content=
 type and configure path to CMS resource
-               using AdminPortlet</note>
+            <note>
+		    <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 AdminPortlet.
+		    </para>
+	    </note>
             </para>
          </sect3>
       </sect2>
-
-
-
-   </sect1>
+</sect1>
    <!--
    <para>This chapter addresses migration issues from version 2.2 to 2.4 o=
f JBoss Portal.</para>
    <sect1 id=3D"migrating_database">


--===============1045072684957916125==--