The Essential Guide to Upgrading Fix Packs on IBM WebSphere Application Server 8.5


Keeping your IBM WebSphere environment up-to-date with the latest fix packs is one of the most critical responsibilities for any WebSphere administrator. New fix packs contain security patches, bug fixes, performance enhancements and new features that can greatly improve the stability, security and capability of your WebSphere platform.

However, upgrading fix packs requires careful planning and execution to avoid downtime or issues. In this comprehensive 3000+ word guide, I‘ll provide you with everything you need to know to successfully upgrade fix packs on WebSphere Application Server 8.5. You‘ll learn:

• The benefits of upgrading to the latest fix packs
• Step-by-step instructions for downloading and installing fixes
• How to verify the upgrade and examine the version history
• Expert tips and best practices for fix pack upgrades
• And much more!

Whether you‘re looking to enhance security, fix bugs or get new features, upgrading fix packs is essential to keeping your WebSphere environment running optimally. So let‘s get started!

Why Upgrading Fix Packs is Important

Before we dig into the how-to, let me quickly explain what makes fixing packs so important:

Security updates – Fix packs contain critical security updates that address vulnerabilities in WebSphere. Keeping up-to-date ensures you have the latest protections.

Bug and issue resolution – IBM uses fix packs to address bugs, defects and other issues in WebSphere. Upgrading can resolve instability and problems.

Performance improvements – Upgrades often include performance enhancements to improve throughput and responsiveness.

New features – Some fix packs introduce new capabilities and APIs for developers.

Support requirements – IBM requires the latest fix packs for continued technical support on older versions.

Industry best practices – Following ITIL and ITSM best practices recommends always staying current with vendor patches and upgrades.

So in summary, upgrading provides better security, stability, performance and support for your WebSphere investment. Keep reading as I provide a full overview and walkthrough of the upgrade process.

Prerequisites and Planning

Before you begin, make sure your environment meets the prerequisites:

• Existing WebSphere 8.5.5+ environment
• Backup of configurations, profiles, nodes etc.
• Sufficient free disk space for the install
• Administrative access and permissions
• IBM Installation Manager installed/configured
• Maintenance window scheduled

I also strongly recommend stopping all non-essential servers, deployments and traffic to the WebSphere farm during the upgrade. This prevents any potential issues and minimizes downtime.

You‘ll also want to carefully schedule a maintenance window and notify any stakeholders who may be impacted.

Finally, closely review the IBM fix pack release notes for the version you plan to upgrade. This will highlight any breaking changes, prerequisites and special upgrade considerations.

With those housekeeping items addressed, let‘s walk through the full fix pack upgrade process step-by-step:

Step 1: Download the Fix Pack from IBM

First, you‘ll need to get the latest fix pack files from the IBM support site:

1. Open your browser and go to IBM Fix Central.

2. Select the fix pack zip file that matches your WebSphere platform and architecture. For example, if you have WAS 8.5.5 on Linux x86-64, choose the "Distributed" package for that platform.

3. The fix pack will be provided in two separate zip files for download. Download both Part 1 and Part 2 of the fix pack.

4. Login with your IBM account and click Continue to download each part of the fix pack.

5. Transfer and save both zip files to the WebSphere server.

Once complete, you should have both fix pack zip files available on your WebSphere server ready for installation. The key files you need will be extracted in the next step.

Step 2: Extract the Fix Pack Contents

Now we need to unpack and extract the fix pack archives:

1. Using the command line or your preferred zip utility, extract the contents of part1.zip.

2. Extract the contents of part2.zip.

This will create a directory structure containing all the fix pack artifacts:

fixpack
├── atoc
├── files
├── Offerings
├── plugins
├── repository.config
├── repository.xml
├── update_*.xml 

The key files and folders:

• repository.config – Repository configuration
• update_*.xml – Package update metadata
• files/ – Binaries, libraries, resources
• plugins/ – Plug-ins
• Offerings/ – Installation offerings
• repository.xml – Repository index

With the fix pack contents extracted, we‘re ready to feed it into the IBM Installation Manager to perform the upgrade.

Step 3: Using IBM Installation Manager to Apply the Fix Pack

The IBM Installation Manager is the officially supported way to upgrade WebSphere fix packs:

1. Launch the Installation Manager application and go to File > Preferences.

2. Click Add Repository and browse to select the extracted repository.config file. Click OK.

3. You should receive confirmation that the fix pack version is recognized from the repository.

4. Accept the license agreement and click Next.

5. On the feature selection screen, choose your desired options or simply click Next to upgrade everything.

6. Review the summary page and click Update to begin the upgrade!

7. Wait for the update to complete. Once finished, you‘ll receive a success message.

And that‘s it! IBM Installation Manager has applied the fix pack upgrade to your WebSphere instance. Next let‘s look at how to validate everything completed correctly.

Step 4: Verifying the Fix Pack Installation

After finishing the upgrade process, we need to double check that the fix pack installed properly.

There are two handy scripts that can provide version information:

versionInfo.sh

This script prints details on the current WebSphere installation:

$WAS_HOME/bin/versionInfo.sh 

WVER0010I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.48, dated 2/8/12  
--------------------------------------------------------------------------------
IBM WebSphere Product Installation Status Report
--------------------------------------------------------------------------------

Report at date and time March 1, 2023 10:15:44 AM EST

Installation                                                     
--------------------------------------------------------------------------------
Product Directory      /opt/IBM/WebSphere/AppServer
Version                8.5.5.6 
[...]

Look for the updated 8.5.5.6 version number to confirm the fix pack upgrade.

historyInfo.sh

This script provides the historical record of upgrades:

$WAS_HOME/bin/historyInfo.sh

WVER0210I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved. 
WVER0212I: HistoryInfo Reporter Version 1.7.1.28, Dated 10/18/11
--------------------------------------------------------------------------------
IBM WebSphere Product History Report
--------------------------------------------------------------------------------

Report at date and time March 1, 2023 10:22:11 AM EST

Installation Event
--------------------------------------------------------------------------------
Version         8.5.5.0
Timestamp       2015-08-12  
[...] 

Installation Event
--------------------------------------------------------------------------------
Version         8.5.5.6  
Timestamp       2015-08-31
[...]

The log shows the fix pack upgrade from 8.5.5.0 to 8.5.5.6.

If both scripts show the updated fix pack release, then you can confirm a successful upgrade!

Best Practices and Tips for Fix Pack Upgrades

Now that we‘ve covered the end-to-end fix pack upgrade process, I wanted to share some pro tips and best practices I‘ve learned over the years:

• Always have a rollback plan in case issues arise with the new fix pack.

• Closely monitor the environment after upgrading and watch for any abnormalities.

• Update your staging/test environments first before upgrading production.

• Review release notes and pause if there are breaking changes or special instructions.

• Upgrade can take 1-2 hours based on environment size, so schedule ample downtime.

• Automate backups before and after upgrading as a precaution.

• Check interoperability and support if upgrading multiple IBM products.

• Consider staggering upgrades across a cluster rather than simultaneously.

• Monitor server logs during and after upgrading for any concerning warnings.

• If possible, clone production to a mirrored "gold" image as added insurance.

And remember upgrading fix packs provides tremendous security, stability and support benefits for your WebSphere deployment. Staying current is a best practice, so use this guide to plan and execute smooth, successful fix pack upgrades.

Let me know if you have any other questions! I‘m always happy to help fellow WebSphere admins master this critical skill.