FileNet P8 Platform, Version 5.2.1              

Database administrator planning

To prepare for an upgrade, review database requirements and complete other planning tasks.

You must upgrade to the appropriate database versions and patches before you upgrade FileNet® P8 components. For minimum database software version and fix pack requirements, see IBM FileNet P8 system requirements.

Rather than upgrading your existing database, it is a best practice to create a new database instance on a version of the database that is supported by the new FileNet P8 components. Import data for, or restore backups of, your existing Content Platform Engine (or your Content Engine and Process Engine) data into the new database. Then retarget your JDBC Content Engine data sources to the new database. This approach allows you to leave the existing production system in place while you do the prerequisite steps for the new database.

FileNet P8 systems with IBM Case Manager (for upgrades from versions 5.0.0, or 5.1.0)

Before upgrading FileNet P8 to version 5.2.1, Process Engine isolated regions that are used in an IBM® Case Manager configuration must be located in the corresponding Content Engine object store database or table space.

For version 5.0 and 5.1 FileNet P8 systems, new installations configured with IBM Case Manager were required to have common Oracle or DB2® for Linux, UNIX and Windows table spaces for the Process Engine isolated region and Content Engine object store. For Microsoft SQL Server, new installations configured with IBM Case Manager were required to have a common database for the Content Engine object store and the Process Engine isolated region. For systems that were upgraded to version 5.0 or 5.1, where IBM Case Manager was then added, there was no requirement for Process Engine and Content Engine databases to be common.

Important: For version 5.0 or 5.1 systems not in compliance with the common database or table space requirement, you must move any Process Engine isolated regions into the appropriate Content Engine object stores before you upgrade. A tool has been provided on the Content Platform Engine installation media for that purpose. See the techdoc documenting the tool for moving isolated regions.

Process Engine (for upgrades from versions 5.0.0, or 5.1.0)

Starting with the 5.2 version of FileNet P8, the Content Engine and Process Engine are deployed together as a single application server instance. In addition, the database is handled as a single entity. New workflow systems and isolated regions are created in object stores, and all database connections require data sources. Existing Process Engine systems become legacy workflow systems and the databases are separate from any new workflow systems.

As a part of the upgrade you will create data sources for any existing Process Engine databases. If you are upgrading from version 5.0 of Process Engine and had multiple virtual servers, each virtual server had a unique database and each of those databases will require a data source and those data sources will also be targeted to the new database. Upgrade the Content Engine, Process Engine, and Case Analyzer software and complete all upgrade procedures before you allow users to access information in the new database.

To upgrade the Process Engine database, identify the existing database user name and password. In versions of Process Engine older than 5.0, the default was the f_sw user. Record this database user name and password in the Installation and Upgrade Worksheet as the pe_db_user and password.



Last updated: March 2016
p8ppu070.htm

© Copyright IBM Corporation 2013, 2016.