From portal-commits at lists.jboss.org Wed Feb 6 20:08:47 2008 Content-Type: multipart/mixed; boundary="===============8808781323439124318==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r9820 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules. Date: Wed, 06 Feb 2008 20:08:47 -0500 Message-ID: --===============8808781323439124318== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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/configur= ation.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migratio= n.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/c= onfiguration.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/configu= ration.xml 2008-02-07 00:07:31 UTC (rev 9819) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configu= ration.xml 2008-02-07 01:08:46 UTC (rev 9820) @@ -262,10 +262,10 @@ Disabling Dynamic Proxy Un-wrapping - JBoss Portal uses the JBoss Microkernel for the service infras= tructure. The JBoss Microkernel provides injection of services into other s= ervices, 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 i= s highly optimized; however, when it is used with Java 5, a noticeable bott= leneck appears due to the fact that the implementation of the JMX API class= es, javax.management.*, provided by the Java Platform,= performs synchronization. This does not occur under JDK 1.4 since those cl= asses are implemented by JBoss MX. + JBoss Portal uses the JBoss Microkernel for the service infras= tructure. The JBoss Microkernel provides injection of services into other s= ervices, 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 i= s highly optimized; however, when it is used with Java 5, a noticeable bott= leneck occurs due to the fact that the implementation of the JMX API classe= s, javax.management.*, provided by the Java Platform, = perform synchronization. This does not occur under JDK 1.4, since those cla= sses are implemented by JBoss MX. - JBoss Portal services use a special kind of Model MBean called JBossServiceModelMBean, which allows the un-wrapping of inject= ed 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 enable= d, but it is possible to disable. To do this on Linux systems, change into = the $JBOSS_HOME/bin/ directory and run the following c= ommand: + JBoss Portal services use a special kind of Model MBean called JBossServiceModelMBean, which allows the un-wrapping of inject= ed dynamic proxies, and replaces them with plain old java object (POJO) ser= vices. This removes the bottleneck when using Java 5, and also provides a p= erformance 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 $JBOSS_HOME/bin/ directory and run the following command: 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 00:07:31 UTC (rev 9819) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migrati= on.xml 2008-02-07 01:08:46 UTC (rev 9820) @@ -11,52 +11,63 @@ boleslaw dot dawidowicz at redhat dot com - Upgrading 2.4 - 2.6 + Upgrading JBoss Portal 2.4 to 2.6 + - Before performing any instructions or operations mentioned below rem= ember to backup your database content and - the whole application server directory! + + Before performing any instructions or operations in this chapter, back u= p your database content and + the entire JBoss EAP or JBoss AS directory! + + - Manual upgrade + Manual Upgrade - Although database schema remains the same in JBoss Portal 2.6 the= re 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 ve= rsion 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 w= ith JBoss Portal 2.6. - Upgrading procedure can be quite straightforward: - + The upgrade procedure can be straightforward: + + + - Remove $JBOSS_HOME/server/default/d= eploy/jboss-portal.sar file. + + If you are using the JBoss Portal binary, remove the $JBOSS_H= OME/server/default/deploy/jboss-portal.sar/ directory. If JBoss = Portal was built from source, remove the $JBOSS_HOME/server/defau= lt/deploy/jboss-portal.sar file. + - Update data in portal database like described in following = sections of this chapter + + Update the data in the JBoss Portal database, as described in . + - Deploy JBoss Portal 2.6 + + Deploy JBoss Portal 2.6. + - + - Theme + Themes + + Themes in JBoss Portal 2.6 have changed since the Portal pages now cont= ain additional areas, such as the Login, Admin<= /guiicon>, and Dashboard links, on the top right-hand co= rner: + + + - Themes in 2.6 version changed as now they - contain additional areas - the best example is upper right cor= ner 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. - - If you stay with old theme files you may find JBP 2.6 unusa= ble to the point that you may not even be able to log in + If you use a default theme that exists in JBoss Portal 2.6, such as ren= aissance, 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 JBo= ss Portal as an example. + - - Database + + Updating the Database 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. --===============8808781323439124318==--