5.3 Configuring and deploying AEM forms on JEE

Configuring Adobe Experience Manager forms

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, click Next to accept the default directory locations, or click Browse to navigate to and change the directories that Adobe Experience Manager forms 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. Adobe Experience Manager forms 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, and click Next .

   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: You must point to the existing GDS directory or copy its contents to the newly specified location.

   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 AEM forms on JEE 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.

Note: In case of clustered deployment, you must copy the content from the [aem-forms root]/configurationManager/export/crx-quickstart/ directory to the specified location on all cluster node hosts.

Configuring Acrobat for PDF Generator

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

Configuring your application server and database

1. On the Application Server Configuration Details screen, provide the information for the fields (all fields are mandatory) and then click Verify Server Connection .

   Ensure that the the Deploy Type is set to Cluster.

   When the verification has completed successfully, click Next .

   Note: The Administration and Managed Servers’ listen addresses must match the values specified in the WebLogic administration console.
   Note: You must enter a fully qualified hostname as the Server Instance Name of the WebLogic application server. The hostname is case-sensitive. The default value of localhost will not work.
   Note: For WebLogic Cluster, provide Hostname of Admin Server and the Port Number.

2. On the Application Server Configuration Selection screen, select the tasks for Configuration Manager to perform, and click Next .

   If you prefer to configure the application server manually, ensure that all the tasks are deselected, then click Next .

   If you do not configure packaged JDBC modules, under the Configure Datasource section, select Globally-scoped datasources.

3. On the Server Settings Configuration screen (appears only if Configure Server Settings was selected) , provide the information for the fields, and then click Next .

   Note: On a WebLogic cluster, the paths for pop3.jar and the JDK must be same on all nodes. The pop3.jar is at <aem-forms_root>/lib/weblogic/pop3.jar
   Note: : If you are using UDP then multicast port can be any available port between 1025 and 65535. The multicast port must be unique to the Adobe Experience Manager forms cluster (that is, the port must not be used by any other cluster on the same network, any attempt to use the same port by any other cluster on the same network would result in bootstrap failure).
   Note: LCM does not configure - Dadobe.cache.multicast-address and -Dadobe.cache.bind-address jvm arguments. You may need to configure these arguments manually. See 6.1.2 Configuring server start arguments section for more details.

4. On the Configure Datasource JDBC Driver Classpath screen (appears if Configure Datasource option with Packaged JDBC Modules is selected) , provide the path for JDBC driver and click Next .

5. On the Datasource Configuration screen (appears only if Configure Datasource option with globally scoped datasources is selected) , provide the information for the fields and then click Test Database Connection . When the connection is tested successfully, click Next . Press F1 for details about the required information.

   You can choose to manually configure data sources rather than allowing Configuration Manager to configure them for you. To override automatic data source configuration, select Manually configure data source now before continuing , at the bottom of the screen.

   Without exiting Configuration Manager, go to the application server administration console, and configure data sources as described in Configuring database connectivity in Installing and Deploying Adobe Experience Manager forms for WebLogic guide.

   Note: For a weblogic cluster, the path of JDBC driver must be same for all the nodes of the cluster.

6. On the Application Server Configuration screen, click Configure . When the process is completed, click Next .

7. On the Package JDBC modules into Adobe Experience Manager forms EARs (1 of 2) screen (appears if Configure Datasource with Packaged JDBC modules option was selected) , provide JDBC configuration details and click Test Database Connection . When complete, click Next .

8. On the Package JDBC modules into Adobe Experience Manager forms EARs (2 of 2) screen (appears only if Configure Datasource with Packaged JDBC modules options was selected) , provide details to generate an encrypted database password for WebLogic . Use one of the following options:

   Use an existing WebLogic encrypted password

   Select this option if you already have an encrypted password for the database. You can use the WebLogic encryption utility to encrypt the password that you entered in the previous screen for database connection test.

   Generate WebLogic encrypted password

   Select this option to generate an encrypted password for your database and provide the required details. The plain text password that you entered in the previous screen for database connection test is automatically populated in the Password field. Click Encrypt Password to generate the encrypted database password.

   Important: This is the database password encrypted by WebLogic application server, and not the application server password.

   Click Configure to package the JDBC modules into Adobe Experience Manager forms EARs, and when complete, click Next .

9. Restart the Node Manager, Managed Server, and Admin Server.

10. On the Application Server Configuration Validation screen, select the tasks for validating and then click Validate . When the process is completed, click Next .

    Note: If you have packaged JDBC modules into Adobe Experience Manager forms EAR files, Configuration Manager will report failed datasource validation during application server configuration validation. You can ignore this message.
    Note: Datasource validation may fail if you are using globally-scoped datasource. In this case, restart your WebLogic server and re-validate the datasource.

Choose installation verification sample (IVS) EAR files

(Forms, Output, Mobile Forms, and Assembler only)On the Adobe Experience Manager forms Installation Verification Sample (IVS) EAR files screen, you can install three service-specific sample applications. Select I nclude IVS EARs in deployment set and click Next to install these sample files.

The ear files appear only if you have selected respective modules on the Modules screen.

Note: Do not deploy the IVS EAR files to a production environment.

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 AEM forms on JEE EARs

1. You must deploy the EAR only on the master node and keep other nodes in the shutdown status.

   In the Weblogic administration console, stop all managed servers running on slave nodes and keep only the managed server of the master node running.

   Note: After you have completed all configurations and have quit the Configuration Manager, ensure that you run one of the stopped managed servers, wait for it to start completely, and then run other stopped managed servers, one by one.

2. On the Deploy Adobe Experience Manager forms EARs screen, select the EAR files to deploy and then click Deploy . This operation may take several minutes to complete. When the deployment has completed successfully, click Next .

   Note: After this step, ensure that you stop the managed server, node manager, and admin server, and then start them in the reverse order. Ensure that a directory named adobe is created in [appserverdomain] after the restart. This is required so that the [appserverdomain]/null directory does not get created, which can lead to the run time issues. Delete the [appserverdomain]/null directory if it gets created.
   Note: Before restarting the server, ensure that AEM is up and running. If AEM is not up and running and the server is restarted, it may lead to the corruption of repository data. Perform the following steps to verify that AEM is up and running:

   1. Watch the error.log file for activity. Ensure that it is stable and no more action is performed. The default path of the error.log file is <aem-forms_root>/crx-repository/logs/error.log.

   2. In the browser window, open URL http://[host]:[port]/lc/system/console/bundles, and ensure that only one bundle is in the installed state.

   3. Restart the server.

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 only on one node 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.

   Note: After this step, ensure that you stop the managed server, node manager, and admin server, and then start them in the reverse order. Ensure that a directory named adobe is created in [appserverdomain] after the restart. This is required so that the [appserverdomain]/null directory does not get created, which can lead to the run time issues. Delete the [appserverdomain]/null directory if it gets created.

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 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 service container that is part of AEM forms on JEE for purposes of deploying, orchestrating, and executing services. Click View Progress Log to view the deployment progress and, when the deployment has completed successfully, click Next .

2. On the Adobe Experience Manager forms Component Deployment Validation screen, click Validate . Click View Progress Log to view the validation progress and, 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 .

Configure Connector for EMC® Documentum®

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 .

Configure Connector for IBM® Content 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 .

Configure Connector for IBM® Filenet

1. On the Specify Client for IBM FileNet screen, select Configure Client 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 . Press F1 for more information.

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 .. Press F1 for more information.

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 .

   Note: The server fails to start if the path to the jass.conf.WSI file contains any space. In this case, copy the file to another location to ensure there are no spaces in the path.

Configure Connector for Microsoft® SharePoint®

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 .

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 Adobe Experience Manager forms is deployed on a remote machine.

Configuring Acrobat Reader DC extensions

On the Adobe Experience Manager forms 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 AEM forms on JEE.

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.