4.4 Configuring LiveCycle ES4

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. If you are prompted to choose to use existing configuration data, click OK.

4. On the Welcome to Adobe LiveCycle ES4 screen, click Next.

5. On the Upgrade Task Selection screen, select the appropriate option for your existing version of LiveCycle, and then click Next.

 On the Shutdown previous LiveCycle screen, click the button to stop the JBoss service for your previous LiveCycle version, and click Next.

 On the Migrate Custom Data Sources screen, if you had created custom datasources after installing your previous instance of LiveCycle, select the Import datasources option, click Start to import them. When complete, click Next.

If you do not have custom data sources, leave the option deselected and click Next.

1. On the Configure LiveCycle ES4 (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 ES4 (2 of 5) screen, set the directories that LiveCycle 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. The default path is [LiveCycle root]/fonts

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

   • (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.

3. On the Configure LiveCycle ES4 (3 of 5) screen, accept the default location for the Location of temporary directory, or enter the path or click Browse to specify the path. The default location is [LiveCycle root]/temp. 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. If your previous LiveCycle version did not use the default GDS directory, for a successful upgrade you must specify a directory for LiveCycle ES4, and copy the contents of the previous GDS directory to this new location.

   Note: If you migrated GDS contents to the LiveCycle ES4 installation in the step 4.4.6 Migrating Global Document Storage directory, do not modify the prepopulated value of Global document storage directory path.

5. On the Configure Persistent Document Storage (5 of 5) screen, select either Use GDS or Use database, and then click Configure.

   • 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 persistent documents and long-lived artifacts. However, the file-system based GDS is also required. Using the database simplifies backup and restore procedures.

   Click Next.

1. On the Content Services Configuration screen, specify location to store contents. The default path is [LiveCycle root]\lccs_data.

   Note: This location must be the content storage root directory from your previous installation of LiveCycle. If you want to specify a new location then you must copy the contents from content storage root directory configured in your previous LiveCycle installation to this new location before proceeding further.

   You may choose Configure File Servers (CIFS and FTP) to configure file servers, and Advanced Settings to configure settings, such as inbound e-mail server and disk usage. Click Next.

2. On the Content Services File Server Configuration screen, set the parameters that CIFS and FTP Server requires. This screen appears only if you select Configure File Servers option on Content Services Configuration screen.

   • FTP Server Port: To enter the port number, ensure that the Enable FTP Server option is selected. The Port number that FTP server uses for communication. Default port number is 8021.

   • CIFS Server Name: To enter the CIFS server name, ensure that the Enable CIFS option is selected. The Content Services repository will be accessible by the server name mentioned in CIFS Server Name box. For example, cifs-servername.

   • Choose the CIFS Server Implementation: Choose Java (Socket Based) or Windows Native (DLL Based).

     If your CIFS Implementation type is Java (Socket Based), then enter the following details:

     • Alternate IP Address: IP Address of the CIFS server.

     • Primary WINS Server IP Address: The Windows Internet Name Service (WINS) server to dynamically map the IP address to the computer names. It is used to resolve the local domain. It is the IP address of the Primary WINS server. Its value can be found using the ipconfig/all command.

     • Secondary WINS Server IP Address: The IP address of the secondary WINS server. Its value can be found using ipconfig/all command.

     • Broadcast IP Address: The broadcast IP address which is used to resolve the local domain.

     If your CIFS Implementation type is Windows Native (DLL Based):

     • System Path to copy CIFS dlls: Provide a location to where Configuration Manager can copy CIFS dll files.

   Click Next.

3. On the Content Services Advanced Settings Configuration screen, select required options. You can limit disk usage quota and provide settings for inbound email server on this screen. This screen appears only if you select Advanced Settings in Content Services Configuration screen.

   • Propagate Content Services events to LiveCycle: Select if Content Services events like create, delete, update, check in and check-out events must be propagated to LiveCycle processes.

   • Enable Auditing in Content Services: When selected, application or user interactions with Content Services repository can be recorded.

   • Enable Disk Usage Quota: Specify, in megabytes, the disk space quota for a user in Content Services. If a user attempts to add more data than the quota specified, an error message is displayed.

   • Inbound email server settings: Settings of the internal email server to which messages are directed. Further settings:

     • Mail Server Domain: The domain of the inbound email server.

     • Mail Server Port: The port that the email server listens to, for incoming connections. The defaults port number is 25.

     • Allowed Email Senders: The domains of allowed email senders.

     • Blocked Email Senders: The domains of blocked email senders.

     • Unknown User

   Click Next.

4. On the Content Services Module Configuration screen, select the AMPs to package in Content Services. You can package custom AMPs in Content Services by selecting Do you want to package your own AMPs in Content Services? Click Configure to configure Content Services module. When complete, click Next.

   Important: If you chose to package custom AMPs in your previous version of LiveCycle, then you must specify the AMPs again to re-package them in LiveCycle EAR.

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.

1. On the Adobe LiveCycle ES4 Database screen, specify information about the database you are going to use with LiveCycle, and then click Verify Connection to test the connection. Click Next.

2. On the Previous LiveCycle Database screen, specify information about the LiveCycle database that you are upgrading from, and then click Verify Connection to test the connection. Click Next.

   Note: This screen appears only if you have chosen the Prepare to upgrade existing installation to Adobe LiveCycle ES4 option on the Preparation for Upgrade screen.

3. On the Upgrade MySQL Relational Database screen, click Upgrade MySQL to migrate the old LiveCycle data to the new MySQL database.

   Note: This screen appears only if you have chosen the Prepare to upgrade existing installation to Adobe LiveCycle ES4 option on the Preparation for Upgrade screen.

In the CRX Configuration screen, specify the path to the repository and click Configure to create the required repository files at the specified location.

It configures the repository to bundle within the LiveCycle Core EAR file.

Click Next to continue.

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

 On the LiveCycle Server Information screen, type the administrator user ID and password from your previous version of LiveCycle, 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.

 On the LiveCycle ES4 JNDI Information screen, specify the JNDI server host name and port number and click Verify Connection. When verified, click Next.

 On the Perform critical tasks before component deployment screen, click Start to perform the tasks required before components are deployed. When complete, click Next.

 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.

 On Central Migration Bridge Service Deployment Configuration screen, 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 ES4 Component Deployment screen, click Deploy. The components deployed at this time are Java archive files that plug into the LiveCycle service container for purposes of deploying, orchestrating, and executing services. When the deployment has completed successfully, click Next.

2. On the LiveCycle ES4 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 Migrate Data Essential to LiveCycle ES4 Operation screen, click Start to migrate the data from your previous LiveCycle environment. When complete, click Next.

This step involves copying forms, form data, processes, preferences, file type settings, job options, security settings, watched folders, and email job sources (depending on the product you are upgrading), custom fonts, and documents in the GDS directory.

 Restart the JBoss application server as specified on the Server Restart Required screen. This is necessary as some configurations are applied only after the server is restarted. Click Next.

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.