Analyze your existing LiveCycle installation

Checklist/Task Item

Action Item

Failure Points

More Information

LiveCycle Service Packs

Check if latest service packs are applied.

You have not applied the latest service packs for your existing LiveCycle installation.

(Upgrading from LiveCycle ES Update 1 only) Download and install Service Pack 4.

(Upgrading from LiveCycle ES2 only) Download and install Service Pack 2.

7.x Compatiblity Layer

Check if installed and currently in use.

Not supported with LiveCycle ES3.

Migrate the solutions based on compatiblity layer to LiveCycle ES Update 1 or LiveCycle ES2.

Quick fixes

Track all quick fixes installed.

N/A

If you are upgrading from LiveCycle ES Update 1, after applying service pack 3, download and install Quick Fix 3.19. Contact Adobe support for more information.

Fonts

Back up all system and custom fonts.

N/A

N/A

(LiveCycle ES2.5 only) Solution Accelerators

Check if Solution Accelerators are installed.

Cannot be upgraded using LiveCycle ES3 Configuration Manager.

Contact Adobe support for more information.

(JBoss only) Crypto Jar Files

Check if you are using Adobe pre-configured JBoss 4.2.1.

If you do not copy the crypto jar files, LiveCycle ES3 Core EAR file will fail to deploy.

Crypto Jar Files are not present in Adobe pre-configured JBoss 4.2.1 provided with LiveCycle ES2 or LiveCycle ES2.5. If you are leveraging LiveCycle ES2 or LiveCycle ES2.5's, Adobe pre-configured JBoss 4.2.1 for upgrade to LiveCycle ES3, manually copy the jsafeJCEFIPS.jar, jsafeFIPS.jar and certjFIPS.jar files from JBoss_DVD/third_party/jboss-4.2.1_jars/crypto to [LiveCycle ES2 or LiveCycle ES2.5 JBoss 4.2.1 Home]/server/<server_profile>/lib

(JBoss only) EJB Applications

Check if you have EJB applications built against JBoss 4.2.1.

If you are migrating to JBoss 5.1, these EJB applications will not function.

You can choose to reuse JBoss 4.2.1 or recompile EJB applications with JBoss 5.1 libraries and jdk1.6_26.

Note: JBoss 4.2.1 will be end of life by the end of 2012; therefore, it is recommended to use JBoss 5.1 during upgrade.

// Ethnio survey code removed