|
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, 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.
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. 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.
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 (Windows only) 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.
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: 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.
Deploying LiveCycle EARs Without
exiting Configuration Manager, manually deploy the LiveCycle EAR files
to JBoss by copying the following files from the [LiveCycle root]/configurationManager/export
directory to directories as specified: adobe-livecycle-native-jboss-[OS].ear
adobe-livecycle-jboss.ear
adobe-workspace-client.ear ( Adobe® LiveCycle® Process Management
11 only)
- Manually-configured JBoss
- [appserver root]/server/standard/deploy
- Adobe-preconfigured JBoss on single server
- [appserver root]/server/lc_<db name>/deploy
You can optionally
deploy the Adobe® LiveCycle® Forms Standard 11, Adobe® LiveCycle®
Output 11, Adobe® LiveCycle® Mobile Forms, and Assembler IVS EARs
as well.
To create publish instance for Correspondence Management,
deploy adobe-livecycle-cq-publish.ear. Ensure that adobe-livecycle-cq-publish.ear is
deployed on a different server. Do not deploy adobe-livecycle-cq-publish.ear on
LiveCycle server. For detailed information about configuring the
publish instance, see 6.3.2 Configure the Publish instance
Important: Deploying the IVS EAR files to a production
environment is not recommended.
Start JBoss to ensure
the LiveCycle applications start successfully and return to Configuration
Manager.
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 against only one server 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 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. 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 ES4 Server
JNDI Information screen, enter the host name, port number, and JBoss
client jar location for the JNDI server. Press F1 for more information.
Click Verify Server Connection to ensure that Configuration Manager
can connect to the JNDI server. Click Next to continue.
Connector for EMC DocumentumNote: 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.
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.
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 Connector for IBM FileNet Content Manager,
and specify the following settings.
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.
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.
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.
Connector for Microsoft SharePointNote: 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 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
|
|
|
