Table of Contents
Advertisement
MDV
Fix
This section describes two different approaches to help you avoid problems (maintenance)
and correct or prevent problems (fix) in your environment.
Overview of the maintenance strategy
Among the most beneficial actions an administrator can perform on a portal is to keep it up to
date with regard to service levels. By keeping the environment current, the likelihood of
encountering a problem already corrected ("rediscovery") is very rare, and allows the
environment to take advantage of performance and stability improvements integrated into
later service releases. Long gone are the days of installing some middleware on a server and
sticking it in a closet with the expectation that it will not need any additional attention. Today's
environments can include a multitude of client and server platforms, dynamic content creation
and presentation, and challenges to keep pace with changes in numerous industry standards.
The TechNote "Update Strategy for WebSphere Portal versions 5.1 and 6.0" (#1248245)
describes the current philosophy of the development and support teams. In short, we deliver
Fix Packs on a periodic schedule of release every three to six months. This TechNote can be
found at:
http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg21248245
Guidance is provided from IBM support showing the current list of recommendations for
WebSphere Portal in the TechNote "Recommended fixes and updates for WebSphere Portal"
(#7007603). Customers are recommended to use this as a foundation for understanding
which service release level to use in their environment, and which Interim Fixes are
considered to be critical in nature, to prevent rediscovering problems already corrected. This
TechNote can be found at:
http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg27007603
Installing maintenance on a clustered environment is different from installing it on a
stand-alone node. Be sure to read and understand the installation instructions in the
WebSphere Portal V6.0 Information Center regarding the installation of updates in a clustered
Appendix B. Maintenance: Fix strategy, backup strategy, and migration strategy
Characteristics
A single published emergency fix, such as
PK29999.
A fix is an Interim Fix, test fix or cumulative
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).
We recommend that you test functions
affected by the fixed WebSphere component.
Reference the Recommended fixes and
updates for WebSphere Portal page for
currently available fixes at:
http://www-1.ibm.com/support/docview.ws
s?rs=688&uid=swg27007603. When urgent,
the fix will also be highlighted on the Support
page.
213
Advertisement
Table of Contents
Troubleshooting
