You need to upgrade your object stores before they can
be made available for use in version 5.0.0 (or later) of Content Engine.
To upgrade object stores:
- Select the object stores to
be upgrade.
If you want to upgrade 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 . You can upgrade object stores in any order. In either
case, the first set of Content Engine object
store that you select for upgrade includes (by default) the GCD, domain
addons, and fixed content devices.
You can clear your selections
by choosing (The Clear
All Object Stores menu choice is unavailable until you
select at least one object store.
Tip: The upgrade
log file can get long. For ease in viewing the log, upgrade only one
object store at a time.
- Choose . The right
panel displays a log showing the progress of the upgrade.
Each
time you choose Upgrade, Content Engine Web Upgrade Tool creates
a file named upgrade-running.log in the FileNet/upgrader/logs directory,
and copies the previous upgrade-running.log file
to the upgrader_trace-timestamp.log file
in the FileNet/upgrader/logs/backup directory.
After the upgrade starts, you can pause it by clicking Pause.
The upgrade pauses as soon as it finishes upgrading whatever object
store node it is currently processing. To resume the upgrade, click Resume.
If you exit the browser in which Content Engine Web Upgrade Tool is running,
an upgrade that is in progress continues in the background. If you
log back in, you see the upgrade status at its current state in the
right panel.
Content Engine Web
Upgrade Tool indicates which object store it is upgrading by changing
the appearance of the corresponding icon in the left panel. The tool
also changes the appearance of each icon to indicate that it has completed
the upgrade of an object store.
Content Engine Web Upgrade Tool also puts
the most recent upgrade report file upgrade.htm into
the directory FileNet/upgrader/reports and moves
the (time-stamped) report file from the previous upgrade into the
directory FileNet/upgrader/reports/backup. Both
directories are relative to the location specified in the working
directory on the Upgrade Information page.
- If Content Engine Web
Upgrade Tool detects an error in upgrading an object store, it halts.
To correct the error, complete the following substeps:
- Choose and search the upgrade log to determine
where the error occurred.
- Close the error log in the right panel and click the
node in the left panel where the error occurred.
- If the error can be fixed without requiring you to restore
the version 5.0.0 GCD database (in case of a domain upgrade failure)
or the object store database (in case of an object store upgrade failure),
fix the condition that caused the error and then click Reset
Status next to the failed node to reset the node to the
ready state.
- If the error indicates that you need to restore the
version 5.0.0 GCD database to its state before the upgrade, click Reset
All Status at the top of the right panel for each domain
node to reset it to the ready state. Use your database tools to restore
the database to its state before the upgrade of Content Engine from version 3.5.2.
- If the error indicates that you need to restore the
object store database to its state before the upgrade, click Reset
All Status at the top of the right panel to reset all
nodes of the object store to ready state. Use your database tools
to restore the database to its state before the upgrade of Content Engine from version 3.5.2. If
the error occurred during the Upgrade Addons phase because of classes
or properties that were removed from the object store and imported
by a System Addon, reimport the Addon XML file to replace the missing
classes or properties. Then, log in to version 5.0.0 of IBM® FileNet® Enterprise Manager and refresh the object
stores node. If the object store that failed is visible, delete it.
- Click Bring Online for each object
store selected for upgrade that Content Engine Upgrade
Tool did not attempt to upgrade (because of the error that stopped
processing) if you need the version 3.5.2 object stores available
while you are resolving the object store or domain error.
- Return to step 2.
- If the upgrade succeeds, and you have additional object
stores to upgrade, return to step 1.
Important: When you have successfully upgraded an object store, Content Engine Web Upgrade Tool prevents
you from trying to upgrade the object store again.
- When you have upgraded all the object stores, choose to see a summary of the results of the upgrades.