FileNet P8 Content Search Engine, Version 5.0.+              

Starting Content Engine Web Upgrade Tool

To use Content Engine Web Upgrade Tool, you browse to the machine where the tool is running.

To start Content Engine Web Upgrade Tool:

  1. Start of changeLog on to a system from which you intend to browse to Content Engine Web Upgrade Tool.End of change
  2. Open your completed Installation and Upgrade Worksheet file.
    Tip: In the worksheet file, verify that the Data > Filter > AutoFilter command is enabled. To view only Content Engine Web Upgrade Tool values, filter by CE Web Upgrade Tool in the Installation or Configuration Program column.
  3. From the system you logged on to, browse to the website http://ce_server_name:port_number/upgrader. ce_server_name is the host name of the machine where you run the tool. port_number is the WSI port used by the application server on which Content Engine and Content Engine Web Upgrade Tool are deployed. (Alternatively you can browse to the website using the HTTPS protocol if SSL is configured on the application server.)
    Important: If Content Engine is in a cluster or farm environment, you can run the tool from any node in the environment. Browse directly to the node where the tool is running, rather than using a load balance URL.
  4. At the Log In window, log in as the ce_upgrade_user.
    Important: Do not run more than one instance of Content Engine Web Upgrade Tool at a time.

    The first time you log in, continue at step 5. Otherwise, Content Engine Web Upgrade Tool displays the Upgrade Information window, where you can resume validating and upgrading the object stores.

  5. Enter the location of the GCD file sysinit.dat on the Windows machine where version 3.5.2 of Content Engine is installed. If you previously copied sysinit.dat to another location to ensure that it is accessible from a UNIX Content Engine server, you can specify that location instead. Do not rename the file. Otherwise, Content Engine Web Upgrade Tool prompts you for a file named sysinit.dat.
    Important: Do not delete the GCD file on the Windows system where version 3.5.2 of Content Engine is installed.
  6. Verify that a file named CE35_to_50upgrade.xml exists. To find the file, navigate to the directory shown in the working directory entry in the right panel of the Upgrade Information page. Then, navigate within that directory to the FileNet/upgrader directory. You might need to edit this file to fix errors that occur during the validation or upgrade phases.
  7. Verify that a file named upgrade_trace-timestamp.log is in the FileNet/upgrader/logs directory. Content Engine Web Upgrade Tool creates this file anew each time you log in, and it moves the file from the previous login to the FileNet/upgrader/logs/backup directory. This file records all the validation and upgrade activity.


Feedback

Last updated: November 2010


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