|
Note: Press F1 in
Configuration Manager to view Help information for the screen you are
viewing.
Configuring LiveCycleOn the Configure
LiveCycle ES4 (1 of 5) screen, click Configure and click Next when
done.
On the Configure LiveCycle ES4 (2 of 5) screen, click Next to
accept the default directory locations, or click Browse to
navigate to and change 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.
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. To add more directories to
the list, click Add.
(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.
Click Browse on the Configure LiveCycle ES4 (3 of
5) screen to specify the Location of the temporary directory.
Note: Ensure
that the temporary directory is on the local file system. LiveCycle does
not support a temporary directory at a remote location.
Note: If you do not specify the temporary directory,
the default system-configured temp location is used.
On the Configure LiveCycle ES4 (4 of 5) screen, click Browse to
specify the path for the Global Document Storage (GDS) directory,
and click Next. Note: If
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.
Note: You
must point to the existing GDS directory or copy its contents to
the newly specified location.
Note: Ensure that GDS directory
is accessible from all the nodes of the cluster. For Cluster, do
not leave the directory field empty.
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 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
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. Click Next when
complete. Note: This screen will perform the desired configuration
only when Configuration Manager is running locally. You must have
Adobe Acrobat XI Pro already installed or this step will fail.
Note: You
should manually configure Acrobat for PDF generator on all the other
nodes of the cluster. See 8.6 Configuring PDF Generator in the Post Deployment chapter.
LiveCycle Configuration Summary On the Configure LiveCycle ES4 Summary screen, click Next.
Configured archives are placed in the [LiveCycle root]/configurationManager/export directory.
Configure CRX The CRX Configuration
screen allows you to configure the CRX repository and install it
into the LiveCycle Core EAR file. On this screen, specify the path
to the repository and click Configure to create the required
repository files at the specified location. If you are using a custom
path for the repository, ensure that the file system already contains
custom directory. Note: (Non-turnkey only) If your LiveCycle
server is running remotely, select Server is running on remote host,
and specify the path to the repository on the remote host.
Click Next to
continue.
Note: Ensure that the CRX repository
path does not contain spaces and the content repository is available
on all the nodes of the cluster. After the configuration is complete,
copy the content repository from local node to all the nodes on
the same location (as specified on the CRX configuration screen)
.
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.
(Remote host only) CRX Configuration Summary For a remote deployment, copy the content from the [ LiveCycle root]/configurationManager/export/crx-quickstart/
directory to the location on the remote host you specified on the
CRX Configuration screen. Note: In 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 databaseOn 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: The Administration
and Managed Servers’ listen addresses must match the values specified
in the WebLogic Administration Console.
Note: You must enter
a fully qualified hostname as the Server Instance Name of the WebLogic
application server. The hostname is case-sensitive. The default
value of localhost will not work.
Note: For
WebLogic Cluster, provide Hostname of Admin Server and the Port
Number.
On the Application Server Configuration Selection
screen, select the tasks for Configuration Manager to perform, and
click Next.
If you prefer to configure
the application server manually, ensure that all the tasks are deselected,
then click Next.
On the Server Settings Configuration screen (appears only if Configure Server Settings was selected),
provide the information for the fields, and then click Next.
Note: On a WebLogic cluster, the paths for pop3.jar and the JDK must be same on all nodes.
Note: :
If you are using UDP then multicast port can be any available port
between 1025 and 65535. The multicast port must be unique to the
LiveCycle cluster (that is, the port must not be used by any other
cluster on the same network, any attempt to use the same port by
any other cluster on the same network would result in bootstrap
failure).
Note: LCM does not configure - Dadobe.cache.multicast-address and -Dadobe.cache.bind-address jvm
arguments. You may need to configure these arguments manually.
See 6.1.2 Configuring server start arguments section for more details.
On the Configure Datasource JDBC Driver Classpath screen (appears if Configure Datasource option with Packaged JDBC Modules is selected),
provide the path for JDBC driver and click Next.
On the Datasource Configuration screen (appears only if Configure Datasource option with globally scoped datasources is selected),
provide the information for the fields and then click Test Database Connection.
When the connection is tested successfully, click Next. Press
F1 for details about the required information.
You 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 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 Configuring database
connectivity in Installing and Deploying LiveCycle for WebLogic guide.
On
the Application Server Configuration screen, click Configure.
When the process is completed, click Next.
On the Package JDBC modules into LiveCycle EARs (1 of 2)
screen (appears if Configure Datasource with Packaged JDBC modules option was selected), provide
JDBC configuration details and click Test Database Connection. When
complete, click Next.
On the Package JDBC modules into LiveCycle EARs (2 of 2)
screen (appears only if Configure Datasource with Packaged JDBC modules options was selected), provide
details to generate an encrypted database password for WebLogic
. Use one of the following options: - Use an existing WebLogic encrypted password
- Select this option if you already have an encrypted password
for the database. You can use the WebLogic encryption utility to
encrypt the password that you entered in the previous screen for
database connection test.
- Generate WebLogic encrypted password
- Select this option to generate an encrypted password for
your database and provide the required details. The plain text password
that you entered in the previous screen for database connection
test is automatically populated in the Password field. Click Encrypt Password to
generate the encrypted database password.
Important: This is the database password encrypted by
WebLogic application server, and not the application server password.
Click Configure to
package the JDBC modules into LiveCycle EARs, and when complete,
click Next.
Restart the Node Manager.
On the Application Server Configuration Validation screen,
select the tasks for validating and then click Validate.
When the process is completed, click Next.
Note: If you have packaged JDBC modules into LiveCycle EAR files, Configuration Manager will report failed datasource validation during application server configuration validation. You can ignore this message.
Note: Datasource
validation may fail if you are using globally-scoped datasource. In
this case, restart your WebLogic server and re-validate the datasource.
Choose installation verification sample (IVS) EAR files (Forms, Output, Mobile Forms, and Assembler
only)On the LiveCycle ES4 Installation Verification Sample (IVS)
EAR files screen, you can install three service-specific sample
applications. Select I nclude IVS EARs in deployment set and
click Next to install these sample files. The ear files
appear only if you have selected respective modules on the Modules
screen.
Note: Do not deploy the IVS EAR files to
a production environment.
Copy CRX ContentCopy
all the content of the [LiveCycle root]/configurationManager/export/crx-quickstart/
directory to the location specified on the CRX Configuration screen on
all the cluster nodes.
Deploying LiveCycle EARs On the Deploy LiveCycle ES4 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, click Next. Note: After
this step, ensure that you stop the managed server, node manager, and
admin server, and then start them in the reverse order. Ensure that
a directory named adobe is created in [appserverdomain] after the
restart. This is required so that the [appserverdomain]/null directory
does not get created, which can lead to the run time issues. Delete
the [appserverdomain]/null directory if it gets created.
Initializing LiveCycle databaseOn the LiveCycle ES4 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
do so.
Note: Initialize the database
only on one node of the cluster. Subsequent steps are performed
only on initialized server.
On the LiveCycle ES4 Information screen, enter LiveCycle ES4 User ID and Password whose
default values are administrator and password respectively.
Click Verify Server Connection,
and when complete, click Next.
Note: 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.
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 componentsOn the LiveCycle ES4 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. Click View Progress Log to
view the deployment progress and, when the deployment has completed
successfully, click Next.
On the LiveCycle ES4 Component Deployment Validation screen,
click Validate. Click View Progress Log to view the
validation progress and, when the validation has completed successfully,
click Next.
Configuring LiveCycle components On the Configure LiveCycle 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. Click Verify Server Connection to ensure that
Configuration Manager can connect to the JNDI server. Click Next to continue.
Configure Adobe® LiveCycle® 11 Connector for EMC® Documentum®Note: In case of a remote LiveCycle deployment,
you cannot configure the Connector for EMC Documentum using Configuration
Manager.
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.
Configure Adobe® LiveCycle® 11 Connector for IBM® Content ManagerNote: In case of a remote LiveCycle deployment,
you cannot configure the Connector for IBM Content Manager using
Configuration 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
continue.
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,
click Next.
On the Required Manual Configurations for Connector for IBM
Content Manager screen, review and perform the manual steps listed
and then click Next.
Configure Adobe® LiveCycle® 11 Connector for IBM® FilenetNote: In case of a remote LiveCycle deployment, you
cannot configure the Connector for IBM FileNet using Configuration
Manager.
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
Server.
IBM FileNet Client Installation Directory Path: Click Browse to
select the directory path.
Note: The validation of IBM FIleNet
may fail if there are special characters, such as hyphen (-), underscore
(_), comma (,), or dot (.) in the directory name containing the
IBM FileNet client.
Click Verify, 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
more information.
On the Specify Client for IBM FileNet Process Engine screen,
enter the required details, and click Verify. When complete,
click Next.
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
click Next.
Note: The server fails to start if the path
to the jass.conf.WSI file contains any space. In this case, copy
the file to another location to ensure there are no spaces in the
path.
Configure Adobe® LiveCycle® 11 Connector for Microsoft® SharePoint®Note: In case of a remote LiveCycle deployment,
you cannot configure the Connector for Microsoft SharePoint using
Configuration Manager.
On the Configure Adobe LiveCycle
ES4 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.
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 screen,
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 Document Services 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 Reader Extensions On the LiveCycle 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 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.
Summary, and Next Steps Review the Configuration Manager task summary list and choose
the appropriate options:
Click Finish to
exit the Configuration Manager
|
|
|
