FileNet P8 Platform, Version 5.2.1              

Migration upgrade overview and roadmap

The goal of an upgrade that involves a migration to a new server instance is to minimize the unavailability of the production system.

Upgrading large FileNet® P8 systems involves significant work. The upgrade can be particularly challenging if you are changing the underlying platform of major system components, such as Content Platform Engine. Using this approach, you might install and configure a new server instance, such as for the application server or database server. The initial installation and configuration work can be done without impacting the production system.

At a high level, complete the upgrade migration procedures by using the following steps. Some steps are repeated for each major FileNet P8 component:

Migration roadmap
The migration roadmap lists the major steps that are required to upgrade FileNet P8 onto a different set of servers. Use this roadmap as a template for your own plan.
Table 1. Steps required to complete a migration upgrade.
  Migration task. Where to go for instructions.
Learn about upgrading FileNet P8. Upgrade planning considerations
Create a replica of your FileNet P8 environment. This scenario involves installing a new environment with the same servers and same version of FileNet P8 as your production system.
  • The GCD, object store, and Process Engine databases in the replica must be backups of the databases that are used on the production system. If the database accounts required by FileNet P8 are not included in the backup, create new instances of the accounts and use the same ID and password as on your production system.
  • The replica must use the same LDAP provider, LDAP configuration settings, and LDAP-based security accounts as the production system.
  • The replica application server can start with a new Configuration Manager profile or a copy of the production Configuration Manager profile. The installation instructions have sections for both these possibilities.
  • On the new Content Platform Engine computer, complete the installation preparation tasks for the Application Server administrator except for the tasks that are related to Application Engine or Workplace XT, as these components are not being upgraded now.
  • As part of an upgrade or if you are moving Workplace XT from 1.1.4 to 1.1.5, you might apply fix packs to Application Engine or Workplace XT because the older version is supported by older FileNet P8 releases.
  • If you still have a copy of the installation and upgrade worksheet for your production system, use it to help you install the replica system. Do not use this older version of the worksheet for upgrades.
Download the 5.2.1 installation and upgrade worksheet. Run the customization macro and select Upgrade for the Procedure Type option. Use the customized worksheet to enter values that are required for an upgrade. Using the installation and upgrade worksheet
Prepare the replica for upgrade. Follow the steps in the upgrade preparation instructions.

Depending on your replica system, not all upgrade preparation instructions apply to migration upgrades.

Performing the required upgrade preparation tasks
Upgrade the replica. Follow the steps in the 5.2.1 upgrade instructions. Upgrade instructions have separate sections for whether you are working with a new configuration profile in the replica or copied your former configuration profile into the replica. Upgrading and configuring FileNet P8 platform
When the replica system is tested and is ready for production, disconnect the former system and make the replica your new production system. Putting the upgraded FileNet P8 system into production
Tip: Because large-system upgrades involve interacting with many system components, a common approach is to go through a test upgrade run first. In this scenario, you complete the upgrade on a test system, and then discard the test system after you verify the integrity of the upgrade. You preserve the original production system in case the upgrade fails and to minimize outages to the production system. Running a test upgrade first takes more time than doing the upgrade immediately, but it can minimize risk. The test upgrade approach involves extra steps to completely replicate the production data. Replication is needed to simulate production activities by using a duplicated system.
You can practice the upgrade of your production environment by using either of these two methods:


Last updated: March 2016
p8ppu118.htm

© Copyright IBM Corporation 2013, 2016.