Upgrade scenarios
Upgrade planning depends on the details of your existing installation. The starting version and platform choices all influence the upgrade path of your existing components.
Thoroughly review the planning and preparing information to understand the requirements for the upgrade process. You can determine what steps can be accomplished before you run the upgrade in order to ensure that system downtime is as short as possible.
Make sure that you designate a time for the upgrade process when no users will be accessing the system and no data will be modified.
To upgrade to Content Platform Engine V5.5.x, your system must be at V5.2.0 or later.
- If your system is at a version previous to V5.2.0, and you want to upgrade to V5.5.x, you must first upgrade your system to V5.2.0 or V5.2.1.
- If your system is at V5.2.x, you can directly upgrade to V5.5.8.
- If your system is at V5.5.x, you can directly upgrade to V5.5.8.
- Starting with V5.5.9, to upgrade to Content Platform Engine V5.5.9 or higher, your system must be at V5.5.2 or later. If your system is at a version prior to V5.5.2, and you want to upgrade to V5.5.9 and higher, you must first upgrade your system to at least V5.5.2 with a recommendation to upgrade to V5.5.8.
It is recommended to update your starting version to the most recent fix pack level before you begin the upgrade to V5.5.x.
- IBM® Content Navigator client files
- IBM Content Search Services
- IBM FileNet® Content Federation Services
- Case Analyzer can be upgraded at the same time if you need full access to case data after the upgrade. However, you can also upgrade this component later, such as the following weekend. All backlogged data will be processed after those upgrades are complete. See the Case Analyzer documentation for information on upgrading this component.
See the FileNet P8 Fix Pack Compatibility Matrices for a list of compatible component versions.