5.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 .

    • (Optional) To enable FIPS, ensure that Enable Federal Information Processing Standards (FIPS) 140-2 cryptography is selected. Select this option only if you require the Federal Information Processing Standards (FIPS) to be enforced.

  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. The temporary directory must exist on every node of the cluster and path of the temporary directory must be same on every node of the cluster.
  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: If you leave the GDS directory field empty, AEM forms on JEE will create the directory in a default location in the application server directory tree. After you finish the configuration steps, you can access the location from administration console > Settings > Core System Settings > Configurations.
    Note: Ensure that GDS directory is accessible from all the nodes of the cluster. For Cluster, do not leave the directory field empty.
  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 .

Configure CRX

The CRX Configuration screen allows you to configure the CRX repository and install it into the adobe-livecycle-cq-author.ear EAR file.

  1. Specify the path to the repository. The default location is [aem-forms root] /crx-repository.

    Note: Ensure that the CRX repository path does not contain spaces and the content repository is available on all the nodes of the cluster. After the configuration is complete, copy the content repository from local node to all the nodes on the same location (as specified on the CRX configuration screen) .

  2. Select the repository type, as appropriate and keep a note of the following points:

    • CRX3 TAR is not supported in clustered deployments.

    • If selecting CRX3 Mongo DB, specify the Mongo database name and URL to the database. The format of the URL is: mongodb://<HOST>:<Port> .

      HOST: IP address of the machine running MongoDB.

      Port: Port number used for the MongoDB. The default port number is 27017.

    • CRX3 RDB is supported only with Oracle 12c or IBM DB2 10.5 databases. Selecting this option sets the CRX repository persistence to RDB MK (document MK) .

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

  4. 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.
Note: Clustered environments with relational databases are now supported for production use under a "gated" program. If you intend to use a relational database in a clustered environment, contact AEM Forms product team at forms_documents@adobe.com for approval. Also ensure that the mandatory patches are installed and configured.

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 DC Pro already installed or this step will fail.
Note: You should manually configure Acrobat for PDF generator on all the other nodes of the cluster. See 6.5 Configuring PDF Generator in the Post Deployment chapter.

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.
Note: Stop each JBoss Application Server instance of the cluster.

Copy CRX Content

Copy all the content of the [ aem-forms root ]/configurationManager/export/crx-quickstart/ directory to the location specified on the CRX Configuration screen on all the cluster nodes.

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 ( forms workflow only)

  • adobe-livecycle-cq-author.ear

  • (optional) adobe-assembler-ivs.ear

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

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

Perform the following steps to manually deploy EAR files from management Console

  1. Shut down all the nodes except the master node.

    Note: After the Configuration Manager completes configuring AEM forms, restart all the nodes of the cluster. Do not restart all the nodes simultaneously. Start these nodes one-by-one. For example, start node1 and wait for it to be up and running. After node 1 is up and running, start node 2.

  2. Copy the configured EAR files from [aem_root]\configurationManager\export to a local directory on the server.

  3. Open the management console, click Runtime, and click Manage Deployments. The default URL is http://<Ip_Address>:9990/console/ and the default port is 9990. A Content Repository window opens. It has options to Add, Remove, Assign, and Replace options.

  4. To deploy the EAR files

    1. Click Add, click Browse, and navigate to the local directory which contains EAR files. Select an EAR file to add, click Next, and click Save. The added EAR appears in the Content Repositorywindow.

    2. Repeat step 4a for all the EAR files.

    3. On the Content Repository page, select an EAR files one by one, and perform the following steps:

    4. On the select server groups, select the assign option, leave the Enable <ear file> option checked, and click Save. Value in the assignment column changes from 0 to 1.

    5. Repeat step 4c and 4d for all the Ear files.

    6. After all the EAR files are deployed, return to the configuration management window, and continue from the Initializing Adobe Experience Manager forms database section.

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 forms server. For detailed information about configuring the publish instance, see 6.4.2 Configure the Publish instance

Note: The data source definition files have to be modified to point to the database server and database. For more information, see Appendix - Manually Configuring Data Sources .
Important: Deploying the IVS EAR files to a production environment is not recommended.

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: Initialize the database against only one server of the cluster. Subsequent steps are performed only on initialized server.

  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.

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

    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.

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 .

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 .

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 Acrobat Reader DC extensions

On the Acrobat Reader DC extensions Credential Configuration screen, specify the details that are associated with the Acrobat Reader DC extensions credential that activates the module services:
Note: You can skip this step at this time by selecting Configure later using administration console . You can configure the Acrobat Reader DC 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

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.

Note: You will see a message on the screen to restart the server. However, do not immediately restart. Ensure that error.log is stable and all bundles (except signatures) are in active mode before you restart the server.
Click Finish to exit the Configuration Manager
Note: After the Configuration Manager completes configuring AEM forms, restart all the nodes of the cluster. Do not restart all the nodes simultaneously. Start these nodes one-by-one. For example, start node1 and wait for it to be up and running. After node 1 is up and running, start node 2.

// Ethnio survey code removed