FileNet P8 Content Engine, FileNet P8 Content Search Engine, Version 5.0.+              

Validating object stores

Validation determines whether your object stores and other Content Engine data are ready to be upgraded. You cannot upgrade your object stores until they are successfully validated.

To validate object stores:
  1. For each fixed content device in the left panel of the Upgrade Information window that needs info (as indicated by its icon in the left panel), select the device and specify the required parameter values in the right panel.
    Important: The SnapLockPassword parameter value is not stored. If you log off Content Engine Web Upgrade Tool and log back on, you must reenter the value.
  2. If Hitachi or IBM [Tivoli] are listed among the fixed content devices in the left panel, complete the following substeps. Otherwise, Content Engine Web Upgrade Tool does not process them:
    1. Choose Tools > Edit XML.
    2. In the CE35_to_50upgrade.xml file, replace all occurrences of Unsupported with UpgradeFinished to make Content Engine Web Upgrade Tool ignore these unsupported fixed content devices and fixed file stores (if any) in the object stores you upgrade.
    3. Click Save.
  3. Select the object stores to be validated. Initially, all the object stores are selected for validation. You can validate object stores in any order.

    If you want to validate object stores individually, select them from the left panel of Content Engine Web Upgrade Tool. If you want to select all the object stores at once, choose Tools > Select All Object Stores.

    You can clear your selections by choosing Tools > Clear All Object Stores. (The Clear All Object Stores menu choice is unavailable until you select at least one object store.)

  4. For each object store that you selected to be validated, complete the following substeps:
    1. In the right panel, specify the required values from your worksheet.
    2. If the object store uses fixed file stores, set the values for the root directories to their current locations. (The initial values that appear in these fields are from sysinit.dat and are not correct for version 5.0.0 of Content Engine.)
    3. When you click Save, a prompt reminds you to be sure that you chose the correct data sources for the object store. It also reminds to you to verify that you can read from and write to the file stores of the object stores from the Content Engine server.
  5. Choose Actions > Validate to validate the object stores that you selected.

    Each time you choose Validate, Content Engine Web Upgrade Tool creates the file validation.log in the directory FileNet/upgrader/logs, and moves the (time-stamped) log file from the previous validation (if any) into the directory FileNet/upgrader/logs/backup. Both directories are relative to the location specified in the working directory on the Upgrade Information page.

    Validation errors, such as missing or incorrect parameters, open in the right panel and are also written to validation.log.

  6. Select View > Validation Log to check the validation.log file for errors. The file opens in a scrollable window. Errors are also displayed in the right panel.

    You can correct some validation errors within the Content Engine Web Upgrade Tool interface; other errors can be corrected only manually or by using another interface, such as IBM® FileNet® Enterprise Manager.

  7. To correct a validation error within Content Engine Web Upgrade Tool, complete the following substeps:
    1. If the error indicates unspecified or invalid JDBC or JDBC XA data sources, choose the correct data source or fix the data source at the application server.
    2. If the error is in the file store path, specify the correct path.
    3. If the error is in the file store path, ensure that the file store exists, and that Content Engine can read and write to the file store. (Content Engine Web Upgrade Tool checks that the destination directory associated with the file store exists and that the inbound directory is empty.)
    4. Click Save.
    5. Click Validate and return to step 6.
  8. If the validation log indicates an invalid object store state because of pre-upgrade errors (for example, conflicting classes or properties or pending queue items or publishing requests), log on to version 3.5.2 of IBM FileNet Enterprise Manager and fix the error within the Content Engine 3.5.2 domain.
  9. If you successfully validated an object store, you can upgrade it. To validate more object stores, return to step 3.


Feedback

Last updated: November 2010


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