Content Platform Engine, Version 5.2              

Upgrading Content Engine and Process Engine software

Upgrading Content Engine and Process Engine software is a multistep process.

Important: Before you start to upgrade the Content Engine software, ensure that you are at the correct version and fix pack level, as indicated in Plan and Prepare Your Environment for IBM FileNet P8.
When you upgrade to version 5.2 you will use a single installation program to install the server and client software for the combined Content Platform Engine. In addition, IBM® Business Process Manager has been replaced by IBM Case Foundation, which has a separate installation program that includes a license agreement and files related to Case Analyzer. After the upgrade, Content Engine and Process Engine no longer exist as separate components but now run as a single deployed application. During the upgrade process, Content Engine and Process Engine databases are upgraded and configuration changes are made.
  1. Upgrading to Content Platform Engine
    You can install Content Platform Engine either interactively or silently.
  2. Upgrading to IBM Case Foundation
    If your FileNet® P8 system is configured to include Process Engine, you must install IBM Case Foundation. You can install IBM Case Foundation either interactively or silently.
  3. Upgrading Enterprise Manager
    If you did not upgrade Enterprise Manager as part of a Content Engine upgrade to Content Platform Engine, you can upgrade Enterprise Manager interactively or silently.
  4. Installing Content Platform Engine software updates
    You must apply any updates, fix packs, or interim fixes for the Content Platform Engine software that have been released.
  5. Granting directory permissions to the Configuration Manager user
    You must grant the file and directory permissions required by config_mgr_user, which is the user who runs Configuration Manager.
  6. Configuring Content Platform Engine within an existing application server instance
    You can configure your upgraded Content Platform Engine instances with Configuration Manager. You must upgrade the Content Platform Engine bootstrap properties for the upgraded Content Platform Engine instance. A single Content Platform Engine application instance equates to one deployed application on your application server.
  7. Configuring Content Platform Engine into a new application server instance
    You can configure your upgraded Content Platform Engine instances with Configuration Manager into a new application server instance.
  8. Deploying upgraded Content Platform Engine instances
    You must deploy the upgraded Content Platform Engine on the web application server. Deploying makes the Content Platform Engine application available for use.
  9. Installing storage device source files
    If your FileNet P8 system includes Tivoli® Storage Manager or EMC Centera devices, you must install files on the Content Platform Engine server.
  10. Completing Content Platform Engine post-deployment steps
    You must complete several Content Platform Engine post-deployment steps before you can put an FileNet P8 system into production.
  11. Verifying the Content Platform Engine deployment
    You can verify that the Content Platform Engine deployment was successful by accessing the FileNet P8 System Health page.
  12. Checking the automatic upgrade status for Content Engine data
    When you deploy the upgraded Content Engine application on the web application server and start the application, the existing Content Engine data upgrade begins. You can check the progress on the upgrade to confirm that the upgrade was successful.
  13. Creating an index on the IBM Content Search Services index requests table
    The automatic upgrade of Content Engine data includes the creation of a new index on the IBM Content Search Services index requests table. However, if the table is too large, the automatic upgrade cannot build the index. In which case you need to build it manually.
  14. Creating the Process Engine upgrade property file and upgrading the database
    Complete the following tasks to upgrade the Process Engine database.
  15. Converting the Oracle DATE data type to the TIMESTAMP data type (upgrading from version 4.5.0 or 4.5.1)
    If you are upgrading Oracle-based Content Platform Engine data, the auto-upgrade converts the Content Engine DateTime property columns from the Oracle DATE data type to the Oracle TIMESTAMP data type. However, if there is a function-based index that involves the DATE data type, then auto-upgrade will not be able to perform this conversion. In this case, you must drop the index, manually convert the DATE data type to the TIMESTAMP data type, and then recreate the original index in the Oracle database.
  16. Restore Component Manager custom settings for CE_Operations
    Use the procedure in this task to restore Component Manager custom settings for CE_Operations after the upgrade. You must complete the upgrade of at least one Workplace or Workplace XT client before you can start the Process Configuration Console.
  17. Backing up the Content Platform Engine database and configuration files
    Back up the database and configuration files after the upgrade to Content Platform Engine.
  18. Installing the latest Content Platform Engine client files on other FileNet P8 servers
    When you upgrade Content Engine software, you must also install the latest associated Content Platform Engine client files on other machines running FileNet P8 components, for example, on Application Engine servers.
  19. Putting the upgraded FileNet P8 system into production
    Before you disconnect your previous system and put the newly upgraded FileNet P8 system into production, make sure that you perform all prerequisite upgrade tasks.
Parent topic: Upgrading and configuring Content Engine and Process Engine
Related information:
General requirements for all FileNet P8 Platform systems

Feedback

Last updated: October 2013
p8pup096.htm

© Copyright IBM Corporation 2013, 2014.
This information center is powered by Eclipse technology. (http://www.eclipse.org)