|
4.1.1 General ConsiderationsFor 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.
For MySQL, download and install the necessary JDBC drivers.
If
you have manually configured JBoss, the database drivers have to
be downloaded and copied in the [appserver root]/server/<profile_name>/lib
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.
4.1.2 CLI versus GUI versions of Configuration ManagerThis section describes the GUI version of Configuration
Manager. For instructions about using the command line interface
(CLI) version of Configuration Manager, see 9 Appendix - Configuration Manager Command Line Interface.
LiveCycle configuration task
|
Configuration Manager GUI
|
Configuration Manager CLI
|
Manual
|
|---|
Configure LiveCycle
|
Yes
|
Yes
|
No
|
Initialize LiveCycle database
|
Yes
|
Yes
|
No
|
Validate LiveCycle Server connection
|
Yes
|
Yes
|
No
|
Deploy LiveCycle components
|
Yes
|
Yes
|
No
|
Validate LiveCycle component deployment
|
Yes
|
Yes
|
Yes
|
Configure LiveCycle components
|
Yes
|
Yes
|
Yes
|
4.1.3 Considerations for JBoss application serverThe Configure Application Server, Validate Application Server Configuration, and Deploy LiveCycle EARs tasks
are not available for JBoss.
You must configure JBoss and deploy the LiveCycle EARs manually
as described in the 5 Deploying LiveCycle to JBoss.
4.1.4 Set the date, time, and time zoneSetting 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).
|
|
|
