bb c Configuring LiveCycle ES Application

bb c Configuring LiveCycle ES Application
bc
Configuring LiveCycle® ES Application
Server Clusters Using WebSphere®
Adobe® LiveCycle® ES
November 19, 2010
Update 1 (8.2)
© 2009 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle® ES Update 1 (8.2) Configuring LiveCycle ES Application Server Clusters Using WebSphere® for Microsoft® Windows®,
UNIX®, and Linux
Edition 2.4, November 19, 2010
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end-user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Acrobat, Flash, Flex Builder, FrameMaker, LiveCycle, PageMaker, PhotoShop, and Reader are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
IBM, AIX, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the U.S. and other countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft, Windows, Windows Server, and Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Novell is a registered trademark and SUSE is a trademark of Novell, Inc. in the United States and other countries.
Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. Products bearing
SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
Sun, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the US and other countries.
All other trademarks are the property of their respective owners.
This product contains either BSAFE and/or TIPEM software by RSA Security, Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).
This product includes copyrighted software developed by E. Wray Johnson for use and distribution by the Object Data Management Group
(http://www.odmg.org/).
Portions © Eastman Kodak Company, 199- and used under license. All rights reserved. Kodak is a registered trademark and Photo CD is a
trademark of Eastman Kodak Company.
Powered by Celequest. Copyright 2005-2008 Adobe Systems Incorporated. All rights reserved. Contains technology distributed under license
from Celequest Corporation. Copyright 2005 Celequest Corporation. All rights reserved.
Single sign-on, extending Active Directory to Adobe LiveCycle ES provided by Quest Software “www.quest.comlidentity-management” in a
subsequent minor release that is not a bug fix (i.e., version 1.1 to 1.2 but not 1.1.1 to 1.1.2) of the Licensee Product that incorporates the
Licensed Product.
The Spelling portion of this product is based on Proximity Linguistic Technology.
©Copyright 1989, 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey
USA.
© Copyright 1990 Merriam-Webster Inc. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2003 Franklin Electronic Publishers Inc. © Copyright 2003 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1991 Dr.Lluis de Yzaguirre I Maura © Copyright 1991 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1990 Munksgaard International Publishers Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1995 Van Dale Lexicografie bv © Copyright 1996 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1990 IDE a.s. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc.
Burlington, New Jersey USA.
© Copyright 2004 Franklin Electronics Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1992 Hachette/Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of
Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 Bertelsmann Lexikon Verlag © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 MorphoLogic Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers,
Inc. Burlington, New Jersey USA.
© Copyright 1990 Williams Collins Sons & Co. Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA. © Copyright 1993-95 Russicon Company Ltd.
© Copyright 1995 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 IDE a.s. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc.
Burlington, New Jersey USA.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 7
Who should read this document? ............................................................................................................................................ 7
Conventions used in this document ....................................................................................................................................... 8
Additional information................................................................................................................................................................. 8
1
Introduction ............................................................................................................................... 10
Preparing your server cluster to install LiveCycle ES .......................................................................................................10
About the LiveCycle ES installation, configuration, and deployment process......................................................10
Selecting tasks for configuring and deploying LiveCycle ES........................................................................................11
Upgrading to LiveCycle ES........................................................................................................................................................11
LiveCycle ES installation, configuration, and deployment lists ...................................................................................11
Automatic installation and deployment list.................................................................................................................12
Manual installation and deployment list.......................................................................................................................12
2
Creating a WebSphere Application Server Cluster ................................................................. 14
Preparing to install.......................................................................................................................................................................14
Installing WebSphere Network Deployment software...................................................................................................15
Modes of installing the WebSphere Network Deployment software.................................................................15
Creating and configuring the WebSphere cluster ...........................................................................................................15
Creating WebSphere profiles.............................................................................................................................................16
Federating WebSphere Application Server profiles..................................................................................................19
Creating the WebSphere cluster ......................................................................................................................................21
Modifying the SOAP connection time-out settings ..................................................................................................23
Configuring transaction logs for high availability......................................................................................................24
Testing the WebSphere Application Server cluster .........................................................................................................25
Next steps........................................................................................................................................................................................26
3
Installing the Solution Component Files ................................................................................. 27
Installing the product files ........................................................................................................................................................27
Installing on a Windows staging platform for deployment on Linux or UNIX.................................................28
Configuring the LiveCycle Reader Extensions ES Rights credential ....................................................................28
Including the Java 5 SDK in the JAVA_HOME environment variable..................................................................28
Installing LiveCycle ES ..........................................................................................................................................................28
Viewing the error log ..................................................................................................................................................................31
Configuring the caching locators (caching using TCP only).........................................................................................31
Modifying the TCP locators ................................................................................................................................................31
Starting the TCP locators.....................................................................................................................................................33
Configuring the font directories .............................................................................................................................................33
Next steps........................................................................................................................................................................................33
4
Configuring LiveCycle ES for Deployment .............................................................................. 34
About LiveCycle Configuration Manager ............................................................................................................................34
CLI versus GUI versions of LiveCycle Configuration Manager ...............................................................................35
Determining the application server SOAP port.................................................................................................................35
Configuring and deploying LiveCycle ES.............................................................................................................................36
Uninstalling EAR files .................................................................................................................................................................41
Next steps........................................................................................................................................................................................41
4
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
5
5
Manually Configuring a WebSphere Cluster ........................................................................... 43
Configuring the WebSphere Application Server instances ..........................................................................................43
Modifying the WebSphere time-out settings..............................................................................................................43
Modifying the JVM properties...........................................................................................................................................44
Creating a J2C authentication alias for the database ...............................................................................................45
Configuring the LiveCycle ES database connectivity......................................................................................................46
Configuring the DB2 data source.....................................................................................................................................46
Configuring the Oracle data source ................................................................................................................................49
Configuring the SQL Server data source .......................................................................................................................51
Configuring WebSphere Messaging .....................................................................................................................................55
Configuring a default messaging provider...................................................................................................................55
SQL Server JMS validation ..................................................................................................................................................63
Next steps........................................................................................................................................................................................63
6
Manually Deploying WebSphere.............................................................................................. 65
About deploying LiveCycle ES solution components.....................................................................................................65
WebSphere directory name ...............................................................................................................................................65
Summary of deployable components............................................................................................................................65
Deploying to WebSphere..........................................................................................................................................................66
Starting the application .............................................................................................................................................................66
Next steps........................................................................................................................................................................................67
7
Post-Deployment Activities ...................................................................................................... 68
Verifying the deployment and accessing LiveCycle Administration Console........................................................68
Accessing LiveCycle Administration Console..............................................................................................................68
Viewing the log files..............................................................................................................................................................69
Accessing solution component web applications ...........................................................................................................70
Accessing Rights Management ES...................................................................................................................................71
Accessing User Management ............................................................................................................................................71
Accessing the Content Services ES repository...................................................................................................................72
Configuring LiveCycle PDF Generator ES or 3D ES ..........................................................................................................73
Setting environment variables..........................................................................................................................................73
Setting the Adobe PDF Printer as the default printer...............................................................................................75
Configuring Acrobat 9.0 ......................................................................................................................................................76
Installing East Asian characters in Windows ................................................................................................................77
Adding fonts to PDF Generator ES or PDF Generator 3D ES ..................................................................................77
Configuring HTML to PDF conversions..........................................................................................................................79
Installing the IPP client ...............................................................................................................................................................80
Final setup for LiveCycle Rights Management ES.............................................................................................................81
Final setup for Content Services ES .......................................................................................................................................81
Configuring LiveCycle ES to access LDAP............................................................................................................................82
Setting PDF Generator ES or 3D ES watched folder performance parameters......................................................84
Enabling FIPS mode.....................................................................................................................................................................84
Configuring HTML digital signature ......................................................................................................................................85
Overriding session management for Content Services ES............................................................................................85
Configuring the Document Management service for LiveCycle Content Services ES ........................................86
Configuring the Connector for EMC Documentum service..........................................................................................86
Configuring the Connector for IBM FileNet service.........................................................................................................90
Configuring the connector using FileNet 3.5...............................................................................................................90
Configuring the connector using FileNet 4.0.1 ...........................................................................................................93
Configuring the LiveCycle ES Connector for IBM Content Manager...................................................................98
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
6
Uninstalling LiveCycle ES........................................................................................................................................................ 102
Uninstalling a LiveCycle ES solution component.................................................................................................... 103
8
Configuring Load Balancing ...................................................................................................104
Preparing for installation........................................................................................................................................................ 104
Installing the web server ........................................................................................................................................................ 104
Installing the web server plug-in......................................................................................................................................... 105
Configuring message-driven beans ................................................................................................................................... 106
9
Advanced Production Configuration.....................................................................................108
Configuring pool size for LiveCycle Output ES and LiveCycle Forms ES............................................................... 108
LiveCycle PDF Generator ES .................................................................................................................................................. 108
Configuring EJB Pool Size ................................................................................................................................................ 109
10 Troubleshooting ......................................................................................................................111
Getting help ................................................................................................................................................................................ 111
PDF Generator ES on Windows fails when converting native files ......................................................................... 111
JMS fails to validate .................................................................................................................................................................. 111
Log file error message: exception=
No scheduler found with name IDPSchedulerService........................................................................................... 112
Exception: No trusted certificate found ............................................................................................................................ 112
Pop-up window (English/European) appears with LiveCycle Configuration Manager................................... 113
Connector for EMC Documentum error............................................................................................................................ 114
A
Appendix - Install Command Line Interface ..........................................................................115
Installing LiveCycle ES ............................................................................................................................................................. 115
Error logs ...................................................................................................................................................................................... 120
Uninstalling LiveCycle ES in console mode ..................................................................................................................... 120
Next steps..................................................................................................................................................................................... 120
B
Appendix - LCM Command Line Interface .............................................................................121
Order of operations .................................................................................................................................................................. 121
Command line interface property file................................................................................................................................ 121
Common properties........................................................................................................................................................... 122
Configure LiveCycle ES properties................................................................................................................................ 124
Configure or validate application server properties .............................................................................................. 126
Deploy LiveCycle properties ........................................................................................................................................... 128
Initialize LiveCycle properties......................................................................................................................................... 128
Initialize BAM properties .................................................................................................................................................. 129
Deploy LiveCycle Components properties................................................................................................................ 129
Command line interface usage...................................................................................................................................... 130
Examples usage ......................................................................................................................................................................... 133
Error logs ...................................................................................................................................................................................... 133
Next steps..................................................................................................................................................................................... 133
About This Document
This document is one of several resources available to help you learn about Adobe® LiveCycle® ES
(Enterprise Suite) Update 1. LiveCycle ES is a flexible, extensible platform that helps automate and
accelerate the flow of business-critical information to and from customers, partners, constituents, and
employees.
This document provides information about how to install and configure the following solution
components in a clustered environment on Microsoft® Windows®, Linux®, IBM® AIX®, and Sun™ Solaris™,
and how to deploy the solution components to IBM WebSphere® Application Server:
●
Adobe LiveCycle Barcoded Forms ES
●
Adobe LiveCycle ES Business Activity Monitoring
●
Adobe LiveCycle ES Connector for EMC Documentum
●
Adobe LiveCycle ES Connector for IBM FileNet
●
Adobe LiveCycle ES Connector for IBM Content Manager
●
Adobe LiveCycle Content Services ES
●
Adobe LiveCycle Digital Signatures ES
●
Adobe LiveCycle Forms ES
●
Adobe LiveCycle Foundation
●
Adobe LiveCycle Output ES
●
Adobe LiveCycle PDF Generator ES
●
Adobe LiveCycle PDF Generator 3D ES
●
Adobe LiveCycle Process Management ES
●
Adobe LiveCycle Reader Extensions ES
●
Adobe LiveCycle Rights Management ES
Who should read this document?
This document provides information for administrators or developers who are responsible for installing,
configuring, administering, or deploying LiveCycle ES components in a clustered environment. The
information provided assumes that readers are familiar with Java™ 2 Platform, Enterprise Edition (J2EE)
application servers; Linux, Windows, AIX, or Solaris operating systems; Oracle®, DB2®, or SQL Server
database servers; and web environments.
7
Adobe LiveCycle ES
About This Document
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Conventions used in this document
Conventions used in this document
This document uses the following naming conventions for common file paths.
Name
Default value
Description
[LiveCycleES root]
Windows:
C:\Adobe\LiveCycle8.2\
The installation directory that is used for all
LiveCycle ES solution components. The
installation directory contains
subdirectories for LiveCycle Configuration
Manager and the LiveCycle ES SDK.
Linux and UNIX:
/opt/adobe/livecycle8.2/
[appserver root]
WebSphere on Windows:
C:\Program Files\IBM\WebSphere\
AppServer
The home directory of the application
server that runs the LiveCycle ES services.
WebSphere on Linux and Solaris:
/opt/IBM/WebSphere/AppServer
WebSphere on AIX:
/usr/IBM/WebSphere/AppServer
[profiles root]
Application Server:
[appserver root]/profiles
The directory location that stores profiles.
The directory paths listed indicate the
default locations; however, administrators
may specify their own profiles directory
location.
[server name]
server1
The name of the server configured on your
application server.
[dbserver root]
The location where the LiveCycle ES Depends on the database type and your
database server is installed.
specification during installation.
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux and UNIX®). Any platform-specific information is indicated as required.
Additional information
The resources in this table can help you learn more about LiveCycle ES.
For information about
See
Preparing to install LiveCycle ES on a server cluster
Preparing to Install LiveCycle ES (Server
Cluster)
Upgrading from LiveCycle 7.x to LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Performing administrative tasks for LiveCycle ES
Administering LiveCycle ES
Installing LiveCycle Workbench ES
Installing Your IDevelopment Environment
8
Adobe LiveCycle ES
About This Document
Configuring LiveCycle ES Application Server Clusters Using WebSphere
For information about
Additional information
See
Other services and products that integrate with LiveCycle ES www.adobe.com
Patch updates, technical notes, and additional information
on this product version
LiveCycle Technical Support
9
1
Introduction
This chapter provides information to help you understand how to prepare your cluster to install
LiveCycle ES, the type of installation and deployment you should perform for LiveCycle ES, and
information that will help you understand the LiveCycle ES installation, configuration, and deployment
process:
●
“Preparing your server cluster to install LiveCycle ES” on page 10
●
“About the LiveCycle ES installation, configuration, and deployment process” on page 10
●
“LiveCycle ES installation, configuration, and deployment lists” on page 11
For information about preparing your system to create your server cluster and install LiveCycle ES,
including system requirements, preparing the database, and configuring LiveCycle Reader Extensions ES
credentials, see Preparing to Install LiveCycle ES (Server Cluster).
Preparing your server cluster to install LiveCycle ES
You must create and configure your server cluster before you install, configure, and deploy LiveCycle ES.
(See “Creating a WebSphere Application Server Cluster” on page 14.)
About the LiveCycle ES installation, configuration, and
deployment process
Installing, configuring, and deploying LiveCycle ES involves the following processes:
Installing: Install LiveCycle ES by running the installation program. Installing LiveCycle ES places all of
the required files onto your computer, within one installation directory structure. The default
installation directory is C:\Adobe\LiveCycle8.2 (Windows) or /opt/adobe/LiveCycle8.2 (Linux or UNIX);
however, you can install the files to a different directory. In this docment, the default installation
directory is referred to as [LiveCycleES root]. (See “Installing the Solution Component Files” on page 27.)
Configuring and assembling: Configuring LiveCycle ES modifies various settings that determine how
LiveCycle ES works. Assembling the product places all of the installed components into several
deployable EAR and JAR files, according to your configuration instructions. Configure and assemble the
components for deployment by running LiveCycle Configuration Manager. (See “Configuring
LiveCycle ES for Deployment” on page 34.) You can configure and assemble multiple LiveCycle ES
solution components at the same time.
Deploying: Deploying the product involves deploying the assembled EAR files and supporting files to
the WebSphere Application Server cluster on which you plan to run your LiveCycle ES solution. If you
have configured and assembled multiple solution components, the deployable components are
packaged within the deployable EAR files. Components and LiveCycle ES archive (LCA) files are
packaged as JAR files.
Initializing the LiveCycle ES database: Initializing the database to be used with LiveCycle ES creates
tables for use with User Management and other components. Deploying any solution component that
connects to the LiveCycle ES database requires you to initialize the LiveCycle ES database after the
deployment process.
10
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Introduction
Selecting tasks for configuring and deploying LiveCycle ES
11
Selecting tasks for configuring and deploying LiveCycle ES
After you perform an installation, you can run LiveCycle Configuration Manager to perform various tasks:
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
cluster
●
Configure application server properties across all servers of the cluster to support LiveCycle ES
●
Validate application server cluster configuration
●
Deploy LiveCycle ES EAR files
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES component deployment
●
Validate the LiveCycle ES component deployment
●
Configure the LiveCycle Reader Extensions ES Rights credential (optional)
●
Import the LiveCycle ES Samples (optional)
If you install Reader Extensions ES, you can also specify and import the Reader Extensions ES Rights
credential that is required for applying usage rights to PDF documents.
Although you can use LiveCycle Configuration Manager to configure the application server cluster and set
up data sources to the database, you may prefer to complete these steps manually.
You may want to configure your application server cluster manually for these reasons:
●
You have other applications running on the application server cluster and are concerned about
possible conflicting configurations.
●
Corporate security procedures for configuration management dictate finer control.
●
You are performing deployments where automatic configuration is not available.
In the manual configuration case, do these tasks:
●
Use LiveCycle Configuration Manager to configure LiveCycle ES components with the required font
and temp directories
●
Manually configure the application server cluster, configure data sources, and deploy LiveCycle ES EAR
files
●
Run LiveCycle Configuration Manager to initialize the database
Upgrading to LiveCycle ES
Before you install LiveCycle ES for upgrading from LiveCycle 7.x and later, ensure that you completed the
tasks that are described in Preparing to Upgrade to LiveCycle ES.
LiveCycle ES installation, configuration, and deployment lists
This section includes lists that you can use to step through the installation and configuration process. A list
is provided for installing and configuring when using either the automatic method or the manual method.
Automatic method: Refers to using LiveCycle Configuration Manager to configure and deploy
LiveCycle ES EAR files, configure the application server cluster, initialize the database, and deploy the
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Introduction
Automatic installation and deployment list
12
solution components to the server cluster. Use the automatic method if you want to have limited input
into the installation, configuration, and deployment of LiveCycle ES.
Manual method: Refers to using LiveCycle Configuration Manager only to configure LiveCycle ES EAR
files, initialize the database, and deploy the solution components to the server cluster. Configuring the
application server cluster, connecting to the database, and deploying LiveCycle ES EAR files to the
server cluster is done manually by the administrator by following the instructions later in this
document. Use the manual method if you want to have precise input into the installation,
configuration, and deployment of LiveCycle ES. For example, this method may be used in a
locked-down server environment.
Automatic installation and deployment list
The following list includes the steps that are required for installing LiveCycle ES solution components by
using the automatic method. The WebSphere Application Server cluster must be installed before you
perform the installation:
●
Ensure that you have the required software installed in the target environment. (See Preparing to Install
LiveCycle ESPreparing to Install LiveCycle ES (Server Cluster) and “Creating a WebSphere Application
Server Cluster” on page 14 and “Manually Configuring a WebSphere Cluster” on page 43).
●
Run the installation program. (See “Installing the Solution Component Files” on page 27.)
●
Run LiveCycle Configuration Manager and select all the tasks on the Task Selection screen. This step
configures and assembles the LiveCycle ES EAR files, configures application server settings, deploys the
EAR files and other components to the application server cluster, initializes the LiveCycle ES database,
and verifies the deployment. (See “Configuring LiveCycle ES for Deployment” on page 34.)
●
Access the LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 68.)
●
(Optional) Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 82.)
Manual installation and deployment list
The following list includes the steps that are required for installing LiveCycle ES by using the manual
method. Your application server cluster must be installed and configured before you perform the
installation.
●
Ensure that you have the required software installed and configured in the target environment. (See
Preparing to Install LiveCycle ES (Server Cluster).
●
Ensure that you created and configured the application server cluster in the target environment. (See
“Creating a WebSphere Application Server Cluster” on page 14 and “Manually Configuring a
WebSphere Cluster” on page 43.)
●
Run the installation program. (See “Installing the Solution Component Files” on page 27.)
●
Run LiveCycle Configuration Manager and select the Configure LiveCycle ES EARs task. This task
configures and assembles LiveCycle ES. (See “Configuring LiveCycle ES for Deployment” on page 34.)
●
Configure WebSphere Application Server settings. A variety of settings must be configured. (See
“Manually Configuring a WebSphere Cluster” on page 43.)
●
Deploy the EAR files to the application server cluster. You can do this manually or use
LiveCycle Configuration Manager. (See “Manually Deploying WebSphere” on page 65.)
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Introduction
Manual installation and deployment list
●
Run LiveCycle Configuration Manager to deploy LiveCycle ES component files, initialize the
LiveCycle ES database, and (optionally) deploy product samples. (See “Configuring LiveCycle ES for
Deployment” on page 34.)
●
Access LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 68.)
●
(Optional) Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 82.)
13
2
Creating a WebSphere Application Server Cluster
You must install the WebSphere Application Server Network Deployment software to create your
WebSphere cluster. Perform the following tasks:
●
Ensure that you properly prepared all computers in the cluster. (See “Preparing to install” on page 14.)
●
Install the WebSphere Application Server Network Deployment software. (See “Installing WebSphere
Network Deployment software” on page 15.)
●
Create your WebSphere Application Server cluster. (See “Creating and configuring the WebSphere
cluster” on page 15.)
●
Test the WebSphere Application Server cluster configuration. (See “Testing the WebSphere Application
Server cluster” on page 25.)
Preparing to install
Before you install WebSphere Application Server on the computers of your cluster, ensure that your system
meets the following configuration requirements:
Disk space: Ensure that the partition that will hold the application server has a minimum of 10 GB of
free disk space. In addition to the space required to install the product, your environment variable
TEMP or TMP must point to a valid temporary directory with at least 500 MB of free disk space. The
downloadable executable requires approximately 500 MB, plus an additional 1.0 GB to unpack the
images.
IP address settings: All the computers must have a fixed IP address that is managed through a single
DNS.
IP multicast: All the computers must fully support IP multicast packet propagation, which means that
all routers and other tunneling technologies must be configured to propagate multicast messages to
clustered server instances. The network latency must be low enough to ensure that most multicast
messages reach their final destination within 200 to 300 milliseconds. Also, the multicast time-to-live
(TTL) value for the cluster must be high enough to ensure that routers do not discard multicast packets
before they reach their final destination.
Versions: All the computers in the cluster must have the same version and same service pack of
WebSphere Application Server software.
Horizontal clustering: If your configuration is horizontally clustered (that is, instances of WebSphere
Application Server are installed on separate computers), ensure that all computers are on the same
network subnet and that the computer clocks are synchronized. (See Preparing to Install LiveCycle ES
(Server Cluster).)
Account privileges: (Windows) You must install and run WebSphere Application Server under a user
account that has administrator privileges.
Shared network drive: You must have a secure shared network drive created that all computers in the
cluster can access with read and write permissions. (See Preparing to Install LiveCycle ES (Server Cluster).)
14
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing WebSphere Network Deployment software
15
Installing WebSphere Network Deployment software
You must install WebSphere Application Server Network Deployment software to create your WebSphere
Deployment Manager and Application Server.
WebSphere Deployment Manager allows you to manage your WebSphere Application Server cluster. You
can install WebSphere Application Server Network Deployment on a dedicated administrative computer
or on any node in the cluster that has sufficient capacity to install and run the Deployment Manager. (See
this WebSphere Application Server site
Note: Make sure you install WebSphere Application Server 6.1.0 Fixpack 7 (6.1.0.7) with the IBM JDK SR5
service release.
●
For information about the fix pack, see Fix list for IBM WebSphere Application Server version 6.1.
●
For information about the service release, see Java SDK 1.5 SR3 Cumulative Fix for WebSphere
Application Server.
Modes of installing the WebSphere Network Deployment software
You can install the WebSphere Network Deployment software in one of the following ways:
●
Choose None on the WebSphere Application Server Environments screen to install the WebSphere
Network Deployment Software without creating any profiles. Later, you can create a Deployment
Manager or application server profile using the manageprofiles script. See “Creating WebSphere
profiles” on page 16.
●
Choose Application server on the WebSphere Application Server Environments screen to install
the WebSphere Network Deployment software along with a single application server profile.
●
Choose Deployment Manager on the WebSphere Application Server Environments screen to
install the WebSphere Network Deployment software along with the Deployment Manager profile.
●
Select the Cell (Deployment Manager and a Managed Node) option on the WebSphere
Application Server Environments screen to install the WebSphere Network Deployment software
along with a cell that includes a Deployment Manager and a managed node application server profile.
Selecting this option during installation saves the effort of manually creating the profiles later.
For more information about installing WebSphere Application Server software, see this WebSphere
Application Server site.
Note: While installing the WebSphere Network Deployment software on nodes where you want to host
only the application server, choose the Application server option on the WebSphere Application
Server Environments screen.
Note: You can use the manageprofiles script to create Deployment Manager or application server
profiles any time after installing WebSphere Network Deployment software in one of the above
ways.
Creating and configuring the WebSphere cluster
Configure your WebSphere Application Server cluster by performing the following tasks:
●
Create WebSphere Deployment Manager and WebSphere Application Server profiles. (See
“Creating WebSphere profiles” on page 16.)
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating WebSphere profiles
16
●
Federate the nodes to the Deployment Manager. (See “Federating WebSphere Application Server
profiles” on page 19.)
●
Create the cluster. (See “Creating the WebSphere cluster” on page 21.)
●
Modify the SOAP connection time-out. (See “Modifying the SOAP connection time-out settings” on
page 23.)
●
Configure the transaction logs for high availability. (See “Configuring transaction logs for high
availability” on page 24.)
Creating profiles creates empty nodes that do not contain an administrative console or server. After
federating these nodes, use the Deployment Manager to create a cluster of servers that use these nodes.
Creating WebSphere profiles
Once you have installed WebSphere Network Deployment software in one of the ways listed in “Modes of
installing the WebSphere Network Deployment software” on page 15, you can create different type of
WebSphere profiles. Create WebSphere profiles for your WebSphere Deployment Manager and for your
WebSphere Application Server instances.
The procedure to create WebSphere profiles depends on whether your WebSphere Application Server is
32 bit or 64 bit:
●
For 32-bit WebSphere Application Server, see “Creating WebSphere profiles for 32 bit WebSphere
Application Server” on page 16.
●
For 64-bit WebSphere Application Server, see “Creating WebSphere profiles for 64-bit WebSphere
Application Server” on page 18.
If you selected the Cell (Deployment Manager and a Managed Node) option (on the WebSphere
Application Server environments screen) when you installed WebSphere Application Server Network
Deployment, the Deployment Manager and managed Application Server profiles were created
automatically for you. This applies to either 32-bit or 64-bit WebSphere Application Server.
Creating WebSphere profiles for 32 bit WebSphere Application Server
Use the WebSphere profile management tool to create profiles on a 32-bit WebSphere Application Server
by performing the following tasks:
1. Create a Deployment Manager profile that will run the WebSphere Administrative Console. (See
“Creating a WebSphere Deployment Manager profile” on page 16.)
2. Create profiles for the WebSphere Application Server instances that will comprise your cluster. (See
“Creating a WebSphere Application Server profile” on page 17.)
Creating a WebSphere Deployment Manager profile
Create a Deployment Manager profile on the node that you selected to host the WebSphere Deployment
Manager. This profile contains the WebSphere Administrative Console and also hosts the cell that the
nodes of your cluster will be federated to.
➤ To create a WebSphere Deployment Manager profile:
1. On the node hosting your WebSphere Deployment Manager, open a command prompt and navigate
to the [appserver root]/bin/ProfileManagement directory.
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating WebSphere profiles
17
2. Start the WebSphere Profile Management Tool by entering the following command:
●
(Windows) pmt.bat
●
(Linux/UNIX) ./pmt.sh
3. On the Welcome screen, click Next.
4. In the list of environments to create, select Deployment manager and then click Next.
5. Select Advanced profile creation and click Next.
6. Ensure that Deploy Administration Console is selected and click Next.
7. In the Profile Name box, accept the default or enter a name for the profile, and then click Next.
Note: The default profile name is Dmgr01 and the profile directory is [appserver root]/profiles/Dmgr01.
If you change the profile name, you should update the profile directory to match in order to
simplify future administration.
8. In the Node Name box, enter a unique name to represent the node to which this profile applies. The
default node name is in the form [DNS_Name][CellManager_Name].
9. In the Host Name box, enter the full DNS name or IP address of the computer hosting this profile.
10. In the Cell Name box, enter a name for the cell or accept the default, and then click Next.
11. (Optional) Deselect Enable administrative security and click Next.
12. Record the port numbers used and click Next.
Note: You will need the port numbers for later tasks when you configure the application server.
13. (Windows and Linux) Specify whether to run the server as a service and specify the user account to run
the service, and then click Next.
14. Review the profile summary to confirm it is correct and click Create.
15. Deselect Launch the First steps console and click Finish.
16. Start the deployment manager:
●
(Windows) If you configured the server as a service, start the deployment manager by using the
service. Select Start > Run, type services.msc, and click OK. Otherwise, open a command
prompt and run this script:
[appserver root]/profiles/[deployment manager]/bin/startManager.bat
●
(Linux/UNIX) Open a command prompt and run this script:
[appserver root]/profiles/[deployment manager]/bin/startManager.sh
Creating a WebSphere Application Server profile
You can create a custom profile for each WebSphere Application Server in your cluster.
➤ To create a WebSphere Application Server profile:
1. On one WebSphere Application Server instance of the cluster, open a command prompt and navigate
to the [appserver root]/bin/ProfileManagement directory.
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating WebSphere profiles
18
2. Start the WebSphere Profile Creation wizard by entering the following command:
●
(Windows) pmt.bat
●
(Linux/UNIX) ./pmt.sh
3. On the Welcome screen, click Next.
4. In the Environments To Create list, select Application server, and then click Next.
5. Select Advanced profile creation and click Next.
6. On the Optional Application Deployment screen, accept the default selections and click Next.
7. In the Profile Name box, accept the default or enter a name for the profile, and then click Next.
Note: The default profile name is AppSrv01 and the profile directory is [appserver root]/profiles/
AppSrv01. If you change the profile name, you should update the profile directory to match in
order to simplify future administration.
8. In the Node Name box, enter a unique name to represent the node to which this profile applies.
Typically, this name is in the form [DNS_NAME][Node_Name].
9. In the Host Name box, enter the full DNS name or IP address of the computer hosting this profile, and
then click Next.
10. (Optional) Deselect Enable administrative security and click Next.
11. Review the port values and click Next.
12. Deselect Create a Web server definition and click Next.
13. Review the profile summary to confirm it is correct and click Create.
14. Deselect Launch the First steps console and click Finish.
15. Repeat steps 1 to14 for each WebSphere Application Server instance in the cluster:
●
If your cluster employs vertical clustering, repeat these steps for each additional WebSphere
Application Server instance on the node where you created the first profile.
●
If your cluster employs horizontal clustering, repeat these steps for each WebSphere Application
Server instance on every additional node of the cluster.
Creating WebSphere profiles for 64-bit WebSphere Application Server
Use the WebSphere manageprofiles script (manageprofiles.bat on Windows and
manageprofiles.sh on Linux or UNIX) to create profiles on a 64-bit WebSphere Application Server.
Create a Deployment Manager profile on the node that you selected to host the WebSphere Deployment
Manager. This profile contains the WebSphere Administrative Console and also hosts the cell to which the
nodes of your cluster will be federated.
You must also create profiles for each of the WebSphere Application Server instances that will comprise
your cluster.
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Federating WebSphere Application Server profiles
19
➤ To create a WebSphere profile with the manageprofiles script:
1. On the computer that you will create the profile for, open a command prompt and navigate to the
[appserver root]/bin/ directory.
2. Start the WebSphere Profile Management Tool by entering the following command:
●
(Windows) manageprofiles.bat
●
(Linux/UNIX) ./manageprofiles.sh
3. Type a command with the appropriate options to create a profile with the manageprofiles script.
For example, type the following text:
●
(Windows):
[appserver root]\bin>manageprofiles.bat -create -templatePath
"[appserver root]\profileTemplates\default" -profileName LCES_AppSrv01
-profilePath "[appserver root]\profiles\LCES_AppSrv01" -isDefault
●
(Linux/UNIX):
[appserver root]/bin>./manageprofiles.sh -create -templatePath
"[appserver root]/profileTemplates/default" -profileName LCES_AppSrv01
-profilePath "[appserver root]/profiles/LCES_AppSrv01" -isDefault
Note: You can view a list of the allowable options for the manageprofiles script by typing
manageprofiles.sh –help –create from a command line. You should typically specify
the following options:
●
The template path. Use the path where you installed WebSphere Application Server. For the
default path that WebSphere Application Server installs to, see “Conventions used in this
document” on page 8.
●
The profile path. Use the path where you installed WebSphere Application Server. For the
default path that WebSphere Application Server installs to, see “Conventions used in this
document” on page 8.
●
The profile name. Specify a profile name that readily identifies the WebSphere Application
Server that the profile applies to (for example, include the identifier LCES for LiveCycle ES or
JMS for Java Message Service).
●
If the profile is the default profile for the WebSphere Application Server. The -isDefault
option specifies that the profile is the default profile. On a cluster that uses Network
Deployment, the dmgr01 profile typically exists as the default profile.
Federating WebSphere Application Server profiles
You must now federate individual servers by adding the profiles that you created for each WebSphere
Application Server instance into the Deployment Manager profile. (See “Adding profiles” on page 20.)
You can also remove a WebSphere Application Server instance from an existing WebSphere cell by
removing its profile from the Deployment Manager profile. (See “Removing and deleting profiles” on
page 20.)
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Federating WebSphere Application Server profiles
20
Adding profiles
Before you add WebSphere Application Server profiles, ensure that the Deployment Manager is running.
Also ensure that you can connect to the Deployment Manager from the WebSphere Application Server
instance by using the name of the Deployment Manager as well as the IP address.
Caution: Before you add WebSphere Application Server profiles, ensure that the system clocks of all
WebSphere Application Server instances are synchronized.
➤ To add a custom profile to the Deployment Manager:
1. If the Deployment Manager is not running, navigate to the bin directory of the Deployment Manager
Profile and run the appropriate script:
●
(Windows) startManager.bat
●
(Linux, UNIX) ./startManager.sh
If you installed WebSphere Application Server using the Cell (deployment manager and a managed
node) option, navigate to the directory [appserver root]/profiles/<profile_name>/bin and start the
node agent by running the appropriate command:
●
(Windows) startNode.bat
●
(Linux, UNIX) ./startNode.sh
2. From a command prompt, navigate to the [profiles root]/<profile name>/bin directory of the
WebSphere Application Server instance you want to add.
3. Run the addNode script by using the computer name as a parameter; for example, type this text:
●
(Windows) addNode.bat [ND_ServerName] [ND_ServerPort]
●
(UNIX/Linux) ./addNode.sh [ND_ServerName] [ND_ServerPort]
In addition to federating the node to the cell, addNode also starts the node agent process. After the node
is federated to a cell, the node agent is started with the startNode command, which is also located in the
bin directory of the WebSphere Application Server profile. During this process, the node being federated
communicates to the Deployment Manager by using port 8879 by default.
It is a good practice to add the node agent as an operating system daemon process in UNIX. You can add
the node agent as a service in Windows by using WASService, which is available in the bin directory of
the application server installation.
Removing and deleting profiles
You can remove a WebSphere Application Server profile from the cell by removing its profile from the
WebSphere Deployment Manager. You can execute this task by using either a pair of script files or the
Deployment Manager Administrative Console.
Note: Removing a profile from the cell only removes the server from the cluster; it does not delete the
profile. The profile remains (and can be added back to the cell later, if needed). To completely
remove a profile, delete the profile as a separate task.
You can delete profiles that you no longer need on your Deployment Manager and servers.
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating the WebSphere cluster
21
➤ To remove a WebSphere Application Server using script files:
1. If the Deployment Manager is not running, navigate to the bin directory of the Deployment Manager
Profile and run the appropriate script:
●
(Windows) startManager.bat
●
(Linux, UNIX) ./startManager.sh
2. On each WebSphere Application Server that you want to remove, navigate to the bin directory of the
profile that is running the node agent and run the appropriate removeNode script:
●
(Windows) removeNode.bat
●
(Linux, UNIX) ./removeNode.sh
3. Navigate to the bin directory of the Deployment Manager profile and run the appropriate cleanup
script:
●
(Windows) cleanupNode.bat
●
(Linux, UNIX) ./cleanupNode.sh
➤ To remove a WebSphere Application Server using the Deployment Manager:
1. Verify that the Deployment Manager is running.
2. In a web browser, type the URL to the Deployment Manager; for example, type
http://<servername>:<port>/ibm/console
Note: By default, the Deployment Manager Administrative Console web application listens on port
9060.
3. In the left pane, select System Administration and click Nodes.
4. Select the node to remove and click Remove Node.
5. To verify that the node is removed, navigate to System Administration > Nodes and confirm that the
node is not listed.
➤ To delete a profile:
1. Open a command prompt and navigate to the [appserver root]/bin directory.
2. Run the following command from the console:
●
(Windows) manageprofiles.bat -delete -profileName [profileName]
●
(UNIX/Linux) ./manageprofiles.sh -delete -profileName [profileName]
Note: The profile directory and log files are not deleted. You must manually delete the profile directory.
Any attempt to create a profile by using the same name as the deleted profile without first deleting
the directory causes an error.
Creating the WebSphere cluster
You must now create the WebSphere cluster by perform the following tasks:
●
Creating the cluster by using the Deployment Manager.
●
Configuring the distributed environment settings for the cluster.
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Creating the WebSphere cluster
22
Add ports and host aliases for WebSphere Application Server instances of the cluster.
By default, the WebSphere Administrative Console web application listens on port 9060.
➤ To create a cluster using the Deployment Manager:
1. Log in to the WebSphere Administrative Console of the computer hosting Deployment Manager.
2. In a web browser, enter the URL to the Deployment Manager; for example, type
http://<servername>:<port>/ibm/console
Note: By default, the Deployment Manager Administrative Console web application listens on port
9060.
3. In the navigation tree, click Servers > Clusters, and then click New.
4. In the Enter Basic Cluster Information box, enter the name of the cluster; for example, type
lc8_cluster.
5. Select Configure HTTP session memory-to-memory replication and click Next.
6. In the Member name box in the right pane, enter a member name. This name is for the first WebSphere
Application Server in the cluster.
7. In the Select Node list, select the node that this cluster member will reside on.
8. Select Create the member using an application server template, select default from the list, and
then click Next.
9. In the Member Name box, enter the name of another member to add to the cluster.
10. In the Select Node list, select the node that this cluster member will reside on.
11. Select Generate unique HTTP ports and click Add Member.
12. Repeat steps 9 to 11 to add WebSphere Application Servers to the cluster, entering the new member
name.
13. After you add all members, click Next.
14. Click Finish and then click Save.
15. Click System Administration > Save Changes to Master Repository, select Synchronize changes
with Nodes, and then click Save.
➤ To configure distributed environment settings for the cluster:
1. In the WebSphere Administrative Console navigation tree, click System administration > Nodes, and
ensure that the nodes are listed, that their status is Synchronized, and that all WebSphere Application
Server instances of the cluster are started.
2. Click Servers > Application servers and, in the right pane, click the server name.
3. Click the Configuration tab and, under Container Settings, click Session management.
4. Under Additional Properties, click Distributed environment settings.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating a WebSphere Application Server Cluster
Modifying the SOAP connection time-out settings
23
5. Under General Properties click Memory-to-memory replication.
6. In the Replication domain list, select the name of the cluster and, in the Replication mode list, select
Both client and server, and then click OK.
7. On the next screen, under Additional Properties, click Custom tuning parameters.
8. Select Low (optimize for failover) and then click OK.
9. In the navigation tree, click Servers > Application servers and, in the right pane, click the server name.
10. Under Performance, select Performance Monitoring Infrastructure (PMI).
11. On the next screen, select Enable Performance Monitoring Infrastructure (PMI).
12. Under Currently Monitored Statistics Set, select Basic and then click OK.
13. Repeat steps 2 to 12 for each server in your cluster.
14. In the Messages box, click Save directly to the master configuration.
➤ To configure WebSphere Application Server ports and aliases:
1. In a web browser, type the URL to the Deployment Manager; for example, type
http://<servername>:<port>/ibm/console
Note: By default, the WebSphere Administrative Console listens on port 9060.
2. In the navigation tree, click Servers > Application servers and, in the right pane, click the server name.
3. On the next screen, under Communications, click Ports.
4. In the table, click WC_defaulthost and assign a unique port address for each server in the cluster.
5. Repeat steps 2 to 4 for each server in the cluster.
6. Click Save directly to the master configuration.
7. In the navigation tree, click Environment > Virtual Hosts and, in the right pane, click default_host.
8. Under Additional Properties, click Host Aliases.
9. On the next screen, click New and add the port you assigned for a server in the cluster.
10. In the Host Name box, enter an asterisk (*).
11. Repeat step 9 for each port that is assigned in step 4.
12. Click OK and then click Save directly to master configuration.
13. To start the newly added server, click Servers > Application servers, select the check box beside the
the new server, and then click Start.
Modifying the SOAP connection time-out settings
Modify the SOAP connection time-out settings for each WebSphere Application Server in the cluster.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating a WebSphere Application Server Cluster
Configuring transaction logs for high availability
24
➤ To modify SOAP connection time-out settings
1. Log in to the WebSphere Administrative Console and, in the navigation tree, click Servers > Clusters.
2. In the right pane, stop all clusters.
3. Navigate to [appserver root]\profiles\<profile name>\properties and open the soap.client.props file in a
text editor.
4. Configure the com.ibm.SOAP.requestTimeout property to 1800.
5. Save the edited file.
6. Repeat steps 3 to 5 for each server in the cluster.
7. Restart the clusters.
Configuring transaction logs for high availability
If your WebSphere Application Server cluster is designed to provide high availability, you can employ
WebSphere’s transaction peer-recovery strategy. Peer recovery allows an alternate WebSphere Application
Server instance in the cluster to continue processing a LiveCycle ES transaction if the initial WebSphere
Application Server instance fails. You must allow the separate WebSphere Application Server instances in
the cluster to share access to their transaction logs, and configure the WebSphere Application Server
transaction logs to support failover.
Consider these recommendations:
●
Use a shared network drive that supports a lease-based, file-locking protocol.
●
Make the shared network drive available to each WebSphere Application Server instance in the cluster.
Each instance must have read and write permission to this shared network drive.
●
Configure each WebSphere Application Server instance of the cluster to use this shared network drive
for the transaction logs. Each server in the cluster must have a unique transaction log directory;
however, each server must be able to access the transaction log directories of other servers in the
cluster. (See “To configure transaction logs for failover:” on page 24.)
For more information, see Transactional High Availability.
➤ To configure transaction logs for failover:
1. Ensure that all WebSphere Application Server instances of the cluster have read and write access to a
shared network drive that is configured with lease-based file locking.
2. Ensure that all WebSphere Application Server instances of the cluster are started.
3. In the WebSphere Administrative Console navigation tree, click Severs > Application servers, and
then click the name of a server in the cluster.
4. Under Container Settings, click Container Services > Transaction Service.
5. In the Transaction log directory box, enter the path to the location on the shared network drive for
the transaction logs for this WebSphere Application Server instance, and then click OK.
6. Repeat steps 2 to 5 for each WebSphere Application Server instance in the cluster, and then click Save
directly to the master configuration.
Adobe LiveCycle ES
Creating a WebSphere Application Server Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Testing the WebSphere Application Server cluster
25
7. In the navigation tree, click Severs > Clusters, and then click the name of your cluster (for example,
click lc8_cluster).
8. On the Configuration tab, select Enable failover of transaction log recovery and then click OK.
9. In the navigation tree, click Servers > Core groups > Core group settings, and then click the name of
the core group for your cluster.
10. Under Additional properties, click Policies and verify these conditions:
●
A One of N policy type exists with Match criteria of type=WAS_TRANSACTIONS. If such a policy
does not exist, create one. (See this IBM documentation site.)
●
No static policy type exists with Match criteria of type=WAS_TRANSACTIONS. If such a policy
exists, delete it.
11. Restart the cluster.
Testing the WebSphere Application Server cluster
You can test the WebSphere Application Server cluster to ensure that all members are active and that the
cluster operates according to your design. You should ensure that the WebSphere Application Server
cluster functions correctly before you proceed to install and configure LiveCycle ES.
➤ To test the WebSphere Application Server cluster:
1. Ensure that all WebSphere Application Server instances of the cluster are started.
2. View the server.log file located in [appserver root]/server/all/log. Messages such as the following one
confirm the active members of the cluster:
[1/22/08 13:50:09:643 PDT] 00000018 PtpConnectedC I DCSV1031I: DCS Stack
DefaultCoreGroup.lc8_cluster at Member LCcell\Node01\Node01Server1:
Received a connection from an undefined member LCcell\Node02\
Node02Server1. Source address is /11.11.11.11.
[1/22/08 13:50:09:696 PDT] 0000001f RoleMember I DCSV8051I: DCS Stack
DefaultCoreGroup.lc8_cluster at Member LCcell\Node01\Node01Server1: Core
group membership set changed. Added: [LCcell\Node02\Node02Server1].
[1/22/08 13:50:09:704 PDT] 0000001d RecoveryDirec I CWRLS0012I: All
persistent services have been directed to perform recovery processing for
this WebSphere server (LCcell\Node01\Node01Server1).
[1/22/08 13:50:09:712 PDT] 00000018 MbuRmmAdapter I DCSV1032I: DCS Stack
DefaultCoreGroup.lc8_cluster at Member LCcell\Node01\Node01Server1:
Connected a defined member LCcell\Node02\Node02Server1.
[1/22/08 13:50:09:839 PDT] 00000020 RecoveryManag A WTRN0028I:
Transaction service recovering 0 transactions.
[1/22/08 13:50:26:744 PDT] 0000001f RoleMergeLead I DCSV8054I: DCS Stack
DefaultCoreGroup.lc8_cluster at Member LCcell\Node01\Node01Server1: View
change in process.
[1/22/08 13:50:26:764 PDT] 00000018 VSyncAlgo1 I DCSV2004I: DCS Stack
DefaultCoreGroup.lc8_cluster at Member LCcell\Node01\Node01Server1: View
synchronization completed successfully. The View Identifier is
(1:0.LCcell\Node01\Node01Server1). The internal details are None.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating a WebSphere Application Server Cluster
Next steps
26
Next steps
You must now install the LiveCycle ES solution component files. (See “Installing the Solution Component
Files” on page 27.)
3
Installing the Solution Component Files
This section describes the first phase of setting up a LiveCycle ES system that is running the LiveCycle ES
installation program on a Windows, Linux, or UNIX operating system. A subsequent phase will include
running LiveCycle Configuration Manager to configure and deploy LiveCycle ES.
Before you install the solution components, ensure that your environment includes the software and
hardware that is required to run LiveCycle ES. You should also understand the installation options and
have the environment prepared as required. (See Preparing to Install LiveCycle ES (Server Cluster).)
LiveCycle ES also provides a command line interface (CLI) for the installation program. The CLI is intended
to be used by advanced users of LiveCycle ES or in server environments that do not support the use of the
graphical user interface of LiveCycle Configuration Manager (See “Appendix - LCM Command Line
Interface” on page 121.)
This chapter covers the following topics:
●
“Installing the product files” on page 27
●
“Viewing the error log” on page 31
●
“Configuring the caching locators (caching using TCP only)” on page 31
●
“Configuring the font directories” on page 33
Installing the product files
When you run an installation program, you need the serial number for the solution components that you
are installing. If you are upgrading from LiveCycle ES 8.0, the existing serial numbers for LiveCycle ES 8.0
are used. In this case, you must add additional serial numbers only if you are installing solution
components in addition to those you are upgrading.
●
The type of installation and configuration you are performing.
To successfully install, you need read and write permissions for the installation directory. The following
installation directories are the defaults; however, you can specify a different directory as required:
●
(Windows) C:\Adobe\LiveCycle8.2\
●
(UNIX) /opt/adobe/livecycle8.2/
When installing on Linux, the installation program uses the logged-in user's home directory as a
temporary directory for storing files. As a result, messages such as the following text may appear in the
console:
WARNING: could not delete temporary file /home/<username>/ismp001/1556006
When you complete the installation, you must manually delete the temporary files.
Caution: Ensure that the temporary directory for your operating system meets the minimum
requirements as outlined in Preparing to Install LiveCycle ES (Server Cluster). The temporary
directory is one of the following locations:
●
(Windows) TMP or TEMP path as set in the environment variables
●
(UNIX) Logged-in user’s home directory
27
Adobe LiveCycle ES
Installing the Solution Component Files
Configuring LiveCycle ES Application Server Clusters Using WebSphere Installing on a Windows staging platform for deployment on Linux or
On UNIX systems, you can install, configure, and deploy as a non-root user:
●
(Solaris) /var/tmp
●
(AIX) /tmp
Note: When you are installing the solution components on a Linux or UNIX operating system, you must be
logged in as the root user to successfully install the solution components to the default location,
which is /opt/adobe/LiveCycle8.2/. If you are logged in as a non-root user, change the installation
directory to one that you have permissions (read-write-execute privileges) for. For example, you can
change the directory to /home/[username]/livecycle8.2.
Temporary files are generated in the system default temp directory or in the directory that you
specified. In certain instances, the generated temporary files may remain after the installer is closed.
You can choose to remove these files manually.
Installing on a Windows staging platform for deployment on Linux or UNIX
LiveCycle ES can be installed and configured on Windows for deployment on a Linux or UNIX platform. You
can use this functionality for installing on a locked-down Linux or UNIX environment. For example, a
locked-down environment does not have a graphical user interface installed. When you run the
installation program on Windows, you can choose a Linux or UNIX operating system as the target platform
for deploying LiveCycle ES. The installation program installs binaries for Linux, or Solaris that are also used
by LiveCycle Configuration Manager when you configure the product.
The computer running Windows can then be used as a staging location for the deployable objects, which
can be copied to a Linux or UNIX computer for deployment to the application server. The application
server that you are targeting must be consistent with what you choose during installation and
configuration, regardless of the operating system.
Note: The host and target operating system must be Windows to support installing Acrobat for
LiveCycle PDF Generator ES from the installer.
Configuring the LiveCycle Reader Extensions ES Rights credential
Ensure that you have a new valid credential and password before you run the installation. If you do not
have the information at this time, you can install the credential after you install and deploy LiveCycle ES on
the Trust Store configuration pages in LiveCycle Administration Console.
Including the Java 5 SDK in the JAVA_HOME environment variable
The JAVA_HOME environment variable must point to the Java 5 SDK. The required Java SDK is IBM JDK
1.5.0 SR2 (embedded in the application server) on all platforms except Solaris. On Solaris, you must point
to Sun JDK 1.5.0_09.
The Java 5 SDK requirements are also listed in Preparing to Install LiveCycle ES (Server Cluster).
Installing LiveCycle ES
This section covers the initial installation of LiveCycle ES. For information about configuration and
deployment, see “Configuring LiveCycle ES for Deployment” on page 34.
Adobe LiveCycle ES
Installing the Solution Component Files
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing LiveCycle ES
29
Note: To avoid permission issues during deployment, ensure that you run the LiveCycle ES installer and
LiveCycle Configuration Manager as the same user who will run the WebSphere server.
➤ To install LiveCycle ES:
1. Ensure that the JAVA_HOME environment variable is set to [appserver root]/java/.
2. Navigate to the ./livecycle_server/8.2 directory of the installation media.
3. If you are installing on AIX or Linux and you are not installing directly from a release DVD, set
executable permissions on the installation file by typing one of the following commands at the
command prompt:
chmod 007 aix_livecycle8_setup.bin
chmod 007 linux_livecycle8_setup.bin
4. Start the installation program:
●
(Windows) Double-click the win_livecycle8_setup.exe file.
●
(UNIX) From a command prompt, type the file name that is appropriate for your operating system:
./aix_livecycle8_setup.bin
./linux_livecycle8_setup.bin
./solaris_livecycle8_setup.bin
If you are installing on a Windows staging platform for deployment to UNIX, start the Windows
executable.
Specify the following additional arguments to redirect the LiveCycle ES installer temporary directory to
an alternate, non-default location:
-cp:p stage.jar -is:tempdir [alternate temporary directory]
(Solaris Only) To use a higher heap size (such as 512M) in the installer argument, you must specify
the heap size settings in a separate file and then run the install script.
To do this, create a filed named solaris_livecycle8_setup.ja in the directory where
solaris_livecycle8_setup.bin exists, and add the following lines in it:
-XMS256M
-XMX512M
After this, run the install script to direct the installer to use the JDK you installed:
# ./solaris_livecycle8_setup.bin -cp:p stage.jar -is:tempdir /[temporary
directory] -is:javahome [java_home]
5. When prompted, select the language for the installation to use and click OK.
6. On the Welcome screen, click Next. If you have a previous version of LiveCycle ES 8.0.x the Update
Installation screen appears.
7. Select one of the following options and then click Next:
●
Upgrade Existing Installation to LiveCycle ES v8.2: Choose this option if you intend to upgrade
from LiveCycle ES 8.0.x to LiveCycle ES 8.2. Ensure that the directory shown on the screen
corresponds with the existing version of LiveCycle ES; otherwise, browse to the correct directory.
Choosing this option ensures that information from the existing installation, such as the product
serial number, is used. LiveCycle Configuration Manager performs the actual upgrade tasks when
the installation process is complete. It is important that you back up your existing environment
Adobe LiveCycle ES
Installing the Solution Component Files
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing LiveCycle ES
30
before you upgrade. (See “LiveCycle ES Database” and “GDS Backup and Recovery” in Administering
LiveCycle ES.)
●
Install LiveCycle ES v8.2: Choose this option to install a new, separate instance of LiveCycle ES 8.2.
If you choose this option, your previous installation of LiveCycle ES will not be upgraded or
removed.
8. On the Installation Location screen, accept the default directory as listed or click Browse and navigate
to the directory where you intend to install the solution component, and then click Next.
Note: If you type the name of a directory that does not exist, it is created for you.
Caution: When you install the solution component, you can specify a different installation location. If you
are installing on Linux or UNIX, the directory you specify should not contain any spaces;
otherwise, the installation program does not install the solution component.
9. Type a serial number in the text box and click Add. If you have licensed multiple solution components,
repeat this step for each serial number you have. After you add all the serial numbers to the list, click
Next.
Tip: You can reset the serial number by clicking Clear.
10. Read the Adobe LiveCycle ES Server License Agreement and select I accept to the terms of the license
agreement. If you do not accept the license agreement, you cannot continue.
11. Click Next and then select the JAVA SE SDK location. You can browse the correct SDK location or you
can continue with the default and click Next.
12. (Windows only) On the OS Selection screen, select the operating system that you plan to configure
LiveCycle ES for and click Next.
Note: At this point, you can specify to use Windows as a staging platform for your deployment. You can
select a UNIX operating system as the target for deployment even if you are installing on
Windows. (See “Installing on a Windows staging platform for deployment on Linux or UNIX” on
page 28.)
13. (PDF Generator ES or PDF Generator 3D ES for Windows only) Select No, do not enable native
application support for LiveCycle PDF Generator ES. Native application support is supported in a
cluster; however, you must select No in this dialog box and then configure each node in the cluster
manually. (See “Setting environment variables” on page 73).
Note: PDF Generator 3D ES requires native application support to convert 3D files to PDF.
14. On the Pre-installation Summary Details screen, review the details and click Install. The installation
program displays the progress of the installation.
15. Review the release notes that are displayed and click Next.
16. Review the details of the Post-installation summary screen. Select Start LiveCycle Configuration
Manager and then click Finish.
Note: Selecting the Start LiveCycle Configuration Manager option starts LiveCycle Configuration
Manager, which allows you to complete your configuration and deployment immediately. If you are
not ready to run LiveCycle Configuration Manager, ensure that Start LiveCycle Configuration
Manager is not selected when you click Finish. You can start LiveCycle Configuration Manager
later, when you are ready. (See “Configuring LiveCycle ES for Deployment” on page 34.)
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing the Solution Component Files
Viewing the error log
31
Note: (PDF Generator ES or PDF Generator 3D ES for Windows only) If you did not choose to install
Acrobat 9.0 using the LiveCycle ES installer, you need to complete the steps in “Configuring Acrobat
9.0” on page 76.
Viewing the error log
If errors occur during the installation, the installation program creates the adobe_lc8.2_server_install.log
file, which contains the error messages. This log file is in the system temporary directory (TEMP or TMP).
(See “Troubleshooting” on page 111.)
Configuring the caching locators (caching using TCP only)
If you implement caching for your LiveCycle ES cluster by using TCP, you must properly configure the TCP
locators to find other members of the LiveCycle ES cluster.
Note: This section does not apply if you implement caching for your LiveCycle ES cluster by using UDP.
(See “Modifying the JVM properties” on page 44 to configure caching for your LiveCycle ES cluster
using UDP.)
You must perform the following tasks to enable LiveCycle ES cluster caching using TCP:
●
Ensure that the TCP locators are installed and configured as you prefer for your implementation. The
TCP locators are installed in the [LiveCycle ES root]/lib/caching directory, with a default configuration,
when you install LiveCycle ES. You can change the default configuration. (See “Modifying the TCP
locators” on page 31.)
●
Configure each node in the LiveCycle ES cluster to use the locators. (See “Modifying the JVM
properties” on page 44.)
●
Ensure that the TCP locators are running. (See “Starting the TCP locators” on page 33.)
Modifying the TCP locators
The LiveCycle ES installer creates a default configuration of the TCP locators that is ready to use without
modification. You can move the locators to any computer on your network and run them on that
computer. The locators do not have to reside on a computer that is a member of the LiveCycle ES cluster.
You can also create additional failover locators to support high availablity in your cluster. (See “To install
the TCP locators:” on page 31.)
You can also modify the TCP locators to use a port other than the default port (22345). (See “To modify the
default locator port (Windows):” on page 31 or “To modify the default locator port (UNIX):” on page 32.)
➤ To install the TCP locators:
1. Log on to the computer where you installed LiveCycle ES and navigate to the [LiveCycle ES root]/lib/
caching directory.
2. Copy the caching directory and its contents to the computer on which you want to run the locators.
➤ To modify the default locator port (Windows):
1. Open the startlocator.bat file in a text editor. The startlocator file for a default installation is on the
computer where you installed LiveCycle ES, in the [LiveCycle ES root]/lib/caching directory.
Adobe LiveCycle ES
Installing the Solution Component Files
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Modifying the TCP locators
32
2. Change the default port number (22345) to your preferred port number in the following properties:
-port=22345
-Dlocators=localhost[22345]
Note: The port number can be any available port between 1 and 65535.
Caution: Ensure that the port number that is configured here matches the port number that is configured
in the JVM argument of each node of the LiveCycle ES cluster. (See “Modifying the JVM
properties” on page 44.)
3. (Computers with multiple network cards only) If the computer hosting the locator has multiple
network cards, add the following argument at the the end of the java -cp line:
-address=<bind IP address>
Note: The value of <bind IP address> is the IP address that the locator will listen on. You must
must specify the <bind IP address> for the JVM argument
adobe.cache.cluster-locators on each node in your LiveCycle ES cluster. (See
“Modifying the JVM properties” on page 44.)
4. Save the edited file.
5. Repeat steps 1 to 4 on any additional locators for your LiveCycle ES cluster.
➤ To modify the default locator port (UNIX):
1. Open the startlocator.sh file in a text editor. The startlocator file for a default installation is located on
the computer where you installed LiveCycle ES, in the [LiveCycle ES root]/lib/caching directory.
2. Change the default port number (22345) to your preferred port number in the following properties:
GF_PORT=22345
-Dlocators=localhost[22345]
Note: The port number can be any available port between 1 and 65535.
Caution: Ensure that the port number that is configured here matches the port number that is configured
in the JVM argument of each node of the LiveCycle ES cluster. (See “Modifying the JVM
properties” on page 44.)
3. (Computers with multiple network cards only) If the computer hosting the locators has multiple
network cards, modify the following argument:
GF_BIND_ADDRESS=”<bind IP address>”
Note: The value of <bind IP address> is the IP address that the locator will listen on. You must
must specify the <bind IP address> for the JVM argument
adobe.cache.cluster-locators on each node in your LiveCycle ES cluster. (See
“Modifying the JVM properties” on page 44.)
4. Save the edited file.
5. Repeat steps 1 to 4 on any additional locators for your LiveCycle ES cluster.
Adobe LiveCycle ES
Installing the Solution Component Files
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Starting the TCP locators
33
Starting the TCP locators
You must start the TCP locators before you start your cluster. If the TCP locators are not running when you
start the members of the LiveCycle ES cluster, caching will not function.
➤ To start the TCP locators:
1. On the computer where the TCP locators are installed, navigate to the caching directory. For a default
installation, the TCP locators are installed on the computer where you installed LiveCycle ES, in the
[LiveCycle ES root]/lib/caching directory.
2. Run the appropriate file:
●
(Windows) startlocator.bat
●
(UNIX) startlocator.sh
3. Repeat steps 1 to 2 on any additional locators for your LiveCycle ES cluster.
➤ To stop the TCP locators:
1. On the computer where the TCP locators are installed, navigate to the caching directory. For a default
installation, the TCP locators are installed on the computer where you installed LiveCycle ES, in the
[LiveCycle ES root]/lib/caching directory.
2. Run the appropriate file:
●
(Windows) stoplocator.bat
●
(UNIX) stoplocator.sh
3. Repeat steps 1 to 2 on any additional locators for your LiveCycle ES cluster.
Configuring the font directories
You must configure the font directories for each computer in the cluster, including the LiveCycle ES fonts
that are installed in the [LiveCycleES root]\fonts directory.
The fonts must exist in the same path, and the directory must have identical contents on all computers in
the cluster. This can be accomplished by using a shared directory that all computers in the cluster can
access or by making the contents of the [LiveCycle ES root]\fonts directory available on each computer in
the cluster in an identical path.
Record the location where you create these shared directories for later use when you configure
LiveCycle ES using LiveCycle Configuration Manager.
Caution: The font directories must be distinct from the GDS directory; however, they may be distinct
sibling subdirectories of a single shared parent directory.
Next steps
You must now configure LiveCycle ES for deployment. (See “Configuring LiveCycle ES for Deployment” on
page 34.)
4
Configuring LiveCycle ES for Deployment
This chapter describes how to use LiveCycle Configuration Manager to perform any of the following tasks:
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
●
Configure application server properties to support LiveCycle ES
●
Validate application server configuration
●
Deploy LiveCycle ES EAR files
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES component
●
Validate the LiveCycle ES component deployment
●
(Optional) Configure the LiveCycle Reader Extensions ES Rights credential (if Reader Extensions ES is
installed)
●
Initialize BAM metadata for LiveCycle ES Business Activity Monitoring (if Business Activity Monitoring is
installed)
●
(Optional) Import the LiveCycle ES Samples into LiveCycle ES
This chapter assumes that you prepared your environment for hosting LiveCycle ES and installed the
solution component files. If you have not done this task, see Preparing to Install LiveCycle ES Clustering and
“Installing the Solution Component Files” on page 27.
About LiveCycle Configuration Manager
LiveCycle Configuration Manager is a wizard-like tool used to configure, deploy, and validate LiveCycle ES
components for deployment to the application server. You can optionally use LiveCycle Configuration
Manager to configure the application server and deploy the product EAR files to the application server.
LiveCycle Configuration Manager is installed with the solution component files when you run the
LiveCycle ES installation program. When you run LiveCycle Configuration Manager, you specify the
LiveCycle ES solution components you are configuring, and the tasks that you want LiveCycle
Configuration Manager to perform.
You can start LiveCycle Configuration Manager from the installation program to configure solution
components during the installation process, or you can start LiveCycle Configuration Manager any time
after the installation. If you plan to use LiveCycle Configuration Manager to configure the application
server or deploy to the application server, the application server must be started so that LiveCycle
Configuration Manager can perform configuration tasks on it.
You can configure an application server that is installed on a different computer from the one on which
you are running LiveCycle Configuration Manager. However, an application server must also be installed
(but does not have to be running) on the computer that is running LiveCycle Configuration Manager so
that LiveCycle Configuration Manager can use the application server library files.
34
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring LiveCycle ES for Deployment
CLI versus GUI versions of LiveCycle Configuration Manager
35
CLI versus GUI versions of LiveCycle Configuration Manager
This section describes the GUI version of LiveCycle Configuration Manager. For instructions about using
the command line interface (CLI) version of LiveCycle Configuration Manager, see “Appendix - LCM
Command Line Interface” on page 121. The following table illustrates the functionality offered by both
versions of LiveCycle Configuration Manager and configuration tasks you can perform manually.
LiveCycle ES configuration task
LCM GUI
LCM CLI
Manual
(Non-LCM)
Configure LiveCycle ES
Yes
Yes
No
Configure application server
Yes
Yes
Yes
Validate application server configuration
Yes
Yes
Yes
Deploy LiveCycle ES EARs
Yes
Yes
Yes
Initialize LiveCycle ES database
Yes
Yes
No
Initialize Business Activity Monitoring
Yes
Yes
Yes
Deploy LiveCycle ES components
Yes
Yes
No
Validate LiveCycle ES component deployment
Yes
Yes
Yes
Validate server connection
Yes
Yes
No
Validate LiveCycle ES server connection
Yes
Yes
No
Validate database connection
Yes
Yes
No
Configure Reader Extensions ES
Yes
No
Yes
Import Samples
Yes
No
Yes
Determining the application server SOAP port
On some LiveCycle Configuration Manager screens, you must provide the SOAP port of the application
server. Use the steps in this topic to determine which port is used for SOAP connections with the
application server. The default port is 8880.
➤ To determine the SOAP port on WebSphere:
1. In the navigation panel of the WebSphere Administrative Console, click System
Administration->Deployment Manager.
2. Under Additional Properties, click Ports. On the next screen, make a note of the port number for
SOAP_CONNECTOR_ADDRESS.
Note: The WebSphere Administrative Console lists the SOAP Connector Address in two different sections.
You must ensure you use the path provided in Step #1. If you use the SOAP port listed at Servers >
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring and deploying LiveCycle ES
36
Application Servers > [serverName] > Communications > Ports you will receive the following
error when running the LiveCycle Configuration Manager:
com.adobe.livecycle.cdv.util.JaclResponseParser, parseString: WASX7017E: Exception received
while running file "..\scripts\jacl\config.jacl"; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available.
Configuring and deploying LiveCycle ES
When you run LiveCycle Configuration Manager, you can select the tasks that you want the program to
perform automatically.
Note: Using LiveCycle Configuration Manager to deploy LiveCycle ES solution components to remote
servers is supported only for managed application servers, not for stand-alone application servers.
Tip: LiveCycle Configuration Manager verifies the values that are specified on each screen when you click
Next. If it cannot validate a value, a warning message appears, the property on the screen becomes
red, and you cannot proceed until you enter a valid value.
If you are deploying to a cluster, the JMS cluster must be configured before configuring the application
server cluster using LiveCycle Configuration Manager. (See the “Configuring JMS Resources” section in the
Configuring LiveCycle ES Application Server Clusters guide for your application server.)
After LiveCycle Configuration Manager configures the LiveCycle ES EAR files, it places the files
adobe-livecycle-native-websphere-[OS].ear, adobe-livecycle-websphere.ear, adobe-workspace-client.ear
(if you installed LiveCycle Process Management ES) and adobe-contentservices.ear (if you installed
LiveCycle Content Services ES) in the following directory:
●
(Windows) [LiveCycleES root]\configurationManager\export
●
(Linux, UNIX) [LiveCycleES root]/configurationManager/export
If you use LiveCycle Configuration Manager to deploy the EAR files, LiveCycle Configuration Manager
accesses these files and deploys them to the application server. If you manually deploy the LiveCycle ES
EAR files, you can access the files in this directory and deploy them to the application server.
After LiveCycle Configuration Manager configures the LiveCycle ES EAR files, you may rename the EAR files
to a custom file name (for example, to specify in the file name a version identifier, or any other information
required by standard practices in the local J2EE environment). LiveCycle Configuration Manager does not
support deployment or undeployment of EAR files with custom file names. If your EAR files use a custom
file name, you must manually deploy and undeploy them to the application server (for example, when you
deploy the initial custom-named EAR files, and when applying any later changes such as service packs or
patches).
Note: If you previously deployed LiveCycle ES files, you must first undeploy the product EAR files from the
application server. However, if you use LiveCycle Configuration Manager to deploy EAR files, it
automatically undeploys previously deployed files before deploying updated files. If errors occur
during this process, you can undeploy the EAR files manually. (See “Uninstalling LiveCycle ES” on
page 102.)
If you are configuring a remote application server, ensure that an application server is also installed on the
same computer as LiveCycle Configuration Manager so that LiveCycle Configuration Manager can use the
application server library files.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring and deploying LiveCycle ES
37
➤ To configure, upgrade to, and deploy LiveCycle ES:
Tip: You can press F1 in LiveCycle Configuration Manager to view Help information for the screen you are
viewing. This Help contains details that may not be included in this document and are specific to the
context of each screen in LiveCycle Configuration Manager.
1. If you did not start LiveCycle Configuration Manager automatically from the installation program,
navigate to the [LiveCycleES root]/configurationManager/bin directory and enter the appropriate
command:
●
(Windows) ConfigurationManager.bat
●
(Linux, UNIX) ./ConfigurationManager.sh
2. If prompted, select a language and click OK.
3. On the Welcome screen, click Next.
4. On the Upgrade task selection screen, ensure that Upgrade from LiveCycle ES is not selected, then
click Next to continue.
Caution: If you want to upgrade an existing LiveCycle ES installation, do not continue this procedure. For
upgrade information and procedures, see the Preparing for Upgrading to LiveCycle ES guide
applicable to your current version of LiveCycle ES and the Upgrading to LiveCycle ES guide
applicable to your application server.
5. On the Solution Component Selection screen, select the LiveCycle ES solution components that you
installed and plan to deploy, and then click Next.
6. On the Task Selection screen, select all the tasks you want to perform and click Next.
Note: If you do not plan to configure the application server and deploy LiveCycle ES automatically by
using LiveCycle Configuration Manager, do not select the Configure application server,
Validate application server configuration, and Deploy LiveCycle ES EARs tasks. However,
you must manually configure the application server by completing the steps provided in
“Manually Configuring a WebSphere Cluster” on page 43.
Caution: Do not select the Configure application server option if you previously configured your
application server cluster manually. Selecting this option for a manually configured application
server cluster can cause LiveCycle ES errors or failure.
7. On the Configure LiveCycle ES (1 of 3) screen, click Configure. When the EAR files are configured, click
Next.
8. On the Configure LiveCycle ES (2 of 3) screen, set the directories that LiveCycle ES will use to access
fonts and store temporary data that is associated with processing jobs:
●
(Optional) To change the default location of the Adobe server fonts directory, type the path or
browse to the directory.
●
(Optional) Specify a directory for the Customer fonts directory box. The directory contains any
additional fonts that you have licensed and installed.
●
(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.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring and deploying LiveCycle ES
38
9. After you specify the directories, click Next.
10. On the Configure LiveCycle ES (3 of 3) screen, add the location of the GDS directory path by doing one
of these tasks:
●
Type the location of the GDS directory.
●
Click Browse and navigate to the location of the GDS directory.
Note: You must specify the location of the global document storage directory you established
previously (see the Preparing to Install to LiveCycle ES (Server Cluster) guide).
11. Click Next, click Configure to configure the LiveCycle ES EARs with this directory information and, after
the configuration is complete, click Next.
12. (Content Services ES only) On the LiveCycle Content Services ES Configuration screen, set the
parameters that Content Services ES will use:
●
Deploy Type: Select Cluster.
●
Index Root Directory: Specify the indexes directory that is used by Content Services ES.
●
Content storage root directory: Specify the root directory that is used by Content Services ES. The
content storage root directory should be a location shared by all WebSphere Application Server
instances in the cluster.
13. On the Configure LiveCycle ES Summary screen, click Next.
14. On the Deploy LiveCycle ES EARs screen, click Deploy.
15. (LiveCycle ES Connector for EMC Documentum, LiveCycle ES Connector for IBM FileNet, or
LiveCycle ES Connector for IBM Content Manager only) On the Configure LiveCycle ES Connectors
screen, press F1, follow the instructions in the Help dialog box, and then click Next.
16. On the Application Server Configuration Details screen, provide the information for the fields
(mandatory fields are denoted by an asterisk) and then click Verify Server Connection. When the
verification has completed successfully, click Next. Press F1 for details about the required information.
Note: During this task, the adobe-lcm-lcvalidator.ear file is deployed to the WebSphere Application
Server to capture version information.
Caution: Ensure that you select Cluster in the Deploy Type box.
17. On the Application Server Configuration Selection screen, select the tasks for LiveCycle Configuration
Manager to perform and then click Next. Press F1 for details about the required information.
If you prefer to configure the application server cluster manually, ensure that the tasks are deselected,
then click Next. You must perform the manual configuration tasks described in “Manually Configuring
a WebSphere Cluster” on page 43.
18. On the Server Settings Configuration screen, provide the information for the fields, and then click Next.
Press F1 for details about the required information.
If you are configuring your server settings manually, without exiting LiveCycle Configuration Manager,
perform the tasks that are described in the section “Configuring the WebSphere Application Server
instances” on page 43.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring LiveCycle ES for Deployment
Configuring and deploying LiveCycle ES
39
19. On the JMS Configuration screen, select the cluster you wish to use for your JMS, and then click Next.
Press F1 for details about the required information.
If you are configuring your JMS manually, without exiting LiveCycle Configuration Manager, perform
the tasks describe in the section “Configuring WebSphere Messaging” on page 55.
20. On the Datasource Configuration screen, 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.
If you are configuring your data source manually, without exiting LiveCycle Configuration Manager,
perform the tasks describe in the section “Configuring the LiveCycle ES database connectivity” on
page 46.
Note: If you are using Microsoft SQL Server for your database, you must download the appropriate
database drivers as described in Preparing to Install LiveCycle ES (Server Cluster). You can choose
to manually configure data sources instead of having LiveCycle Configuration Manager
configure them. Select Manually configure datasource in the WebSphere Administrative
Console before continuing, then, without exiting LiveCycle Configuration Manager, go to the
WebSphere Administrative Console and configure data sources, as needed, by following the
instructions in the “Manually Configuring WebSphere” chapter in this guide.
21. (If you selected “Configure Server Settings” only) On the Application Server Configuration screen,
click Configure. Restart the servers if you are prompted to do so. When the process is completed, click
Next.
22. (If you selected “Configure Datasource” only) On the Application Server Configuration Validation
screen, select the tasks for validating and then click Validate. When the process is completed, click
Next.
23. On the Deploy LiveCycle ES EARs screen, select the EAR files to deploy and the virtual host to deploy to,
and then click Deploy. This operation may take several minutes to complete. Restart the servers if you
are prompted to do so. When the deployment has completed successfully, click Next.
Caution: If you configured a non-default GDS directory in step 10, you must restart the WebSphere
Application Server before you deploy the LiveCycle ES EAR files.
24. On the LiveCycle ES Database Initialization screen, verify that the host (using the IP address) and port
information matches the host and port information for a LiveCycle ES server in the cluster, 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. Restart the servers if you are prompted to do so. When
the initialization has completed successfully, click Next.
Note: You need to initialize the database against only one server of the cluster.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring and deploying LiveCycle ES
40
25. (Business Activity Monitoring only) On the Initialize Business Activity Monitoring screen, provide the
information for the following fields:
Database type: The database on which BAM metadata is running.
BAM Host: The name or IP address of the computer that hosts the application server on which BAM
server is running.
BAM HTTP Port: The HTTP service port that the database uses (for example, 9080).
BAM Administrator User ID: The administrator ID that is required to log in to BAM Workbench. The
default user ID is system.
BAM Administrator Password: The password to log in to the BAM Workbench. The default
password is manager.
26. (Business Activity Monitoring only) Click Initialize to begin the initialization process and, when
initialization is complete, click Next to continue.
27. On the LiveCycle ES Server Information screen, in the Password box, type password. (This password is
the default administrator password; it is recommended that you change the password later.)
28. Click Verify Server Connection to ensure that the information for the application servers is correct
and, when the verification has completed successfully, 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.
29. On the LiveCycle Component Deployment screen, click Deploy. The components that are deployed at
this time are Java archive files that plug into the LiveCycle ES service container 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.
30. On the LiveCycle Component Deployment Validation screen, click Validate. LiveCycle Configuration
Manager validates that the LiveCycle components (Java archive files) are deployed to and running on
the LiveCycle ES server. Click View Progress Log to view the validation progress and, wen the
validation has completed successfully, click Next.
31. (Reader Extensions ES only) On the LiveCycle Reader Extensions ES Credential Configuration screen,
specify the details that are associated with the Rights credential that activates the solution component
services:
LiveCycle Reader Extensions ES Rights credential: The path and file name of the Rights
credential (.pfx or .p12 file type).
LiveCycle Reader Extensions ES Rights credential password: The password that is associated
with the credential. This password was provided with the credential file.
Name for the configured Rights Credential: The name (or alias) that LiveCycle Configuration
Manager gives the credential when it is configured.
This name appears in the Reader Extensions ES web interface, and the alias that is used to reference the
credential through SDK calls. You can create any unique name for the Rights credential.
Tip: You can skip this step at this time by selecting Configure later using LiveCycle Administration
Console. You can configure the Rights credential by using LiveCycle Administration Console after you
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Uninstalling EAR files
41
complete the deployment. (After logging in to LiveCycle Administration Console, click Home >
Settings >Trust Store Management > Local Credentials.)
Click Configure and then click Next.
32. (Optional) On the LiveCycle ES Samples Import screen, click Import. When the import has completed
successfully, click Next or click Skip LiveCycle Samples Import to import the samples at a later time.
33. On the Summary page, review the tasks performed and click Next. The Next steps screen displays URL
and login information.
34. Click Exit.
35. Restart each WebSphere Application Server instance in your cluster and each server in your JMS cluster.
Uninstalling EAR files
Perform the following procedure if you need to undeploy a LiveCycle ES solution component.
1. Start the application server.
2. Start WebSphere Administrative Console by typing http://hostname:port/admin in the URL line
of a web browser.
3. In the navigation tree, click Applications > Enterprise Applications.
4. Select the adobe-livecycle-native-websphere-[OS].ear, adobe-livecycle-websphere.ear, and
adobe-workspace-client.ear applications, and any other installed LiveCycle ES applications, and then
click Stop.
Note: The adobe-workspace-client.ear is deployed only with Process Management ES.
5. Select the adobe-livecycle-native-websphere-[OS].ear, adobe-livecycle-websphere.ear, and
adobe-workspace-client.ear applications, and any other installed LiveCycle ES applications, and then
click Uninstall.
6. Click Save directly to Master Configuration and then restart WebSphere.
After you uninstall the EAR file, you may need to reconfigure your EAR file and redeploy it if you have
added something that requires additional JVM or JMS settings. You should also run LiveCycle
Configuration Manager to migrate essential and non-essential data, reinitialize the database, and deploy
LiveCycle ES components.
Next steps
Now that you have configured and deployed LiveCycle ES, you can do the following tasks:
●
Verify the deployment. (See “Verifying the deployment and accessing LiveCycle Administration
Console” on page 68.)
●
Access LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 68.)
●
Configure PDF Generator ES or PDF Generator 3D ES. (See “Configuring LiveCycle PDF Generator ES or
3D ES” on page 73.)
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Next steps
42
●
Perform the final setup for Rights Management ES. (See “Final setup for LiveCycle
Rights Management ES” on page 81.)
●
Configure LiveCycle ES solution components to access LDAP. (See “Configuring LiveCycle ES to access
LDAP” on page 82.)
●
Perform watched folder performance-tuning for PDF Generator ES. (See “Setting PDF Generator ES or
3D ES watched folder performance parameters” on page 84.)
●
Enable FIPS mode. (See “Enabling FIPS mode” on page 84.)
●
Enable HTML digital signatures. (See “Configuring HTML digital signature” on page 85.)
●
Configuring Connector for EMC Documentum, Connector for IBM Content Manager, or
Connector for IBM FileNet. (See “Configuring the Connector for EMC Documentum service” on
page 86, “Configuring the Connector for IBM FileNet service” on page 90, or “Configuring the
LiveCycle ES Connector for IBM Content Manager” on page 98.)
●
Set environment variables for PDF Generator ES. (See “Setting environment variables” on page 73.)
●
Uninstall LiveCycle ES. (See “Uninstalling LiveCycle ES” on page 102.)
5
Manually Configuring a WebSphere Cluster
This chapter describes how to manually configure a WebSphere Application Server cluster to prepare for
the manual deployment of LiveCycle ES in the clustered environment. This chapter applies only if you
chose not to configure your WebSphere Application Server cluster automatically. For information about
how to automatically configure your application server, see “Configuring LiveCycle ES for Deployment” on
page 34.
At this point in the installation process, you have already installed LiveCycle ES files and run LiveCycle
Configuration Manager to configure the LiveCycle ES deployable archives. Now, you must perform the
following tasks manually:
●
Configure the WebSphere Application Servers. (See “Configuring the WebSphere Application Server
instances” on page 43.)
●
Configure JDBC connectivity. (See “Configuring the LiveCycle ES database connectivity” on page 46.)
●
Configure WebSphere messaging. (See “Configuring WebSphere Messaging” on page 55.)
Configuring the WebSphere Application Server instances
You must configure the WebSphere Application Server instances that you installed in the cluster by
performing the following tasks:
●
Modify the WebSphere time-out settings. (See “Modifying the WebSphere time-out settings” on
page 43.)
●
Modify the JVM properties. (See “Modifying the JVM properties” on page 44.)
●
Create a J2C authentication alias for the database. (See “Creating a J2C authentication alias for the
database” on page 45.)
Modifying the WebSphere time-out settings
You must modify the WebSphere time-out settings on each WebSphere Application Server in the cluster.
➤ To modify WebSphere time-out settings:
1. In the WebSphere Administrative Console navigation tree, click Servers > Application servers and, in
the right pane, click the server name.
2. Under Container Settings, click Container services > Transaction Service.
3. In the Total transaction lifetime timeout box, type 300 and then click OK.
4. Under Container Settings, click Container Services > ORB Service.
5. In the Request timeout box, type 360 and, in the Locate Request Timeout box, type 300, and then
click OK.
6. Under Server Infrastructure, click Administration > Administration Services.
7. On the next screen, click JMX Connectors and, in the table, click SOAPConnector.
43
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Modifying the JVM properties
44
8. On the next screen, click Custom properties and, in the table, click requestTimeout.
9. In the Value box, type 1800.
10. Click OK and then click Save directly to the master configuration.
Modifying the JVM properties
You must modify the the Java Virtual Machine (JVM) properties of each WebSphere Application Server
instance in the LiveCycle ES cluster to add LiveCycle ES options.
Before starting this procedure, you must know if your cluster uses a 32-bit or 64-bit JVM. See Preparing to
Install LiveCycle ES (Server Cluster) to determine the JVM required for your cluster configuration.
Before starting this procedure, you must determine how your LiveCycle ES cluster implements cluster
caching so that you can correctly configure a JVM argument for cluster caching. You may implement
cluster caching by using UDP or TCP but not both. The following factors may affect your choice:
●
Use UDP only if your cluster is based on IPv4.
●
Use TCP if your cluster is either IPv4-based or IPv6-based. On an IPv6-based cluster, you must use TCP to
be IPv6-compliant.
If you implement cluster caching by using TCP, you must also ensure that you configure the TCP
locators correctly (see “Configuring the caching locators (caching using TCP only)” on page 31).
➤ To modify JVM properties:
1. Log in to the WebSphere Administrative Console and, in the navigation tree, click Servers >
Application servers and then, in the right pane, click the server name.
2. Under Server Infrastructure, click Java and Process Management > Process Definition.
3. Under Additional Properties, click Java Virtual Machine and add or configure the following properties:
●
In the Initial Heap Size box, type 512
●
In the Maximum Heap Size box, set one of the following values:
●
(32-bit JVM only) Type 1024
●
(64-bit JVM only) Type 1792
●
In the Generic JVM arguments box, type -Dfile.encoding=utf8
●
In the Generic JVM arguments box, set one of the following values:
●
(32-bit JVM only) Type -XX:MaxPermSize=256m
●
(64-bit JVM only) Type -XX:MaxPermSize=512m
4. On the same screen, in the Generic JVM arguments box, add or configure one of the following
caching arguments:
●
(Caching using UDP discovery) Configure the multicast port argument in the following format:
-Dadobe.cache.multicast-port=<port number>
Note: The value for <port number> can be any available port between 1 and 65535. The multicast
port must be unique to the LiveCycle ES cluster (that is, the port must not be used by any other
cluster on the same network). It is recommended that you configure the same <port number>
on all nodes in the LiveCycle ES cluster, as in this example:
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Creating a J2C authentication alias for the database
45
-Dadobe.cache.multicast-port=33456
●
(Caching using TCP discovery) Configure the cluster locators argument in the following format:
-Dadobe.cache.cluster-locators=<IPaddress>[<port number>],<IPaddress>
[<port number>]
Note: Configure, as a comma-separated list, the locators for all nodes of the cluster. The value for
<IPaddress> is the IP address of the computer running the locator, and the value for <port
number> is any unused port between 1 and 65535. It is recommended that you configure the
same <port number> for all locators, as in this example:
-Dadobe.cache.cluster-locators=10.20.30.5[22345],10.20.30.6[22345]
5. Click Apply and click Custom Properties.
6. On the next screen, click New, add or configure the following properties, and then click OK:
●
In the Name box, type java.net.preferIPv4Stack.
●
In the Value box, type true.
7. Click OK and then click Save directly to the master configuration.
8. Restart the server.
9. Repeat steps 1 to 8 for each server in the cluster.
Creating a J2C authentication alias for the database
You must create a J2C authentication alias for the database.
➤ To create a J2C authentication configuration for the data source:
1. In the WebSphere Administrative Console navigation tree, click Security > Secure administration,
applications, and infrastructure.
2. In the right pane, under Authentication, click Java Authentication and Authorization Service > J2C
authentication data, and then click New.
3. Set the following properties:
●
In the Alias box, type an alias name appropriate to the database user, such as
IDP_DS/db2-db2user).
●
In the User ID box, type a name, such as db2user. This ID is the login credential used to access the
database that will be used with the IDP_DS data source.
●
In the Password, type a password for this user.
Note: In this guide, IDP_DS identifies the LiveCycle ES data source.
4. Click OK and then click Save directly to master configuration.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the LiveCycle ES database connectivity
46
Configuring the LiveCycle ES database connectivity
To enable WebSphere and your LiveCycle ES deployment to connect to the LiveCycle ES database, you
must create a database connection for LiveCycle ES by installing the database drivers and then setting up
a data source.
You must install drivers for the type of database that you use for the LiveCycle ES database. The drivers
should be placed in the installation directories of the application server.
You must configure the data source to connect to the database. For WebSphere, you can configure a DB2,
an Oracle 10g, or a SQL Server 2005 data source.
You will need the following information from tasks you did in Preparing to Install LiveCycle ES (Server
Cluster):
●
Database name
●
Server name
●
Port number
●
User name
●
Password
Refer to the following section that applies to your database:
●
“Configuring the DB2 data source” on page 46
●
“Configuring the Oracle data source” on page 49
●
“Configuring the SQL Server data source” on page 51
Configuring the DB2 data source
Configuring the DB2 data source requires you to install the DB2 database drivers, create a DB2 JDBC
provider on WebSphere, create the data source on WebSphere, and then configure the corresponding
connection pool.
➤ To install the DB2 database driver:
1. On a WebSphere Application Server instance, in the [appserver root] directory, create a directory named
db2libs.
2. Copy the db2jcc_license_cu.jar and db2jcc.jar files from one of these locations to the
[appserver root]\db2libs directory:
●
The java directory under your [dbserver root] directory, such as [dbserver root]/ibm/Sqllib/java
(Windows) or [dbserver root]/java (Linux or UNIX)
●
(DB2 version 8.2) [LiveCycle ES root]\lib\db\db2
●
(DB2 version 9.1) [LiveCycle ES root]\lib\db\db2\9.1
3. Repeat steps 1 to 2 for each WebSphere Application Server in the cluster.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the DB2 data source
47
➤ To create a DB2 JDBC provider:
1. On a WebSphere Application Server instance, in the WebSphere Administrative Console navigation
tree, click Environment > WebSphere Variables and, in right pane, click
DB2UNIVERSAL_JDBC_DRIVER_PATH.
2. In the Value box on the next screen, type the path to the db2libs directory.
3. Repeat steps 1 to 2 for each WebSphere Application Server instance, inserting the appropriate path to
the db2libs directory for the node on which the WebSphere Application Server instance resides.
4. Click OK or Apply and in the Messages box, click Save directly to master configuration.
5. In the navigation tree, click Resources > JDBC > JDBC Providers.
6. In the drop-down list above the table, select Cluster=lc8_cluster as the scope, and then click New.
7. In the Step 1 pane, set the following configuration and then click Next:
●
In the Database type list, select DB2.
●
In the Provider type list, select DB2 Universal JDBC Driver Provider.
●
In the Implementation type list, select Connection pool data source. Take note that for each
LiveCycle Configuration Manager configuration script, the field implementation class name is
com.ibm.db2.jcc.DB2ConnectionPoolDataSource.
●
In the Name box, keep the name DB2 Universal JDBC Driver Provider.
8. In the Step 2 pane, enter the path to the db2libs directory (for example, [appserver root]/db2libs), and
then click Next.
9. In the Step 3 pane, click Finish and then click Save directly to master configuration.
➤ To create the DB2 JDBC data source:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
provider you created in “To create a DB2 JDBC provider:” on page 47.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 pane, set the following configurations and then click Next.
●
In both the Data source name box and the JNDI name box, type IDP_DS.
●
In the list under Component-Managed Authentication and XA Recovery Authentication, select the
authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45, and then click Next.
4. In the Step 2 pane, type the database name and server name of the database you created in “Creating a
J2C authentication alias for the database” on page 45.
Note: If the port used by the database is not the default port (50000), also specify your alternative port
in the Port number box.
5. Ensure that Use this data source in container managed persistence (CMP) is selected.
6. Click Next and, in the Step 3 pane, click Finish.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the DB2 data source
48
7. In the right pane, click the data source you just created to modify additional parameters and set the
following configuration:
●
In the Container-managed authentication alias list, select the authentication alias created for this
data source in “Creating a J2C authentication alias for the database” on page 45.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
8. Click OK or Apply, and then click Save directly to master configuration.
➤ To configure IDP_DS connection pools:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the DB2
Universal JDBC Driver Provider you created in “To create a DB2 JDBC provider:” on page 47.
2. Under Additional Properties, click Data sources and, in the right pane, click IDP_DS.
3. On the next screen, under Additional Properties, click Connection Pool Properties and set the
properties as follows:
●
In the Maximum connections box, type 30.
●
In the Minimum connections box, type 1.
4. Click OK or Apply, and then click Save directly to master configuration.
➤ To create the DB2 JDBC data source for LiveCycle Rights Management ES:
Note: This procedures applies only if you have Rights Management ES installed.
1. In the navigation tree, click Resources > JDBC > JDBC Providers and click the provider you created in
“To create a DB2 JDBC provider:” on page 47.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 pane, set the following configurations and then click Next:
●
In the Data source name box, type RM_DS.
●
In the JNDI name box, type EDC_DS.
●
In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select
the authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45.
4. In the Step 2 pane, type the database name and server name of the database you created in “Creating a
J2C authentication alias for the database” on page 45.
Note: If the port used by the database is not the default port (50000), also specify your alternative port
in the Port number box.
5. Click Next and, in the Step 3 pane, click Finish.
6. Select the data source you just created to modify additional parameters and set the following
configuration:
●
In the Container-managed authentication alias list, select the authentication alias created for this
data source in “Creating a J2C authentication alias for the database” on page 45.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the Oracle data source
49
7. Click OK or Apply, and then click Save directly to master configuration.
➤ To configure RM_DS connection pools for LiveCycle Rights Management ES:
Note: This section applies only if you have Rights Management ES installed.
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
DB2 Universal JDBC Driver Provider provider created in “To create a DB2 JDBC provider:” on page 47.
2. Under Additional Properties, click Data sources and, in the right pane, click RM_DS.
3. On the next screen, under Additional Properties, click Connection Pool Properties and set the
properties as follows:
●
In the Maximum connections box, enter 20.
●
In the Minimum connections box, enter 1.
4. Click OK or Apply, and then click Save directly to master configuration.
Configuring the Oracle data source
Configuring the Oracle data source requires you to install the Oracle database drivers, create a Oracle JDBC
provider on WebSphere, create the data source on WebSphere, and then configure the corresponding
connection pool.
➤ To install the Oracle 10g database driver:
1. Download the Oracle 10g Release 2 (10.2.0.2 Thin) driver from this Oracle Database site.
2. For a WebSphere Application Server instance, in the [appserver root] directory, create a directory named
db_driver and copy to this directory the ojdbc14.jar file that you downloaded.
3. Repeat step 2 for each WebSphere Application Server instance in the cluster.
➤ To create the Oracle JDBC provider:
1. On a WebSphere Application Server instance, in the WebSphere Administrative Console navigation
tree, click Environment > WebSphere Variables and, in the right pane, click
ORACLE_JDBC_DRIVER_PATH.
2. Under General Properties, in the Value box, type the path to the ojdbc14.jar file you created in “To
install the Oracle 10g database driver:” on page 49 and then click OK.
3. Repeat steps 1 to 2 for each WebSphere Application Server instance, inserting the appropriate path to
the db_driver directory for the node on which the WebSphere Application Server instance resides.
4. Click Save directly to master configuration.
5. In the navigation tree, click Resources > JDBC > JDBC Providers.
6. In the drop-down list above the table, select Cluster=lc8_cluster as the scope and then click New.
7. In the Step 1 pane, set the following configuration and then click Next:
●
In the Database type list, select Oracle.
●
In the Provider type list, select Oracle JDBC Driver.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Configuring the Oracle data source
50
In the Implementation type list, select Connection pool data source.
8. In the Step 2 pane, accept the default database class path and then click Next.
9. In the Step 3 pane, click Finish and then click Save directly to master configuration.
➤ To create the Oracle JDBC data source:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
provider you created in “To install the Oracle 10g database driver:” on page 49.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 pane, set the following configurations and then click Next:
●
In both the Data source name and the JNDI name box, type IDP_DS.
●
In the list, under Component-Managed Authentication and XA Recovery Authentication, select the
authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45
4. In the Step 2 pane, type the following line in the URL box and then click Next:
jdbc:oracle:thin:@<server_host>:<port>:<SID>
where <server_host> is the IP address of the database server, <port> is the port on which the
database is listening (default 1521), and <SID> is the service ID of the database.
5. In the Step 3 pane, click Finish and then click Save directly to master configuration.
6. Select the data source you just created to modify additional parameters and set the following
configuration options:
●
In the Container-managed authentication alias list, select the authentication alias created for this
data source in “Creating a J2C authentication alias for the database” on page 45.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
7. Click OK or Apply, and then click Save directly to master configuration.
➤ To configure IDP_DS connection pools:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the Oracle
JDBC driver data source created in “To create the Oracle JDBC provider:” on page 49
2. Under Additional Properties, click Data sources and, in the right pane, click IDP_DS.
3. On the next screen, under Additional Properties, click Connection Pool Properties and, in the
Maximum connections box, type 30.
4. Click OK or Apply, and then click Save directly to master configuration.
➤ To create the Oracle JDBC data source for LiveCycle Rights Management ES:
Note: This section applies only if you have Rights Management ES installed.
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
provider you created in “To create the Oracle JDBC provider:” on page 49.
2. Under Additional Properties, click Data sources and then click New.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the SQL Server data source
51
3. In the Step 1 pane, set the following configurations and then click Next:
●
In the Data source name box, type RM_DS.
●
In the JNDI name box, type EDC_DS.
●
In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select
the authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45.
4. In Step 2 pane, type the following line in the URL box and then click Next:
jdbc:oracle:thin:@<server_host>:<port>:<SID>
where <server_host> is the IP address of the database server, <port> is the port on which the
database is listening (default 1521), and <SID> is the service ID of the database.
5. In the Step 3 pane, click Finish and then click Save directly to master configuration.
6. Select the data source you just created to modify additional parameters and set the following
configuration options:
●
In the Container-managed authentication alias list, select the authentication alias created for this
data source in “Creating a J2C authentication alias for the database” on page 45.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
7. Click OK and then click Save directly to master configuration.
➤ To configure RM_DS connection pools for LiveCycle Rights Management ES:
Note: This section applies only if you have Rights Management ES installed.
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the Oracle
JDBC driver provider created in “To create the Oracle JDBC provider:” on page 49
2. Under Additional Properties, click Data sources and, in the right pane, click RM_DS.
3. On the next screen, under Additional Properties, click Connection Pool Properties and set the
properties as follows:
●
In the Maximum connections box, enter 20.
●
In the Minimum connections box, enter 1.
4. Click OK or Apply, and then click Save directly to master configuration.
Configuring the SQL Server data source
Configuring the SQL Server data source requires you to install the SQL Server database drivers, create a
SQL Server JDBC provider on WebSphere, create the data source on WebSphere, and then configure the
corresponding connection pool.
➤ To install the SQL Server database driver:
●
If you have not done so, download and install the SQL Server 2005 JDBC Driver 1.2 from the Microsoft
Download site by following the site instructions.
Note: Make note of the directory location where you install the driver on your system.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the SQL Server data source
52
➤ To create the SQL Server 2005 JDBC provider:
1. In the WebSphere Administrative Console navigation tree, click Environment > WebSphere Variables
and, in the right pane, click MSSQLSERVER_JDBC_DRIVER_PATH.
2. Under General Properties, in the Value box, type the path to the sqljdbc.jar file you created in “To
install the SQL Server database driver:” on page 51 and then click OK.
3. Repeat steps 1 to 2 for each WebSphere Application Server instance, inserting the appropriate path to
the db_driver directory for the node on which the WebSphere Application Server instance resides.
4. Click Save directly to master configuration.
5. In the navigation tree, click Resources > JDBC > JDBC Providers.
6. In the drop-down list above the table, select Cluster=lc8_cluster as the scope, and then click New.
7. In the Step 1 pane, set the following configurations and then click Next:
●
In the Database type list, select User-defined.
●
In the Implementation class name box, type
com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource.
●
In the Name box, type LiveCycle - SQL Server - IDP_DS (default) or any meaningful
alternative name.
8. In the Step 2 pane, set the class path configuration as follows and then click Next:
${MSSQLSERVER_JDBC_DRIVER_PATH}/sqljdbc.jar
9. In the Step 3 pane, click Finish and then click Save directly to master configuration.
➤ To create the SQL Server 2005 data source:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
provider you created in “To create the SQL Server 2005 JDBC provider:” on page 52.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 pane, set the following configurations and then click Next:
●
In both the Data source name box and the JNDI name box, type IDP_DS.
●
In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select
the authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45.
4. In the Step 2 pane, replace the existing entry with the following in the Data store helper class name
box, and click Next.
com.ibm.websphere.rsadapter.GenericDataStoreHelper
5. In the Step 3 pane, click Finish and then click Save directly to master configuration.
6. Select the data source you just created to modify additional parameters.
7. Set the following configuration and then click OK:
●
In the Container-managed authentication alias list, select the authentication alias created for this
data source in “Creating a J2C authentication alias for the database” on page 45.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Configuring the SQL Server data source
53
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
8. Click Save directly to master configuration.
➤ To configure IDP_DS connection pools:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
User-defined JDBC Driver provider created in “To create the SQL Server 2005 JDBC provider:” on
page 52
2. Under Additional Properties, click Data sources and, in the right pane, click IDP_DS.
3. On the next screen, under Additional Properties, click Custom Properties.
4. For each property listed below, click New and enter the property Name and Value specified:
serverName: The IP address of the SQL server database
portNumber: The port number of the SQL Server database
databaseName: The name of the SQL Server database
5. Click OK or Apply and then click Save directly to master configuration.
6. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
User-defined JDBC Driver provider created in “To create the SQL Server 2005 JDBC provider:” on
page 52
7. Under Additional Properties, click Data sources and, in the right pane, click IDP_DS.
8. On the next screen, under Additional Properties, click Connection Pool Properties and, in the
Maximum connections box, enter 30.
9. Click OK or Apply and then click Save directly to master configuration.
10. Restart WebSphere Application Server Deployment Manager and the WebSphere Application Server
node agents.
➤ To create the SQL Server 2005 data source for LiveCycle Rights Management ES:
Note: This section applies only if you have Rights Management ES installed.
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
provider you created in “To create the SQL Server 2005 JDBC provider:” on page 52.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 pane, set the following configuration and then click Next:
●
In the Data source name box, type RM_DS.
●
In the JNDI name box, type EDC_DS.
●
In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select
the authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the SQL Server data source
4. In the Step 2 pane, replace the existing entry with the following in the Data store helper class name
box, and click Next.
com.ibm.websphere.rsadapter.GenericDataStoreHelper
5. In the Step 3 pane, click Finish and then click Save directly to master configuration.
➤ To configure RM_DS connection pools for LiveCycle Rights Management ES:
Note: This section applies only if you have installed Rights Management ES.
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
User-defined JDBC Driver provider created in “To create the SQL Server 2005 JDBC provider:” on
page 52
2. Under Additional Properties, click Data sources and, in the right pane, click RM_DS.
3. On the next screen, under Additional Properties, click Custom Properties.
4. For each property listed below, click New,and enter the property Name and Value specified:
serverName: The IP address of the SQL server database
portNumber: The port number of the SQL Server database
databaseName: The name of the SQL Server database
5. Click OK or Apply and then click Save directly to master configuration.
6. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
User-defined JDBC Driver provider created in “To create the SQL Server 2005 JDBC provider:” on
page 52.
7. Under Additional Properties, click Data sources and, in the right pane, click RM_DS.
8. On the next screen, under Additional Properties, click Connection Pool Properties and set the
properties as follows:
●
In the Maximum connections box, enter 20.
●
In the Minimum connections box, enter 1.
9. Click OK or Apply and then click Save directly to master configuration.
➤ To configure integrated security on Windows:
1. In the navigation tree, click Resources > JDBC > Data Sources and, in the right pane, click IDP_DS.
2. In the right pane, under Additional Properties, click Custom Properties, and then click New.
3. In the Name box, type integratedSecurity and, in the Value box, type true, then click Apply.
4. In the navigation tree, click Resources > JDBC > Data Sources and, in the right pane, click RM_DS.
5. In the right pane, under Additional Properties, click Custom Properties, and then click New.
6. In the Name box, type integratedSecurity and, in the Value box, type true.
7. Click Apply and and then click Save directly to master configuration.
54
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring WebSphere Messaging
55
8. On the computer where WebSphere is installed, add the sqljdbc_auth.dll file to the Windows systems
path (C:\Windows). The sqljdbc_auth.dll file is in the same location as the Microsoft SQL JDBC 1.2 driver
installation (default is [InstallDir]/sqljdbc_1.2/enu/auth/x86).
9. Modify the Log On As property of the Windows service that starts the WebSphere Application Server
(IBM WebSphere Application Server V6.1 - [node name]) by doing the following tasks:
●
Click Start > Settings > Control Panel > Administrative Tools > Services.
●
Right click IBM WebSphere Application Server V6.1 - [node name] and select Properties.
●
On the Log On tab, select This account and select a valid user account other than Local System,
then click OK.
10. Change SQL Server’s Security from Mixed mode to Windows Authentication only.
Configuring WebSphere Messaging
You must now configure the default messaging provider for WebSphere by performing these tasks:
●
“Configuring a default messaging provider” on page 55
●
(Microsoft SQL) “SQL Server JMS validation” on page 63
Configuring a default messaging provider
The recommended topology for LiveCycle ES in a WebSphere cluster is to have one active JMS messaging
engine that is external to the LiveCycle ES cluster. To ensure failover of the JMS messaging engine, a
second cluster of at least two servers should be created to host the messaging engine.
Each application server instance in the messaging engine cluster should run on a separate physical
computer to avoid a single point of hardware failure. The messaging cluster can use the same physical
computers that are used for the LiveCycle ES application server cluster, but the name of any specific
computer must be different in each cluster.
Perform the following tasks to configure a default messaging provider:
●
Create the messaging engine cluster.
●
Create the JDBC provider for the messaging engine.
●
Create J2C Authentication alias for the messaging engine.
●
Create the data source for the messaging provider.
●
Configure the connection pools for the messaging provider.
●
Create a service integration bus.
●
Define the bus members.
●
Create the messaging engines.
●
Set up WebSphere queue connection factories.
●
Set up WebSphere topic connection factories.
●
Set up WebSphere queue destinations.
●
Set up WebSphere topic destinations.
●
Set up WebSphere activation specifications.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
56
You can also perform the task “Assigning JMS activation specification” on page 61.
➤ To create the messaging engine cluster:
1. In the navigation tree, click Servers > Clusters, and then click New.
2. In the Cluster Name box, type the name of your cluster; for example, type lc8_jms_cluster.
3. Select the default settings for all other options.
4. Select Configure HTTP session memory-to-memory replication and then click Next.
5. In the Create First Cluster Member box, enter a member name. This name is for the first WebSphere
Application Server in the cluster.
6. In the Select Node list, select the node on which this cluster member will reside.
7. Select Create the member using an application server template, select default from the list, and
then click Next.
8. In the Member Name box, enter the name of another member to add to the cluster.
9. In the Select Node list, select the node on which this cluster member will reside.
10. Select Generate Unique HTTP Ports and then click Add Member.
11. Repeat steps 7 to 10 for each additional application server to add to the messaging engine cluster.
Note: You must create at least two application server instances in the message engine cluster.
12. Click Next, click Finish, and then click Save changes to the master configuration.
➤ To create the JDBC provider for the messaging engine cluster:
1. In the WebSphere Administrative Console navigation tree, click Resources > JDBC > JDBC Providers.
2. In the drop-down list above the table, select Cluster=lc8_jms_cluster as the scope, and then click
New.
3. Create a new JDBC provider for lc8_jms_cluster by following the procedure that pertains to your
database:
●
(DB2) “To create a DB2 JDBC provider:” on page 47
●
(Oracle) “To create the Oracle JDBC provider:” on page 49
●
(SQL Server) “To create the SQL Server 2005 JDBC provider:” on page 52
➤ To configure J2C authentication for the messaging engine cluster data source:
1. In the WebSphere Administrative Console navigation tree, click Security > Secure administration,
applications, and infrastructure.
2. Under Authentication, click Java Authentication and Authorization Service > J2C authentication
data, and then click New.
3. Set the following properties:
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
●
In the Alias box, enter an alias name appropriate to the database user; for example, type
IDP_JMS_DS/db2-db2user.
●
In the User ID box, type a user ID (for example, type db2user). This user ID is the login credential
used to access the database that will be used with the IDP_JMS_DS data source.
●
In the Password box, type a type a password for this user.
57
4. Click OK or Apply, and then click Save directly to master configuration.
➤ To create the data source for the messaging provider:
1. In the WebSphere Administrative Console navigation tree, click Resources > JDBC > JDBC Providers
and select the provider that you created for your LiveCycle JMS cluster. (See “To create the JDBC
provider for the messaging engine cluster:” on page 56)
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 pane, set the following configurations and then click Next:
●
In both the Data source name box and the JNDI name box, type JMS_DS.
●
In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select
the authentication alias created for this data source in “Creating a J2C authentication alias for the
database” on page 45.
4. In the Step 2 pane, set the following configurations and then click Next:
Database name: Enter the name of the LiveCycle ES database.
Server name: Enter the name of the server on which the LiveCycle ES database runs.
Note: The JMS_DS data source should point to the LiveCycle ES database (that is, the same database
instance used by the IDP_DS data source, described in “Configuring the LiveCycle ES database
connectivity” on page 46). This ensures proper backup and recovery of your LiveCycle ES
implementation.
5. In the Step 3 pane, click Finish and then click Save directly to master configuration.
6. Select the JMS_DS data source you just created, set the following configuration, and then click OK:
●
In the Container-managed authentication alias list, select the authentication alias created for this
data source in “Creating a J2C authentication alias for the database” on page 45.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
7. Click Save directly to master configuration.
➤ To configure JMS_DS connection pools:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the JDBC
driver for the provider that you created for your LiveCycle ES cluster.
2. Under Additional Properties, click Data sources and, in the right pane, click JMS_DS.
3. On the next screen, under Additional Properties, click Connection Pool Properties and set the
properties as follows:
●
In the Maximum connections box, enter 20.
●
In the Minimum connections box, enter 1.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
58
4. Click OK or Apply and then click Save directly to master configuration.
➤ To create a service integration bus:
1. In the navigation tree, click Service Integration > Buses and click New.
2. In the Name box, type IDP_JMS_Bus, and then click Next.
3. Click Finish and then click Save changes to the master configuration.
➤ To create bus members:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS_Bus.
2. Under Topology, click Bus Members and then click Add.
3. Select Cluster and select your messaging engine from the list, and then click Next.
4. Select Data store and then click Next.
5. In the Data Source JNDI Name box, type JMS_DS.
6. In the Schema name box, specify the database schema name used when creating the database.
7. Select the authentication alias for this data source and click Next.
8. Click Next and review the configuration.
9. Click Finish and then click Save changes to the master configuration.
Caution: Do not add the LiveCycle ES cluster as a bus member. If it is added, remove it.
➤ To configure JMS queue connection factories:
1. In the navigation tree, click Resources > JMS > Queue connection factories.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Select Default messaging provider and click OK.
4. Under Administration on the next screen, in the Name box and the JNDI name box, type
QueueConnectionFactory.
5. Under Connection, in the Bus name list, select IDP_JMS_Bus.
6. Under Quality of Service, set these properties:
●
In the Non persistent message reliability list, select As bus destination.
●
In the Persistent message reliability list, select As bus destination.
7. Under Advanced Administrative, select the appropriate component-managed authentication alias as
defined in “Creating a J2C authentication alias for the database” on page 45.
8. Click OK or Apply and then click Save directly to master configuration.
9. In the list, click QueueConnectionFactory and, under Additional Properties, click Connection pool
properties.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
59
10. On the next screen, under General Properties, set the following properties:
●
In the Maximum connections box, type 50.
●
In the Minimum connections box, type 10.
11. Click OK or Apply and then click Save directly to master configuration.
12. Repeat steps 2 through 11 to create another JMS queue connection factory, replacing
QueueConnectionFactory with JobManagerQueueConnectionFactory in step 5 for the Name box
and the JNDI name box.
➤ To configure JMS topic connection factories:
1. In the navigation tree, click Resources > JMS > Topic connection factories.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Select Default messaging provider and click OK.
4. Under Administration on the next screen, in the Name box and the JNDI name box, type
TopicConnectionFactory.
5. Under Connection, in the Bus name list, select IDP_JMS_Bus.
6. Under Quality of Service, set these properties:
●
In the Non persistent message reliability list, select As bus destination.
●
In the Persistent message reliability list, select As bus destination.
7. Under Advanced Administrative, select the appropriate component-managed authentication alias as
defined in “Creating a J2C authentication alias for the database” on page 45.
8. Click OK or Apply and then click Save directly to master configuration.
9. In the list, select TopicConnectionFactory and, under Additional Properties, click Connection Pool
Properties.
10. Under Administration on the next screen, set the following properties:
●
In the Maximum connections box, type 50.
●
In the Minimum connections box, type 10.
11. Click OK or Apply and then click Save directly to master configuration.
➤ To create a queue:
1. In the navigation tree, click Resources > JMS > Queues.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Accept the default or select Default messaging provider and then click OK.
4. Under Administration on the next screen, set these properties:
●
In the Name box, type adobe_PECommandQueue.
●
In the JNDI name box, type queue/adobe_PECommandQueue.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
60
5. Under Connection, set the properties as follows:
●
In the Bus name list, select IDP_JMS_Bus.
●
In the Queue name list, select other, please specify and then type adobe_PECommandQueue in
the box that appears.
●
In the Delivery mode list, select Persistent.
6. Under Advanced, in the Read ahead list, select Inherited from connection factory.
7. Click OK or Apply and then click Save directly to master configuration.
8. Repeat steps 3 through 7 for each of the queues in the following table, replacing the properties under
the Connection group set in step 5 with the appropriate values.
Name
Persistent
JNDI name
adobe_PEDCommandQueue
Yes
queue/adobe_PEDCommandQueue
adobe_PEInteractionQueue
Yes
queue/adobe_PEInteractionQueue
adobe_JobManagerQueue
Yes
queue/adobe_JobManagerQueue
Next, create a bus destination for each queue defined. (See “To create bus destinations for queues:” on
page 60).
➤ To create bus destinations for queues:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS_Bus.
2. Under Destination Resources on the next screen, click Destinations, and then click New.
3. Under Select Destination Type on the next screen, select Queue and then click Next.
4. In the step 1 pane, in the Identifier box, type adobe_PECommandQueue and click Next.
5. Click Next, click Finish, and then click Save directly to the master configuration.
6. Repeat steps 3 through 5 for each queue defined in “To create a queue:” on page 59.
Next, create an exception destination for the adobe_PECommandQueue queue (see “To create an
exception destination for the adobe_PECommandQueue queue:” on page 60) and create topics (see “To
create bus destinations for queues:” on page 60).
➤ To create an exception destination for the adobe_PECommandQueue queue:
1. On any WebSphere Application Server instance in the cluster, open a command prompt and navigate
to the [appserver root]/bin directory.
2. Start the wsadmin utility by entering the following command:
●
(Windows) wsadmin.bat
●
(Linux or UNIX) wsadmin.sh
3. From the wsadmin command prompt, view the current SIB destination of adobe_PECommandQueue
by entering the following command:
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
61
$AdminTask showSIBDestination {-bus IDP_JMS_Bus -name
adobe_PECommandQueue}
4. If required, modify the SIB destination of adobe_PECommandQueue to adobe_PEDCommandQueue
by entering the following command:
$AdminTask modifySIBDestination {-bus IDP_JMS_Bus -name
adobe_PECommandQueue -exceptionDestination adobe_PEDCommandQueue}
5. Save the changes by entering the command $AdminConfig save
6. Quit the wsadmin utility by entering the command quit
➤ To create topics:
1. In the navigation tree, click Resources > JMS > Topics.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. Under Administration on the next screen, set the properties as follows:
●
In the Name box, type adobe_TaskEventTopic
●
In the JNDI name box, type topic/adobe_TaskEventTopic
5. Under Connection on the screen, set the properties as follows:
●
In the Topic name box, type adobe_TaskEventTopic
●
In the Bus name box, select IDP_JMS_Bus
●
In the Topic space box, select Default.Topic.Space
●
In the JMS Delivery mode box, select Persistent
6. Click OK or Apply and then click Save directly to master configuration.
Next, create a bus destination for each topic defined. (See “To create bus destinations for topics:” on
page 61).
➤ To create bus destinations for topics:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS_Bus.
2. Under Destination Resources on the next screen, click Destinations, and then click New.
3. Under Select Destination Type on the next screen, select Topic space, and then click Next.
4. In the step 1 pane, in the Identifier box, type adobe_TaskEventTopic and click Next.
5. Click Next, click Finish, and then click Save directly to master configuration.
6. Repeat steps 3 through 5 for each queue defined in “To create topics:” on page 61.
Assigning JMS activation specification
You must assign JMS activation specifications. These activation specifications are associated with
message-driven beans and are required for the MDBs to receive messages from the queues and topics.
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring a default messaging provider
➤ To create PECommand_AS:
1. In the WebSphere Administrative Console navigation tree, click Resources > JMS > Activation
specifications.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. Under Administration on the next screen, in the Name box and the JNDI name box, type
PECommand_AS.
5. Under Destination, set the properties as follows:
●
In the Destination type box, type Queue
●
In the Destination JNDI name box, type queue/adobe_PECommandQueue
●
In the Bus name box, type IDP_JMS_Bus
6. Click OK or Apply and then click Save directly to master configuration.
➤ To create PEDCommand_AS:
1. In the navigation tree, click Resources > JMS > Activation specifications.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. Under Administration on the next screen, in the Name box and the JNDI name box, type
PEDCommand_AS.
5. Under Destination, set the properties as follows:
●
In the Destination type box, type Queue
●
In the Destination JNDI name box, type queue/adobe_PEDCommandQueue
●
In the Bus name box, type IDP_JMS_Bus
6. Click OK or Apply and then click Save directly to master configuration.
➤ To create Task_Event_AS:
1. In the navigation tree, click Resources > JMS > Activation specifications.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. Under Administration on the next screen, in the Name box and the JNDI name box, type
Task_Event_AS.
5. Under Destination properties, set the properties as follows:
●
In the Destination type box, type Topic
●
In the Destination JNDI name box, type topic/adobe_TaskEventTopic
●
In the Bus name box, type IDP_JMS_Bus
62
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
SQL Server JMS validation
63
6. Click OK or Apply and then click Save directly to master configuration.
➤ To create JobManager_AS:
1. In the navigation tree, click Resources > JMS > Activation specifications.
2. In the list above the table, select Cluster=lc8_cluster as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. Under Administration on the next screen, in the Name box and the JNDI name box, type
JobManager_AS.
5. Under Destination properties, set the properties as follows:
●
In the Destination type box, type Queue
●
In the Destination JNDI name box, type queue/adobe_JobManagerQueue
●
In the Bus name box, type IDP_JMS_Bus
6. Click OK or Apply, and then click Save directly to master configuration.
SQL Server JMS validation
The SQL Server JMS setup requires additional verification. This is also required if the JMS or LiveCycle
Configuration Manager verification fails.
Note: Validation is required only for Microsoft SQL Server.
➤ To verify the JMS setup with SQL Server:
1. In the WebSphere Administrative Console navigation tree, click Service Integration > Buses, and, in
the right pane, click IDP_JMS_Bus.
2. Under Topology, click Messaging Engines. When working, it should display a green arrow. The status
for the bus is probably unknown at this point.
3. Select your messaging engine.
4. Under Additional Properties, click Message store. The schema name must match the user name; if it
does not, set it to match. To set up the Microsoft SQL Server database and users, see Preparing to Install
LiveCycle ES.
5. Click Save directly to master configuration.
6. Delete any tables that begin with SIB to ensure that no conflicts exist with old bus configurations.
7. Restart each WebSphere Application Server instance in lc8_jms_cluster and retry step 1 to ensure that
the bus is running.
Next steps
After you configure your WebSphere Application Server cluster, do the following tasks:
Adobe LiveCycle ES
Manually Configuring a WebSphere Cluster
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Next steps
●
Configure the LiveCycle ES EAR files by using LiveCycle Configuration Manager. (See “Configuring
LiveCycle ES for Deployment” on page 34.)
●
Choose one of these ways to deploy the LiveCycle ES EAR files to your WebSphere Application
Server cluster:
●
Automatically: Use LiveCycle Configuration Manager. (See “Configuring LiveCycle ES for
Deployment” on page 34.)
●
Manually: See “Manually Deploying WebSphere” on page 65.
64
6
Manually Deploying WebSphere
This chapter describes how to manually deploy your LiveCycle ES solution components to a WebSphere
cluster. This chapter applies only if you chose not to deploy LiveCycle ES to your WebSphere Application
Server cluster automatically. For information about how to automatically deploy LiveCycle ES to your
application server cluster, see “Configuring and deploying LiveCycle ES” on page 36.
At this point in the installation process, you have already installed LiveCycle ES files, run LiveCycle
Configuration Manager to configure the LiveCycle ES deployable archives, and manually configured your
WebSphere Application Server cluster. Now you manually deploy the LiveCycle ES deployable archives.
This chapter includes the following topics:
●
“About deploying LiveCycle ES solution components” on page 65
●
“Deploying to WebSphere” on page 66
●
“Starting the application” on page 66
About deploying LiveCycle ES solution components
Before you deploy LiveCycle ES, ensure that you completed these tasks:
●
Installed the required software and files, and know the location of the directories you will be working
with. If you did not complete this task, see Preparing to Install LiveCycle ES (Server Cluster).
●
Run LiveCycle Configuration Manager to configure and assemble LiveCycle ES solution components
according to your system and application server requirements. To add a solution component to your
deployment, you can run LiveCycle Configuration Manager to make the changes and then redeploy the
updated EAR file.
If you are deploying LiveCycle ES for the first time, initialize the database by using LiveCycle Configuration
Manager after you deploy the product.
If you are using an external web server, see your web server documentation for information about the
configuration that is required to allow access to the application server.
WebSphere directory name
This chapter refers to the WebSphere Application Server home directory as [appserver root]. The home
directory is the same as the one specified for the WAS_INSTALL_ROOT environment variable. Similarly,
[LiveCycleES root] refers to the location where LiveCycle ES components are installed. (See “Conventions
used in this document” on page 8.)
Summary of deployable components
During the deployment process, you need to deploy the following components for LiveCycle ES:
●
adobe-livecycle-native-websphere-[OS].ear
●
adobe-livecycle-websphere.ear
●
adobe-workspace-client.ear
65
Adobe LiveCycle ES
Manually Deploying WebSphere
Configuring LiveCycle ES Application Server Clusters using WebSphere
●
Deploying to WebSphere
66
adobe-contentservices.ear (LiveCycle Content Services ES only)
After LiveCycle ES is configured using LiveCycle Configuration Manager (required), these files are located
in the [LiveCycleES root]/configurationManager/export/ directory.
Deploying to WebSphere
Deploy LiveCycle ES solution components to WebSphere by deploying the component EAR files to the
application server using the WebSphere Administrative Console.
Before deploying to WebSphere, start the application server on your computer. After you deploy the
required components, stop and restart the application server before you start any services.
➤ To deploy the EAR files:
1. In the WebSphere Administrative Console navigation tree, click Applications > Install New
Application.
2. In the right pane, select Remote file system or Local File System.
3. Click Browse, navigate to one of the EAR files in “Summary of deployable components” on page 65,
and select the EAR file.
4. Select Show me all installation options and parameters and click Next.
5. Select Generate Default Bindings and click Next.
6. In the left column of the Map Modules to Servers pane on the right, select the second step and then,
from the list of available clusters and servers, select lc8_cluster.
Note: If you already configured a web server for load balancing in your cluster, you must also select the
web server. Use the CTRL key to select the additional server.
7. Click Select all and then click Apply.
8. In the left column of the Summary pane on the right, select the last step and click Finish.
9. When the EAR file is installed successfully, in the Messages box, click Save directly to Master
Configuration.
10. Repeat these steps for each of the EAR files in “Summary of deployable components” on page 65.
Starting the application
After deploying the solution component, you need to start the applications. When the red “X” beside the
name of the application changes to a green arrow, the application has been deployed and started
successfully. WebSphere displays an error message if it cannot start the application.
For information about WebSphere error messages, see your WebSphere Application Server
documentation.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters using WebSphere
Manually Deploying WebSphere
Next steps
67
➤ To start an application in WebSphere:
1. In the WebSphere Administrative Console navigation tree, click Applications > Enterprise
Applications.
2. Select any or all of the LiveCycle ES applications that you want to start and click Start. The red “X”
beside the status of each application changes to a green arrow, indicating that the application is
running.
Next steps
You must run LiveCycle Configuration Manager to initialize the database and deploy the components and
LiveCycle ES archive files (LCAs). You can also choose to validate the component and archive deployment.
(See “Configuring LiveCycle ES for Deployment” on page 34.)
7
Post-Deployment Activities
This chapter describes how to verify the deployment by accessing the LiveCycle Administration Console
and checking the application server log files. It also describes how to get started using LiveCycle ES
solution components and services after they are installed, configured, and deployed to your application
server:
●
“Verifying the deployment and accessing LiveCycle Administration Console” on page 68
●
“Accessing solution component web applications” on page 70
●
“Accessing the Content Services ES repository” on page 72
●
“Accessing User Management” on page 71
●
“Configuring LiveCycle PDF Generator ES or 3D ES” on page 73
●
“Final setup for LiveCycle Rights Management ES” on page 81
●
“Final setup for Content Services ES” on page 81
●
“Configuring LiveCycle ES to access LDAP” on page 82
●
“Setting PDF Generator ES or 3D ES watched folder performance parameters” on page 84
●
“Enabling FIPS mode” on page 84
●
“Configuring HTML digital signature” on page 85
●
“Configuring the Document Management service for LiveCycle Content Services ES” on page 86
●
“Configuring the Connector for EMC Documentum service” on page 86
●
“Configuring the Connector for IBM FileNet service” on page 90
●
“Configuring the LiveCycle ES Connector for IBM Content Manager” on page 98
●
“Uninstalling LiveCycle ES” on page 102
After you configure the settings in this chapter, for additional information about configuring your
LiveCycle ES environment for development and production, see Administering LiveCycle ES.
Verifying the deployment and accessing LiveCycle Administration
Console
You can verify the deployment by logging in to LiveCycle Administration Console. If you log in successfully,
then LiveCycle ES is running on the application server and the default user is created in the database.
You can review the application server log files to ensure that components were deployed correctly or to
determine the cause of any deployment issues you may encounter.
Accessing LiveCycle Administration Console
LiveCycle Administration Console is the web-based portal for accessing a variety of configuration pages
where you can set run-time properties that control the way LiveCycle ES operates. When you log in to
LiveCycle Administration Console, you can access User Management, Watched Folder, and Email client
configuration, and administrative configuration options for other services. LiveCycle Administration
68
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Viewing the log files
69
Console also provides access to Applications and Services, which administrators use for managing archives
and deploying services to a production environment.
The default user name and password for logging in is administrator and password. After you log in the first
time, access User Management and change the password. If you have upgraded, the user name and
password remain the same as when they were set by the administrator when was configured.
Before you access LiveCycle Administration Console, LiveCycle ES must be deployed and running on your
application server.
For information about using LiveCycle Administration Console, see Applications and Services Administration
Help.
➤ To access LiveCycle Administration Console:
1. Type the following URL in a web browser:
http://[host name]:[port]/adminui
The default port number for WebSphere is 9080.
2. In the User Name box, type administrator and, in the Password box, type password.
3. After you log in, click Services to access the service administration pages or click Settings to access the
pages on which you can administer settings for different solution components.
Viewing the log files
You can view the log files to verify that the LiveCycle ES cluster functions properly. Events, such as run-time
or startup errors, are recorded to the application server log files. If you have problems deploying to the
application server, you can use the log files to help you find the problem. You can open the log files by
using any text editor.
The following log files are located in the [appserver root]/profiles/default/logs/servername directory:
●
SystemErr.log
●
SystemOut.log
●
StartServer.log
➤ To verify the LiveCycle ES cluster:
1. Ensure that all WebSphere Application Server instances of the cluster are started.
2. View the Gemfire.log file, located in the directory [LiveCycle ES temp ]/adobews_[Cell Name]_[Node
Name]_[Server Name]/Caching. Messages such as the following confirm that the cache is connected to
all servers of the cluster:
[info 2008/01/22 14:24:31.109 EST GemfireCacheAdapter <UDP mcast
receiver> nid=0x5b611c24] Membership: received new view
[server-0:2916|1] [server-0:2916/2913, server-1:3168/3165]
[info 2008/01/22 14:24:31.125 EST GemfireCacheAdapter <View Message
Processor> nid=0x7574d1dc] DMMembership: admitting member
<server-1:3168/3165>; now there are 2 non-admin member(s)
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Accessing solution component web applications
70
Note: Ensure that the number of non-admin members (two in the example log entry above) matches
the number of members in your cluster. A discrepancy indicates that some members of the
cluster are not connected to the cache.
Accessing solution component web applications
After LiveCycle ES is deployed, you can access the web applications that are associated with the following
solution components:
●
LiveCycle Reader Extensions ES
●
LiveCycle Workspace ES
●
LiveCycle Rights Management ES
●
LiveCycle Content Services ES
After accessing the web applications by using the default administrator permissions to ensure that they
are accessible, you can create additional users and roles so that others can log in and use the applications.
(See User Management Help.)
➤ To access the Reader Extensions ES web application:
Note: You must apply a Reader Extensions ES credential and apply the user roles for a new user. (See
“Configuring SSL” in Administering LiveCycle ES.)
1. Open a web browser and enter this URL:
http://localhost:9080/ReaderExtensions (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
Note: You must have administrator or superuser privileges to log in using the default user name and
password. To allow other users to access the Reader Extensions ES web application, you must create
the users in User Management and grant them the Reader Extensions Web Application role .
➤ To access Workspace ES:
1. Open a web browser and enter this URL:
http://localhost:9080/workspace (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
➤ To access the Content Services ES web application:
Note: You must apply the LiveCycle Contentspace Administrator or LiveCycle Contentspace roles for a
new user to login to this web application. To do this, you must create the users in User Management
and grant them the appropriate role.
1. Open a web browser and enter this URL:
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Accessing Rights Management ES
71
http://localhost:9080/contentspace (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
Accessing Rights Management ES
You must create a user with the LiveCycle Rights Management End User role in User Management and log
in to the Rights Management ES administrator or end-user applications by using the login information
that is associated with that user.
➤ To access the Rights Management ES end-user web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/edc/Login.do
Note: The administrator user cannot access the Rights Management ES end-user web application. You can
create new users by using LiveCycle Administration Console.
➤ To access the Rights Management ES administration web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/adminui
2. Click Services > LiveCycle Rights Management ES. For information about setting up users and roles
for Rights Management ES, see Administering LiveCycle ES.
➤ To assign the LiveCycle Rights Management End User role:
1. Log in to LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 68.)
2. Click Settings > User Management > Users and Groups.
3. In the Find box, type all and, in the In list, select Groups.
4. Click Find and, for the required domains, click All Principals in the list that appears.
5. Click the Role Assignments tab and click Find Roles.
6. In the list of roles, select the check box next to LiveCycle Rights Management End User.
7. Click OK and then click Save.
Accessing User Management
By using User Management, administrators can maintain a database of all users and groups, synchronized
with one or more third-party user directories. User Management provides authentication, authorization,
and user management for LiveCycle ES solution components, including Reader Extensions ES,
Workspace ES, Rights Management ES, Process Management ES, and Forms ES.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Accessing the Content Services ES repository
72
➤ To access User Management:
1. Log in to LiveCycle Administration Console.
2. On the home page, click Settings > User Management.
Note: For information about configuring users with User Management, click User Management Help in
the upper-right corner of the User Management page.
Accessing the Content Services ES repository
You can access the Content Services ES repository using:
●
File Transfer Protocol (FTP)
●
Web-based Distributed Authoring and Versioning (WebDAV)
●
Common Internet File Services (CIFS)
➤ To access the Content Services ES repository using FTP:
1. Open a web browser and enter this URL:
ftp://[server name]:[port]
Note: The default port for the Content Services ES repository is port 8021.
2. Log in using your user name and password.
Note: You can not log in to the Content Services ES repository by FTP using the Mozilla FireFox
browser. Use another browser (for example, Internet Explorer) to access the Content Services ES
repository by FTP.
➤ To access the Content Services ES repository using WebDAV:
1. Open Windows Explorer and navigate to My Network Places .
2. Right click and select Add a network place.
3. Enter the following network address:
http://[server name]:[port]/contentspace/webdav
4. Log in using your user name and password.
➤ To access the Content Services ES repository using CIFS:
Note: Your Content Services ES repository must be previously configured to support CIFS access.
1. On a computer running the Windows operating system, click Start > Run.
2. Enter the following:
\\[server name]a
Note: You will not be asked for a user name or password.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring LiveCycle PDF Generator ES or 3D ES
73
Configuring LiveCycle PDF Generator ES or 3D ES
If you installed LiveCycle PDF Generator ES or LiveCycle PDF Generator 3D ES as part of your LiveCycle ES
solution, complete the following tasks:
●
“Setting environment variables” on page 73
●
“Configuring the EJB pool size” on page 74
●
“Setting the Adobe PDF Printer as the default printer” on page 75
●
“Configuring Acrobat 9.0” on page 76
●
“Installing East Asian characters in Windows” on page 77
●
“Adding fonts to PDF Generator ES or PDF Generator 3D ES” on page 77
●
“Installing the IPP client” on page 80
Setting environment variables
If you installed the PDF Generator ES or PDF Generator 3D ES solution component and configured it to
convert files to PDF, for some file formats, you must manually set an environment variable that contains
the absolute path of the executable that is used to start the corresponding application. The table below
lists the native applications that PDF Generator ES or PDF Generator 3D ES requires you to set up
environment variables for.
Application
Environment variable
Example
Acrobat
Acrobat_PATH
C:\Program
Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe
Note: The Acrobat_PATH environment variable is
case-sensitive.
Adobe
FrameMaker®
FrameMaker_PATH
C:\Program
Files\Adobe\FrameMaker7.1\FrameMaker.exe
Notepad
Notepad_PATH
C:\WINDOWS\Notepad.exe
OpenOffice
OpenOffice_PATH
C:\Program Files\OpenOffice.org 2.0
Adobe
PageMaker®
PageMaker_PATH
C:\Program
Files\Adobe\PageMaker 7.0\PageMaker.exe
WordPerfect
WordPerfect_PATH
C:\Program Files\WordPerfect Office
12\Programs\wpwin12.exe
Note: The environment variable OpenOffice_PATH is set to the installation folder instead of the path to
the executable.
You do not need to set up the paths for Microsoft Office applications such as Word, PowerPoint, Excel,
Visio, and Project, or for AutoCAD. The Generate PDF service starts these applications automatically if they
are installed on the server.
➤ To create a new Windows environment variable:
1. Select Start > Control Panel > System.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Setting environment variables
74
2. Click the Advanced tab and click Environment Variables.
3. In the System variables section, click New.
4. Enter the environment variable name you need to set (for example, enter Photoshop_PATH). This
folder is the one that contains the executable file. For example, type the following code:
D:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe
➤ To set the PATH variables on Linux or UNIX (OpenOffice only):
●
Type the following command:
export OpenOffice_PATH /opt/openoffice.org2
Configuring the EJB pool size
Four different stateless session beans exist for enforcing independent pool sizes for these types of input
files:
●
PostScript and Encapsulated PostScript files
●
Image files (such as BMP, TIFF, PNG, JPEG etc.)
●
OpenOffice files
●
All other file types (except HTML files) such Microsoft Office files, Adobe Photoshop, PageMaker, and
FrameMaker files
The pool size for HTML-to-PDF conversions is not managed through the use of stateless session beans.
The default pool size for PostScript and Encapsulated PostScript files, and for Image files, is set to 3, and the
default pool size for OpenOffice and other file types (except HTML) is set to 1.
You can configure the PS/EPS and Image pool-size to a different value based on your server hardware
configuration, such as the number of CPUs, the number of cores within each CPU, and so on. However, it is
mandatory for the OpenOffice and the pool size for other file types to be left unchanged for proper
functioning of PDF Generator ES.
This section describes how the pool size for PS2PDF and Image2PDF can be configured for each of the
supported application-servers.
The text below assumes that the following two LiveCycle ES application EAR files have been deployed on
the application server:
●
adobe-livecycle-websphere.ear
●
adobe-livecycle-native-websphere-[platform].ear
In the above line, [platform] should be replaced with one of these four strings, depending on whether you
are running your application server on a Windows, Linux, SunOS, or an AIX operating system:
●
“x86_win32”
●
“x86_linux”
●
“sparc_sunos”
●
“powerpc_aix”
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Post-Deployment Activities
Setting the Adobe PDF Printer as the default printer
75
➤ To configure the pool size for PS2PDF and Image2PD:
1. Ensure that IBM WebSphere Application Server is running.
2. Log in to the WebSphere Administrative Console at http://<hostname>:9060/ibm/console.
The URL might be different if you chose WebSphere to run on a non-standard port or if HTTPS is
enforced. Depending on whether security is enabled, WebSphere may prompt you to authenticate
yourself with administrator privileges.
3. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and in
the right pane, click the server name.
4. Under Server Infrastructure, click Java and Process Management > Process Definition.
5. Under Additional Properties, click Java Virtual Machine and then click Custom Properties.
6. Click the property com.ibm.websphere.ejbcontainer.poolSize. If this property is not in the list, click
New and type the property name in the Name box.
If the property existed previously, its value should appear as follows:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#NativeToPDFInvoker=1,1:LiveCycle
8#adobe-pdfg-bmc-invoker-ejb.jar#OpenOfficeToPDFInvoker=1,1:LiveCycle8#ado
be-pdfg-bmc-invoker-ejb.jar#ImageToPDFInvoker=3,3:LiveCycle8#adobe-pdfg-bm
c-invoker-ejb.jar#PSToPDFInvoker=3,3
Here, imageToPDFInvoker=3,3 and PSToPDFInvoker=3,3 specify that the values of the
minimum/maximum EJB pool size for Image2PDF and PS2PDF conversions are set to 3 each.
7. Modify these values appropriately. For example, to configure a pool size of 5 for Image2PDF and a pool
size of 8 for PS2PDF, the modified property value should read as follows:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#NativeToPDFInvoker=1,1:LiveCycle
8#adobe-pdfg-bmc-invoker-ejb.jar#OpenOfficeToPDFInvoker=1,1:LiveCycle8#ado
be-pdfg-bmc-invoker-ejb.jar#ImageToPDFInvoker=5,5:LiveCycle8#adobe-pdfg-bm
c-invoker-ejb.jar#PSToPDFInvoker=8,8.
Note: In the string above, replace LiveCycle8 with the actual name of the LiveCycle ES application
deployed on WebSphere Application Server.
8. Save your changes and restart WebSphere Application Server. If you are running an application server
cluster, you need to make identical changes on each of the application server cluster nodes. Therefore,
to save time, it is a good idea to make the changes before you create a cluster. This ensures that these
values will be automatically set on each cluster node that is created after these changes are made on
the primary node.
Setting the Adobe PDF Printer as the default printer
You must set the Adobe PDF Printer to be the default printer on the server. If the Adobe PDF Printer is not
set as the default, PDF Generator ES cannot convert files successfully.
➤ To set the default printer:
1. Select Start > Printers and Faxes.
2. In the Printers and Faxes window, right-click Adobe PDF and select Set as Default Printer.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring Acrobat 9.0
76
Configuring Acrobat 9.0
This procedure is required only if you upgraded to or installed Acrobat 9.0 after you completed the
LiveCycle ES installation. Upgrading Acrobat can be completed after you run LiveCycle Configuration
Manager and deploy LiveCycle ES to the application server.
➤ To configure Acrobat 9.0 Professional Extended for use with PDF Generator ES or
PDF Generator 3D ES:
1. If an earlier version (8.1 or earlier) of Acrobat is installed, uninstall it by using Add or Remove Programs
in the Windows Control Panel.
2. Acrobat 9.0 Professional Extended is provided with the LiveCycle ES media or as an option for ESD
downloads.
●
If you are using the media, insert the Acrobat 9.0 Professional Extended CD.
●
If you are using the ESD downloads, download Acrobat 9.0 Professional Extended from your ESD
location.
3. Install Acrobat 9.0 Professional Extended by running the AutoPlay.exe file.
4. Navigate to the additional\scripts folder on the LiveCycle ES installation media.
5. Run the following batch file:
Acrobat_for_PDFG_Configuration.bat [LiveCycleES root]
6. Open Acrobat and select Help > Check for updates > Preferences.
7. Deselect Automatically check for Adobe updates.
➤ To validate the Acrobat 9.0 Professional Extended installation:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat. If the PDF file opens
successfully, Acrobat 9.0 Professional Extended is installed correctly.
2. If the PDF file does not open correctly, uninstall Acrobat and reinstall it.
Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after the Acrobat installation
is completed and disable the automatic updates for Acrobat.
Set the Acrobat_PATH environment variable to point to Acrobat.exe (such as C:\Program Files\
Adobe\Acrobat 9.0\Acrobat\Acrobat.exe).
➤ To configure native application support:
1. Install and validate Acrobat as described in the previous procedure.
2. Set Adobe PDF printer as the default printer.
3. (PDF Generator 3D ES) Register the DLL file located at [LiveCycle8.2 root]\plugins\x86win32\
PDFG3dAddin.dll.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Post-Deployment Activities
Installing East Asian characters in Windows
77
Installing East Asian characters in Windows
When HTML files are converted to PDF by using PDF Generator ES or PDF Generator 3D ES, some East
Asian languages, such as Japanese, Korean, and Chinese, and also right-to-left languages, such as Arabic,
Armenian, Georgian, Hebrew, Indic, Thai, and Vietnamese, may not be displayed in the PDF file.
To ensure that these languages are displayed in Windows, appropriate fonts must be present on the client
and server.
➤ To install East Asian characters in Windows:
1. Select Start > Control Panel and open Regional and Language Options.
2. Click the Languages tab and select Install Files for East Asian Languages.
3. Click the Advanced tab and select all the options under Code Page Conversion Tables.
If converted PDF files are still missing fonts, verify that the Arial Unicode MS (TrueType) font (ARIALUNI.TTF)
is present in the C:\WINDOWS\Fonts directory.
Adding fonts to PDF Generator ES or PDF Generator 3D ES
LiveCycle ES provides a central repository of fonts named Adobe LiveCycle ES Fonts Management, which is
accessible to all LiveCycle ES solution components. The Fonts Management module is a central font
repository for all fonts that are accessible to and shared by various LiveCycle ES solution components.
However, PDF Generator ES or PDF Generator 3D ES frequently needs to start external (non-LiveCycle ES)
applications on the server that cannot be configured to use the LiveCycle ES fonts repository. This section
describes how to make the extra fonts available to these applications so that PDF documents that are
created by using PDF Generator ES or PDF Generator 3D ES can use these extra fonts.
Non-Adobe applications
The following list contains non-LiveCycle ES applications that PDF Generator ES or PDF Generator 3D ES
can use for PDF generation on the server side:
Windows-only Applications
●
Microsoft Office Word
●
Microsoft Office Excel
●
Microsoft Office PowerPoint
●
Microsoft Office Project
●
Microsoft Office Visio
●
Microsoft Office Publisher
●
AutoDesk AutoCAD
●
Corel WordPerfect
●
Adobe Photoshop CS
●
Adobe FrameMaker
●
Adobe PageMaker
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Post-Deployment Activities
Adding fonts to PDF Generator ES or PDF Generator 3D ES
78
Adobe Acrobat Professional Extended
Multiplatform applications
●
OpenOffice Writer
●
OpenOffice Calc
●
OpenOffice Draw
●
OpenOffice Impress
Note: In addition to these applications, your list may include additional applictions that you added.
Of the above applications, the OpenOffice Suite (which includes Writer, Calc, Draw, and Impress) is
available on Windows, Solaris, and Linux platforms, whereas other applications are available on Windows
only.
Adding new fonts to Windows applications only
All the Windows-only applications that are mentioned above can access all the fonts that are available in
the C:\Windows\Fonts (or equivalent) folder. In addition to C:\Windows\Fonts, each of these applications
may have its own private fonts folders.
Therefore, if you plan to add any custom fonts to the LiveCycle ES fonts repository, you must ensure that
the same fonts are available to the Windows-only applications also by copying these fonts to either
C:\Windows\Fonts or to an equivalent folder.
Your custom fonts must be licensed under an agreement that allows you to use them with the applications
that have access to these fonts.
Adding new fonts to OpenOffice Suite
Adding custom fonts to OpenOffice Suite is explained on the OpenOffice Fonts-FAQ page at
http://wiki.services.openoffice.org.
In addition, OpenOffice Suite has these resources about the fonts-related behavior:
●
OpenOffice Fonts Troubleshooting Guide at http://www.openoffice.org/FAQs/fontguide.html. Some of
the text in this guide is applicable only to OpenOffice 1.x and therefore may be obsolete for OpenOffice
2.x
●
Importing Fonts into OpenOffice 2.1 at http://openoffice.blogs.com/openoffice/2007/02/
font_import_wiz.html. Even though this blog mentions OpenOffice 2.1, the instructions that are
mentioned should be applicable to OpenOffice 2.2 and later.
Adding new fonts to other applications
If you extended PDF Generator ES by adding support for PDF creation by using other applications, see the
user guide that is applicable to the corresponding application to determine the best procedure to use to
add new fonts to that application. In Windows, copying your custom fonts to the C:\Windows\Fonts (or
equivalent) folder should be sufficient.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring HTML to PDF conversions
79
Configuring HTML to PDF conversions
The HTML-to-PDF conversion process is designed to use the settings from Acrobat 9.0, thereby overriding
the settings from LiveCycle PDF Generator ES.
Note: This configuration is required to enable the HTML-to-PDF conversion process, otherwise this
conversion type will fail.
➤ To configure the HTML-to-PDF conversion:
1. Install and validate Acrobat as described in “Configuring Acrobat 9.0” on page 76.
2. Locate the pdfgen.api file in the [LiveCycle8.2 root]\plugins\x86win32 directory and copy it to
[Acrobat9.0 root]\Acrobat\plug_ins directory.
Enabling support for Unicode fonts in HTML to PDF conversions
To enable PDF Generator ES or PDF Generator 3D ES to generate PDF files from HTML source files that
contain Unicode fonts, complete the following steps.
Caution: The HTML-to-PDF conversion will fail if a zipped input file contains HTML files with double-byte
characters in the filenames. To avoid this problem, do not use double-byte characters when
naming HTML files.
1. Copy the Unicode font to any of the following directories as appropriate for your system:
●
Windows
[Windows root]\windows\fonts
[Windows root]\winnt\fonts
●
UNIX
/usr/X/lib/X11/fonts/TrueType
/usr/openwin/lib/X11/fonts/TrueType
/usr/share/fonts/default/TrueType
/usr/X11R6/lib/X11/fonts/ttf
/usr/X11R6/lib/X11/fonts/truetype
/usr/X11R6/lib/X11/fonts/TrueType
/usr/X11R6/lib/X11/fonts/TTF
/Users/cfqauser/Library/Fonts
/System/Library/Fonts
/Library/Fonts
/Users/ + System.getProperty(<user name>, root) + /Library/Fonts
System.getProperty(JAVA_HOME) + /lib/fonts
2. Modify the font-name mapping in the cffont.properties file located in the
[LiveCycle8.2 root]/adobe-generatepdf-dsc.jar file:
●
Unpackage this archive, and locate the cffont.properties file and open it in an editor.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Installing the IPP client
80
In the comma-separated list of Java font names, add a map to your Unicode system font for each
font type, as shown in these examples where kochi mincho is the name of your Unicode system
font:
dialog=Arial, Helvetica, kochi mincho
dialog.bold=Arial Bold, Helvetica-Bold, kochi mincho ...
●
Save and close the properties file, and then repackage and redeploy the adobe-generatepdf-dsc.jar
file.
Note: On a Japanese operating system, specify the font mapping in the cffont.properties.ja file as well,
which takes precedence over the standard cffont.properties file.
Tip: Fonts in the list are searched from left to right, using the first font found. HTML-to-PDF conversion
logs return a list of all the font names that are found in the system. To determine the font name you
need to map, add the font to one of the directories above, restart the server and run a conversion. You
can determine from the log files the font name to use for mapping.
To embed the font in the generated PDF files, set the embedFonts property in the cffont.properties file to
true (the default is false).
Installing the IPP client
PDF Generator ES includes an Internet Printing Protocol (IPP) client installer for installation of the
PDF Generator ES Internet printer on a client computer. After the installation is complete, a
PDF Generator ES printer is added to the list of existing printers on the client computer. This printer can
then be used to send documents for conversion to PDF.
Note: The PDF Generator ES IPP Client (wizard) is supported on 32-bit Windows platforms only.
If the IPP Client fails to install on Windows or if you want to install the IPP printer on UNIX or Linux
platforms, use the operating system’s native Add Printer utility and configure it as described in “To
configure IPP Printer on Windows using the native Add Printer wizard:” on page 81.
➤ To install the PDF Generator ES IPP Client:
1. Ensure that you successfully installed PDF Generator ES on your server.
2. From a Windows client computer, enter the following URL in your web browser, where [server] is the
name of the server where you installed PDF Generator ES and [port] is the application server port
used:
http://[server]:[port]/pdfg-ipp/install
3. On the Configure Internet Port screen, select Use the specified user account and provide the
credentials of a LiveCycle user who has the PDFG Administrator/User role. This user must also have an
email address that can be used to receive the converted files. To have this security setting apply to all
users on the client computer, select Use the same security options for all users, and then click OK.
Upon successful installation, a dialog box appears, indicating that “The Printer Adobe LiveCycle
PDF Generator ES has been successfully installed.”
4. Click OK. You will now have a printer named Adobe LiveCycle PDF Generator ES in your list of available
printers.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Final setup for LiveCycle Rights Management ES
81
➤ To configure IPP Printer on Windows using the native Add Printer wizard:
1. Click Start > Printers and Faxes and double-click Add Printer.
2. Click Next, select A network printer, or a printer attached to another computer, and then click
Next.
3. Select Connect to a printer on the internet or on a home or office network and type the following
URL for the IPP printer, where [server] is the server name and [port] is the port number where
the server is running:
http://[server]:[port]/pdfg-ipp/printer
4. On the Configure Internet Port screen, select Use the specified user account and provide valid User
Management credentials.
5. In the Printer Driver Select box, choose any standard PostScript-based printer driver (for example, HP
Color LaserJet PS).
6. Complete the installation by choosing appropriate options (for example, setting this printer as default).
Note: The user credentials used while adding the printer must have a valid email ID configured in User
Management to receive the response.
7. Configure the email service’s sendmail service. Provide a valid SMTP server and authentication
information in the service’s configuration options.
➤ To install and configure the PDF Generator ES IPP Client using Proxy server port forwarding
1. Configure port forwarding on the CC Proxy server on a particular port to the LiveCycle ES server, and
disable the authentication at proxy server level (since LiveCycle ES uses its own authentication). If a
client connects to this Proxy server on the forwarded port, then all the requests will be forwarded to
the LiveCycle ES server.
2. Install PDFG-IPP printer using the following URL:
http://[proxy server]:[forwarded port]/pdfg-ipp/install.
3. Provide the necessary credentials for authentication of the IPP printer.
4. The IPP printer will be installed on the client machine which you can use for PDF conversion using the
firewall protected LiveCycle ES server.
Final setup for LiveCycle Rights Management ES
Rights Management ES requires the application server to be configured to use SSL. (See
Administering LiveCycle ES.)
Final setup for Content Services ES
If your LiveCycle ES installation uses Content Services ES, you must perform additional manual
configuration of the application server after deployment. Complete the following procedure on your
application server.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring LiveCycle ES to access LDAP
82
Note: You must configure and deploy LiveCycle ES before you perform this procedure (see “Configuring
and deploying LiveCycle ES” on page 36). This procedure configures directories that are created
only when you deploy LiveCycle ES.
➤ To configure final setup for Content Services ES:
1. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and, in
the right pane, click the server name.
2. Under Server Infrastructure, click Java and Process Management > Process Definition.
3. Under Additional Properties, click Java Virtual Machine and add or configure the following properties:
●
In the Generic JVM arguments box, type
-Dalfresco.tcp.initial_hosts=<host name>[<port value>],<host
name>[<port value>]
Note: Replace <host name> with the names of the computers in the cluster. Replace <port value>
with the port number (any value between 7800 and 8000) for that computer.
Caution: You must include all computers of the cluster by naming them, separated by commas, in the
arguments list.
4. Under Additional Properties, click Custom Properties.
5. Click New, add or configure the following properties, and then click OK:
●
In the Name box, type alfresco.cluster.name
●
In the Value box, type lc8_cluster
6. Click New, add or configure the following properties,and then click OK:
●
In the Name box, type alfresco.tcp.port_range
●
In the Value box, type 3
7. Click New, add or configure the following properties, and then click OK:
●
In the Name box, type alfresco.tcp.start_port
●
In the Value box, type <port value>
Note: Replace <port value> with the port number that you configured in step 3 for the computer.
8. Click New, add or configure the following properties, and then click OK:
●
In the Name box, type index.recovery.mode
●
In the Value box, type AUTO
9. Click Save directly to the master configuration.
10. Repeat steps 1 to 9 for each WebSphere Application Server of the cluster.
Configuring LiveCycle ES to access LDAP
If you configured LDAP for LiveCycle 7.x products, those settings are migrated during the upgrade process,
and you do not need to perform the steps in this section. If you did not previously configure LDAP, you can
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring LiveCycle ES to access LDAP
83
use the following procedure as a guideline when configuring User Management to support authentication
using LDAP.
➤ To configure User Management with LDAP (Enterprise Domain):
1. Open a web browser, navigate to http://[host name]:[port]/adminui and log in. (See “Accessing
LiveCycle Administration Console” on page 68.)
2. Click Settings > User Management > Domain Management, and then click New Enterprise
Domain.
3. In the ID box, type a unique identifier for the domain and, in the Name box, type a descriptive name for
the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
4. Click Add Authentication and, in the Authentication Provider list, select LDAP.
5. Click OK.
6. Click Add Directory and, in the Profile Name box, type a name for your LDAP profile.
7. Click Next.
8. Specify values in the Server, Port, SSL, and Binding boxes, and in the Populate Page with box, select
a directory settings option such as Default Sun ONE values. (See “Directory settings” in User
Management Help.)
9. (Optional) Test your configuration:
●
Click Test. The screen displays a message indicating either a successful server test or any
configuration errors that exist.
10. Click Next and configure the User Settings as required. (See “Directory settings” in User Management
Help.)
11. (Optional) Test your configuration:
●
Click Test.
●
In the Search Filter box, verify the search filter or specify a new search filter, and then click Submit.
The screen displays a list of entries that match the search criteria.
●
Click Close to return to the User Settings screen.
12. Click Next configure the Group Settings as required. (See “Directory settings” in User Management
Help.)
13. (Optional) Test your configuration:
●
Click Test.
●
In the Search Filter box, verify the search filter or specify a new search filter, and then click Submit.
The screen displays a list of entries that match the search criteria.
●
Click Close to return to the Group Settings screen.
14. Click Finish to exit the New Directory page and then click OK to exit.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere Setting PDF Generator ES or 3D ES watched folder performance pa-
➤ To configure User Management with LDAP (Local Domain):
1. Open a web browser, navigate to http://[host name]:[port]/adminui, and log in. (See “Accessing
LiveCycle Administration Console” on page 68.)
2. Click Settings > User Management > Domain Management, and then click New Local Domain.
Setting PDF Generator ES or 3D ES watched folder performance
parameters
To avoid java.io.IOException error messages indicating that not enough disk space is available to
perform PDF conversions by using a watched folder, you can modify the settings for PDF Generator ES
PDF Generator 3D ES in LiveCycle Administration Console.
You must also ensure that the maximum transaction time-out and ORB service values have the proper
values“Modifying the WebSphere time-out settings” on page 43).
➤ To set performance parameters for PDF Generator ES or PDF Generator 3D ES:
1. Log in to LiveCycle Administration Console and click Services > Applications and Services > Service
Management.
2. In the list of services, navigate to and click PDFGConfigService, and then set the following values:
●
PDFG Cleanup Scan Seconds: 1800
●
Job Expiration Seconds: 6000
●
Server Conversion Timeout: Change the default of 270 to a higher value, such as 450.
3. Click Save and restart the server.
4. Click Next and, on the next screen, click Advanced Targeting.
5. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
6. Click Next and, on the next screen, click Advanced Targeting.
7. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
8. Click Next and, on the next screen, click Advanced Targeting.
9. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
Enabling FIPS mode
LiveCycle ES provides a FIPS mode to restrict data protection to Federal Information Processing Standard
(FIPS) 140-2 approved algorithms using the RSA BSAFE Crypto-C 2.1 encryption module.
If you did not enable this option by using LiveCycle Configuration Manager during LiveCycle ES
configuration or if you enable it but want to turn it off, you can change this setting through LiveCycle
Administration Console.
Modifying FIPS mode requires you to restart the server.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Post-Deployment Activities
Configuring HTML digital signature
85
FIPS mode does not support Acrobat versions earlier than 7.0. If FIPS mode is enabled and the Encrypt
With Password and Remove Password processes include the Acrobat 5 setting, the process fails.
In general, when FIPS is enabled, the Assembler service does not apply password encryption to any
document. If this is attempted, a FIPSModeException is thrown, indicating that “Password encryption
is not permitted in FIPS mode.” Additionally, the PDFsFromBookmarks element is not supported in FIPS
mode when the base document is password-encrypted.
➤ To turn FIPS mode on or off:
1. Log in to LiveCycle Administration Console.
2. Click Settings > Core System > Core Configurations > Configurations.
3. Select Enable FIPS to enable FIPS mode or deselect it to disable FIPS mode.
4. Click OK and restart the application server.
Note: LiveCycle ES software does not validate code to ensure FIPS compatibility. It provides a FIPS
operation mode so that FIPS-approved algorithms are used for cryptographic services from the
FIPS-approved libraries (RSA).
Configuring HTML digital signature
To use the HTML digital signature feature of Forms ES, complete the following procedure.
➤ To enable HTML digital signature:
1. Manually deploy the [LivecycleES root]/deploy/adobe-forms-ds.ear file to your application server.
2. Log in to LiveCycle Administration Console and click Service > LiveCycle Forms ES.
3. Select HTML Digital Signature Enabled and then click Save.
Overriding session management for Content Services ES
You must override session management settings for Content Services ES in WebSphere Application Server
and then ensure that session replication is set to none.
➤ To override session management and disable session replication:
1. In the WebSphere Administrative Console navigation tree, click Applications > Enterprise
applications, then in the right pane click LiveCycle Content Services.
2. Under Web Module Properties, click Session management.
3. Under General Properties, select Override session management.
4. Under Additional Properties, click Distributed environment settings.
5. Under General Properties, locate Distributed sessions and select None.
6. Click Apply or OK.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the Document Management service for
7. Click Save to master configuration.
Configuring the Document Management service for
LiveCycle Content Services ES
If you installed Content Services ES and your application server is running on a non-default port (that is, a
port other than 9080 in WebSphere), modify the port that the Document Management service uses.
➤ To modify the port:
1. Log in to LiveCycle Administration Console and click Services > Applications and Services > Service
Management.
2. In the list, select DocumentManagementService.
3. On the Configuration tab, in the HTTP Port box, specify the port numbers you are using on each
member of the cluster (as a comma-separated list - for example, specify 9080, 9081, 9082), and
then click Save.
Configuring the Connector for EMC Documentum service
If you installed the Connector for EMC Documentum service as part of your LiveCycle ES solution,
complete the following procedure to configure the service to connect to the Documentum repository.
➤ To configure Connector for EMC Documentum:
1. Locate the adobe-component-ext.properties file in the [WAS HOME]/AppsServer/profiles/[profile name]
folder (if the file does not exist, create it).
2. Add a new system property that provides the following Documentum Foundation Classes JAR files
(and for the Connector for EMC Documentum 5.3 only, the location of the Documentum Content
Server config folder):
●
dfc.jar
●
(Connector for EMC Documentum 5.3) dfcbase.jar
●
(Connector for EMC Documentum 6.0) aspectjrt.jar
●
log4j.jar
The new system property should take on this form:
[component id].ext=[JAR files and/or folders]
For example, using default Content Server and Documentum Foundation Classes installations, add to
the file one of the following system properties on a new line, with no line breaks, and end the line with
a carriage return:
●
Connector for EMC Documentum 5.3 only:
com.adobe.livecycle.ConnectorforEMCDocumentum.ext=
C:/Documentum/Config,
C:/Program Files/Documentum/Shared/dfc.jar,
C:/Program Files/Documentum/Shared/dfcbase.jar,
C:/Program Files/Documentum/Shared/log4j.jar
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Configuring the Connector for EMC Documentum service
87
Connector for EMC Documentum 6.0 only:
com.adobe.livecycle.ConnectorforEMCDocumentum.ext=
C:/Program Files/Documentum/Shared/dfc.jar,
C:/Program Files/Documentum/Shared/aspectjrt.jar,
C:/Program Files/Documentum/Shared/log4j.jar
Note: The above text contains formatting characters for line breaks. If you copy and paste this text, you
must remove the formatting characters.
3. (Connector for EMC Documentum 6.0 only) Delete the dfc.keystore file located in the
C:\Documentum\config directory.
Note: This step is required due to incompatible JDK requirements for WebSphere and Documentum
Foundation Classes of EMC Documentum 6.0.
4. If WebSphere Application Server is not currently running, start the server. Otherwise, stop and then
restart the server.
5. Repeat step 1 to step 4 on each WebSphere Application Server instance of the cluster.
6. Open a web browser and enter this URL:
http://localhost:9080/adminui (local deployment using the default port)
7. Log in using the default user name and password:
User name: administrator
Password: password
8. Navigate to Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings
and perform these tasks:
●
Type all the required Documentum repository information.
●
To use Documentum as your repository provider, under Repository Service Provider Information,
select EMC Documentum Repository Provider, and then click Save. (For more information, click
the Help link in the upper-right corner of the page in the EMC Documentum Help. )
9. (Optional) Navigate to Services > LiveCycle ES Connector for EMC Documentum > Repository
Credentials Settings, click Add, specify the Docbase information, and then click Save. (For more
information, click Help in the upper-right corner.)
10. Navigate to Services > Applications and Services > Service Management and select these services:
●
EMCDocumentumAuthProviderService
●
EMCDocumentumContentRepositoryConnector
●
EMCDocumentumRepositoryProvider
11. Click Start. If any of the services do not start correctly, check the settings entered in step 8.
12. Do one of the following tasks:
●
To use the Documentum Authorization service (EMCDocumentumAuthProviderService) to display
content from a Documentum repository in the Resources view of Workbench ES, continue with this
procedure. Using the Documentum Authorization service overrides the default LiveCycle ES
authorization and must be configured to log in to Workbench ES using Documentum credentials.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Configuring the Connector for EMC Documentum service
88
To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super
administrator credentials (by default, Administrator and password).
You have now completed the required steps for this procedure. Use the credentials provided in step 8
for accessing the default repository in this case and use the default LiveCycle ES authorization service.
13. Restart WebSphere Application Server.
14. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
15. Click New Enterprise Domain, and type a domain ID and name. The domain ID is the unique identifier
for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
16. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Select EMCDocumentumAuthProvider and then click OK.
17. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP, and then click OK.
18. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required.
●
Click Next, configure the user settings, click Next, configure group settings, as required, and then
click Next.
For details about the settings, click User Management Help in the upper-right corner of the page.
19. Click OK to exit the Add Directory page and then click OK again.
20. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
21. Navigate to Settings > User Management > Users and Groups.
22. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Configuring the Connector for EMC Documentum service
89
Click OK a second time to confirm the role assignment.
Repeat this step for all users that you assign roles to. For more information , click User Management
Help in the upper-right corner of the page.
23. Start Workbench ES and log in by using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The Documentum repository should now be visible in the Resources view within Workbench ES. If you
do not log in using the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 8.
24. (Optional) If you intend to install the LiveCycle ES Samples for Connector for EMC Documentum, create
a Documentum repository named Samples, and then install the samples in that repository.
After you configure the Connector for EMC Documentum service, it is recommended that you see
Administering LiveCycle ES for information about configuring Workbench ES functions properly with your
Documentum repository.
Creating the XDP MIME format in your Documentum repository
Before users can store and retrieve XDP files from a Documentum repository, you must do one of these
tasks:
●
Create a corresponding XDP format in each repository where users will access XDP files.
●
Configure the Connector for EMC Documentum service to use a Documentum Administrator account
when accessing the Documentum repository. In this case, the Connector for EMC Documentum service
uses the XDP format whenever it is required.
➤ To create the XDP format on Documentum Content Server using Documentum Administrator:
1. Log in to Documentum Administrator.
2. Click Formats and then select File > New > Format.
3. Type the following information in the corresponding fields:
Name: xdp
Default File Extension: xdp
Mime Type: application/xdp
4. Repeat steps 1 to 3 for all other Documentum repositories where users will store XDP files.
➤ To configure the Connector for EMC Documentum service to use a Documentum Administrator:
1. Open a web browser and enter this URL:
http://localhost:[port]/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the Connector for IBM FileNet service
90
4. Under Documentum Principal Credentials Information, update the following information and then
click Save:
User Name: [Documentum Administrator user name]
Password: [Documentum Administrator password]
5. Click Repository Credentials Settings, select a repository from the list or, if none exist, click Add.
6. Provide the appropriate information in the corresponding fields and then click Save:
Repository Name: [Repository Name]
Repository Credentials User Name: [Documentum Administrator user name]
Repository Credentials Password: [Documentum Administrator password]
7. Repeat steps 5 to 6 for all repositories where users will store XDP files.
Configuring the Connector for IBM FileNet service
If you installed the Connector for IBM FileNet service as part of your LiveCycle ES solution, you must
configure the service to connect to the FileNet object store. See one of the following sections appropriate
to your version of IBM FileNet:
●
“Configuring the connector using FileNet 3.5” on page 90
●
“Configuring the connector using FileNet 4.0.1” on page 93)
Configuring the connector using FileNet 3.5
Complete the following procedure to configure the Connector for IBM FileNet service using FileNet 3.5.
➤ To configure the connector using FileNet 3.5:
1. Locate the adobe-component-ext.properties file in the [appserver root]/profiles/[profile name] folder (if
the file does not exist, create it)
2. Add a new system property that provides the location of the following FileNet Application Engine JAR
files:
●
activation.jar
●
javaapi.jar
●
log4j-1.2.8.jar
●
mailapi.jar
●
p8cjares.jar
●
soap.jar
●
xercesimpl.jar
●
xml-apis.jar
●
(optional) pe.jar
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the connector using FileNet 3.5
91
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service.
The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system,
add to the file the following system property on a new line, with no line breaks, and end the line with a
carriage return:
Note: The following text contains formatting characters for line breaks. If you copy this text to a location
outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext=
C:/Program Files/FileNet/lib2/activation.jar,
C:/Program Files/FileNet/lib2/javaapi.jar,
C:/Program Files/FileNet/lib2/log4j-1.2.8.jar,
C:/Program Files/FileNet/lib2/mailapi.jar,
C:/Program Files/FileNet/lib2/p8cjares.jar,
C:/Program Files/FileNet/lib2/soap.jar,
C:/Program Files/FileNet/lib2/xercesImpl.jar,
C:/Program Files/FileNet/lib2/xml-apis.jar,
C:/Program Files/FileNet/lib2/pe.jar
Note: Add the text C:/Program Files/FileNet/lib2/pe.jar only if your deployment uses the
IBMFileNetProcessEngineConnector service.
3. If WebSphere Application Server is not currently running, start the server. Otherwise, stop and then
restart the server.
4. Repeat steps 1 to 3 on each WebSphere Application Server instance of the cluster.
5. Open a web browser and enter this URL:
http://localhost:9080/adminui (local deployment using the default port)
6. Log in using the default user name and password:
User name: administrator
Password: password
7. Click Services > LiveCycle ES Connector for IBM FileNet.
8. Provide all the required FileNet repository information and, under Repository Service Provider
Information, select IBM FileNet Repository Provider.
If your deployment uses the optional process engine service, under Process Engine Settings, select Use
Process Engine Connector Service and specify the process engine settings. For more information,
click the Help link on the upper-right corner of the page.
Note: The credentials you provide in this step are validated later when you start the IBM FileNet
repository services. If the credentials are not valid, an error is thrown and the services will not
start.
9. Click Save and then navigate to Services > Applications and Services > Service Management.
10. Select the check box next to each of the following services and then click Start:
●
IBMFileNetAuthProviderService
●
IBMFileNetContentRepositoryConnector
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
IBMFileNetRepositoryProvider
●
IBMFileNetProcessEngineConnector (if configured)
Configuring the connector using FileNet 3.5
92
If any of the services do not start correctly, verify the settings entered in step 8.
11. Do one of the following tasks:
●
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a
FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the
FileNet Authorization service overrides the default LiveCycle ES authorization and must be
configured to log in to Workbench ES by using FileNet credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super
administrator credentials (by default, Administrator and password). The credentials provided in step
8 use the default LiveCycle ES authorization service for accessing the default repository in this case.
12. Restart WebSphere Application Server.
13. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
14. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier
for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
15. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Select IBMFileNetAuthProviderService and then click OK.
16. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
17. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the settings, click the Help link in the upper-right corner of the page.
18. Click OK to exit the Add Directory page and then click OK again.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the connector using FileNet 4.0.1
93
19. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
20. Navigate to Settings > User Management > Users and Groups.
21. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the
upper-right corner of the page.
22. Start Workbench ES and log in using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The FileNet object store should now be visible in the Resources view within Workbench ES. If you do
not log in using [email protected]_name, Workbench ES attempts to log in to the default repository
specified in step 8.
23. (Optional) If you intend to install the LiveCycle ES samples for Connector for IBM FileNet, create a
FileNet object store named Samples and then install the samples in that object store.
After you configure your Connector for IBM FileNet service, it is recommended that you see Administering
LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet
repository.
Configuring the connector using FileNet 4.0.1
Complete the following procedure to configure the Connector for IBM FileNet service using FileNet 4.0.1.
➤ To configure the connector using FileNet 4.0.1 and CEWS transport:
1. Log in to WebSphere Administrative Console, click Servers > Application servers, and then click the
name of the server instance to configure (for example, server1).
2. Under Server Infrastructure, click Java and Process Management > Process Definition.
3. Under Additional Properties, click Java Virtual Machine.
4. Under Generic JVM arguments, add the location of the FileNet Configuration files as a Java option to
the application server start command.
-Dwasp.location=/<configuration files location>
For example, using a default FileNet Application Engine installation on a Windows operating system,
add this Java option:
-Dwasp.location=C:/Progra~1/FileNet/AE/CE_API/wsi
5. Click Apply and then click Save to Master Configuration.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the connector using FileNet 4.0.1
94
6. Locate the adobe-component-ext.properties file in the [appserver root]/profiles/[profile name] folder (if
the file does not exist, create it).
7. Add a new system property that provides the location of these FileNet Application Engine JAR files:
●
javaapi.jar
●
log4j-1.2.13.jar
●
soap.jar
●
wasp.jar
●
builtin_serialization.jar
●
wsdl_api.jar
●
jaxm.jar
●
jaxrpc.jar
●
saaj.jar
●
jetty.jar
●
runner.jar
●
p8cjares.jar
●
Jace.jar
●
(optional) pe.jar
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service.
The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system,
add the following system property on a new line with no line breaks and end the line with a carriage
return:
Note: The following text contains formatting characters for line breaks. If you copy this text to a location
outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext=
C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar,
C:/Program Files/FileNet/AE/CE_API/lib2/log4j-1.2.13.jar,
C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/soap.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/wasp.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/wsdl_api.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxm.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxrpc.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/saaj.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jetty.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/runner.jar,
C:/Program Files/FileNet/AE/CE_API/lib2/p8cjares.jar,
C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar,
C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar
Note: Add C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar only if your
deployment uses the IBMFileNetProcessEngineConnector service.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the connector using FileNet 4.0.1
95
8. (FileNet Process Engine Connector only) Using a text editor, create a file with the following content as a
single line and end the line with a carriage return:
RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/
wsi/FNCEWS40DIME/
9. Save the file as WCMApiConfig.properties in a separate folder, and add the location of the folder that
contains the WCMApiConfig.properties file to the adobe-component-ext.properties file.
For example, if you save the file as c:/pe_config/WCMApiConfig.properties, add the path c:/pe_config
to the adobe-component-ext.properties file.
10. Locate the file wsjaas.conf and add the following lines:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
FileNetP8WSI {com.filenet.api.util.WSILoginModule required;};
FileNetP8Engine
{com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy
required delegate=com.ibm.ws.security.common.auth.module.
WSLoginModuleImpl;};
FileNetP8Server
{com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy
required delegate=com.ibm.ws.security.common.auth.module.
WSLoginModuleImpl;};
FileNetP8KerberosService
{com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy
required delegate=com.filenet.engine.authentication.kerberos.login.
KrbServiceLoginModule;
com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required
delegate=com.ibm.ws.security.server.lm.ltpaLoginModule;
com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required
delegate=com.ibm.ws.security.server.lm.
wsMapDefaultInboundLoginModule;}
Note: By default, the wsjaas.conf file is located in the folder [appserver root]/profiles/[profile name]/
properties/.
11. If WebSphere Application Server is not currently running, start the server. Otherwise, stop and then
restart the server.
12. Repeat steps 1 to 11 on each WebSphere Application Server instance of the cluster.
13. Open a web browser and enter this URL:
http://localhost:9080/adminui (local deployment using the default port)
14. Log in using the default user name and password:
User name: administrator
Password: password
15. Click Services > LiveCycle ES Connector for IBM FileNet.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the connector using FileNet 4.0.1
96
16. Provide all of the required FileNet repository information and, under Repository Service Provider
Information, select IBM FileNet Repository Provider.
If your deployment uses the optional process engine service, under Process Engine Settings, select Use
Process Engine Connector Service and specify the process engine settings. For more information,
click the Help link in the upper-right corner of the page.
Note: The credentials that you provide in this step are validated later when you start the IBM FileNet
repository services. If the credentials are not valid, an error is thrown and the services will not
start.
17. Click Save and navigate to Services > Applications and Services > Service Management.
18. Select the check box next to each of these services and then click Start:
●
IBMFileNetAuthProviderService
●
IBMFileNetContentRepositoryConnector
●
IBMFileNetRepositoryProvider
●
IBMFileNetProcessEngineConnector (if configured)
If any of the services do not start correctly, verify the settings entered in step 16.
19. Do one of the following tasks:
●
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a
FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the
FileNet Authorization service overrides the default LiveCycle ES authorization and must be
configured to log in to Workbench ES by using FileNet credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super
administrator credentials (by default, Administrator and password). The credentials provided in step
16 use the default LiveCycle ES authorization service for accessing the default repository in this
case.
20. Restart WebSphere Application Server.
21. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
22. Click New Enterprise Domain and then type a domain ID and name. The domain ID is the unique
identifier for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for
the ID. (See “Adding enterprise domains” in User Management Help.)
23. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Slect IBMFileNetAuthProviderService and then click OK.
24. Add an LDAP authentication provider:
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the connector using FileNet 4.0.1
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
97
25. Add an LDAP directory:
●
Click Add Directory and, in the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the settings, click Help link in the upper-right corner of the page.
26. Click OK to exit the Add Directory page, and then click OK again.
27. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
28. Navigate to Settings > User Management > Users and Groups.
29. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the
upper-right corner of the page.
30. Start Workbench ES and log in using the following credentials:
User name: [username]@[repository_name]
Password: [password]
The FileNet object store should now be visible in the Resources view within Workbench ES. If you do
not log in using the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 16.
31. (Optional) If you intend to install the LiveCycle ES Samples for Connector for IBM FileNet, create a
FileNet object store named Samples and install the samples in that object store.
After you configure your Connector for IBM FileNet service, it is recommended that you see Administering
LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet
repository.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring the LiveCycle ES Connector for IBM Content Manager
Configuring the LiveCycle ES Connector for IBM Content Manager
If you installed the Connector for IBM Content Manager service as part of your LiveCycle ES solution,
complete the following procedure to configure the service to connect to the IBM Content Manager data
store.
➤ To configure Connector for IBM Content Manager:
1. Locate the adobe-component-ext.properties file in the [WAS HOME]/AppsServer/profiles/[profile name]
folder. If the file does not exist, create it. Add a new system property that provides the location of the
following IBM II4C JAR Files, Config folder that contains the IBM II4C property files and a ZIP file from
DB2 Universal Database Client installation:
●
Clio4CM.jar
●
cmb81.jar
●
cmbcm81.jar
●
cmbdb281.jar
●
cmbdb2c81.jar
●
cmbfed81.jar
●
cmbfedc81.jar
●
cmbicm81.jar
●
cmbicmc81.jar
●
cmbicmcup.jar
●
cmbjdbc81.jar
●
cmbjdbcc81.jar
●
cmblog4j81.jar
●
cmbsdk81.jar
●
cmbservlets81.jar
●
cmbtag81.jar
●
cmbupes81.jar
●
cmbutil81.jar
●
cmbutilfed81.jar
●
cmbutilicm81.jar
●
cmbutiljdbc81.jar
●
cmbview81.jar
●
cmbwas81.jar
●
cmbwcm81.jar
●
cmbwebservices.jar
●
cmbxmlmap.jar
●
cmbxmlservice.jar
●
common.jar
●
common.resources.jar
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
ecore.jar
●
ecore.resources.jar
●
ecore.xmi.jar
●
icmadm81.jar
●
icmrm81.jar
●
icmsdk81.jar
●
jcache.jar
●
log4j-1.2.8.jar
●
NLVLog.jar
●
xalan.jar
●
xerces.jar
●
xsd.jar
●
xsd.resources.jar
●
cmgmt (copy this folder and its contents)
●
db2java.zip
Configuring the LiveCycle ES Connector for IBM Content Manager
The new system property look like this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default DB2 Universal Database Client and II4C installation, in the file, add the
following system property on a new line, with no line breaks, and end the line with a carriage return:
com.adobe.livecycle.ConnectorforIBMCM.ext=
C:/Program Files/IBM/db2cmv8/lib/Clio4CM.jar,
C:/Program Files/IBM/db2cmv8/lib/cmb81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbcm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbdb281.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbdb2c81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbfed81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbfedc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbicm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbicmc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbicmcup.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbjdbc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbjdbcc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmblog4j81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbsdk81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbservlets81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbtag81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbupes81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutil81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutilfed81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutilicm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutiljdbc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbview81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbwas81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbwcm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbwebservices.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbxmlmap.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbxmlservice.jar,
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
Configuring the LiveCycle ES Connector for IBM Content Manager
Files/IBM/db2cmv8/lib/common.jar,
Files/IBM/db2cmv8/lib/common.resources.jar,
Files/IBM/db2cmv8/lib/ecore.jar,
Files/IBM/db2cmv8/lib/ecore.resources.jar,
Files/IBM/db2cmv8/lib/ecore.xmi.jar,
Files/IBM/db2cmv8/lib/icmadm81.jar,
Files/IBM/db2cmv8/lib/icmrm81.jar,
Files/IBM/db2cmv8/lib/icmsdk81.jar,
Files/IBM/db2cmv8/lib/jcache.jar,
Files/IBM/db2cmv8/lib/log4j-1.2.8.jar,
Files/IBM/db2cmv8/lib/NLVLog.jar,
Files/IBM/db2cmv8/lib/xalan.jar,
Files/IBM/db2cmv8/lib/xerces.jar,
Files/IBM/db2cmv8/lib/xsd.jar,
Files/IBM/db2cmv8/lib/xsd.resources.jar,
Files/IBM/db2cmv8/cmgmt,
Files/IBM/SQLLIB/java/db2java.zip
2. If WebSphere Application Server is not currently running, start the server; otherwise, stop and then
restart the server.
3. Repeat steps 1 and 2 on each WebSphere Application Server instance in the cluster.
You can now connect to the IBM Content Manager data store from the IBMCMConnectorService Property
Sheets by using the Use User Credentials as the login mode.
You have now completed the required steps for this procedure.
(Optional) If you want to connect to IBM Content Manager data store from IBMCMConnectorService
Property Sheets by using the Use Credentials From Process Context as the login mode, complete the
following procedure.
➤ To connect using Use Credentials from process context login mode:
1. Open a web browser and enter this URL:
http://localhost:9080/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Services > LiveCycle ES Connector for IBM Content Manager > Configuration Settings.
4. Type all of the required repository information and click Save. For more information about the
IBM Content Manager repository information, click the Help link in the upper-right corner of the page.
5. Do one of the these tasks:
●
To use the IBM Content Manager Authorization service (IBMCMProviderService) to use content from
an IBM Content Manager data store, in the Processes view of Workbench ES, continue with this
procedure. Using the IBM Content Manager Authorization service overrides the default LiveCycle ES
authorization and must be configured to log in to Workbench ES by using IBM Content Manager
credentials.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Configuring the LiveCycle ES Connector for IBM Content Manager
To use the System Credentials provided in step 8 to use content from an IBM Content Manager data
store, in the Processes view of Workbench ES, log in to Workbench ES by using the LiveCycle ES
super administrator credentials (by default, Administrator and password). You have now
completed the required steps for this procedure. The System Credentials that are provided in step 8
use the default LiveCycle ES authorization service for accessing the default repository in this case.
6. Log in to the LiveCycle Administration Console, and click Settings > User Management > Domain
Management.
7. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier
for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
8. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom, and then select IBMCMAuthProviderService
and click OK.
9. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
10. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the above settings, click the Help link in the upper-right corner of the page.
11. Click OK to exit the Add Directory page and click OK again.
12. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
13. To verify the status of the synchronization, click Refresh and view the status in the Current Sync State
column.
14. Navigate to Settings > User Management > Users and Groups.
15. Search for users that were synchronized from LDAP and do these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Uninstalling LiveCycle ES
102
Click OK a second time to confirm the role assignment.
Repeat this step for all users that you want to assign roles to. For more information, click the Help link in
the upper-right corner of the page.
16. Start Workbench ES and log in using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The IBM Content Manager data store can now be used in the Processes view within Workbench ES
when the login mode for IBMCMConnectorService orchestrable components is selected as Use
Credentials from process context.
After you configure your Connector for IBM Content Manager service, it is recommended that you see
Administering LiveCycle ES.
Uninstalling LiveCycle ES
The uninstall program located in the [LivecycleES root] directory does not remove the files that you
deployed to your application server.
Caution: By running the uninstall program, all the contents within the product installation directory are
subject to removal without further warning. Before you proceed, back up any data you do not
want to lose.
➤ To remove the files from your computer:
1. Invoke the uninstall program:
●
(Windows) Perform these tasks:
●
●
Use Add or Remove Programs in the Windows Control Panel:
●
Remove Adobe LiveCycle ES.
●
Remove Adobe Acrobat 9.0 Professional (if installed with PDF Generator ES).
Alternatively, you can complete these manual steps:
●
Set the JAVA_HOME and PATH so that they use the IBM JDK from WebSphere.
●
cd [LivecycleES root]/_uninst/server
●
Double-click the livecycle8_uninstall.exe file.
●
(Linux and UNIX) From a terminal, type ./livecycle8_uninstall.bin (you may need to make
this binary an executable file by typing a command, such as chmod 777).
●
(AIX) Perform these tasks:
●
Set JAVA_HOME and PATH so that they use the IBM JDK from WebSphere.
●
Change directory: cd /opt/adobe/livecycle8/_uninst/server.
●
From a terminal, type java -jar uninstall.jar.
2. Follow the on-screen instructions in the uninstall program, and then click Finish.
Adobe LiveCycle ES
Post-Deployment Activities
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Uninstalling a LiveCycle ES solution component
103
Uninstalling a LiveCycle ES solution component
If you want to remove a previously installed solution component, there are two main tasks associated with
the process:
●
Stop and undeploy the existing LiveCycle ES EAR files from your application server.
●
Run LiveCycle Configuration Manager to reconfigure and redeploy the LiveCycle ES EAR files and
solution components (omitting the eliminated component).
➤ To uninstall a solution component without removing LiveCycle ES:
1. Stop and undeploy the LiveCycle ES EAR files from your application server’s administration utility. See
“Uninstalling EAR files” on page 41.
2. Run LiveCycle Configuration Manager. See “Configuring and deploying LiveCycle ES” on page 36.
3. On the Solution Component Selection screen, select only those components to redeploy or if the
previously installed components are selected, deselect the component to remove.
4. On the Task Selection screen, select the following tasks and the click Next:
●
Configure LiveCycle ES
●
Deploy LiveCycle ES EARs
●
Deploy LiveCycle ES components
5. Perform the tasks on the remaining screens, review the Next Steps, and then click Exit.
If you are uninstalling Output ES, you will need to perform the following tasks to complete its removal
from your LiveCycle ES environment:
●
Log in to Workbench ES and uninstall the Output service via the Components view.
●
Remove any related samples.
8
Configuring Load Balancing
You can configure your WebSphere cluster to provide load-balancing functionality. Use the IBM HTTP
server that ships with the WebSphere Application Server to perform the following tasks:
●
Preparatory tasks. (See “Preparing for installation” on page 104.)
●
Install IBM HTTP Server. (See “Installing the web server” on page 104.)
●
Install the web server plug-in. (See “Installing the web server plug-in” on page 105.)
●
(Optional) Change the default configuration for message-driven beans (MDBs) to tune load
balancing. (See “Configuring message-driven beans” on page 106.)
Note: LiveCycle ES in a cluster environment supports only sticky sessions for load balancing. IBM HTTP
server supports sticky sessions by default.
Preparing for installation
Before you install the web server, perform the following configuration tasks:
Server domain: If you are using a domain architecture, ensure that the server is not a member of any
domain other than the same domain as the LDAP server.
Create local user: In Microsoft Windows, if you plan to run IBM HTTP Server as a service, you can create
a local account and make this account a part of the local administrators group.
Installing the web server
The following steps describe how to install IBM HTTP Server on a separate node from the WebSphere ND
or WebSphere basic application servers. For information about installing and configuring other IBM
supported web servers, such as Apache, Microsoft IIS, and Sun Java System Web Server, see the IBM web
page Editing Web Server Configuration Files.
You must first insert the installation media or copy the files to a local directory.
Note: This procedure can be used to upgrade the current version of IBM HTTP Server by replacing the
existing installation.
➤ To install the web server:
1. To start the installation, go to the directory that contains the web server installer and type the
appropriate command:
●
(Linux/UNIX) ./launchpad.sh
●
(Windows) launchpad.bat
2. From the Launchpad, select Launch the installation for IBM HTTP Server.
3. On the Welcome screen, click Next.
4. Select I accept the terms in the license agreement and click Next.
104
Adobe LiveCycle ES
Configuring Load Balancing
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing the web server plug-in
105
5. Specify the location of the installation directory and click Next.
6. Select Custom and click Next.
7. Under Product Information, select HTTPServer Base and Security and then click Next.
8. Specify the HTTP port and HTTP Administration port and click Next.
9. (Windows) Select Run IBM HTTP Server as a Windows Service, Run IBM HTTP Administration as a
Windows Service, and Log on as local system account.
Note: A user name and password is not required for this selection. To run this service using a specific
user account and password combination, select Log on as a specified user account and specify
your user ID and password information.
10. Under Startup Type, select Automatic and then click Next.
11. Review the confirmation panel to verify your selections, click Back to change any of your specifications,
and click Next to begin installing IBM HTTP Server.
After displaying the installation status, the wizard displays the Completion status panel that indicates a
successful installation.
12. Deselect Launch the WebSphere Application Server - Plugin install and click Finish.
Installing the web server plug-in
After the application server is installed and the applications are deployed, install the web server plug-in on
the HTTP server. This procedure assumes that the HTTP server is on a node that is not in the cluster.
➤ To install the web server plug-in:
1. On the web server computer (the remote system that has HTTP server installed), copy the WebSphere 6
installer and, from a console, go to the WebSphere 6 installer directory and run Launchpad by typing
the appropriate command:
●
(Linux/UNIX) ./launchpad.sh
●
(WIndows) launchpad.bat
2. From Launchpad, select Launch the installation wizard for Web server plug-ins.
3. Deselect Installation roadmap and Plug-ins section of the Getting Started guide, and then click
Next.
4. Select I accept the terms in the license agreement and click Next. The installer will now check your
system.
5. If your system passes the prerequisites check, click Next.
Note: If your system does not pass the prerequisites check, stop the installation, correct any problems,
and restart the installation.
6. Select IBM HTTP Server V6 and click Next.
7. Select Web server machine (remote) and click Next.
Adobe LiveCycle ES
Configuring Load Balancing
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring message-driven beans
106
8. Specify the [plugins_root] directory and the location where the web server plug-ins should be installed,
and click Next.
9. In Select the existing IBM HTTP Server httpd.conf file, click Browse and select the httpd.conf file
from the [webserver root]/conf directory, where [webserver root] specifies the directory where IBM HTTP
Server is installed.
10. In the Specify the Web server port box, keep the default port value of 80 and click Next.
11. In the Specify a unique Web server definition name box, enter a unique identifier for this definition
and then click Next.
12. In the Web server plugin-cfg.xml file box, accept the default settings and then click Next.
13. In the Host name or IP address for the Application Server box, type the host name or IP address of
the ND node and then click Next.
14. In the confirmation pane, click Next and, in the summary information pane, click Next.
15. After the files are copied, click Next and then click Finish.
16. Copy the appropriate file to the WebSphere ND [appserver root]\bin folder:
●
(Windows) configure[webserver definition name].bat
●
(Linux/UNIX) configure[webserver definition name].sh
17. Ensure that Deployment Manager is running and then run the configurewebserver command
(configure<webserver definition name>.bat for Windows or configure<webserver definition name>.sh for
Linux or UNIX) on the WebSphere ND computer to create an unmanaged node on the WebSphere ND
computer and add the web server to it.
18. Open a web browser and access the administrative console for the web server computer
(http://[web server name]:80/adminui) to verify whether the plug-in generated and propagated
successfully. The following response indicates that you must generate and propagate the plug-in as
described in steps 19 to 22:
/[application name] not defined
Note: The plug-in generates and propagates automatically only if your system previously enabled
automatic synchronization, which is disabled by default.
19. Log in to the WebSphere Administrative Console and, in the navigation tree, click Servers > Web
servers and then, in the right pane, select the Select check box beside the HTTP server name.
20. Click Generate Plug-in. A message confirms successful generation of the Plugin-cfg.xml file.
21. Click Propagate Plug-in. A message confirms successful propagation of the Plugin-cfg.xml file.
22. Restart the web server.
Configuring message-driven beans
LiveCycle ES uses message-driven beans (MDBs) and a distributed JMS queue.
Each node maintains a pool of MDB instances that are available to process job requests in the queue and
attempts to keep the MDB pool fully used. That is, a node pulls JMS requests for all of its idle MDB
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring Load Balancing
Configuring message-driven beans
107
instances. Light load conditions can result in uneven load balancing across nodes of the cluster because a
single node processes multiple requests to fully use all MDB instances that are available in its pool. Heavy
load conditions balance the load more evenly across the cluster because more nodes of the cluster have
fully used their MDB pool.
Reducing the MDB pool size to a small number results in a more even load distribution under light load
conditions at the expense of reduced throughput under heavy loads. For more information about MDB
parameters and instructions to change them, see the WebSphere Server Application documentation.
9
Advanced Production Configuration
This section describes advanced tuning for LiveCycle Output ES, LiveCycle Forms ES, and
LiveCycle PDF Generator ES. This section should be completed only on a production system by an
advanced application server administrator.
Configuring pool size for LiveCycle Output ES and
LiveCycle Forms ES
The current default value for PoolMax is 4. The actual value to set depends on the hardware configuration
and the expected usage in your environment.
For optimal use, we recommend that the lower limit of PoolMax not be less than the number of CPUs that
are available. The upper limit must be determined by the load pattern on your server. Generally, the upper
limit should be set to twice the number of CPUs on your server.
➤ To modify the existing PoolMax value:
1. Log in to the WebSphere Administrative Console.
2. In the navigation tree, click Servers > Application Servers > [server name] > Java and Process
Management > Process Definition > Java Virtual Machine > Custom Properties.
3. Add the following properties for ConvertPdf:
●
com.adobe.convertpdf.bmc.POOL_MAX=[new value]
●
com.adobe.convertpdf.bmc.MAXIMUM_REUSE_COUNT=5000
●
com.adobe.convertpdf.bmc.REPORT_TIMING_INFORMATION=true
●
com.adobe.convertpdf.bmc.CT_ALLOW_SYSTEM_FONTS=true
4. Add the following properties for XMLFM:
●
com.adobe.xmlform.bmc.POOL_MAX=[new value]
●
com.adobe.xmlform.bmc.MAXIMUM_REUSE_COUNT=5000
●
com.adobe.xmlform.bmc.REPORT_TIMING_INFORMATION=true
●
com.adobe.xmlform.bmc.CT_ALLOW_SYSTEM_FONTS=true
5. Repeat steps 2 to 4 for each server in the cluster.
LiveCycle PDF Generator ES
LiveCycle PDF Generator ES is capable of doing multiple PDF conversions simultaneously for some types of
input files. This is enforced through the use of stateless session beans.
108
Adobe LiveCycle ES
Advanced Production Configuration
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring EJB Pool Size
109
Configuring EJB Pool Size
Four different stateless session beans exist for enforcing independent pool sizes for the following types of
input files:
●
Adobe PostScript® and Encapsulated PostScript (EPS) files
●
Image files, such as BMP, TIFF, PNG, and JPEG files
●
OpenOffice files
●
All other file types (except HTML files), such as Microsoft Office, Photoshop®, PageMaker®, and
FrameMaker® files
The pool size for HTML-to-PDF conversions is not managed through the use of stateless session beans.
The default pool size for PostScript and EPS files and for image files is set to 3, and the default pool size for
OpenOffice and other file types (except HTML) is set to 1.
You can configure the PS/EPS and image pool size to a different value based on your server hardware
configuration, such as the number of CPUs, the number of cores within each CPU, and so on. However, it is
mandatory that the pool size for the OpenOffice and other file types be left unchanged at 1 for proper
functioning of PDF Generator ES.
This section describes how the pool size for PS2PDF and Image2PDF can be configured for each of the
supported application servers.
The text that follows assumes that the following two LiveCycle ES application EARs are deployed on the
application server:
●
adobe-livecycle-websphere.ear
●
adobe-livecycle-native-websphere-[platform].ear
where [platform] should be replaced with one of the following strings, depending on your operating
system:
●
(Windows) x86_win32
●
(Linux) x86_linux
●
(SunOS™) sparc_sunos
●
(AIX) powerpc_aix
➤ To configure the pool size for PS2PDF and Image2PDF:
1. Ensure that WebSphere Application Server is running.
2. In the URL line of a web browser, type http://[hostname]:9060/ibm/console to access the
WebSphere Administrative Console. The URL may be different if you chose WebSphere to run on a
non-standard port or if HTTPS is enforced. Depending on whether security is enabled, you may be
prompted for your user name and password.
3. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers then
click on a server name.
4. Under Server Infrastructure, click > Java and Process Management > Process Definition.
5. Under Additional Properties, click Java Virtual Machine.
Adobe LiveCycle ES
Advanced Production Configuration
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configuring EJB Pool Size
110
6. Under Additional Properties, click Custom Properties.
7. Search for a property named com.ibm.websphere.ejbcontainer.poolSize and, if it exists, click
the name. Otherwise, click New and type the property name
com.ibm.websphere.ejbcontainer.poolSize. If the property existed previously, its value
should be as follows:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#NativeToPDFInvoker=1,1:LiveCycle
8#adobe-pdfg-bmc-invoker-ejb.jar#OpenOfficeToPDFInvoker=1,1:LiveCycle8#ado
be-pdfg-bmc-invoker-ejb.jar#ImageToPDFInvoker=3,3:LiveCycle8#adobe-pdfg-bm
c-invoker-ejb.jar#PSToPDFInvoker=3,3.
In the above code, imageToPDFInvoker=3,3 and PSToPDFInvoker=3,3 specify that the values of
minimum/maximum EJB pool size for Image2PDF and PS2PDF conversions are set to 3 each.
8. Modify these values appropriately. For example, to configure a pool size of 5 for Image2PDF and a pool
size of 8 for PS2PDF, the modified property value should read as follows:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#NativeToPDFInvoker=1,1:LiveCyc
le8#adobe-pdfg-bmc-invoker-ejb.jar#OpenOfficeToPDFInvoker=1,1:LiveCycle8
#adobe-pdfg-bmc-invoker-ejb.jar#ImageToPDFInvoker=5,5:LiveCycle8#adobe-p
dfg-bmc-invoker-ejb.jar#PSToPDFInvoker=8,8.
Note: LiveCycle8 in the string above represents the name of the LiveCycle ES application deployed on
your application server (for example, adobe-livecycle-websphere).
9. Save your changes and restart WebSphere Application Server.
Note: If you are running an application server cluster, make identical changes on each of the
Application Server cluster nodes. To save time, make the changes before you create a cluster to
ensure that these values are automatically set on each cluster node that you create after these
changes are made on the primary node.
10. Repeat steps 3 to 9 for each server in the cluster.
10
Troubleshooting
This section discusses issues you may encounter when installing and deploying LiveCycle ES in a cluster
configuration, and suggests steps for avoiding or working around them. For additional troubleshooting
issues that are related to LiveCycle ES in general, see Installing and Deploying LiveCycle ES for WebSphere .
Getting help
This section describes the steps that you should take before you contact Adobe Support. If, after reviewing
the LiveCycle ES documentation, you have not resolved your issues, contact Adobe Support. To help
expedite your service, have the following information available:
●
What were you doing when the problem occurred?
●
Can you repeat the problem?
●
Was an error message displayed when the problem occurred? Did you observe anything else?
●
If you deselect the Show Friendly HTTP Error Messages option in Internet Explorer (Tools > Options >
Advanced), do the errors persist?
PDF Generator ES on Windows fails when converting native files
LiveCycle PDF Generator ES running on a Windows operating system may fail when converting native files,
such as from Microsoft Word to PDF, giving an exception in the log file similar to this:
INFO [PDF Generator] Application server started as user: SYSTEM
This problem occurs if you did not use the same user account for all of Microsoft Office, PDF Generator ES,
Acrobat for PDF Generator ES, and your application server process.
To correct this problem, change the user for the WebSphere for Adobe LiveCycle service to be the same as
the user for Microsoft Office.
➤ To set the user for the WebSphere for Adobe LiveCycle service:
1. Select Start > Control Panel > Administrative Tools > Computer Management > Services and
Applications > Services.
2. Double click the WebSphere for Adobe LiveCycle service and then click the Log On tab.
3. Select This account, type the user name and password that runs Microsoft Office, and click OK.
JMS fails to validate
You may encounter a JMS exception when validating your WebSphere Application Server cluster with
LiveCycle Configuration Manager.
This problem occurs if inappropriate JDBC drivers exist in the directory [appserver root]/lib. To correct this
problem, remove JDBC drivers from the [appserver root]/lib directory.
111
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Troubleshooting
No scheduler found with name IDPSchedulerService
112
You can complete the following steps to resolve LiveCycle Configuration Manager validation errors that
may occur when using Microsoft SQL Server as the JMS database.
➤ To verify the JMS setup with SQL Server:
1. In the WebSphere Administrative Console navigation tree, click Service Integration > Buses, and then
click IDP_JMS_BUS.
2. Under Topology, click Messaging Engines. If everything is functioning properly, a green arrow
appears. The status for the bus is likely unknown at this point.
3. Select your messaging engine and, under Additional Properties, click Message Store. The schema
name must match the user name; if it does not match, set it to match. To set up the Microsoft SQL
Server database and users, see Preparing to Install LiveCycle ES (Server Cluster).
4. Click Save directly to the master configuration.
5. Delete any tables that begin with SIB to ensure that conflicts exist with old bus configurations.
6. Restart WebSphere and retry step 1 to ensure that the bus is running.
7. Run LiveCycle Configuration Manager validation to confirm JMS is set up successfully.
No scheduler found with name IDPSchedulerService
After restarting your WebSphere Application Server cluster, you may see exceptions in the log files that are
similar to these:
[5/28/08 17:20:15:032 EDT] 00000023 EventManagerI E
Event Data storage
failed. Reason: com.adobe.idp.event.policy.EventPolicyException: No
scheduler found with name IDPSchedulerService
com.adobe.idp.event.exception.EventContentException:
com.adobe.idp.event.policy.EventPolicyException: No scheduler found with
name IDPSchedulerService
This problem occurs if some MBeans fire before the scheduler service initializes. This exception does not
cause other problems, and may be ignored.
Exception: No trusted certificate found
Your WebSphere Application Server may give exceptions similar to those described below.
Exceptions seen from LiveCycle Administration Console:
Could not connect to Inbox. Error message: com.ibm.jsse2.util.h:
No trusted certificate found; nested exception is:
javax.net.ssl.SSLHandshakeException:
com.ibm.jsse2.util.h: No trusted certificate found
Exceptions seen in WebSphere Application Server log files:
[5/28/08 13:15:30:283 CDT] 00000025 SystemOut
O
CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN
"CN=imap.gmail.com, O=Google Inc, L=Mountain View, ST=California, C=US"
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Troubleshooting
Pop-up window (English/European) appears with LCM
113
was sent from target host:port "null:null". The signer may need to be
added to local trust store "D:/servers/websphere6.1/profiles/AppSrv01
/config/cells/MN-TOBIKONode01Cell/nodes/MN-TOBIKONode01/trust.p12"
located in SSL configuration alias "NodeDefaultSSLSettings" loaded from
SSL configuration file "security.xml". The extended error message from
the SSL handshake exception is: "No trusted certificate found".
[5/28/08 13:15:30:283 CDT] 00000025 SystemOut
O
[5/28/08 13:15:30:283 CDT] 00000025 ExceptionUtil E
CNTR0020E: EJB threw an unexpected (non-declared) exception during
invocation of method "doSupports" on bean "BeanId(adobe-core-websphere
#adobe-dscf.jar#EjbTransactionCMTAdapter, null)". Exception data:
java.lang.RuntimeException: Could not connect to Inbox. Error message:
com.ibm.jsse2.util.h: No trusted certificate found;
nested exception is:
javax.net.ssl.SSLHandshakeException:
com.ibm.jsse2.util.h: No trusted certificate found
This problem occurs when the WebSphere key store does not contain a required certificate. Notice that the
default WebSphere key store contains only a limited set of certificates. Use the following procedure to add
a new certificate to the key store.
➤ To add a new certificate to the WebSphere key store:
1. Obtain the appropriate certificate from the Email service.
2. Copy the certificate to the [appserver root]\profiles\[server name]\etc directory on each server in the
cluster.
3. Log in to the WebSphere Administrative Console and, in the navigation tree, click Security > SSL
certificate and key management.
4. Under Related Items, click Key stores and certificates, and then click CellDefaultTrustStore.
5. Under Additional Properties, click Signer certificates, and then cllick Add.
6. In the Alias box, type an appropriate alias for the certificate you are importing.
7. In the File name box, type the location where you installed the certificate at step 2, and click OK.
8. Click Save. The certificate you just added should now be listed as a Signer certificate.
9. Restart each WebSphere Application Server in the cluster.
Pop-up window (English/European) appears with LCM
When you select a language for LiveCycle Configuration Manager, an additional small pop-up window
may appear as shown below.
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Troubleshooting
Connector for EMC Documentum error
114
Ignore this window. Proceed to select your language on the main window.
Connector for EMC Documentum error
While using LiveCycle ES Connector for EMC Documentum with the Documentum DFC 5.3 client installed
on LiveCycle ES server, you may see the following error in the server logs:
DM_CCONTENT_E_REMOVE_DIRECTORY
If this occurs, add the following entry to the [DMAPI_CONFIGURATION] section of the dmcl.ini file:
'local_clean_on_init=F'
On a Windows server, by default the dmcl.ini file is located in the [Windows Installation Drive]\WINDOWS
folder.
Restart the LiveCycle ES server for this change to take affect.
A
Appendix - Install Command Line Interface
LiveCycle ES provides a command line interface (CLI) for the installation program. The CLI is intended to be
used by advanced users of LiveCycle ES or in server environments which do not support the use of the
Graphical User Interface (GUI) of the installation program. The CLI runs in console mode with one
interactive session for all install operations.
Before you install the solution components, you must ensure that your environment includes the software
and hardware required to run LiveCycle ES. You should also understand the installation options and have
prepared the environment as required. (See Preparing to Install LiveCycle ES (Server Cluster).) Then you
should review the first page of “Installing the product files” on page 27 and the “Installing the Solution
Component Files” on page 27 section.
Note: MySQL is not supported for server clusters. Do not choose a MySQL option when you respond to
prompts displayed by the LiveCycle ES CLI installation program.
This appendix covers the following topics:
●
“Installing LiveCycle ES” on page 115
●
“Error logs” on page 120
●
“Next steps” on page 120
Installing LiveCycle ES
This section covers the initial installation of LiveCycle ES. For information about configuration and
deployment, see “Configuring LiveCycle ES for Deployment” on page 34 or “Appendix - LCM Command
Line Interface” on page 121.
Note: To avoid permission issues during the deployment, ensure that you are logged in as the user who
will run the WebSphere process when you run the LiveCycle ES install CLI and LiveCycle
Configuration Manager.
➤ To install LiveCycle ES:
1. Open a command prompt and navigate to the /livecycle_server/8.2 directory of the installation media.
2. Run the following command on a single line:
●
(Windows) java -cp stage.jar;..\..\third_party\jdbc\
mysql-connector-java-3.1.12-bin.jar run -console
●
(Linux) ./linux_livecycle8_setup.bin -cp:p stage.jar -console
●
(UNIX) ./solaris_livecycle8_setup.bin -cp:p stage.jar -console
●
(AIX) ./aix_livecycle8_setup.bin -cp:p stage.jar -console
Note: Specify the following additional arguments to redirect the LiveCycle ES installer temporary
directory to an alternate, non-default location:
115
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing LiveCycle ES
116
-cp:p stage.jar -is:tempdir [alternate temporary directory]
(Solaris Only) To use a higher heap size (such as 512M) in the installer argument, you must specify
the heap size settings in a separate file and then run the install script.
To do this, create a filed named solaris_livecycle8_setup.ja in the directory where
solaris_livecycle8_setup.bin exists, and add the following lines in it:
-XMS256M
-XMX512M
After this, run the install script to direct the installer to use the JDK you installed:
# ./solaris_livecycle8_setup.bin -cp:p stage.jar -is:tempdir /[temporary
directory] -is:javahome [java_home]
3. Respond to the prompts as described in the following table:
Prompt
Description
Select a language to be used for this wizard.
Select the language for the installation to
use by entering a value between 1 and 4.
The selection will then be displayed in
brackets ([X]).
[X] 1 - English
[ ] 2 - French
[ ] 3 - German
[ ] 4 - Japanese
Enter [0] when you finish selecting a
language.
To select an item, enter its number, or [0] when you are
finished: [ ]
Adobe LiveCycle ES
Welcome to Adobe LiveCycle ES
The installation wizard will install Adobe LiveCycle ES
(Enterprise Suite) server version 8.2. To continue, choose
Next.
Adobe LiveCycle ES
Adobe Systems Incorporated
http://www.adobe.com/products/livecycle/
Press 1 for Next, 3 to Cancel, or 5 to Redisplay [1]
On the Welcome screen, enter 1 to
continue the installation.
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing LiveCycle ES
Prompt
Description
Adobe LiveCycle ES
On the Destination screen, press Enter to
accept the default directory or type the
new installation directory location.
Adobe LiveCycle ES Install Location
Please specify a directory or press Enter to accept the
default directory.
Destination Directory For Windows is
[C:\Adobe\LiveCycle8.2]
117
Note: If you type the name of a directory
that does not exist, it will be created
for you.
Destination Directory for Unix/Linux is
[/opt/adobe/livecycle8.2]
Caution: When you install the solution
components, you can specify a
different installation location. If
you are installing on Linux or
UNIX, the directory you specify
should not contain any spaces; if
it does, the installation program
does not install the solution
component.
Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Adobe LiveCycle ES
Enter a serial number. The components that
you are licensed for will be displayed.
Serial Number [ ]
[ ] 1 - Add
[ ] 2 - Clear
[X] 3 - Finish
To select an item enter its number, or 0 when you are
finished: [0]
If you have licensed multiple solution
components, enter 1 to add another serial
number. You will then be prompted for
another serial number as in the previous
step. Repeat this step for each serial
number that you have.
Enter 0 when you finish entering serial
numbers.
Note: To reset the serial number, enter 2.
Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Press ENTER to read the text [Type q to quit]
The Product License Agreement will
display. Press enter to read the agreement.
Please choose from the following options:
If you agree with the terms of the Product
License Agreement, enter 1.
[ ] 1 - I accept the terms of the license agreement.
[X] 2 - I do not accept the terms of the license agreement.
Enter [0] when you are done with the
Product License Agreement.
To select an item enter its number, or 0 when you are
finished: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing LiveCycle ES
118
Prompt
Description
Adobe LiveCycle ES
Select the operating system for which you
are configuring.
OS Selection
Selecting an operating system from the list below
indicates to the installer which native environment you
want to configure.
Which configuration is this installation intended for?
Please choose from the following options:
[X] 1 - Windows
[ ] 2 - Linux
[ ] 3 - Solaris
[ ] 4 - AIX
To select an item enter its number, or 0 when you are
finished: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Adobe LiveCycle ES
(PDF Generator ES for Windows Only)
LiveCycle PDF Generator ES Native Application Support
If you enter 1 to enable native application
support for PDF Generator ES, the software
will check the version of Adobe Acrobat®
you have installed. If you do not have
Acrobat installed, accept the prompt to
install Acrobat 9.0 now.
LiveCycle PDF Generator ES can convert Microsoft Office
Word, Adobe Photoshop, AutoCAD, and other native
application files to Adobe PDF.
Please choose from the following options:
For detailed information about native application
support, please see the documentation.
[ ] 1 - Yes, enable native application support for LiveCycle
PDF Generator ES
[X] 2 - No, do not enable native application support for
LiveCycle PDF Generator ES (select this option for
clustered deployments)
If you are installing in a clustered
environment, enter 2 and do not enable
native application support for
PDF Generator ES.
Enter [0] when you are done making your
selection.
To select an item enter its number, or 0 when you are
finished: [ ]
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Press Enter to continue the installation.
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Installing LiveCycle ES
119
Prompt
Description
Adobe LiveCycle ES
Press 1 to install LiveCycle ES.
Pre-installation Summary
Pre-installation summary -> Please read the
summary information. LiveCycle ES will be
installed in the following location with the
following features.The installation progress
will display.
Please read the summary information below.
Adobe LiveCycle ES will be installed in the following
location:
/opt/adobe/livecycle8.2
With the following features:
●
Adobe LiveCycle Foundation
●
Adobe LiveCycle Configuration Manager
●
LiveCycle ES SDK
●
Adobe LiveCycle Forms ES
●
Adobe LiveCycle Reader Extensions ES
●
Adobe LiveCycle Process Management ES
●
Adobe LiveCycle ES Business Activity Monitoring
●
Adobe LiveCycle Output ES
●
Adobe LiveCycle Rights Management ES
●
Adobe LiveCycle Digital Signatures ES
●
Adobe LiveCycle PDF Generator ES
●
Adobe LiveCycle PDF Generator 3D ES
●
Adobe LiveCycle Barcoded Forms ES
●
Adobe LiveCycle ES Connector for IBM FileNet
●
Adobe LiveCycle ES Connector for EMC Documentum
●
Adobe LiveCycle ES
Connector for IBM Content Manager
Note: The installation location and solution
components specified will vary
depending on your license key and
your specified installation directory.
Press ENTER to read the text. Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
Press ENTER to read the test (Type q to quit).
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
After installation is done, the Release Notes
Summary is displayed.
Please choose from the following options:
Post Installation Details are displayed.
[X] 1 - Start LiveCycle Configuration Manager.
Enter 1 to start LiveCycle Configuration
Manager or 2 and then [0] to end the
installation.
[ ] 2 - Not Start LiveCycle Configuration Manager.
To select an item enter its number, or 0 when you are
finished: [0]
Press 3 to Finish or 5 to Redisplay [3]
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Error logs
120
Error logs
If an error occurs, you can review the adobe_lc8.2_server_install.log in the system temporary directory
(TEMP or TMP).
For information about errors that may occur during the installation, see “Troubleshooting” on page 111.
Uninstalling LiveCycle ES in console mode
If you need to uninstall your LiveCycle ES environment, open a command prompt, change to the
[LiveCycle8.2 root]/_uninst/server directory and run the following command as appropriate for your
operating system:
●
(Windows) ./windows.*.bin - console
●
(Linux) ./linux.*.bin - console
●
(UNIX) ./solaris.*.bin - console
●
(AIX) ./aix.*.bin - console
Next steps
You must now configure LiveCycle ES for deployment. (See “Configuring LiveCycle ES for Deployment” on
page 34 or “Appendix - LCM Command Line Interface” on page 121.)
B
Appendix - LCM Command Line Interface
LiveCycle ES provides a Command Line Interface (CLI) for LiveCycle Configuration Manager. The CLI is
intended to be used by LiveCycle ES advanced users, for example, in server environments that do not
support the use of the graphical user interface (GUI) of LiveCycle Configuration Manager.
Order of operations
The LiveCycle Configuration Manager CLI must follow the same order of operations as the GUI version of
LiveCycle Configuration Manager. Ensure that you use the CLI operations in this order:
1. Configure LiveCycle ES.
2. Configure the Application Server.
3. Deploy LiveCycle ES.
4. Initialize LiveCycle ES.
5. Initialize LiveCycle ES Business Activity Monitoring.
6. Deploy LiveCycle ES Components.
Caution: You must restart each WebSphere Application Server of your cluster after you complete your
LiveCycle Configuration Manager CLI operations.
Command line interface property file
The LiveCycle Configuration Manager CLI requires containing the defined properties for your LiveCycle ES
environment. The template for the properties file, cli_propertyFile_template.txt, located in the
[LiveCycleES root]/configurationManager/bin folder. You must create and edit the values. You can
customize based on the LiveCycle Configuration Manager operations you intend to use. The following
section describes the properties and values required.
Note: If you use the GUI version of LiveCycle Configuration Manager, and then chose to use the CLI
version, you can use the property file created by the GUI version as the CLI version property file.
When you run the [LiveCycleES root]/configurationManager/bin/ConfigurationManager.bat file, the
userValues.properties file is created in the [LiveCycleES root]/configurationManager/config
directory. You can copy this file, rename it userValuesForCLI.properties, and use it as input for the
LiveCycle Configuration Manager CLI.
121
Adobe LiveCycle ES
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Appendix - LCM Command Line Interface
Common properties
122
Common properties
The common properties are as follows:
WebSphere specific properties: Required for the Configure the Application Server, Deploy LiveCycle,
Validate Application Server Topology and Validate Application Server Configurations operations.
LiveCycle Server specific properties: Required for the Initialize LiveCycle and Deploy LiveCycle
Components operations.
The properties in the table are required for following operations:
●
Initialize LiveCycle
●
Deploy LiveCycle Components
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Common properties
123
WebSphere specific properties
Property
Values
Description
targetServer.topologyType
server or cluster
The type of application server
topology for which you are
deploying LiveCycle ES
targetServer.name
String
The name assigned to the
application server node or cluster
targetServer.adminHost
Default:
The host name of the server
where the WebSphere
application server is installed
localhost
targetServer.adminPort
Integer
The port number the WebSphere
administration server uses to
listen for SOAP requests
targetServer.adminUserID
String
The administrative user ID to use
when accessing the WebSphere
Application Server
localServer.appServerRootDir
Default:
The root directory of the
application server instance that
you are configuring locally (that
you plan to deploy LiveCycle ES
to or that you will use to
communicate with a remote
server that you plan to deploy
LiveCycle ES to)
(Windows) C:\Program Files\
WebSphere\AppServer
(Linux, Solaris)
/opt/IBM/WebSphere/AppServer
(AIX)
/usr/IBM/WebSphere/AppServer
LiveCycle Server specific properties
Property
Values
Description
LCHost
String
The host name of the server
where LiveCycle ES will be
deployed
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configure LiveCycle ES properties
124
Property
Values
Description
LCPort
Integer
The web port number where
LiveCycle ES will be deployed
excludedSolutionComponents
Choose a value:
(Optional) List the LiveCycle ES
solution components you do not
want to configure. Specify the
excluded components in a
comma-separated list.
String. Values include:
ALC-LFS-Forms,
ALC-LFS-BusinessActivityMonito
ring,
ALC-LFS-ConnectorEMCDocume
ntum,
ALC-LFS-ConnectorIBMFileNet,
ALC-LFS-ConnectorIBMContent
Manager,
ALC-LFS-ContentServices,
ALC-LFS-DigitalSignatures,
ALC-LFS-DataCapture,
ALC-LFS-Output,
ALC-LFS-PDFGenerator,
ALC-LFS-PDFGenerator3D,
ALC-LFS-ProcessManagement,
ALC-LFS-ReaderExtensions,
ALC-LFS-RightsManagement
Configure LiveCycle ES properties
These properties only apply to the configureLiveCycle operation.
Property
Values
Description
AdobeFontsDir
String
Location of the Adobe server
fonts directory. This path must
be accessible from the server
being deployed to.
customerFontsDir
String
Location of the customer fonts
directory. This path must be
accessible from the server being
deployed to.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configure LiveCycle ES properties
125
Property
Values
Description
systemFontsDir
String
Location of the system fonts
directory. Multiple system fonts’
locations can be entered using a
semicolon as separator.
These paths must be accessible
from the server being deployed
to.
LCTempDir
String
Location of the temporary
directory. This path must be
accessible from the server being
deployed to.
LCGlobalDocStorageDir
String
The global document storage
(GDS) root directory.
Specify a path to an NFS shared
directory used to store
long-lived documents and to
share them among all cluster
nodes.
Specify this property only when
deploying LiveCycle ES products
in a clustered environment. This
path must be accessible from
the server being deployed to.
enableFIPS
true or false
Default:
false
Enabling the Federal
Information Processing
Standards (FIPS) option restricts
data protection to FIPS 140-2
approved algorithms using the
RSA BSAFE Crypto-J 3.5.2
encryption module with FIPS
140-2 validation certificate #590.
Set this value to true only if you
require FIPS to be enforced.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configure or validate application server properties
126
Property
Values
Description
contentServices.rootDir
String
Required if you are configuring
LiveCycle Content Services ES
only.
Specify the root directory used
by Content Services ES. The
content storage root directory
should be a location shared by
all WebSphere Application
Server instances in the cluster.
contentServices.indexesDir
String
Required if you are configuring
LiveCycle Content Services ES
only.
Specify the indexes directory
used by Content Services ES.
Configure or validate application server properties
LiveCycle Configuration Manager can configure or validate your WebSphere application server as required
by LiveCycle ES.
These properties apply to the following operations:
●
Configure Application Server
●
Validate Application Server Topology
●
Validate Application Server Configurations
●
Validate Database Connectivity
Note: You must configure the WebSphere specific properties section. For more information, see
“Common properties” on page 122.
Property
Values
Description
jvm.initialHeapSize
Default:
The initial heap size, in MB, for the
JVM
512
jvm.maxHeapSize
Default:
1024
cache.useUDP
true or false
The maximum heap size, in MB,
for the JVM
Set the value to true if
LiveCycle ES uses UDP to
implement caching.
Set to false if LiveCycle ES uses
TCP to implement caching.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Configure or validate application server properties
127
Property
Values
Description
cache.udp.port
Default:
The port number that the
primary WebSphere Application
Server computer uses for
UDP-based caching
communication.
33456
Configure only if
cache.useUDP=true.
cache.tcpip.primaryhost
String
The host name of the computer
where the primary WebSphere
Application Server is installed.
Configure only if
cache.useUDP!=true.
cache.tcpip.primaryport
Default:
22345
The port number that the
primary WebSphere Application
Server computer uses for
TCP-based caching
communication.
Configure only if
cache.useUDP!=true.
cache.tcpip.secondaryhost
String
The host name of the computer
where the secondary WebSphere
Application Server is installed.
Configure only if
cache.useUDP!=true.
cache.tcpip.secondaryport
Default:
22345
The port number that the
secondary WebSphere
Application Server computer
uses for TCP-based caching
communication.
Configure only if
cache.useUDP!=true.
jms.MEClusterName
String
(Cluster only) The JMS ME cluster
name
classpath.targetServer.javaHome
String
Configuration of target
application server requires the
location of the JAVA_HOME that
is used to run the target
application server.
This path must be accessible from
the server being configured.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Deploy LiveCycle properties
128
Property
Values
Description
classpath.targetServer.pop3JarPath
String
Path to the Pop3 JAR file that is
accessible to the target
application server. This path must
be accessible from the server
being configured.
datasource.dbType
Choose a database:
The type of database configured
to use with LiveCycle ES
●
oracle
●
sqlserver
●
db2
datasource.dbName
String
The name of the database
datasource.dbHost
String
The host name or IP address of
the server where the database is
located
datasource.dbPort
Integer
The database port LiveCycle ES
will use when communicating
with the database
datasource.dbUser
String
The user ID LiveCycle ES will use
when accessing the database
datasource.dbPassword
String
The password associated with the
database user ID
datasource.target.driverPath
String
JDBC driver in the application
server lib directory. This path
must be valid and accessible from
the server being configured.
datasource.local.driverPath
String
Local JDBC driver. This value is
used for testing direct database
connection.
jms.MEClusterName
String.
This property is required for
WebSphere Clustering only.
Specify the JMS ME Cluster Name.
Deploy LiveCycle properties
These properties only apply to the deployLiveCycle operation.
Note: You must configure the LiveCycle Server Information section. (See “Common properties” on
page 122.)
Initialize LiveCycle properties
These properties only apply to the initializeLiveCycle operation.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Initialize BAM properties
129
Note: You must configure the LiveCycle Server Information section. (See “Common properties” on
page 122.)
Initialize BAM properties
These properties only apply to the initialize BAM operation.
Note: LiveCycle ES Business Activity Monitoring is an optional solution component with LiveCycle ES.
Property
Values
Description
BAMHost
String
The host name of the server
where
Business Activity Monitoring is
deployed and running
BAMPort
Integer
The port number BAM Server
uses to listen for requests
BAMAdminUserID
String
The Business Activity Monitoring
administrator user ID to use
when connecting to BAM Server
BAMAdminPassword
String
The Business Activity Monitoring
administrator password to use
when connecting to BAM Server
databaseType
Choose a database:
The type of database
LiveCycle ES is using to capture
Business Activity Monitoring
data
oracle
sqlserver
db2
Deploy LiveCycle Components properties
The properties in the table apply to these operations:
●
Deploy LiveCycle Components
●
Validate LiveCycle Component Deployment
●
Validate LiveCycle Server
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Command line interface usage
130
Note: You must configure the LiveCycle Server Information section. (See “Common properties” on
page 122.)
Property
Values
Description
LCAdminUserID
String
The user ID to assign to the
LiveCycle administrator user. This
User ID is used to log in to
LiveCycle Administration
Console.
LCAdminPassword
String
The password to assign to the
LiveCycle administrator user. This
password is used to log in to
LiveCycle Administration
Console.
Command line interface usage
After you configure your property file, navigate to the [LiveCycleES root]/configurationManager/bin folder.
To view a complete description of the LiveCycle Configuration Manager CLI commands, type
configurationManagerCLI help.
Note: The LiveCycle Configuration Manager CLI requires that the Sun™ Java™ Software Development Kit
(JDK) 1.5.0_11 or later is installed, the JAVA_HOME environment variable is configured, and the
PATH points to the location where your JDK is installed. For more information, see the Preparing to
Install LiveCycle ES guide for your single or cluster environment.
Configure LiveCycle CLI usage
The Configure LiveCycle operation requires the following syntax:
configureLiveCycle -f [propertyFile]
where:
●
-f [propertyFile] is a property file containing the required arguments. For more information
on creating a property file, see “Command line interface property file” on page 121.
Configure Application Server CLI usage
The Configure Application Server operation for WebSphere requires the following syntax:
configureApplicationServer -targetServer_AdminPassword [password] -f
[propertyFile] [-skip [configurationsToSkipList]]
where:
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
●
-f [propertyFile] : A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
●
Command line interface usage
131
-skip [configurationsToSkipList]: This is an optional parameter which allows you to list
the application server components you do not want to configure. Specify the excluded components
in a comma separated list. Valid options are JMS, Datasource, or Core.
Deploy LiveCycle CLI usage
The Deploy LiveCycle operation requires the following syntax:
deployLiveCycle -f [propertyFile]
where:
●
-f [propertyFile]: A property file containing the required arguments. For more information
on creating a property file, see “Command line interface property file” on page 121.
Initialize LiveCycle CLI usage
The initialize LiveCycle operation requires the following syntax:
initializeLiveCycle -f [propertyFile]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
Initialize Business Activity Monitoring CLI usage
The Initialize Business Activity Monitoring operation requires the following syntax:
initializeBAM -f [propertyFile]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
Deploy LiveCycle Components CLI usage
The Deploy LiveCycle Components operation requires the following syntax:
deployLiveCycleComponents -f [propertyFile] -targetServer_AdminPassword
[password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Validate Application Server Topology CLI usage
The Validate Application Server Topology operation is optional and requires the following syntax:
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Command line interface usage
132
validateApplicationServerTopology -f [propertyFile]
-targetServer_AdminPassword [password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Validate Database Connectivity CLI usage
The Validate Database Connectivity operation is optional and requires the following syntax:
validateDBConnectivity -f [propertyFile] -datasource_dbPasssword
[password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
●
-datasource_dbPassword [password]: Allows you to set the database user password on the
command line. If this argument is present, it will override the datasource.dbPassword property in
the property file.
Validate Application Server Configurations CLI usage
The Validate Application Server Configurations operation is optional and requires the following syntax:
validateApplicationServerConfigurations -f [propertyFile]
-targetServer_AdminPassword [password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Validate LiveCycle Server CLI usage
The Validate LiveCycle Server operation is optional and requires the following syntax:
validateLiveCycleServer -f [propertyFile] -targetServer_AdminPassword
[password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Configuring LiveCycle ES Application Server Clusters Using WebSphere
Examples usage
133
Validate LiveCycle Component Deployment CLI usage
The Validate LiveCycle Component Deployment operation is optional and requires the following syntax:
validateLiveCycleComponentDeployment -f [propertyFile]
-targetServer_AdminPassword [password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 121.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Examples usage
From the C:\Adobe\LiveCycle8.2\configurationManager\bin, type:
./configurationManagerCLI ConfigureLiveCycle -f cli_propertyFile.txt
where cli_propertyFile.txt is the name of the property file you created.
Error logs
If an error occurs, you can review the CLI error logs located in the [LiveCycleES
root]\configurationManager\log folder. The log file generated has a naming convention such as
lcmCLI.0.log where the number in the file name (0) increments when the log files are rolled over.
Next steps
If you used LiveCycle Configuration Manager CLI to configure and deploy LiveCycle ES, you can now do the
following tasks:
●
Verify the deployment. (See “Final setup for LiveCycle Rights Management ES” on page 81.)
●
Access LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 68.)
●
Configure LiveCycle ES solution components to access LDAP. (See “Configuring LiveCycle ES to access
LDAP” on page 82.)
●
Uninstall LiveCycle ES. (See “Uninstalling LiveCycle ES” on page 102.)
If you did not configure your application server for deployment, you must now configure your application
server. (See “Manually Configuring a WebSphere Cluster” on page 43.)
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement