Content Platform Engine, Version 5.2.1              

Upgrading Content Platform Engine software

Upgrading Content Platform Engine software is a multistep process. (If you are upgrading FileNet P8 from a version prior to 5.2, you upgrade Content Engine and Process Engine software.)

Before you begin

Important: Before you start to upgrade the Content Platform Engine software, ensure that you are at the correct version and fix pack level, as indicated in System requirements: Hardware and software requirements for IBM® FileNet® P8.

About this task

When you upgrade, you use a single installation program to install the server and client software for the Content Platform Engine. In addition, as of version 5.2, IBM Business Process Manager is replaced by IBM Case Foundation, which has a separate installation program that includes a license agreement and files related to Case Analyzer. After upgrading from a version of FileNet P8 prior to 5.2.0, Content Engine and Process Engine no longer exist as separate components but now run as a single deployed application. The upgrade process also changes the configuration of the Content Engine and Process Engine databases.
  1. Upgrading Content Platform Engine
    You can install Content Platform Engine either interactively or silently.
  2. Upgrading IBM Case Foundation
    You must install IBM Case Foundation if you need full workflow processing capabilities. You can install IBM Case Foundation either interactively or silently.
  3. 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.
  4. 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.
  5. Adding security arguments to the application server startup script (WebLogic Server only)
    You must add several environment arguments Java™ Authentication and Authorization Service (JAAS) to the security arguments in the WebLogic Server startup script to enable users to connect to Content Platform Engine by using Administration Console for Content Platform Engine.
  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 and the Content Platform Engine Startup Context (Ping Page).
  12. Enabling Java applet support for Administration Console for Content Platform Engine on WebSphere Application Server 8
    If you need to use workflow-related applets in Administration Console for Content Platform Engine with version 8 (or higher) of WebSphere® Application Server, you must disable HttpOnly session cookies. Because Administration Console for Content Platform Engine is collocated with Content Platform Engine, you must disable the cookies in the WebSphere profile that hosts Content Platform Engine. You can disable the cookies globally or just for your deployed application.
  13. Checking the automatic upgrade status for Content Platform Engine data
    When you deploy the upgraded Content Platform Engine application on the web application server and start the application, the existing Content Platform Engine data upgrade begins. (If you upgraded FileNet P8 from a version prior to 5.2.0, the existing Content Engine data upgrade begins.) You can check the progress on the upgrade to confirm that the upgrade was successful.
  14. Creating an index on the IBM Content Search Services index requests table
    The automatic upgrade of Content Platform Engine data (Content Engine data if you are upgrading FileNet P8 from a version prior to 5.2.0) 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.
  15. Completing the Process Engine upgrade (from version 5.1 or earlier)
    If you are upgrading FileNet P8 from version 5.1 or earlier, complete the following tasks to upgrade the Process Engine database.
  16. Verifying the successful upgrade of workflow systems
    Verify that all workflow systems were successfully upgraded.
  17. Converting the Oracle DATE data type to the TIMESTAMP data type (upgrading from version 4.5.1)
    If you are upgrading Oracle-based Content Engine data as part of an upgrade of FileNet P8 from version 4.5.1, 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 re-create the original index in the Oracle database.
  18. 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.
  19. Backing up the Content Platform Engine database and configuration files
    Back up the database and configuration files after the upgrade to Content Platform Engine.
  20. Installing the latest Content Platform Engine client files on other FileNet P8 servers
    Content Platform Engine updates usually ship with both server and client installation programs. You must run the client installation program for most components (including custom applications) that communicate directly with the Content Platform Engine server. Some components, such as IBM Content Navigator, have special tools to query the Content Platform Engine server and then to download and install the updated files as needed.
  21. 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 Platform Engine

Last updated: March 2016
p8pup096.htm

© Copyright IBM Corporation 2013, 2016.