You're viewing help content for version:

AEM 6.3 Forms includes several new features and enhancements that streamline the creation, management, and user experiences with forms, documents, and correspondences. It also brings enhancements to Adobe Sign and Forms Workflow and many new features such as Data Integration. To learn about all the new capabilities and enhancements of AEM 6.3 Forms, see New features summary document.

You can upgrade your existing LiveCycle or AEM Forms installation to obtain new capabilities and enhancements offered in AEM 6.3 Forms while retaining existing data, processes, and assets intact. On upgrade, metadata and state of the processes are also preserved. You can choose an upgrade path to get started with upgrade.

Available upgrade paths

You can upgrade existing AEM Forms or LiveCycle installation to AEM 6.3 Forms. Available upgrade paths are:

Available upgrade paths for AEM Forms on OSGi

The following diagram displays the available upgrade paths for AEM Forms on OSGi:

upgrade-path-OSGi

You can perform a direct upgrade from:

  • AEM 6.1 Forms on OSGi
  • AEM 6.2 Forms on OSGi

 You can also perform a multi-hop upgrade from

  • AEM 6.1 Forms on OSGi

 

Available upgrade paths for LiveCycle and AEM Forms on JEE

The following diagram displays the available upgrade paths for AEM Forms on JEE:

upgrade-pathsES4SP1

You can perform a direct upgrade from:

  • LiveCycle ES4 SP1
  • AEM 6.1 Forms on JEE
  • AEM 6.2 Forms on JEE

You can also perform a multi-hop upgrade from

  • LiveCycle ES2
  • LiveCycle ES3
  • AEM 6.0 Forms on JEE    

Upgrade to AEM 6.3 Forms on OSGi

Use one of the following upgrade paths, as appropriate for your environment

AEM 6.1 Forms or AEM 6.2 Forms > AEM 6.3 Forms

