bb c Installing and Deploying LiveCycle ES

bb c Installing and Deploying LiveCycle ES
bc
Installing and Deploying LiveCycle® ES
for JBoss®
Adobe® LiveCycle® ES
August 2010
Update 1 (8.2)
© 2010 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle® ES Update 1 (8.2) Installing and Deploying LiveCycle ES for JBoss® for Microsoft® Windows®, UNIX®, and Linux®
Edition 2.4, August 2010
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end-user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Acrobat, 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.
JBoss is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries.
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 BSAFE and/or TIPEM software by RSA Security, Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).
This product includes copyrighted software developed by E. Wray Johnson for use and distribution by the Object Data Management Group
(http://www.odmg.org/).
Portions © Eastman Kodak Company, 199- and used under license. All rights reserved. Kodak is a registered trademark and Photo CD is a
trademark of Eastman Kodak Company.
Powered by Celequest. Copyright 2005-2008 Adobe Systems Incorporated. All rights reserved. Contains technology distributed under license
from Celequest Corporation. Copyright 2005 Celequest Corporation. All rights reserved.
Single sign-on, extending Active Directory to Adobe LiveCycle ES provided by Quest Software “www.quest.comlidentity-management” in a
subsequent minor release that is not a bug fix (i.e., version 1.1 to 1.2 but not 1.1.1 to 1.1.2) of the Licensee Product that incorporates the
Licensed Product.
The Spelling portion of this product is based on Proximity Linguistic Technology.
©Copyright 1989, 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey
USA.
© Copyright 1990 Merriam-Webster Inc. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2003 Franklin Electronic Publishers Inc. © Copyright 2003 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1991 Dr.Lluis de Yzaguirre I Maura © Copyright 1991 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1990 Munksgaard International Publishers Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1995 Van Dale Lexicografie bv © Copyright 1996 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1990 IDE a.s. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc.
Burlington, New Jersey USA.
© Copyright 2004 Franklin Electronics Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1992 Hachette/Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of
Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 Bertelsmann Lexikon Verlag © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 MorphoLogic Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers,
Inc. Burlington, New Jersey USA.
© Copyright 1990 Williams Collins Sons & Co. Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA. © Copyright 1993-95 Russicon Company Ltd.
© Copyright 1995 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 IDE a.s. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc.
Burlington, New Jersey USA.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
1
About This Document.................................................................................................................. 7
What’s in this document?............................................................................................................................................................ 7
Who should read this document? ............................................................................................................................................ 7
Additional information................................................................................................................................................................. 8
1
Introduction ............................................................................................................................... 10
About the LiveCycle ES installation, configuration, and deployment process......................................................10
Selecting tasks for configuring and deploying LiveCycle ES........................................................................................10
Upgrading to LiveCycle ES........................................................................................................................................................11
Installation and deployment list .............................................................................................................................................11
2
Installing the Solution Component Files ................................................................................. 12
Installing the product files ........................................................................................................................................................12
Installing on a Windows staging platform for deployment on Linux or UNIX.................................................13
Configuring the LiveCycle Reader Extensions ES Rights credential ....................................................................13
Including the Java 5 SDK in the JAVA_HOME environment variable..................................................................13
Installing LiveCycle ES ..........................................................................................................................................................13
Viewing the error log ..................................................................................................................................................................16
Next steps........................................................................................................................................................................................16
3
Configuring LiveCycle ES for Deployment .............................................................................. 17
About LiveCycle Configuration Manager ............................................................................................................................17
CLI versus GUI versions of LiveCycle Configuration Manager ...............................................................................17
Configuring and deploying LiveCycle ES.............................................................................................................................18
Next steps........................................................................................................................................................................................22
4
Deploying LiveCycle ES to JBoss Application Server.............................................................. 23
About deploying LiveCycle ES solution components.....................................................................................................23
Summary of deployable components ..................................................................................................................................23
Deploying to JBoss Application Server ................................................................................................................................23
Next steps........................................................................................................................................................................................24
5
Post-Deployment Activities ...................................................................................................... 25
Verifying the deployment and accessing LiveCycle Administration Console........................................................25
Accessing LiveCycle Administration Console..............................................................................................................25
Viewing the log files..............................................................................................................................................................26
Accessing solution component web applications ...........................................................................................................26
Accessing Rights Management ES...................................................................................................................................27
Accessing User Management ............................................................................................................................................28
Accessing the Content Services ES repository...................................................................................................................28
Configuring LiveCycle PDF Generator ES or 3D ES ..........................................................................................................29
Setting environment variables..........................................................................................................................................29
Configuring the application server to use HTTP proxy server...............................................................................30
Setting the Adobe PDF Printer as the default printer...............................................................................................31
Configuring Acrobat 9.0 ......................................................................................................................................................31
Installing East Asian characters in Windows ................................................................................................................32
Adding fonts to PDF Generator ES or PDF Generator 3D ES ..................................................................................32
Configuring HTML to PDF conversions..........................................................................................................................34
4
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Contents
5
Installing the IPP client ...............................................................................................................................................................35
Final setup for LiveCycle Rights Management ES.............................................................................................................37
Configuring LiveCycle ES to access LDAP............................................................................................................................37
Setting PDF Generator ES or 3D ES watched folder performance parameters......................................................38
Enabling FIPS mode.....................................................................................................................................................................39
Configuring HTML digital signature ......................................................................................................................................39
Configuring the Document Management service for LiveCycle Content Services ES ........................................40
Configuring the Connector for EMC Documentum service..........................................................................................40
Configuring the Connector for IBM FileNet service .........................................................................................................44
Configuring the connector using FileNet 3.5...............................................................................................................44
Configuring the connector using FileNet 4.0.1 ...........................................................................................................47
Configuring the LiveCycle ES Connector for IBM Content Manager...................................................................51
Uninstalling LiveCycle ES...........................................................................................................................................................56
Uninstalling a LiveCycle ES solution component.......................................................................................................56
6
Manually Configuring BAM Server for LiveCycle ES ............................................................... 58
Installing JBoss Application Server ........................................................................................................................................58
Configuring JBoss 4.2.0 for BAM.......................................................................................................................................59
Configuring the keystore...........................................................................................................................................................60
Creating the bam.properties file.............................................................................................................................................60
Creating and configuring the BAM Server metadata database ..................................................................................61
User accounts ..........................................................................................................................................................................61
Configuring your database environment (DB2 only)................................................................................................61
Installing database drivers on JBoss Application Server for BAM Server.................................................................62
Configuring the BAM Server metadata database.............................................................................................................62
Connecting JBoss Application Server for BAM Server to the LiveCycle ES database....................................65
Configuring required JBoss Application Server JVM options ................................................................................68
Optional JBoss Application Server JVM parameters .................................................................................................69
Configuring LiveCycle Process Management ES for BAM Server................................................................................70
Deploying BAM Server EAR file to JBoss Application Server ........................................................................................70
Configuring Business Activity Monitoring ..........................................................................................................................70
Configuring LDAP settings for BAM Server.........................................................................................................................72
Limitations of BAM Server LDAP connectivity.............................................................................................................72
Best practices for BAM Server LDAP connectivity......................................................................................................73
Configuring automatic LDAP synchronization ...........................................................................................................73
Configuring LDAP user mapping .....................................................................................................................................75
Configuring LDAP role mapping......................................................................................................................................75
Manually synchronizing with the LDAP server............................................................................................................76
Using BAM Dashboard ...............................................................................................................................................................76
Shutting down BAM Server ......................................................................................................................................................77
Additional documentation .......................................................................................................................................................78
Uninstalling Business Activity Monitoring ..........................................................................................................................78
7
Advanced Production Configuration....................................................................................... 79
Configuring pool size for LiveCycle Output ES and LiveCycle Forms ES..................................................................79
LiveCycle PDF Generator ES .....................................................................................................................................................79
Configuring EJB Pool Size ...................................................................................................................................................79
8
Troubleshooting ........................................................................................................................ 82
Getting help ...................................................................................................................................................................................82
Installation considerations .................................................................................................................................................82
Change of log on account for JBoss on Windows......................................................................................................82
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
6
Application server considerations ...................................................................................................................................83
Database initialization considerations .................................................................................................................................83
Address a high number of concurrent calls .................................................................................................................83
Problems accessing the Services page in LiveCycle Administration Console .................................................83
Troubleshooting with log files.................................................................................................................................................84
LiveCycle Configuration Manager log file.....................................................................................................................84
JBoss log file.............................................................................................................................................................................84
Deleting the application server transaction log file ..................................................................................................84
IBM FileNet messages appear in JBoss Application Server log file ......................................................................84
Scheduler service configuration for nondefault JNDI URLs..........................................................................................84
Non-clustered environments.............................................................................................................................................84
Error messages ..............................................................................................................................................................................85
PDF Generator ES or PDF Generator 3D ES (on Windows) fails when converting native files ...................85
Class not found .......................................................................................................................................................................85
JNDI name not found ...........................................................................................................................................................86
If yes, this is not one of the common problems that cause this issue. Contact Adobe Support...............86
OutputIVS Printer not found..............................................................................................................................................86
Exceptions thrown when initializing the database multiple times .....................................................................87
J2CA0081E: Method cleanup error on SQL Server.....................................................................................................87
Database initialization fails on WebLogic .....................................................................................................................87
OutOfMemoryError: Java heap space error..................................................................................................................87
Connector for EMC Documentum error ........................................................................................................................88
Failure to deploy EAR files ..................................................................................................................................................88
Improving Windows Server Performance with LDAP............................................................................................88
Could not start/create deployment errors on Solaris ...............................................................................................89
PDF Generator ES considerations...........................................................................................................................................89
Configuring PDF Generator ES to convert MS Office files to PDF format..........................................................89
Microsoft Visio 2007 default macro settings cause conversion time-out .........................................................89
A
Appendix - Install Command Line Interface ............................................................................ 91
Installing LiveCycle ES ................................................................................................................................................................91
Error logs .........................................................................................................................................................................................97
Uninstalling LiveCycle ES in console mode ........................................................................................................................97
Next steps........................................................................................................................................................................................97
B
Appendix - LCM Command Line Interface ............................................................................... 98
Order of operations .....................................................................................................................................................................98
Command line interface property file...................................................................................................................................98
Common properties..............................................................................................................................................................98
Configure LiveCycle ES properties...................................................................................................................................99
Configure application server properties..................................................................................................................... 100
Deploy LiveCycle properties ........................................................................................................................................... 100
Initialize LiveCycle properties......................................................................................................................................... 100
Initialize BAM properties .................................................................................................................................................. 100
Deploy LiveCycle Components properties................................................................................................................ 101
Command line interface usage...................................................................................................................................... 101
Examples usage ......................................................................................................................................................................... 104
Error logs ...................................................................................................................................................................................... 104
Next steps..................................................................................................................................................................................... 104
1
About This Document
This document is one of several resources that are available to help you learn about Adobe® LiveCycle® ES
(Enterprise Suite) Update 1. LiveCycle ES is a flexible, extensible platform that helps automate and
accelerate the flow of business-critical information to and from customers, partners, constituents, and
employees.
What’s in this document?
This guide provides information about how to install and configure the following solution components on
Microsoft® Windows® and Linux® and how to deploy the solution components to JBoss® Application
Server:
●
Adobe LiveCycle Barcoded Forms ES
●
Adobe LiveCycle Business Activity Monitoring
●
Adobe LiveCycle ES Connector for EMC Documentum
●
Adobe LiveCycle ES Connector for IBM FileNet
●
Adobe LiveCycle ES Connector for IBM Content Manager
●
Adobe LiveCycle Content Services ES
●
Adobe LiveCycle Digital Signatures ES
●
Adobe LiveCycle Forms ES
●
Adobe LiveCycle Foundation
●
Adobe LiveCycle Output ES
●
Adobe LiveCycle PDF Generator ES
●
Adobe LiveCycle PDF Generator 3D ES
●
Adobe LiveCycle Process Management ES
●
Adobe LiveCycle Reader Extensions ES
●
Adobe LiveCycle Rights Management ES
Who should read this document?
This guide provides information for administrators or developers who are 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 and
Microsoft Windows operating systems, MySQL, Oracle®, DB2®, or SQL Server database servers, and web
environments.
7
Adobe LiveCycle ES
About This Document
Installing and Deploying LiveCycle ES for JBoss
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.2\
The installation directory that is used for all
LiveCycle ES solution components. The
installation directory contains
subdirectories forAdobe LiveCycle
Configuration Manager, the
Programming with LiveCycle ES, and each
LiveCycle ES solution component installed
(along with the product documentation).
This directory also includes directories
relating to third-party technologies.
Linux:
/opt/adobe/livecycle8.2/
[appserver root]
These installation locations are
examples. Your installation location
may be different.
The home directory of the application
server that runs the LiveCycle ES services.
C:\bea\wlserver_10.0\
/opt/IBM/WebSphere/AppServer
JBoss Application Server on Windows:
C:\jboss
JBoss Application Server on Linux:
/opt/jboss
[dbserver root]
Depends on the database type and
your specification during installation.
The location where the LiveCycle ES
database server is installed.
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux). 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 the
solution components
LiveCycle ES Overview
What’s new in this LiveCycle ES (Enterprise Suite) What’s New
release
LiveCycle ES terminology
LiveCycle ES Glossary
LiveCycle ES solution components
Adobe LiveCycle ES
8
Adobe LiveCycle ES
About This Document
Installing and Deploying LiveCycle ES for JBoss
Additional information
For information about
See
Other services and products that integrate with
LiveCycle ES
Adobe Developer Connection
Installing Adobe LiveCycle Workbench ES
Installing Your Development Environment
Upgrading to LiveCycle ES from a previous
version.
Preparing to Upgrade to LiveCycle ES
Upgrading to LiveCycle ES for JBoss
Performing administrative tasks for LiveCycle ES
Administering LiveCycle ES
All the documentation available for LiveCycle ES
LiveCycle ES documentation
LiveCycle ES release information and last-minute Release Notes
changes that occur to the product
Patch updates, technical notes, and additional
information about this product version
LiveCycle Technical Support
9
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 LiveCycle ES installation, configuration, and deployment process” on page 10
●
“Installation and deployment list” on page 11
For information about preparing your system for installing LiveCycle ES, including system requirements,
see Preparing to Install LiveCycle ES.
About the LiveCycle ES installation, configuration, and
deployment process
Installing, configuring, and deploying LiveCycle ES involves the following processes:
Installing: Install LiveCycle ES by running the installation program. Installing LiveCycle ES places all of
the required files onto your computer, within one installation directory structure. The default
installation directory is C:\Adobe\LiveCycle8.2 (Windows) or /opt/adobe/LiveCycle8.2 (Linux); however,
you can install the files to a different directory. In this docment, the default installation directory is
referred to as [LiveCycleES root]. (See “Installing the Solution Component Files” on page 12.)
Configuring and assembling: Configuring LiveCycle ES modifies various settings that determine how
LiveCycle ES works. Assembling the product places all of the installed components into several
deployable EAR and JAR files, according to your configuration instructions. Configure and assemble the
components for deployment by running LiveCycle Configuration Manager. (See “Configuring
LiveCycle ES for Deployment” on page 17.) 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 JBoss 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 (LCA) files are packaged as JAR
files.
Initializing the LiveCycle ES database: Initializing the database to be used with LiveCycle ES creates
tables for use with User Management and other components. Deploying any solution component that
connects to the LiveCycle ES database requires you to initialize the LiveCycle ES database after the
deployment process.
Selecting tasks for configuring and deploying LiveCycle ES
After you perform an installation, you can run LiveCycle Configuration Manager to perform various tasks:
●
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES component deployment
●
Validate the LiveCycle ES component deployment
10
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
●
Configure the LiveCycle Reader Extensions ES Rights credential (optional)
●
Import the LiveCycle ES Samples (optional)
Introduction
Upgrading to LiveCycle ES
11
If you install Reader Extensions ES, you can also specify and import the Reader Extensions ES Rights
credential that is required for applying usage rights to PDF documents.
If you want to perform a turnkey installation and deployment (installs, configures, and deploys
LiveCycle ES along with JBoss and MySQL), see Installing and Deploying LiveCycle ES for JBoss Using Turnkey.
Upgrading to LiveCycle ES
Before you install LiveCycle ES for upgrading from LiveCycle 7.x and later, ensure that you completed the
tasks that are described in Preparing to Upgrade to LiveCycle ES.
Installation and deployment list
The following list includes the steps that are required for installing LiveCycle ES by using the manual
method. Your application server must be installed and configured before you perform the installation.
●
Ensure that you have the required software installed and configured in the target environment. (See
Preparing to Install LiveCycle ES (Single Server).
●
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 task
configures and assembles LiveCycle ES. (See “Configuring LiveCycle ES for Deployment” on page 17.)
●
Deploy the EAR files to the application server. You must do this manually. (See “Deploying LiveCycle ES
to JBoss Application Server” on page 23.)
●
Run LiveCycle Configuration Manager to deploy LiveCycle ES component files, initialize the
LiveCycle ES database, and (optionally) deploy product samples. (See “Configuring LiveCycle ES for
Deployment” on page 17.)
●
Access LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 25.)
●
(Optional) Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 37.)
To perform a Turnkey installation and deployment (install, configure, and deploy LiveCycle ES along with
JBoss and MySQL), see Installing and Deploying LiveCycle ES for JBoss Using Turnkey.
2
Installing the Solution Component Files
This section describes the first phase of setting up a LiveCycle ES system that is running the LiveCycle ES
installation program on a Windows or Linux operating system. A subsequent phase will include running
LiveCycle Configuration Manager to configure and deploy LiveCycle ES.
Before you install the solution components, ensure that your environment includes the software and
hardware that is required to run LiveCycle ES. You should also understand the installation options and
have the environment prepared as required. (See Preparing to Install LiveCycle ES (Single Server).)
LiveCycle ES also provides a command line interface (CLI) for the installation program. The CLI is intended
to be used by advanced users of LiveCycle ES or in server environments that do not support the use of the
graphical user interface of LiveCycle Configuration Manager (See “Appendix - LCM Command Line
Interface” on page 98.)
This chapter covers the following topics:
●
“Installing the product files” on page 12
●
“Viewing the error log” on page 16
Installing the product files
When you run an installation program, you need the serial number for the solution components that you
are installing. If you are upgrading from LiveCycle ES 8.0, the existing serial numbers for LiveCycle ES 8.0
are used. In this case, you must add additional serial numbers only if you are installing solution
components in addition to those you are upgrading.
●
The type of installation and configuration you are performing. (See “Configuring JBoss Application
Server” in Preparing to Install LiveCycle ES.)
To successfully install, you need read and write permissions for the installation directory. The following
installation directories are the defaults; however, you can specify a different directory as required:
●
(Windows) C:\Adobe\LiveCycle8.2\
●
(UNIX) /opt/adobe/livecycle8.2/
When installing on Linux, the installation program uses the logged-in user's home directory as a
temporary directory for storing files. As a result, messages such as the following text may appear in the
console:
WARNING: could not delete temporary file /home/<username>/ismp001/1556006
When you complete the installation, you must manually delete the temporary files.
Caution: Ensure that the temporary directory for your operating system meets the minimum
requirements as outlined in Preparing to Install LiveCycle ES (Single Node). The temporary
directory is one of the following locations:
●
(Windows) TMP or TEMP path as set in the environment variables
●
(UNIX) Logged-in user’s home directory
12
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for JBoss
Installing on a Windows staging platform for deployment on Linux or UNIX
13
Note: When you are installing the solution components on a Linux operating system, you must be logged
in as the root user to successfully install the solution components to the default location, which is
/opt/adobe/LiveCycle8.2/. If you are logged in as a non-root user, change the installation directory
to one that you have permissions (read-write-execute privileges) for. For example, you can change
the directory to /home/[username]/livecycle8.2.
Temporary files are generated in the system default temp directory or in the directory that you
specified. In certain instances, the generated temporary files may remain after the installer is closed.
You can choose to remove these files manually.
Installing on a Windows staging platform for deployment on Linux or UNIX
LiveCycle ES can be installed and configured on Windows for deployment on a Linux or UNIX platform. You
can use this functionality for installing on a locked-down Linux or UNIX environment. For example, a
locked-down environment does not have a graphical user interface installed. When you run the
installation program on Windows, you can choose a Linux or UNIX operating system as the target platform
for deploying LiveCycle ES. The installation program installs binaries for Linux that are also used by
LiveCycle Configuration Manager when you configure the product.
The computer running Windows can then be used as a staging location for the deployable objects, which
can be copied to a Linux or UNIX computer for deployment to the application server. The application
server that you are targeting must be consistent with what you choose during installation and
configuration, regardless of the operating system.
Note: The host and target operating system must be Windows to support installing Acrobat for
LiveCycle PDF Generator ES from the installer.
Configuring the LiveCycle Reader Extensions ES Rights credential
Ensure that you have a new valid credential and password before you run the installation. If you do not
have the information at this time, you can install the credential after you install and deploy LiveCycle ES on
the Trust Store configuration pages in LiveCycle Administration Console.
Including the Java 5 SDK in the JAVA_HOME environment variable
The JAVA_HOME environment variable must point to the Java 5 SDK. The required Java SDK is Sun JDK
1.5.0_11 or higher.
The Java 5 SDK requirements are also listed in Preparing to Install LiveCycle ES (Single Node).
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 17.
Note: To avoid permission issues during deployment, ensure that you run the LiveCycle ES installer and
LiveCycle Configuration Manager as the same user who will run the JBoss server.
➤ To install LiveCycle ES:
1. Navigate to the ./livecycle_server/8.2 directory of the installation media.
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
14
2. If you are installing on Linux and you are not installing directly from a release DVD, set executable
permissions on the installation file by typing the following command at the command prompt:
chmod 007 linux_livecycle8_setup.bin
3. Start the installation program:
●
(Windows) Double-click the win_livecycle8_setup.exe file.
●
(UNIX) From a command prompt, type the file name that is appropriate for your operating system:
./linux_livecycle8_setup.bin
./solaris_livecycle8_setup.bin
If you are installing on a Windows staging platform for deployment to UNIX, start the Windows
executable.
Specify the following additional arguments to redirect the LiveCycle ES installer temporary directory to
an alternate, non-default location:
-cp:p stage.jar -is:tempdir [alternate temporary directory]
(Solaris Only) To use a higher heap size (such as 512M) in the installer argument, you must specify
the heap size settings in a separate file and then run the install script.
To do this, create a filed named solaris_livecycle8_setup.ja in the directory where
solaris_livecycle8_setup.bin exists, and add the following lines in it:
-XMS256M
-XMX512M
After this, run the install script to direct the installer to use the JDK you installed:
# ./solaris_livecycle8_setup.bin -cp:p stage.jar -is:tempdir /[temporary
directory] -is:javahome [java_home]
4. When prompted, select the language for the installation to use and click OK.
5. On the Welcome screen, click Next. If you have a previous version of LiveCycle ES 8.0.x the Update
Installation screen appears.
6. Select one of the following options and then click Next:
●
Upgrade Existing Installation to LiveCycle ES v8.2: Choose this option if you intend to upgrade
from LiveCycle ES 8.0.x to LiveCycle ES 8.2. Ensure that the directory shown on the screen
corresponds with the existing version of LiveCycle ES; otherwise, browse to the correct directory.
Choosing this option ensures that information from the existing installation, such as the product
serial number, is used. LiveCycle Configuration Manager performs the actual upgrade tasks when
the installation process is complete. It is important that you back up your existing environment
before you upgrade. (See “LiveCycle ES Database” and “GDS Backup and Recovery” in Administering
LiveCycle ES.)
Note: If you choose to upgrade the existing LiveCycle ES, go to the Upgrading to LiveCycle ES 8.2 from
8.0.x document for your application server and follow the instructions for upgrading in that
document.
●
Install LiveCycle ES v8.2: Choose this option to install a new, separate instance of LiveCycle ES 8.2.
If you choose this option, your previous installation of LiveCycle ES will not be upgraded or
removed.
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
15
7. On the Installation Location screen, accept the default directory as listed or click Browse and navigate
to the directory where you intend to install the solution component, and then click Next.
Note: If you type the name of a directory that does not exist, it is created for you.
Caution: When you install the solution component, you can specify a different installation location. If you
are installing on Linux, the directory you specify should not contain any spaces; otherwise, the
installation program does not install the solution component.
8. 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.
Note: If you chose to upgrade an existing installation to LiveCycle ES 8.2, the serial number or numbers
already appear in the Solution Component License Type list. You do not need to add a serial
number; just click Next to continue.
Tip: You can reset the serial number by clicking Clear.
9. Read the Adobe LiveCycle ES Server License Agreement and select I accept to the terms of the license
agreement. If you do not accept the license agreement, you cannot continue.
10. Click Next and then select the JAVA SE SDK location. You can browse the correct SDK location or you
can continue with the default and click Next.
11. (Windows only) On the OS Selection screen, select the operating system that you plan to configure
LiveCycle ES for and click Next.
Note: At this point, you can specify to use Windows as a staging platform for your deployment. You can
select a UNIX operating system as the target for deployment even if you are installing on
Windows. (See “Installing on a Windows staging platform for deployment on Linux or UNIX” on
page 13.)
12. (PDF Generator ES or PDF Generator 3D ES for Windows only) Select the appropriate option on the
PDF Generator ES screen:
●
Yes, enable native application support for PDF Generator ES: Select this option if Acrobat 9.0 is
installed. If you do not have Acrobat installed, install it now.
Note: PDF Generator 3D ES requires native application support to convert 3D files to PDF.
If you have an unsupported version of Acrobat installed, complete the LiveCycle ES installation,
uninstall Acrobat, and then install Acrobat 9.0 from the LiveCycle ES installation media by following
the instructions in the procedure “Configuring Acrobat 9.0” on page 31.
●
No, do not enable native application support for LiveCycle PDF Generator ES: Select this
option if you do not intend to use the native application functionality.
13. (PDF Generator ES for or PDF Generator 3D ES Windows only) Confirm that you have Acrobat
installed and click Next.
14. On the Pre-installation Summary Details screen, review the details and click Install. The installation
program displays the progress of the installation.
15. Review the release notes that are displayed and click Next.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Installing the Solution Component Files
Viewing the error log
16
16. Review the details of the Post-installation summary screen. Select Start LiveCycle Configuration
Manager and then click Finish.
Note: Selecting the Start LiveCycle Configuration Manager option starts LiveCycle Configuration
Manager, which allows you to complete your configuration and deployment immediately. If you are
not ready to run LiveCycle Configuration Manager, ensure that Start LiveCycle Configuration
Manager is not selected when you click Finish. You can start LiveCycle Configuration Manager
later, when you are ready. (See “Configuring LiveCycle ES for Deployment” on page 17.)
Note: (PDF Generator ES or PDF Generator 3D ES for Windows only) If you did not choose to install
Acrobat 9.0 using the LiveCycle ES installer, you need to complete the steps in “Configuring Acrobat
9.0” on page 31.
Viewing the error log
If errors occur during the installation, the installation program creates the adobe_lc8.2_server_install.log
file, which contains the error messages. This log file is in the system temporary directory (TEMP or TMP).
(See “Troubleshooting” on page 82.)
You must configure the font directories for each computer in the cluster, including the LiveCycle ES fonts
that are installed in the [LiveCycleES root]\fonts directory.
The fonts must exist in the same path, and the directory must have identical contents on all computers in
the cluster. This can be accomplished by using a shared directory that all computers in the cluster can
access or by making the contents of the [LiveCycle ES root]\fonts directory available on each computer in
the cluster in an identical path.
Record the location where you create these shared directories for later use when you configure
LiveCycle ES using LiveCycle Configuration Manager.
Caution: The font directories must be distinct from the GDS directory; however, they may be distinct
sibling subdirectories of a single shared parent directory.
Next steps
You must now configure LiveCycle ES for deployment. (See “Configuring LiveCycle ES for Deployment” on
page 17.)
3
Configuring LiveCycle ES for Deployment
This chapter describes how to perform any of the following tasks using LiveCycle Configuration Manager
and manual steps:
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES component
●
(Optional) Configure the LiveCycle Reader Extensions ES Rights credential (if Reader Extensions ES is
installed)
●
Initialize BAM metadata for LiveCycle ES Business Activity Monitoring (if Business Activity Monitoring is
installed)
●
(Optional) Import the LiveCycle ES Samples into LiveCycle ES
This chapter assumes that you prepared your environment for hosting LiveCycle ES and installed the
solution component files. If you have not done this task, see Preparing to Install LiveCycle ES Single Node
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. LiveCycle Configuration Manager is installed with
the solution component files when you run the LiveCycle ES installation program. When you run LiveCycle
Configuration Manager, you specify the LiveCycle ES solution components you are configuring, and the
tasks that you want LiveCycle Configuration Manager to perform.
You can start LiveCycle Configuration Manager from the installation program to configure solution
components during the installation process, or you can start LiveCycle Configuration Manager any time
after the installation.
CLI versus GUI versions of LiveCycle Configuration Manager
This section describes the GUI version of LiveCycle Configuration Manager. For instructions about using
the command line interface (CLI) version of LiveCycle Configuration Manager, see “Appendix - LCM
Command Line Interface” on page 98. The following table illustrates the functionality offered by both
versions of LiveCycle Configuration Manager and configuration tasks you can perform manually.
17
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for JBoss
LiveCycle ES configuration task
Configuring and deploying LiveCycle ES
LCM GUI
LCM CLI
18
Manual
(Non-LCM)
Configure LiveCycle ES
Yes
Yes
No
Configure application server
No
No
Yes
Validate application server configuration
No
No
Yes
Deploy LiveCycle ES EARs
No
No
Yes
Initialize LiveCycle ES database
Yes
Yes
No
Initialize Business Activity Monitoring
Yes
Yes
Yes
Deploy LiveCycle ES components
Yes
Yes
No
Validate LiveCycle ES component deployment
Yes
Yes
Yes
Validate server connection
Yes
Yes
No
Validate LiveCycle ES server connection
Yes
Yes
No
Validate database connection
Yes
Yes
No
Configure Reader Extensions ES
Yes
No
Yes
Import Samples
Yes
No
Yes
Configuring and deploying LiveCycle ES
When you run LiveCycle Configuration Manager, you can select the tasks that you want the program to
perform automatically.
Tip: LiveCycle Configuration Manager verifies the values that are specified on each screen when you click
Next. If it cannot validate a value, a warning message appears, the property on the screen becomes
red, and you cannot proceed until you enter a valid value.
After LiveCycle Configuration Manager configures the LiveCycle ES EAR files, it places the files
adobe-livecycle-native-jboss-[OS].ear, adobe-livecycle-jboss.ear, adobe-workspace-client.ear (if you
installed LiveCycle Process Management ES) and adobe-contentservices.ear (if you installed LiveCycle
Content Services ES) in the following directory:
●
(Windows) [LiveCycleES root]\configurationManager\export
●
(Linux) [LiveCycleES root]/configurationManager/export
When you manually deploy the LiveCycle ES EAR files, you can access the files in this directory and deploy
them to the application server.
After LiveCycle Configuration Manager configures the LiveCycle ES EAR files, you may rename the EAR files
to a custom file name (for example, to specify in the file name a version identifier, or any other information
required by standard practices in the local J2EE environment). LiveCycle Configuration Manager does not
support deployment or undeployment of EAR files with custom file names. If your EAR files use a custom
file name, you must manually deploy and undeploy them to the application server (for example, when you
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for JBoss
Configuring and deploying LiveCycle ES
19
deploy the initial custom-named EAR files, and when applying any later changes such as service packs or
patches).
Note: If you previously deployed LiveCycle ES files, you must first undeploy the product EAR files from the
application server. (See “Uninstalling LiveCycle ES” on page 56.)
➤ To configure LiveCycle ES:
Tip: You can press F1 in LiveCycle Configuration Manager to view Help information for the screen you are
viewing. This Help contains details that may not be included in this document and are specific to the
context of each screen in LiveCycle Configuration Manager.
1. If you did not start LiveCycle Configuration Manager automatically from the installation program,
navigate to the [LiveCycleES root]/configurationManager/bin directory and enter the appropriate
command:
●
(Windows) ConfigurationManager.bat
●
(Linux) ./ConfigurationManager.sh
2. If prompted, select a language and click OK.
3. On the Welcome screen, click Next.
4. On the Upgrade task selection screen, ensure that Upgrade from LiveCycle ES is not selected, then
click Next to continue.
Caution: If you want to upgrade an existing LiveCycle ES installation, do not continue this procedure. For
upgrade information and procedures, see the Preparing for Upgrading to LiveCycle ES guide
applicable to your current version of LiveCycle ES and the Upgrading to LiveCycle ES guide
applicable to your application server.
5. On the Solution Component Selection screen, select the LiveCycle ES solution components that you
installed and plan to deploy, and then click Next.
6. On the Task Selection screen, select all the tasks you want to perform and click Next.
Note: The Configure Application Server, Validate Application Server Configuration, and Deploy
LiveCycle ES EARs tasks are not available for JBoss. You must configure your JBoss Application
Server and deploy the LiveCycle ES EARs manually (see the Preparing to Install LiveCycle ES (Single
Server) guide.
7. On the Configure LiveCycle ES (1 of 3) screen, click Configure. When the EAR files are configured, click
Next.
8. On the Configure LiveCycle ES (2 of 3) screen, set the directories that LiveCycle ES will use to access
fonts and store temporary data that is associated with processing jobs:
●
(Optional) To change the default location of the Adobe server fonts directory, type the path or
browse to the directory.
●
(Optional) Specify a directory for the Customer fonts directory box. The directory contains any
additional fonts that you have licensed and installed.
●
(Optional) To change the default location of the System fonts directory, type the path or browse to
the directory.
●
(Optional) To specify the Location of the temporary directory, click Browse.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for JBoss
●
Configuring and deploying LiveCycle ES
20
(Optional) To enable FIPS, ensure that Enable FIPS is selected. Select this option only if you require
the Federal Information Processing Standards (FIPS) to be enforced.
9. After you specify the directories, click Next.
10. On the Configure LiveCycle ES (3 of 3) screen, add the location of the GDS directory path by doing one
of these tasks:
●
Type the location of the GDS directory.
●
Click Browse and navigate to the location of the GDS directory.
Note: If you do not specify a specific location for the global document storage root directory, a default
value is used.
11. Click Next, click Configure to configure the LiveCycle ES EARs with this directory information and, after
the configuration is complete, click Next.
12. (Content Services ES only) On the LiveCycle Content Services ES Configuration screen, set the
parameters that Content Services ES will use:
●
Deploy Type: Select Single Server or .
●
Content storage root directory: Specify the root directory that is used by Content Services ES.
13. On the Configure LiveCycle ES Summary screen, click Next.
14. On the Deploy LiveCycle ES EARs screen, click Deploy.
15. (LiveCycle ES Connector for EMC Documentum, LiveCycle ES Connector for IBM FileNet, or
LiveCycle ES Connector for IBM Content Manager only) On the Configure LiveCycle ES Connectors
screen, press F1, follow the instructions in the Help dialog box, and then click Next.
16. Without exiting LiveCycle Configuration Manager, stop JBoss Application Server.
17. Without exiting LiveCycle Configuration Manager, manually deploy the LiveCycle ES EAR files to JBoss
by copying the following files from the [LiveCycleES root]/configurationManager/export directory to
the [appserver root]/server/all/deploy directory:
●
adobe-livecycle-native-jboss-[OS].ear
●
adobe-livecycle-jboss.ear
●
adobe-workspace-client.ear (Process Management ES only)
18. Start JBoss to ensure the LiveCycle ES applications start successfully.
19. Return to LiveCycle Configuration Manager and click Next.
Caution: If you configured a non-default GDS directory in step 10, you must restart the JBoss Application
Server before you deploy the LiveCycle ES EAR files.
20. On the LiveCycle ES Database Initialization screen, verify that the host (using the IP address) and port
information matches the host and port information for a LiveCycle ES server , and then click Initialize.
The database initialization task creates tables in the database, adds default data to the tables, and
creates basic roles in the database. Restart the server if you are prompted to do so. When the
initialization has completed successfully, click Next.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for JBoss
Configuring and deploying LiveCycle ES
21
21. (Business Activity Monitoring only) On the Initialize Business Activity Monitoring screen, provide the
information for the following fields:
Database type: The database on which BAM metadata is running.
BAM Host: The name or IP address of the computer that hosts the application server on which BAM
server is running.
BAM HTTP Port: The HTTP service port that the database uses (for example, 8080).
BAM Administrator User ID: The administrator ID that is required to log in to BAM Workbench. The
default user ID is system.
BAM Administrator Password: The password to log in to the BAM Workbench. The default
password is manager.
22. (Business Activity Monitoring only) Click Initialize to begin the initialization process and, when
initialization is complete, click Next to continue.
23. On the LiveCycle ES Server Information screen, in the Password box, type password. (This password is
the default administrator password; it is recommended that you change the password later.)
24. Click Verify Server Connection to ensure that the information for the default application server is
correct and, when the verification has completed successfully, click Next.
Note: The server information that appears on this screen represents default values for the deployment.
Verifying the server connection helps narrow troubleshooting in case failures occur in the
deployment or validation. If the connection test passes but deployment or validation fails in the
next few steps, connectivity issues can be eliminated from the troubleshooting process.
25. On the LiveCycle Component Deployment screen, click Deploy. The components that are deployed at
this time are Java archive files that plug into the LiveCycle ES service container for purposes of
deploying, orchestrating, and executing services. Click View Progress Log to view the deployment
progress and, when the deployment has completed successfully, click Next.
26. On the LiveCycle Component Deployment Validation screen, click Validate. LiveCycle Configuration
Manager validates that the LiveCycle components (Java archive files) are deployed to and running on
the LiveCycle ES server. Click View Progress Log to view the validation progress and, wen the
validation has completed successfully, click Next.
27. (Reader Extensions ES only) On the LiveCycle Reader Extensions ES Credential Configuration screen,
specify the details that are associated with the Rights credential that activates the solution component
services:
LiveCycle Reader Extensions ES Rights credential: The path and file name of the Rights
credential (.pfx or .p12 file type).
LiveCycle Reader Extensions ES Rights credential password: The password that is associated
with the credential. This password was provided with the credential file.
Name for the configured Rights Credential: The name (or alias) that LiveCycle Configuration
Manager gives the credential when it is configured.
This name appears in the Reader Extensions ES web interface, and the alias that is used to reference the
credential through SDK calls. You can create any unique name for the Rights credential.
Tip: You can skip this step at this time by selecting Configure later using LiveCycle Administration
Console. You can configure the Rights credential by using LiveCycle Administration Console after you
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for JBoss
Next steps
22
complete the deployment. (After logging in to LiveCycle Administration Console, click Home >
Settings >Trust Store Management > Local Credentials.)
Click Configure and then click Next.
28. (Optional) On the LiveCycle ES Samples Import screen, click Import. When the import has completed
successfully, click Next or click Skip LiveCycle Samples Import to import the samples at a later time.
29. On the Summary page, review the tasks performed and click Next. The Next steps screen displays URL
and login information.
30. Click Exit.
Next steps
Now that you have configured and deployed LiveCycle ES, you can do the following tasks:
●
Verify the deployment. (See “Verifying the deployment and accessing LiveCycle Administration
Console” on page 25.)
●
Access LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 25.)
●
Configure PDF Generator ES or PDF Generator 3D ES. (See “Configuring LiveCycle PDF Generator ES or
3D ES” on page 29.)
●
Perform the final setup for Rights Management ES. (See “Final setup for LiveCycle
Rights Management ES” on page 37.)
●
Configure LiveCycle ES solution components to access LDAP. (See “Configuring LiveCycle ES to access
LDAP” on page 37.)
●
Perform watched folder performance-tuning for PDF Generator ES. (See “Setting PDF Generator ES or
3D ES watched folder performance parameters” on page 38.)
●
Enable FIPS mode. (See “Enabling FIPS mode” on page 39.)
●
Enable HTML digital signatures. (See “Configuring HTML digital signature” on page 39.)
●
Configuring Connector for EMC Documentum, Connector for IBM Content Manager, or
Connector for IBM FileNet. (See “Configuring the Connector for EMC Documentum service” on
page 40, “Configuring the Connector for IBM FileNet service” on page 44, or “Configuring the
LiveCycle ES Connector for IBM Content Manager” on page 51.)
●
Set environment variables for PDF Generator ES. (See “Setting environment variables” on page 29.)
●
Uninstall LiveCycle ES. (See “Uninstalling LiveCycle ES” on page 56.)
4
Deploying LiveCycle ES to JBoss Application Server
This chapter describes how to deploy LiveCycle ES to JBoss Application Server:
●
“About deploying LiveCycle ES solution components” on page 23
●
“Summary of deployable components” on page 23
●
“Deploying to JBoss Application Server” on page 23
About deploying LiveCycle ES solution components
Before you deploy LiveCycle ES, ensure that you completed these tasks:
●
Installed the required software and files, and know the location of the directories you will be working
with. If you did not complete this task, see Preparing to Install LiveCycle ES (Single Server).
●
Run LiveCycle Configuration Manager to configure and assemble LiveCycle ES solution components
according to your system and application server requirements. To add a solution component to your
deployment, you can run LiveCycle Configuration Manager to make the changes and then redeploy the
updated EAR file.
If you are deploying LiveCycle ES for the first time, initialize the database by using LiveCycle Configuration
Manager after you deploy the product.
If you are using an external web server, see your web server documentation for information about the
configuration that is required to allow access to the application server.
Summary of deployable components
During the deployment process, you need to deploy the following components for LiveCycle ES:
●
adobe-livecycle-native-jboss-[OS].ear
●
adobe-livecycle-jboss.ear
●
adobe-workspace-client.ear (LiveCycle Process Management ES only)
●
adobe-contentservices.ear (LiveCycle Content Services ES only)
After LiveCycle ES is configured with LiveCycle Configuration Manager (required), these files are located in
the [LiveCycleES root]/configurationManager/export/ directory.
Deploying to JBoss Application Server
Deploy LiveCycle ES solution components to JBoss Application Server by copying the deployable
components to the deploy directory. JBoss Application Server can be running or stopped when you copy
the files to the directory. After you copy the files, start or restart the server to ensure that the services start
correctly.
23
Adobe LiveCycle ES
Deploying LiveCycle ES to JBoss Application Server
Installing and Deploying LiveCycle ES for JBoss
Next steps
24
➤ To deploy LiveCycle ES solution components to JBoss Application Server:
●
Copy the following files from the [LiveCycleES root]/configurationManager/export directory to the
[appserver root]/server/all/deploy directory:
●
adobe-livecycle-native-jboss-[OS].ear
●
adobe-livecycle-jboss.ear
●
adobe-workspace-client.ear (LiveCycle Process Management ES only)
Next steps
You must run LiveCycle Configuration Manager to initialize the database, and to deploy the components
and LiveCycle ES archive files (LCAs).
5
Post-Deployment Activities
This chapter describes how to verify the deployment by accessing the LiveCycle Administration Console
and checking the application server log files. It also describes how to get started using LiveCycle ES
solution components and services after they are installed, configured, and deployed to your application
server:
●
“Verifying the deployment and accessing LiveCycle Administration Console” on page 25
●
“Accessing solution component web applications” on page 26
●
“Accessing the Content Services ES repository” on page 28
●
“Accessing User Management” on page 28
●
“Configuring LiveCycle PDF Generator ES or 3D ES” on page 29
●
“Final setup for LiveCycle Rights Management ES” on page 37
●
“Configuring LiveCycle ES to access LDAP” on page 37
●
“Setting PDF Generator ES or 3D ES watched folder performance parameters” on page 38
●
“Enabling FIPS mode” on page 39
●
“Configuring HTML digital signature” on page 39
●
“Configuring the Document Management service for LiveCycle Content Services ES” on page 40
●
“Configuring the Connector for EMC Documentum service” on page 40
●
“Configuring the Connector for IBM FileNet service” on page 44
●
“Configuring the LiveCycle ES Connector for IBM Content Manager” on page 51
●
“Uninstalling LiveCycle ES” on page 56
After you configure the settings in this chapter, for additional information about configuring your
LiveCycle ES environment for development and production, see Administering LiveCycle ES.
Verifying the deployment and accessing LiveCycle Administration
Console
You can verify the deployment by logging in to LiveCycle Administration Console. If you log in successfully,
then LiveCycle ES is running on the application server and the default user is created in the database.
You can review the application server log files to ensure that components were deployed correctly or to
determine the cause of any deployment issues you may encounter.
Accessing LiveCycle Administration Console
LiveCycle Administration Console is the web-based portal for accessing a variety of configuration pages
where you can set run-time properties that control the way LiveCycle ES operates. When you log in to
LiveCycle Administration Console, you can access User Management, Watched Folder, and Email client
configuration, and administrative configuration options for other services. LiveCycle Administration
25
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Viewing the log files
26
Console also provides access to Applications and Services, which administrators use for managing archives
and deploying services to a production environment.
The default user name and password for logging in is administrator and password. After you log in the first
time, access User Management and change the password. If you have upgraded, the user name and
password remain the same as when they were set by the administrator when was configured.
Before you access LiveCycle Administration Console, LiveCycle ES must be deployed and running on your
application server.
For information about using LiveCycle Administration Console, see Applications and Services Administration
Help.
➤ To access LiveCycle Administration Console:
1. Type the following URL in a web browser:
http://[host name]:[port]/adminui
The default port number for JBoss is 8080.
2. In the User Name box, type administrator and, in the Password box, type password.
3. After you log in, click Services to access the service administration pages or click Settings to access the
pages on which you can administer settings for different solution components.
Viewing the log files
Events, such as run-time or startup errors, are recorded to the application server log files. If you have
problems deploying to the application server, you can use the log files to help you find the problem. You
can open the log files by using any text editor.
Accessing solution component web applications
After LiveCycle ES is deployed, you can access the web applications that are associated with the following
solution components:
●
LiveCycle Reader Extensions ES
●
LiveCycle Workspace ES
●
LiveCycle Rights Management ES
●
LiveCycle Content Services ES
After accessing the web applications by using the default administrator permissions to ensure that they
are accessible, you can create additional users and roles so that others can log in and use the applications.
(See User Management Help.)
➤ To access the Reader Extensions ES web application:
Note: You must apply a Reader Extensions ES credential and apply the user roles for a new user. (See
“Configuring SSL” in Administering LiveCycle ES.)
1. Open a web browser and enter this URL:
http://localhost:8080/ReaderExtensions (local deployment using the default port)
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Accessing Rights Management ES
27
2. Log in using the default user name and password:
User name: administrator
Password: password
Note: You must have administrator or superuser privileges to log in using the default user name and
password. To allow other users to access the Reader Extensions ES web application, you must create
the users in User Management and grant them the Reader Extensions Web Application role .
➤ To access Workspace ES:
1. Open a web browser and enter this URL:
http://localhost:8080/workspace (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
➤ To access the Content Services ES web application:
Note: You must apply the LiveCycle Contentspace Administrator or LiveCycle Contentspace roles for a
new user to login to this web application. To do this, you must create the users in User Management
and grant them the appropriate role.
1. Open a web browser and enter this URL:
●
http://localhost:8080/contentspace (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
Accessing Rights Management ES
You must create a user with the LiveCycle Rights Management End User role in User Management and log
in to the Rights Management ES administrator or end-user applications by using the login information
that is associated with that user.
➤ To access the Rights Management ES end-user web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/edc/Login.do
Note: The administrator user cannot access the Rights Management ES end-user web application. You can
create new users by using LiveCycle Administration Console.
➤ To access the Rights Management ES administration web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/adminui
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Accessing User Management
28
2. Click Services > LiveCycle Rights Management ES. For information about setting up users and roles
for Rights Management ES, see Administering LiveCycle ES.
➤ To assign the LiveCycle Rights Management End User role:
1. Log in to LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 25.)
2. Click Settings > User Management > Users and Groups.
3. In the Find box, type all and, in the In list, select Groups.
4. Click Find and, for the required domains, click All Principals in the list that appears.
5. Click the Role Assignments tab and click Find Roles.
6. In the list of roles, select the check box next to LiveCycle Rights Management End User.
7. Click OK and then click Save.
Accessing User Management
By using User Management, administrators can maintain a database of all users and groups, synchronized
with one or more third-party user directories. User Management provides authentication, authorization,
and user management for LiveCycle ES solution components, including Reader Extensions ES,
Workspace ES, Rights Management ES, Process Management ES, and Forms ES.
➤ To access User Management:
1. Log in to LiveCycle Administration Console.
2. On the home page, click Settings > User Management.
Note: For information about configuring users with User Management, click User Management Help in
the upper-right corner of the User Management page.
Accessing the Content Services ES repository
You can access the Content Services ES repository using:
●
File Transfer Protocol (FTP)
●
Web-based Distributed Authoring and Versioning (WebDAV)
●
Common Internet File Services (CIFS)
➤ To access the Content Services ES repository using FTP:
1. Open a web browser and enter this URL:
ftp://[server name]:[port]
Note: The default port for the Content Services ES repository is port 8021.
2. Log in using your user name and password.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring LiveCycle PDF Generator ES or 3D ES
29
Note: You can not log in to the Content Services ES repository by FTP using the Mozilla FireFox
browser. Use another browser (for example, Internet Explorer) to access the Content Services ES
repository by FTP.
➤ To access the Content Services ES repository using WebDAV:
1. Open Windows Explorer and navigate to My Network Places .
2. Right click and select Add a network place.
3. Enter the following network address:
http://[server name]:[port]/contentspace/webdav
4. Log in using your user name and password.
➤ To access the Content Services ES repository using CIFS:
Note: Your Content Services ES repository must be previously configured to support CIFS access.
1. On a computer running the Windows operating system, click Start > Run.
2. Enter the following:
\\[server name]a
Note: You will not be asked for a user name or password.
Configuring LiveCycle PDF Generator ES or 3D ES
If you installed LiveCycle PDF Generator ES or LiveCycle PDF Generator 3D ES as part of your LiveCycle ES
solution, complete the following tasks:
●
“Setting environment variables” on page 29
●
“Configuring the application server to use HTTP proxy server” on page 30
●
“Setting the Adobe PDF Printer as the default printer” on page 31
●
“Configuring Acrobat 9.0” on page 31
●
“Installing East Asian characters in Windows” on page 32
●
“Adding fonts to PDF Generator ES or PDF Generator 3D ES” on page 32
●
“Installing the IPP client” on page 35
Setting environment variables
If you installed the PDF Generator ES or PDF Generator 3D ES solution component and configured it to
convert files to PDF, for some file formats, you must manually set an environment variable that contains
the absolute path of the executable that is used to start the corresponding application. The table below
lists the native applications that PDF Generator ES or PDF Generator 3D ES requires you to set up
environment variables for.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the application server to use HTTP proxy server
30
Application
Environment variable
Example
Acrobat
Acrobat_PATH
C:\Program
Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe
Note: The Acrobat_PATH environment variable is
case-sensitive.
Adobe
FrameMaker®
FrameMaker_PATH
C:\Program
Files\Adobe\FrameMaker7.1\FrameMaker.exe
Notepad
Notepad_PATH
C:\WINDOWS\Notepad.exe
OpenOffice
OpenOffice_PATH
C:\Program Files\OpenOffice.org 2.0
Adobe
PageMaker®
PageMaker_PATH
C:\Program
Files\Adobe\PageMaker 7.0\PageMaker.exe
WordPerfect
WordPerfect_PATH
C:\Program Files\WordPerfect Office
12\Programs\wpwin12.exe
Note: The environment variable OpenOffice_PATH is set to the installation folder instead of the path to
the executable.
You do not need to set up the paths for Microsoft Office applications such as Word, PowerPoint, Excel,
Visio, and Project, or for AutoCAD. The Generate PDF service starts these applications automatically if they
are installed on the server.
➤ To create a new Windows environment variable:
1. Select Start > Control Panel > System.
2. Click the Advanced tab and click Environment Variables.
3. In the System variables section, click New.
4. Enter the environment variable name you need to set (for example, enter Photoshop_PATH). This
folder is the one that contains the executable file. For example, type the following code:
D:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe
➤ To set the PATH variables on Linux (OpenOffice only):
●
Type the following command:
export OpenOffice_PATH /opt/openoffice.org2
Configuring the application server to use HTTP proxy server
If the computer that LiveCycle ES is running on uses proxy settings to access external websites, the
application server should be started with the following values set as Java virtual machine (JVM)
arguments:
-Dhttp.proxyHost=[server host]
-Dhttp.proxyPort=[server port]
Complete the following procedure to start your application server with HTTP proxy host setting.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Setting the Adobe PDF Printer as the default printer
31
➤ To add the setting to JBoss:
1. From a command line, edit the run script in the [JBOSS HOME]/bin/ directory:
●
(Windows) run.bat
●
(Linux, UNIX) run.sh
2. Add the following text to the script file:
Set JAVA_OPTS=%JAVA_OPTS%
-Dhttp.proxyHost=[server host]
-Dhttp.proxyPort=[server port]
3. Save and close the file.
Setting the Adobe PDF Printer as the default printer
You must set the Adobe PDF Printer to be the default printer on the server. If the Adobe PDF Printer is not
set as the default, PDF Generator ES cannot convert files successfully.
➤ To set the default printer:
1. Select Start > Printers and Faxes.
2. In the Printers and Faxes window, right-click Adobe PDF and select Set as Default Printer.
Configuring Acrobat 9.0
This procedure is required only if you upgraded to or installed Acrobat 9.0 after you completed the
LiveCycle ES installation. Upgrading Acrobat can be completed after you run LiveCycle Configuration
Manager and deploy LiveCycle ES to the application server.
➤ To configure Acrobat 9.0 Professional Extended for use with PDF Generator ES or
PDF Generator 3D ES:
1. If an earlier version (8.1 or earlier) of Acrobat is installed, uninstall it by using Add or Remove Programs
in the Windows Control Panel.
2. Acrobat 9.0 Professional Extended is provided with the LiveCycle ES media or as an option for ESD
downloads.
●
If you are using the media, insert the Acrobat 9.0 Professional Extended CD.
●
If you are using the ESD downloads, download Acrobat 9.0 Professional Extended from your ESD
location.
3. Install Acrobat 9.0 Professional Extended by running the AutoPlay.exe file.
4. Navigate to the additional\scripts folder on the LiveCycle ES installation media.
5. Run the following batch file:
Acrobat_for_PDFG_Configuration.bat [LiveCycleES root]
6. Open Acrobat and select Help > Check for updates > Preferences.
7. Deselect Automatically check for Adobe updates.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Installing East Asian characters in Windows
32
➤ To validate the Acrobat 9.0 Professional Extended installation:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat. If the PDF file opens
successfully, Acrobat 9.0 Professional Extended is installed correctly.
2. If the PDF file does not open correctly, uninstall Acrobat and reinstall it.
Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after the Acrobat installation
is completed and disable the automatic updates for Acrobat.
Set the Acrobat_PATH environment variable to point to Acrobat.exe (such as C:\Program Files\
Adobe\Acrobat 9.0\Acrobat\Acrobat.exe).
➤ To configure native application support:
1. Install and validate Acrobat as described in the previous procedure.
2. Set Adobe PDF printer as the default printer.
3. (PDF Generator 3D ES) Register the DLL file located at [LiveCycle8.2 root]\plugins\x86win32\
PDFG3dAddin.dll.
Installing East Asian characters in Windows
When HTML files are converted to PDF by using PDF Generator ES or PDF Generator 3D ES, some East
Asian languages, such as Japanese, Korean, and Chinese, and also right-to-left languages, such as Arabic,
Armenian, Georgian, Hebrew, Indic, Thai, and Vietnamese, may not be displayed in the PDF file.
To ensure that these languages are displayed in Windows, appropriate fonts must be present on the client
and server.
➤ To install East Asian characters in Windows:
1. Select Start > Control Panel and open Regional and Language Options.
2. Click the Languages tab and select Install Files for East Asian Languages.
3. Click the Advanced tab and select all the options under Code Page Conversion Tables.
If converted PDF files are still missing fonts, verify that the Arial Unicode MS (TrueType) font (ARIALUNI.TTF)
is present in the C:\WINDOWS\Fonts directory.
Adding fonts to PDF Generator ES or PDF Generator 3D ES
LiveCycle ES provides a central repository of fonts named Adobe LiveCycle ES Fonts Management, which is
accessible to all LiveCycle ES solution components. The Fonts Management module is a central font
repository for all fonts that are accessible to and shared by various LiveCycle ES solution components.
However, PDF Generator ES or PDF Generator 3D ES frequently needs to start external (non-LiveCycle ES)
applications on the server that cannot be configured to use the LiveCycle ES fonts repository. This section
describes how to make the extra fonts available to these applications so that PDF documents that are
created by using PDF Generator ES or PDF Generator 3D ES can use these extra fonts.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Post-Deployment Activities
Adding fonts to PDF Generator ES or PDF Generator 3D ES
33
Non-Adobe applications
The following list contains non-LiveCycle ES applications that PDF Generator ES or PDF Generator 3D ES
can use for PDF generation on the server side:
Windows-only Applications
●
Microsoft Office Word
●
Microsoft Office Excel
●
Microsoft Office PowerPoint
●
Microsoft Office Project
●
Microsoft Office Visio
●
Microsoft Office Publisher
●
AutoDesk AutoCAD
●
Corel WordPerfect
●
Adobe Photoshop CS
●
Adobe FrameMaker
●
Adobe PageMaker
●
Adobe Acrobat Professional Extended
Multiplatform applications
●
OpenOffice Writer
●
OpenOffice Calc
●
OpenOffice Draw
●
OpenOffice Impress
Note: In addition to these applications, your list may include additional applictions that you added.
Of the above applications, the OpenOffice Suite (which includes Writer, Calc, Draw, and Impress) is
available on Windows, Solaris, and Linux platforms, whereas other applications are available on Windows
only.
Adding new fonts to Windows applications only
All the Windows-only applications that are mentioned above can access all the fonts that are available in
the C:\Windows\Fonts (or equivalent) folder. In addition to C:\Windows\Fonts, each of these applications
may have its own private fonts folders.
Therefore, if you plan to add any custom fonts to the LiveCycle ES fonts repository, you must ensure that
the same fonts are available to the Windows-only applications also by copying these fonts to either
C:\Windows\Fonts or to an equivalent folder.
Your custom fonts must be licensed under an agreement that allows you to use them with the applications
that have access to these fonts.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring HTML to PDF conversions
34
Adding new fonts to OpenOffice Suite
Adding custom fonts to OpenOffice Suite is explained on the OpenOffice Fonts-FAQ page at
http://wiki.services.openoffice.org.
In addition, OpenOffice Suite has these resources about the fonts-related behavior:
●
OpenOffice Fonts Troubleshooting Guide at http://www.openoffice.org/FAQs/fontguide.html. Some of
the text in this guide is applicable only to OpenOffice 1.x and therefore may be obsolete for OpenOffice
2.x
●
Importing Fonts into OpenOffice 2.1 at http://openoffice.blogs.com/openoffice/2007/02/
font_import_wiz.html. Even though this blog mentions OpenOffice 2.1, the instructions that are
mentioned should be applicable to OpenOffice 2.2 and later.
Adding new fonts to other applications
If you extended PDF Generator ES by adding support for PDF creation by using other applications, see the
user guide that is applicable to the corresponding application to determine the best procedure to use to
add new fonts to that application. In Windows, copying your custom fonts to the C:\Windows\Fonts (or
equivalent) folder should be sufficient.
Configuring HTML to PDF conversions
The HTML-to-PDF conversion process is designed to use the settings from Acrobat 9.0, thereby overriding
the settings from LiveCycle PDF Generator ES.
Note: This configuration is required to enable the HTML-to-PDF conversion process, otherwise this
conversion type will fail.
➤ To configure the HTML-to-PDF conversion:
1. Install and validate Acrobat as described in “Configuring Acrobat 9.0” on page 31.
2. Locate the pdfgen.api file in the [LiveCycle8.2 root]\plugins\x86win32 directory and copy it to
[Acrobat9.0 root]\Acrobat\plug_ins directory.
Enabling support for Unicode fonts in HTML to PDF conversions
To enable PDF Generator ES or PDF Generator 3D ES to generate PDF files from HTML source files that
contain Unicode fonts, complete the following steps.
Caution: The HTML-to-PDF conversion will fail if a zipped input file contains HTML files with double-byte
characters in the filenames. To avoid this problem, do not use double-byte characters when
naming HTML files.
1. Copy the Unicode font to any of the following directories as appropriate for your system:
●
Windows
[Windows root]\windows\fonts
[Windows root]\winnt\fonts
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
●
Installing the IPP client
35
UNIX
/usr/X/lib/X11/fonts/TrueType
/usr/openwin/lib/X11/fonts/TrueType
/usr/share/fonts/default/TrueType
/usr/X11R6/lib/X11/fonts/ttf
/usr/X11R6/lib/X11/fonts/truetype
/usr/X11R6/lib/X11/fonts/TrueType
/usr/X11R6/lib/X11/fonts/TTF
/Users/cfqauser/Library/Fonts
/System/Library/Fonts
/Library/Fonts
/Users/ + System.getProperty(<user name>, root) + /Library/Fonts
System.getProperty(JAVA_HOME) + /lib/fonts
2. Modify the font-name mapping in the cffont.properties file located in the
[LiveCycle8.2 root]/adobe-generatepdf-dsc.jar file:
●
Unpackage this archive, and locate the cffont.properties file and open it in an editor.
●
In the comma-separated list of Java font names, add a map to your Unicode system font for each
font type, as shown in these examples where kochi mincho is the name of your Unicode system
font:
dialog=Arial, Helvetica, kochi mincho
dialog.bold=Arial Bold, Helvetica-Bold, kochi mincho ...
●
Save and close the properties file, and then repackage and redeploy the adobe-generatepdf-dsc.jar
file.
Note: On a Japanese operating system, specify the font mapping in the cffont.properties.ja file as well,
which takes precedence over the standard cffont.properties file.
Tip: Fonts in the list are searched from left to right, using the first font found. HTML-to-PDF conversion
logs return a list of all the font names that are found in the system. To determine the font name you
need to map, add the font to one of the directories above, restart the server and run a conversion. You
can determine from the log files the font name to use for mapping.
To embed the font in the generated PDF files, set the embedFonts property in the cffont.properties file to
true (the default is false).
Installing the IPP client
PDF Generator ES includes an Internet Printing Protocol (IPP) client installer for installation of the
PDF Generator ES Internet printer on a client computer. After the installation is complete, a
PDF Generator ES printer is added to the list of existing printers on the client computer. This printer can
then be used to send documents for conversion to PDF.
Note: The PDF Generator ES IPP Client (wizard) is supported on 32-bit Windows platforms only.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Installing the IPP client
36
If the IPP Client fails to install on Windows or if you want to install the IPP printer on UNIX or Linux
platforms, use the operating system’s native Add Printer utility and configure it as described in “To
configure IPP Printer on Windows using the native Add Printer wizard:” on page 36.
➤ To install the PDF Generator ES IPP Client:
1. Ensure that you successfully installed PDF Generator ES on your server.
2. From a Windows client computer, enter the following URL in your web browser, where [server] is the
name of the server where you installed PDF Generator ES and [port] is the application server port
used:
http://[server]:[port]/pdfg-ipp/install
3. On the Configure Internet Port screen, select Use the specified user account and provide the
credentials of a LiveCycle user who has the PDFG Administrator/User role. This user must also have an
email address that can be used to receive the converted files. To have this security setting apply to all
users on the client computer, select Use the same security options for all users, and then click OK.
Upon successful installation, a dialog box appears, indicating that “The Printer Adobe LiveCycle
PDF Generator ES has been successfully installed.”
4. Click OK. You will now have a printer named Adobe LiveCycle PDF Generator ES in your list of available
printers.
➤ To configure IPP Printer on Windows using the native Add Printer wizard:
1. Click Start > Printers and Faxes and double-click Add Printer.
2. Click Next, select A network printer, or a printer attached to another computer, and then click
Next.
3. Select Connect to a printer on the internet or on a home or office network and type the following
URL for the IPP printer, where [server] is the server name and [port] is the port number where
the server is running:
http://[server]:[port]/pdfg-ipp/printer
4. On the Configure Internet Port screen, select Use the specified user account and provide valid User
Management credentials.
5. In the Printer Driver Select box, choose any standard PostScript-based printer driver (for example, HP
Color LaserJet PS).
6. Complete the installation by choosing appropriate options (for example, setting this printer as default).
Note: The user credentials used while adding the printer must have a valid email ID configured in User
Management to receive the response.
7. Configure the email service’s sendmail service. Provide a valid SMTP server and authentication
information in the service’s configuration options.
➤ To install and configure the PDF Generator ES IPP Client using Proxy server port forwarding
1. Configure port forwarding on the CC Proxy server on a particular port to the LiveCycle ES server, and
disable the authentication at proxy server level (since LiveCycle ES uses its own authentication). If a
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Post-Deployment Activities
Final setup for LiveCycle Rights Management ES
37
client connects to this Proxy server on the forwarded port, then all the requests will be forwarded to
the LiveCycle ES server.
2. Install PDFG-IPP printer using the following URL:
http://[proxy server]:[forwarded port]/pdfg-ipp/install.
3. Provide the necessary credentials for authentication of the IPP printer.
4. The IPP printer will be installed on the client machine which you can use for PDF conversion using the
firewall protected LiveCycle ES server.
Final setup for LiveCycle Rights Management ES
Rights Management ES requires the application server to be configured to use SSL. (See
Administering LiveCycle ES.)
Configuring LiveCycle ES to access LDAP
If you configured LDAP for LiveCycle 7.x products, those settings are migrated during the upgrade process,
and you do not need to perform the steps in this section. If you did not previously configure LDAP, you can
use the following procedure as a guideline when configuring User Management to support authentication
using LDAP.
➤ To configure User Management with LDAP (Enterprise Domain):
1. Open a web browser, navigate to http://[host name]:[port]/adminui and log in. (See “Accessing
LiveCycle Administration Console” on page 25.)
2. Click Settings > User Management > Domain Management, and then click New Enterprise
Domain.
3. In the ID box, type a unique identifier for the domain and, in the Name box, type a descriptive name for
the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for
the ID. (See “Adding enterprise domains” in User Management Help.)
4. Click Add Authentication and, in the Authentication Provider list, select LDAP.
5. Click OK.
6. Click Add Directory and, in the Profile Name box, type a name for your LDAP profile.
7. Click Next.
8. Specify values in the Server, Port, SSL, and Binding boxes, and in the Populate Page with box, select
a directory settings option such as Default Sun ONE values. (See “Directory settings” in User
Management Help.)
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Setting PDF Generator ES or 3D ES watched folder performance parameters
38
9. (Optional) Test your configuration:
●
Click Test. The screen displays a message indicating either a successful server test or any
configuration errors that exist.
10. Click Next and configure the User Settings as required. (See “Directory settings” in User Management
Help.)
11. (Optional) Test your configuration:
●
Click Test.
●
In the Search Filter box, verify the search filter or specify a new search filter, and then click Submit.
The screen displays a list of entries that match the search criteria.
●
Click Close to return to the User Settings screen.
12. Click Next configure the Group Settings as required. (See “Directory settings” in User Management
Help.)
13. (Optional) Test your configuration:
●
Click Test.
●
In the Search Filter box, verify the search filter or specify a new search filter, and then click Submit.
The screen displays a list of entries that match the search criteria.
●
Click Close to return to the Group Settings screen.
14. Click Finish to exit the New Directory page and then click OK to exit.
➤ To configure User Management with LDAP (Local Domain):
1. Open a web browser, navigate to http://[host name]:[port]/adminui, and log in. (See “Accessing
LiveCycle Administration Console” on page 25.)
2. Click Settings > User Management > Domain Management, and then click New Local Domain.
Setting PDF Generator ES or 3D ES watched folder performance
parameters
To avoid java.io.IOException error messages indicating that not enough disk space is available to
perform PDF conversions by using a watched folder, you can modify the settings for PDF Generator ES
PDF Generator 3D ES in LiveCycle Administration Console.
➤ To set performance parameters for PDF Generator ES or PDF Generator 3D ES:
1. Log in to LiveCycle Administration Console and click Services > Applications and Services > Service
Management.
2. In the list of services, navigate to and click PDFGConfigService, and then set the following values:
●
PDFG Cleanup Scan Seconds: 1800
●
Job Expiration Seconds: 6000
●
Server Conversion Timeout: Change the default of 270 to a higher value, such as 450.
3. Click Save and restart the server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Post-Deployment Activities
Enabling FIPS mode
39
4. Click Next and, on the next screen, click Advanced Targeting.
5. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
6. Click Next and, on the next screen, click Advanced Targeting.
7. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
8. Click Next and, on the next screen, click Advanced Targeting.
9. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
Enabling FIPS mode
LiveCycle ES provides a FIPS mode to restrict data protection to Federal Information Processing Standard
(FIPS) 140-2 approved algorithms using the RSA BSAFE Crypto-C 2.1 encryption module.
If you did not enable this option by using LiveCycle Configuration Manager during LiveCycle ES
configuration or if you enable it but want to turn it off, you can change this setting through LiveCycle
Administration Console.
Modifying FIPS mode requires you to restart the server.
FIPS mode does not support Acrobat versions earlier than 7.0. If FIPS mode is enabled and the Encrypt
With Password and Remove Password processes include the Acrobat 5 setting, the process fails.
In general, when FIPS is enabled, the Assembler service does not apply password encryption to any
document. If this is attempted, a FIPSModeException is thrown, indicating that “Password encryption
is not permitted in FIPS mode.” Additionally, the PDFsFromBookmarks element is not supported in FIPS
mode when the base document is password-encrypted.
➤ To turn FIPS mode on or off:
1. Log in to LiveCycle Administration Console.
2. Click Settings > Core System > Core Configurations > Configurations.
3. Select Enable FIPS to enable FIPS mode or deselect it to disable FIPS mode.
4. Click OK and restart the application server.
Note: LiveCycle ES software does not validate code to ensure FIPS compatibility. It provides a FIPS
operation mode so that FIPS-approved algorithms are used for cryptographic services from the
FIPS-approved libraries (RSA).
Configuring HTML digital signature
To use the HTML digital signature feature of Forms ES, complete the following procedure.
➤ To enable HTML digital signature:
1. Manually deploy the [LivecycleES root]/deploy/adobe-forms-ds.ear file to your application server.
2. Log in to LiveCycle Administration Console and click Service > LiveCycle Forms ES.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the Document Management service for LiveCycle Content Services ES
40
3. Select HTML Digital Signature Enabled and then click Save.
Configuring the Document Management service for
LiveCycle Content Services ES
If you installed Content Services ES and your application server is running on a non-default port (that is, a
port other than 8080 in JBoss), modify the port that the Document Management service uses.
➤ To modify the port:
1. Log in to LiveCycle Administration Console and click Services > Applications and Services > Service
Management.
2. In the list, select DocumentManagementService.
3. On the Configuration tab, in the HTTP Port box, specify the port number you are using, and then click
Save.
Configuring the Connector for EMC Documentum service
If you installed the Connector for EMC Documentum service as part of your LiveCycle ES solution,
complete the following procedure to configure the service to connect to the Documentum repository.
➤ To configure Connector for EMC Documentum:
1. Locate the adobe-component-ext.properties file in the [JBOSS HOME]/bin folder (if the file does not
exist, create it).
2. Add a new system property that provides the following Documentum Foundation Classes JAR files
(and for the Connector for EMC Documentum 5.3 only, the location of the Documentum Content
Server config folder):
●
dfc.jar
●
(Connector for EMC Documentum 5.3) dfcbase.jar
●
(Connector for EMC Documentum 6.0) aspectjrt.jar
The new system property should take on this form:
[component id].ext=[JAR files and/or folders]
For example, using default Content Server and Documentum Foundation Classes installations, add to
the file one of the following system properties on a new line, with no line breaks, and end the line with
a carriage return:
●
Connector for EMC Documentum 5.3 only:
com.adobe.livecycle.ConnectorforEMCDocumentum.ext=
C:/Documentum/Config,
C:/Program Files/Documentum/Shared/dfc.jar,
C:/Program Files/Documentum/Shared/dfcbase.jar
●
Connector for EMC Documentum 6.0 only:
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the Connector for EMC Documentum service
41
com.adobe.livecycle.ConnectorforEMCDocumentum.ext=
C:/Program Files/Documentum/Shared/dfc.jar,
C:/Program Files/Documentum/Shared/aspectjrt.jar
Note: The above text contains formatting characters for line breaks. If you copy and paste this text, you
must remove the formatting characters.
3. If JBoss Application Server is not currently running, start the server. Otherwise, stop and then restart
the server.
4. Open a web browser and enter this URL:
http://localhost:8080/adminui (local deployment using the default port)
5. Log in using the default user name and password:
User name: administrator
Password: password
6. Navigate to Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings
and perform these tasks:
●
Type all the required Documentum repository information.
●
To use Documentum as your repository provider, under Repository Service Provider Information,
select EMC Documentum Repository Provider, and then click Save. (For more information, click
the Help link in the upper-right corner of the page in the EMC Documentum Help. )
7. (Optional) Navigate to Services > LiveCycle ES Connector for EMC Documentum > Repository
Credentials Settings, click Add, specify the Docbase information, and then click Save. (For more
information, click Help in the upper-right corner.)
8. Navigate to Services > Applications and Services > Service Management and select these services:
●
EMCDocumentumAuthProviderService
●
EMCDocumentumContentRepositoryConnector
●
EMCDocumentumRepositoryProvider
9. Click Start. If any of the services do not start correctly, check the settings entered in step 6.
10. 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 by using the LiveCycle ES super
administrator credentials (by default, Administrator and password).
You have now completed the required steps for this procedure. Use the credentials provided in step 6
for accessing the default repository in this case and use the default LiveCycle ES authorization service.
11. Restart JBoss Application Server.
12. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the Connector for EMC Documentum service
42
13. Click New Enterprise Domain, and type a domain ID and name. The domain ID is the unique identifier
for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for
the ID. (See “Adding enterprise domains” in User Management Help.)
14. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Select EMCDocumentumAuthProvider and then click OK.
15. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP, and then click OK.
16. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required.
●
Click Next, configure the user settings, click Next, configure group settings, as required, and then
click Next.
For details about the settings, click User Management Help in the upper-right corner of the page.
17. Click OK to exit the Add Directory page and then click OK again.
18. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
19. Navigate to Settings > User Management > Users and Groups.
20. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users that you assign roles to. For more information , click User Management
Help in the upper-right corner of the page.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the Connector for EMC Documentum service
43
21. Start Workbench ES and log in by using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The Documentum repository should now be visible in the Resources view within Workbench ES. If you
do not log in using the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 6.
22. (Optional) If you intend to install the LiveCycle ES Samples for Connector for EMC Documentum, create
a Documentum repository named Samples, and then install the samples in that repository.
After you configure the Connector for EMC Documentum service, it is recommended that you see
Administering LiveCycle ES for information about configuring Workbench ES functions properly with your
Documentum repository.
Creating the XDP MIME format in your Documentum repository
Before users can store and retrieve XDP files from a Documentum repository, you must do one of these
tasks:
●
Create a corresponding XDP format in each repository where users will access XDP files.
●
Configure the Connector for EMC Documentum service to use a Documentum Administrator account
when accessing the Documentum repository. In this case, the Connector for EMC Documentum service
uses the XDP format whenever it is required.
➤ To create the XDP format on Documentum Content Server using Documentum Administrator:
1. Log in to Documentum Administrator.
2. Click Formats and then select File > New > Format.
3. Type the following information in the corresponding fields:
Name: xdp
Default File Extension: xdp
Mime Type: application/xdp
4. Repeat steps 1 to 3 for all other Documentum repositories where users will store XDP files.
➤ To configure the Connector for EMC Documentum service to use a Documentum Administrator:
1. Open a web browser and enter this URL:
http://localhost:[port]/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the Connector for IBM FileNet service
44
4. Under Documentum Principal Credentials Information, update the following information and then
click Save:
User Name: [Documentum Administrator user name]
Password: [Documentum Administrator password]
5. Click Repository Credentials Settings, select a repository from the list or, if none exist, click Add.
6. Provide the appropriate information in the corresponding fields and then click Save:
Repository Name: [Repository Name]
Repository Credentials User Name: [Documentum Administrator user name]
Repository Credentials Password: [Documentum Administrator password]
7. Repeat steps 5 to 6 for all repositories where users will store XDP files.
Configuring the Connector for IBM FileNet service
If you installed the Connector for IBM FileNet service as part of your LiveCycle ES solution, you must
configure the service to connect to the FileNet object store. See one of the following sections appropriate
to your version of IBM FileNet:
●
“Configuring the connector using FileNet 3.5” on page 44
●
“Configuring the connector using FileNet 4.0.1” on page 47)
Configuring the connector using FileNet 3.5
Complete the following procedure to configure the Connector for IBM FileNet service using FileNet 3.5.
➤ To configure the connector using FileNet 3.5:
1. Locate the adobe-component-ext.properties file in the [appserver root]/bin folder (if the file does not
exist, create it)
2. Add a new system property that provides the location of the following FileNet Application Engine JAR
files:
●
activation.jar
●
javaapi.jar
●
log4j-1.2.8.jar
●
mailapi.jar
●
p8cjares.jar
●
soap.jar
●
xercesimpl.jar
●
xml-apis.jar
●
(optional) pe.jar
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the connector using FileNet 3.5
45
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service.
The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system,
add to the file the following system property on a new line, with no line breaks, and end the line with a
carriage return:
Note: The following text contains formatting characters for line breaks. If you copy this text to a location
outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext=
C:/Program Files/FileNet/lib2/activation.jar,
C:/Program Files/FileNet/lib2/javaapi.jar,
C:/Program Files/FileNet/lib2/log4j-1.2.8.jar,
C:/Program Files/FileNet/lib2/mailapi.jar,
C:/Program Files/FileNet/lib2/p8cjares.jar,
C:/Program Files/FileNet/lib2/soap.jar,
C:/Program Files/FileNet/lib2/xercesImpl.jar,
C:/Program Files/FileNet/lib2/xml-apis.jar,
C:/Program Files/FileNet/lib2/pe.jar
Note: Add the text C:/Program Files/FileNet/lib2/pe.jar only if your deployment uses the
IBMFileNetProcessEngineConnector service.
3. If JBoss Application Server is not currently running, start the server. Otherwise, stop and then restart
the server.
4. Open a web browser and enter this URL:
http://localhost:8080/adminui (local deployment using the default port)
5. Log in using the default user name and password:
User name: administrator
Password: password
6. Click Services > LiveCycle ES Connector for IBM FileNet.
7. Provide all the required FileNet repository information and, under Repository Service Provider
Information, select IBM FileNet Repository Provider.
If your deployment uses the optional process engine service, under Process Engine Settings, select Use
Process Engine Connector Service and specify the process engine settings. For more information,
click the Help link on the upper-right corner of the page.
Note: The credentials you provide in this step are validated later when you start the IBM FileNet
repository services. If the credentials are not valid, an error is thrown and the services will not
start.
8. Click Save and then navigate to Services > Applications and Services > Service Management.
9. Select the check box next to each of the following services and then click Start:
●
IBMFileNetAuthProviderService
●
IBMFileNetContentRepositoryConnector
●
IBMFileNetRepositoryProvider
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
●
Configuring the connector using FileNet 3.5
46
IBMFileNetProcessEngineConnector (if configured)
If any of the services do not start correctly, verify the settings entered in step 7.
10. Do one of the following tasks:
●
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a
FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the
FileNet Authorization service overrides the default LiveCycle ES authorization and must be
configured to log in to Workbench ES by using FileNet credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super
administrator credentials (by default, Administrator and password). The credentials provided in step
7 use the default LiveCycle ES authorization service for accessing the default repository in this case.
11. Restart JBoss Application Server.
12. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
13. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier
for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for
the ID. (See “Adding enterprise domains” in User Management Help.)
14. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Select IBMFileNetAuthProviderService and then click OK.
15. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
16. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the settings, click the Help link in the upper-right corner of the page.
17. Click OK to exit the Add Directory page and then click OK again.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the connector using FileNet 4.0.1
47
18. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
19. Navigate to Settings > User Management > Users and Groups.
20. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the
upper-right corner of the page.
21. Start Workbench ES and log in using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The FileNet object store should now be visible in the Resources view within Workbench ES. If you do
not log in using [email protected]_name, Workbench ES attempts to log in to the default repository
specified in step 7.
22. (Optional) If you intend to install the LiveCycle ES samples for Connector for IBM FileNet, create a
FileNet object store named Samples and then install the samples in that object store.
After you configure your Connector for IBM FileNet service, it is recommended that you see Administering
LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet
repository.
Configuring the connector using FileNet 4.0.1
Complete the following procedure to configure the Connector for IBM FileNet service using FileNet 4.0.1.
➤ To configure the connector using FileNet 4.0.1 and CEWS transport:
1. Open the application server run file in a text editor. The run file is as follows:
●
(Windows) [appserver root]/bin/run.bat
●
(UNIX) [appserver root]/bin/run.sh
2. Add the location of the FileNet Configuration files as a Java option to the application server start
command.
-Dwasp.location=/<configuration files location>
For example, using a default FileNet Application Engine installation on a Windows operating system,
add this Java option:
-Dwasp.location=C:/Progra~1/FileNet/AE/CE_API/wsi
Note: If JBoss is running as a service, add the Java option in the registry where other JVM arguments
are defined.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the connector using FileNet 4.0.1
48
3. Save the edited file.
4. If your deployment uses the Process Engine Connector service, copy this file:
[appserver root]\client\logkit.jar to the directory [appserver root]\server\all\lib.
5. Locate the adobe-component-ext.properties file in the [appserver root]/bin folder (if the file does not
exist, create it).
6. Add a new system property that provides the location of these FileNet Application Engine JAR files:
●
javaapi.jar
●
log4j-1.2.13.jar
●
soap.jar
●
wasp.jar
●
builtin_serialization.jar
●
wsdl_api.jar
●
jaxm.jar
●
jaxrpc.jar
●
saaj.jar
●
jetty.jar
●
runner.jar
●
p8cjares.jar
●
Jace.jar
●
(optional) pe.jar
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service.
The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system,
add the following system property on a new line with no line breaks and end the line with a carriage
return:
Note: The following text contains formatting characters for line breaks. If you copy this text to a location
outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext=
C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar,
C:/Program Files/FileNet/AE/CE_API/lib2/log4j-1.2.13.jar,
C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/soap.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/wasp.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/wsdl_api.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxm.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxrpc.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/saaj.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jetty.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/runner.jar,
C:/Program Files/FileNet/AE/CE_API/lib2/p8cjares.jar,
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the connector using FileNet 4.0.1
49
C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar,
C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar
Note: Add C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar only if your
deployment uses the IBMFileNetProcessEngineConnector service.
7. (FileNet Process Engine Connector only) Using a text editor, create a file with the following content as a
single line and end the line with a carriage return:
RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/
wsi/FNCEWS40DIME/
8. Save the file as WCMApiConfig.properties in a separate folder, and add the location of the folder that
contains the WCMApiConfig.properties file to the adobe-component-ext.properties file.
For example, if you save the file as c:/pe_config/WCMApiConfig.properties, add the path c:/pe_config
to the adobe-component-ext.properties file.
9. Locate the login-config.xml file in the [appserver root]/server/all/conf folder and add the following
application policy as a child of the <policy> node:
<application-policy name = "FileNetP8WSI">
<authentication>
<login-module code = "com.filenet.api.util.WSILoginModule" flag =
"required" />
</authentication>
</application-policy>
10. (FileNet Process Engine Connector only) If your deployment uses the process engine, add the following
node to the login-config file:
<application-policy name = "FileNetP8">
<authentication>
<login-module code = "com.filenet.api.util.WSILoginModule" flag =
"required" />
</authentication>
</application-policy>
11. If JBoss Application Server is not currently running, start the server. Otherwise, stop and then restart
the server.
12. Open a web browser and enter this URL:
http://localhost:8080/adminui (local deployment using the default port)
13. Log in using the default user name and password:
User name: administrator
Password: password
14. Click Services > LiveCycle ES Connector for IBM FileNet.
15. Provide all of the required FileNet repository information and, under Repository Service Provider
Information, select IBM FileNet Repository Provider.
If your deployment uses the optional process engine service, under Process Engine Settings, select Use
Process Engine Connector Service and specify the process engine settings. For more information,
click the Help link in the upper-right corner of the page.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the connector using FileNet 4.0.1
50
Note: The credentials that you provide in this step are validated later when you start the IBM FileNet
repository services. If the credentials are not valid, an error is thrown and the services will not
start.
16. Click Save and navigate to Services > Applications and Services > Service Management.
17. Select the check box next to each of these services and then click Start:
●
IBMFileNetAuthProviderService
●
IBMFileNetContentRepositoryConnector
●
IBMFileNetRepositoryProvider
●
IBMFileNetProcessEngineConnector (if configured)
If any of the services do not start correctly, verify the settings entered in step 15.
18. Do one of the following tasks:
●
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a
FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the
FileNet Authorization service overrides the default LiveCycle ES authorization and must be
configured to log in to Workbench ES by using FileNet credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super
administrator credentials (by default, Administrator and password). The credentials provided in step
15 use the default LiveCycle ES authorization service for accessing the default repository in this
case.
19. Restart JBoss Application Server.
20. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
21. Click New Enterprise Domain and then type a domain ID and name. The domain ID is the unique
identifier for the domain. The name is a descriptive name for the domain.
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for
the ID. (See “Adding enterprise domains” in User Management Help.)
22. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Slect IBMFileNetAuthProviderService and then click OK.
23. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
24. Add an LDAP directory:
●
Click Add Directory and, 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 JBoss
Configuring the LiveCycle ES Connector for IBM Content Manager
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
51
For details about the settings, click Help link in the upper-right corner of the page.
25. Click OK to exit the Add Directory page, and then click OK again.
26. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
27. Navigate to Settings > User Management > Users and Groups.
28. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the
upper-right corner of the page.
29. Start Workbench ES and log in using the following credentials:
User name: [username]@[repository_name]
Password: [password]
The FileNet object store should now be visible in the Resources view within Workbench ES. If you do
not log in using the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 15.
30. (Optional) If you intend to install the LiveCycle ES Samples for Connector for IBM FileNet, create a
FileNet object store named Samples and install the samples in that object store.
After you configure your Connector for IBM FileNet service, it is recommended that you see Administering
LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet
repository.
Configuring the LiveCycle ES Connector for IBM Content Manager
If you installed the Connector for IBM Content Manager service as part of your LiveCycle ES solution,
complete the following procedure to configure the service to connect to the IBM Content Manager data
store.
➤ To configure Connector for IBM Content Manager:
1. Locate the adobe-component-ext.properties file in the [JBOSS HOME]/bin folder. If the file does not
exist, create it. Add a new system property that provides the location of the following IBM II4C JAR Files,
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the LiveCycle ES Connector for IBM Content Manager
52
Config folder that contains the IBM II4C property files and a ZIP file from DB2 Universal Database Client
installation:
●
Clio4CM.jar
●
cmb81.jar
●
cmbcm81.jar
●
cmbdb281.jar
●
cmbdb2c81.jar
●
cmbfed81.jar
●
cmbfedc81.jar
●
cmbicm81.jar
●
cmbicmc81.jar
●
cmbicmcup.jar
●
cmbjdbc81.jar
●
cmbjdbcc81.jar
●
cmblog4j81.jar
●
cmbsdk81.jar
●
cmbservlets81.jar
●
cmbtag81.jar
●
cmbupes81.jar
●
cmbutil81.jar
●
cmbutilfed81.jar
●
cmbutilicm81.jar
●
cmbutiljdbc81.jar
●
cmbview81.jar
●
cmbwas81.jar
●
cmbwcm81.jar
●
cmbwebservices.jar
●
cmbxmlmap.jar
●
cmbxmlservice.jar
●
common.jar
●
common.resources.jar
●
ecore.jar
●
ecore.resources.jar
●
ecore.xmi.jar
●
icmadm81.jar
●
icmrm81.jar
●
icmsdk81.jar
●
jcache.jar
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the LiveCycle ES Connector for IBM Content Manager
●
log4j-1.2.8.jar
●
NLVLog.jar
●
xalan.jar
●
xerces.jar
●
xsd.jar
●
xsd.resources.jar
●
cmgmt (copy this folder and its contents)
●
db2java.zip
The new system property look like this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default DB2 Universal Database Client and II4C installation, in the file, add the
following system property on a new line, with no line breaks, and end the line with a carriage return:
com.adobe.livecycle.ConnectorforIBMCM.ext=
C:/Program Files/IBM/db2cmv8/lib/Clio4CM.jar,
C:/Program Files/IBM/db2cmv8/lib/cmb81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbcm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbdb281.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbdb2c81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbfed81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbfedc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbicm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbicmc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbicmcup.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbjdbc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbjdbcc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmblog4j81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbsdk81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbservlets81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbtag81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbupes81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutil81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutilfed81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutilicm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbutiljdbc81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbview81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbwas81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbwcm81.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbwebservices.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbxmlmap.jar,
C:/Program Files/IBM/db2cmv8/lib/cmbxmlservice.jar,
C:/Program Files/IBM/db2cmv8/lib/common.jar,
C:/Program Files/IBM/db2cmv8/lib/common.resources.jar,
C:/Program Files/IBM/db2cmv8/lib/ecore.jar,
C:/Program Files/IBM/db2cmv8/lib/ecore.resources.jar,
C:/Program Files/IBM/db2cmv8/lib/ecore.xmi.jar,
C:/Program Files/IBM/db2cmv8/lib/icmadm81.jar,
C:/Program Files/IBM/db2cmv8/lib/icmrm81.jar,
C:/Program Files/IBM/db2cmv8/lib/icmsdk81.jar,
C:/Program Files/IBM/db2cmv8/lib/jcache.jar,
C:/Program Files/IBM/db2cmv8/lib/log4j-1.2.8.jar,
53
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
Configuring the LiveCycle ES Connector for IBM Content Manager
54
Files/IBM/db2cmv8/lib/NLVLog.jar,
Files/IBM/db2cmv8/lib/xalan.jar,
Files/IBM/db2cmv8/lib/xerces.jar,
Files/IBM/db2cmv8/lib/xsd.jar,
Files/IBM/db2cmv8/lib/xsd.resources.jar,
Files/IBM/db2cmv8/cmgmt,
Files/IBM/SQLLIB/java/db2java.zip
2. If JBoss Application Server is not currently running, start the server; otherwise, stop and then restart the
server.
You can now connect to the IBM Content Manager data store from the IBMCMConnectorService Property
Sheets by using the Use User Credentials as the login mode.
You have now completed the required steps for this procedure.
(Optional) If you want to connect to IBM Content Manager data store from IBMCMConnectorService
Property Sheets by using the Use Credentials From Process Context as the login mode, complete the
following procedure.
➤ To connect using Use Credentials from process context login mode:
1. Open a web browser and enter this URL:
http://localhost:8080/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Services > LiveCycle ES Connector for IBM Content Manager > Configuration Settings.
4. Type all of the required repository information and click Save. For more information about the
IBM Content Manager repository information, click the Help link in the upper-right corner of the page.
5. Do one of the these tasks:
●
To use the IBM Content Manager Authorization service (IBMCMProviderService) to use content from
an IBM Content Manager data store, in the Processes view of Workbench ES, continue with this
procedure. Using the IBM Content Manager Authorization service overrides the default LiveCycle ES
authorization and must be configured to log in to Workbench ES by using IBM Content Manager
credentials.
●
To use the System Credentials provided in step 7 to use content from an IBM Content Manager data
store, in the Processes view of Workbench ES, log in to Workbench ES by using the LiveCycle ES
super administrator credentials (by default, Administrator and password). You have now
completed the required steps for this procedure. The System Credentials that are provided in step 7
use the default LiveCycle ES authorization service for accessing the default repository in this case.
6. Log in to the LiveCycle Administration Console, and click Settings > User Management > Domain
Management.
7. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier
for the domain. The name is a descriptive name for the domain.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Configuring the LiveCycle ES Connector for IBM Content Manager
55
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100
single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See
“Adding enterprise domains” in User Management Help.)
Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for
the ID. (See “Adding enterprise domains” in User Management Help.)
8. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom, and then select IBMCMAuthProviderService
and click OK.
9. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
10. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the above settings, click the Help link in the upper-right corner of the page.
11. Click OK to exit the Add Directory page and click OK again.
12. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
13. To verify the status of the synchronization, click Refresh and view the status in the Current Sync State
column.
14. Navigate to Settings > User Management > Users and Groups.
15. Search for users that were synchronized from LDAP and do these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users that you want to assign roles to. For more information, click the Help link in
the upper-right corner of the page.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Uninstalling LiveCycle ES
56
16. Start Workbench ES and log in using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The IBM Content Manager data store can now be used in the Processes view within Workbench ES
when the login mode for IBMCMConnectorService orchestrable components is selected as Use
Credentials from process context.
After you configure your Connector for IBM Content Manager service, it is recommended that you see
Administering LiveCycle ES.
Uninstalling LiveCycle ES
The uninstall program located in the [LivecycleES root] directory does not remove the files that you
deployed to your application server.
Caution: By running the uninstall program, all the contents within the product installation directory are
subject to removal without further warning. Before you proceed, back up any data you do not
want to lose.
➤ To remove the files from your computer:
1. Invoke the uninstall program:
●
(Windows) Perform these tasks:
●
●
●
Use Add or Remove Programs in the Windows Control Panel:
●
Remove Adobe LiveCycle ES.
●
Remove Adobe Acrobat 9.0 Professional (if installed with PDF Generator ES).
Alternatively, you can complete these manual steps:
●
cd [LivecycleES root]/_uninst/server
●
Double-click the livecycle8_uninstall.exe file.
(Linux) From a terminal, type ./livecycle8_uninstall.bin (you may need to make this
binary an executable file by typing a command, such as chmod 777).
2. Follow the on-screen instructions in the uninstall program, and then click Finish.
Uninstalling a LiveCycle ES solution component
If you want to remove a previously installed solution component, there are two main tasks associated with
the process:
●
Stop and undeploy the existing LiveCycle ES EAR files from your application server.
●
Run LiveCycle Configuration Manager to reconfigure and redeploy the LiveCycle ES EAR files and
solution components (omitting the eliminated component).
➤ To uninstall a solution component without removing LiveCycle ES:
1. Stop JBoss Application Server and undeploy the LiveCycle ES EAR files by navigating to
[appserver_root]/server/all/deploy and deleting the EAR files.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for JBoss
Uninstalling a LiveCycle ES solution component
2. Run LiveCycle Configuration Manager. See “Configuring and deploying LiveCycle ES” on page 18.
3. On the Solution Component Selection screen, select only those components to redeploy or if the
previously installed components are selected, deselect the component to remove.
4. On the Task Selection screen, select the following tasks and the click Next:
●
Configure LiveCycle ES
●
Deploy LiveCycle ES EARs
●
Deploy LiveCycle ES components
5. Perform the tasks on the remaining screens, review the Next Steps, and then click Exit.
If you are uninstalling Output ES, you will need to perform the following tasks to complete its removal
from your LiveCycle ES environment:
●
Log in to Workbench ES and uninstall the Output service via the Components view.
●
Remove any related samples.
57
6
Manually Configuring BAM Server for LiveCycle ES
This section describes the tasks that must be performed to manually install and configure
LiveCycle ES Business Activity Monitoring for use with LiveCycle ES:
●
“Configuring the keystore” on page 60
●
“Creating the bam.properties file” on page 60
●
“Creating and configuring the BAM Server metadata database” on page 61
●
“Installing database drivers on JBoss Application Server for BAM Server” on page 62
●
“Configuring LiveCycle Process Management ES for BAM Server” on page 70
●
“Deploying BAM Server EAR file to JBoss Application Server” on page 70
●
“Configuring Business Activity Monitoring” on page 70
●
“Configuring LDAP settings for BAM Server” on page 72
●
“Using BAM Dashboard” on page 76
●
“Shutting down BAM Server” on page 77
●
“Uninstalling Business Activity Monitoring” on page 78
The instructions in this document use the following naming conventions for common file paths.
'
Name
Description
Default value
[jboss bam root]
The home directory of the
application server for
Business Activity Monitoring.
JBoss on Windows: C:\jboss- bam
[LiveCycleES root]
JBoss on Linux: /opt/jboss-bam
The location where the LiveCycle ES Windows: C:\Adobe\LiveCycle8.2
services are installed
Linux and UNIX: /opt/adobe/livecycle8.2
Most of the information about directory locations in this document is cross-platform (all file names and
paths are case-sensitive on Linux and UNIX). Platform-specific information is indicated as required.
Installing JBoss Application Server
If you are deploying LiveCycle ES Solution Components in addition to LiveCycle
Business Activity Monitoring ES in a production environment then LiveCycle Business Activity Monitoring
ES should be deployed into a separate Application Server instance then that of the other LiveCycle ES
Solution Components. It is recommend that for larger production use that the LiveCycle
Business Activity Monitoring ES Solution Component be installed into a dedicated system that just runs
the one Solution Component and that that system should run both a 64 bit Operating system and Java
Application Server. This is because the modelling process requires large amounts of RAM to compute and
can require more then the memory limit on 32 bit systems. See “Customizing port numbers” on page 59 to
resolve port number conflicts.
If you are manually configuring JBoss Application Server for running BAM Server, download and install
JBoss Application Server 4.0.3 SP1 or 4.2.0 from the JBoss Application Server Download site.
58
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring JBoss 4.2.0 for BAM
59
Install the JBoss Application Server that will host BAM Server to a directory such as C:\jboss-bam.
Configuring JBoss 4.2.0 for BAM
You must modify the WAR file class-loading isolation attributes to successfully deploy BAM on JBoss 4.2.0.
➤ To modify the WAR file class-loading isolation:
1. Open the [appserver root]/server/all/deploy/jboss-web.deployer/META-INF/jboss-service.xml file in an
editor.
2. Locate <attribute name="Java2ClassLoadingCompliance"> and ensure that the value is false.
3. Locate <attribute name="UseJBossWebLoader"> and ensure that the value is false.
4. Save and close the file.
Customizing port numbers
If it is necessary to run more than one JBoss Application Server on a computer, the following ports should
be changed for the secondary servers. In the following list, the change to port is a suggestion. Utilities such
as TCPView for Windows, or Netstat can be used to verify that a change to a port is available.
For each of the following files, open it in a text editor and make the changes as indicated:
[jboss bam root]\server\all\deploy\jbossweb-tomcat50.sar\server.xml
●
Change HTTP/1.1 Connector port from 8080 to 8888.
●
Change AJP 1.3 Connector port from 8009 to 8099.
●
Change SSL/TLS Connector port from 8443 to 8493.
[jboss bam root]\server\all\conf\jboss-service.xml
●
Change WebService port from 8083 to 8899.
●
Change NamingService port from 1099 to 9999.
●
Change RMIport from 1098 to 9998.
●
Change RMIObjectPort from 4444 to 9444.
●
Change PooledInvoker ServerBindPort from 4445 to 9445.
[jboss bam root]\server\all\deploy\cluster-service.xml
●
Change ha.jndi.HANamingService port from 1100 to 1190.
●
Change RmiPort from 1101 to 1191.
●
Change RMIObjectPort from 4447 to 9447.
●
Change ServerBindPort from 4446 to 9446 (only needed in a cluster).
[jboss bam root]\server\all\deploy\jms\hajndi-jms-ds.xml
●
Change java.naming.provider.url from 1100 to 1190.
[jboss bam root]\server\all\conf\jacorb.properties
●
Change OAPort from 3528 to 9528.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
●
Configuring the keystore
60
Change OASSLPort from 3529 to 9529.
[jboss bam root]\server\all\deploy-hasingleton\jms\uil2-service.xml
●
Change ServerBindPort from 8093 to 8993.
[jboss bam root]\server\all\deploy\snmp-adaptor.sar\META-INF\jboss-service.xml
●
Change port from 1162 to 1182.
●
Change port from1161 to 1181.
[jboss bam root]\server\all\deploy\snmp-adaptor.sar\managers.xml
●
Change port from1162 to 1182.
Configuring the keystore
You need administrator and user keystores for password encryption and decryption. You also need to
specify the location of these keystores.
➤ To set up the keystores and keystore locations:‘178 ‘
1. Copy the admin.jks keystore file from [LiveCycleES root]/LiveCycle_ES_SDK\misc\
Business_Activity_Monitoring\keystore to a location that will be called [Admin Keystore Location]. The
default password is 40fd2442fa.
2. Copy the user_sample.jks keystore file from [LiveCycleES root]/LiveCycle_ES_SDK\
misc\Business_Activity_Monitoring\keystore to a location that will be called [User Keystore Location].
The default password is 8deb5102f8.
➤ To create a user keystore:
It is strongly recommended that you create you own user keystore. To create a user keystore, do the
following:
1. Refer to “Working with Encryption Configuration” in LiveCycle Workbench ES Help for information on
how to create a Java Keystore.
2. Specify the location of your user keystore with the system setting property called Keystore
Location in your bam.properties file. (See “Creating the bam.properties file” on page 60.)
Creating the bam.properties file
Before you begin installation, you must create a system properties text file called bam.properties. Save this
file anywhere in the file system. This document refers to this file location as [bam.properties file
location]. The properties are required so that Business Activity Monitoring can start properly. Without
this text file, BAM Workbench might display the First Time Setup web page dialog box because some
required system properties are not set.
To set the required system properties, create a text file called bam.properties and save it your
[appserver-bam root]/bin directory. You must set the following properties and defaults in your start-up
properties text file:
Logging Directory= [specify a log directory]
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Manually Configuring BAM Server for LiveCycle ES
Creating and configuring the BAM Server metadata database
61
Recovery Log Directory = [specify a recovery log directory]
Log File Prefix=bam
SMTP Host=localhost
SMTP From [email protected]
SMTP User=lava
Admin Keystore Location=[Admin Keystore Location]/admin.jks
Keystore Location=[User Keystore Location]/user_sample.jks
Creating and configuring the BAM Server metadata database
You must have a BAM Server metadata database created to store the definitions of the process metrics
that BAM Server monitors. For details on supported databases and permissions, see Preparing to Install
LiveCycle ES (Single Server).
User accounts
You must create a dedicated user account that BAM Server can use to connect to the BAM Server metadata
database. For details on the required user permissions, please consult Preparing to Install LiveCycle ES
(Single Server).
Configuring your database environment (DB2 only)
This section only applies if you are using DB2 as your metadata database.
If you are using DB2 as the BAM Server 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, with DB2 library files installed in the
/opt/IBM/db2/V8.1/lib directory:
export DB2INSTANCE=db2f
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Manually Configuring BAM Server for LiveCycle ES
Installing database drivers on JBoss Application Server for BAM Server
62
export LIBPATH=/opt/IBM/db2/V8.1/lib:${LIBPATH}
Installing database drivers on JBoss Application Server for
BAM Server
To enable BAM Server to connect to the BAM Server metadata database and the LiveCycle ES database,
install the drivers for the types of databases you are using.
Note: LiveCycle ES and BAM Server run in completely different JBoss navigation trees, which means that
drivers are required in each tree. As a result, reinstall these drivers for BAM Server.
➤ To install the JDBC driver for MySQL:
1. Obtain the mysql-connector-java-3.0.15-ga-bin-jar file from the MySQL Connector website.
2. Copy the file to the [jboss bam root]/server/all/lib directory.
➤ To install the JDBC driver for SQL Server:
●
Copy the database server driver file called sqljdbc.jar to the [jboss_bam_root]/server/all/lib/ directory.
➤ To install the JDBC driver for Oracle:
●
Copy the database server driver file called ojdbc14.jar (for Oracle 10g) to the [jboss_bam_root]/server/
all/lib directory.
Configuring the BAM Server metadata database
The following procedure describes how to configure the BAM Server metadata database.
➤ To configure the MySQL data source:
1. Navigate to the [jboss bam root]/server/all/deploy directory and create a file named
celequest_metadata-ds.xml by using a text editor.
2. Add the following code into the celequest_metadata-ds.xml file:
<datasources>
<no-tx-datasource>
<jndi-name>com.celequest.metadata.metaDatasource</jndi-name>
<use-java-context>false</use-java-context>
<connection-url>jdbc:mysql://[host name]:[port]/[dbname]
</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>[username]</user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>20</max-pool-size>
<blocking-timeout-millis>20000</blocking-timeout-millis>
<idle-timeout-minutes>10</idle-timeout-minutes>
<prepared-statement-cache-size>50</prepared-statement-cache-size>
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring the BAM Server metadata database
63
</no-tx-datasource>
</datasources>
where:
●
[host name] is the name of the computer where MySQL is running.
●
[port] is the port that is used to access the database. The default port for MySQL is 3306.
●
[dbname] is the name of the BAM Server metadata database.
●
[username] is the name of the database user account that can access the BAM Server metadata
database.
●
[password] is the password for the user name that is specified for the[username]element.
3. Save and close the file.
➤ To configure the SQL Server 2005 data source:
1. Navigate to the [jboss bam root]/server/all/deploy directory and create a file named
celequest_metadata-ds.xml by using a text editor.
2. Add the following code into the celequest_metadata-ds.xml file:
<datasources>
<no-tx-datasource>
<jndi-name>com.celequest.metadata.metaDatasource</jndi-name>
<use-java-context>false</use-java-context>
<connection-url>jdbc:sqlserver://[host name]:[port];dbname=[dbname]
</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver
</driver-class>
<user-name>[username]</user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>20</max-pool-size>
<blocking-timeout-millis>20000</blocking-timeout-millis>
<idle-timeout-minutes>10</idle-timeout-minutes>
<prepared-statement-cache-size>50</prepared-statement-cache-size>
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
</no-tx-datasource>
</datasources>
where:
●
[host name] is the name of the computer where SQL Server 2005 is running.
●
[port] is the port that is used to access the database. The default port for SQL Server 2005 is 1433.
●
[dbname] is the name of the BAM Server metadata database.
●
[username] is the name of the database user account that can access the BAM Server metadata
database.
●
[password] is the password for the user name that is specified for the[username]element.
3. Save and close the file.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring the BAM Server metadata database
64
➤ To configure the Oracle data source:
1. Create a new file by using a text editor and save it as celequest_metadata-ds.xml in the
[jboss bam root]/server/all/deploy directory.
2. Add the following code into the celequest_metadata-ds.xml file:
<datasources>
<no-tx-datasource>
<jndi-name>com.celequest.metadata.metaDatasource</jndi-name>
<use-java-context>false</use-java-context>
<connection-url>jdbc:oracle:thin:[dbuser]/[dbpassword]@
[dbhost]:[dbport]:[dbSID]</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>[username]<user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>20</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
<track-statements>false</track-statements>
<application-managed-security/>
</no-tx-datasource>
</datasources>
where:
●
[dbuser] is the user name that is used to access Oracle.
●
[dbpassword] is the password that is used to access Oracle.
●
[dbhost] is the name of the computer where Oracle is running.
●
[dbport] is the port that is used to access the database.
●
[dbSID] is the system ID of the Oracle database.
●
[username] is the name of the database user account that can access the BAM Server metadata
database.
●
[password] is the password for the user name that is specified for the[username]element.
3. Save and close the file.
➤ To configure the DB2 data source:
1. Create a new file by using a text editor and save it as celequest_metadata-ds.xml in the
[jboss bam root]/server/all/deploy directory.
2. Add the following code into the celequest_metadata-ds.xml file:
<datasources>
<no-tx-datasource>
<jndi-name>com.celequest.metadata.metaDatasource</jndi-name>
<use-java-context>false</use-java-context>
<connection-url>jdbc:db2://[host_name]:[port]/[dbname]</connection-url>
<driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
<user-name>[username]<user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>20</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Connecting JBoss Application Server for BAM Server to the LiveCycle ES database
65
<track-statements>false</track-statements>
<application-managed-security/>
</no-tx-datasource>
</datasources>
where:
●
[host_name] is the name of the computer where DB2 is running.
●
[port] is the port that is used to access the database.
●
[dbname] is the name of the BAM Server metadata database.
●
[username] is the name of the database user account that can access the BAM Server metadata
database.
●
[password] is the password for the user name that is specified for the[username]element.
3. Save and close the file.
Connecting JBoss Application Server for BAM Server to the LiveCycle ES
database
Configure a connection to the LiveCycle ES database on the instance of JBoss Application Server that runs
BAM Server so that it can retrieve information about the process run-time data.
The procedure to configure the connection you use depends on the type of database you are using to
store LiveCycle ES data:
“Connecting to the LiveCycle ES database on SQL Server” on page 65“
“Connecting to the LiveCycle ES database on MySQL” on page 66
“Connecting to the LiveCycle ES database on Oracle” on page 67
“Connecting to the LiveCycle ES database on DB2” on page 67
Connecting to the LiveCycle ES database on SQL Server
To enable BAM Server to connect to the LiveCycle ES database, create a data source file and deploy it to
the instance of JBoss Application Server that runs BAM Server.
➤ To create a data source for the LiveCycle ES database on SQL Server 2005:
1. Open a text editor and create a new text file using the following code:
<datasources>
<local-tx-datasource>
<jndi-name>IDP_DS</jndi-name>
<connection-url>jdbc:sqlserver://[host name]:[port];
databaseName=[dbname]</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver
</driver-class>
<user-name>[username]</user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>30</max-pool-size>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<idle-timeout-minutes>15</idle-timeout-minutes>
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Connecting JBoss Application Server for BAM Server to the LiveCycle ES database
66
<prepared-statement-cache-size>100</prepared-statement-cache-size>
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
<!-- sql to call an existing pooled connection when it is obtained from
pool
<check-valid-connection-sql>some arbitrary sql
</check-valid-connection-sql>
-->
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml
(optional) -->
<metadata>
<type-mapping>MS SQLSERVER2000</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
where:
●
[host name] is the name of the computer where SQL Server 2005 is running.
●
[port] is the port that is used to access the LiveCycle ES database. The default port for SQL Server
2005 is 1433.
●
[dbname] is the name of the LiveCycle ES database.
●
[username] is the user name of the database user account that can access the LiveCycle ES
database.
●
[password] is the password for the user name that is specified for the [username] element.
2. Save the file as adobe-ds.xml in the [jboss bam root]/server/all/deploy/ directory.
Connecting to the LiveCycle ES database on MySQL
To enable BAM Server to connect to the LiveCycle ES database, create a data source file and deploy it to
the instance of JBoss Application Server that runs BAM Server.
➤ To create a data source for the LiveCycle ES database on MySQL:
1. Open a text editor and create a new text file using the following code:
<datasources>
<local-tx-datasource>
<jndi-name>IDP_DS</jndi-name>
<connection-url>jdbc:mysql://[host_name]:[port]/[dbname]
</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>[username]</user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>30</max-pool-size>
<blocking-timeout-millis>20000</blocking-timeout-millis>
<idle-timeout-minutes>10</idle-timeout-minutes>
<prepared-statement-cache-size>50</prepared-statement-cache-size>
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Connecting JBoss Application Server for BAM Server to the LiveCycle ES database
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
</local-tx-datasource>
</datasources>
where:
●
[host name] is the name of the computer on which MySQL is running.
●
[port] is the port that is used to access the LiveCycle ES database.
●
[dbname] is the name of the LiveCycle ES database.
●
[username] is the user name of the database user account that can access the LiveCycle ES
database.
●
[password] is the password for the user name that is specified for the [username] element.
2. Save the file as adobe-ds.xml in the [jboss bam root]/server/all/deploy directory.
Connecting to the LiveCycle ES database on Oracle
To enable BAM Server to connect to the LiveCycle ES database, create a data source file and deploy it to
the instance of JBoss Application Server that runs BAM Server.
➤ To create a data source for the LiveCycle ES database on Oracle:
1. Open a text editor and create a new text file using the following code, where [port] is the port that is
used to access the LiveCycle ES database. The default port for Oracle is 152:
<datasources>
<local-tx-datasource>
<jndi-name>IDP_DS</jndi-name>
<connection-url>jdbc:oracle:thin:@ [host name]: [port]: [dbname]
/</connection-url>
<driver-class> com.oracle.jdbc.OracleDriver </driver-class>
<user-name>[username]</user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>30</max-pool-size>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<idle-timeout-minutes>15</idle-timeout-minutes>
<prepared-statement-cache-size>100</prepared-statement-cache-size>
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
</local-tx-datasource>
</datasources>
2. Save the file as adobe-ds.xml in the [jboss bam root]/server/all/deploy/ directory.
Connecting to the LiveCycle ES database on DB2
To enable BAM Server to connect to the LiveCycle ES database, create a data source file and deploy it to
the instance ofJBoss Application Server that runs BAM Server.
67
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring required JBoss Application Server JVM options
68
➤ To configure the DB2 data source:
1. Open a text editor and create a new text file using the following code, where [port] is the port that is
used to access the LiveCycle ES database. The default port for DB2 is 50000:
<datasources>
<local-tx-datasource>
<jndi-name>IDP_DS</jndi-name>
<connection-url>jdbc:db2:// [host name]:[port]/[dbname]</connection-url>
<driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
<user-name>[username]</user-name>
<password>[password]</password>
<min-pool-size>1</min-pool-size>
<max-pool-size>30</max-pool-size>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<idle-timeout-minutes>15</idle-timeout-minutes>
<prepared-statement-cache-size>100</prepared-statement-cache-size>
<transaction-isolation>TRANSACTION_READ_COMMITTED
</transaction-isolation>
</local-tx-datasource>
</datasources>
2. Save the file as adobe-ds.xml in the [jboss bam root]/server/all/deploy/ directory.
Configuring required JBoss Application Server JVM options
You must configure the JVM to support BAM Server.
➤ To configure the JBoss Application Server JVM options:
1. Navigate to the [jboss bam root]/bin directory and open the startup script in a text editor:
●
(Windows) run.bat
●
(Linux) run.sh
2. Change the JAVA_OPTS memory settings to 256M minimum and 1024M maximum, and include
-server to improve the performance:
●
(Windows) set JAVA_OPTS=%JAVA_OPTS% -server -XX:MaxPermSize=256m -Xms256m
-Xmx1024m
●
(Linux) JAVA_OPTS="$JAVA_OPTS -server -XX:MaxPermSize=256m -Xms256m
-Xmx1024m"
For large data loads, consider increasing the maximum memory to -Xmx1536m (1.5 GB).
3. Add a JAVA_OPTS setting to point to the bam.properties file:
●
(Windows) set JAVA_OPTS=%JAVA_OPTS% -DCASBOOTPROPS=[bam.properties file
location] -Dcom.celequest.bootstrap.envpropname=CASBOOTPROPS
●
(Linux) JAVA_OPTS="%JAVA_OPTS% -DCASBOOTPROPS=[bam.properties file
location] -Dcom.celequest.bootstrap.envpropname=CASBOOTPROPS"
4. Add a JAVA_OPTS setting to enable UTF-8 character support:
●
(Windows) set JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=utf8
●
(Linux) JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=utf8"
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Optional JBoss Application Server JVM parameters
69
5. Add a JAVA_OPTS setting to increase the thread stack size to 300:
●
(Windows) set JAVA_OPTS=%JAVA_OPTS% -XX:ThreadStackSize=300
●
(Linux) JAVA_OPTS="$JAVA_OPTS -XX:ThreadStackSize=300"
6. Save and close the startup script file.
Optional JBoss Application Server JVM parameters
You can set several optional JVM parameters that are related to the BAM Server metadata database,
including language, country, and collation strength. These JVM parameters are expressed by using
commands in the following format:
-Dcom.celequest.property.[PARAMETER]=[VALUE]
This table provides valid values for [PARAMETER] and [VALUE].
Parameter
Description
LANGUAGE
The ISO language code for the server. For example, the following command sets
the LANGUAGE parameter to Portuguese:
-Dcom.celequest.property.LANGUAGE=PT
COUNTRY
The ISO country code for the server.
LOCALESORT
Specifies whether locale-sensitive string comparisons are performed. Valid values
are true and false:
●
Specify true to have locale-sensitive string comparisons performed.
●
Specify false to not have locale-sensitive string comparisons performed.
The default value is false.
STRENGTH
The level of collation strength, which is the extent to which non-English
characters are compared and collated.
Valid values (in the order of least discriminating to most discriminating) are
primary, secondary, tertiary, and identical. The default value is
tertiary.
For more information, see the Sun Java documentation.
Note: This setting is functional only if LOCALESORT is set to true.
DECOMPOSITION
The mode of collation decomposition. Valid values are none, canonical, and
full. The default value is canonical.
For more information, see the Sun Java documentation.
Note: This setting is functional only if LOCALESORT is set to true.
To set multiple properties, separate each command with a space. For example, the following commands
set the language to Portuguese and the locale to Brazil:
-Dcom.celequest.property.LANGUAGE=PT -Dcom.celequest.property.LOCALE=BR
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring LiveCycle Process Management ES for BAM Server
70
Configuring LiveCycle Process Management ES for BAM Server
You can configure LiveCycle Process Management ES to connect to BAM Server by using LiveCycle
Administration Console. You must specify the server that the LiveCycle ES server and BAM Server are
running on and the user account information to use to access BAM Server.
➤ 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 that BAM Server is running on. The default
value is localhost.
BAM Port: The service port of the application server that BAM Server is running on.
LiveCycle Server Host: The host name or IP address of the server that the LiveCycle ES server is
running on. The default value is localhost.
LiveCycle Server SOAP Port: The service port of the application server that the LiveCycle ES server
is running on.
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, ensure that the user has complete
administrative privileges for BAM Server. For information about administering BAM Server user
accounts, see LiveCycle Workbench ESHelp.
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 EAR file to JBoss Application Server
Deploy the BAM Server EAR file (CAS_Adobe.ear) to the application server that you configured for running
BAM Server.“]
➤ To deploy the BAM Server EAR file:
1. Stop JBoss Application Server for BAM Server, if it is running.
2. Navigate to [LiveCycle ES root]/deploy and copy the Lava_Adobe.ear file to [jboss bam root]/server/all/
deploy/.
3. Restart the application server.
Configuring Business Activity Monitoring
You must log in to the BAM Workbench interface and then configure the BAM Server system.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring Business Activity Monitoring
71
➤ To log in to the BAM Workbench interface:
1. After JBoss Application Server is started, access the BAM Workbench interface by typing the following
URL in a web browser:
http://[host name]:[port]/bam/login/workbench.htm
2. Log in as an administrator. The default administrator account for BAM Server uses the following ID:
Username: system
Password: manager
Note: Perform the following steps only if you cannot access the BAM Workbench interface using steps
1 and 2.
1. Go to the Services control panel and verify that the JBoss for Adobe LiveCycle8 service is running.
2. Right-click the service entry and click Properties to set the service Startup type to manual.
3. On the General tab, select Manual from the Startup type list and then click OK. This action ensures
that the JBoss service does not start automatically when the computer is restarted.
4. Stop the JBoss for Adobe LiveCycle8 service by clicking Stop the service.
5. From a command prompt, navigate to [LiveCycleES root]/jboss/bin and type the command run.bat
-c all.
➤ 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
When you log in for the first time, you are prompted to configure the system settings.
3. Click Open system settings.
4. In the Configure list, select Checkpoint Configuration and then ensure that Enable Checkpoint is
selected.
5. In the Configure list, select System Control and then ensure that Recover State on Restart is
selected.
6. In the Configure list, select Encryption Configuration.
7. Specify a password in the Keystore Password and User PrivateKey Password boxes. The default user
keystore password is 8deb5102f8.
8. Click OK.
➤ 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.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring LDAP settings for BAM Server
72
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 on the server and enter the full path to the location of the
Business Activity Monitoring metadata template that is appropriate for the type of database that you
are using for the LiveCycle ES database:
●
(DB2) adobeimport_DB2.jar
●
(MySQL) adobeimport_MySQL.jar
●
(Oracle) adobeimport_Oracle.jar
●
(SQL Server) adobeimport_SQLServer.jar
These files are installed in the [LiveCycle root]/deploy directory.
5. Click OK to import the file.
Configuring LDAP settings for BAM Server
In addition to manually creating users and user permissions, you can 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 roles. Users are assigned roles according to the group they belong to in LDAP.
(See “Limitations of BAM Server LDAP connectivity” on page 72.)
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 that a role is not yet created for, 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 75.)
●
If BAM Server imports a user and the user does not belong to a group that a
Business Activity Monitoring role corresponds to, 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.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Best practices for BAM Server LDAP connectivity
73
Best practices for BAM Server LDAP connectivity
When setting up the BAM Server connectivity with the LDAP server, it is strongly recommended that 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. (See “Configuring automatic LDAP synchronization” on page 73.)
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.
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 were 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 and then select LDAP Enabled if it is not already selected.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring automatic LDAP synchronization
74
4. 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 that the LDAP server is running on. The default port is typically 389. However, if
you select the SSL option, the default port is typically 636. 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 that is 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.
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 that is associated with the user that is specified
for the LDAP Synchronization User option.
5. Click Test Connection. The connection and the user-mapping and role-mapping configuration are
tested. If the connection settings are correct, a message indicates that the connection was successful. If
you did not yet configure LDAP User Mapping and LDAP Role Mapping, the message returns an error.
6. To set the LDAP Synchronization Schedule, use the Add Schedule, Edit Schedule, and Remove
Schedule buttons to create the schedule you want, and then click OK.
Note: You should set synchronization for a time when the fewest number of users are likely to be
logged in.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Configuring LDAP user mapping
75
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.
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, as shown is these
examples:
●
(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 can have a special group for Business Activity Monitoring users. This
filter can then ensure that only users with this group membership are imported.
LDAP User LoginID: The login ID of the indicated provider. This value becomes the user’s login ID in
Business Activity Monitoring.
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 that is associated with the specified user if
you are using either Sun ONE or Tivoli. Keep the default value for Active Directory.
4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are
imported successfully, and then 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 JBoss
Manually synchronizing with the LDAP server
76
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 that is used as the Business Activity Monitoring login ID.
4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are
imported successfully, and then 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 and then click Synchronize Now. The time that is required to
synchronize depends on your environment. A message appears when the synchronization is complete.
4. Click OK.
Using BAM Dashboard
Process-specific dashboards are created in Business Activity Monitoring if you select "Auto generate BAM
dashboards" when creating your process in LiveCycle Workbench ES. 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 you invoke it.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Shutting down BAM Server
77
If you install BAM Server after LiveCycle ES has run a process, you must 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 that is 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. Log in to BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL
line of a web browser.
2. Click Application Workbench > Events.
3. In the Events list in the right pane, find ActivityInstanceStartedEvent and
ActivityInstanceCompletedEvent.
4. Disable each event by clicking the arrow button on the Status column and selecting Disable
dependencies.
5. Enable the events by clicking the arrow button in the Status column and selecting Enable all.
6. Repeat steps 3 to 5 for ProcessInstanceStartedEvent and
ProcessInstanceCompletedEvent.
7. Repeat steps 3 to 5 for all remaining events except AdobeEvent, VC_SYSTEM_EVENTS, and
VC_TASK_EVENTS.
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
Shutting down BAM Server
Use the following procedure to shut down BAM Server under JBoss Application Server.
➤ To shutdown Business Activity Monitoring on JBoss Application Server:
1. Log in to the BAM Workbench as a system administrator.
2. Perform a system checkpoint by selecting Administration Console > System Settings dialog >
Checkpoint Configuration tab, and then click Run Checkpoint Now.
A snapshot saves the state of the system. When the Recover Check Point State on Restart option on the
System controls tab is on, the servers restore the last checkpoint data when they restart.
3. Run the JBoss Application Server shutdown script:
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
●
(Windows) \[jboss bam root]\bin\shutdown.bat -S
●
(UNIX) ./[jboss bam root]/bin/shutdown.sh -S
Additional documentation
78
Additional documentation
You can access additional information about Business Activity Monitoring in these documents:
●
Using Business Activity Monitoring Dashboard
●
Business Activity Monitoring Server Reference
●
LiveCycle Workbench ES Help
Uninstalling Business Activity Monitoring
You must uninstall BAM Server completely before attempting to reinstall.
➤ To uninstall BAM Server:
1. Stop BAM Server.
2. Undeploy the BAM Server EAR file by removing Lava_Adobe.ear from [jboss bam root]/server/all/deploy
directory.
3. Remove the following files:
●
[jboss bam root]/server/all/log/*
4. Delete all the files from the recovery log directory and logging directory that have names similar to the
following patterns:
●
filestore*.dat
●
DEFAULTRECOVERYLOGGER_*
●
chkpoint*
5. Review the contents of the [appserver root]\bin folder and, if any chkpoint* files exist, delete them.
6. 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.
7
Advanced Production Configuration
This section describes advanced tuning for LiveCycle Output ES, LiveCycle Forms ES, and
LiveCycle PDF Generator ES. This section should be completed only on a production system by an
advanced application server administrator.
Configuring pool size for LiveCycle Output ES and
LiveCycle Forms ES
The current default value for PoolMax is 4. The actual value to set depends on the hardware configuration
and the expected usage in your environment.
For optimal use, we recommend that the lower limit of PoolMax not be less than the number of CPUs that
are available. The upper limit must be determined by the load pattern on your server. Generally, the upper
limit should be set to twice the number of CPUs on your server.
➤ To modify the existing PoolMax value:
1. Using a text editor, edit the JBoss startup script.
2. Add the following properties for ConvertPdf :
●
com.adobe.convertpdf.bmc.POOL_MAX=[new value]
●
com.adobe.convertpdf.bmc.MAXIMUM_REUSE_COUNT=5000
●
com.adobe.convertpdf.bmc.REPORT_TIMING_INFORMATION=true
●
com.adobe.convertpdf.bmc.CT_ALLOW_SYSTEM_FONTS=true
3. Add the following properties for XMLFM:
●
com.adobe.xmlform.bmc.POOL_MAX=[new value]
●
com.adobe.xmlform.bmc.MAXIMUM_REUSE_COUNT=5000
●
com.adobe.xmlform.bmc.REPORT_TIMING_INFORMATION=true
●
com.adobe.xmlform.bmc.CT_ALLOW_SYSTEM_FONTS=true
LiveCycle PDF Generator ES
LiveCycle PDF Generator ES is capable of doing multiple PDF conversions simultaneously for some types of
input files. This is enforced through the use of stateless session beans.
Configuring EJB Pool Size
Four different stateless session beans exist for enforcing independent pool sizes for the following types of
input files:
●
Adobe PostScript® and Encapsulated PostScript (EPS) files
●
Image files, such as BMP, TIFF, PNG, and JPEG files
79
Adobe LiveCycle ES
Advanced Production Configuration
Installing and Deploying LiveCycle ES for JBoss
Configuring EJB Pool Size
●
OpenOffice files
●
All other file types (except HTML files), such as Microsoft Office, Photoshop®, PageMaker®, and
FrameMaker® files
80
The pool size for HTML-to-PDF conversions is not managed through the use of stateless session beans.
The default pool size for PostScript and EPS files and for image files is set to 3, and the default pool size for
OpenOffice and other file types (except HTML) is set to 1.
You can configure the PS/EPS and image pool size to a different value based on your server hardware
configuration, such as the number of CPUs, the number of cores within each CPU, and so on. However, it is
mandatory that the pool size for the OpenOffice and other file types be left unchanged at 1 for proper
functioning of PDF Generator ES.
This section describes how the pool size for PS2PDF and Image2PDF can be configured for each of the
supported application servers.
The text that follows assumes that the following two LiveCycle ES application EARs are deployed on the
application server:
●
adobe-livecycle-jboss.ear
●
adobe-livecycle-native-jboss-[platform].ear
where [platform] should be replaced with one of the following strings, depending on your operating
system:
●
(Windows) x86_win32
●
(Linux) x86_linux
●
(SunOS™) sparc_sunos
●
(AIX) powerpc_aix
➤ To configure the pool size for PS2PDF and Image2PDF:
1. Open the adobe-livecycle-jboss.ear file in WinRAR.
2. Go to the following path, opening nested JAR files one after another in WinRAR:
adobe-pdfg-bmc-invoker-ejb.jar > META-INF
3. Extract jboss.xml to any suitable location on the file system and open it in a plain text editor.
4. In the XML code, go to the node that has the following path (expressed in the standard XPath notation):
jboss / container-configurations / container-configuration
5. Choose the container-configuration node for which the container-name node is set to the
value PDFG ImageToPDF Stateless SessionBean.
6. Go to container-pool-conf and set the MaximumSize node to the appropriate value, such as the
new pool size for Image2PDF conversions.
7. If required, repeat steps 5 and 6 for the PS2PDF pool size. The container-name node for PS2PDF
conversions is set to PDFG PSToPDF Stateless SessionBean.
8. Save your changes and repackage the entire EAR structure in the original form.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Advanced Production Configuration
Configuring EJB Pool Size
9. Redeploy the modified EAR file in JBoss Application Server. You will be prompted to restart JBoss.
81
8
Troubleshooting
This section discusses 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 have problems installing, configuring, or deploying LiveCycle ES, ensure that you carefully follow the
instructions in these LiveCycle ES documents:
●
Preparing to Install LiveCycle ES
●
Installing and Deploying LiveCycle ES document for your application server
●
Administering LiveCycle ES
If you installed and configured everything according to the documentation, review the following sections
for issues similar to those you are experiencing.
Change of log on account for JBoss on Windows
When you apply Service Pack 3 on your LiveCycle ES (8.2) installation, the log on account for JBoss service
on Windows is reset to local system. You must change this to administrator for the Windows
sercvice to start.
To correct this problem, change the log on account for the JBoss for Adobe LiveCycle service.
➤ To change the user for the JBoss for Adobe LiveCycle service:
1. Select Start > Control Panel > Administrative Tools > Computer Management > Services and
Applications > Services.
2. Double click the JBoss for Adobe LiveCycle service, and then select the Log On tab.
3. Select This account, and change the user name and password as administrator and the required
password, and then click OK.
82
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for JBoss
Application server considerations
83
Application server considerations
Before you contact Adobe Support, ensure that your application server settings are set as follows:
●
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 30, RM_DS is 20, BAM metadata database is 20
●
Topics and queues connection factories maximum pool connections: 50
Database initialization considerations
If you are having problems initializing the LiveCycle ES server, consider the following restrictions:
●
Database instances must contain only alphanumeric characters in their names.
●
(Linux) Database instances must not exceed the platform-specific threshold of 8 characters.
If the initialization fails at the beginning of the process, ensure that the following conditions exist:
●
The LiveCycle ES database is already 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 is 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 are configured properly.
Address a high number of concurrent calls
If a high number of concurrent calls are expected, increase the maximum connection pool size for the
datasource (IDP_DS) to be more than the number of concurrent calls.
Problems accessing the Services page in LiveCycle Administration Console
If you go to the Services page in LiveCycle Administration Console and the page appears blank, perform
this workaround to ensure that the page displays correctly:
➤ To display the Services page correctly:
1. Start JBoss Application Server manually (not using the Windows service) using the command:
run -b localhost -c all
2. In the Windows hosts file located in the C:\windows\system32\drivers\etc. . . \hosts directory, add the IP
address and host name of the LiveCycle ES server.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for JBoss
Troubleshooting with log files
84
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 in [LiveCycleES root]\ConfigurationManager\log
and may be named lcm.0.log. The log files are useful for LiveCycle Configuration Manager failure analysis
and may be required when dealing with Adobe Enterprise Support.
JBoss log file
By default, the JBoss log files are located in [LiveCycleES root]\jboss\server\all\log and are named boot.log
and server.log. The log files are useful for JBoss Application Server and LiveCycle ES deployment and
bootstrapping failure analysis and may be required when dealing with Adobe Enterprise Support.
Deleting the application server transaction log file
If the component solutions fail to deploy for any reason, the application server that hosts LiveCycle ES
does not restart because it attempts to recover what it interprets as rolled back transactions but fails to do
so. To resolve this issue, locate and delete the application server transaction log file and restart the
application server.
IBM FileNet messages appear in JBoss Application Server log file
<bug 1760314>To stop unnecessary ERROR and WARNING log messages, generated by IBM FileNet, from
appearing in theJBoss Application Server log file, make the following modification to the log4j.xml file
located at [jboss_root]/server/all/conf.
1. Locate the log4j.xml file and open it in an editor.
2. Add the following text to the [Category] section:
<category name="com.filenet">
<priority value="FATAL"/>
</category>
3. Save and close the file.
4. Restart the application server.
Scheduler service configuration for nondefault JNDI URLs
To function correctly, the Scheduler service may require some additional configuration.
Non-clustered environments
If the JNDI URL differs from the default JNDI URL for the application server (that is, for JBoss:
jnp://localhost:1099), this is the JNDI URL for the IDP_DS that is managed by your application server:
org.quartz.dataSource.idp.java.naming.provider.url
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for JBoss
Error messages
85
➤ To set the scheduler properties:
1. Create a new file named dscscheduler.properties.
2. Set the values of the above properties as necessary for the app server node, such as the following text:
org.quartz.dataSource.idp.java.naming.provider.url =
jnp://localhost:1099/
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 describes error messages that are specific to LiveCycle ES and how to resolve the underlying
problems.
PDF Generator ES or PDF Generator 3D ES (on Windows) fails when
converting native files
PDF Generator ES or PDF Generator 3D ES running in a Windows operating system may fail when
converting native files, such as from Microsoft Word to PDF, giving an exception in the log file similar to
this:
INFO [PDF Generator] Application server started as user: SYSTEM
This problem occurs if you did not use the same user account for Microsoft Office, PDF Generator ES,
Acrobat for PDF Generator ES, and your application server process.
To correct this problem, change the user for the JBoss for Adobe LiveCycle service to be the same as the
user for Microsoft Office.
➤ To change the user for the JBoss for Adobe LiveCycle service:
1. Select Start > Control Panel > Administrative Tools > Computer Management > Services and
Applications > Services.
2. Double click the JBoss for Adobe LiveCycle service, and then select the Log On tab.
3. Select This account, type the user name and password that runs Microsoft Office, and then click OK.
Class not found
If you see this error message, check for and then resolve any of the following problems:
●
Is the class path setting invalid or missing?
●
Is the JAR file obsolete?
●
Is there a compilation problem in the class?
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for JBoss
JNDI name not found
86
JNDI name not found
If you see this error message, check whether an exception stack trace shows the following string:
javax.naming.NameNotFoundException: jdbc/<badName>
If the expected name is not spelled correctly, you must fix the code.
➤ To correct the 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 does 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 that the
resource is listed in. See 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 is configured to make this
resource available but something is going wrong, an exception is 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, go 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 no exception appears at startup to explain why it is not
available, most likely the application server is not configured properly to make that resource available.
Review the application server configuration. Is it configured to make this resource available?
●
If no, review “Configuring the LiveCycle ES database connectivity” in the Preparing to Install
LiveCycle ES guide.
If yes, this is not one of the common problems that cause this issue. Contact Adobe Support.
OutputIVS Printer not found
If you see this error, then follow the steps below:
1. In the URL \\<servername>\<printername>, specify the full name of the printer.
2. Add the printer to the windows account before starting JBoss.
3. Enable JBoss to run in the context of a valid user. To perform this task, change the properties of the
JBoss service by clicking the Log On tab and selecting This account. Supply a valid user name and
password and restart the service for this change to take effect.
4. The server that hosts LiveCycle ES needs to have permissions to access the printer; the connection fails
if it does not have the necessary permissions.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Troubleshooting
Exceptions thrown when initializing the database multiple times
87
Exceptions thrown when initializing the database multiple times
When you initialize the LiveCycle ES database after it is already initialized, exceptions may be thrown
indicating that the POF schema was initialized.
This error can be safely ignored.
J2CA0081E: Method cleanup error on SQL Server
If you see the error “J2CA0081E: Method cleanup failed while trying to execute method cleanup...”, the
stack trace appears as follows:
"00000057 MCWrapper E J2CA0081E: Method cleanup failed while trying to execute
method cleanup on ManagedConnection [email protected] from
resource SP_DS. Caught exception: com.ibm.ws.exception.WsException:
DSRA0080E: An exception was received by the Data Store Adapter. See original
exception message: This operation is not supported.. with SQL State : null SQL
Code : 0"
You must update to SQL Server 2005 JDBC driver version 1.2. Obtain this driver from the Microsoft
Download Center.
Database initialization fails on WebLogic
You may receive the following exception while intializing the LiveCycle ES database on WebLogic Server:
Servlet failed with Exception java.lang.ClassCastException:
weblogic.jndi.factories.java.ReadOnlyContextWrapper at
com.adobe.livecycle.bootstrap.framework.BootstrapServlet.checkDatasource(Boo
tstrapServlet.java:216)
To resolve this problem, modify the IDP_DS-3079-jdbc.xml file.
➤ To modify the IDP_DS-3079-jdbc.xml file:
1. Locate the IDP_DS-3079-jdbc.xml file in the [appserverdomain]/config/jdbc directory and open it in an
editor.
2. Locate the line <jndi-name></jndi-name> and delete it.
3. Save and close the file, and reinitialize the database.
OutOfMemoryError: Java heap space error
LiveCycle ES can require transactions that run for longer than the default application server transaction
time-out value. For example, processing large PDF documents can be very time-intensive. These errors can
appear in the application server log when LiveCycle Workbench ES users drag large files to the Resources
view.
If you see OutOfMemoryError messages in the application server log, you must increase the transaction
time-out value. The recommended value is 300 seconds (5 minutes).
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for JBoss
Connector for EMC Documentum error
88
➤ To configure the JBoss transaction time-out:
1. Open [appserver root]/server/all/conf/jboss.service.xml using a text editor.
2. Locate the attribute element that has the name attribute with the value TransactionTimeout:
<attribute name="TransactionTimeout">300</attribute>
3. Modify the text in the attribute element to be a larger number, as required.
4. Save jboss.service.xml.
Connector for EMC Documentum error
While using LiveCycle ES Connector for EMC Documentum with the Documentum DFC 5.3 client installed
on LiveCycle ES server, you may see the following error in the server logs:
DM_CCONTENT_E_REMOVE_DIRECTORY
If this occurs, add the following entry to the [DMAPI_CONFIGURATION] section of the dmcl.ini file:
'local_clean_on_init=F'
On a Windows server, by default the dmcl.ini file is located in the [Windows Installation Drive]\WINDOWS
folder.
Restart the LiveCycle ES server for this change to take affect.
Failure to deploy EAR files
Depending on the LiveCycle ES services you are installing and your system configuration, you may
receive errors when deploying the EAR files. If this occurs, increase the MaxPermSize on your
application server from 256 to 512. For specific instructions on setting this value on your application
server, see Preparing to Install LiveCycle ES.
Improving Windows Server Performance with LDAP
Using connection pooling on the search connection can decrease the number of ports needed by as much
as 50% because that connection always uses the same credentials for a given domain, and the context and
related objects are closed explicitly.
➤ To configure your Windows Server for connection pooling:
1. Start the registry editor by selecting Start > Run and, in the Open box, type regedit, and then click
OK.
2. Go to the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. In the right pane of the registry editor, look for the TcpTimedWaitDelay value name. If the name does
not appear, select Edit > New > DWORD Value to add it.
4. In the name box, type TcpTimedWaitDelay.
5. If you do not see an insertion point and New Value # inside the box, right-click inside the right panel,
select Rename from the menu and then, in the name box, type TcpTimedWaitDelay.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for JBoss
Troubleshooting
Could not start/create deployment errors on Solaris
89
6. Repeat steps 4 and 5 for the following value names: MaxUserPort, MaxHashTableSize, and
MaxFreeTcbs.
7. Double-click inside the right pane to set the TcpTimedWaitDelay value; under Base, select Decimal
and, in the Value box, type 30.
8. Double-click inside the right pane to set the MaxUserPort value; under Base, select Decimal and, in
the Value box, type 65534.
9. Double-click inside the right pane to set the MaxHashTableSize value; under Base, select Decimal
and, in the Value box, type 65536.
10. Double-click inside the right pane to set the MaxFreeTcbs value; under Base, select Decimal and, in
the Value box, type 16000.
Caution: Serious problems may occur if you modify the registry incorrectly by using Registry Editor or by
another method. These problems may require that you reinstall your operating system. Modify
the registry at your own risk.
Could not start/create deployment errors on Solaris
Download the GNU tar tool and use it to extract all files on a Solaris environment. Do not use the Solaris tar
command to extract files otherwise errors such as missing files and log entries similar to the following will
occur:
ERROR[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/invok
er]] Exception starting filter ReadOnlyAccessFilter
java.lang.ClassNotFoundException:
org.jboss.invocation.http.servlet.ReadOnlyAccessFilter
PDF Generator ES considerations
The following topics address issues encountered with PDF Generator ES and their respective resolutions.
Configuring PDF Generator ES to convert MS Office files to PDF format
It is a known issue that on some LiveCycle ES servers, a DCOM permission policy must be modified to use
PDF Generator ES to convert Microsoft Office application files successfully. Otherwise, the following error
message appears:
INFO [STOUT] com.jniwrapper.win32.com.ComException: COM object method returns
error code: 0x80004005; E_FAIL (Unspecified error)
Microsoft has documented the required steps in a knowledgebase article on the Microsoft Help and
Support site.
Microsoft Visio 2007 default macro settings cause conversion time-out
If a Microsoft Visio 2007 file that contains macros is submitted for conversion, the resultant Microsoft
Office Visio Security Notice dialog box causes the conversion to time out. To successfully convert files that
contain macros, the default macro settings in Visio must be changed.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for JBoss
Microsoft Visio 2007 default macro settings cause conversion time-out
➤ To change the default Visio 2007 macro settings:
●
In Visio 2007, click Tools > Trust Center > Macro Settings and select either of the following options
and then click OK:
●
Disable all macros without notification
●
Enable all macros
90
A
Appendix - Install Command Line Interface
LiveCycle ES provides a command line interface (CLI) for the installation program. The CLI is intended to be
used by advanced users of LiveCycle ES or in server environments which do not support the use of the
Graphical User Interface (GUI) of the installation program. The CLI runs in console mode with one
interactive session for all install operations.
Before you install the solution components, you must ensure that your environment includes the software
and hardware required to run LiveCycle ES. You should also understand the installation options and have
prepared the environment as required. (See Preparing to Install LiveCycle ES (Single Server) .) Then you
should review the first page of “Installing the product files” on page 12 and the “Installing the Solution
Component Files” on page 12 section.
This appendix covers the following topics:
●
“Installing LiveCycle ES” on page 91
●
“Error logs” on page 97
●
“Next steps” on page 97
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 17 or “Appendix - LCM Command
Line Interface” on page 98.
Note: To avoid permission issues during the deployment, ensure that you are logged in as the user who
will run the JBoss process when you run the LiveCycle ES install CLI and LiveCycle Configuration
Manager.
➤ To install LiveCycle ES:
1. Open a command prompt and navigate to the /livecycle_server/8.2 directory of the installation media.
2. Run the following command on a single line:
●
(Windows)win_livecycle8_setup.exe -cp:p stage.jar -console;
..\..\third_party\jdbc\mysql-connector-java-3.1.12-bin.jar run -console
●
(Linux) ./linux_livecycle8_setup.bin -cp:p stage.jar -console
●
(UNIX) ./solaris_livecycle8_setup.bin -cp:p stage.jar -console
Note: Specify the following additional arguments to redirect the LiveCycle ES installer temporary
directory to an alternate, non-default location:
91
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
92
-cp:p stage.jar -is:tempdir [alternate temporary directory]
(Solaris Only) To use a higher heap size (such as 512M) in the installer argument, you must specify
the heap size settings in a separate file and then run the install script.
To do this, create a filed named solaris_livecycle8_setup.ja in the directory where
solaris_livecycle8_setup.bin exists, and add the following lines in it:
-XMS256M
-XMX512M
After this, run the install script to direct the installer to use the JDK you installed:
# ./solaris_livecycle8_setup.bin -cp:p stage.jar -is:tempdir /[temporary
directory] -is:javahome [java_home]
3. Respond to the prompts as described in the following table:
Prompt
Description
Select a language to be used for this wizard.
Select the language for the installation to
use by entering a value between 1 and 4.
The selection will then be displayed in
brackets ([X]).
[X] 1 - English
[ ] 2 - French
[ ] 3 - German
[ ] 4 - Japanese
Enter [0] when you finish selecting a
language.
To select an item, enter its number, or [0] when you are
finished: [ ]
Adobe LiveCycle ES
Welcome to Adobe LiveCycle ES
The installation wizard will install Adobe LiveCycle ES
(Enterprise Suite) server version 8.2. To continue, choose
Next.
Adobe LiveCycle ES
Adobe Systems Incorporated
http://www.adobe.com/products/livecycle/
Press 1 for Next, 3 to Cancel, or 5 to Redisplay [1]
On the Welcome screen, enter 1 to
continue the installation.
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
Prompt
Description
Adobe LiveCycle ES
On the Destination screen, press Enter to
accept the default directory or type the
new installation directory location.
Adobe LiveCycle ES Install Location
Please specify a directory or press Enter to accept the
default directory.
Destination Directory For Windows is
[C:\Adobe\LiveCycle8.2]
93
Note: If you type the name of a directory
that does not exist, it will be created
for you.
Destination Directory for Unix/Linux is
[/opt/adobe/livecycle8.2]
Caution: When you install the solution
components, you can specify a
different installation location. If
you are installing on Linux, the
directory you specify should not
contain any spaces; if it does, the
installation program does not
install the solution component.
Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Adobe LiveCycle ES
Enter a serial number. The components that
you are licensed for will be displayed.
Serial Number [ ]
[ ] 1 - Add
[ ] 2 - Clear
[X] 3 - Finish
To select an item enter its number, or 0 when you are
finished: [0]
If you have licensed multiple solution
components, enter 1 to add another serial
number. You will then be prompted for
another serial number as in the previous
step. Repeat this step for each serial
number that you have.
Enter 0 when you finish entering serial
numbers.
Note: To reset the serial number, enter 2.
Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
Prompt
Description
Adobe LiveCycle ES
Select an installation type. By default,
Turnkey installation is selected.
Note: This prompt is only provided for Windows.
Type of Installation
Enter 0 when you are have made your
selection.
Please choose from the following options:
[X] 1 - Turnkey
The turnkey installation automatically performs all of
the tasks required to install and configure LiveCycle ES
components on a single (non-clustered) JBoss Application
Server running on Windows with a preconfigured MySQL
database.
[ ] 2 - Manual
The manual method lets you install the files and then
run LiveCycle Configuration Manager to configure the
EAR file and other components. However, you must
manually install, configure, and start your application
server as well as create and configure the database before
running LiveCycle Configuration Manager and deploying
to the application server.
To select an item enter its number, or 0 when you are
finished: [ ]
Note: This prompt is only provided for Windows.
Enter 1 to continue the installation.
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [ ]
Press ENTER to read the text [Type q to quit]
The Product License Agreement will
display. Press enter to read the agreement.
Please choose from the following options:
If you agree with the terms of the Product
License Agreement, enter 1.
[ ] 1 - I accept the terms of the license agreement.
[X] 2 - I do not accept the terms of the license agreement.
Enter [0] when you are done with the
Product License Agreement.
To select an item enter its number, or 0 when you are
finished: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter 1 to continue the installation.
Adobe LiveCycle ES
Type a new Java SE SDK directory location
or press enter to accept the default
directory.
Java SE SDK Location
Select the location of your Java SDK. Version 1.5.0 or later
is required.
Browse... [ ] C:\Program Files\Java\jdk1.5.0_11
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Note: This prompt is only provided for
Windows.
Press enter to continue the installation.
94
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
95
Prompt
Description
Adobe LiveCycle ES
(PDF Generator ES for Windows Only)
LiveCycle PDF Generator ES Native Application Support
If you enter 1 to enable native application
support for PDF Generator ES, the software
will check the version of Adobe Acrobat®
you have installed. If you do not have
Acrobat installed, accept the prompt to
install Acrobat 9.0 now.
LiveCycle PDF Generator ES can convert Microsoft Office
Word, Adobe Photoshop, AutoCAD, and other native
application files to Adobe PDF.
Please choose from the following options:
For detailed information about native application
support, please see the documentation.
[ ] 1 - Yes, enable native application support for LiveCycle
PDF Generator ES
[X] 2 - No, do not enable native application support for
LiveCycle PDF Generator ES (select this option for
clustered deployments)
If you are installing in a clustered
environment, enter 2 and do not enable
native application support for
PDF Generator ES.
Enter [0] when you are done making your
selection.
To select an item enter its number, or 0 when you are
finished: [ ]
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Press Enter to continue the installation.
Adobe LiveCycle ES
Press Enter to accept the default port
number or type a new port number.
MySQL will be installed to use the following available
port. To override this selection, enter a different port
number and click Test to verify the port is available.
Note: This prompt is only provided for
Windows.
Port: [3306]
Port: [3306]
[ ] 1 - Test
[ ] 2 - Reset
To test the port number, enter 1 and then
enter 3 to finish. A message will display the
result of the test.
[X] 3 - Finish
To reset the port number to the default
value, enter 2.
To select an item enter its number, or 0 when you are
finished: [0]
Enter 0 when you have completed selecting
and testing port numbers.
Note: This prompt is only provided for
Windows.
The password entered gives full access to all functionality
of the database.
MySQL adobe/root User Password
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter a unique database password.
Note: This prompt is only provided for
Windows.
Enter 1 to continue the installation.
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Installing LiveCycle ES
96
Prompt
Description
Adobe LiveCycle ES
Press 1 to install LiveCycle ES.
Pre-installation Summary
Pre-installation summary -> Please read the
summary information. LiveCycle ES will be
installed in the following location with the
following features.The installation progress
will display.
Please read the summary information below.
Adobe LiveCycle ES will be installed in the following
location:
/opt/adobe/livecycle8.2
With the following features:
●
Adobe LiveCycle Foundation
●
Adobe LiveCycle Configuration Manager
●
LiveCycle ES SDK
●
Adobe LiveCycle Forms ES
●
Adobe LiveCycle Reader Extensions ES
●
Adobe LiveCycle Process Management ES
●
Adobe LiveCycle ES Business Activity Monitoring
●
Adobe LiveCycle Output ES
●
Adobe LiveCycle Rights Management ES
●
Adobe LiveCycle Digital Signatures ES
●
Adobe LiveCycle PDF Generator ES
●
Adobe LiveCycle PDF Generator 3D ES
●
Adobe LiveCycle Barcoded Forms ES
●
Adobe LiveCycle ES Connector for IBM FileNet
●
Adobe LiveCycle ES Connector for EMC Documentum
●
Adobe LiveCycle ES
Connector for IBM Content Manager
Note: The installation location and solution
components specified will vary
depending on your license key and
your specified installation directory.
Press ENTER to read the text. Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
Press ENTER to read the test (Type q to quit).
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
After installation is done, the Release Notes
Summary is displayed.
Please choose from the following options:
Post Installation Details are displayed.
[X] 1 - Start LiveCycle Configuration Manager.
Enter 1 to start LiveCycle Configuration
Manager or 2 and then [0] to end the
installation.
[ ] 2 - Not Start LiveCycle Configuration Manager.
To select an item enter its number, or 0 when you are
finished: [0]
Press 3 to Finish or 5 to Redisplay [3]
Adobe LiveCycle ES
Appendix - Install Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Error logs
97
Error logs
If an error occurs, you can review the adobe_lc8.2_server_install.log in the system temporary directory
(TEMP or TMP).
For information about errors that may occur during the installation, see “Troubleshooting” on page 82.
Uninstalling LiveCycle ES in console mode
If you need to uninstall your LiveCycle ES environment, open a command prompt, change to the
[LiveCycle8.2 root]/_uninst/server directory and run the following command as appropriate for your
operating system:
●
(Windows) ./windows.*.bin - console
●
(Linux) ./linux.*.bin - console
●
(UNIX) ./solaris.*.bin - console
Next steps
You must now configure LiveCycle ES for deployment. (See “Configuring LiveCycle ES for Deployment” on
page 17 or “Appendix - LCM Command Line Interface” on page 98.)
B
Appendix - LCM Command Line Interface
LiveCycle ES provides a Command Line Interface (CLI) for LiveCycle Configuration Manager. The CLI is
intended to be used by LiveCycle ES advanced users, for example, in server environments that do not
support the use of the graphical user interface (GUI) of LiveCycle Configuration Manager.
Order of operations
The LiveCycle Configuration Manager CLI must follow the same order of operations as the GUI version of
LiveCycle Configuration Manager. Ensure that you use the CLI operations in this order:
1. Configure LiveCycle ES.
2. Deploy LiveCycle ES.
3. Initialize LiveCycle ES.
4. Initialize LiveCycle ES Business Activity Monitoring.
5. Deploy LiveCycle ES Components.
Caution: You must restart your JBoss Application Server after you complete your LiveCycle Configuration
Manager CLI operations.
Command line interface property file
The LiveCycle Configuration Manager CLI requires a property file containing the defined properties for
your LiveCycle ES environment. The template for the properties file, cli_propertyFile_template.txt, is
located in the [LiveCycleES root]/configurationManager/bin folder. You must create a copy of this file and
edit the values. You can customize this file based on the LiveCycle Configuration Manager operations you
intend to use. The following section describes the properties and values required.
Note: If you use the GUI version of LiveCycle Configuration Manager, and then chose to use the CLI
version, you can use the property file created by the GUI version as the CLI version property file.
When you run the [LiveCycleES root]/configurationManager/bin/ConfigurationManager.bat file, the
userValues.properties file is created in the [LiveCycleES root]/configurationManager/config
directory. You can copy this file, rename it userValuesForCLI.properties, and use it as input for the
LiveCycle Configuration Manager CLI.
Common properties
The common properties are as follows:
LiveCycle Server specific properties: Required for the Initialize LiveCycle and Deploy LiveCycle
Components operations.
The properties in the table are required for following operations:
●
Initialize LiveCycle
98
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
●
Configure LiveCycle ES properties
99
Deploy LiveCycle Components
Configure LiveCycle ES properties
These properties only apply to the configureLiveCycle operation.
Property
Values
Description
AdobeFontsDir
String
Location of the Adobe server
fonts directory. This path must
be accessible from the server
being deployed to.
customerFontsDir
String
Location of the customer fonts
directory. This path must be
accessible from the server being
deployed to.
systemFontsDir
String
Location of the system fonts
directory. Multiple system fonts’
locations can be entered using a
semicolon as separator.
These paths must be accessible
from the server being deployed
to.
LCTempDir
String
Location of the temporary
directory. This path must be
accessible from the server being
deployed to.
LCGlobalDocStorageDir
String
The global document storage
(GDS) root directory.
Specify a path to an NFS shared
directory used to store
long-lived documents and to
share them among all cluster
nodes.
Specify this property only when
deploying LiveCycle ES products
in a clustered environment. This
path must be accessible from
the server being deployed to.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Configure application server properties
100
Property
Values
Description
enableFIPS
true or false
Enabling the Federal
Information Processing
Standards (FIPS) option restricts
data protection to FIPS 140-2
approved algorithms using the
RSA BSAFE Crypto-J 3.5.2
encryption module with FIPS
140-2 validation certificate #590.
Set this value to true only if you
require FIPS to be enforced.
Default:
false
contentServices.rootDir
String
Required if you are configuring
LiveCycle Content Services ES
only.
Specify the root directory used
by Content Services ES.
Configure application server properties
If you are installing LiveCycle ES with a JBoss Application Server, you must either manually configure JBoss
Application Server, use the Adobe preconfigured JBoss Application Server provided on the LiveCycle ES
DVD, or use the JBoss turnkey option.
Deploy LiveCycle properties
These properties only apply to the deployLiveCycle operation.
Note: You must configure the LiveCycle Server Information section. (See “Common properties” on
page 98.)
Initialize LiveCycle properties
These properties only apply to the initializeLiveCycle operation.
Note: You must configure the LiveCycle Server Information section. (See “Common properties” on
page 98.)
Initialize BAM properties
These properties only apply to the initialize BAM operation.
Note: LiveCycle ES Business Activity Monitoring is an optional solution component with LiveCycle ES.
Property
Values
Description
BAMHost
String
The host name of the server
where
Business Activity Monitoring is
deployed and running
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Deploy LiveCycle Components properties
101
Property
Values
Description
BAMPort
Integer
The port number BAM Server
uses to listen for requests
BAMAdminUserID
String
The Business Activity Monitoring
administrator user ID to use
when connecting to BAM Server
BAMAdminPassword
String
The Business Activity Monitoring
administrator password to use
when connecting to BAM Server
databaseType
Choose a database:
The type of database
LiveCycle ES is using to capture
Business Activity Monitoring
data
oracle
mysql
sqlserver
db2
Deploy LiveCycle Components properties
The properties in the table apply to these operations:
●
Deploy LiveCycle Components
●
Validate LiveCycle Component Deployment
●
Validate LiveCycle Server
Note: You must configure the LiveCycle Server Information section. (See “Common properties” on
page 98.)
Property
Values
Description
LCAdminUserID
String
The user ID to assign to the
LiveCycle administrator user. This
User ID is used to log in to
LiveCycle Administration
Console.
LCAdminPassword
String
The password to assign to the
LiveCycle administrator user. This
password is used to log in to
LiveCycle Administration
Console.
Command line interface usage
After you configure your property file, navigate to the [LiveCycleES root]/configurationManager/bin folder.
To view a complete description of the LiveCycle Configuration Manager CLI commands, type
configurationManagerCLI help.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Command line interface usage
102
Note: The LiveCycle Configuration Manager CLI requires that the Sun™ Java™ Software Development Kit
(JDK) 1.5.0_11 or later is installed, the JAVA_HOME environment variable is configured, and the
PATH points to the location where your JDK is installed. For more information, see the Preparing to
Install LiveCycle ES guide for your single or cluster environment.
Configure LiveCycle CLI usage
The Configure LiveCycle operation requires the following syntax:
configureLiveCycle -f [propertyFile]
where:
●
-f [propertyFile] is a property file containing the required arguments. For more information
on creating a property file, see “Command line interface property file” on page 98.
Deploy LiveCycle CLI usage
The Deploy LiveCycle operation requires the following syntax:
deployLiveCycle -f [propertyFile]
where:
●
-f [propertyFile]: A property file containing the required arguments. For more information
on creating a property file, see “Command line interface property file” on page 98.
Initialize LiveCycle CLI usage
The initialize LiveCycle operation requires the following syntax:
initializeLiveCycle -f [propertyFile]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 98.
Initialize Business Activity Monitoring CLI usage
The Initialize Business Activity Monitoring operation requires the following syntax:
initializeBAM -f [propertyFile]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 98.
Deploy LiveCycle Components CLI usage
The Deploy LiveCycle Components operation requires the following syntax:
deployLiveCycleComponents -f [propertyFile] -targetServer_AdminPassword
[password]
where:
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Command line interface usage
103
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 98.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Validate Database Connectivity CLI usage
The Validate Database Connectivity operation is optional and requires the following syntax:
validateDBConnectivity -f [propertyFile] -datasource_dbPasssword
[password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 98.
●
-datasource_dbPassword [password]: Allows you to set the database user password on the
command line. If this argument is present, it will override the datasource.dbPassword property in
the property file.
Validate LiveCycle Server CLI usage
The Validate LiveCycle Server operation is optional and requires the following syntax:
validateLiveCycleServer -f [propertyFile] -targetServer_AdminPassword
[password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 98.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Validate LiveCycle Component Deployment CLI usage
The Validate LiveCycle Component Deployment operation is optional and requires the following syntax:
validateLiveCycleComponentDeployment -f [propertyFile]
-targetServer_AdminPassword [password]
where:
●
-f [propertyFile]: A property file containing the required arguments. For instructions on
creating a property file, see “Command line interface property file” on page 98.
●
-targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword
property in the property file.
Adobe LiveCycle ES
Appendix - LCM Command Line Interface
Installing and Deploying LiveCycle ES for JBoss
Examples usage
104
Examples usage
From the C:\Adobe\LiveCycle8.2\configurationManager\bin, type:
./configurationManagerCLI ConfigureLiveCycle -f cli_propertyFile.txt
where cli_propertyFile.txt is the name of the property file you created.
Error logs
If an error occurs, you can review the CLI error logs located in the [LiveCycleES
root]\configurationManager\log folder. The log file generated has a naming convention such as
lcmCLI.0.log where the number in the file name (0) increments when the log files are rolled over.
Next steps
If you used LiveCycle Configuration Manager CLI to configure and deploy LiveCycle ES, you can now do the
following tasks:
●
Verify the deployment. (See “Final setup for LiveCycle Rights Management ES” on page 37.)
●
Access LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 25.)
●
Configure LiveCycle ES solution components to access LDAP. (See “Configuring LiveCycle ES to access
LDAP” on page 37.)
●
Uninstall LiveCycle ES. (See “Uninstalling LiveCycle ES” on page 56.)
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