4.3 Configuring and deploying LiveCycle

Configuring LiveCycle

1. On the Configure LiveCycle ES3 (1 of 5) screen, click Configure and click Next when done.

2. On the Configure LiveCycle ES3 (2 of 5) screen, click Next to accept the default directory locations, or click Browse to navigate to and change the directories that LiveCycle will use to access fonts, and then click Next.

   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.

3. Click Browse on the Configure LiveCycle ES3 (3 of 5) screen to specify the Location of the temporary directory.

   Note: If you do not specify the temporary directory, the default system-configured temp location is used.
4. On the Configure LiveCycle ES3 (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 LiveCycle 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 LiveCycle EARs with this directory information and, after the configuration is complete, click Next.

Configuring Content Services (Deprecated)

1. On the Content Services Configuration screen, select the deploy type and specify the content storage root directory. The default path is [LiveCycle root]/lccs_data.

   Note: To upgrade correctly, the Content storage root directory location must either point to the location of Content storage root directory in the previous installation of LiveCycle, or must point to the new location where you have copied the content from your previous installation.

   To configure Content Services to use CIFS and FTP file servers, select Configure File Servers.

   To configure advanced settings, such as disk usage quota and email server settings, select Advanced Settings.

   Note: If you change the default location of the Content Storage Root directory during configuration, you must make note of the new location because no user interface is available to verify or change this location.

   Click Next.

2. On the Content Services File Server Configuration screen (appears only if you selected Configure File Servers option on the Content Services Configuration screen), you can configure Content Services to use CIFS and FTP servers. For more information, press F1. Click Next.

   Note: To enable CIFS on an IPv6 implementation of LiveCycle, you must edit the contentservices.war file after the configuration of the EAR files is completed. Update the EAR file and then proceed to the next step in Configuration Manager. See 5.10.1 Edit the contentservices.war file.
   Note: In addition to these steps in Configuration Manager, you must complete other manual configuration steps for Windows Server 2003 and Windows Server 2008. See the Server configuration for enabling CIFS section in the preparing guides for install, cluster, or upgrade, as applicable. The complete LiveCycle documentation is available at LiveCycle documentation website.

3. On the Content Services ES3 Advanced Settings Configuration screen (appears only if you selected Advanced Settings option on the Content Services Configuration screen), specify the settings that you want to configure and click Next. For more information, press F1.

4. On the Content Services Module Configuration screen, select the AMPs to merge, and then click Configure. You can also choose to package custom AMPs. After the configuration is complete, click Next. See Alfresco documentation for more information.

   Note: If you want to enable SharePoint clients to migrate to Alfresco CMS, you must add the SharePoint AMP: [LiveCycle root]\sdk\misc\ContentServices\adobe-vti-module.amp

   After you add this file, follow the steps detailed in 5.9 Configuring SharePoint client access.

Configuring Acrobat for PDF Generator

 On the Configure Acrobat for LiveCycle 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 X already installed or this step will fail.

LiveCycle Configuration Summary

 On the Configure LiveCycle ES3 Summary screen, click Next. Configured archives are placed in the [LiveCycle root]/configurationManager/export directory.

Configure Correspondence Management Solution

Important: If you are installing Correspondence Management Solution on a non-Windows machine, ensure that you set the ulimit (Open Files, -n) parameter to 8192. Otherwise, the configuration on this steps might fail with an error.

 In Correspondence Management Solution Configuration screen, specify the path to the content repository for Correspondence Management Solution and click Configure to create the required repository files at the specified location.

Note: (Non-turnkey custom mode only) If your LiveCycle server is running ‘ly, select Server is running on remote host, and specify the path to the content repository on the remote host.

It configures the Correspondence Management Solution to bundle within the LiveCycle Core EAR file.

Click Next to continue.

(Turnkey mode only) A backup (adobe-jboss-core-ear.orig) for the original LiveCycle Core EAR file is taken in the [LiveCycle root]\deploy folder. You can restore the EAR file in case you want to run the set up again without Correspondence Management Solution.

Correspondence Management Solution Configuration Summary

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

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

Configuring your application server and database

1. On the LiveCycle ES3 Database screen, provide the information about the instance of LiveCycle 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 LiveCycle 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 guide).
   Note: Ensure that the JDBC driver points to the correct database driver located inside [LiveCycle root]/lib/db/<database> directory. If you are upgrading on a machine with a previous version of LiveCycle installation 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.

2. On the Application Server Configuration Details screen, provide the information for the fields (all fields are mandatory) and then click Verify Server Connection. 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.

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

4. 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: LCM does not configure configure -Dadobe.cache.multicast-address and -Dadobe.cache.bind-address jvm arguments. You may need to configure these arguments manually. See Configuring server start arguments section for more details.

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

6. 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 LiveCycle for WebLogic guide.

