Skip to main content

Support & downloads  >  

Update Strategy for WebSphere Portal versions 6.0 and 6.1

 Preventive Service Planning
 
Abstract
This document describes the strategy for delivering maintenance updates for IBM® WebSphere® Portal versions 6.0 and 6.1 and provides tentative availability dates for future deliveries. By implementing a consistent and timely update strategy, customers can avoid rediscovering the problems we have already fixed and maintain a more stable and robust environment.
 
Content


Update Strategy Overview
Recommended Update Path
Tentative Release Schedule
Maintenance Planning
Delivering Updates
Related Information


Update Strategy Overview
WebSphere Portal Support is delivering this strategy to provide a clear upgrade path for our customers that reduces the risk of installing multiple individual interim fixes for their portal.

Since WebSphere Portal version 5.1.0 fix pack 2 (5.1.0.2), the Websphere Portal team has provided a comprehensive fix pack strategy which has carried forward into the current versions 6.0 and 6.1. The document below describes the key points of our fix pack strategy and gives an outlook of the timeline and planned software and hardware updates for the next planned fix pack, both subject to change based on our pre-release testing. Any deviations from the fix pack strategy will be noted in the documentation of the fix pack and on the Recommended fixes and updates for WebSphere Portal document.

The fix packs:
  • Provide a collection of APAR fixes that were available for previous WebSphere Portal fix packs
  • Include additional defect fixes found during the test of the fix pack
  • Include no major new features or behavioral changes
    • Rarely, minor new features may need to be included but by design will be documented and disabled by default
  • Are tested with updates to the underlying software and hardware to verify the function for our customers, when available.

WebSphere Portal will provide fix packs containing cumulative fixes that will be updated regularly. This provides a consistent maintenance approach you can follow as you manage your environment.

Installing preventative maintenance as soon as it becomes available will save you time. As long as you test appropriately, actively applying preventative maintenance can avoid problems that could result in a service call.

Back to Top

Recommended Update Path
  • Fresh installations should begin with the most recent refresh pack (if available).
  • Update to latest refresh pack and fix pack in order to proactively avoid problems already resolved within WebSphere Portal.
  • Plan appropriate testing prior to installing any WebSphere Portal update solution in production.
  • Testing or staging environments should closely match the production environment (same hardware, topology, operating system and software maintenance levels) to avoid unforeseen (and unwelcome) surprises.

Back to Top

Tentative Release Schedule

6.1:
Current Maintenance LevelNext Planned UpdateScheduled Release Date*
6.1.0.2: IBM WebSphere Portal version 6.1 fix pack 26.1.0.3: IBM WebSphere Portal version 6.1 fix pack 34Q2009 (fourth quarter, 2009)
*Note: any release date shown is subject to change until the actual update solution is delivered.


6.0:
Current Maintenance LevelNext Planned UpdateScheduled Release Date*
6.0.1.6: IBM WebSphere Portal version 6.0.1 fix pack 66.0.1.7: IBM WebSphere Portal version 6.0.1 fix pack 7to be determined at a later date
*Note: any release date shown is subject to change until the actual update solution is delivered.

Back to Top


Maintenance Planning
Choose the appropriate update solution and verify inclusion of needed individual fixes in the fix pack:
Prior to installing any WebSphere Portal update solution in production environments, appropriate testing should be done on a test system.

Back to Top

Delivering Updates
  • Fix pack deliveries will be scheduled (every 3 to 6 months). The date of the next planned fix pack will be published in Recommended fixes and updates for WebSphere Portal at least 30 days prior to availability, and in this document, above.
  • There is a single list of all internal defects and APARs fixed for each release (For example, V6.0), that is updated for each new fix pack.
  • Install on top of either a specific refresh pack with no fix pack applied or a refresh pack with any previous fix pack installed (for example, 6.0.1.4 could be applied to 6.0.0.1, 6.0.1.0 or 6.0.1.3).
  • Newer maintenance levels of underlying software are tested with the latest fix pack, but delivered separately. It is your responsibility to retrieve and install these updates, if necessary.

Refer to the document IBM WebSphere Portal interim fixes and fix pack file name changes for more information on the updates delivered. These updates are explained in the following table*:


Solutions

Characteristics of Each Solution

Release

  • A new WebSphere Portal that includes major new function, such as V6.0
  • This is a separate installation that can coexist with other WebSphere Portal releases
  • Full testing of all applications with new release is recommended
  • Requires migration to upgrade, distribution via Passport Advantage

Refresh pack

  • A package that may include new features and fixes, such as V6.0.1
  • Refresh packs are cumulative, so for example a V6.0.2 would include features and fixes contained in V6.0.1, as well as any subsequent fix packs and interim fixes published for V6.0.1
  • Refresh packs uninstall all fix packs and interim fixes previously applied to the release. So, it is necessary to check the list of delivered fixes to determine if an interim fix must be reinstalled.
  • Regression testing of critical functions with new refresh pack is strongly recommended to ensure your custom applications continue to function as expected.

Fix pack

  • This is the standard delivery for updates - it has been fully regression tested by IBM prior to release.
  • A fix pack is a cumulative package of only fixes, such as V6.1.0.1, unless otherwise noted
  • Fix packs install on top of a specific refresh pack, such as applying V6.1.0.1 to V6.1.0.0
  • Fix packs also install on top of a previous fix pack, such as applying V6.1.0.3 to V6.1.0.1
  • Fix packs are cumulative, so V6.1.0.3 includes all fixes in V6.1.0.1
  • Fix packs uninstall all interim fixes applied to the release since the last refresh pack or fix pack was installed. Therefore, it is necessary to check the list of delivered fixes to determine if an interim fix needs to be reinstalled.
  • Brief testing of critical functions with the new fix pack is recommended to ensure your custom applications continue to function as expected.

Fix

  • A single published emergency fix, such as PK89999
  • WebSphere Portal can only guarantee to provide fixes on the latest two fix pack levels of a release. A customer could be required to upgrade to the one of the two latest fixpacks before being able to install a fix.
  • A fix is an interim fix or test fix that resolves one or more product defects.
  • A fix can be applied to a release, refresh pack,or fix pack where applicable
  • Interim fixes are created when a stand-alone fix is required between fix packs. They are validated by at least one customer and verified by IBM before publishing. Test fixes are not generally released but might be provided by IBM support during the course of a service call (PMR).
  • It is recommended that you test functions affected by the WebSphere component fixed
  • Reference the Recommended fixes and updates for WebSphere Portal page for currently available fixes. When urgent, the fix will also be highlighted on the Support page.
*Some of the service releases mentioned in the above table are for example purposes only and may not reflect any specific planned releases or updates.

Back to Top

Related Information

Back to Top
 
Related information
Update strategy for Lotus WCM
 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Organizational Productivity, Portals & Collaboration
 Portals
 WebSphere Portal
 General
 Operating system(s):
  AIX, HP-UX, Linux, Solaris, Windows, i5/OS
 Software version:
  6.0, 6.1
 Software edition:
  Enable, Extend, Server
 Reference #:
  1248245
 IBM Group:
 Software Group
 Modified date:
 2009-07-02

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.