Upgrading from LiveCycle ES2, ADEP, or
LiveCycle ES3 to LiveCycle ES4 involves installing LiveCycle ES4
software that is subsequently configured using settings from the
existing LiveCycle server. Configuration settings, user data, and
job information are migrated to the LiveCycle ES4 system.
Most of the tasks in the upgrade process are automated and performed
(with some user input) by Configuration Manager. Configuration Manager is
a tool used to configure, deploy, and validate LiveCycle ES4 components
for deployment to the application server. When run in upgrade mode,
Configuration Manager also performs upgrade specific tasks such
as updating configuration settings and data.
The GDS directory, Content Storage Root directory (if applicable),
and database must be accessible to Configuration Manager during
the upgrade process.
You can continue to use your existing database if it is a version
that is compatible with LiveCycle ES4. If your current database
version is no longer supported, back up the data and restore it
to a compatible version.
If you are not changing major application server version and
are performing an in-place upgrade, your existing application server
must be running to deploy the new EAR files. For all other upgrades,
the old application server does not need to run during the process.
For more information on in-place or out-of-place upgrades, see 5.2 In-place or Out-of-place upgrades
