Author: mmcallis
Date: 2008-02-06 20:08:46 -0500 (Wed, 06 Feb 2008)
New Revision: 9820
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
Log:
revising 4.1. Manual Upgrade and 4.1.1. Themes
minor corrections to 3.6. Disabling Dynamic
Proxy Un-wrapping
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-07
00:07:31 UTC (rev 9819)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-07
01:08:46 UTC (rev 9820)
@@ -262,10 +262,10 @@
</sect1>
<sect1>
<title>Disabling Dynamic Proxy Un-wrapping</title>
- <para>JBoss Portal uses the JBoss Microkernel for the service infrastructure.
The JBoss Microkernel provides injection of services into other services, otherwise known
as wiring. Due to the Microkernel being JMX based, tt is only possible to inject dynamic
proxies that talk to the MBeanServer. The overhead at runtime is minimal since the
Microkernel implementation is highly optimized; however, when it is used with Java 5, a
noticeable bottleneck appears due to the fact that the implementation of the JMX API
classes, <emphasis>javax.management.*</emphasis>, provided by the Java
Platform, performs synchronization. This does not occur under JDK 1.4 since those classes
are implemented by JBoss MX.
+ <para>JBoss Portal uses the JBoss Microkernel for the service infrastructure.
The JBoss Microkernel provides injection of services into other services, otherwise known
as wiring. Due to the Microkernel being JMX based, it is only possible to inject dynamic
proxies that talk to the MBeanServer. The overhead at runtime is minimal since the
Microkernel implementation is highly optimized; however, when it is used with Java 5, a
noticeable bottleneck occurs due to the fact that the implementation of the JMX API
classes, <emphasis>javax.management.*</emphasis>, provided by the Java
Platform, perform synchronization. This does not occur under JDK 1.4, since those classes
are implemented by JBoss MX.
</para>
<para>
- JBoss Portal services use a special kind of Model MBean called
<emphasis>JBossServiceModelMBean</emphasis>, which allows the un-wrapping of
injected dynamic proxies, and replaces them with real plain old java object (POJO)
services. This allows the removal of the bottleneck with Java 5, and also provides a
performance boost on JDK 1.4. By default this feature is enabled, but it is possible to
disable. To do this on Linux systems, change into the
<filename>$JBOSS_HOME/bin/</filename> directory and run the following
command:
+ JBoss Portal services use a special kind of Model MBean called
<emphasis>JBossServiceModelMBean</emphasis>, which allows the un-wrapping of
injected dynamic proxies, and replaces them with plain old java object (POJO) services.
This removes the bottleneck when using Java 5, and also provides a performance boost on
JDK 1.4. By default this feature is enabled, but it is possible to disable. To do this on
Linux systems, change into the <filename>$JBOSS_HOME/bin/</filename> directory
and run the following command:
</para>
<para>
<screen>
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
00:07:31 UTC (rev 9819)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07
01:08:46 UTC (rev 9820)
@@ -11,52 +11,63 @@
<email>boleslaw dot dawidowicz at redhat dot com</email>
</author>
</chapterinfo>
- <title>Upgrading 2.4 - 2.6</title>
+ <title>Upgrading JBoss Portal 2.4 to 2.6</title>
+ <para>
<warning>
- Before performing any instructions or operations mentioned below remember to backup
your database content and
- the whole application server directory!
+ <para>
+ Before performing any instructions or operations in this chapter, back up your database
content and
+ the entire JBoss EAP or JBoss AS directory!
+ </para>
</warning>
+ </para>
<sect1 id="manual_migration">
- <title>Manual upgrade</title>
+ <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.
+ Although the database schema remains the same in JBoss Portal 2.6, there are
several differences that prevent simply deploying the latest version of JBoss Portal, when
using a database created for JBoss Portal 2.4. This chapter describes updating a JBoss
Portal 2.4 MySQL database for use with JBoss Portal 2.6.
</para>
<para>
- Upgrading procedure can be quite straightforward:
- <itemizedlist>
+ The upgrade procedure can be straightforward:
+ </para>
+ <para>
+ <orderedlist>
<listitem>
- Remove <emphasis
role="bold">$JBOSS_HOME/server/default/deploy/jboss-portal.sar</emphasis>
file.
+ <para>
+ If you are using the JBoss Portal binary, remove the
<filename>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/</filename>
directory. If JBoss Portal was built from source, remove the
<filename>$JBOSS_HOME/server/default/deploy/jboss-portal.sar</filename> file.
+ </para>
</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
+ <para>
+ Update the data in the JBoss Portal database, as described in <xref
linkend="upgrade_portal_database"/>.
+ </para>
</listitem>
<listitem>
- Deploy JBoss Portal 2.6
+ <para>
+ Deploy JBoss Portal 2.6.
+ </para>
</listitem>
- </itemizedlist>
+ </orderedlist>
</para>
<sect2>
- <title>Theme</title>
+ <title>Themes</title>
+ <para>
+ Themes in JBoss Portal 2.6 have changed since the Portal pages now contain additional
areas, such as the <guiicon>Login</guiicon>,
<guiicon>Admin</guiicon>, and <guiicon>Dashboard</guiicon> links,
on the top right-hand corner:
+ </para>
+ <para>
<mediaobject>
<imageobject>
<imagedata align="center" valign="middle"
fileref="images/migration/theme.png"/>
</imageobject>
</mediaobject>
+ </para>
<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" that is
present in 2.6, you shouldn't need to do anything. To update your custom themes
please
- refer to those bundled with portal as an example.
- </para>
- <note>If you stay with old theme files you may find JBP 2.6 unusable to
the point that you may not even be able to log in</note>
+ If you use a default theme that exists in JBoss Portal 2.6, such as renaissance, no
configuration should be necessary. Using old themes from JBoss Portal 2.4 may make JBoss
Portal 2.6 unusable, for example, not being able to log in. To update custom themes,
please refer to those bundled with JBoss Portal as an example.
+ </para>
</sect2>
- <sect2>
- <title>Database</title>
+ <sect2 id="upgrade_portal_database">
+ <title>Updating the Database</title>
<note>All things described in this section can be done using AdminPortlet.
Treat this directions more as guideline
if you need to automate migration for big portal deployment.</note>
<para>