5.5.2 Configuring LiveCycle using Partial Turnkey Custom Mode

1. If you are continuing from the LiveCycle installation, proceed to step 3; otherwise, navigate to the [LiveCycle root]\configurationManager\bin folder and run ConfigurationManager.bat.

2. When prompted, select the language to use, and then click OK.

3. On the Welcome to Adobe LiveCycle ES3 screen, click Next.

4. On the Upgrade Task Selection screen, ensure that Upgrade from LiveCycle ESU1, and Upgrade from LiveCycle ES2 or ES2.5 are deselected. If you are performing a LiveCycle ES3 upgrade, review the appropriate LiveCycle turnkey upgrade guide.

1. On Flexible Turnkey Installation screen, do one of the following tasks:

   • Leave the Skip dataSource configuration option deselected to configure the data source, and then click Next.

   • Select the Skip dataSource configuration option if you have already configured the data source, and click Next.

   This screen will appear only if you have already configured the datasource.

2. On the Datasource configuration screen, enter the appropriate information to configure the database connection string and click Test Database Connection to ensure that the connection is configured properly.

   Note: If the database server is not running or is not set up yet, you can still configure the data source; however, the Test Database Connection will result in a failure message.

3. On the Application Server configuration screen, click Configure, and then click Next.

1. On the Turnkey Mode screen, select Custom Mode and click Next to proceed to the next section. Custom Mode allows you to customize the system configuration and requires some additional knowledge.

2. On the Correspondence Management Solution Selection screen, select the Correspondence Management Solution and then click Next. This screen appears only if have already installed the Correspondence Management Solution.

On the Task Selection screen, ensure that all the available tasks are selected, and then click Next.

1. On the Configure LiveCycle (1 of 5) screen, click Configure and, when the EAR files have been configured, click Next. Depending on the number of modules that are included in the configuration, this process may take several minutes to complete.

2. On the Configure LiveCycle (2 of 5) screen, set the directories that LiveCycle will use to access fonts and then click Next.

   Edit the configuration only if you are required to change any of the values on this screen.

   • (Optional) To change the default location of the Adobe server fonts directory, type the path or browse to the directory. The default path is [LiveCycle root]/fonts.

   • In the Customer fonts directory box, you can choose to 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 in connection 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.

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

     Note: Any modification to the System fonts directory or Enable FIPS values made on this screen will not be configured during an upgrade process. You must manually update your system fonts directories and enable the FIPS option in Administration Console after configuration is complete. See “Core Configurations” in the LiveCycle Administration Help.

3. On the Configure LiveCycle (3 of 5) screen, accept the default location for the Location of the temporary directory, or enter the path or browse to it. Click Next to continue.

4. On the Configure LiveCycle (4 of 5) screen, accept the default location for the Global document storage directory path, or click Browse to specify the fully qualified path. Click Next to continue.

   The default location is [JBoss root]/server/lc_turnkey/svcnative/DocumentStorage

5. On the Configure Persistent Document Storage (5 of 5) screen, select either Use GDS or Use Database. Click Configure to configure the persistent document storage method and when the process has finished, click Next

1. (PDF Generator only) On the Configure Acrobat For LiveCycle PDF Generator screen, click Configure to run the configuration script. When complete, click Next.

2. On the Configure LiveCycle Summary screen, click Next.

On the Configure Turnkey JBoss SSL screen, add the information to configure the SSL certificate and click Configure JBoss SSL, when complete click Next.

You can skip this step if you have not installed Reader Extensions and configure it later in the Administration Console.

On the Deploy LiveCycle ES3 EAR files screen, select the EAR files you want to deploy to JBoss, click Deploy and when complete, click Next.

On the LiveCycle Database Initialization screen, verify the host and port information, 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 completes successfully, click OK on the dialog and manually restart the JBoss server and then click Next.

On the LiveCycle information screen, type the LiveCycle ES3 User ID and password, and click Verify Server Connection. When the validation is complete, click Next.

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.

Select Include Central Migration Bridge service in deployment if you are licensed to configure LiveCycle with Central Pro or Web Output Pak, and then click Next.

1. On the LiveCycle Component Deployment screen, click Deploy. The components 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. When the deployment has completed successfully, click Next.

2. On the LiveCycle Component Deployment Validation screen, click Validate. Configuration Manager validates that the Java archive files are deployed to and running on the LiveCycle server. When the validation is completed successfully, click Next.

On the Configure LiveCycle Components screen, select the LiveCycle modules to configure, and then click Next. The screens that appear next depend on your selection on this screen.

Review the Configuration Manager task summary list and select Next Steps to launch an html page containing information about LiveCycle user and administrative interfaces. Click Finish.