You can perform a direct upgrade from AEM 6.1 Forms or AEM 6.2 Forms to AEM 6.3 Forms. Do the following:

  1. Upgrade the existing AEM instance to AEM 6.3. The steps are listed below:

    1. Install the latest service pack and patches for AEM 6.1 Forms or AEM 6.2 Forms. For details, see:

    2. Prepare the source instance for the upgrade. For detailed steps, see Upgrading to AEM 6.3.

    3. Download the AEM 6.3 QuickStart.

    4. (Unix/Linux-based installations only) If you are using UNIX or Linux as the underlying operating system, open the terminal window, navigate to the folder containing crx-quickstart, and run the following command:

      chmod -R 755 ../crx-quickstart

    5. Upgrade your AEM instance to AEM 6.3. For step by step instructions, see Upgrading to AEM 6.3.

      Before continuing with the next steps, wait until the ServiceEvent REGISTERED and ServiceEvent UNREGISTERED messages stop appearing in the <crx-repository>/error.log file.  

      Note:

      After the server is up and running, a few AEM Forms bundles remain in install state. The number of bundles can vary for every installation. You can safely ignore the state these bundles. The bundles are listed at http://[server]:[port]/system/console/.

  2. Prepare the upgraded AEM instance for AEM 6.3 Forms.

    1. Copy the [AEM_installation_directory]\crx-repository\archived-versions\[time-stamp]\fonts\fonts directory to [AEM_installation_directory]\crx-repository.  

    2. Open CRXDE Lite, navigate to /libs/fd/signatures/install, delete the aemfd-signatures-bootdelegated-libs-pkg package, and click Save All.

    3. Shut down the AEM server.

    4. Download AEM Forms add-on package from AEM Package Share.

      A separate AEM Forms add-on package is available for every supported operating system. For the complete list of the available packages and download links, see AEM Forms Releases.

    5. Extract the downloaded AEM Forms add-on package.

      Copy the core-common-pkg-<version>.zip file from [extracted-aem-forms-add-on-package]\jcr_root\etc\packages\day\cq60\fd\[adobe-aemds-common-pkg-version.zip]\jcr_root\etc\packages\day\cq60\fd to [AEM-Installation-Directory]\crx-quickstart\install directory

    6. AEM Forms requires RSA and BouncyCastle libraries to be installed with AEM Forms add-on package. Perform the following steps to boot delegate these libraries:   

      1. Open the sling.properties at [AEM installation]\crx-quickstart\conf\ for editing. If you use [AEM_installation_directory]\crx-quickstart\bin\start.bat to start AEM, then edit the sling.properties at [AEM_installation_directory]\crx-quickstart\

      2. Add the following properties to the sling.properties file:

        sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
        sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider=org.bouncycastle.*

        Save and close the file.

    7. Start the AEM Server.

      Before continuing with the next steps, wait until the ServiceEvent REGISTERED and ServiceEvent UNREGISTERED messages stop appearing in the <crx-repository>/error.log file.  

  3. Install AEM Forms add-on package. The steps are listed below:

    1. Log in to the AEM server as an administrator and open the package share. The default URL of the package share is http://[server]:[port]/crx/packageshare.

    2. In package share, search AEM 6.3 Forms add-on packages, click the package applicable to your operating system, and click Download. Read and accept the license agreement and click OK. The download starts. Once downloaded, the word Downloaded appears next to the package.

      Alternately, you can also use the hyperlinks listed in AEM Forms releases to manually download a package.

    3. After the download is complete, click Downloaded. You are redirected to package manager. In the package manager, search the downloaded package, and click Install.  

      If you manually download the package using the direct link listed in AEM Forms releases, then open AEM Package Manager, click Upload Package, select the downloaded package, and click upload. After the package is uploaded, click package name, and click Install.

      Note:

      After the package is installed, you are prompted to restart the AEM instance. Do not immediately stop the server. Before stopping the AEM Forms server, wait until the ServiceEvent REGISTERED and ServiceEvent UNREGISTERED messages stop appearing in the <crx-repository>/error.log file and the log is stable. Also note, the following three packages can remain in the installed state. You can safely ignore the state of these packages:

      • Adobe Correspondence Management Migration
      • Adobe LiveCycle FormsManager Core
      • Forms Common Service

    4. Stop the AEM instance and delete the following files:

      • [AEM_Installation_Directory]\[crx-quickstart]\launchpad\ext\bcmail-jdk15-1.35
      • [AEM_Installation_Directory]\[crx-quickstart]\launchpad\ext\bcprov-jdk15-1.35
    5. Start the AEM instance.

  4. Perform post-installation activities.

    • Run Migration Utility

      The migration utility makes the adaptive forms and correspondence management assets of earlier versions compatible with AEM 6.3 forms. You can download the utility from AEM package share. For step-by-step information to configure and use the migration utility, see migration utility.

    • Reconfigure Adobe Sign

      If you had Adobe Sign configured in the previous version of AEM Forms, then reconfigure Adobe Sign from AEM Cloud services. For more details, see Integrate Adobe Sign with AEM Forms.

      Moreover, AEM 6.3 Forms release has introduced many new Adobe Sign features. For step-by-step information to use Adobe Sign, see Using Adobe Sign in an adaptive form.

    • Reconfigure analytics and reports

      In AEM 6.3 Forms, traffic variable for source and success event for impression are not available. So, when you upgrade to AEM 6.3 Forms, AEM Forms stops sending data to Adobe Analytics server and analytics reports for adaptive forms and adaptive document are not available. Moreover, AEM 6.3 Forms introduces traffic variable for the version of form analytics and success event for the amount of time spent on a field. So, reconfigure analytics and reports for your AEM Forms environment. For detailed steps, see Configuring analytics and reports.

      Methods to calculate average fill time for forms and average read time for adaptive documents have changed. So, when you upgrade to AEM 6.3 forms, older data (data from previous AEM Forms release) for these metrics is available only in Adobe Analytics. It is not visible in AEM Forms analytics reports. For these metrics, AEM Forms analytics reports display data which is captured after performing the upgrade.

  5. Verify that the server is upgraded successfully, all the data is also migrated successfully, and it can operate normally.

    • Verify the status of the bundles: Ensure that all the bundles are in active state.
    • Verify replication and reverse replication: Publish, fill, and submit a few migrated forms. Verify the submitted data also.
    • Verify access to admin and developer user interfaces: Log in to AEM instance from an admin account and verify that you have access to the following URLs:
      • http://[server]:[port]/crx/packmgr
      • http://[server]:[port]/crx/de
      • http://[server]:[port]/aem/forms.html/content/dam/formsanddocuments

AEM 6.0 Forms > AEM 6.3 Forms

Direct upgrade from AEM 6.0 Forms to AEM 6.3 Forms is not available. Perform an intermediate upgrade to AEM 6.2 Forms and then upgrade from AEM 6.2 Forms to AEM 6.3 Forms. 

Upgrade to AEM 6.3 Forms on JEE

Use one of the following upgrade paths, as appropriate for your environment

AEM 6.1 Forms on JEE, or AEM 6.2 Forms on JEE > AEM 6.3 Forms on JEE

Perform the following procedure to upgrade existing AEM 6.1 Forms on JEE or AEM 6.2 Forms on JEE to AEM 6.3 Forms on JEE:

  1. Download the AEM 6.3 Forms on JEE installer from the Adobe Licensing Website (LWS). You require a valid Maintenance & Support contract to download the installer.

  2. See Upgrade checklist and planning to learn about the checks to perform to ensure a successful upgrade.

  3. See Prepare to upgrade to AEM Forms to learn and perform the tasks that ensure the upgrade runs correctly with minimal server downtime.

