IBM FileNet P8 5.2.1 on Windows 2012 to IBM FileNet 5.5.9 on Windows 2019/2022

An out-place upgrade involves transitioning to a new version of the software on a separate set of hardware or infrastructure. This method minimizes downtime, allowing for meticulous testing before users are shifted to the upgraded system. For FileNet P8, an out-place upgrade provides a systematic and controlled approach to migrate from an older version to a more advanced one.

If we want to Upgrade 5.2.1 to 5.5.9, we have to follow some Rule

  • First we have to upgrade FileNet 5.2.1 to 5.5.2 the we can upgrade to 5.5.9.
  • Apply 5.2.1 FixPack 7 before upgrade to 5.5.X version
  • 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.

Project Scope

The proposed project will involve the following phases

  • Planning and Preparation: This phase will involve assessing the current system, identifying migration goals, and
    creating a detailed project plan.
  • Testing and Validation: This phase will involve conducting unit testing, integration testing, and user acceptance testing
    to ensure the migrated system is functioning correctly.
  • Deployment and Cutover:This phase will involve deploying the migrated system to production and cutover from the old
    system to the new system. 

Objectives

  • Platform Migration:(Out of Scope) Transition from Windows Server 2012 to either Windows Server 2019 or 2022, ensuring compatibility and optimal performance. 
  • Upgrade IBM FileNet Version:(Include all FileNet Component)Upgrade from FileNet P8 5.2.1 to 5.5.9 on Windows Server 2019/2022. 
  • Database Upgrade:(Out of Scope) Upgrade the underlying database, ensuring it is compatible with the new FileNet version. 
  • Configuration Optimization: Review and optimize system configurations to leverage new features and enhance overall performance.
  • Backup and Disaster Recovery:(Out of Scope) Implement robust backup and disaster recovery procedures to safeguard data during the migration process. 
  • User Training: Provide training sessions for end-users and IT staff to familiarize them with the new features and
    functionalities of IBM FileNet 5.5.9.

Share:

This migration proposal outlines a systematic approach to upgrade IBM FileNet P8 from version 5.2.1 to 5.5.9 on
Windows Server 2019/2022. The proposed plan aims to minimize downtime, ensure data integrity, and optimize the overall performance of the FileNet environment. We look forward to the opportunity to discuss and implement this upgrade to enhance the capabilities of your FileNet system.

Scope of Work:

Phase 1:

Install Prerequisites:

Set the stage by installing and configuring necessary software prerequisites for IBM FileNet 5.5.9 on the target servers:

Ensure that operating system updates and patches are applied.
Install and configure Java Runtime Environment (JRE) and other required components System Compatibility Check
Ensure that all hardware, software, and third-party components are compatible with IBM FileNet 5.5.9 and the chosen
Windows Server version.

Pre-upgrade Checklist:

Identify Target Components: Determine which specific FileNet P8 components require upgrading. 

Version Compatibility: Ensure the target components are compatible with the existing versions and operating systems. Refer to the IBM FileNet Compatibility Matrix for detailed information.

Software Prerequisites: Install and configure any necessary software prerequisites for the target component upgrade, such as Java Runtime Environment (JRE) or database software updates. 

Download Upgrade Packages: Download the appropriate upgrade packages for each target component from the IBM FileNet P8 Downloads page.

Phase 2:

Upgrade Process(FileNet):

Content Process Engine (CPE):

  • Download the upgrade installer for CPE 5.5.9 from the IBM Support Portal.
  • Close all FileNet P8 applications and services.
  • Run the upgrade wizard following the instructions provided in the IBM documentation for CPE 5.5.9
    upgrade.
  • Follow the on-screen instructions to upgrade the Content Process Engine.
  • Selecting the source and target versions.
  • Specifying upgrade options and customizations.
  • Validating pre-requisite checks.
  • Initiating the upgrade process.
  • Monitoring the upgrade progress.
  • After the upgrade finishes successfully, update configuration files and settings as necessary.
  • Apply fix packs and interim fixes recommended by IBM for the new CPE version.

Workplace XT (Out of Support):

  • Stop Workplace XT services.
  • Backup the Workplace XT configuration files.
  • Install the Workplace XT upgrade package.
  • Configure the upgraded Workplace XT files.
  • Start the Workplace XT services.

IBM Content Navigator:

  • Stop IBM Content Navigator services.
  • Backup the IBM Content Navigator configuration files.
  • Install the IBM Content Navigator upgrade package.
  • Configure the upgraded IBM Content Navigator files.
  • Start the IBM Content Navigator services.

Take WAS Backup:

Here is the easiest way to make backup of WebSphere Application Server

  • First go to WebSphere Application Server location
          e.g. C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>\ 
  • And run the Backup Command with File Name
         “backupConfig.bat Filename –nostop”

Easiest Way to Recover WebSphere Application Server Backup

  • First go to WebSphere Application Server location
          e.g. C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>\
  • And run the Restore Command with File Name
         “RestoreConfig.bat Filename”.
  • All server on node are stopped before configuration restoration can take place , so that
    Node synchronization does not occur during the Restoration.

Phase 3:

Post-Migration Validation

  • Testing and Quality Assurance: Conduct thorough testing to validate the functionality and performance of the upgraded FileNet environment.
  • User Acceptance Testing (UAT):  Engage end-users in UAT to ensure that their workflows and applications function as expected.

Phase 4:

Documentation and Training

  • Documentation: Create comprehensive documentation detailing the new environment, configurations, and procedures. Update system documentation to reflect changes made during the upgrade. Maintain a detailed record of the migration process for future reference.
  • Training Sessions:
    Provide training sessions for end-users and IT staff to familiarize them with the upgraded FileNet system.

This migration proposal outlines a systematic approach to upgrade IBM FileNet P8 from version 5.2.1 to 5.5.9 on
Windows Server 2019/2022. The proposed plan aims to minimize downtime, ensure data integrity, and optimize the
overall performance of the FileNet environment. We look forward to the opportunity to discuss and implement this
upgrade to enhance the capabilities of your FileNet system.