4.3 Configuring and deploying AEM forms on JEE

Note: Press F1 in Configuration Manager to view Help information for the screen you are viewing.

Configuring AEM forms on JEE

  1. On the Configure Adobe Experience Manager forms (1 of 5) screen, click Configure and click Next when done.

  2. On the Configure Adobe Experience Manager forms (2 of 5) screen, set the directories that AEM forms on JEE will use to access fonts and then click Next.

    Click Edit configuration to change any values on this screen. This button is not available when the Configuration Manager is run for the first time, but is available on the second and subsequent runs of the Configuration Manager.
    • (Optional) To change the default location of the Adobe server fonts directory , type the path or browse to the directory.

    • To change the default location of the Customer fonts directory, click Browse or specify a new location for your customer fonts.

      Note: Your right to use fonts provided by parties other than Adobe is governed by the license agreements provided to you by such parties with those fonts, and is not covered under your license to use Adobe software. Adobe recommends that you review and ensure that you are in compliance with all applicable non-Adobe license agreements before using non-Adobe fonts with Adobe software, particularly with respect to use of fonts in a server environment.
    • (Optional) To change the default location of the System fonts directory , type the path or browse to the directory. To add more directories to the list, click Add .

  3. Click Browse on the Configure Adobe Experience Manager forms (3 of 5) screen to specify the Location of the temporary directory.

    Note: Ensure that the temporary directory is on the local file system. AEM forms on JEE does not support a temporary directory at a remote location.
    Note: If you do not specify the temporary directory, the default system-configured temp location is used.
  4. On the Configure Adobe Experience Manager forms (4 of 5) screen, click Browse to specify the path for the Global Document Storage (GDS) directory.
    Note: You must point to the existing GDS directory or copy its contents to the newly specified location.
  5. On the Configure Persistent Document Storage (5 of 5) screen, select the option for persistent document storage in addition to the GDS directory. Select one of the following:
    • Use GDS : Use the file system-based GDS for all persistent document storage. This option provides the best performance, and a single location for GDS.

    • Use database : Use the AEM forms on JEE database for storing the persistent documents and long-lived artifacts. However, the file-system based GDS is also required. Using the database simplifies backup and restore procedures.

    Click Configure to configure the EARs with this directory information and, after the configuration is complete, click Next .

Configuring your database

On the Adobe Experience Manager forms Database screen, provide the information about the instance of AEM forms on JEE database, so that Configuration Manager can connect to it.

Click Verify Connection to ensure that the information is valid and Configuration Manager can connect to the database, and then click Next to continue.

Note: The above information applies to the database AEM forms on JEE will connect to. This can be either your existing LiveCycle database (if supported), or a new one that you have already configured and migrated the existing LiveCycle data to. (See Preparing to Upgrade to AEM forms on JEE ).
Note: Ensure that the JDBC driver points to the correct database driver located inside [aem-forms root]/lib/db/<database> directory. If you are upgrading on a machine with a previous version of LiveCycle and are reusing the old configuration data, then the JDBC driver is pre-populated with the old incompatible driver jar from the previous installation. Select any other database in the Database Type list and re-select the desired database.

Configure CRX

The CRX Configuration screen allows you to configure the CRX repository and install it into the AEM forms on JEE Core EAR file.

The screen provides you the option to upgrade your existing LiveCycle CRX repository to the CRX repository for AEM forms on JEE or configure a separate CRX repository for AEM forms on JEE while retaining the LiveCycle repository.

On this screen:

  1. If you are upgrading your existing LiveCycle ES4 repository, select Do you want to upgrade existing LiveCycle ES4 SP1 CRX repository in CRX2 mode. Else, deselect the option.

  2. If you are upgrading your existing LiveCycle ES4 repository, specify the path to the existing LiveCycle repository. Else, specify a path different from the existing LiveCycle repository.

    Note: If you specify the path to the existing LiveCycle CRX repository while deselecting the option to upgrade, the LiveCycle repository might corrupt.
  3. If you are configuring a separate CRX repository, select the repository type, as appropriate. If selecting CRX3 Mongo DB, specify the Mongo database name and URL to the database.

  4. Optionally, select AEM Samples need to be installed to install AEM samples.

  5. Click Configure to create the required repository files at the specified location.

Note: If your AEM forms on JEE server is running remotely, select Server is running on remote host , and specify the path to the repository on the remote host.

Click Next to continue.

Note: Once the packages are configured, you cannot remove them by re-running the Configuration Manager. For clean uninstallation of deployed packages, you need to uninstall and delete the packages using Package Manager.

(Remote host only) CRX Configuration Summary

For a remote deployment, copy the content from the [ aem-forms root ]/configurationManager/export/crx-quickstart/ directory to the location on the remote host you specified on the CRX Configuration screen.

Configuring Acrobat for PDF Generator

(Windows only) On the Configure Acrobat For PDF Generator screen, click Configure to run the script that will configure Adobe Acrobat and required environment settings. Click Next when complete.
Note: This screen will perform the desired configuration only when Configuration Manager is running locally. You must have Adobe Acrobat XI Pro already installed or this step will fail.

Configuration Summary

