Search
Recent articles
Tag cloud
- admin
- ajax
- amazonec2
- articolo
- as400
- beta
- bleedyellow
- blog
- blogroll
- browser
- clienti
- cloud_computing
- collaboration
- community
- composite_apps
- connections
- daos
- db2
- development
- diary
- domino
- dominodesigner
- dominopoint
- dwa
- eclipse
- english
- expeditor
- hcldx
- ideajam
- ilug2007
- ilug2008
- Java
- linux
- lotus
- lotusknows
- lotusnotes
- lotusphere
- lotussymphony
- lotus_connections
- lotus_foundations
- ls2009
- marketing
- misc
- mytechnotes
- nd85
- notes
- notes_domino
- openntf
- partnerworld
- personal
- perspectives
- photo
- poll
- portal
- portlet
- presentation
- productivity
- quickr
- reference
- sales
- sametime
- secondlife
- security
- sntt
- symphony
- technology
- upgrade beta socialedition domino notes
- voltmx
- webdesign
- websphere
- websphere_portal
- widgets
Archives
- July 2024 (1)
- December 2012 (1)
- March 2010 (1)
- January 2010 (1)
- November 2009 (1)
- August 2009 (2)
- March 2009 (1)
- February 2009 (4)
- January 2009 (4)
- December 2008 (3)
- November 2008 (1)
- October 2008 (2)
- September 2008 (2)
- August 2008 (5)
- July 2008 (6)
- June 2008 (9)
- May 2008 (4)
- April 2008 (2)
- March 2008 (10)
- February 2008 (1)
- January 2008 (4)
- December 2007 (1)
- November 2007 (6)
- October 2007 (3)
- September 2007 (14)
- August 2007 (11)
- July 2007 (5)
- June 2007 (6)
- May 2007 (6)
- April 2007 (4)
- March 2007 (3)
- February 2007 (4)
- January 2007 (5)
- December 2006 (2)
- November 2006 (7)
- October 2006 (6)
Last week the first fixpack for WebSphere Portal 6.1 has been released.
Among the other things the new fixpack integrates all the updates that were made available to fix browser issues with the new Client Side Aggregation feature that promises more dynamics portals (ajax everywhere).
Also a number of fixes have been integrated concerning the WCM (Web Content Manager) component.
If you're going to update your portal to 6.1.0.1 (wathever version and topology, standalone or clustered) keep in mind these few tips:
- Portal 6.1 ships with WAS 6.1.0.15 ND, the Fixpack 1 for WPS requires WAS to be updated to WAS 6.1.0.17 (minimum supported level), installing the portal fixpack without updating WAS may end with a broken system. (Hint: BACKUP, BACKUP, BACKUP)
- Consider adding CopyWpsEarScreens=true to your wkplc.properties , this will ensure all jsps will be updated with new "screens" in the portal theme ear (wps.ear). Remember that your changes to the wps.ear application will need to be re-applied after the upgrade process (Hint: save them before upgrading or use the new feature for deploying themes as separate EAR/WAR applications).
I'm now looking for the real improvements that this fixpack brings in. For sure it fixed all the issues with browsers (Web2.0 theme, side palette scolling etc)
Now it's time to start your upgrade, go here for all the pointer you need (also I suggest downloading fixes trough IBM Lotus FixCentral)
Note:
During my tests it appears that themes deployed as standalone applications don't work well with the Web Application Integrator feature. I'm still looking into this issue.
Comments (2)
Daniele Vistalli December 6th, 2008 19:50:29