Author: bdaw
Date: 2007-03-26 18:00:36 -0400 (Mon, 26 Mar 2007)
New Revision: 6836
Added:
docs/trunk/referenceGuide/en/images/migration/querybrowser1.png
docs/trunk/referenceGuide/en/images/migration/querybrowser2.png
docs/trunk/referenceGuide/en/images/migration/theme.png
Modified:
docs/trunk/referenceGuide/en/modules/migration.xml
Log:
migration guide
Added: docs/trunk/referenceGuide/en/images/migration/querybrowser1.png
===================================================================
(Binary files differ)
Property changes on: docs/trunk/referenceGuide/en/images/migration/querybrowser1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/trunk/referenceGuide/en/images/migration/querybrowser2.png
===================================================================
(Binary files differ)
Property changes on: docs/trunk/referenceGuide/en/images/migration/querybrowser2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/trunk/referenceGuide/en/images/migration/theme.png
===================================================================
(Binary files differ)
Property changes on: docs/trunk/referenceGuide/en/images/migration/theme.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: docs/trunk/referenceGuide/en/modules/migration.xml
===================================================================
--- docs/trunk/referenceGuide/en/modules/migration.xml 2007-03-26 19:48:47 UTC (rev 6835)
+++ docs/trunk/referenceGuide/en/modules/migration.xml 2007-03-26 22:00:36 UTC (rev 6836)
@@ -13,9 +13,174 @@
</chapterinfo>
<title>Upgrading 2.4 - 2.6</title>
<warning>
- This section to be updated soon with 2.4 to 2.6 migration instructions, using the
Migration Application.
+ Before performing any instructions or operations mentioned below remember to backup
your database content!
</warning>
-<!--
+ <sect1 id="manual_migration">
+ <title>Manual upgrade</title>
+ <para>
+ Although database schema remains the same in JBoss Portal 2.6 there are several
differences that prevent from simple deployment
+ of newest portal version using JBoss Portal 2.4 database. In this chapter we
will list major ones and give
+ instructions on how to manually update proper data.
+ </para>
+ <para>
+ Upgrading procedure can be quite straightforward:
+ <itemizedlist>
+ <listitem>
+ Remove <emphasis
role="bold">$JBOSS_HOME/server/default/deploy/jboss-portal.sar</emphasis>
file.
+ </listitem>
+ <listitem>
+ Remove <emphasis
role="bold">$JBOSS_HOME/server/default/data</emphasis> directory.
+ </listitem>
+ <listitem>
+ Update data in portal database like described in following sections of
this chapter
+ </listitem>
+ <listitem>
+ Deploy JBoss Portal 2.6
+ </listitem>
+ </itemizedlist>
+ </para>
+ <sect2>
+ <title>Theme</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" valign="middle"
fileref="images/migration/theme.png"/>
+ </imageobject>
+ </mediaobject>
+ <para>
+ Themes in 2.6 version changed as now they
+ contain additional areas - the best example is upper right corner where links
like "Login", "Admin", "My Dashboard"
+ are visable. If you use default theme like "renaissance" you should
clean up old theme files deployed in portal by removing
+ <emphasis
role="bold">$JBOSS_HOME/server/default/data</emphasis> directory. To
update your custom themes please
+ refere to those bundled with portal as an example.
+ </para>
+ <note>If you stay with old theme files you may find JBP 2.6 unusable by
not even be able to log in.</note>
+ </sect2>
+ <sect2>
+ <title>Database</title>
+ <para>
+ Database schema wasn't changed between 2.4 and 2.6 releases. Still
content that is kept in the database
+ 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
<emphasis>MySQL Query Browser</emphasis> that can
+ be downloaded from <emphasis>MySQL</emphasis> website.
+ </para>
+ <note>
+ Instructions below refer to standard JBoss Portal 2.4 deployment. If you
named core portlets, portlet instances
+ or portlet windows differently you will need to make proper modifications in
those steps.
+ </note>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" valign="middle"
fileref="images/migration/querybrowser1.png"/>
+ </imageobject>
+ </mediaobject>
+ <sect3>
+ <title>Portlet names</title>
+ <para>Names of few core bundled portlets changed. To update them you
need to:</para>
+ <para>
+ In <emphasis role="bold">JBP_INSTANCES</emphasis>
table:
+ <itemizedlist>
+ <listitem>Change
"<emphasis>local.portal.CMSPorlet</emphasis>" in
<emphasis>PORTLET_REF</emphasis> column to
+
"<emphasis>local./portal-cms.CMSPortlet</emphasis>"
+ </listitem>
+ <listitem>Change
"<emphasis>local.portal.CMSAdminPorlet</emphasis>" in
<emphasis>PORTLET_REF</emphasis> column to
+
"<emphasis>local./portal-cms.CMSAdminPortlet</emphasis>"
+ </listitem>
+ <listitem>Change
"<emphasis>local.portal.ManagementPorlet</emphasis>" in
<emphasis>PORTLET_REF</emphasis> column to
+
"<emphasis>local./portal-admin.AdminPortlet</emphasis>"
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ <emphasis>NavigationPortlet</emphasis> from JBP 2.4 is not
present anymore. Its functionality is now realized by
+ <emphasis>PageCustomizerInterceptor</emphasis> so all
references to <emphasis>NavigationPortlet</emphasis> should
+ be removed from all portal pages. You can do it either by cleaning up
database content or by using
+ <emphasis>AdminPortlet</emphasis> in Portal interface. In
database you should remove:
+ <itemizedlist>
+ <listitem>
+ Rows containing
"<emphasis>local.portal.NavigationPortlet</emphasis>" in
+ "<emphasis>PORTLET_REF</emphasis>" column in
+ "<emphasis>JBP_INSTANCES</emphasis>" table.
+ </listitem>
+ <listitem>
+ Rows containing
"<emphasis>NavigationPortletInstance</emphasis>" in
+ "<emphasis>INSTANCE_REF</emphasis>" column in
+ "<emphasis>JBP_WINDOW</emphasis>" table.
+ </listitem>
+ <listitem>
+ Rows containing
"<emphasis>NavigationPortletWindow</emphasis>" in
+ "<emphasis>NAME</emphasis>" column in
+ "<emphasis>JBP_OBJECT</emphasis>" table.
+ </listitem>
+ </itemizedlist>
+ </para>
+ </sect3>
+ <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[
+ <window>
+ <window-name>CMSWindow</window-name>
+ <content>
+ <content-type>cms</content-type>
+ <content-uri>/default/index.html</content-uri>
+ </content>
+ <region>center</region>
+ <height>0</height>
+ </window>
+ ]]>
+ </programlisting>
+ </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
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" valign="middle"
fileref="images/migration/querybrowser2.png"/>
+ </imageobject>
+ </mediaobject>
+ <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
+ </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:
+ <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>
+ <note>Remember that you can also change portlet window content type and
configure path to CMS resource
+ using AdminPortlet</note>
+ </para>
+ </sect3>
+ </sect2>
+
+
+
+ </sect1>
+ <!--
<para>This chapter addresses migration issues from version 2.2 to 2.4 of JBoss
Portal.</para>
<sect1 id="migrating_database">
<title>Migrating the Database</title>
Show replies by date