You must upgrade your current Content Engine data (GCD, addons, fixed
content devices, object stores, and related information).
There are two tools available
to you for upgrading Content Engine data:
the GUI-based Content Engine Web
Upgrade Tool, and the command-line-based Content Engine Upgrader. You can use the
command-line Content Engine Upgrader
only if you explicitly chose to install it as part of the Content Engine Server installation.
Whichever
tool you use, keep in mind the following guidelines as you prepare
for the upgrade:
- It is not necessary to check in checked-out documents before running
the upgrade tool.
- Ensure the system where the upgrade process runs has sufficient
resources, most especially processor and memory. If the upgrade process
will run on a system with other applications, such as the database
server, ensure the resources are sufficient for all the processes
on that system
- Ensure the system where the upgrade process runs has sufficient
resources, most especially processor and memory. A system adequately
sized for production processing will be sufficient to run the upgrade
process.
- If you use Content Engine Web
Upgrade Tool to upgrade your Content Engine data,
you must deploy it on the same Java Virtual Machine where the new
version of Content Engine is
deployed.
- If you are upgrading an IBM® FileNet® P8 environment
with many object stores, use the following approach:
- Upgrade fewer than 20 object stores at a time.
- For best performance when Content Engine is
deployed on a web application server with a 32-bit JVM, restrict each
version 5.0.0 FileNet P8 domain
to 50 or fewer object stores. If the version 3.5.2 FileNet P8 domains contain more than
50 object stores, consider partitioning them into multiple version
5.0.0 FileNet P8 domains
during the upgrade process.
- Ensure that the version 3.5.2 object stores with the same basic
set of system objects (for file stores, fixed file stores, and related
objects) are upgraded into the same FileNet P8 domain.
- The time to upgrade object stores from version 3.5.2 depends on
the number of documents the object store contains, the database type,
and the resources of the machine on which the database system runs.
If you are upgrading version 3.5.2 object stores that contain more
than a million documents or a million custom objects, the upgrade
tool can take more than an hour to complete the upgrade.
- For non-English support relating to collections, see IBM FileNet P8 Non-English Support
Guide.