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/migration.xml
Log:
revising 4.1.2.2. CMS
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-02-07
05:21:26 UTC (rev 9824)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.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 database. In JBP
2.6 version the way that CMS
- content is being displayed changed significantly. Please refer to
- <link linkend="contentintegration">Content
Integration</link> and <link linkend="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
displays CMS content not by referring to that portlet instance
- but by having proper <emphasis>content-type</emphasis>
defined. 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 changed
significantly. For further information, please refer to <xref
linkend="contentintegration"/> and <xref
linkend="cmsPortlet"/>. Currently there is no need to have more than one
instance of the <emphasis>CMSPortlet</emphasis>. The portlet window displays
CMS content, not by referring to that portlet instance, but by having the proper
<emphasis>content-type</emphasis> defined. The following configuration is in
the <filename>jboss-portal.sar/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="bold">JBP_OBJECT_NODE</emphasis> table in your database schema.
By looking at
- <emphasis role="bold">PATH</emphasis> column you
will easily find any occurances of CMS in your portal
- deployment
+ The following example uses the MySQL Query Browser. Open the <emphasis
role="bold">JBP_OBJECT_NODE</emphasis> table in your database schema.
Look at the <emphasis role="bold">PATH</emphasis> column to identify
any occurrences of CMS in your JBoss Portal deployment. Identify any row referring to
<emphasis>CMSPortletWindow</emphasis>, and remember the number in <emphasis
role="bold">PARENT_KEY</emphasis> column. The <emphasis
role="bold">PARENT_KEY</emphasis> number is needed in the following
steps:
</para>
+ <para>
<mediaobject>
<imageobject>
<imagedata align="center" valign="middle"
fileref="images/migration/querybrowser2.png"/>
</imageobject>
</mediaobject>
+ </para>
<para>
- For any row you will identify as referring to
<emphasis>CMSPortletWindow</emphasis> in your system remember
- the number in <emphasis role="bold">PK</emphasis>
column. It will be needed in next steps
+ Go to the <emphasis role="bold">JBP_WINDOW</emphasis> table
and find a row with the same
+ <emphasis role="bold">PARENT_KEY</emphasis> value from the
<emphasis role="bold">JBP_OBJECT_NODE</emphasis> table. In such a
row, replace <emphasis>CMSPortletInstance</emphasis> with a path to your CMS
resource. For example, by default, JBoss Portal displays
<filename>/default/index.html</filename>.
</para>
- <para> Go to <emphasis
role="bold">JBP_WINDOW</emphasis> table and find row with the same
- <emphasis role="bold">PK</emphasis> value like the
one from
- <emphasis role="bold">JBP_OBJECT_NODE</emphasis>
table. In such row replace
- "<emphasis>CMSPortletInstance</emphasis>" with a
path to your CMS resource. For example by default
- portal is displaying
"<emphasis>/default/index.html</emphasis>".
- </para>
- <para> Go to <emphasis
role="bold">JBP_PORTAL_OBJECT_PROPS</emphasis> table and add a row
containing:
+ <para> Go to the <emphasis
role="bold">JBP_PORTAL_OBJECT_PROPS</emphasis> table and add a row
containing:
<itemizedlist>
<listitem>
- The number you remembered in
"<emphasis>OBJECT_KEY</emphasis>" column.
- </listitem>
- <listitem>
-
"<emphasis>portal.windowContentType</emphasis>" in
"<emphasis>NAME</emphasis>" column.
- </listitem>
- <listitem>
- "<emphasis>cms</emphasis>" in
"<emphasis>jbp_VALUE</emphasis>" column.
- </listitem>
- </itemizedlist>
- </para>
+ <para>
+ The <emphasis role="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> column.
+ </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 of JBoss
Portal.</para>
<sect1 id="migrating_database">