|
The personnel responsible for upgrade should first survey
the existing LiveCycle ES4 SP1 environment to determine if the software
infrastructure continues to be supported by AEM forms on JEE. The
survey results help estimate the effort required to upgrade and
also determine the upgrade path.
When upgrading from LiveCycle ES4 SP1, two scenarios influence
how you can upgrade to AEM forms on JEE.
In-place upgrade:
If you choose to upgrade to AEM forms
on JEE using the existing application server instance, then it is
considered an in-place upgrade. For example, continued usage of
a WebSphere 8.5 instance from LiveCycle ES4 SP1to AEM forms on JEE
having installed necessary fix packs.
Using the same application server instance implies that changes
need not be made to the operating system or the server machine.
Out-of-place upgrade:
The following scenarios are considered
out-of-place upgrade:
-
Change of computers
: If you change your server
machine from the one that runs your existing LiveCycle installation
to use a new machine when upgrading to AEM forms on JEE.
-
Upgrading the application server
: If you are upgrading
your application server with a major version revision. For example,
upgrading WebSphere 6.1 to WebSphere 7.0.
-
Application server migration
: If you are migrating
from a 32-bit application server to a 64-bit variant. For example,
32-bit JBoss to 64-bit JBoss application server.
Note:
You cannot upgrade if you are changing your application
server, your operating system, or your database; it is considered
a fresh installation. For example, if you are changing your application
server from WebLogic to JBoss.
Supporting software infrastructure compatibilities
Some platforms that are supported with LiveCycle ES4 SP1
continue to be supported with AEM forms on JEE. However, AEM forms
on JEE supports the more recent versions of all software, so you
should upgrade to or use supported versions of all software.
|
Check or Task Item
|
Action Item
|
Failure Points
|
Additional Information
|
|
LiveCycle 7.x
|
N/A
|
Direct upgrade to AEM forms on JEE not supported.
|
Upgrade to LiveCycle ES Update 1 first,
followed by upgrade to LiveCycle ES2 and then to LiveCycle ES4 before you
can upgrade to AEM forms on JEE. See appropriate upgrade documentation.
|
|
LiveCycle ES (8.0.x)
|
N/A
|
Direct upgrade to AEM forms on JEE not
supported.
|
Upgrade to LiveCycle ES2 first, followed
by an upgrade to LiveCycle ES4 and then to AEM forms on JEE. See
appropriate upgrade documentation.
|
|
LiveCycle ES Update 1 (8.2.1.x)
|
N/A
|
Direct upgrade to AEM forms on JEE not
supported.
|
Upgrade to LiveCycle ES2 first, followed
by an upgrade to LiveCycle ES4 and then to AEM forms on JEE. See
appropriate upgrade documentation.
|
|
LiveCycle ES2 (9.0.0.x)
|
N/A
|
Direct upgrade to AEM forms on JEEAEM forms
on JEE not supported.
|
Upgrade to LiveCycle ES4 and then to AEM
forms on JEE. See appropriate upgrade documentation.
|
|
LiveCycle ES3 (10.0.x)
|
N/A
|
Direct upgrade to AEM forms on JEE not supported.
|
Upgrade to LiveCycle ES4 and then to AEM
forms on JEE. See appropriate upgrade documentation.
|
|
LiveCycle ES4 (11.0.x)
|
N/A
|
Direct upgrade to AEM forms on JEE supported.
|
Apply a minimum of service pack 1 on top
of LiveCycle ES4 and then upgrade to AEM forms on JEE. See appropriate upgrade
documentation:
|
|
Deployment Type
|
Check if the deployment type is single server
or server cluster.
|
N/A
|
N/A
|
|
Operating System
|
Check if the version is supported in
Supported Platform Combinations
.
|
Version not supported.
|
Install or upgrade to a supported version.
Note
that changing the operating system or upgrading it to a major version
revision will be an out-of-place upgrade.
|
|
Application server
|
Check if the version is supported in
Supported Platform Combinations.
|
Version not supported.
|
Install or upgrade to a supported version.
If
supported, it is recommended that you apply application server patches
and continue to run the updated application server before you upgrade.
This approach helps ensure that the application server is running
correctly when you are ready to upgrade.
|
|
Database
|
Check if the version is supported in
Supported Platform Combinations
.
|
Version not supported.
|
Install or upgrade to a supported version.
|
|
Database driver
|
Check if the version is supported in
Supported Platform Combinations
.
|
Version not supported.
|
Install or upgrade to a supported version.
|
|
JDK
|
Check if the version is supported in
Supported Platform Combinations
.
|
Version not supported.
|
Install or upgrade to a supported version.
|
|
Hardware support
|
Check if the server machine conforms to
the hardware requirements specified in the System Requirements section in
the
Preparing to Upgrade
guide.
|
N/A
|
Ensure sufficient hard disk space and RAM
are allocated on the server.
|
|
Firewall
|
Check if Firewall is enabled.
|
Is enabled.
|
Deactivate Firewall.
|
|
Antivirus
|
Check if Antivirus is installed and enabled.
|
N/A
|
Disable Antivirus during upgrade.
|
|
Custom applications
|
Track all custom applications.
|
N/A
|
Make necessary modifications after upgrade.
|
|
Custom WAR/EAR
|
Track all custom WARs and EARs.
|
Not upgraded during upgrade to AEM forms
on JEE.
|
Redeploy after upgrade.
|
|
Application Server Client JARs
|
Track all client JAR.
|
N/A
|
If necessary, modify them after upgrade.
|
Client-side applications compatibility
It is necessary to ensure that your client-side applications
are upgraded to supported versions to ensure that the end-user interfaces
of AEM forms on JEE continue to be functional.
|
Checklist/Task Item
|
Action Item
|
Failure Points
|
More Information
|
|
Adobe® Flash® Player
|
Download and install Flash Player 11.1.
|
Workspace fails to render post-upgrade.
|
N/A
|
|
Browser
|
See
Supported Platform Combinations
and
install a supported version.
|
N/A
|
N/A
|
|
Adobe® Reader®
|
Note the version of Adobe Reader.
|
Versions lesser than Adobe Reader 8 are
not supported.
|
See
Adobe
Reader compatibility
for more information.
|
|
Adobe® LiveCycle® Workbench 11
|
Download and install Workbench.
|
N/A
|
For more information, see:
Installing Workbench
|
|
Adobe® LiveCycle® Designer 11
|
Download and install Designer.
|
N/A
|
For more information, see:
Installing Workbench
|
Data, process, and API compatibility
On the server, process data and configuration information
is migrated automatically so that it is available for AEM forms
on JEE. For example, old process data continues to be available
so that users can run queries that span the upgrade. The configuration
information of the existing LiveCycle ES4 SP1 installation, that AEM
forms on JEE requires, is migrated. Changes in schema are also handled automatically
during the upgrade.
Processes that are developed in or updated to LiveCycle ES4 run
natively in AEM forms on JEE. Long-lived processes will resume after
the upgrade. For processes that are migrated from an existing LiveCycle
ES4 SP1 system, end users can continue to log in to Workspace and
see processes in the state that they left them in. Most APIs that
are used with LiveCycle ES4 SP1are compatible with AEM forms on
JEE.
|
Checklist/Task Item
|
Action Item
|
Failure Points
|
More Information
|
|
LiveCycle 7.x QPAC-based processes
|
Check if currently in use.
|
Not supported with AEM forms on JEE.
|
Upgrade to DSCs compatible with AEM forms
on JEE using Workbench Process Upgrade tool. For more information, see:
Upgrading
LiveCycle 7.x QPAC processes
in
Workbench help
.
|
|
LiveCycle ES Update 1 Processes
|
Check if currently in use.
|
Not supported with AEM forms on JEE.
|
Upgrade to DSCs compatible with AEM forms
on JEE using Workbench Process Upgrade tool. For more information, see:
Upgrading
LiveCycle 7.x QPAC processes
in
Workbench help
.
|
|
LiveCycle ES2 Processes and Applications
|
Check if currently in use.
|
N/A
|
Will continue to work with AEM forms on
JEE.
|
|
ADEP Processes and Applications
|
Check if currently in use.
|
N/A
|
Will continue to work with AEM forms on
JEE.
|
|
LiveCycle ES3 Processes and Applications
|
Check if currently in use.
|
N/A
|
Will continue to work with AEM forms on
JEE.
|
|
LiveCycle ES4 Processes and Applications
|
Check if currently in use.
|
N/A
|
Will continue to work with AEM forms on
JEE.
|
|
Custom DSCs
|
Track all custom DSCs.
|
N/A
|
After upgrade, update the versions of custom
DSCs.
|
|
LiveCycle Client APIs
|
Track all client APIs.
|
N/A
|
After upgrade, modify the existing APIs
to take advantage of the new APIs available with AEM forms on JEE.
|
AEM forms on JEE Component Patching
Two scenarios determine how a Document Service Component
is patched:
-
Patching a DSC with a new version
: When a DSC
is deployed with a new version, it co-exists with the older version
instead of patching it with additional configuration parameters.
This behavior applies to all LiveCycle DSCs and to any custom DSCs
you have deployed.
For example, if you are upgrading from
LiveCycle ES Update 1(8.2.1.x), SignatureService 1.0 and 1.1 exist
prior to upgrading. Post upgrade, configuration parameters of SignatureService
1.1 are copied to SignatureService 2.0. And both, SignatureService
versions, 1.1 and 2.0 will be made available for usage.
-
Patching a DSC with the same version
: When a DSC is
deployed with the same version, it overwrites the existing DSC,
but retains the configuration parameters.
For example, if
you have versions 1.0, 1.1, 1.2 already deployed, and the patching
DSC version is 1.2, then the existing DSC version 1.2 will be overwritten
by the new DSC with version 1.2. However, the configuration parameters
of the old DSC version 1.2 will be retained. Also currently the endpoint/security
configurations assume default values and no existing values are
carried over.
|
|
|
