|
4.4.2.1 Configuring LiveCycleNote: 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.
Note: 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.
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 ES4 screen, click Next.
On
the Upgrade Task Selection screen, ensure that Upgrade from LiveCycle ES2 and ES2.5, Upgrade from ADEP and Upgrade from LiveCycle ES3 are deselected.
Click Next.
If you are performing
a LiveCycle ES4 upgrade, review Upgrading to LiveCycle ES4 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.
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. Note: Some modules have technical
dependencies on other modules for proper configuration and functioning.
Configuration Manager displays a dialog and does not allow to proceed
further if mutually dependent modules are not selected. For example,
you must select Adobe LiveCycle Forms, Adobe LiveCycle Output, and Content
Repository modules if you are configuring Correspondence Management Solution.
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 Configuring LiveCycle EAR, Fonts, and GDSOn the Configure LiveCycle ES4 (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 ES4 (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 ES4 (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. The
default location is [LiveCycle root]/temp. Click Next to
continue.
On
the Configure LiveCycle ES4 (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 [LiveCycle root]/gds.
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.5 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.6 Configure CRXIn the CRX Configuration screen, specify the path
to the repository and click Configure to create the required
repository files at the specified location.
It configures the repository to bundle within the LiveCycle Core
EAR file.
Click Next to continue.
Note: 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 the CRX repository.
Note: Once the packages are configured, you cannot remove them by
re-running the Configuration Manager. For clean uninstallation of
deployed packages, you need to uninstall and delete the packages
using Package Manager.
4.4.2.7 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.8 Install verification samples ( Adobe® LiveCycle® Forms Standard 11, Adobe® LiveCycle® Mobile Forms 11, Adobe® LiveCycle® Output 11, and PDF Generator only)
On the LiveCycle ES4 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, adobe-mobileforms-ivs.ear, and adobe-forms-ivs-jboss.ear appear
only if you have selected respective modules on the Modules screen.
Note: Do not deploy the IVS EAR files to a production
environment.
4.4.2.9 Deploying LiveCycle EARs On the Deploy LiveCycle ES4 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.10 LiveCycle Database Initialization On the LiveCycle ES4 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.11 LiveCycle Server Information On the LiveCycle ES4
information screen, type the LiveCycle ES4 User ID and password,
and click Verify Server Connection. When the validation is
complete, click Next. Important: By
default, the LiveCycle ES4 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.12 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.13 LiveCycle Components DeploymentOn the LiveCycle ES4 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 ES4 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.14 Configuring LiveCycle Components On the Configure LiveCycle ES4 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.14.1 Configure 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.14.2 Configure 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.14.3 Configure 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.14.4 Configure Connector for Microsoft SharePoint On the Configure Adobe LiveCycle 11 Connector
for Microsoft SharePoint screen, do one of the following tasks: Deselect the Configure Adobe LiveCycle ES4 Connector for Microsoft SharePoint option
to manually configure Microsoft Sharepoint later, and then click Next.
Leave the Configure Adobe LiveCycle ES4 Connector for Microsoft SharePoint option
selected. Enter the required values, and then click Configure SharePoint
Connector. When complete, click Next.
4.4.2.14.5 Verifying Configuration for ECM Connectors On the Verify Configurations screen, do one
of the following tasks:
4.4.2.14.6 Configuring PDF GeneratorIn the Admin 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 Document Services 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.14.7 Configuring Reader Extensions Credential On 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 ES4 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.
4.4.2.15 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.
|
|
|
