FileNet P8 Content Engine, Version 5.0.+            Operating systems:  Windows

Performing the upgrade

You can run the command-line Content Engine Upgrader to upgrade the items that you selected for upgrade in the upgrade status file upgrade.xml.

Before upgrading an object store, the command-line Content Engine Upgrader takes the object store offline. After upgrading an object store, the Upgrader updates the corresponding status value for the object store in the upgrade.xml file.

To perform the upgrade:

  1. Log on to the system where the command-line Content Engine Upgrader is installed as the ce_upgrade_user.
  2. Navigate to the ce_install_path\tools\upgrade directory, which contains CE35_to_50Upgrader.bat.
  3. Optional: To see the available options, run the Upgrader tool from a command line, as follows: CE35_to_50Upgrader.bat -h
  4. Run the Upgrader tool by entering the following command:

    CE35_to_50Upgrader -i upgrade.xml -r

    The -r flag is optional. If you include it in the command, the tool generates an HTML report.

    Important: The Upgrader upgrades only the items that have an initial status of ReadyToUpgrade and a SelectedForUpgrading value of yes.

    The Upgrader sends a status message to the command line and to a log4j logging system as it attempts to upgrade each item. If the upgrade for a specific item fails, the Upgrader stops.

  5. If the upgrade fails for an item, complete the following steps:
    1. Use the information (exception code and stack trace) in the command-line output or the log4j file to correct the error.
    2. Edit the upgrade.xml file to replace any Status value of UpgradeStarted or UpgradeFailed to ReadyToUpgrade.
    3. If the object store add-on upgrade takes longer than 10 minutes and the upgrade fails, note the exceptions in the log. Increase your application server timeout settings.

      Complete the following steps:

      1. Increase your application server transaction timeout value. Make a note of your existing values before you change them. Depending on your hardware, you might need to increase the timeout value to as much as 6000 seconds.
        IBM® WebSphere® Application Server
        Navigate to Application Servers > servername > Container Services > Transaction Services, and increase the values for Total transaction lifetime timeout and Maximum transaction timeout.
        Oracle WebLogic Server
        Increase the value for Domain > Services > JTA > Timeout Seconds and the value for Servers > CEServerInstanceName > Configuration > Tuning > Stuck Thread Max Time. Use the same value for both settings.
        JBoss Application Server
        Edit the jboss-service.xml file to set the value for <attribute name="TransactionTimeout">.
      2. Restart the application server.
      3. Restart the upgrade for the object store add-ons.
      4. After the upgrade completes successfully, you can reset the application server timeout settings to the previous values.
    4. If the failure occurred due to an error after the database upgrade has completed, then restore your database from backup.


Feedback

Last updated: November 2010


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