|
4.4.2.1 Configuring LiveCycleNote: 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.
Note: Press F1 in Configuration Manager to view Help information
for the screen you are viewing. You can view the configuration progress
at any time by clicking View Progress Log.
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.
When prompted, select the language to use, and then click OK.
On the Welcome to Adobe LiveCycle ES3 screen, click Next.
On
the Upgrade Task Selection screen, ensure that Upgrade from LiveCycle ES Update 1,
and Upgrade from LiveCycle ES2 or LiveCycle ES2.5 are deselected.
If
you are performing a LiveCycle ES3 upgrade, review Upgrading to LiveCycle ES3 for JBoss Turnkey.
On
the Turnkey Mode screen, select Custom Mode and click Next to
proceed to the next section. Custom Mode allows you to customize
the system configuration and requires some additional knowledge.
On the Correspondence Management Solution Selection screen, Correspondence Management Solution 10.0.2 option
is selected by default. With this option selected, you will be presented
with the configuration screens to configure Correspondence Management
Solution.
Click Next to continue
Note: This screen
appears only when Correspondence Management Solution is installed.
4.4.2.2 Selecting modules On the Modules screen, ensure that the Adobe LiveCycle
modules that you want to upgrade are selected. By default, all the
modules that you select will be licensed with an Evaluation License.
Click Next.
4.4.2.3 Selecting Tasks On the Task Selection screen, ensure that all
the required tasks are selected, and then click Next. Note: The Configure Application Server and Validate Application Server Configuration tasks are not available for selection for JBoss turnkey. The JBoss turnkey method does not support these tasks because the application server is already configured for LiveCycle.
4.4.2.4 In-place or out-of-place upgradeSelect In-place upgrade or Out-of-place upgrade,
and then Click Next to continue configuring LiveCycle. Select
In-place upgrade, If you are upgrading to LiveCycle ES3 using your
existing LiveCycle application server instance, this upgrade is
considered in-place.Select Out-of-place upgrade when you are: Changing computers or updating your application server version
(major revision).
Moving from a 32-bit version of your application server to
a 64-bit version.
Upgrading from LiveCycle ES (version 8.2) WebLogic Turnkey
to a supported LiveCycle WebLogic platform combination.
4.4.2.5 Configuring LiveCycle EAR, Fonts, and GDSOn the Configure LiveCycle ES3 (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.
On the Configure LiveCycle ES3 (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.
On the Configure LiveCycle ES3 (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. Click Next to
continue.
On
the Configure LiveCycle ES3 (4 of 5) screen, accept the default
location for the Global document storage directory path,
or click Browse to specify the fully qualified path. Click Next to
continue.
The default location is [JBoss root]/server/lc_turnkey/svcnative/DocumentStorage
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.
4.4.2.6 Configuring Acrobat for PDF Generator(PDF Generator only) On the Configure Acrobat
For LiveCycle PDF Generator screen, click Configure to run
the configuration script. When complete, click Next.
On the Configure LiveCycle Summary screen, click Next.
4.4.2.7 Configure Correspondence Management SolutionNote: This screen appears only if Correspondence Management
Solution is installed.
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 screen,
specify the path to the content repository for Correspondence Management
Solution and click Configure to create the required repository
files at the specified location.
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.
It 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. 4.4.2.8 Configuring turnkey JBoss SSL On the Configure Turnkey JBoss SSL screen, add
the information to configure the SSL certificate and click Configure JBoss SSL,
when complete click Next. You can skip this step by
selecting the Skip Configuration and configure it later in LiveCycle
Configuration Manager.
Certificate Alias: The
alternate unique name that is used to reference the certificate
(for example, LiveCycleCert).
Keystore filename: The name of the keystore that is
assigned to store the keys and the certificate (for example, lces).
4.4.2.9 Installing verification samples ( Forms, Output, and Assembler only) On the
LiveCycle ES3 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 to 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
environment.
4.4.2.10 Undeploying the EAR filesIf you are deploying your LiveCycle EAR files to the same
application server instance that your previous LiveCycle environment
resides on, undeploy the previous EAR files from your application
server before you deploy the new LiveCycle EAR files. For JBoss,
delete the EAR files from the [jboss_root]/server/all/deploy
directory.Click Next to continue.
4.4.2.11 Deploying LiveCycle EARs On the Deploy LiveCycle ES3 EAR files screen,
select the EAR files you want to deploy to JBoss, click Deploy and
when complete, click Next. Note: During EAR
files Deployment to LiveCycle, certain errors may be displayed regarding
EARs being unable to locate the correct table. You may ignore these errors.
4.4.2.12 LiveCycle Database Initialization On the LiveCycle ES3 Database Initialization
screen, verify the host and port information, 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 completes successfully, and then
click Next. Do not skip this step.
Database initialization does not harm legacy data. 4.4.2.13 LiveCycle Server Information On the LiveCycle ES3
information screen, type the LiveCycle ES3 User ID and password,
and click Verify Server Connection. When the validation is
complete, click Next. Important: By
default, the LiveCycle ES3 User ID is administrator and
the password is password. After completing the initial
configuration, change the default password in Administration Console.
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.
4.4.2.14 Central Migration Bridge Service Deployment Configuration 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.
4.4.2.15 LiveCycle Components DeploymentOn the LiveCycle ES3 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.
On the LiveCycle ES3 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.
4.4.2.16 Configuring LiveCycle Components On the Configure LiveCycle ES3 Components screen,
select the LiveCycle modules to configure, and then click Next. The
screens that appear next depend on your selections on this screen.
4.4.2.16.1 Configuring Connector for EMC Documentum On the Specify Client for EMC Documentum
screen, do one of the following tasks: Deselect the Configure Connector for EMC Documentum Content Server option
to manually configure EMC Documentum later, and then click Next.
Leave the option selected, enter the appropriate version
and directory path, and then click Verify. When complete,
click Next and complete the tasks on the following screens:
On the Specify EMC Documentum Content Server Settings screen,
enter the required values and then click Next.
On the Configure Connector for EMC Documentum screen, click Configure Documentum Connector.
When complete, click Next.
4.4.2.16.2 Configuring Connector for IBM Content Manager On the Specify Client for IBM Content Manager screen,
do one of the following tasks: Deselect the Configure Connector for IBM Content Manager option
to manually configure IBM Content Manager later, and then click Next.
Leave the option selected, enter the appropriate directory
path, and then click Verify. When complete, click Next and
complete the tasks on the following screens:
On the
Specify IBM Content Manager Server Settings screen, enter the required
values and then click Next.
On the Configure Connector for IBM Content Manager screen,
click Configure IBM Content Manager Connector. When complete,
click Next.
4.4.2.16.3 Configuring Connector for IBM FileNet On the Specify Client for IBM FileNet screen,
do one of the following tasks: Deselect the Configure Connector for IBM FileNet Content Manager option
to manually configure IBM FileNet later, and then click Next.
Leave the option selected, enter the appropriate version
and directory path, and then click Verify. When complete,
click Next and complete the following screens:
On the Specify IBM FileNet Content Server Settings screen,
enter the required values and then click Next.
On the Configure Connector for IBM FileNet Process Engine
screen, enter the appropriate version (if enabled) and directory
path, and then click Verify. When complete, click Next.
On the Specify IBM FileNet Process Engine Server Settings
screen, enter the required values and then click Next.
On the Configure Connector for IBM FileNet screen, click Configure FileNet Connector. When
complete, click Next.
4.4.2.16.4 Configuring Connector for Microsoft SharePoint On 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.
4.4.2.16.5 Verifying Configuration for ECM Connectors On the Verify Configurations screen, do one
of the following tasks: If you are configuring the
connectors for the first time or have modified any of the configurations
on the previous screens, leave the Restart Application Server option
selected and click Validate Configurations. When successfully
validated, click Next.
If you wish to configure connectors later, deselect the Restart Application Server option
and click Validate Configurations. When successfully validated,
click Next.
4.4.2.16.6 Configuring PDF GeneratorIn the Administrator user credentials for native PDF conversions screen box,
enter the user name and password of a user with administrative privileges on
the server machine. Click Add user.
Add at least one
administrative user for Windows 2008 Server and Click Next.
Note: On Windows 2008 Server, disable User Account Control
(UAC) 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.
Click OK. Your changes become effective when the system is restarted.
In the LiveCycle PDF Generator System Readiness Test screen,
click Start to validate if the system has been configured
correctly for PDF Generator. Review the System Readiness Tool Report
and click Next.
4.4.2.16.7 Configuring Reader Extensions CredentialOn the Reader Extensions Credential Configuration screen,
specify the details that are associated with the Reader Extensions
credential that activates the module services. Note: You 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 click Next.
On Correspondence Management Solution Deployment screen,
specify the Admin user ID and password, and click Configure to
package modified web applications and copy them to the LiveCycle
EAR.
When the configuration is complete, click Next.
4.4.2.17 Importing samples On the LiveCycle ES3 Samples Import screen, perform
one of these actions: Click Import to import
the LiveCycle Samples, and then click Next.
To skip this step, select Skip LiveCycle Samples Import,
and click Next. You can import the samples later by restarting
Configuration Manager and choosing to import the samples.
Important: Do not import the LiveCycle Samples if either
of these options apply to your implementation:
If you are deploying LiveCycle to a production system. Importing
the samples creates users with default passwords, which may be a
security concern for your production environment.
If you are deploying the services for Connector for EMC Documentum
or Connector for IBM FileNet, you can import the samples into the Documentum
repository or FileNet object store after you configure, enable, and
activate the ECM to be the repository provider by using Administration Console.
4.4.2.18 Task summaryReview 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.
|
|
|