On the Configure Adobe Experience Manager forms Summary screen, click Next . Configured archives are placed in the [aem-forms root] /configurationManager/export directory.

Deploying Adobe Experience Manager forms EARs

Without exiting Configuration Manager, manually deploy the Adobe Experience Manager forms EAR files to JBoss by copying the following files from the [aem-forms root] /configurationManager/export directory to directories as specified:
  • adobe-livecycle-native-jboss- [OS] .ear

  • adobe-livecycle-jboss.ear

  • adobe-workspace-client.ear ( Process Management only)

  • adobe-contentservices.ear (Content Services only)

  • adobe-livecycle-cq-author.ear

  • (optional) adobe-assembler-ivs.ear

  • (optional) adobe-forms-ivs-jboss.ear

  • (optional) adobe-output-ivs-jboss.ear

  • JBoss
    (Manually-configured JBoss, cluster)
    [appserver root]/standalone/deployments

    (Manually-configured JBoss, single server)
    [ appserver root]/server/standard/deploy

    (Adobe-preconfigured JBoss, single server)
    [appserver root]/standalone/deployments

    (Adobe-preconfigured JBoss, cluster)
    [ appserver root]/server/lc_<dbname>_cl/deploy

You can optionally deploy the Forms Standard, Output , Mobile Forms, and Assembler IVS EARs as well.

To create publish instance for Correspondence Management, deploy a dobe-livecycle-cq-publish.ear. Ensure that adobe-livecycle-cq-publish.ear is deployed on a different server outside of the this setup. Do not deploy adobe-livecycle-cq-publish.ear on LiveCycle server. For detailed information about configuring the publish instance, see 5.3.2 Configure the Publish instance

Important: Deploying the IVS EAR files to a production environment is not recommended.

If you are deploying Content Services on a cluster set up, refer to Setup for Content Services section in the Configuring Adobe Experience Manager forms Application Server Clusters Using Jboss to configure the required JVM arguments in the run.conf.bat/run.conf file for each JBoss Application Server instance prior to EAR deployment.

Initializing Adobe Experience Manager forms database

  1. On the Adobe Experience Manager forms Database Initialization screen, verify that the hostname and port number provided for your application server is correct and then click Initialize . The database initialization task creates tables in the database, adds default data to the tables, and creates basic roles in the database. When the initialization has completed successfully, click Next . Restart the application server manually when you are prompted to do so.
    Note: Do not skip this step or the upgrade will fail. This process does not harm the existing data.
  2. On the Adobe Experience Manager forms Information screen, enter Adobe Experience Manager forms User ID and Password whose default values are administrator and password respectively.

    As you are upgrading to Adobe Experience Manager forms, enter the administrator password of your previous LiveCycle installation.

    Click Verify Server Connection , and when complete, click Next .

    Note: If the server verification fails, restart the server but only when error.log gets stable and http://[server]:[port] /lc is accessible. If the verification fails yet again, restart the server again.
    Note: The server information that appears on this screen represents default values for the deployment.

    Verifying the server connection helps narrow troubleshooting in case failures occur in the deployment or validation. If the connection test passes but deployment or validation fails in the next few steps, connectivity issues can be eliminated from the troubleshooting process.

Adobe Experience Manager forms Server JNDI information

On the Adobe Experience Manager forms Server JNDI Information screen, enter the host name, port number, and JBoss client jar location for the JNDI server. Press F1 for more information. Click Text Connection to ensure that Configuration Manager can connect to the JNDI server. Click Next to continue.

Perform critical tasks before deployment

Click Start to allow Configuration Manager to perform critical tasks before deploying Adobe Experience Manager forms components and when finished, click Next .

Session ID Migration Errors

View and fix the errors that were encountered while migrating session IDs from you old instance of LiveCycle, and then click Next. It is important to fix these errors else you may encounter some failed workflow invocations post-upgrade.

Deploying Central Migration Bridge Service

On the Central Migration Bridge Service Deployment Configuration screen, if applicable, select the Include Central Migration Bridge Service in deployment in deployment option and then click Next .

Deploying Adobe Experience Manager forms components

  1. On the Adobe Experience Manager forms Component Deployment screen, click Deploy . The components that are deployed at this time are Java archive files that plug into the Adobe Experience Manager forms service container for purposes of deploying, orchestrating, and executing services. When the deployment has completed successfully, click Next .

  2. On the Adobe Experience Manager forms Component Deployment Validation screen, click Validate . When the validation has completed successfully, click Next .

Migrate Data

On the Migrate Data Essential to Adobe Experience Manager forms Operation screen, click Start and, when the migration is complete, click Next .

Configuring Adobe Experience Manager forms components

On the Configure Adobe Experience Manager forms Components screen, select the tasks to run with Configuration Manager, and click Next .
Note: (Upgrade only) If you are upgrading any Connectors for ECM module, do not select them on this screen. Only include them if you are licensing them for the first time in Adobe Experience Manager forms and proceed with the following steps as appropriate.

Connector for EMC Documentum

Note: In case of a remote Adobe Experience Manager forms deployment, you cannot configure the Connector for EMC Documentum using Configuration Manager.
  1. On the Specify Client for EMC Documentum screen, select Configure Connector for EMC Documentum Content Server , and specify the following settings. Enter the details, click Verify , and when complete, click Next to continue.

    • Choose EMC Documentum Client Version: Select the client version to use with the EMC Documentum Content Server.

    • EMC Documentum Client Installation Directory Path: Click Browse to select the directory path.

  2. On the Specify EMC Documentum Content Server Settings screen, enter the EMC Documentum Server details, and then click Next . Press F1 for information about the details you need to enter.

  3. On the Configure Connector for EMC Documentum screen, click Configure Documentum Connector . When completed, click Next .

  4. On the Required Manual Configurations for Connector for EMC Documentum screen, review and perform the manual steps listed and then click Next .

Connector for IBM Content Manager

Note: In case of a remote Adobe Experience Manager forms deployment, you cannot configure the Connector for IBM Content Manager using Configuration Manager.
  1. On the Specify Client for IBM Content Manager screen, select Configure Connector for IBM Content Manager , and enter a value for the IBM Content Manager Client Installation Directory Path. Click Verify and when complete, click Next to continue.

  2. On the Specify IBM Content Manager Server Settings screen, enter the details of the IBM Content Manager Server, and click Next .

  3. On the Configure Connector for IBM Content Manager screen, click Configure IBM Content Manager Connector . When complete, click Next .

  4. On the Required Manual Configurations for Connector for IBM Content Manager screen, review and perform the manual steps listed and then click Next .

Connector for IBM FileNet

Note: In case of a remote Adobe Experience Manager forms deployment, you cannot configure the Connector for IBM FileNet using Configuration Manager.
  1. On the Specify Client for IBM FileNet screen, select Configure Connector for IBM FileNet Content Manager , and specify the following settings.

    • Choose IBM FileNet Client Version: Select the client version that you want to use with the IBM FileNet Content Server.

    • IBM FileNet Client Installation Directory Path: Click Browse to select the directory path.
      Note: The validation of IBM FIleNet may fail if there are special characters, such as hyphen (-), underscore (_), comma (,), or dot (.) in the directory name containing the IBM FileNet client.

    Click Verify , and when complete, click Next to continue.

  2. On the Specify IBM FileNet Content Server Settings screen, enter the required details, and click Next .

  3. On the Specify Client for IBM FileNet Process Engine screen, enter the required details, and click Verify . When complete, click Next .

  4. On the Specify IBM FileNet Process Engine Server Settings screen, enter the required details and click Next .

  5. On the Configure Connector for IBM FileNet screen, click Configure FileNet Connector . When complete, click Next .

  6. On the Required Manual Configurations for Connector for IBM FileNet screen, review and perform the manual steps listed and then click Next .

Connector for Microsoft SharePoint

Note: In case of a remote Adobe Experience Manager forms deployment, you cannot configure the Connector for Microsoft SharePoint using Configuration Manager.

On the Configure Adobe Experience Manager forms Connector for Microsoft SharePoint screen, do one of the following tasks:

  • Deselect the Configure Adobe Experience Manager forms Connector for Microsoft SharePoint option to manually configure Microsoft Sharepoint later, and then click Next .

  • Leave the Configure Adobe Experience Manager forms Connector for Microsoft SharePoint option selected. Enter the required values, and then click Configure SharePoint Connector. When complete, click Next .

Note: You can skip this step if you want to configure the Connector for Microsoft SharePoint later using Administration Console.

Configuring Adobe Experience Manager forms Server for native file conversions

(PDF Generator only) On the Admin user credentials for native PDF conversions screen, enter the user name and password of a user with administrative privileges on the server computer, and then click Add user.
Note: You must add at least one administrative user for Windows 2008 Server. On Windows 2008 Server, User Account Control (UAC) must be disabled for the users you add. To disable UAC, click Control Panel > User Accounts > Turn User Account Control on or off and deselect Use User Account Control (UAC) to help protect your computer, then click OK . Restart the computer to apply these changes.

System readiness test for PDF Generator

On the Document Services PDF Generator System Readiness Test screen, click Start to validate if the system has been appropriately configured for PDF Generator. Review the System Readiness Tool Report and click Next. Note that the system readiness test fails if AEM forms on JEE is deployed on a remote machine.

Configuring Reader Extensions

On the Reader Extensions Credential Configuration screen, specify the details that are associated with the Reader Extensions credential that activates the module services:
Note: You can skip this step at this time by selecting Configure later using Adobe Experience Manager forms Administration Console . You can configure the Reader Extensions credential by using Administration Console after you complete the deployment. (After logging in to Administration Console, click Home > Settings > Trust Store Management > Local Credentials .)

Click Configure and then click Next .

Summary, and Next Steps

  1. Server restart required screen requires you to restart your application server for some configurations to take effect. When finished, click Next .

  2. Review the Configuration Manager task summary list and choose the appropriate options:

    • Select Launch Next Steps to view information about AEM forms on JEE users and administrative interfaces to launch an html page containing step-by-step instructions to start and use Adobe Experience Manager forms.

    Click Finish to exit the Configuration Manager

// Ethnio survey code removed