AEM 6.0 Forms on JEE > AEM 6.3 Forms on JEE

Direct upgrade from LiveCycle ES2, LiveCycle ES3, or AEM 6.0 Forms to AEM 6.3 Forms is not available. You can perform an intermediate upgrade to one or more versions of LiveCycle or AEM Forms and then upgrade from AEM 6.3 Forms. For the list of intermediate versions and corresponding upgrade instructions, see Choose an upgrade path.

LiveCycle ES4 SP1 > AEM 6.3 Forms on JEE

Upgrading LiveCycle ES4 SP1 to AEM 6.3 Forms on JEE is an out-of-place upgrade, as it involves migrating assets and data from previous versions to the fresh instances (new versions) of supported application servers, operating systems, and databases.  

Following is an overview of the procedure to upgrade an existing LiveCycle ES4 SP1 server to AEM 6.3 Forms. For detailed instructions, see the documents listed at the end of the procedure.

  1. Before you upgrade:  

    1. Download the AEM 6.3 Forms on JEE installer from the Adobe Licensing Website (LWS). You require a valid Maintenance & Support contract to download the installer.

    2. Choose CRX Repository type to use. Only a few AEM Forms on JEE capabilities use CRX repository persistence to store content and assets. Install and configure CRX repository only if you plan to use such AEM Forms on JEE capabilities:

      • In LiveCycle ES4 SP1, the Correspondence Management, Forms Portal, HTML Workspace, and Process Reporting capabilities use crx-repository. If you did not use these capabilities in LiveCycle ES4 and plan not to use these capabilities in AEM Forms, then crx-repository is not required.
      • In AEM Forms, Adaptive Forms, Correspondence Management, HTML5 Forms (Known as Mobile Forms in LiveCycle ES4 SP1), Forms Portal, HTML Workspace, Process Reporting, Forms centric workflows on OSGi, capabilities use crx-repository. If you plan to use AEM Forms for these capabilities, then crx-repository is required.
      • You do not require crx-repository for AEM Forms Document Security.

      Moreover, repository type of LiveCycle and AEM Forms are different. For available repository types and related information, see Choosing a persistence type for an AEM Forms installation.   

    3. Create a backup of LiveCycle ES4 SP1 content and data:

      Create a backup of LiveCycle ES4 SP1 database, Global Data Storage (GDS), and crx-repository (not required for document security). If you're upgrading to MongoMK or RDBMK persistence, export LiveCycle ES4 SP1 correspondence management assets in a .cmp file and forms assets as an AEM package.

      Note:

      Before you take backup of the crx repository, change the credentials of the admin user to admin/admin. Perform the following procedure to change the password:

      1. Log in to Content Explorer as an administrator. The URL is http://[LiveCycle ES4 SP1 server]:[port]/lc/crx/explorer/
      2. Click User Administration. The user Administration window opens.
      3. Navigate to users\a\admin. Change the password of the administrator to admin.
      4. Take backup of the repository.

    4. Ensure your existing platform (that is, application server, database, operating system, Adobe Acrobat, third-party applications, and hardware) is supported for AEM 6.4 Forms on JEE. For information about supported hardware and software, refer to the supported platform combinations document.

      If you create a fresh instance of the database, import the data backed up in step 3 to the database. For information about how to import data to a database, see documentation of corresponding database vendor.

      Note:

      If you are using RDBMK persistence format, use single database for both repository persistence and document services running on AEM Forms on JEE.

  2. Perform the upgrade:

    1. Install AEM 6.3 Forms on JEE on a new server by running the installation program. The installer places all of the required files onto your computer, within one installation directory structure. 
    2. After installation is complete, run the Configuration Manager to configure various AEM Forms modules and set appropriate configurations. Along with configuring settings, it allows to specify the path of Global Data Storage (GDS) and crx-repository.  

      Note:

      On the Upgrade Task Selection screen, select the Upgrade from Adobe Experience Manager Forms 6.1.0 option. The Upgrade from Adobe Experience Manager Forms 6.1.0 option allows the configuration manager to upgrade from LiveCycle ES4 SP1 to AEM 6.3 Forms.

    3. (Not required for AEM Forms document security module) Upgrade and import the CRX repository to AEM 6.3 Forms server.

      Note:

  3. Perform the post-deployment tasks to verify login credentials, configure document services, correspondence management, document security, and more depending on your use case.

  4. Verify that the server is upgraded successfully:

    Perform a few routine operations on upgraded AEM Forms server to ensure that the server is upgraded successfully. You can fill and submit a few migrated forms or protect documents to ensure a successful upgrade.


This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy