Updating the Vital Product Data (VPD) script (version 4.0.1 and Solaris only)
Perform the
following steps only if Content Engine Server
is at version 4.0.1
on a Solaris machine, a non-root user installed the current version
of Content Engine Server, and
a different non-root user will upgrade Content Engine.
Shutting down CFS Exporter
If your system includes version 4.0.0 or 4.5 of Content Federation Services (CFS), you must shut down
the CFS Exporter before upgrading Content Engine.
Detecting name conflicts with reserved words
It is a best practice to verify that the names of custom
classes and custom properties in your current version do not conflict
with reserved words before you begin the upgrade from version 4.0.1
or 4.5.0.
Removing the deployed FileNetEngine application
You must remove the existing FileNetEngine application
from the web application server to undeploy or uninstall the application
EAR file. Removing the existing version ensures a clean deployment
of the upgraded version 5.0.0 Content Engine EAR
file.
Clearing the web application server cache
You must clear the cache for the web application server
to remove the currently deployed Content Engine data
to prevent conflicts with the upgraded version.
When upgrading Process Engine client
files on Content Engine, you
must clear the cache before redeploying the Content Engine EAR file. Otherwise, the
upgraded Process Engine client
JAR files do not persist.
Editing XA data source XML files (Oracle and JBoss 4)
If you are using an Oracle database with JBoss Application Server version 4.0.5 or version
4.2.3, you must edit the data source XML files to set the <mbean>
attribute to allow successful connection to the database.