5.1 Considerations when configuring and deploying LiveCycle

• For IPv6, run IPv6 LiveCycle Configuration Manager. For detailed information, see LiveCycle IPv6 support section in prepare to install guide.

• You can override the default font for the Configuration Manager by adding the following JVM argument in [LiveCycle root]\configurationManager\bin\ConfigurationManager.bat (Windows) or [LiveCycle root]\configurationManager\bin\ConfigurationManager.sh (Linux, UNIX):

  -Dlcm.font.override=<FONT_FAMILY _NAME>

  For example:

  -Dlcm.font.override=SansSerif

  Restart the Configuration Manager after adding the JVM argument.

• During configuration, if you must reset the data in Configuration Manager by using the Reset to Default option, ensure that you relaunch the Configuration Manager. Otherwise, you may encounter some missing configuration screens.

• During configuration, you must provide the location of the JDBC drivers for your database. The Oracle, SQL Server, and DB2 drivers are in the [LiveCycle root]/lib/db/[database] directory.

• Temporary directory: Do not specify a shared network directory as your temporary directory on cluster configurations. It is recommended to use local directory as a temporary directory. The temporary directory should exist on every node of the cluster and the path of the temporary directory should be same for every node of the cluster.

• Global Document Storage (GDS) directory: Specify the GDS directory that meets the requirements outlined in the Preparing to Install (Single Server or Server Cluster). For latest documentation, see http://www.adobe.com/go/learn_lc_documentation_11.

• On cluster environments, several steps need to be performed manually in addition to the automatic configuration that Configuration Manager performs.

This section describes the GUI version of Configuration Manager. For instructions about using the command line interface (CLI) version of Configuration Manager, see 12 Appendix - Configuration Manager Command Line Interface.

• If you plan to use Configuration Manager to configure the application server or deploy to the application server, the application server must be manually started and running prior to running the Configuration Manager. You can also configure an application server that is installed on a different computer.

• Ensure that you have assigned listen addresses for Administration Server, Node Manager, and Managed Servers, before running Configuration Manager on dual stack machines (IPV6 and IPV4 supported). If you have not already done this, assign listen addresses and restart each of them. For more information, see the Configuring a WebLogic Server section in the Preparing to Install LiveCycle guide.

• To secure the data sources, select Package JDBC Modules into LiveCycle EARs (secure datasources).

  Note: Do not select this task if your LiveCycle implementation is required to handle XML Forms. Alternatively, perform the steps in the Technote at http://kb2.adobe.com/cps/844/cpsid_84435.html to secure access to JNDI artifacts on your WebLogic application server.

• Configuration Manager does not support deployment or undeployment of EAR files with custom file names. If your EAR files use a custom file name, you must manually deploy and undeploy them to the application server.

• If you are configuring a remote application server, ensure that an application server is also installed on the same computer as Configuration Manager so that Configuration Manager can use the application server library files.

• You cannot configure settings for IPv6-based clusters using Configuration Manager.

  Note: If your WebLogic cluster is IPv6-based, see 6 Manually Configuring a WebLogic Server Cluster

• It is recommended that you have local server fonts and customer fonts directories at the same path on each node in the cluster. Having shared fonts directories instead of local fonts directories may cause performance issues.

Setting the date, time, and time zone on all servers connected to your LiveCycle environment will ensure that time-dependent modules, such as Adobe® LiveCycle® Digital Signatures 11 and Reader Extensions 11, function correctly. For example, if a signature appears to have been created in the future, it will not validate.

Servers that require time synchronization are database servers, LDAP servers, HTTP servers and J2EE servers (Application servers).