4.3 Configuring and deploying LiveCycle
If you plan to install
Correspondence Management Solution, ensure that you have run the
Correspondence Management Solution installer before running the Configuration
Manager. For more information, see Installing Correspondence Management Solution
On the Configure
LiveCycle ES3 (1 of 5) screen, click Configure and click Next when
On the Configure LiveCycle ES3 (2 of 5) screen, click Next
accept the default directory locations, or click Browse
navigate to and change the directories that LiveCycle will use to
access fonts, and then click Next
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
Click Browse on the Configure LiveCycle ES3 (3 of
5) screen to specify the Location of the temporary directory.
you do not specify the temporary directory, the default system-configured temp
location is used.
On the Configure LiveCycle ES3 (4 of 5) screen, click Browse
specify the path for the Global Document Storage (GDS) directory.
you leave the GDS directory field empty, LiveCycle will create the
directory in a default location in the application server directory
tree. After you finish the configuration steps, you can access the
location from Administration Console > Settings > Core System
Settings > Configurations.
On the Configure Persistent Document Storage (5 of 5) screen,
select the option for persistent document storage in addition to
the GDS directory. Select one of the following:
Use the file system-based GDS for all persistent document storage.
This option provides the best performance, and a single location for
Use database: Use the LiveCycle database for storing
the persistent documents and long-lived artifacts. However, the
file-system based GDS is also required. Using the database simplifies
backup and restore procedures.
Click Configure to
configure the LiveCycle EARs with this directory information and,
after the configuration is complete, click Next.
Configuring Acrobat for PDF Generator
On the Configure Acrobat For LiveCycle
PDF Generator screen, click Configure
to run the script that
will configure Adobe Acrobat and required environment settings.
Note: This screen will perform the
desired configuration only when Configuration Manager is running
locally. You must have Adobe Acrobat X already installed or this
step will fail.
LiveCycle Configuration Summary
On the Configure LiveCycle ES3 Summary screen, click Next.
Configured archives are placed in the [LiveCycle root]/configurationManager/export directory.
Configure Correspondence Management Solution
Important: If you are installing Correspondence
Management Solution on a non-Windows machine, ensure that you set
the ulimit (Open Files, -n) parameter to 8192. Otherwise,
the configuration on this steps might fail with an error.
In Correspondence Management Solution Configuration
specify the path to the content repository for Correspondence Management
Solution and click Configure
to create the required repository
files at the specified location. The default location is [LiveCycle root]
Note: (Non-turnkey custom mode only) If your
LiveCycle server is running remotely, select Server is running on remote host,
and specify the path to the content repository on the remote host.
configures the Correspondence Management Solution to bundle within
the LiveCycle Core EAR file.
Click Next to continue.
(Turnkey mode only)
A backup (adobe-jboss-core-ear.orig)
for the original LiveCycle Core EAR file is taken in the [LiveCycle
root]\deploy folder. You can restore the EAR file in case you want
to run the set up again without Correspondence Management Solution.
Correspondence Management Solution Configuration Summary
For a remote deployment, copy the content
from the [LiveCycle root
directory to the location on the remote host you specified on the
Correspondence Management Solution Configuration screen.
case of clustered deployment, you must copy the content from the [LiveCycle
root]/configurationManager/export/crx-quickstart/ directory to the specified
location on all cluster node hosts.
Configuring your application server and database
On the Application Server Configuration Details screen, provide
the information for the fields (all fields are mandatory) and then
click Verify Server Connection. When the verification has
completed successfully, click Next.
Note: If WebSphere
Administrative Security is off, User Name and Password fields can
be left blank.
Note: When using WebSphere Cluster or WebSphere
Network Deployment server to configure a standalone WebSphere Application
server, enter the port number of the deployment manager in the SOAP
On the Application Server Configuration Selection
screen, select the tasks for Configuration Manager to perform, and
On the Server Settings Configuration screen (appears only if Configure Server Settings was selected),
provide the information for the fields, and then click Next.
LCM does not configure configure -Dadobe.cache.multicast-address
arguments. You may need to configure these arguments manually.
the JVM properties
section for more details.
On the Datasource Configuration screen (appears only if Configure Datasource option is selected),
provide the information for the fields and then click Test Database Connection.
When the connection is tested successfully, click Next.
can choose to manually configure data sources rather than allowing Configuration
Manager to configure them for you. To override automatic data source
configuration, select Manually configure data source in the WebSphere Administrative Console now before continuing,
at the bottom of the screen.
Without exiting Configuration
Manager, go to the application server administration console, and
configure data sources as described in 9.5 Configuring the LiveCycle database connectivity in Installing LiveCycle
for WebSphere Server Guide.
default, Configuration Manager creates datasources at node level.
To set the datasource at the server level, see how to create a JDBC
provider for your database in 9 Appendix - Manually Configuring WebSphere
in the Installing and Deploying
LiveCycle for WebSphere guide.
On the Application Server Configuration screen, click Configure.
When the process is completed, click Next.
On the Application Server Configuration Validation screen,
select the tasks for validating and then click Validate and
select Yes on prompt to deploy adobe-lcm-lcmvalidator.ear. When
the process is completed, click Next.
Choose installation verification sample (IVS) EAR files
(Forms, Output, and Assembler only
On the LiveCycle Installation Verification Sample (IVS) EAR files
screen, you can install three service-specific sample applications.
Select Include IVS EARs in deployment set
and click Next
install these sample files.
adobe-output-ivs-jboss.ear and adobe-forms-ivs-jboss.ear appears
only if you selected respective modules in Modules screen.
Note: Do not deploy the IVS EAR files to a production
Deploying LiveCycle EARs
On the Deploy LiveCycle ES3 EARs screen, select the EAR files
to deploy, and then click Deploy
. This operation may take
several minutes to complete. When the deployment has completed successfully,
Note: (WebSphere only) When Configuration Manager has started the execution of the IBM WebSphere® JACL deployment scripts, you cannot stop the deployment even if you exit or cancel Configuration Manager prior to deployment completion. No user action is required because the product EARs will be successfully deployed.
default, Configuration Manager deploys the EAR files to the WebSphere default
virtual host, default_host. To deploy the EAR files
to a different virtual host, select the target host from the Virtual
To connect to the application server using a secure
port while running Configuration Manager, do the following tasks:
Add the crypto.jar file provided by IBM to the LiveCycle
Configuration Manager path.
Set the following JVM argument to disable hostname verification:
can connect to the application server using this workaround only
if you are using the default HTTPS port.
Initializing LiveCycle database
On the LiveCycle ES3 Database Initialization screen, verify
that the hostname and port number provided for your application
server is correct 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 has completed successfully, click Next
Restart the application server manually when you are prompted to
On the LiveCycle ES3 Information screen, enter LiveCycle ES3 User ID and Password whose
default values are administrator and password respectively.
Click Verify Server Connection,
and when complete, click Next.
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.
Deploying Central Migration Bridge Service
On the Central Migration Bridge Service Deployment Configuration
screen, if applicable, select the Include Central Migration Bridge Service in deployment
option and then click Next.
Deploying LiveCycle components
On the LiveCycle ES3 Component Deployment screen, click Deploy.
The components that are 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.
On the LiveCycle Component Deployment Validation screen,
click Validate. Click View Progress Log to view the
validation progress and, when the validation has completed successfully,
Configuring LiveCycle components
On the Configure LiveCycle ES3 Components screen, select
the tasks to run with Configuration Manager, and click Next.
LiveCycle Server JNDI information
On the LiveCycle Server
JNDI Information screen, enter the host name and port number for
the JNDI server. Provide location for Local Application Server Root
Directory, and Click Test Connection. When complete, click Next.
Adobe® LiveCycle® 10 Connector for EMC® Documentum®
On the Specify Client for EMC Documentum screen, select Configure Connector for EMC Documentum Content Server,
and specify the following settings. Enter the details, click Verify,
and when complete, click Next to continue.
Choose EMC Documentum Client Version: Select the client
version to use with the EMC Documentum Content Server.
EMC Documentum Client Installation Directory Path: Click Browse to select
the directory path.
Note: Configure Documentum 6.7 manually,
LCM does not contains support for Documentum 6.7.
On the Specify EMC Documentum Content Server Settings screen,
enter the EMC Documentum Server details, and then click Next.
Press F1 for information about the details you need to enter.
On the Configure Connector for EMC Documentum screen, click Configure Documentum Connector.
When completed, click Next.
On the Required Manual Configurations for Connector for EMC
Documentum screen, review and perform the manual steps listed and
then click Next.
Adobe® LiveCycle® 10 Connector for IBM® Content Manager
On the Specify Client for IBM Content
Manager screen, select Configure Connector for IBM Content Manager,
and enter a value for the IBM Content Manager Client Installation
Directory Path. Click Verify and when complete, click Next to
On the Specify IBM Content Manager Server Settings screen,
enter the details of the IBM Content Manager Server, and click Next.
On the Configure Connector for IBM Content Manager screen,
click Configure IBM Content Manager Connector. When complete,
On the Required Manual Configurations for Connector for IBM
Content Manager screen, review and perform the manual steps listed
and then click Next.
Adobe® LiveCycle® 10 Connector for IBM® FileNet
On the Specify Client for IBM FileNet screen, select Configure Client for IBM FileNet Content Manager,
and specify the following settings.
Choose IBM FileNet Client Version: Select
the client version that you want to use with the IBM FileNet Content
IBM FileNet Client Installation Directory Path: Click Browse to
select the directory path.
and when complete, click Next to continue.
On the Specify IBM FileNet Content Server Settings screen,
enter the required details, and click Next. Press F1 for
On the Specify Client for IBM FileNet Process Engine screen,
enter the required details, and click Verify. When complete,
On the Specify IBM FileNet Process Engine Server Settings
screen, enter the required details and click Next. Press
F1 for more information.
On the Configure Connector for IBM FileNet screen, click Configure FileNet Connector.
When complete, click Next.
On the Required Manual Configurations for Connector for IBM
FileNet screen, review and perform the manual steps listed and then
Adobe® LiveCycle® 10 Connector for Microsoft® SharePoint®
the Configure Adobe LiveCycle ES3 Connector for Microsoft SharePoint screen,
do one of the following tasks:
Deselect the Configure Adobe LiveCycle ES3 Connector for Microsoft SharePoint option
to manually configure Microsoft Sharepoint later, and then click Next.
Leave the Configure Adobe LiveCycle ES3 Connector for Microsoft SharePoint option
selected. Enter the required values, and then click Configure SharePoint
Connector. When complete, click Next.
Note: You can skip
this step if you want to configure the Connector for Microsoft SharePoint
later using Administration Console.
Configuring LiveCycle Server for native file conversions
(PDF Generator only)
On the Admin user credentials for native PDF conversions
enter the user name and password of a user with administrative privileges
on the server computer, and then click Add user.
Note: You must add at least one administrative user for
Windows 2008 Server. On Windows 2008 Server, User Account Control
(UAC) must be disabled for the users you add. To disable UAC, click Control Panel > User Accounts > Turn User Account Control on or off and
deselect Use User Account Control (UAC) to help protect your computer,
then click OK. Restart the computer to apply these changes.
System readiness test for PDF Generator
On the Adobe LiveCycle PDF Generator System Readiness Test screen,
click Start to validate if the system has been appropriately
configured for PDF Generator. Review the System Readiness Tool Report
and click Next. Note that the system readiness test fails
if LiveCycle is deployed on a remote machine.
Configuring LiveCycle Reader Extensions
On the Reader Extensions Credential Configuration screen,
specify the details that are associated with the Reader Extensions
credential that activates the module services.
can skip this step at this time by selecting Configure later using LiveCycle ES3 Administration Console.
You can configure the Reader Extensions credential by using Administration
Console after you complete the deployment. (After logging in to
Administration Console, click Home > Settings > Trust Store Management > Local Credentials.)
Click Configure and then
Configure Correspondence Management Solution
On Configure Correspondence Management Solution Deployment screen,
specify the User ID and password, and click Configure to
package modified web applications and copy them to the LiveCycle
When the configuration is complete, click Next.
Importing LiveCycle samples, Summary, and Next Steps
(Optional) On the LiveCycle ES3 Samples Import screen, click Import.
When the import has completed successfully, click Next or
select Skip LiveCycle ES3 Samples Import and then click Next to
import the samples at a later time.
not import the LiveCycle Samples in a production environment. These
samples create users with default passwords, which may be a security concern
for your production environment.
Review the Configuration Manager task summary list and choose
the appropriate options:
Click Finish to exit the