Product Documentation
Abstract
Announcing a strategy for delivering Fix Packs for IBM WebSphere Application Server 8.5 and 9.0 releases. Fix Packs are the standard maintenance delivery vehicle.
Content
| Update strategy overview |
WebSphere Application Server Support is delivering this strategy to provide a clear update path which is easier to maintain than managing multiple, individual Application Server fixes.
In response to requests for published collections of fixes that are:
- Delivered in a timely manner.
- Tested together.
Installing preventive maintenance as soon as it becomes available will save you time. As long as you test appropriately, actively applying preventive maintenance can avoid problems that could result in a service call.
For further details on the Lifecycle of WebSphere Application Server, see https://www.ibm.com/support/pages/node/869800
Unless specified otherwise, the policy documented here applies to IBM HTTP Server as well.
| Update Deliverables |
WebSphere Application Server traditional provides updates as a Maintenance Delivery Vehicle (MDV) which uses a V.R.M.F. numbering scheme:
|
V
|
Version Number = (8, 9)
|
|
R
|
Release Number = 0
|
|
M
|
Modification Number
|
|
F
|
Fix Pack Number
|
Based on this numbering scheme 2 types of MDV may be provided for WebSphere Application Server traditional:
- A Fix Pack which comprises a cumulative package of fixes and may further include a small number of new features.
- Normally, cumulative fix packs increment the "fix pack number"
- Some fix packs with significant new function will instead increase the modification level, for example the fix pack that followed 9.0.0.11 is 9.0.5.0.
- In this case all future fix packs will be based on the new modification level, there is no separate service stream.
- An individual (interim) fix which comprises one or a small number of fixes. Fixes do not change the V.R.M.F number.
- An interim fix is a downloadable, installable package produced to resolve a specific Authorized Program Analysis Report (APAR) or known issue. The identifier (such as PH12345) of the APAR resolved by the interim fix is incorporated into the filename.
- Each interim fix can be installed on 1 or more base fix pack levels. The lowest fix pack level is incorporated into the filename, and the highest fix pack level is embedded in fix metadata
- Multiple interim fixes may be created to correct the same APAR, to apply to multiple installed fix pack levels.
- An interim fix may supersede 1 or more previously published interim fixes. Such an interim fix may be installed either on top of the superseded fix or as an alternative to the superseded fix.
- The download documents as well as the embedded fix metadata produced for the new interim fix will list the APARS listed as resolved in the superseded fixes.
|
Y
|
Year = last 2 digits
|
|
R
|
Release Number = 0
|
|
M
|
Modification Number
|
|
F
|
Fix Pack Number = Fix Pack Number during the year
|
Based on this numbering scheme 2 types of MDV may be provided for WebSphere Application Server Liberty:
- A Fix Pack which comprises a cumulative package of fixes and may further include a small number of new features. Each subsequent quarterly delivered Fix Pack increases the Fix Pack number while Y.R.M remain the same.
- A individual (interim) fix which comprises one or a small number of fixes. Fixes do not change the Y.R.M.F number.
For more details on WebSphere Application Server Liberty continuous fix pack delivery please refer to the Knowledge Center
Fix Pack.
Fix Pack are currently delivered approximately every 3 months for 9.0 and every 6 months for 8.5. The following document provides estimated dates for the next fix pack, at least 30 days before its release: Recommended fixes for WebSphere Application Server
WebSphere Liberty fix packs are currently delivered approximately every 4 weeks.
WebSphere Application Server Liberty executable JAR file Fix Packs are a complete replacement. IBM recommends customers to install each new Fix Pack in a separate location from the previous install and configure the new install to use the existing applications and configuration. The previous install then provides a suitable back-up should problems be found with the new install.
When a Fix Pack is published an IBM Support page is created with details of the Fix Pack including download and install instructions and a list of problems fixed. This page may be updated with new information related to the Fix Pack when available, for example details of known new problems introduced.
IBM recommends customers to install the latest available Fix Pack level.
WebSphere Application Server Liberty executable JAR file Fix Packs are a complete replacement. IBM recommends customers to install each new Fix Pack in a separate location from the previous install and configure the new install to use the existing applications and configuration. The previous install then provides a suitable back-up should problems be found with the new install.
When a Fix Pack is published an IBM Support page is created with details of the Fix Pack including download and install instructions and a list of problems fixed. This page may be updated with new information related to the Fix Pack when available, for example details of known new problems introduced.
IBM recommends customers to install the latest available Fix Pack level.
- Customers should review details of known problems introduced to determine impact on customer function.
Notes:
- The WebSphere offerings included in each Fix Pack are tested together by IBM.
- Customer testing of critical functions after install of a Fix Pack is recommended before updating a production environment.
- In some cases, a Fix Pack might not be delivered for every offering at each Fix Pack delivery.
Interim Fixes
An interim may be provided upon request and at IBM's discretion, as a way to provide a fix in advance of the fixes availability in a Fix Pack, if all of the following conditions apply
- The fix resolves a problem that impacts ongoing production or a committed production start date.
- There is no acceptable workaround for the problem.
- The fix applies to one or more sequential Fix Pack levels that have been generally available for no more than two years.
- The fix can be provided without significantly impacting the provision of support or other service activities in a timely manner.
If a request for an interim fix meets the conditions above, some circumstances that affect IBM's discretion include:
- Whether the fix has already been incorporated into released fix packs, and when they were first released.
- Whether the interim fix is already available for more recent fix packs
- If the fix or interim fix is already available, wow much additional content the requesting customer would pick up as a result of first upgrading to the prerequisite fix pack of existing fixes.
- The reason for the inability or reluctance to update to the prerequisite fix pack of existing fixes.
- The risk and effort implied by the scope of the changes in the interim fix
- The risk and effort implied by the relationship between the fix and other recent fixes
Fixes may be provided in one of two following forms:
- Interim fix:
- Interim fixes are regression tested by IBM for the affected function and may be used to update a production environment.
- It is recommended that customers test functions affected by the fix before updating a production environment.
- It is recommended that customers move to a Fix Pack which includes the interim fix when available.
- Interim fixes may optionally be published. A published fix generally has the following additional properties:
- A published interim fix is available to all customers and supports all relevant IBM WebSphere Application Server offerings and all relevant supported operating systems (including z/OS). Depending on the severity or urgency, the published fix may also be accompanied by a flash.
- Published fixes generally target the two most recent Fix Packs, when applicable, for each affected release.
- Published fixes may be marked as "recommended" on Fix Central. This is primarily used to facilitate search filtering within the Fix Central application.
- If a fix is superseded by a later fix, the "recommended" flag may be removed from the earlier fix.
- Separate from "recommended" flag in Fix Central, interim fixes packaged packaged with IBM Installation Manager contain metadata describing whether or not the fix is recommended. This information is used to allow recommended fixes to be presented differently in the user interface or to be selected for installation from the command line as a group. This flag embedded in the fix does not change over time.
- IBM highly recommends all affected customers to install the relevant interim fix.
- Interim fixes for Security/Integrity issues generally have the following additional properties:
- They are proactively created and published for the two most recent Fix Packs for all in-service affected releases.
- They are accompanied by a Security Bulletin
- Interim fixes for IBM HTTP Server archive installations (non IBM Installation Manager) and IBM HTTP Server for z/OS installed via SMP/E have the following unique properties:
- Interim fixes are cumulative, full installations that can also be used to upgrade existing installations of any previous fix pack levels.
- Interim fixes "based on" older fix packs will not be provided.
- The included code level supersedes all previously published interim fixes
- The servers version is nominally the current latest fixpack plus the last APAR in the interim fix (e.g. 9.0.5.10-PH12345)
- Interim fixes are cumulative, full installations that can also be used to upgrade existing installations of any previous fix pack levels.
- Test fix
- A test fix is used to verify that a fix addresses a reported product defect.
- Is not intended to be used to update a production environment.
- For some problems, IBM will not include a fix in a Fix pack until the customer has confirmed that the test fix addresses the problem.
Note: A fix to a JAR file of WebSphere Application Server traditional will update one or more class files in the JAR file whereas a fix to a JAR file of WebSphere Application Server Liberty will effectively replace the JAR file. As a result, to prevent a later fix overwriting some or all of a previous fix, WebSphere Application Server Liberty fixes are likely to fix more product defects than a WebSphere Application Server traditional fix.
| Update Deliverable Availability and Install |
IBM Installation Manager installable update deliverables
IBM Installation Manager installable update deliverables must be installed using IBM Installation Manager for WebSphere Application Server V9.0.
- Installing interim fixes and fix packs on distributed and IBM i operating systems.
- Installing interim fixes and fix packs on z/OS operating systems.
IBM Installation Manager uses product repositories to install products and maintenance. The following repository options are provided for WebSphere Application Server V9.0:
- A current, IBM-hosted web repository.
- A local repository created from the web repository using Package Utility.
- Download and unzip of one or more zip files from Fix Central.
IBM Installation Manager interim fixes will be removed, and may be re-applied, as part of a Fix Pack install. Interim fixes are re-applied if they also apply to the new Fix pack level installed. As a result some interim fixes may not be re-applied and it is therefore necessary to check the list of delivered fixes to determine if a removed interim fix is not included in the Fix Pack.
Executable JAR file Install deliverables
WebSphere Liberty executable JAR file update deliverables are installed by executing the JAR and are published under entitlement in Fix Central.
Executable JAR file Interim fixes will not be re-installed when a new Fix pack is installed. It is therefore necessary to check the list of delivered fixes to determine if a required interim fix is not included in the Fix Pack.
- Use the productInfo command to compare a previous install and a new install to determine if an interim fix installed in the previous install is included in the new install.
Update Strategy for Features Downloaded From IBM WebSphere Liberty Repository
IBM WebSphere Liberty Repository enables customers to select which of WebSphere Liberty features to install in more granular manner.
Update Strategy for Features Downloaded From IBM WebSphere Liberty Repository follows the same rules and schedules as WebSphere Liberty Update Strategy.
IBM WebSphere Liberty Repository content is refreshed with updates to existing features and with addition of any new features at the time of release of the Fix Pack of WebSphere Liberty.
Depending on install path chosen (Archive Install or Install Manager), customer should follow respective install manual for applying Interim fixes and/or Fix Packs.
| Maintenance planning |
Choose the appropriate update solution and verify inclusion of needed individual fixes in the Fix Pack:
- Review Recommended fixes and the Fix list for each release to help you plan updates.
- In order to ensure quality Fix Packs, individual fixes that become available late in the development cycle may not be included in a Fix Pack.
- The historyInfo command lists the history of installed and uninstalled fix packs and interim fixes .
- For WebSphere Liberty the productInfo utility provides a list of interim fixes installed.
Before installing any WebSphere Application Server solution in production, appropriate testing should be done on a test system.
Update a Fix Pack from any previous Fix Pack or WebSphere Application server V9.0 base release of a WebSphere Application Server component. For example update directly to Fix Pack 9.0.0.3 from 9.0.0.0, 9.0.0.1 or 9.0.0.2.
Update a Fix Pack from any previous Fix Pack or WebSphere Application server V9.0 base release of a WebSphere Application Server component. For example update directly to Fix Pack 9.0.0.3 from 9.0.0.0, 9.0.0.1 or 9.0.0.2.
| Recommended update path |
- Remaining on an early Fix Pack level (two or more Fix Packs behind the latest) with interim fixes applied puts IBM's ability to deliver additional interim fixes at risk. Situations may arise where IBM will not be able to safely deliver additional interim fixes on an early level. If a customer has interim fixes applied, they should plan on moving to a Fix Pack level which contains those fixes.
- Update to the latest Fix Pack for cumulative fixes in order to avoid problems already resolved within WebSphere Application Server.
- Update to the latest Fix Pack only when there is time in the development schedule for a full regression test of your application.
- Plan appropriate testing prior to installing any WebSphere Application Server solution in production.
| Related Information |
- Recommended updates for WebSphere Application Server
- IBM Installation Manager
- Update Strategy for WebSphere Application server V8.5 releases
- WebSphere Liberty Single Stream Continuous Delivery
- Lifecycle Policy: WebSphere Application Server
[{"Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdNPAA0","label":"1. IBM Support Praxis"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
10 July 2024
UID
swg27048352