bb c Installing and Deploying LiveCycle ES

bb c Installing and Deploying LiveCycle ES
bc
Installing and Deploying LiveCycle® ES
for WebSphere®
Adobe® LiveCycle® ES
February 2008
Version 8.0
© 2008 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle® ES (8.0) Installing and Deploying LiveCycle ES for Microsoft® Windows®, UNIX®, and Linux
Edition 1.2, February 2008
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, FrameMaker, LiveCycle, PageMaker, PhotoShop, Reader, and PostScript are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
IBM, AIX, DB2, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.
Sun, Java, and Solaris, and SunOS 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 BISAFE and/or TIPEM software by RSA Data Security, Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes code licensed from RSA Data Security.
This product includes software developed by the JDOM Project (http://www.jdom.org/).
Macromedia Flash 8 video is powered by On2 TrueMotion video technology. © 1992-2005 On2 Technologies, Inc. All Rights Reserved.
http://www.on2.com.
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
Portions of this code are licensed from Nellymoser(www.nellymoser.com)
MPEG Layer-3 audio compression technology licensed by Fraunhofer IIS and THOMSON Multimedia (http://www.iis.fhg.de/amm/).
This product includes software developed by L2FProd.com (http://www.L2FProd.com/)
The BeanShell library is licensed under the GNU Library General Public License, a copy of which is included with this software.
This product includes software developed by The Werken Company.
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
The OpenOffice.org library is licensed under the GNU Library General Public License, a copy of which is included with this software.
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.................................................................................................................. 6
What’s in this document?............................................................................................................................................................ 6
Who should read this document? ............................................................................................................................................ 6
Additional information................................................................................................................................................................. 7
1
Introduction ................................................................................................................................. 9
About the installation, configuration, and deployment process.................................................................................. 9
Selecting tasks for configuring and deploying LiveCycle ES.......................................................................................... 9
Upgrading to LiveCycle ES........................................................................................................................................................10
Installation, configuration, and deployment lists.............................................................................................................10
Automatic installation and deployment list.................................................................................................................11
Manual installation and deployment list.......................................................................................................................11
2
Installing the Solution Component Files ................................................................................. 12
Installing the product files ........................................................................................................................................................12
Installing to a Windows staging platform for deployment on Linux or UNIX..................................................13
Installing LiveCycle ES ..........................................................................................................................................................13
Viewing the error log ..................................................................................................................................................................15
Next steps........................................................................................................................................................................................15
3
Configuring LiveCycle ES for Deployment .............................................................................. 16
About LiveCycle Configuration Manager ............................................................................................................................16
Configuration tasks: Automatic configuration............................................................................................................17
Configuration tasks: Manual configuration..................................................................................................................17
Deploying LiveCycle ES into a distributed environment ...............................................................................................17
Determining the application server SOAP port.................................................................................................................17
Using LiveCycle Configuration Manager with administrative security ....................................................................18
Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES ............................................18
Saving configurations in LiveCycle Configuration Manager..................................................................................20
Uninstalling EAR files ..................................................................................................................................................................21
Next steps........................................................................................................................................................................................21
4
Manually Configuring WebSphere........................................................................................... 22
Configuring the JVM arguments and properties..............................................................................................................22
Configuring WebSphere Application Server if global security is enabled ........................................................23
Configuring WebSphere time-out settings ........................................................................................................................24
Configuring the LiveCycle ES database connectivity......................................................................................................26
Configuring the DB2 data source.....................................................................................................................................27
Configuring the Oracle data source ................................................................................................................................29
Configuring the SQL Server data source .......................................................................................................................32
Configuring JMS resources for WebSphere........................................................................................................................35
Assigning JMS Activation Specification.........................................................................................................................39
Configuring J2C authentication for JMS ..............................................................................................................................40
SQL Server JMS validation.........................................................................................................................................................41
Restart WebSphere ......................................................................................................................................................................42
Run LiveCycle Configuration Manager validation............................................................................................................42
Next step..........................................................................................................................................................................................42
3
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
5
Contents
4
Manually Deploying WebSphere.............................................................................................. 43
About deploying LiveCycle ES solution components.....................................................................................................43
WebSphere directory name ...............................................................................................................................................43
Summary of deployable components............................................................................................................................43
Deploying to WebSphere..........................................................................................................................................................44
Starting the application .............................................................................................................................................................44
Next steps........................................................................................................................................................................................44
6
Post-Deployment Activities ...................................................................................................... 45
Configuring Acrobat 8.1 for PDF Generator ES .................................................................................................................45
Final setup for LiveCycle Rights Management ES.............................................................................................................46
Verifying the deployment and accessing LiveCycle Administration Console........................................................46
Accessing LiveCycle Administration Console..............................................................................................................46
Viewing the log files..............................................................................................................................................................47
Accessing solution component web applications ...........................................................................................................47
Accessing Rights Management ES:..................................................................................................................................48
Accessing User Management ..................................................................................................................................................48
Configuring LiveCycle ES to access LDAP............................................................................................................................49
Setting PDF Generator ES Watched Folder performance parameters......................................................................49
Configuring FIPS mode ..............................................................................................................................................................50
Configuring HTML digital signature ......................................................................................................................................51
Configuring the Connector for EMC Documentum service..........................................................................................51
Creating the XDP MIME format in your Documentum repository .......................................................................53
Configuring the Connector for IBM FileNet service .........................................................................................................54
Uninstalling LiveCycle ES...........................................................................................................................................................57
7
Manually Configuring BAM Server for LiveCycle ES ............................................................... 59
Configuring WebSphere for BAM Server .............................................................................................................................59
Creating a virtual host alias ................................................................................................................................................60
Creating and configuring the BAM Server metadata database ..................................................................................60
User accounts ..........................................................................................................................................................................61
Configuring your database environment .....................................................................................................................61
Creating the data source for the BAM Server metadata database.......................................................................63
Configuring WebSphere parameters ....................................................................................................................................65
Configuring Process Management ES for BAM Server....................................................................................................65
Deploying BAM Server to WebSphere..................................................................................................................................66
Limitations of BAM Server LDAP connectivity.............................................................................................................69
Best practices for BAM Server LDAP connectivity......................................................................................................69
Configuring automatic LDAP synchronization ...........................................................................................................70
Configuring LDAP user mapping .....................................................................................................................................71
Configuring LDAP role mapping......................................................................................................................................72
Manually synchronizing with the LDAP server............................................................................................................73
Using the BAM Dashboard........................................................................................................................................................74
Additional documentation .......................................................................................................................................................75
Uninstalling Business Activity Monitoring ES ....................................................................................................................75
8
Advanced Production Configuration....................................................................................... 76
LiveCycle Output ES and LiveCycle Forms ES ....................................................................................................................76
LiveCycle PDF Generator ES .....................................................................................................................................................76
EJB Pool Size Configuration ...............................................................................................................................................76
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
A
Contents
5
Troubleshooting ........................................................................................................................ 79
Getting help ...................................................................................................................................................................................79
Installation considerations .................................................................................................................................................79
Application server considerations ...................................................................................................................................79
Troubleshooting with log files.................................................................................................................................................80
LiveCycle Configuration Manager log file.....................................................................................................................80
Viewing the JVM system output and error logs..........................................................................................................80
Non-clustered environments.............................................................................................................................................81
Error messages ..............................................................................................................................................................................81
PDF Generator ES on Windows fails when converting native files ......................................................................81
Class not found .......................................................................................................................................................................82
JNDI name not found ...........................................................................................................................................................82
Failure to deploy adobe-livecycle-websphere.ear.....................................................................................................83
J2CA0294W warning messages ........................................................................................................................................83
XMLForm.exe permission error.........................................................................................................................................84
About This Document
This guide is one of several resources available to help you learn about Adobe® LiveCycle® ES (Enterprise
Suite). 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.
What’s in this document?
This guide provides information about how to install and configure the following solution components 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 Business Activity Monitoring ES
●
Adobe LiveCycle ES Connector for EMC Documentum
●
Adobe LiveCycle ES Connector for IBM FileNet
●
Adobe LiveCycle Digital Signatures ES
●
Adobe LiveCycle Forms ES
●
Adobe LiveCycle Foundation
●
Adobe LiveCycle Output ES
●
Adobe LiveCycle PDF Generator ES
●
Adobe LiveCycle Process Management ES
●
Adobe LiveCycle Reader Extensions ES
●
Adobe LiveCycle Rights Management ES
Who should read this document?
This guide provides information for administrators or developers responsible for installing, configuring,
administering, or deploying LiveCycle ES components. The information provided is based on the
assumption that anyone reading this guide is familiar with J2EE application servers, Linux, Microsoft
Windows, AIX, or Solaris operating systems, Oracle®, DB2®, or SQL Server database servers, and web
environments.
6
Adobe LiveCycle ES
About This Document
Installing and Deploying LiveCycle ES for WebSphere
Conventions used in this document
Conventions used in this document
This guide uses the following naming conventions for common file paths.
Name
Default value
Description
[LiveCycleES root]
Windows:
C:\Adobe\LiveCycle8\
The installation directory that is used for all
LiveCycle ES solution components. The
installation directory contains subdirectories
forAdobe LiveCycle Configuration Manager, the
LiveCycle ES SDK, and each LiveCycle ES
solution component installed (along with the
product documentation). This directory also
includes directories relating to third-party
technologies.
Linux and UNIX®:
/opt/adobe/livecycle8/
[appserver root]
The home directory of the
application server that runs the
LiveCycle ES services.
WebSphere on Windows:
C:\Program Files\IBM\WebSphere\AppServer
WebSphere on Linux and Solaris:
/opt/IBM/WebSphere/AppServer
WebSphere on AIX:
/usr/IBM/WebSphere/AppServer
[server name]
server1 for WebSphere
The name of the server configured on your
application server.
[dbserver root]
The location where the
LiveCycle ES database server is
installed.
Depends on the database type and your
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
General information about LiveCycle ES and LiveCycle ES Overview at
www.adobe.com/go/learn_lc_overview
the solution components
What’s new in the Adobe LiveCycle ES
(Enterprise Suite) release
www.adobe.com/go/learn_lc_whatsNew
LiveCycle ES terminology
www.adobe.com/go/learn_lc_glossary
Other services and products that integrate
with LiveCycle ES
www.adobe.com/products/livecycle
7
Adobe LiveCycle ES
About This Document
Installing and Deploying LiveCycle ES for WebSphere
Additional information
For information about
See
Other Adobe LiveCycle ES solution
components
partners.adobe.com/public/developer/main.html
Installing Adobe LiveCycle Workbench ES
Installing Your Development Environment at
www.adobe.com/go/learn_lc_installWorkbench
Upgrading to LiveCycle ES from a previous
version.
Preparing to Upgrade to LiveCycle ES at
www.adobe.com/go/learn_lc_upgradePreparation
Upgrading to LiveCycle ES for WebSphere at
www.adobe.com/go/learn_lc_upgradeWebSphere
Performing administrative tasks for
LiveCycle ES
Administering LiveCycle ES at
www.adobe.com/go/learn_lc_administration
All the documentation available for
LiveCycle ES
www.adobe.com/go/learn_lc_documentation
LiveCycle ES release information and
last-minute changes that occur to the
product
www.adobe.com/go/learn_lc_releaseNotes
Patch updates, technical notes, and
additional information about this product
version
www.adobe.com/support/products/enterprise
/index.html
8
1
Introduction
This chapter provides information to help you understand the type of installation and deployment you
should perform, and information that will help you understand the installation, configuration and
deployment process:
●
“About the installation, configuration, and deployment process” on page 9
●
“Installation, configuration, and deployment lists” on page 10
For information about preparing your system for installing LiveCycle ES, including system requirements,
see the Preparing to Install LiveCycle ES guide.
About the installation, configuration, and deployment process
Installing, configuring, and deploying LiveCycle ES involves the following processes:
Installing: You 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 (Windows) or /opt/adobe/LiveCycle8 (Linux or UNIX);
however, you can install the files to a different directory. In this guide, the default installation directory
is referred to as [LiveCycleES root]. (See “Installing the Solution Component Files” on page 12.)
Configuring and assembling: Configuring LiveCycle ES modifies a variety of 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. You configure and assemble
the components for deployment by running LiveCycle Configuration Manager. (See “Configuring
LiveCycle ES for Deployment” on page 16.) 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 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 files (LCAs) are packaged as JAR
files.
Initializing the LiveCycle ES database: Initializing the database to be used with LiveCycle ES creates
tables for use with Adobe 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. (See “Configuration tasks: Automatic configuration” on
page 17.)
Selecting tasks for configuring and deploying LiveCycle ES
After you perform an installation, you can run LiveCycle Configuration Manager to perform a variety of
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
9
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
●
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
●
Import the LiveCycle ES Samples
Introduction
Upgrading to LiveCycle ES
10
If you install Reader Extensions ES, you can also specify and import the Reader Extensions ES Rights
credential required for applying usage rights to PDF documents.
Although you can use LiveCycle Configuration Manager to configure the application server and set up
data sources to the database, you may prefer to complete these steps manually.
Here are reasons to configure your application server manually [You may want to configure your
application server manually for these reasons]:
●
You have other applications running on the application server 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, you will do the following tasks:
●
Use LiveCycle Configuration Manager to configure LiveCycle ES components to get the required font
and temp directories.
●
Manually configure the application server, configure datasources, and deploy LiveCycle ES EAR files.
●
Run LiveCycle Configuration Manager to initialize the database.
Upgrading to LiveCycle ES
Before installing LiveCycle ES for upgrading from LiveCycle 7.x and later, ensure that you have completed
the tasks described in Preparing to Upgrade to LiveCycle ES at
www.adobe.com/go/learn_lc_upgradePreparation.
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.
The automatic method refers to using LiveCycle Configuration Manager to configure LiveCycle ES,
configuring the application server, and deploying the solution components to the server. You would use
the automatic method if you want to have limited input into the installation, configuration, and
deployment of LiveCycle ES.
The manual method refers to using LiveCycle Configuration Manager to only configure LiveCycle ES and
initialize (bootstrap) the database. Configuring the application server, connecting to the database, and
deploying to the server is done by the administrator manually by following the instructions later in this
document. You would use the manual method if you want to have precise input into the installation,
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Introduction
Automatic installation and deployment list
11
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 required for installing LiveCycle ES solution components using the
automatic method. WebSphere Application Server must be installed before you perform the installation.
●
Ensure that you have the required software installed in the target environment. For more information,
see Preparing to Install LiveCycle ES.
●
Run the installation program. (See “Installing the Solution Component Files” on page 12.)
●
Run LiveCycle Configuration Manager and select all the tasks on the Task Selection screen. This step
will configure and assemble the LiveCycle ES EAR files, configure application server settings, deploy the
EAR files and other components to the application server, initialize the LiveCycle ES database, and
verify the deployment. (See “Configuring LiveCycle ES for Deployment” on page 16.)
●
Access LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 46.)
●
Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 49.)
Manual installation and deployment list
The following list includes the steps required for installing LiveCycle ES using the manual method. Your
application server must be installed and configured before you perform the installation.
●
Ensure that you have the required software installed and configured in the target environment. For
more information, see Preparing to Install LiveCycle ES at www.adobe.com/go/learn_lc_prepareInstall.
●
Run the installation program. (See “Installing the Solution Component Files” on page 12.)
●
Run LiveCycle Configuration Manager and select the Configure LiveCycle ES EARs task. This step will
configure and assemble LiveCycle ES. For more information, see “Configuring LiveCycle ES for
Deployment” on page 16.
●
Configure WebSphere Application Server settings. A variety of settings must be configured. (See
“Manually Configuring WebSphere” on page 22.)
●
Deploy the EAR files to the application server. You can do this manually or use
LiveCycle Configuration Manager. (See “Manually Deploying WebSphere” on page 43.)
●
Run LiveCycle Configuration Manager to deploy LiveCycle ES component files, and optionally deploy
product samples. (See “Configuring LiveCycle ES for Deployment” on page 16.)
●
Access LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 46.)
●
Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 49.)
2
Installing the Solution Component Files
This chapter describes how to use the installation program to install LiveCycle ES on a Windows, Linux, or
UNIX operating system.
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.)
This chapter covers the following topics:
●
“Installing the product files” on page 12
●
“Viewing the error log” on page 15
●
“Next steps” on page 15
Installing the product files
When you run an installation program, you need the following information:
●
The serial number for the solution components you are installing
●
The type of installation and configuration you are performing
Note: 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\
●
(Linux and UNIX) /opt/adobe/livecycle8/
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. The temporary directory is one of the
following locations:
●
(Windows) TMP or TEMP path as set in the environment variables
●
(Linux and UNIX) Logged-in user’s home directory
The InstallShield command line parameter -is:tempdir is not supported with the
LiveCycle ES installer. To work around this limitation, use the TMP environment variable to point
to a disk that has the required amount of free space.
12
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for WebSphere
Installing to a Windows staging platform for deployment on Linux or UNIX
13
On Linux 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/. If you are logged in as a non-root user, you must change the
installation directory to one for which you have permissions (read-write-execute privileges). For
example, you could change the directory to home/adobe/livecycle8.
Installing to 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 to a locked-down Linux environment. For example, a locked-down
environment would not have XWindows 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 Windows computer 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: If your installation includes LiveCycle PDF Generator ES and you will use the native application
conversion feature, the host and target operating system must be Windows.
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 16.
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 installer and
LiveCycle Configuration Manager.
➤ To install LiveCycle ES:
1. Navigate to the /livecycle_server/8.0 directory of the installation media.
2. Start the installation program:
●
(Windows) Double-click the win_livecycle8_setup.exe file.
●
(Linux, UNIX) From a command prompt, type the file name appropriate for your operating system:
./aix_livecycle8_setup.bin
./linux_livecycle8_setup.bin
./solaris_livecycle8_setup.bin
3. When prompted, select the language for the installation to use, and then click OK.
4. On the Welcome screen, click Next.
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for WebSphere
Installing LiveCycle ES
14
5. On the Destination screen, accept the default directory as listed or click Browse and navigate to the
directory where you want to install the solution component, and then click Next.
Note: If you type in the name of a directory that does not exist, it will be 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; if it
does, the installation program does not install the solution component.
6. 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: To reset the serial number, click Clear.
7. Read the Product License Agreement. If you agree, select I accept to the terms of the license
agreement, and then click Next.
8. (Windows staging only) Select the operating system for which you plan to configure LiveCycle ES and
click Next.
Note: At this point, you can specify to use Windows as a staging platform for your deployment. You can
select Linux or a UNIX operating system as the target for deployment even if you are installing
on Windows. For more details see “Installing to a Windows staging platform for deployment on
Linux or UNIX” on page 13.
9. (PDF Generator ES for Windows only) Select the appropriate option on the PDF Generator ES screen:
●
If you select Yes, 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 8.1 now.
If you have an unsupported version of Acrobat installed, complete the LiveCycle ES installation,
uninstall Acrobat, and then install Acrobat 8.1 from the LiveCycle ES installation media by following
the instructions in the procedure “Configuring Acrobat 8.1 for PDF Generator ES” on page 45.
●
If you are installing in a clustered environment, select No, do not enable native application
support for PDF Generator ES and then go to step 11.
10. (PDF Generator ES for Windows only) Confirm that you have Acrobat installed and click Next.
11. Review the installation details and click Install. The installation program displays the progress of the
installation. A summary screen appears when the solution component installation is completed.
12. Review the release notes that are displayed and click Next.
13. Select Start LiveCycle Configuration Manager and then click Finish. If you are upgrading LiveCycle
7.x to LiveCycle ES, do not select Start LiveCycle Configuration Manager. Click Finish and go to “Next
steps” on page 15.
Note: Selecting the Start option starts LiveCycle Configuration Manager, allowing you to complete your
configuration and deployment immediately. If you are not ready to run
LiveCycle Configuration Manager immediately, ensure that Start
LiveCycle Configuration Manager is not selected when you click Finish. You can start
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for WebSphere
Viewing the error log
15
LiveCycle Configuration Manager later, when you are ready. (See “Running
LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18.)
When you are ready to proceed with the configuration and deployment, see “Configuring
LiveCycle ES for Deployment” on page 16.
Note: (PDF Generator ES for Windows only) If you did not choose to install Acrobat 8.1 using the
LiveCycle ES installer, you must complete the steps listed in “Configuring Acrobat 8.1 for
PDF Generator ES” on page 45.
Viewing the error log
If any errors occur during the installation, the installation program creates a log file called log.txt, which
contains the error messages. The log file is located in the [LiveCycleES root] directory.
For information about errors that may occur during installation, see “Troubleshooting” on page 79.
Next steps
You must now configure LiveCycle ES for deployment. (See “Configuring LiveCycle ES for Deployment” on
page 16.)
3
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 the application server configuration
●
Deploy LiveCycle ES EAR files
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES components
●
Validate the LiveCycle ES component deployment
●
Configure the LiveCycle Reader Extensions ES Rights credential
●
Import the LiveCycle ES Samples
This chapter contains the following sections:
●
“About LiveCycle Configuration Manager” on page 16
●
“Deploying LiveCycle ES into a distributed environment” on page 17
●
“Determining the application server SOAP port” on page 17
●
“Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18
●
“Uninstalling EAR files” on page 21
This chapter assumes that you have prepared your environment for hosting LiveCycle ES and installed the
solution component files. If you have not done this, see the Preparing to Install LiveCycle ES guide and
“Installing the Solution Component Files” on page 12.
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 have the option of using
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, as well as the tasks 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 are planning to use LiveCycle Configuration Manager to configure the
application server or deploy to the application server, the application server must be started to enable
LiveCycle Configuration Manager to perform configuration tasks on it.
You can configure an application server that is installed on a different computer than the one on which
you are running LiveCycle Configuration Manager. However, an application server must also be installed
16
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring LiveCycle ES for Deployment
Configuration tasks: Automatic configuration
17
(but does not have to be running) on the LiveCycle Configuration Manager computer so that
LiveCycle Configuration Manager can use the application server library files. For more information, see
“Installing to a Windows staging platform for deployment on Linux or UNIX” on page 13.
Configuration tasks: Automatic configuration
LiveCycle Configuration Manager provides an interface that prompts you for information so that it can
automatically accomplish the following tasks:
Optionally, step 2 (configure application server properties) and step 4 (deploy EAR files) can be performed
manually (without using LiveCycle Configuration Manager).
Regardless of whether all of the tasks are performed automatically by LiveCycle Configuration Manager or
only some are performed manually, the tasks must be performed in the order in which they are listed.
Configuration tasks: Manual configuration
To manually configure the application server and deploy the EAR files, you perform the following tasks:
1. Run LiveCycle Configuration Manager and select the task to configure and assemble LiveCycle ES
solution component properties and assemble them into EAR files for deploying to the application
server.
2. Manually configure the application server by following the instructions in this document. (See
“Manually Configuring WebSphere” on page 22.)
3. Deploy the LiveCycle ES EAR files by following the instructions in this document. (See “Manually
Deploying WebSphere” on page 43.)
4. Run LiveCycle Configuration Manager and select the tasks to initialize the database, deploy
components and archives, and validate component and archive deployment.
5. Verify that the deployed LiveCycle ES services and solution components are available and operational
by logging in to LiveCycle Administration Console.
Deploying LiveCycle ES into a distributed environment
If the application server instance is on a different server, and not on the server with the Deployment
Manager, you must manually deploy the LiveCycle EAR files. If you attempt to deploy with
LiveCycle Configuration Manager, you will receive an error message indicating that the deployment failed.
Determining the application server SOAP port
Some LiveCycle Configuration Manager screens require you to provide the SOAP port of the application
server. Use this procedure 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 WebSphere Administrative Console navigation tree, select Servers > Application Servers and,
in the right pane, click the server name.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebSphere
Using LiveCycle Configuration Manager with administrative security
18
2. Under Communications, click Ports.
3. In the list of port names, make note of the port number for the SOAP CONNECTOR ADDRESS port.
Using LiveCycle Configuration Manager with administrative
security
When the WebSphere profile is configured to use administrative security (a user name and password are
required to log in to the WebSphere Administrative Console), complete the following configuration steps
before running LiveCycle Configuration Manager.
➤ To configure WebSphere for administrative security:
1. Open a command prompt.
2. Set JAVA_HOME to the JDK used with WebSphere. For details about the JDK version and how to set the
JAVA_HOME environment variable on UNIX, Linux, and Windows, see Preparing to Install LiveCycle ES.
3. Navigate to [appserver root]/bin and type the following command:
retrieveSigners.bat -conntype RMI -host localhost -port port_number
-autoAcceptBootstrapSigner -user administrator -password password
-uploadSigners
Replace port_number with the Bootstrap_address for the WebSphere Application Server and
administrator and password with the credentials used when creating the profile.
Running LiveCycle Configuration Manager to configure and
deploy 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, and 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 appears, the property on the screen turns red, and you
cannot proceed until you enter a valid value.
Note: LiveCycle Configuration Manager does not support the configuration of the data source for a
Microsoft SQL Server database with integrated security enabled. LiveCycle Configuration Manager
configures a data source for Microsoft SQL Server only if the integrated security is disabled (set to
False). If you intend to use integrated security, you must manually configure the data source. (See
“Manually Configuring WebSphere” on page 22.)
When LiveCycle Configuration Manager completes the configuration, it places the files to be deployed to
the application server (adobe-livecycle-native websphere-[OS].ear, adobe-livecycle websphere.ear, and
adobe-workspace-client.ear) in the following directory:
●
(Windows) [LiveCycleES root]\configurationManager\export
●
(Linux, UNIX) [LiveCycleES root]/configurationManager/export
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebSphere Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES
19
If you plan to manually deploy LiveCycle ES to the application server, you can find the files in the
appropriate directory. (See “Uninstalling LiveCycle ES” on page 57.)
If you are configuring a remote application server, ensure that an application server is also installed on the
LiveCycle Configuration Manager computer so that LiveCycle Configuration Manager can use the
application server library files.
➤ To perform configuration or deployment tasks using LiveCycle Configuration Manager:
1. Start the application server.
2. Start LiveCycle Configuration Manager by navigating to the [LiveCycleES root]/configurationManager/
bin directory and entering the following command:
●
(Windows) ConfigurationManager.bat
●
(Linux and UNIX) ./ConfigurationManager.sh
3. On the Welcome screen, click Next.
4. On the Upgrade Selection screen, ensure that Upgrade LiveCycle 7.x is not selected, and then click
Next.
5. On the Solution Component screen, select the LiveCycle ES solution components to configure and
deploy and click Next.
6. On the Task Selection screen, select all the tasks you want to perform and click Next.
Note: If you do not want to configure the application server and deploy LiveCycle ES using
LiveCycle Configuration Manager, select the Configure LiveCycle ES task only. After
completing this task in LiveCycle Configuration Manager, you must configure the application
server, deploy the configured EAR files, and return to LiveCycle Configuration Manager to
initialize the database, and deploy and validate the component files. (See “Next steps” on
page 21.)
Caution: Do not import the LiveCycle ES Samples if you are doing either of the following tasks:
●
If you are deploying LiveCycle ES to a production system. Importing the samples creates
users with default passwords, which may be a security concern for your production
environment.
●
If you are deploying either the Connector for EMC Documentum service or the
Connector for IBM FileNet service and you want to import LiveCycle ES Samples into the
Documentum repository or FileNet object store, you need to skip this step. You can import
the samples after you configure, enable, and activate the ECM to be the repository provider
using LiveCycle Administration Console. For more information, see “Configuring the
Connector for EMC Documentum service” on page 51 or “Configuring the
Connector for IBM FileNet service” on page 54.
7. Follow the instructions on the LiveCycle Configuration Manager screens. For more information about
the content or input required for any screen, press the F1 key on your keyboard to view Help for that
screen.
Note: LiveCycle Configuration Manager requires you to enter the IP address, or qualified host name, of the
server running the application server. The default value of localhost will not work.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring LiveCycle ES for Deployment
Saving configurations in LiveCycle Configuration Manager
20
Caution: LiveCycle Configuration Manager cannot configure WebSphere Application Server if global
security is enabled — you must do this manually (see “Configuring WebSphere Application
Server if global security is enabled” on page 23).
During configuration, you are required to provide the location of the JDBC drivers for your database. The
sections that follow provide the location of these drivers. The Oracle and DB2 drivers are in the [LiveCycleES
root]/lib/db/[database] directory. If you have not already done so, install the SQL Server database driver.
➤ To install the SQL Server database driver:
1. Download the SQL Server 2005 JDBC 1.1 database driver from the Microsoft website.
2. (Windows) Run the file. Extract the files to a temporary directory (referred to as the [SQL_root] directory
in the remainder of this section).
3. (Linux) Extract the *.tar.gz files to a temporary directory (referred to as the [SQL_root] directory in the
remainder of this section). The JDBC driver file is [SQL_root]/sqljdbc_1.1/enu/sqljdbc.jar.
Saving configurations in LiveCycle Configuration Manager
If you have set a series of configuration options in LiveCycle Configuration Manager, you can save the
configuration information so that if you run LiveCycle Configuration Manager again, you can use the same
configuration settings. When you run LiveCycle Configuration Manager again, you can select the saved
configuration and fields will be populated with the saved information.
Configuration information is saved with the .properties file name extension.
You can use LiveCycle Configuration Manager to revert all the current values back to the default values.
➤ To save a configuration:
1. In LiveCycle Configuration Manager, select Display Menu at the bottom of the screen.
2. Select Configurations > Save As.
3. Navigate to the directory where you want to save your configuration, type a name for the
configuration, and click Save.
➤ To open a saved configuration:
1. In LiveCycle Configuration Manager, select Display Menu at the bottom of the window, if it is not
already selected.
2. Select Configurations > Open.
3. Select the configuration you want to use and click Open.
➤ To revert to default values:
1. In LiveCycle Configuration Manager, select Display Menu at the bottom of the window, if it is not
already selected.
2. Select Configurations > Reset to Defaults.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebSphere
Uninstalling EAR files
21
Uninstalling EAR files
To redeploy a LiveCycle ES solution component, you must first uninstall the LiveCycle ES-related
applications from the application server.
For example, if you have assembled LiveCycle ES solution components again to configure solution
component properties differently and the previous adobe-livecycle-websphere.ear file is already
deployed, you must uninstall it before deploying the newly assembled EAR files.
➤ To uninstall the ear files:
1. Start the application server.
2. Start WebSphere Administrative Console by typing http://[host name]:[port]/admin in the
URL line of a web browser.
3. In the navigation tree, select Applications > Enterprise Applications.
4. Select the adobe-livecycle-native-websphere-[OS].ear, adobe-livecycle-websphere.ear and
adobe-workspace-client.ear applications, as well as any other installed LiveCycle ES applications (see
“Summary of deployable components” on page 43), and then click Stop.
5. Select the adobe-livecycle-native-websphere-[OS].ear, adobe-livecycle-websphere.ear application,
and adobe-workspace-client.ear, as well as any other installed LiveCycle ES applications, (see
“Summary of deployable components” on page 43), and then click Uninstall.
6. Save your changes to the Master Configuration and restart WebSphere.
After uninstalling the EAR file, you may need to reconfigure your EAR file and redeploy. See “Running
LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18.
Next steps
If you used LiveCycle Configuration Manager 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 46.)
●
Access LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 46.)
●
Configure LiveCycle solution components to access LDAP. (See “Configuring LiveCycle ES to access
LDAP” on page 49.)
●
Uninstall LiveCycle ES. (See “Uninstalling LiveCycle ES” on page 57.)
If you did not configure your application server for deployment, you must now configure your application
server. (See “Manually Configuring WebSphere” on page 22.)
4
Manually Configuring WebSphere
This chapter describes how to manually configure the application server to prepare for the manual
deployment of LiveCycle ES in a non-clustered environment. For information about how to automatically
configure your application server, see “Configuration tasks: Automatic configuration” on page 17.
Note: The Adobe LiveCycle Configuration manager uses a different naming convention for JMS queues
and topics than provided in this manual configuration section. For a complete listing of the
differences search the Support Knowledgebase for the technote entitled Different naming
conventions used for JMS queues and topics.
At this point in the installation process, you will have already installed LiveCycle ES files and run
LiveCycle Configuration Manager to configure the LiveCycle ES deployable archives. Now, you can
manually configure the database connectivity with the application server.
When LiveCycle ES is deployed to the application server, you can use LiveCycle Configuration Manager to
initialize LiveCycle ES and Business Activity Monitoring ES (if applicable).
This chapter includes the following topics:
●
“Configuring the JVM arguments and properties” on page 22
●
“Configuring WebSphere time-out settings” on page 24
●
“Configuring J2C authentication for JMS” on page 40
●
“Configuring throttling for LiveCycle PDF Generator ES” on page 26
●
“Configuring the LiveCycle ES database connectivity” on page 26
●
“Configuring JMS resources for WebSphere” on page 35
●
“Next step” on page 42
Configuring the JVM arguments and properties
You must configure the JVM arguments and custom properties.
➤ To configure the JVM arguments:
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.
4. In the Initial Heap Size box, type 256 and, in the Maximum Heap Size box, type 1024.
Note: This value depends on the hardware configuration and the available memory. Setting this value to
zero (0) might be preferable because it means NOMAX. Setting the value to zero does not mean that
the heap grows infinitely large because the initial heap size parameter ensures that the garbage
collector runs periodically to limit heap growth.
22
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring WebSphere Application Server if global security is enabled
23
5. In the Generic JVM arguments box, type -Dfile.encoding=utf8 and then click OK.
6. Under Additional Properties, click Custom Properties, and then click New.
7. In the Name box, type java.net.preferIPv4Stack and, in the Value box, type true.
8. Click OK or Apply.
9. Click Save directly to master configuration.
You need to create a J2C Authentication to assign to your data source.
➤ To create a J2C authentication configuration for the data source:
1. In the 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.
3. Click New.
4. Provide the appropriate information in these boxes:
Alias: Type a name appropriate for the database user (for example, type IDP_DS/db2-db2user).
User ID: Enter a user ID. This ID is the login credential used to access whichever database will be
used with the IDP_DS data source (for example, db2user).
Password: Type a password for this user.
5. Click OK or Apply.
6. In the Messages box, click Save directly to master configuration.
Configuring WebSphere Application Server if global security is enabled
If your installation uses global security, you must run WebSphere Application Server as a user with the
appropriate roles. You can employ one of the following options to configure WebSphere Application
Server to run if WebSphere global security is enabled:
●
Create a new user with the necessary roles, and run WebSphere Application Server as that user (see “To
create a new WebSphere Application Server user:” on page 23). If a user already exists to run
WebSphere Application Server, assign the necessary roles to that user. (see “To configure an existing
WebSphere Application Server user:” on page 24).
In a secure environment, it is recommended that you employ this option.
●
Configure the EVERYONE group with the necessary roles. (See “To configure the EVERYONE group:” on
page 24
➤ To create a new WebSphere Application Server user:
1. In the WebSphere Administrative Console navigation tree, click Environment > Naming > CORBA
Naming Service Users, then in the right pane click Add.
2. In User, type the name of the user that will run WebSphere Application Server and in Roles, select all
the roles (Cos Naming Read, Cos Naming Write, Cos Naming Create, Cos Naming Delete).
3. Click OK or Apply.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Manually Configuring WebSphere
Configuring WebSphere time-out settings
24
4. Click Save directly to master configuration.
Caution: Ensure that you start WebSphere Application Server as this user. Some WebSphere processes
may fail if you start WebSphere Application Server as a different user while global security is
enabled.
➤ To configure an existing WebSphere Application Server user:
1. In the WebSphere Administrative Console navigation tree, click Environment > Naming > CORBA
Naming Service Users, then in the right pane click on the user.
2. In Roles, select all the roles (Cos Naming Read, Cos Naming Write, Cos Naming Create, Cos Naming
Delete).
3. Click OK or Apply.
4. Click Save directly to master configuration.
Caution: Ensure that you start WebSphere Application Server as this user. Some WebSphere processes
may fail if you start WebSphere Application Server as a different user while global security is
enabled.
➤ To configure the EVERYONE group:
1. In the WebSphere Administrative Console navigation tree, click Environment > Naming > CORBA
Naming Service Groups, then in the right pane select the EVERYONE group.
2. In Roles, select all the roles (Cos Naming Read, Cos Naming Write, Cos Naming Create, Cos Naming
Delete).
3. Click OK or Apply.
4. Click Save directly to master configuration.
Configuring WebSphere time-out settings
Creation of a large number of users can be done by using a single invocation of the CreateLocalUsers API.
The API is expected to persist all the new users or roll back all changes in the event of a failure. Therefore,
the API is required to operate in a single transaction to support rollback. Because a transaction’s lifetime is
limited by the application server settings (usually 30 seconds), the number of inserts that can be
performed in the given time frame is limited. As a result, bulk insert APIs, such as CreateLocalUser, fail
when the number of users exceeds a certain limit. This limit is decided again by the transaction’s lifetime.
You must modify the following time-out settings:
●
Transaction time-out value
●
CORBA time-out value
●
SOAP request time-out value
Note: If you are installing LiveCycle PDF Generator ES, you must also complete “Next step” on page 42.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Manually Configuring WebSphere
Configuring WebSphere time-out settings
25
➤ To configure transaction time-out:
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. Under General Properties, in the Total transaction lifetime timeout box, type 300 (or higher).
4. Ensure that the value in the Maximum transaction timeout box is greater than or equal to the total
transaction time-out.
5. Click OK or Apply.
➤ To increase the CORBA time-out value:
1. In the navigation tree, click Servers > Application servers and, in the right pane, click the server name.
2. Under Container Settings, click Container Services > ORB Service.
3. Under General Properties, in the Request timeout box, type 360 and, in the Locate Request Timeout
box, type 300.
4. Click OK or Apply.
5. Click Save directly to master configuration.
➤ To increase the SOAP request time-out value:
1. Navigate to your [appserver root] directory and search for all files named soap.client.props. Multiple files
may have this name. Perform steps 2 to 4 for each of them.
2. Open the file in a text editor, find the com.ibm.SOAP.requestTimeout property, and change the value
from 180 to 1800.
3. Save the file(s).
4. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and, in
in the right pane, click the server name.
5. Under Server Infrastructure, expand Administration > Administration Services.
6. Under Additional Properties, click JMX connectors and, in the right pane, click SOAPConnector in the
list.
7. On the next screen, click Custom Properties, and then click requestTimeout in the list.
8. Under General Properties, in the Value box, change 600 to 1800.
9. Click OK or Apply.
10. Click Save directly to master configuration.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring throttling for LiveCycle PDF Generator ES
26
Configuring throttling for LiveCycle PDF Generator ES
PDF Generator ES requires a throttling configuration to be added to the application server configuration.
➤ To set the PDF Generator ES throttling configuration:
1. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and, in
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, on the next screen, click Custom
Properties.
4. Click New and, in the following boxes, type the corresponding text to create a new property:
Name: com.ibm.websphere.ejbcontainer.poolSize
Value: LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#NativeToPDFInvoker=1,1:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#OpenOfficeToPDFInvoker=1,1:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#ImageToPDFInvoker=3,3:
LiveCycle8#adobe-pdfg-bmc-invoker-ejb.jar#PSToPDFInvoker=3,3
Note: You must manually type the value. You cannot copy and paste the value from this document.
In the example, LiveCycle8 is the name of the LiveCycle ES 8.0 core application as shown in the
WebSphere Application Server. If this name is different, all four instances of the string LiveCycle8
in the value parameter must be replaced with the actual application name.
Description: Adobe PDF Generator Throttling Configuration
5. Click OK or Apply.
6. Click Save directly to master configuration.
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
must 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, which is
available at http://www.adobe.com/go/learn_lc_prepareInstall:
●
Database name
●
Server name
●
User name
●
Password
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring the DB2 data source
27
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. 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)
●
[LiveCycleES root]\lib\db\db2
➤ To create a DB2 JDBC provider:
1. In the WebSphere Administrative Console navigation tree, click Environment > Websphere Variables
and, in the right pane, click DB2UNIVERSAL_JDBC_DRIVER_PATH.
2. In the Value box, type the path to the db2libs directory.
3. Click OK or Apply.
4. Click Save directly to master configuration.
5. In the navigation tree, click Resources > JDBC > JDBC Providers.
6. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
7. In the Step 1 pane, set the following configuration:
●
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 default, which is DB2 Universal JDBC Driver Provider, or type
LiveCycle - db2 - IDP_DS.
8. Click Next and, in the Step 2 pane, click Next again.
9. In the Step 3 pane, click Finish.
10. Click Save directly to master configuration.
➤ To create the DB2 JDBC data source:
1. In the navigation tree, select Resources > JDBC > JDBC Providers and, in the right pane, click the
provider you created in “To create a DB2 JDBC provider:” on page 27.
2. Under Additional Properties, click Data sources and then click New.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring the DB2 data source
28
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 “To create a J2C authentication configuration for
the data source:” on page 23, and then click Next.
4. In the Step 2 pane, type the database name and server name of the database you created in “To create
a J2C authentication configuration for the data source:” on page 23.
5. Ensure that Use this data source in container managed persistence (CMP) is selected, and then click
Next.
6. In the Step 3 pane, click Finish.
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 “To create a J2C authentication configuration for the data source:” on page 23.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
8. Click OK or Apply.
9. 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 data
source you just created, either DB2 Universal JDBC Driver Provider or LiveCycle - db2 - IDP_DS, as
used as an example in “To create a DB2 JDBC provider:” on page 27.
2. Under Additional Properties, click Data sources and then select 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 100 or higher if required.
●
In the Minimum connections box, type 1.
4. Click OK or Apply.
5. Click Save directly to master configuration.
➤ To create the DB2 JDBC data source 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 click the provider you created in
“To create a DB2 JDBC provider:” on page 27.
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.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
●
Configuring the Oracle data source
29
In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select
the authentication alias created for this data source in “To create a J2C authentication configuration
for the data source:” on page 23.
4. In the Step 2 pane, type the database name and server name of the database you created in “To create
a J2C authentication configuration for the data source:” on page 23, and then click Next.
5. 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 “To create a J2C authentication configuration for the data source:” on page 23.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
7. Click OK or Apply.
8. 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
DB2 Universal JDBC Driver Provider for RM data source you just created.
2. Under Additional Properties, click Data sources and then select 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 100 or higher if required.
●
In the Minimum connections box, enter 1.
4. Click OK or Apply.
5. 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 the following website:
www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_10201.html
2. In the [appserver root] directory, create a directory named db_driver and copy to this directory the
ojdbc14.jar file that you downloaded.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring the Oracle data source
30
➤ To create the Oracle JDBC provider:
1. 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 29 and then click OK.
3. Click Save directly to master configuration.
4. In the navigation tree, click Resources > JDBC > JDBC Providers.
5. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
6. In the Step 1 pane, set the following configuration:
●
In the Database type list, select Oracle.
●
In the Provider type list, select Oracle JDBC Driver.
●
In the Implementation type list, select Connection pool data source.
7. Click Next and, in the Step 2 pane, accept the default database class path and click Next again.
8. In the Step 3 pane, click Finish.
9. Click Save directly to master configuration.
➤ To create the Oracle JDBCdata 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 29.
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, type IDP_DS.
●
In the JNDI name, type IDP_DS.
●
In the list, under Component-Managed Authentication and XA Recovery Authentication, select the
authentication alias created for this data source in “To create a J2C authentication configuration for
the data source:” on page 23.
4. In the Step 2 pane, type the following line in the URL field, 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.
6. Click Save directly to master configuration.
7. 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 “To create a J2C authentication configuration for the data source:” on page 23.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
●
Configuring the Oracle data source
31
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
8. Click OK or Apply.
9. 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 you just created.
2. Under Additional Properties, click Data sources and then select IDP_DS.
3. On the next screen, under Additional Properties, click Connection Pool Properties and, in the
Maximum connections box, type 100.
4. Click OK or Apply.
5. Click Save directly to master configuration.
➤ To create the Oracle JDBCdata source 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
provider you created in “To install the Oracle 10g database driver:” on page 29.
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, select the
authentication alias created for this data source in “To create a J2C authentication configuration for
the data source:” on page 23.
4. In the Step 2 pane, type the following line in the URL field, 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.
6. Click Save directly to master configuration.
7. Select the data source you just created to modify additional parameters.
8. 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 “To create a J2C authentication configuration for the data source:” on page 23.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
9. Click Save directly to master configuration.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring the SQL Server data source
32
➤ To configure IDP_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
Oracle JDBC Driver data source you just created.
2. Under Additional Properties, click Data sources and then select RM_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.
5. 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 already, download and install the SQL Server 2005 JDBC Driver 1.1 from the
following Microsoft site by following the website instructions:
http://www.microsoft.com/downloads/details.aspx?familyid=6d483869-816a-44cb-9787-a866235
efc7c&displaylang=en
Note: Make note of the directory location where you install the driver on your system.
➤ 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 32 and then click OK.
3. Click Save directly to master configuration.
4. In the navigation tree, click Resources > JDBC > JDBC Providers.
5. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
6. In 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 User-defined JDBC Provider (default).
7. In the Step 2 pane, set the class path configuration as follows and then click Next:
${MSSQLSERVER_JDBC_DRIVER_PATH)/sqljdbc.jar
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring the SQL Server data source
33
8. In the Step 3 pane, click Finish.
9. 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 32.
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 “To create a J2C authentication configuration
for the data source:” on page 23.
4. In the Step 2 pane, accept the default data store helper class and click Next.
5. In the Step 3 pane, click Finish.
6. Click Save directly to master configuration.
7. Select the data source you just created to modify additional parameters.
8. 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 “To create a J2C authentication configuration for the data source:” on page 23.
●
In the Mapping-configuration alias list, select DefaultPrincipalMapping.
9. 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 data source you just created.
2. Under Additional Properties, click Data sources and then select IDP_DS.
3. On the next screen, under Additional Properties, click Custom Properties, and then click New.
4. Under DB2 Universal Data Source Properties, type the database name and server name:
●
In the Database name box, type database_name.
●
In the Server name box, type the IP address of SQL Server database.
5. Click OK or Apply.
6. Click Save directly to master configuration.
7. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
User-defined JDBC Driver data source you just created.
8. Under Additional Properties, click Data sources and then select IDP_DS.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring the SQL Server data source
34
9. On the next screen, under Additional Properties, click Connection Pool Properties and, in the
Maximum connections box, type 100.
10. Click OK or Apply.
11. Click Save directly to master configuration.
➤ To create the SQL Server 2005 data source 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
provider you created in “To create the SQL Server 2005 JDBC provider:” on page 32.
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 “To create a J2C authentication configuration
for the data source:” on page 23.
4. In the Step 2 pane, accept the default data store helper class and click Next.
5. In the Step 3 pane, click Finish.
6. Click Save directly to master configuration.
➤ To configure IDP_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 data source you just created.
2. Under Additional Properties, click Data sources and then select RM_DS.
3. On the next screen, under Additional Properties, click Custom Properties and then click New.
4. Provide the appropriate information in these boxes:
Alias: Type a name appropriate for the database user (for example, type IDP_DS/db2-db2user).
User ID: Enter a user ID. This ID is the login credential used to access whichever database will be
used with the IDP_DS data source (for example, db2user).
Password: Type a password for this user.
5. Click OK or Apply.
6. Click Save directly to master configuration.
7. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the
User-defined JDBC Driver data source you just created.
8. Under Additional Properties, click Data sources and then select RM_DS.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Manually Configuring WebSphere
Configuring JMS resources for WebSphere
35
9. On the next screen, under Additional Properties, click Connection Pool Properties and, in the
Maximum connections box, enter 30.
10. Click OK or Apply.
11. Click Save directly to master configuration.
➤ Configuring integrated security on Windows:
To use integrated security to make a trusted connection with SQL Server:
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.
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. On the computer where WebSphere is installed, add sqljdbc_auth.dll to the Windows systems path
(C:\Windows). The sqljdbc_auth.dll file is in the same location as the Microsoft SQL JDBC 1.1 driver
installation (default is [InstallDir]/sqljdbc_1.1/enu/auth/x86).
8. Modify the WebSphere’s Windows service (IBM WebSphere Application Server V6.1 - <node>) property
for Log On As from Local System to a good login account.
9. Set SQL Server’s Security from Mixed mode to Windows Authentication only.
Configuring JMS resources for WebSphere
You must configure Java Message Service (JMS) resources for WebSphere.
➤ To create the IDP_JMS_Bus:
1. In the WebSphere Administrative Console navigation tree, click Service Integration > Buses and, in
the right pane, click New.
2. In the Step 1 pane, type IDP_JMS_Bus in the box provided.
3. Click Next and then click Finish on the screen that follows.
4. Click Save directly to master configuration.
➤ To assign 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. In the Step 1 pane, ensure that Server is selected and then click Next.
4. In the Step 2 pane, select Data store and click Next.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring JMS resources for WebSphere
36
5. In the Step 3 pane, select Create default data source with generated JNDI name and click Next.
6. Click Finish, and then click Save directly to master configuration.
Note: After you restart the application server, you can test whether the messaging bus has been started
correctly by navigating to Service Integration > Buses, clicking IDP_JMS_Bus, and then clicking
Messaging engines under Topology. A green symbol is displayed to show that a messaging bus is
functioning.
➤ To configure JMS queue connection factories:
1. In the navigation tree, click Resources > JMS > Queue connection factories.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
3. Select Default messaging provider and click OK.
4. In the Administration area, set these properties:
●
In the Name box, type QueueConnectionFactory.
●
In the JNDI name box, type QueueConnectionFactory.
5. In the Connection area, in the Bus name list, select IDP_JMS_Bus.
6. In the Quality of Service area, 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. In the Advanced Administrative area, select the appropriate XA recovery authentication alias as defined
in “To create a J2C authentication configuration for the data source:” on page 23.
8. Click OK or Apply.
9. Click Save directly to master configuration.
10. In the list, click QueueConnectionFactory and, under Additional Properties, click Connection pool
properties.
11. 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.
12. Click OK or Apply.
13. Click Save directly to master configuration.
14. Repeat steps 2 through 13 to create another JMS queue connection factory, replacing
QueueConnectionFactory with JobManagerQueueConnectionFactory in step 5 for both the name
and JNDI name.
➤ To configure JMS topic connection factories:
1. In the navigation tree, click Resources > JMS > Topic connection factories.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring JMS resources for WebSphere
37
3. Select Default messaging provider and click OK.
4. In the Administration area, set these properties:
●
In the Name box, type TopicConnectionFactory.
●
In the JNDI name box, type TopicConnectionFactory.
5. In the Connection area, in the Bus name list, select IDP_JMS_Bus.
6. In the Quality of Service area, 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. In the Advanced Administrative area, select the appropriate XA recovery authentication alias as defined
in “To create a J2C authentication configuration for the data source:” on page 23.
8. Click OK or Apply.
9. Click Save directly to master configuration.
10. In the list, click TopicConnectionFactory and, under Additional Properties, click Connection Pool
Properties.
11. 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.
12. Click OK or Apply.
13. Click Save directly to master configuration.
14. Repeat steps 3 through 13 to create another connection factory, replacing TopicConnectionFactory
with JobManagerTopicConnectionFactory in step 4 for both the name and JNDI name.
➤ To create a queue:
1. In the navigation tree, click Resources > JMS > Queues.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
3. Accept the default or select Default messaging provider and then click OK.
4. In the Administration area, set these properties:
●
In the Name box, type queue/adobe_PECommandQueue.
●
In the JNDI name box, type queue/adobe_PECommandQueue.
5. In the Connection area, 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. In the Advanced area, in the Read ahead list, select Inherited from connection factory.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring JMS resources for WebSphere
38
7. Click OK or Apply.
8. Click Save directly to master configuration.
9. Repeat steps 3 through 8 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
Delivery Mode
JNDI name
adobe_PEDCommandQueue
persistent
queue/adobe_PEDCommandQueue
adobe_PEInteractionQueue
persistent
queue/adobe_PEInteractionQueue
adobe_JobManagerQueue
persistent
queue/adobe_JobManagerQueue
Next, you must create a bus destination for each queue defined in “To create a queue:” on page 37.
➤ To create a bus destination:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS_Bus.
2. On the next screen, under Destination Resources, click Destinations, and then click New.
3. On the next screen, under Select Destination Type, select Queue and then click Next.
4. In the step 1 pane, in the Identifier box, type adobe_PECommandQueue and then click Next.
5. Click Next, and then click Finish.
6. Click Save directly to master configuration.
7. Repeat steps 3 through 6 for each queue defined in “To create a queue:” on page 37.
➤ To create the first topic:
1. In the navigation tree, click Resources > JMS > Topics.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. In the Administration area, set these properties:
●
In the Name box, type adobe_LAFEventTopic.
●
In the JNDI name box, type topic/adobe_LAFEventTopic.
5. In the Connection area, set the properties as follows:
●
In the Topic name box, type adobe_LAFEventTopic.
●
In the Bus name list, select IDP_JMS_Bus.
●
In the Topic space list, select Default.Topic.Space.
6. Click OK or Apply.
7. Click Save directly to master configuration.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Assigning JMS Activation Specification
8. Repeat steps 1 through 7 for the queue in the following table, replacing the Name, JDNI name and
Topic name properties.
Name and topic name
Delivery Mode
JNDI name
adobe_TaskEventTopic
persistent
topic/adobe_TaskEventTopic
Assigning JMS Activation Specification
➤ To create PECommand_AS:
1. In the WebSphere Administrative Console navigation tree, click Resources > JMS > Activation
specifications.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. In the Administration area, set these properties:
●
In the Name box, type PECommand_AS.
●
In the JNDI name box, type PECommand_AS.
5. In the Destination area, set the properties as follows:
●
In the Destination type list, select Queue.
●
In the Destination JNDI name box, type queue/adobe_PECommandQueue.
●
In the Bus name list, select IDP_JMS_Bus.
6. Click OK or Apply.
7. Click Save directly to master configuration.
➤ To create Task_Event_AS:
1. In the navigation tree, click Resources > JMS > Activation specifications.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. In the Administration area, set these properties:
●
In the Name box, type Task_Event_AS
●
In the JNDI name box, type Task_Event_AS
5. In the Destination area, set the properties as follows:
●
In the Destination type list, select Topic.
●
In the Destination JNDI name box, type topic/adobe_TaskEventTopic
●
In the Bus name list, select IDP_JMS_Bus.
6. Click OK or Apply.
7. Click Save directly to master configuration.
39
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
Configuring J2C authentication for JMS
40
➤ To create JobManager_AS:
1. In the navigation tree, click Resources > JMS > Activation specifications.
2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New.
3. Accept the default or select Default messaging provider and click OK.
4. In the Administration area, set these properties:
●
In the Name box, type JobManager_AS.
●
In the JNDI name box, type JobManager_AS.
5. In the Destination area, set the properties as follows:
●
In the Destination type list, select Queue.
●
In the Destination JNDI name box, type queue/adobe_JobManagerQueue
●
In the Bus name list, select IDP_JMS_Bus.
6. Click OK or Apply.
7. Click Save directly to master configuration.
Configuring J2C authentication for JMS
This section outlines how to set J2C authentication.
Note: This procedure is required only for WebSphere installations where administrative security is
enabled. When your application server is configured to enable administrative security, you must
create the JMS group, JMS user, associating security, and assigning group privileges.
➤ To configure J2C authentication:
1. In the WebSphere Administrative Console navigation tree, click Security > Secure administration,
applications > infrastructure.
2. Under Authentication, click Java Authentication and Authorization Service > J2C authentication
data, and then click New.
3. Provide the appropriate information in these boxes:
Alias: Type a name appropriate for the database user (for example, type IDP_DS/db2-db2user).
User ID: Enter a user ID. This ID is the login credential used to access whichever database will be
used with the IDP_DS data source (for example, db2user).
Password: Type a password for this user.
4. Click OK or Apply.
5. Click Save directly to master configuration.
➤ To create a group:
1. In the navigation tree, click User and Groups > Manage Groups, and then click Create.
2. In the Group name box, type lc8_jms_group, and then click Create.
Adobe LiveCycle ES
Manually Configuring WebSphere
Installing and Deploying LiveCycle ES for WebSphere
SQL Server JMS validation
41
➤ To create a user:
1. In the navigation tree, click User and Groups > Manage Users, and then click Create.
2. Click Group Membership and click Search.
3. Select the group name lc8_jms_group that was previously created and click Close.
4. In the User ID box, type [authentication for JAAS name].
5. Add a first and last name in the boxes provided.
6. Type the [JAAS authentication name] as the password, and then click create.
➤ To associate security:
1. In the navigation tree, click Resources > JMS > Activation specifications.
2. Click one of the activation specifications.
3. Under Additional, in the Authentication Alias list, select the JMS authentication alias that was created
in “To configure J2C authentication:” on page 40.
4. Click OK or Apply.
5. Click Save directly to master configuration.
6. Repeat steps 1 to 5 for all activation specifications.
➤ To assign group privileges to the IDP_JMS Bus:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS Bus.
2. Under Additional Properties, click Security.
3. Under Additional Properties, click Users and groups in the bus connector role.
4. In Bus Connector Role group, use the default or select Group name and type the group name created
in “To configure J2C authentication:” on page 40.
5. Click OK or Apply.
6. Click Save directly to master configuration.
SQL Server JMS validation
Note: Validation is required only for Microsoft SQL Server.
The SQL Server JMS setup requires additional verification. This is also required if the JMS/LCM verification
fails.
➤ 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.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Manually Configuring WebSphere
Restart WebSphere
42
2. Under Topology, click Messaging Engines. When working, it should display a green arrow. The status
for the bus is likely 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 at www.adobe.com/go/learn_lc_prepareInstall.
5. Click Save directly to master configuration.
6. Delete any tables that begin with SIB to ensure there are no conflicts with old bus configurations.
7. Restart WebSphere and retry step 1 to ensure that the bus is running.
Restart WebSphere
Restart your WebSphere Application Server for all configuration changes to take affect.
Run LiveCycle Configuration Manager validation
Run LiveCycle Configuration Manager and select Application Server Configuration Validation to ensure
that no issues are reported with your WebSphere Application Server configuration. You must address any
issues before continuing with your LiveCycle ES installation.
Next step
You must now deploy the LiveCycle ES EAR files to the application server. (See “Manually Deploying
WebSphere” on page 43.)
5
Manually Deploying WebSphere
This chapter describes how to deploy your LiveCycle ES solution components to WebSphere:
●
“About deploying LiveCycle ES solution components” on page 43
●
“Deploying to WebSphere” on page 44
●
“Starting the application” on page 44
About deploying LiveCycle ES solution components
Before you deploy LiveCycle ES, ensure that you have performed these tasks:
●
Installed the required software and files, and know the location of the directories you will be working
with. If you have not completed this task, see Preparing to Install LiveCycle ES, at
http://www.adobe.com/go/learn_lc_prepareInstall.
●
Run LiveCycle Configuration Manager to configure and assemble LiveCycle ES solution components
according to your system and application server requirements. If you need 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, you must initialize LiveCycle ES 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 7.)
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
After LiveCycle ES is configured using LiveCycle Configuration Manager (required), these files are located
in the [LiveCycleES root]/configurationManager/export/ directory.
43
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Manually Deploying WebSphere
Deploying to WebSphere
44
Deploying to WebSphere
You 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, you must start the application server on your computer. After deploying
the required components, you must stop and restart the application server before starting 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.
3. Click Browse and navigate to one of the EAR files listed in “Summary of deployable components” on
page 43, select the EAR file, and then click OK.
4. Select Show me all installation options and parameters, and then click Next.
5. Select Generate Default Bindings and click Next.
6. Select the last step in the left column of the right pane titled Summary and click Finish.
7. When the EAR file has installed successfully, in the Messages box, click Save directly to Master
Configuration.
8. Repeat these steps for each of the EAR files listed in “Summary of deployable components” on page 43.
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.
➤ 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 “Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18.)
6
Post-Deployment Activities
This chapter describes how to verify the deployment by accessing 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 have been installed, configured, and deployed to your application
server:
●
“Configuring Acrobat 8.1 for PDF Generator ES” on page 45
●
“Final setup for LiveCycle Rights Management ES” on page 46
●
“Verifying the deployment and accessing LiveCycle Administration Console” on page 46
●
“Accessing solution component web applications” on page 47
●
“Accessing User Management” on page 48
●
“Configuring LiveCycle ES to access LDAP” on page 49
●
“Setting PDF Generator ES Watched Folder performance parameters” on page 49
●
“Configuring the Connector for EMC Documentum service” on page 51
●
“Configuring the Connector for IBM FileNet service” on page 54
●
“Uninstalling LiveCycle ES” on page 57
After you have configured the settings in this chapter, for additional information about configuring your
LiveCycle ES environment for development and production, see Administering LiveCycle ES at
help.adobe.com/en_US/livecycle/es/admin_guide.pdf.
Configuring Acrobat 8.1 for PDF Generator ES
Note: This functionality is only supported on the Windows platform.
If you did not choose to install Acrobat 8.1 using the LiveCycle ES installer, the following procedure needs
to be completed to set up Acrobat 8.1 for use with PDF Generator ES.
➤ To configure Acrobat 8.1 for use with PDF Generator ES:
1. If a previous version (8.0 or earlier) of Acrobat is installed, uninstall it using Add or Remove Programs in
the Windows Control Panel.
2. Navigate to one of the following folders on the LiveCycle ES installation media:
●
additional\acrobat\efg\
●
additional\acrobat\jpn\
3. Install Acrobat 8.1 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]
45
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Final setup for LiveCycle Rights Management ES
46
➤ To validate the Acrobat 8.1 installation:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat.
2. If the PDF file opens successfully, Acrobat 8.1 is installed correctly. If the PDF fails to open correctly,
uninstall Acrobat and reinstall it.
Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after Acrobat installation is
complete, and disable the automatic updates for Acrobat.
Set the environment variable, Acrobat_PATH to point to Acrobat.exe (for example, C:\Program
Files\Adobe\Acrobat 8.0\Acrobat\Acrobat.exe.
Final setup for LiveCycle Rights Management ES
LiveCycle Rights Management ES requires the application server to be configured to use SSL. For the
configuration instructions, see Administering LiveCycle ES at
help.adobe.com/en_US/livecycle/es/admin_guide.pdf.
Verifying the deployment and accessing LiveCycle Administration
Console
You can verify the deployment by logging in to LiveCycle Administration Console. If you cannot log in,
LiveCycle ES is running on the application server and the default user has been 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
that let you 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
Console also provides access to Archive Administration, which administrators use for managing archives
and deploying services to a production environment.
The default user name and password for logging in to LiveCycle Administration Console is administrator
and password. After you log in the first time, access User Management and change the password.
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 Archive Administration Help (available
from the Help menu of the LiveCycle Administration Console window).
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Viewing the log files
47
➤ 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 field, type administrator and, in the Password field, type password.
3. After logging in, you can 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
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 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
Accessing solution component web applications
After LiveCycle ES is deployed, you can access the web applications associated with the following solution
components:
●
LiveCycle Reader Extensions ES
●
LiveCycle Workspace ES
●
LiveCycle Rights Management ES
After accessing the web applications 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. For
information, see User Management Help at www.adobe.com/go/learn_lc_adminUM.
➤ To access the Reader Extensions ES web application:
Note: You must apply a Reader Extension credential and apply the user roles for a new user. For more
information, see the SSL Configuration chapter in Administrating 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
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Accessing Rights Management ES:
48
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 role “Reader Extensions Web Application”.
➤ 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
Accessing Rights Management ES:
You must create a user with the role “RM end user console” in User Management and log in to the
Rights Management ES administrator or end user applications using the login information 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 using the LiveCycle ES Administrative UI.
➤ To access the Rights Management ES administration web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/adminui
Accessing User Management
User Management allows administrators to 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, LiveCycle Process Management ES, and LiveCycle Forms ES.
➤ To access User Management:
1. Log in to LiveCycle Administration Console.
2. From the home page of LiveCycle Administration Console, click Settings.
3. On the Settings page, click 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.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Configuring LiveCycle ES to access LDAP
49
Configuring LiveCycle ES to access LDAP
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. Type http://[host name]:[port]/adminui in the URL line of a web browser and log in. (See
“Accessing LiveCycle Administration Console” on page 46.)
2. Click Settings > User Management > Domain Management and click New Enterprise Domain.
3. In the ID box, type a unique identifier for the domain.
4. In the Name box, type a descriptive name for the domain.
5. Click Add Authentication and, in the Authentication Provider list, select LDAP.
6. Click OK.
7. Click Add Directory, and under Profile Name, select a name for your LDAP profile.
8. Click Next.
9. Specify values in the Server, Port, SSL, and Binding boxes as required. For details on the settin.gs, see
Directory settings in User Management Help at www.adobe.com/go/learn_lc_adminUM.
10. Under Populate Page With, select a directory settings option, such as Default Sun ONE values.
11. Click Next and configure the User Settings as required. For details about the settings, see Directory
settings in User Management Help.
12. Click Next configure the Group Settings as required. For details about the settings, see Directory
settings in User Management Help.
13. (Optional) Test your configuration:
●
Click Test.
●
In the Test Directory pane, in the Find box, enter an object name and, in the using box, select the
object’s type, such as Login ID.
●
Click Test. If successful, your object’s details will be displayed, and then click Back.
14. Click Finish to exit the New Directory page, and click OK again to exit.
Setting PDF Generator ES Watched Folder performance
parameters
To avoid java.io.IOException error messages indicating that not enough disk space is available to perform
PDF conversions using a watched folder, you can modify the settings for PDF Generator ES in LiveCycle
Administration Console.
You must also ensure that the maximum transaction time-out and ORB service values have the proper
values (see “Configuring WebSphere time-out settings” on page 24).
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Configuring FIPS mode
50
➤ To set performance parameters for PDF Generator ES:
1. Log in to LiveCycle Administration Console and click Services > Archive Administration > Service
Management > PDFGConfigService.
2. Set the following values:
●
PDFG Cleanup Scan Seconds: 1800
●
Job Expiration Seconds: 6000
3. Increase Server conversion timeout from the default of 270 to a higher value, such as 450.
4. Click Save.
5. Restart the server.
Configuring 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 using LiveCycle Configuration Manager during the LiveCycle ES
configuration or if you enabled it but want to turn it off, you can change this setting through LiveCycle
Administration Console.
To modify FIPS mode, you must restart the server.
FIPS mode does not support encryption algorithms used in Acrobat versions earlier than 7.0. If FIPS mode
is enabled and you use the Encryption service to encrypt the PDF using a password with a compatibility
level set to Acrobat 5, the encryption attempt will fail with an error.
In general, when FIPS is enabled, the Assembler service will 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 Document Description XML (DDX)
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. Browse to Settings > Core System > Configurations > Core Configurations.
3. Select Enable FIPS to enable FIPS mode or deselect it to disable it.
4. Click OK.
5. 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).
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Configuring HTML digital signature
51
Configuring HTML digital signature
To use the HTML digital signature feature of LiveCycle Forms ES, you must 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 ES Administrator Console.
3. Select Service > Livecycle Forms ES.
4. Select HTML Digital Signature Enabled.
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, you must create it. Add
a new system property that provides the location of the Documentum Content Server config folder
and the following Documentum Foundation Classes JAR files:
●
dfc.jar
●
dfcbase.jar
The new system property should take this form:
[component id]_[component version].ext=[JAR files and/or folders]
For example, using default Content Server and Documentum Foundation Classes installations, you add
the following system property on a new line, with no line breaks, and end the line with a carriage
return, to the file:
com.adobe.livecycle.ConnectorforEMCDocumentum_8.0.3174.1.156395.1.ext
=C:/Documentum/Config,C:/Program Files/Documentum/Shared/dfc.jar,
C:/Program Files/Documentum/Shared/dfcbase.jar
You can determine the version of the component by logging in to the LiveCycle Administration
Console and navigating to Services > Archive Administration > Service Management, and then
searching for the component. The version number is listed in the Component Version column.
2. If WebSphere Application Server is not currently running, start the server. Otherwise, stop and then
restart the server.
3. Open a web browser and enter this URL:
http://localhost:9080/adminui (local deployment using the default port)
4. Log in using the default user name and password:
User name: administrator
Password: password
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Configuring the Connector for EMC Documentum service
52
5. Navigate to Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings.
6. Type all of the required Documentum repository information. To use Documentum as your repository
provider, in the Repository Service Provider Information area, select EMC Documentum Repository
Provider, and then click Save. For more information about the Documentum repository information,
see Documentum Administration Help at www.adobe.com/go/learn_lc_adminDocumentum.
7. (Optional) Navigate to Repository Credentials Settings, click Add, specify the Docbase information,
and then click Save. For more information about the Documentum repository information, see
Documentum Administration Help at www.adobe.com/go/learn_lc_adminDocumentum.
8. Navigate to Services > Archive Administration > Service Management, select the following services,
and then click Start:
●
EMCDocumentumAuthProviderService
●
EMCDocumentumContentRepositoryConnector
●
EMCDocumentumRepositoryProvider
If any of the services do not start correctly, check the settings entered in step 6.
9. 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.
●
To use the LiveCycle ES repository, log in to Workbench ES using the LiveCycle ES super
administrator credentials (by default, Administrator and password). You have now completed the
required steps for this procedure. The credentials provided in step 6 are used for accessing the
default repository in this case and use the default LiveCycle ES authorization service.
10. Restart WebSphere Application Server.
11. Log in to the LiveCycle Administration Console, navigate to Settings > User Management > Domain
Management, and click New Enterprise Domain.
12. 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.
13. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom, and select EMCDocumentumAuthProvider.
●
Click OK.
14. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP.
●
Click OK.
15. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
●
Creating the XDP MIME format in your Documentum repository
53
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.
For details about the settings, see User Management Help at
www.adobe.com/go/learn_lc_adminUM.
●
Configure the user settings, click Next, configure group settings, as required, and then click Next.
For details about the settings, see User Management Help at
www.adobe.com/go/learn_lc_adminUM.
16. Click OK to exit the Add Directory page, and click OK again.
17. 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.
To verify the status of the synchronization, click Refresh and view the status in the Current Sync State
column.
18. Click Settings > User Management > Users and Groups.
19. Search for users that were synchronized from LDAP. Select one or more users, click Assign Role, select
one or more LiveCycle ES roles, and then click OK. Click OK a second time to confirm the role
assignment. Repeat this step for all users you assign roles to. For more information about assigning
LiveCycle ES roles, see User Management Help at www.adobe.com/go/learn_lc_adminUM.
20. Start Workbench ES and log in 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 6.
After you configure your Connector for EMC Documentum service, you should see Administering
LiveCycle ES at www.adobe.com/go/learn_lc_administration for information on correctly 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 XDP format is created by the
Connector for EMC Documentum service 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.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Configuring the Connector for IBM FileNet service
54
3. Select File > New > Format.
4. Type the following information into the corresponding fields:
Name: xdp
Default File Extension: xdp
Mime Type: application/xdp
5. Repeat steps 1 - 4 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: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 EMC Documentum > Configuration Settings.
4. In the Documentum Principal Credentials Information area, update the following information and then
click Save:
User Name: [Documentum Administrator user name]
Password: [Documentum Administrator password]
5. Click Repository Credentials Settings.
6. Select a repository from the list or, if none exist, click Add.
7. Type the following information:
Repository Name: [Repository Name]
Repository Credentials User Name: [Documentum Administrator user name]
Repository Credentials Password: [Documentum Administrator password]
8. Click Save.
9. Repeat steps 7 - 9 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, complete the
following procedure to configure the service to connect to the FileNet object store.
➤ To configure Connector for IBM FileNet:
1. Locate the adobe-component-ext.properties file in the
[WAS HOME]/AppsServer/profiles/[profile name] folder. If the file does not exist, you must create it. Add
a new system property that provides the location of the following Application Engine JAR files:
●
activation.jar
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
●
javaapi.jar
●
log4j-1.2.8.jar
●
mailapi.jar
●
p8cjares.jar
●
soap.jar
●
xercesimpl.jar
●
xml-apis.jar
Configuring the Connector for IBM FileNet service
55
The new system property should take this form:
[component id]_[component version].ext=[JAR files and/or folders]
For example, using a default Application Engine installation, add the following system property on a
new line, with no line breaks, and end the line with a carriage return, to the file:
com.adobe.livecycle.ConnectorforIBMFileNet_8.0.3174.1.156395.1.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
You can determine the version of the component by logging in to LiveCycle Administration Console
and navigating to Services > Archive Administration > Service Management, and then searching
for the component. The version number is listed in the Component Version column.
2. If WebSphere Application Server is not currently running, start the server. Otherwise, stop and then
restart the server.
3. Open a web browser and enter this URL:
http://localhost:9080/adminui (local deployment using the default port)
4. Log in using the default user name and password:
User name: administrator
Password: password
5. Navigate to Services > LiveCycle ES Connector for IBM FileNet > Configuration Settings.
6. Type all of the required FileNet repository information and, in the Repository Service Provider
Information area, select IBM FileNet Repository Provider, and then click Save. For more information
about the FileNet repository information, see FileNet Administration Help at
http://www.adobe.com/go/learn_lc_adminFileNet.
Note: The credentials you provide during this step are validated when the IBM FileNet repository
services are started in the next step. If the credentials are invalid, an error is thrown and the
services will fail to start.
7. Navigate to Services > Archive Administration > Service Management, click the following services,
and then click Start:
●
IBMFileNetAuthProviderService
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
●
IBMFileNetContentRepositoryConnector
●
IBMFileNetRepositoryProvider
Configuring the Connector for IBM FileNet service
56
If any of the services do not start correctly, check the settings entered in step 6.
8. 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 using FileNet credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES using the LiveCycle ES super
administrator credentials (by default, Administrator and password). You have now completed
the required steps for this procedure. The credentials provided in step 6 use the default LiveCycle ES
authorization service for accessing the default repository in this case.
9. Restart WebSphere Application Server.
10. Log in to the LiveCycle Administration Console, navigate to Settings > User Management > Domain
Management, and click New Enterprise Domain.
11. 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.
12. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom, and select IBMFileNetAuthProviderService.
●
Click OK.
13. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP.
●
Click OK.
14. 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.
For details about the settings, see User Management Help at
http://www.adobe.com/go/learn_lc_adminUM.
●
Configure the user settings, click Next, configure group settings, as required, and then click Next.
For details about the settings, see User Management Help at
http://www.adobe.com/go/learn_lc_adminUM.
15. Click OK to exit the Add Directory page, and click OK again.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
Uninstalling LiveCycle ES
57
16. 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.
To verify the status of the synchronization, click Refresh and view the status in the Current Sync State
column.
17. Click Settings > User Management > Users and Groups.
18. Search for users that were synchronized from LDAP. Select one or more users, click Assign Role, select
one or more LiveCycle ES roles, and then 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 about
assigning LiveCycle ES roles, see User Management Help at
http://www.adobe.com/go/learn_lc_adminUM.
19. 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 the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 6.
After you configure your Connector for IBM FileNet service, you should see Administering LiveCycle ES at
www.adobe.com/go/learn_lc_administration for information on correctly configuring Workbench ES
functions properly with your FileNet repository.
Uninstalling LiveCycle ES
The uninstall program located in the [LivecycleES root] directory does not remove any files that you
deployed to your application server.
Caution: By running the uninstall program, all of the contents within the product installation directory are
subject to removal without further warning. Before proceeding, 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 8.1 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).
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebSphere
●
Uninstalling LiveCycle ES
(AIX) Perform these tasks:
●
Set the JAVA_HOME and PATH so that they use the IBM JDK from WebSphere.
●
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.
58
7
Manually Configuring BAM Server for LiveCycle ES
This section describes the tasks that must be performed to manually install and configure
LiveCycle Business Activity Monitoring ES for use with LiveCycle ES:
●
“Configuring WebSphere for BAM Server” on page 59
●
“Creating and configuring the BAM Server metadata database” on page 60
●
“Configuring WebSphere parameters” on page 65
●
“Configuring Process Management ES for BAM Server” on page 65
●
“Deploying BAM Server to WebSphere” on page 66
●
“Configuring LDAP settings for BAM Server” on page 69
●
“Using the BAM Dashboard” on page 74
●
“Uninstalling Business Activity Monitoring ES” on page 75
These instructions use the following naming conventions for common file paths.
Name
Description
Default value
[appserver root]
The home directory of the
application server for
Business Activity Monitoring ES.
WebSphere on Windows: C:\Program
Files\IBM\WebSphere\AppServer
WebSphere on Linux and Solaris:
/opt/IBM/WebSphere/AppServer
WebSphere on AIX:
/usr/IBM/WebSphere/AppServer
[LiveCycleES root]
The location where the LiveCycle ES Windows: C:\Adobe\LiveCycle8
services are installed
Linux and UNIX: /opt/adobe/livecycle8
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.
Configuring WebSphere for BAM Server
If you are installing LiveCycle Process Management ES and you are using Business Activity Monitoring ES,
you must manually configure WebSphere so that BAM Server runs correctly.
You must perform the following tasks:
●
If you have not already done so, create an application server for running BAM Server.
●
If you have not already done so, create the BAM Server database
●
Configure the connection to the BAM Server metadata database.
●
Set application server parameters.
59
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Creating an application server instance for BAM Server
60
Creating an application server instance for BAM Server
You will need to create an application server instance for BAM Server.
➤ To create a new WebSphere instance for BAM Server:
1. Open a command prompt and navigate to [Appserver root]/bin.
2. Run the wsadmin script:
●
(Windows) Type wsadmin.bat
●
(Linux) Type wsadmin.sh
3. Type the following commands:
wsadmin>$AdminTask createApplicationServer [nodeName] {-name [BAMServer]}
wsadmin>$AdminConfig save
wsadmin>exit
Creating a virtual host alias
You need to create a host alias for the port that provides access to the BAM Server service. After you create
the alias, you need to use Administrator[LiveCycle Administration Console?] to update the
Process Management ES settings with the new URL for BAM Server.
➤ To create a virtual host alias:
1. In the WebSphere Administrative Console navigation tree, click Environment > Virtual Hosts.
2. Click default host.
3. Under Additional Properties, click Host Aliases.
4. Click New and specify the following values for the properties:
●
Host Name: *
●
Port: 9091
5. Click OK, then click Save your changes to the master configuration.
Creating and configuring the BAM Server metadata database
You must create a Business Activity Monitoring ES metadata database to store the definitions of the
process metrics that BAM Server monitors, as well as the details of any alerts and object run-time data that
need to be persisted to disk.
Because Business Activity Monitoring ES metadata can grow quite large, you must allocate at least 50 MB
for the BAM Server metadata database. For production deployments, allocate at least 200 MB.
BAM Server can require specific settings for some aspects of the Business Activity Monitoring ES metadata
database configuration. The settings depend on the type of application server that is hosting BAM Server
and the type of database server used to store the Business Activity Monitoring ES metadata.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
User accounts
61
User accounts
You must also create a user account that BAM Server can use to connect to the
Business Activity Monitoring ES metadata database. The user account must have create, modify, and
update privileges on the database.
For Oracle, you must also create a user account that BAM Server can use to connect to the metadata
database. The user account must have create, modify, and update privileges on the database. Assign the
roles CONNECT and RESOURCE, and the ACCESS_ANY_WORKSPACE, CREATE_ANY_VIEW and
UNLIMITED_TABLESPACE system privileges. The database user account must be associated with a
tablespace that you create specifically for Business Activity Monitoring ES metadata.
Configuring your database environment
If you are using DB2 as the Business Activity Monitoring ES metadata database, you must create an
environment variable that contains the name of the associated DB2 instance. You also must include the
path to the DB2 shared libraries in the library path variable.
The following examples show commands for configuring the environment variables. Use the command
that corresponds with your operating system. You may need to modify the command according to the
location where you installed DB2.
Example: Commands to configure environment variables on Windows
The following commands apply to a DB2 instance named DB2, with DB2 library files installed in
C:\SQLLIB\BIN:
set DB2INSTANCE=DB2
set PATH=C:\SQLLIB\BIN;%PATH%
Example: Commands to configure environment variables on Solaris
The following commands apply to a DB2 instance named db2fs, with DB2 library files installed in
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LD_LIBRARY_PATH=/opt/IBM/db2/V8.1/lib:${LD_LIBRARY_PATH}
Example: Commands to configure environment variables on AIX
The following commands apply to a DB2 instance named db2f.
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LIBPATH=/opt/IBM/db2/V8.1/lib:${LIBPATH}
Creating a JAAS authentication alias for the BAM Server metadata database
You must create a JAAS authentication alias for a user account that can access the BAM Server metadata
database.
➤ To create a JAAS authentication alias for the BAM Server metadata database on DB2:
1. Start WebSphere Application Server.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring your database environment
62
2. In the WebSphere Administrative Console navigation tree, click Security > Secure administration,
applications, and infrastructure.
3. In the right pane, under Authentication, click Java Authentication and Authorization Service > J2C
authentication data.
4. On the next screen, in the right pane, click New.
5. Specify values for the following properties and then click OK:
Alias: A name for the alias. Type BAMDB2
User ID: The user name for the user account that can access the BAM Server metadata database on
DB2.
Password: The password associated with the specified User ID.
Description: (Optional) A description of the alias.
6. Save your changes to the master configuration.
Creating the JDBC provider for the BAM Server metadata database
You must create the JDBC provider that you use to create the connection to the BAM Server metadata
database.
➤ To create the JDBC provider:
1. Start WebSphere Application Server.
2. In the WebSphere Administrative Console navigation tree, click Resources > JDBC > JDBC Providers.
3. In the JDBC providers area, select the scope you created for the LiveCycle ES server, then click New.
4. (Oracle) Select the following values on the Step 1 screen:
●
Database type: Oracle
●
Provider type: Oracle JDBC Driver
●
Implementation type: Connection pool data source
5. (DB2) Select the following values on the Step 1 screen:
●
Database type: DB2
●
Provider type: DB2 Universal JDBC Driver Provider
●
Implementation type: Connection pool data source
6. (SQL Server) Select the following values on the Step 1 screen:
●
Database type: SQL Server
●
Provider type: WebSphere embedded Connect JDBC driver for MS SQL Server
●
Implementation type: Connection pool data source
7. Click Next.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Creating the data source for the BAM Server metadata database
63
8. In the Classpath box, add the file paths after any other entries in the box according to the type of
database you are using to store BAM Server metadata. If you need to add more than one class path,
ensure that you include a carriage return after each path:
●
Oracle:
{WAS_INSTALL_ROOT}/db_driver/ojdbc14.jar
●
DB2:
{WAS_INSTALL_ROOT}/db_driver/db2jcc.jar
{WAS_INSTALL_ROOT}/db_driver/db2jcc_license_cu.jar
●
SQL Server - accept the default native drivers:
{WAS_INSTALL_ROOT}/db_driver/sqlserver.jar
{WAS_INSTALL_ROOT}/db_driver/base.jar
{WAS_INSTALL_ROOT}/db_driver/util.jar
Note: Ensure that you do not delete any existing entries in the Classpath box.
9. Click Next in the Step 2 screen.
10. Click Finish in the Step 3 screen.
11. Save your changes to the Master Configuration.
Creating the data source for the BAM Server metadata database
You must create a data source so that BAM Server can connect to the BAM Server metadata database.
➤ To create the DB2 JDBC data source:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and select your provider.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 screen, set the following configurations and then click Next:
Data source name: com.celequest.metadata.metaDatasource
JNDI name: com.celequest.metadata.metaDatasource
Component-managed authentication: Select the authentication alias created for this data source
which was created in “Creating a JAAS authentication alias for the BAM Server metadata database”
on page 61.
4. In the Step 2 screen, type the database name and server name of the BAM Server database, deselect
Use this data source in container managed persistence (CMP) and then click Next.
5. On the Step 3 screen, click Finish.
6. Save your changes to the Master Configuration.
➤ To create the Oracle data source:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and select your provider.
2. Under Additional Properties, click Data sources and then click New.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Creating the data source for the BAM Server metadata database
64
3. In the Step 1 screen, set the following configurations and then click Next:
Data source name: com.celequest.metadata.metaDatasource
JNDI name: com.celequest.metadata.metaDatasource
Component-managed authentication: Select the authentication alias created for this data source.
4. In the Step 2 screen, select the existing JDBC provider and, in the list, select the JDBC provider you
created in “Creating the JDBC provider for the BAM Server metadata database” on page 62.
5. (Oracle 10g) In Datasource Helper Class Name, type this text:
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
6. Deselect Container managed persistence and then click Next.
7. In the Step 3 screen, type the following text in the URL box:
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.
8. Click Next and, on the Summary screen, click Finish.
9. Save the master configuration by clicking Save, and then click Save to the master configuration.
➤ To create the SQL Server 2005 data source:
1. In the navigation tree, click Resources > JDBC > JDBC Providers and click your provider.
2. Under Additional Properties, click Data sources and then click New.
3. In the Step 1 screen, set the following configurations and then click Next:
Data source name: com.celequest.metadata.metaDatasource
JNDI name: com.celequest.metadata.metaDatasource
Component-managed authentication: Select the authentication alias created for this data source.
4. In the Step 2 screen, type the database name and server name of the BAM Server database, deselect
Use this data source in container managed persistence, and then click Next.
5. In the Step 3 screen, click Finish.
6. Save the master configuration by clicking Save, and then clicking Save again.
Testing the database connection
You should test the JDBC provider configuration using the test connection feature in WebSphere.
➤ To test the database connection:
1. In the WebSphere Administrative Console navigation tree, click Resources > JDBC > JDBC Providers,
then click your provider.
2. Under Additional Properties, click Data sources, and then click
com.celequest.metadata.metaDatasource.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring WebSphere parameters
65
3. Click Test Connection.
The Message box at the top of the screen displays the results of the test. If the test fails, use the
WebSphere error reporting features to locate the cause of the problem.
Configuring WebSphere parameters
You must configure several WebSphere Application Server parameters to support BAM Server.
➤ To set application server parameters:
1. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and
click the name of the application server on which you will deploy BAM Server.
2. Click the Configuration tab and, under Server Infrastructure, click Java and Process Management >
Process Definition.
3. On the Process Definition screen, under Additional Properties, click Java Virtual Machine.
4. On the Java Virtual Machine configuration screen, specify values in the Initial Heap and Maximum
Heap boxes.
These settings depend on your system capabilities and you should set them as high as possible. The
default values are 256 and 1024.
5. Type the following text in the Generic JVM Arguments box to configure UTF-8 support:
-Dfile.encoding=utf8
6. Click Apply.
7. Click OK and save your changes to the Master Configuration.
8. Return to the main server screen by clicking the server name at the top of the screen and under
Container Settings, expand Container Services and then click Transaction Service.
9. On the Transaction Service screen, in the Total transaction lifetime timeout box, type 600.
10. Click OK to return to the Custom Properties screen.
11. Save your changes to the Master Configuration.
12. Restart WebSphere.
Configuring Process Management ES for BAM Server
You can configure Process Management ES to connect to BAM Server using LiveCycle Administration
Console. You must specify the server on which the LiveCycle ES server and BAM Server are running and the
user account information with which to access BAM Server.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Deploying BAM Server to WebSphere
66
➤ To configure Process Management ES for BAM Server:
1. Log in to LiveCycle Administration Console.
2. Click Services > LiveCycle Process Management ES > Server Settings > BAM Configuration
Settings.
3. Type values for the following properties:
BAM Host: The host name or IP address of the server on which BAM Server is running. The default
value is localhost.
BAM Port: The service port of the application server on which BAM Server is running. The default
value is 8080.
LiveCycle Server Host: The host name or IP address of the server on which the LiveCycle ES server
is running. The default value is localhost.
LiveCycle Server SOAP Port: The service port of the application server on which the LiveCycle ES
server is running. The default value is 8080.
User Name: (Optional) The user name of the administrator user account that
Process Management ES uses to access BAM Server. The default user name is system.
Note: If you specify the user name for a different user account, you must ensure that the user has
complete administrative privileges for BAM Server. For information about administering
BAM Server user accounts, see Using BAM Workbench.
Password: (Optional) A valid password for the user name specified above. The default password is
manager.
4. Click Save and restart the LiveCycle ES server.
Deploying BAM Server to WebSphere
You must first configure the BAM Server EAR file (CAS_Adobe.ear) using LiveCycle Configuration Manager,
then deploy the configured BAM Server EAR file to your LiveCycle ES application server. See “To perform
configuration or deployment tasks using LiveCycle Configuration Manager:” on page 19 to configure the
BAM Server EAR file.
➤ To deploy the BAM Server EAR file:
1. Start WebSphere Application Server and the BAM Server application server instance.
2. In the navigation tree, click Applications > Install New Application.
3. Click Browse, select the CAS_Adobe.ear file, and then click OK.
4. Select Show me all installation options and parameters, and then click Next.
5. Select Generate Default Bindings, and then click Next.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Deploying BAM Server to WebSphere
67
6. In Map modules to servers, perform these tasks:
●
Select the module Celequest BAM Suite.
●
Under Clusters and Servers, select the server for LiveCycle ES (by default, server1), and then click
Apply.
●
Click Next on all the subsequent screens.
7. Accept the default values by clicking Next until Summary screen appears, and then click Finish.
Note: If you receive a Resource Warning message, you can safely ignore it.
8. Save your changes to the Master Configuration.
9. Restart LiveCycle ES.
➤ To configure the BAM Server system settings:
1. Start BAM Workbench by typing http://[host name]:[BAM port]/bam/workbench in the URL
line of a web browser.
2. On the login page, enter the system manager user name and password. These values are the defaults:
Username: system
Password: manager
3. Navigate to Workbench > Administration console > System settings.
4. In the Configure list, select Checkpoint Configuration.
5. Select Enable Checkpoint.
6. In the Recovery Log Directory field, type the path to the BAM logging directory; for example, type the
following directory:
[appserver root]/profiles/AppSrv01/logs/server1
7. In the Configure list, select Logging.
8. In the Logging Directory field, type the path to the BAM logging directory; for example, type the
following directory:
[appserver root]/profiles/AppSrv01/logs/server1
9. In the Configure list, select System Control and ensure that Recover State on Restart is selected.
10. In the Configure list, select SMTP Configuration and enter the following parameters:
Host: The URL to the SMTP host.
Address: The IP address for the SMTP host.
User: The account user name.
Password: The account user password.
11. Click OK.
12. Restart the LiveCycle ES server and BAM Server.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Deploying BAM Server to WebSphere
68
➤ To import the LiveCycle ES metadata definitions:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. On the login page, type the system manager user name and password. These values are the defaults:
Username: system
Password: manager
3. Click the Administration Console tab and click Import/Export.
4. Select Import Metadata from a JAR file (upload) and enter the full path to the location of the
Business Activity Monitoring ES metadata template that is appropriate for the type of database that
you are using for the LiveCycle ES database:
●
(DB2) adobeimport_DB2.jar
●
(Oracle) adobeimport_Oracle.jar
●
(SQL Server) adobeimport_SQLServer.jar
These files are installed in the [LiveCycle root]/deploy directory.
5. Click Upload and then click OK to import the file.
➤ (Oracle) To update the JDBC Query:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. On the login page, type the system manager user name and password. These values are the defaults:
Username: system
Password: manager
3. Click the Application Workbench tab and click events to see a list of events.
4. Double-click Adobe event and then click Edit This Event.
5. In the JDBC Query box, type in the following code:
select uuid,major_version,minor_version,"descriptor",state,service_uuid,
component_oid,update_time,create_time from tb_sc_service_configuration
where monitor='1'
6. Click Resubmit Query.
7. Click the Polling tab and, in the Incrementing Field list, select update_time. Notice the Initial Value
(such as 2000-01-01 00:00:00); you may need this info later.
8. Click Save this Event.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring LDAP settings for BAM Server
69
Configuring LDAP settings for BAM Server
In addition to manually creating users and user permissions, Business Activity Monitoring ES lets you
import user information from supported LDAP providers. You can schedule automatic synchronizations or
perform manual synchronizations with the LDAP server to automatically update the existing users and
roles.
When synchronizing with the LDAP server, the user base DN, login identification and password, full name,
description, and email address properties are cached in the BAM Server metadata database.
When BAM Server imports users from the LDAP server, LDAP groups are converted to
Business Activity Monitoring ES roles. Users are assigned roles according to the group they belong to in
LDAP. For more information, see “Limitations of BAM Server LDAP connectivity” on page 69.
Note: BAM Server integrates with any LDAP provider that supports the LDAP version 3 protocol.
Limitations of BAM Server LDAP connectivity
The following limitations apply to the BAM Server connectivity with the LDAP server:
●
You can configure a connection to only one LDAP server.
●
BAM Server creates roles based on groups that are defined on the LDAP server. When BAM Server
encounters a group for which a role is not yet created, it creates the role and assigns it a set of zero
permissions. You can later modify the permissions as required. (See “Configuring LDAP role mapping”
on page 72.)
●
If BAM Server imports a user and the user does not belong to a group to which a
Business Activity Monitoring ES role corresponds, the user is created but remains unassigned to any
roles.
●
You cannot change the role that a user is assigned to if the user is imported from the LDAP server. Role
assignments for imported users can be accomplished by making changes to the LDAP server. However,
you can assign manually-created users to roles that are created based on LDAP groups.
Best practices for BAM Server LDAP connectivity
When setting up the BAM Server connectivity with the LDAP server, it is strongly recommended you
adhere to the following best practices:
●
If the connection to the LDAP server is not secure, you should use SSL.
●
For authentication, Simple Authentication and Security Layer (SASL) is the recommended method and
is well supported by LDAP.
●
For security reasons, the access permissions of the LDAP synchronization user should be limited to
querying the LDAP server. For more information on the synchronization user, see “Configuring
automatic LDAP synchronization” on page 70.
Caution: The password for this user is stored in the BAM Server metadata using reversible symmetric
encryption. Therefore, anyone with access to the metadata can obtain this password.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring automatic LDAP synchronization
70
Configuring automatic LDAP synchronization
You can schedule the automatic synchronization of BAM Server with the LDAP server. Synchronization
ensures that the user accounts and role definitions that BAM Server caches in the BAM Server metadata
database are up to date with the content of the LDAP server.
During synchronization, BAM Server creates new roles based on any new groups in the LDAP server and
removes existing roles based on any groups that have been removed from the LDAP server since the
previous synchronization.
Note: Roles are removed even if users that were created manually are assigned to the roles. For these
users, if the roles are removed due to synchronization, the user accounts still exist but are no longer
assigned to the roles.
➤ To configure automatic LDAP synchronization:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab and then click System Settings.
3. Click the LDAP Synchronization tab.
4. Select LDAP Enabled if it is not already selected.
5. Specify values for the following properties:
Initial Context Factory: The JNDI name through which BAM Server connects to the LDAP server.
The default value is com.sun.jndi.ldap.LdapCtxFactory. You probably do not need to
change this value.
LDAP Server: The DNS name or IP address of the LDAP server.
LDAP Port: The port on which the LDAP server is running. The default port is typically 389.
However, if you select the SSL option, the default port is typically 636. You must confirm with your
LDAP administrator which port to specify.
LDAP SSL: Select this option if the LDAP server is configured to use SSL. Selecting this option may
affect the LDAP Port setting.
LDAP Authentication: The authentication method used by the LDAP server. Select one of the
following options:
●
Simple
●
SASL (Simple Authentication and Security Layer). Select this option for Sun ONE.
●
Compare Encrypted Password
LDAP Principal DN Prefix: For the simple authentication method, the text you specify will be
inserted before the user's login name:
●
For LDAP servers that require DN login, set this to the appropriate property value followed by an
equal sign (for example, cn= or uid=).
●
For Active Directory, leave this value blank.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring LDAP user mapping
71
LDAP Principal DN Suffix: For the simple authentication method, the text you specify will be
inserted after the user's login name:
●
For LDAP servers that require DN login, set this to the appropriate chain of values; the first
character of the suffix must be a comma (","), as shown in the example:
,ou=Users,dc=domain,dc=name
●
For Active Directory, which requires a simple login with an email address, set this to an at symbol
(@) followed by the domain name that is set for Active Directory.
LDAP Synchronization User: The user that binds to the server and reads the lists of users and roles.
For security purposes, you must specify a user account that can only read the LDAP directory.
LDAP Synchronization Password: The password associated with the user specified for the LDAP
Synchronization User option.
6. Click Test Connection. The connection and the user mapping and role mapping configuration are
tested. If the connection settings are correct, a message will indicate that the connection was
successful. If you have not yet configured LDAP User Mapping and LDAP Role Mapping, the message
returns an error.
7. To set the LDAP Synchronization Schedule, use the Add Schedule, Edit Schedule, and Remove
Schedule buttons to create the schedule you want.
Note: You should set synchronization for a time when the fewest number of users are likely to be
logged in.
8. Click OK.
Configuring LDAP user mapping
You can configure the user mapping parameters that determine which users are imported and
synchronized from the LDAP server. The parameters you specify depend on the LDAP server provider that
you are using.
➤ To configure the LDAP user mapping parameters:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab, and then click System Settings.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Configuring LDAP role mapping
72
3. Click the LDAP User Mapping tab and specify values for the following parameters:
LDAP User Base DN: The root of the tree that will be searched for users, for example:
●
(Sun ONE) OU=people,DC=your domain,DC=com
●
(Active Directory) CN=Users,DC=yourdomain,DC=com
LDAP User Search Filter: The format that is appropriate for the type of LDAP server you are using.
For example, your LDAP server could have a special group for Business Activity Monitoring ES users.
This filter could then ensure that only users with this group membership are imported.
LDAP User LoginID: The login ID of the indicated provider. This value will become the user’s login
ID in Business Activity Monitoring ES.
LDAP User Full Name: Enter cn if you are using either Sun ONE or Active Directory.
LDAP User Description: Enter description if you are using either Sun ONE or Active Directory.
LDAP User PrimaryEmail: Enter userPrincipalName. This refers to the user’s email address in
the LDAP directory.
LDAP User EncryptedPassword: Enter the password associated with the specified user if you are
using either Sun ONE or Tivoli. Leave blank for Active Directory.
4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are
imported successfully.
5. Click OK.
Configuring LDAP role mapping
You can configure the role mapping parameters that determine which groups or roles are imported or
synchronized, or both. The parameters you specify depend on the LDAP server provider you are using.
➤ To configure the LDAP role mapping parameters:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab and then click System Settings.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Manually synchronizing with the LDAP server
73
3. Click the LDAP Role Mapping tab and specify values for the following parameters:
LDAP Role Base DN: The format that is appropriate for the type of LDAP server you are using:
●
(Sun ONE) OU=Groups,DC=your domain,DC=com
●
(Active Directory) CN=Users,DC=yourdomain,DC=com
LDAP Role Search Filter: The format that is appropriate for the type of LDAP server you are using:
●
(Sun ONE) (&(objectclass=groupOfUniqueNames))
●
(Active Directory) (&(objectclass=group))
LDAP Role LoginID: Enter cn if you are using either Sun ONE or Active Directory.
LDAP Role Full Name: Enter displayname if you are using either Sun ONE or Active Directory.
LDAP Role Description: Enter description if you are using either Sun ONE or Active Directory.
LDAP Role Member: The name of the multivalued property that contains role members:
●
(Sun ONE) uniqueMember
●
(Active Directory) member
LDAP Role Member is: Use one of the following options:
●
Distinguished Name if the role member properties identify users by distinguished names,
such as cn=jadmin,ou=people,dc=your domain,dc=com.
●
Login identification if the role member properties identify users by the value of the
property used as the Business Activity Monitoring ES login ID.
4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are
imported successfully.
5. Click OK.
Manually synchronizing with the LDAP server
You can manually synchronize BAM Server with the LDAP server at any time. Synchronization requests are
queued to prevent concurrent synchronizations.
➤ To manually synchronize with the LDAP server:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab and then click System Settings.
3. Click the LDAP Synchronization tab.
4. Click Synchronize Now. The time required to synchronize depends on your environment. A message
appears when the synchronization is complete.
5. Click OK.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Using the BAM Dashboard
74
Using the BAM Dashboard
When a process is activated and immediately invoked, the process instance is not registered on the
corresponding BAM Dashboard. BAM Server requires several seconds after a process is activated before it
can monitor the process for activity. After you activate a process, wait several seconds before invoking it.
If you install BAM Server after LiveCycle ES has run a process, you will have to populate BAM Dashboard.
Populating BAM Dashboard initializes BAM Server to begin polling the LiveCycle ES database. When this
process is enabled, the AdobeView can be created from the information gathered from the LiveCycle ES
database. In the case of a clean LiveCycle ES installation, the database will be empty and no view will be
created.
➤ To populate BAM Dashboard:
1. Navigate to Workbench > Application Workbench > Events.
2. Find AdobeEvent in the Events list and restart the event, select disable dependencies, and then click
enable all.
3. Select "Disable dependencies" on all the events other than the AdobeEvent and the System Events that
start with VC.
4. Select Enable Only this object during the Enabling ActivityInstanceStartedEvents.
5. Enable all ActivityInstanceCompletedEvents.
6. Select Enable Only this object during the Enabling ProcessInstanceStartedEvents.
7. Enable all ProcessInstanceCompletedEvent, all QueueEvent, all TaskCompletedEvent, all
TaskReassignedEvent, and all TaskSpentTimeOnQueueEvent.
8. Navigate to Workbench > Application Workbench > Views.
9. Find AdobeView in the Views list and restart the view.
10. Click disable dependencies and then click enable all. There will be a delay while the list of existing
orchestrations is populated.
When BAM Dashboard has been populated, you can log in to BAM Dashboard to view the LiveCycle ES
processes.
➤ To log in to BAM Dashboard:
1. Type the URL to the dashboard in a web browser. For example, type this URL:
http://[host name]:[port]/bam/login/dashboard.htm
2. Log in as an administrator. The default administrator account for BAM Server uses the following
credentials:
Username: system
Password: manager
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Additional documentation
75
Additional documentation
You can access additional information on LiveCycle Business Activity Monitor here:
●
Business Activity Monitor - Dashboard at www.adobe.com/go/learn_lc_bamdashboard
●
Business Activity Monitor - Server at www.adobe.com/go/learn_lc_bamserver
●
Business Activity Monitor - Workbench at www.adobe.com/go/learn_lc_bamworkbench
Uninstalling Business Activity Monitoring ES
You must uninstall BAM Server completely before attempting to reinstall.
➤ To uninstall BAM Server:
1. Undeploy the BAM Server EAR file using WebSphere Administrative Console.
2. Delete all of the files from the recovery log directory and logging directory that have names similar to
the following patterns:
●
filestore*.dat
●
DEFAULTRECOVERYLOGGER_*
●
chkpoint*
3. Review the contents of the [appserver root]\bin folder and, if any chkpoint* files exist, delete them.
4. Use your database management tools to drop the database tables that store the BAM Server metadata.
Alternatively, you may want to create a new BAM Server metadata database.
8
Advanced Production Configuration
This section describes advanced tuning for LiveCycle Output ES, LiveCycle Forms ES and
LiveCycle PDF Generator ES. This section should only be completed on a production system by an
advanced application server administrator.
LiveCycle Output ES and LiveCycle Forms ES
The current default value for PoolMax is 4. The actual value to set would depend upon the hardware
configuration and the expected usage in your environment.
For optimal use, we recommend that the lower limit of PoolMax must not be less than the number of CPUs
available and 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 the server.
➤ To modify existing PoolMax value:
1. Log in to the WebSphere Administrative Console.
2. In the navigation tree, click Servers > Application Servers > [server name]> (Server Infrastructure >
Java and process management) Process Definition > Java Virtual Machine > Custom Properties.
3. Add the following properties for ConvertPdf:
●
com.adobe.convertpdf.bmc.POOL_MAX=4
●
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=4
●
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
LiveCycle PDF Generator ES
LiveCycle PDF Generator ES is capable of doing multiple PDF conversions simultaneously for certain types
of input files. This is enforced through the use of stateless session beans.
EJB Pool Size Configuration
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
76
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Advanced Production Configuration
EJB Pool Size Configuration
●
Image files (such as BMP, TIFF, PNG, JPEG etc.)
●
OpenOffice files
●
All other file types (except HTML files) like Microsoft Office files, Photoshop, PageMaker, and
FrameMaker files
77
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 for the OpenOffice and other file types pool size to be left unchanged (that is, one) 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 EARs have been deployed on the
application server:
●
adobe-livecycle-<app-server>.ear
●
adobe-livecycle-native-<app-server>-<platform>.ear
Here, <app-server> should be replaced with the name of the application server on which LiveCycle ES has
been deployed in lowercase (such as “jboss”, “weblogic”. or “websphere”), and <platform> should be
replaced with one of the four strings – “x86_win32”, “x86_linux”, “sparc_sunos”, or “powerpc_aix” –
depending on whether you are running your application server on Windows, Linux, SunOS™, or AIX
operating system.
➤ To configure the pool size for PS2PDF and Image2PDF:
1. Make sure that WebSphere Application Server is running.
2. Type http://<hostname>:9060/ibm/console in the URL line of a web browser to access the
WebSphere Administrative Console. The URL might be different if you have chosen WebSphere to run
on a non-standard port or if HTTPS is enforced. Depending on whether security is enabled, you may be
prompted for you user name and password.
3. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers >
[server name] > Java and Process Management > Process Definition > Java Virtual Machine >
Custom Properties.
4. Search for a property named com.ibm.websphere.ejbcontainer.poolSize and, if it exists, click
the existing property name. Otherwise, click the new button and type the property name as
com.ibm.websphere.ejbcontainer.poolSize.
In case the property existed previously, its value should be showing 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
minimum / maximum EJB pool size for Image2PDF and PS2PDF conversions are set to 3 each.
Adobe LiveCycle ES
Advanced Production Configuration
Installing and Deploying LiveCycle ES for WebSphere
EJB Pool Size Configuration
78
5. Modify these values appropriately. For example, if you want to configure a pool size of 5 for
Image2PDFand 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 should be replaced with the actual name with where the
LiveCycle ES application is deployed on the application server. [AM: Doesn’t make sense to me.
You replace LiveCycle8 with the name where LiveCycle ES is deployed? Should that be the
location (i.e. folder)? Or is the name of a server?”]
6. Save your changes and restart WebSphere Application Server. In case you are running an
Application-Server cluster, you will need to make identical changes on each of the application-server
cluster nodes. Therefore, to save time, it is a good idea make the changes before you create a cluster.
This ensures that these values will be automatically set on each cluster node create after these changes
have been made on the primary node.
A
Troubleshooting
This section discusses possible issues you may encounter when installing and deploying LiveCycle ES, and
suggests steps for avoiding or working around them.
Getting help
This section describes the steps you should take prior to contacting 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 disable the Show Friendly HTTP Error Messages option in Internet Explorer (Tools > Options >
Advanced), do the errors persist?
Installation considerations
If you are having problems installing, configuring, or deploying LiveCycle ES, make certain that you have
carefully followed the instructions in these LiveCycle ES documents:
●
Preparing to Install LiveCycle ES
●
Installing and Deploying LiveCycle ES for your application server
●
Administering LiveCycle ES
If you have installed and configured everything according to the documentation, review the following
sections for issues similar to those you are experiencing.
Application server considerations
Check the following application server settings prior to contacting Adobe Support:
●
Total transaction lifetime timeout: 300
●
Initial heap size: 256
●
Maximum heap size: 1024 Mb
●
Prepared statement cache: 100
●
Database connection pool maximum: IDP_DS is 100 and RM_DS is 30
●
Topics and queues connection factories
●
Connection pool maximum connections: 50
79
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebSphere
Database initialization considerations
80
Database initialization considerations
If you are having problems initializing the LiveCycle ES server, consider the following possibilities:
●
Database instances must contain only alphanumeric characters in their names.
●
(Linux and UNIX) Database instances must not exceed the platform-specific threshold of 8 characters.
If the initialization fails at the beginning of the process, check for the following conditions:
●
The LiveCycle ES database has already been created and the user has full rights to it.
●
The database server is accessible when you ping it.
●
The database is empty, that is, it has no tables, sequences, views or index tables.
●
The JNDI name for IDP_DS has been created.
If initialization fails while writing to the Registry, check the application server logs for errors pertaining to
the queues and topics. If errors exist, verify that the queues and topics have been configured properly.
Troubleshooting with log files
This section describes how to troubleshoot LiveCycle ES using the log files.
LiveCycle Configuration Manager log file
By default, the LiveCycle Configuration Manager log file is located in
[LiveCycleES root]\ConfigurationManager\log and is named lcm.0.log (or similar). The log files are useful for
LiveCycle Configuration Manager failure analysis and may be required when dealing with Adobe
Enterprise Support.
Viewing the JVM system output and error logs
The JVM system output and error logs are valuable tools for troubleshooting problems with your server.
➤ To view the JVM system output and error logs:
1. Log in to WebSphere Administrative Console.
2. In the WebSphere Administration navigation tree, in the Troubleshooting section, select Logs and
Trace.
3. Select the name of the application server.
4. Click JVM Logs.
5. Click the Runtime tab and click View under either System.out (to view the JVM system output log) or
System.err (to view the error log). If any of the selections are unavailable, you can view them from the
Configuration tab by specifying the SystemOut.log and SystemErr.log file names. By default the files
are located in the following location:
[appserver root]/profiles/[profile_name]/logs/[server name]
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebSphere
Scheduler service configuration for nondefault JNDI URLs
81
Scheduler service configuration for nondefault JNDI URLs
To function correctly, the Scheduler service may require some additional configuration.
Non-clustered environments
This is the JNDI URL for the IDP_DS that is managed by your application server:
org.quartz.dataSource.idp.java.naming.provider.url
if the JNDI URL differs from the default JNDI URL for the application server (that is, for WebSphere:
iiop://localhost:2809).
➤ To set the scheduler properties:
1. Create a new file called dscscheduler.properties
2. Set the values of the above properties as necessary for the app server node. For example:
org.quartz.dataSource.idp.java.naming.provider.url =
iop://localhost:2809/
org.quartz.jobstore.isClustered = true
org.quartz.scheduler.instanceId = AUTO
3. Add the JVM argument -Dadobe.idp.scheduler.properties=[Path to this
file]/dscscheduler.properties to the application server startup scripts/configuration.
Error messages
This section contains a list of error messages specific to LiveCycle ES and their definitions.
PDF Generator ES on Windows fails when converting native files
PDF Generator ES running on a Windows operating system may fail when converting native files (for
example, 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 arises 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 on the WebSphere for Adobe LiveCycle service, then select the Log On tab.
3. Select This account, then type the user name and password that runs Microsoft Office and click OK.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebSphere
Class not found
82
Class not found
If you see this error, check the following issues:
●
Is the class path setting invalid or missing?
●
Is the JAR file obsolete?
●
Is there a compilation problem in the class?
JNDI name not found
If you see this error, check the following issues:
●
If the symptom is an exception stack trace showing
javax.naming.NameNotFoundException: jdbc/<badName>
check that the expected name is spelled correctly. If it is not, you must fix the code.
➤ To correct most common JNDI exceptions:
1. Check the JNDI tree on the LiveCycle ES application server. Does the name used appear in the tree?
●
If yes, it is most likely that your code has not properly set up the InitialContext object being
used for the lookup and the lookup is being done on a JNDI tree that is not the one the resource is
listed in. Refer to the property values to use in the Installing and Deploying LiveCycle ES document for
your application server.
●
If no, continue to step 2.
2. Does the resource appear in the JNDI tree under a name other than that listed in the lookup?
●
If yes, you are using the wrong lookup name. Provide the correct name.
●
If no, continue to step 3.
3. Review the application server logs during startup. If the application server has been configured to
make this resource available but something is going wrong, an exception will be shown here. Is there
an exception?
●
If yes, review the exception and stack trace. If the NameNotFoundException is a symptom of
another problem based on your investigation of the server logs, move on to the troubleshooting
steps for that problem.
●
If no, continue to step 4.
4. If the resource is not listed in the JNDI tree, and there is no exception at startup to explain why it isn’t
available, the most probable issue is that the application server has not been configured properly to
make that resource available. Review the application server configuration. Has it been configured to
make this resource available?
●
If no, see Installing and Deploying LiveCycle ES for your application server.
●
If yes, this is not one of the common problems that cause this issue. Contact Adobe Support.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebSphere
Failure to deploy adobe-livecycle-websphere.ear
83
Failure to deploy adobe-livecycle-websphere.ear
This section explains how to correct a failed deployment if you receive the following error message when
attempting to deploy the adobe-livecycle-websphere.ear file:
Could not deploy adobe-livecycle-websphere.ear.
com.adobe.livecycle.cdv.CDVException[ALC-LCM-030-112]: Failed to deploy
EAR. Could not deploy adobe-livecycle-websphere.ear.
➤ To correct WebSphere failed deployment:
1. Run the following command in the command window:
ulimit -n
2. If a value of 1024 is returned, you must increase the value to 2048 in the wasadmin.sh script.
3. Open the [appserver root]/bin/wsadmin.sh script in a text editor. After the file's comment block header,
add the following line:
ulimit -n 2048
4. Restart WebSphere.
5. Deploy the adobe-livecycle-websphere.ear file using LiveCycle Configuration Manager.
J2CA0294W warning messages
To avoid receiving warning messages in the SystemOut.log file related to the deprecated usage of direct
JNDI lookup, you can modify the WebSphere logging level.
To suppress the warning message J2CA0294W from the SystemOut.log, you can change the logging level
to *=info:com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl=severe
➤ To set the logging levels for your logs:
1. Log in to WebSphere Administrative Console through the URL http://[hostname]:9060/admin.
2. In the WebSphere Administrative Console navigation tree, in the Troubleshooting section, select
Logging and Tracing > Change Log Detail Levels.
3. On the Configuration tab, type the following string:
*=info:com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl=severe
4. Click OK.
5. Select Save changes to master configuration.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebSphere
Troubleshooting
Exceptions thrown when initializing the LiveCycle ES database multiple times
84
Exceptions thrown when initializing the LiveCycle ES database multiple
times
When you initialize the LiveCycle ES database after it has already been initialized, exceptions may be
thrown indicating that the POF schema has been initialized.
This error can be safely ignored.
XMLForm.exe permission error
This section explains how to a correct UNIX and Linux permission issue with Forms ES if the following error
message is logged:
Cannot add execute permission on file /[path_to_XMLForm.exe]
To correct this issue, ensure that the swap space on UNIX and Linux servers is at least 3 GB.
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