Most of the work involved in upgrading from previous versions
of LiveCycle to LiveCycle ES3 is done by Configuration Manager.
The tasks that are specific to upgrade are integrated seamlessly
into the configuration and deployment process.
Installing, configuring, and deploying LiveCycle involves the
following processes:
Installing: You install LiveCycle by running the installation
program. Installing LiveCycle places all the required files onto
your computer, within one installation directory structure. The
default installation directory is C:\Adobe\Adobe LiveCycle ES3 (Windows)
or /adobe/adobe_livecycle_es3 (Linux or UNIX); however, you can
install the files to a different directory.
Configuring and assembling: Configuring LiveCycle modifies
a variety of settings that determine how LiveCycle works. Assembling
the product places all the installed components into several deployable
EAR and JAR files according to your configuration instructions.
Configure and assemble the components for deployment by running
Configuration Manager.
Configuring the application server:
You can choose to let Configuration Manager configure the application
server. You already performed some configuration tasks when you prepared
the environment for upgrading; however, you still have a few tasks
to do after LiveCycle is installed, such as configuring Java™ Virtual Machine (JVM™) arguments,
configuring the data source connections, and setting some time-out values.
Deploying: Deploying
the product involves deploying the assembled EAR files and supporting
files to the application server on which you plan to run your LiveCycle.
If you configured and assembled multiple modules, the deployable components
are packaged within the deployable EAR files. Components and LiveCycle
archive files (LCAs) are packaged as JAR files. Configuration Manager automatically
deploys the EAR files, components, and archive files to the application
server.
