|
4.1.1 General ConsiderationsYou 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.
Run
Configuration Manager with the UTF-8 locale if you want to specify
a content storage root directory having international characters.
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
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.
For
upgrades on the same operating system as your existing LiveCycle
installation, you can specify the existing GDS location in the Configuration
Manager. If you choose to change the directory, copy the contents
of the existing GDS directory to the new location before you perform
the Configure LiveCycle ES3 (4 of 5) step in Configuration Manager.
For more information, see Preparing to Upgrade to LiveCycle guide.
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 7 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
|
Import Samples
|
Yes
|
No
|
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 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 10 and Reader Extensions
10, function correctly. For example, if a signature appears to have
been created in the future, it will not validate.
Servers that require synchronization are database servers, LDAP
servers, HTTP servers and J2EE servers.
|
|
|
