LiveCycle Components Verification

BAM installation and continued usage

Check if BAM is installed.

LiveCycle ES3 is the last release to support BAM

Note: You can only reuse an existing instance of LiveCycle BAM with LiveCycle ES3

You can continue using BAM and the existing processes that use BAM will continue to work with LiveCycle ES3. Proceed with the next task item listed in the table.

If you wish to discontinue using BAM, back up existing data, uninstall BAM, and discontinue its resource allocation. See Uninstalling the BAM Server manually for more information.

New Database

If you wish to use a new database, migrate existing BAM data after creating the new database.

N/A

For more information, see: Export and backup Business Activity Monitoring metadata

BAM Publisher DSC

Check if installed (using Workbench, verify if the DSC is active in the components view).

N/A

If you wish to, you could install the BAM Publisher DSC afresh. See the bam_wizard_guide.pdf document found at <LiveCycle root>\LiveCycle_ES_SDK\misc\Business_Activity_Monitoring\LavaActivitySuite\BAMWizard\

ECM Connector

Note the ECM connector in use.

N/A

N/A

ECM Server

Note the version and check if supported.

Not supported with LiveCycle ES3

Upgrade to a supported version.

ECM Client

Note the version and check if supported

Not supported with LiveCycle ES3

Upgrade to a supported version.

ECM Form Templates

Back up form templates and associated data

N/A

N/A

adobe-component-ext.properties file

Should be copied from the old application server profile to the new application server profile in case of an out-of-place upgrade

N/A

N/A

Content Storage Root directory (lccs_data)

Perform cold backup of Content Services (deprecated) data and note the size.

Unable to find lccs_data.

When installing LiveCycle ES2 (service pack 2), LiveCycle Configuration Manager did not append lccs_data to the custom path specified for Content Storage Root directory. Hence, the folder name of the Content Storage Root directory may be different.

LiveCycle AMPs

Track all LiveCycle AMPs.

N/A

Reimport all existing and any additional LiveCycle AMPs when running the Configuration Manager.

Merged Custom AMPs

Track any additional custom AMPs added.

Custom AMPs will be overridden on upgrade.

Remerge the AMPs carefully, paying attention to any potential conflicting changes in the properties.

Content Services (deprecated) APIs

Deprecated. LiveCycle ES3 is the last release supporting these APIs.

N/A

N/A

Database Locks

Check if there are locks on Content Services (deprecated) tables.

Content Services (deprecated) EAR deployment will fail.

Clear all database locks.

ALF_BOOTSTRAP_LOCK

Check if the table is present.

If present, Content Services (deprecated) EAR deployment will fail.

Delete the table.

ALF_NODE_ASPECTS

Check for duplication in the table.

Content Services (deprecated) EAR deployment will fail.

See TechNote for more information.

ALF_ACCESS_CONTROL_ENTRY

ALF_ACCESS_CONTROL_LIST

ALF_NODE

ALF_NODE_ASSOC

ALF_NODE_PROPERTIES

ALF_CHILD_ASSOC

ALF_ACL_MEMBER

ALF_AUDIT_* (that is all tables beginning with alf_audit_)

Note the size of each of these tables.

Content Services (deprecated) EAR deployment may fail due to server timeout if the data volume is large.

For more information, see: Troubleshooting LiveCycle guide

Custom DSC and Data Management DSC

Check if deployed.

N/A

If the DSCs are deployed correctly, the end points are created. Keep track of these end points.

FML TLO Handler

Check if com.adobe.livecycle.datatypeutility. FMLTLOHandler record is present in the tb_sc_tlo registry table. The record is deleted by the upgrade process.

Upgrade does not delete the record.

Manually delete the record.

Legacy LCAs that use FML

Track LCAs that use FML.

N/A

N/A

Classes in DSCs

Check if the classes being serialized are serializable.

N/A

Only serializable classes can be serialized.

HSM-based signatures

Note expiry dates of certificates and credentials.

N/A

N/A

Signatures

Note expiry dates of certificates and credentials.

N/A

N/A

Web Services based implementation for HSM-based Signatures

Redeploy if you are migrating to a new system.

N/A

You can also switch to BMC implementation. For more information, see: HSM-based Signatures on 64-bit Windows Computers.

Email

Note the email addresses assigned to email end points.

The addresses are invalid.

Provide valid email addresses by logging in to Administration Console. See Configuring email endpoints for more information.

Watched Folder

Note the paths assigned to watched folders.

The paths do not exist and the watched folders are inaccessible.

Set up watched folders at locations that are highly available by logging in to Administration Console. See Configuring watched folder endpoints for more information.

Number of forms

Note the number of forms.

N/A

N/A

Web Services used within forms

Note the URLs for usage post-upgrade.

N/A

N/A

Types of forms

Note the types of forms in use (PDF, HTML, Adobe® Flex®, Guides (deprecated), etc.)

N/A

N/A

Customized Guide system (1.0)

If customized, then back up the customized files.

N/A

N/A

Provisioning Profile

If no pin is used on the Mobile Client, 0 should be set for both settings “Minimum Pin Length” and “Maximum Password Retries before Wipe”. Otherwise, no form will be downloaded to the form list on the client.

By default, the Android Minimum Pin Length is set with 4 and Android Maximum Password Retries before Wipe is set with value 5.

Printers

Note the IP addresses of all printers, and check if they are accessible.

Printers are inaccessible.

N/A

PDFG 3D

Not supported with LiveCycle ES3.

PDFG-3D has to be uninstalled manually. See Uninstalling components for more information.

Adobe's partner Prostep AG is now responsible for the support and upgrade of the PDFG 3D service. When planning your upgrade of PDFG 3D, contact Prostep AG. Contact details and additional information about PDFG 3D is available from their website at: http://www.prostep.com/.

Adobe® Acrobat® Version

Note the Acrobat version.

N/A

Install Acrobat X

End-user Interfaces

See Supported Platform Combinations and install supported versions of Flex SDK, Flash Player, and Browser.

N/A

N/A

Number of processes

Using the LiveCycle Administration Console note the number of processes.

N/A

N/A

Service States

Using LiveCycle Administration Console track the service states for all services.

Some services maybe inactive causing exceptions during upgrade.

If these services are not expected to be inactive, start them using Workbench.

TB_PROCESS_INSTANCE

TB_FORM_DATA

TB_JOB_INSTANCE

Note the data volume.

N/A

N/A

Process States

Using the LiveCycle Administration Console note the number of Stalled and Running processes.

N/A

Stalled and Running processes can be resumed after upgrading.

Workspace Customization

Check if Workspace is customized.

Customization cannot be migrated.

Workspace must be recustomized after upgrade. Export and backup adobe-workspace-client.ear. After upgrade, replace the default Workspace client with the old EAR file.

Credentials

Note the expiry date.

N/A

N/A

Custom Credential Files

Locate the custom credential file, if any.

N/A

If you are upgrading from ES2, note down the default credential file.

Certificates

Note the expiry date.

N/A

N/A

URL of the LiveCycle Server

Note the landing URL of your existing LiveCycle installation.

N/A

To ensure that your existing policies continue to work with an out-of-place upgrade to LiveCycle ES3, ensure that the Host Name and Port (landing URL) of the upgraded system remains the same as the existing system.

Policies

Note the number of policies, policy sets, and permissions these policies or policy sets may have.

N/A

N/A

Database size

Note the size of the Rights Management database.

N/A

N/A

LDAP Synchronization

Ensure that the LDAP is synchronized and the authentications function as expected.

N/A

N/A

Canonical names

N/A

N/A

Canonical names of users are not visible on the UI, but will be visible after Upgrade.