7. On the Package JDBC modules into LiveCycle 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 LiveCycle 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 LiveCycle EARs, and when complete, click Next.

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

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 LiveCycle EAR files, Configuration Manager will report failed datasource validation during application server configuration validation. You can ignore this message.

Choose installation verification sample (IVS) EAR files

 On the LiveCycle IVS EARs Inclusion Confirmation screen, you can select the option to include the Installation Verification Sample (IVS) EAR files in the deployment set.

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

Deploying LiveCycle EARs

1. (In-place upgrade only) On the Undeploy LiveCycle ES EARs from the application server screen, review the information, perform the required task, and then click Next.

2. On the Deploy LiveCycle ES3 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.

Initializing LiveCycle database

1. On the LiveCycle ES3 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.

2. On the LiveCycle ES3 Information screen, enter LiveCycle ES3 User ID and Password whose default values are administrator and password respectively.

   As you are upgrading to LiveCycle ES3, enter the administrator password of your previous LiveCycle installation.

   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.

LiveCycle Server JNDI information

 On the LiveCycle ES3 JNDI Information screen, enter the host name and port number for the JNDI server. Click Verify Server 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 LiveCycle 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 option and then click Next.

Deploying LiveCycle components

1. On the LiveCycle ES3 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 LiveCycle 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 LiveCycle ES3 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 ECM Connectors

1. (Connectors for ECM) On the Migrate ECM form templates screen, do one of the following tasks and then click Start:

   • Select Skip Form Template Import and click Next to continue configuring LiveCycle without importing your form templates. You can run Configuration Manager again to import the templates after you configure your LiveCycle environment.

   • Deselect Skip Form Template Import and click Start to have Configuration Manager run a query that gets the form template information that exist in the ECM Connectors’ repository. Configuration Manager then returns the results on the subsequent screen, where you can select individual templates to import.

2. (Connectors for ECM if Skip Form Template Import deselected only) On the Migrate ECM form templates (Contd) screen, do the following optional tasks and then click Next:

   • Deselect the LiveCycle form templates if you do not wish to migrate from your existing LiveCycle environment.

   • In the Add additional form paths to migrate box, type the path to your custom form templates directory, or click Browse to locate it and then click Add. Include the object store name or repository name (according to your ECM) as follows:

     (IBM FileNet) /<ObjectStoreName>/<FormTemplatePath>

     (EMC Documentum) /<DocbaseName>/<FormTemplatePath>

     Note: During data migration, your existing form templates are not deleted from the ECM repository but are copied to the LiveCycle repository. Any form templates deselected at this time can be migrated later by running Configuration Manager again.

3. On the Migrate Data Essential to LiveCycle ES3 Operation screen, click Start and, when the migration is complete, click Next.

Configuring LiveCycle components

 On the Configure LiveCycle Components screen, select the tasks to run with Configuration Manager, and click Next.

Note: 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 LiveCycle and proceed with the following steps as appropriate.

Adobe® LiveCycle® 10 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.

     Note: Configure Documentum 6.7 manually, LCM does not contains support for Documentum 6.7.

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.

Adobe® LiveCycle® 10 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.

Adobe® LiveCycle® 10 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.

   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.

Adobe® LiveCycle® 10 Connector for Microsoft® SharePoint®

On the Configure Adobe LiveCycle ES3 Connector for Microsoft SharePoint screen, do one of the following tasks:

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

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

Configuring LiveCycle 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.

If you are upgrading from LiveCycle ES2, the Administrator User is pre-populated on the screen. You can continue to use the same credentials or replace it.

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

Configuring Reader Extensions

1. On the Default Reader Extensions Credential screen, verify that the alias for the default Reader Extensions credential is correct and then click Next.

   Note: This screen appears only when you are upgrading from LiveCycle ES Update 1, if no credential was configured with your previous installation of LiveCycle ES Update 1, then the following screen appears instead.

2. On the LiveCycle 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 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.

Configure Correspondence Management Solution

 On Correspondence Management Solution Deployment screen, specify the Admin user ID and password, and click Configure to package modified web applications and copy them to the LiveCycle EAR.

When the configuration is complete, click Next.

Importing LiveCycle samples, Summary, and Next Steps

1. (Optional) On the LiveCycle ES3 Samples Import screen, click Import. When the import has completed successfully, click Next or click Skip LiveCycle Samples Import and then click Next to import the samples at a later time.

   Important: Do not import the LiveCycle Samples in a production environment. These samples create users with default passwords, which may be a security concern for your production environment.

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

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

   • Select Launch Administartion Console to launch Administration Console.

   • Select Launch Next Steps to view information about LiveCycle users and administrative interfaces to launch an html page containing step-by-step instructions to start and use LiveCycle.

   Click Finish to exit the Configuration Manager