bb c Installing and Deploying LiveCycle ES

bb c Installing and Deploying LiveCycle ES
bc
Installing and Deploying LiveCycle® ES
for WebLogic®
Adobe® LiveCycle® ES
February 2008
Version 8.0
© 2008 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle® ES (8.0) Installing and Deploying LiveCycle ES for Microsoft® Windows®, UNIX®, and Linux
Edition 1.2, February 2008
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end-user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Acrobat, FrameMaker, LiveCycle, PageMaker, PhotoShop, Reader, and PostScript are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
BEA Weblogic and BEA WebLogic Server are registered trademarks and BEA WebLogic Platform is a trademark of BEA Systems Inc.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.
Sun, Java, and Solaris, and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the US and other countries.
All other trademarks are the property of their respective owners.
This product contains either BISAFE and/or TIPEM software by RSA Data Security, Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes code licensed from RSA Data Security.
This product includes software developed by the JDOM Project (http://www.jdom.org/).
Macromedia Flash 8 video is powered by On2 TrueMotion video technology. © 1992-2005 On2 Technologies, Inc. All Rights Reserved.
http://www.on2.com.
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
Portions of this code are licensed from Nellymoser(www.nellymoser.com)
MPEG Layer-3 audio compression technology licensed by Fraunhofer IIS and THOMSON Multimedia (http://www.iis.fhg.de/amm/).
This product includes software developed by L2FProd.com (http://www.L2FProd.com/)
The BeanShell library is licensed under the GNU Library General Public License, a copy of which is included with this software.
This product includes software developed by The Werken Company.
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
The OpenOffice.org library is licensed under the GNU Library General Public License, a copy of which is included with this software.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 6
What’s in this document?............................................................................................................................................................ 6
Who should read this document? ............................................................................................................................................ 6
Conventions used in this document ....................................................................................................................................... 7
Additional information................................................................................................................................................................. 8
1
Introduction ................................................................................................................................. 9
About the installation, configuration, and deployment process.................................................................................. 9
Selecting tasks for configuring and deploying LiveCycle ES.......................................................................................... 9
Upgrading to LiveCycle ES........................................................................................................................................................10
Installation, configuration, and deployment lists.............................................................................................................10
Automatic installation and deployment list.................................................................................................................11
Manual installation and deployment list.......................................................................................................................11
2
Installing the Solution Component Files ................................................................................. 12
Installing the product files ........................................................................................................................................................12
Installing to a Windows staging platform for deployment on Linux or UNIX..................................................13
Installing LiveCycle ES ..........................................................................................................................................................13
Viewing the error log ..................................................................................................................................................................15
Next steps........................................................................................................................................................................................15
3
Configuring LiveCycle ES for Deployment .............................................................................. 16
About LiveCycle Configuration Manager ............................................................................................................................16
Configuration tasks: Automatic configuration............................................................................................................17
Configuration tasks: Manual configuration..................................................................................................................17
Deploying LiveCycle ES into a distributed environment ...............................................................................................18
Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES ............................................18
Saving configurations in LiveCycle Configuration Manager..................................................................................19
Uninstalling EAR files ..................................................................................................................................................................20
Next steps........................................................................................................................................................................................21
4
Manually Configuring WebLogic Server.................................................................................. 22
Modifying class files.....................................................................................................................................................................22
Increasing the WebLogic Server stuck thread time-out.................................................................................................23
Configuring the JVM arguments ............................................................................................................................................24
Configuring database connectivity .......................................................................................................................................24
Configuring Oracle database connectivity...................................................................................................................24
Configuring DB2 database connectivity........................................................................................................................26
Configuring SQL Server database connectivity ..........................................................................................................29
Configuring JMS resources for WebLogic Server..............................................................................................................32
Creating JMS destinations ..................................................................................................................................................33
Next step..........................................................................................................................................................................................35
3
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
5
Contents
4
Manually Deploying to WebLogic Server ................................................................................ 36
About deploying LiveCycle ES solution components.....................................................................................................36
WebLogic Server directory name.....................................................................................................................................36
Summary of deployable components............................................................................................................................36
Deploying to WebLogic Server ...............................................................................................................................................37
Restarting WebLogic Server .....................................................................................................................................................37
Next steps........................................................................................................................................................................................39
6
Post-Deployment Activities ...................................................................................................... 40
Configuring Acrobat 8.1 for PDF Generator ES .................................................................................................................40
Final setup for LiveCycle Rights Management ES.............................................................................................................41
Verifying the deployment and accessing LiveCycle Administration Console........................................................41
Accessing LiveCycle Administration Console..............................................................................................................41
Viewing the log files..............................................................................................................................................................42
Accessing solution component web applications ...........................................................................................................42
Accessing Rights Management ES:..................................................................................................................................43
Accessing User Management ..................................................................................................................................................43
Configuring LiveCycle ES to access LDAP............................................................................................................................44
Setting PDF Generator ES Watched Folder performance parameters......................................................................44
Configuring FIPS mode ..............................................................................................................................................................45
Configuring HTML digital signature ......................................................................................................................................46
Configuring the Connector for EMC Documentum service..........................................................................................46
Creating the XDP MIME format in your Documentum repository .......................................................................48
Configuring the Connector for IBM FileNet service .........................................................................................................49
Uninstalling LiveCycle ES...........................................................................................................................................................52
7
Manually Configuring BAM Server for LiveCycle ES ............................................................... 53
Configuring WebLogic Server for BAM Server...................................................................................................................53
Adding required JAR files to the lib directory..............................................................................................................54
Creating a managed server for Business Activity Monitoring ES................................................................................54
Configuring the WebLogic Server JVM ..........................................................................................................................55
Creating and configuring the BAM Server metadata database .................................................................................55
User accounts ..........................................................................................................................................................................55
Configuring your database environment .....................................................................................................................56
Configuring the connection to the BAM Server metadata database..................................................................56
Configuring Process Management ES for BAM Server....................................................................................................57
Deploying BAM Server to the WebLogic Server................................................................................................................58
Configuring LDAP settings for BAM Server.........................................................................................................................61
Limitations of BAM Server LDAP connectivity.............................................................................................................61
Best practices for BAM Server LDAP connectivity......................................................................................................61
Configuring automatic LDAP synchronization ...........................................................................................................62
Configuring LDAP user mapping .....................................................................................................................................63
Configuring LDAP role mapping......................................................................................................................................64
Manually synchronizing with the LDAP server............................................................................................................65
Using the BAM Dashboard........................................................................................................................................................65
Additional documentation .......................................................................................................................................................66
Uninstalling Business Activity Monitoring ES ....................................................................................................................66
8
Advanced Production Configuration....................................................................................... 67
LiveCycle Output ES and LiveCycle Forms ES ....................................................................................................................67
LiveCycle PDF Generator ES .....................................................................................................................................................67
EJB Pool Size Configuration ...............................................................................................................................................67
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
A
Contents
5
Troubleshooting ........................................................................................................................ 69
Getting help ...................................................................................................................................................................................69
Installation considerations .................................................................................................................................................69
Application server considerations ...................................................................................................................................69
Database initialization considerations ...........................................................................................................................70
LiveCycle Configuration Manager hangs when re-deploying a LiveCycle ES EAR file..................................70
Troubleshooting with log files.................................................................................................................................................70
LiveCycle Configuration Manager log file.....................................................................................................................70
Scheduler service configuration for nondefault JNDI URLs..........................................................................................71
Non-clustered environments.............................................................................................................................................71
Error messages ..............................................................................................................................................................................71
PDF Generator ES on Windows fails when converting native files ......................................................................71
Class not found .......................................................................................................................................................................72
JNDI name not found ...........................................................................................................................................................72
Exceptions thrown when initializing the LiveCycle ES database multiple times ...........................................73
XMLForm.exe permission error.........................................................................................................................................73
WebLogic JTA time-out error.............................................................................................................................................73
Failure to deploy adobe-livecycle-weblogic................................................................................................................73
Client connection through a proxy server to WebLogic Server on Windows fails.........................................74
Failure to deploy due to PermGen Space error...........................................................................................................74
Unexpected end of file error..............................................................................................................................................74
About This Document
This guide is one of several resources available to help you learn about Adobe® LiveCycle® ES (Enterprise
Suite). LiveCycle ES is a flexible, extensible platform that helps automate and accelerate the flow of
business-critical information to and from customers, partners, constituents, and employees.
What’s in this document?
This guide provides information about how to install and configure the following solution components on
Microsoft® Windows®, Linux®, and Sun™ Solaris™, and how to deploy the solution components to BEA
WebLogic Server®:
●
Adobe LiveCycle Barcoded Forms ES
●
Adobe LiveCycle Business Activity Monitoring ES
●
Adobe LiveCycle ES Connector for EMC Documentum
●
Adobe LiveCycle ES Connector for IBM FileNet
●
Adobe LiveCycle Digital Signatures ES
●
Adobe LiveCycle Forms ES
●
Adobe LiveCycle Foundation
●
Adobe LiveCycle Output ES
●
Adobe LiveCycle PDF Generator ES
●
Adobe LiveCycle Process Management ES
●
Adobe LiveCycle Reader Extensions ES
●
Adobe LiveCycle Rights Management ES
Who should read this document?
This guide provides information for administrators or developers responsible for installing, configuring,
administering, or deploying LiveCycle ES components. The information provided is based on the
assumption that anyone reading this guide is familiar with J2EE application servers, Linux, Microsoft
Windows, or Solaris operating systems, Oracle®, DB2®, or SQL Server database servers, and web
environments.
6
Adobe LiveCycle ES
About This Document
Installing and Deploying LiveCycle ES for WebLogic
Conventions used in this document
Conventions used in this document
This guide uses the following naming conventions for common file paths.
Name
Default value
Description
[LiveCycleES root]
Windows:
C:\Adobe\LiveCycle8\
The installation directory that is used for all
LiveCycle ES solution components. The
installation directory contains subdirectories
forAdobe LiveCycle Configuration Manager, the
LiveCycle ES SDK, and each LiveCycle ES
solution component installed (along with the
product documentation). This directory also
includes directories relating to third-party
technologies.
Linux and UNIX®:
/opt/adobe/livecycle8/
[appserver root]
The home directory of the
application server that runs the
LiveCycle ES services.
WebLogic Server on Windows:
C:\bea\weblogic92\
WebLogic Server on Linux and Solaris:
/opt/bea/weblogic92
WebLogic Server on AIX:
/usr/bea/weblogic92
[server name]
server1 for WebLogic Server
The name of the server configured on your
application server.
BEA_HOME
The install directory for
WebLogic Server as specified for
the BEA_HOME environment
variable.
WebLogic Server on Windows: C:\bea
The domain that you configured
on WebLogic Server.
WebLogic Server on Windows:
C:\bea\user_projects\domains\base_domain
[appserverdomain]
WebLogic Server on Linux and UNIX: /opt/bea
WebLogic Server on Linux and UNIX:
/opt/bea/user_projects/domains/base_domain
[dbserver root]
The location where the
LiveCycle ES database server is
installed.
Depends on the database type and your
specification during installation.
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux and UNIX). Any platform-specific information is indicated as required.
7
Adobe LiveCycle ES
About This Document
Installing and Deploying LiveCycle ES for WebLogic
Additional information
Additional information
The resources in this table can help you learn more about LiveCycle ES.
For information about
See
General information about LiveCycle ES and LiveCycle ES Overview at
www.adobe.com/go/learn_lc_overview
the solution components
What’s new in the Adobe LiveCycle ES
(Enterprise Suite) release
www.adobe.com/go/learn_lc_whatsNew
LiveCycle ES terminology
www.adobe.com/go/learn_lc_glossary
Other services and products that integrate
with LiveCycle ES
www.adobe.com/products/livecycle
Other Adobe LiveCycle ES solution
components
partners.adobe.com/public/developer/main.html
Installing Adobe LiveCycle Workbench ES
Installing Your Development Environment at
www.adobe.com/go/learn_lc_installWorkbench
Upgrading to LiveCycle ES from a previous
version.
Preparing to Upgrade to LiveCycle ES at
www.adobe.com/go/learn_lc_upgradePreparation
Upgrading to LiveCycle ES for WebLogic at
www.adobe.com/go/learn_lc_upgradeWebLogic
Performing administrative tasks for
LiveCycle ES
Administering LiveCycle ES at
www.adobe.com/go/learn_lc_administration
All the documentation available for
LiveCycle ES
www.adobe.com/go/learn_lc_documentation
LiveCycle ES release information and
last-minute changes that occur to the
product
www.adobe.com/go/learn_lc_releaseNotes
Patch updates, technical notes, and
additional information about this product
version
www.adobe.com/support/products/enterprise
/index.html
8
1
Introduction
This chapter provides information to help you understand the type of installation and deployment you
should perform, and information that will help you understand the installation, configuration and
deployment process:
●
“About the installation, configuration, and deployment process” on page 9
●
“Installation, configuration, and deployment lists” on page 10
For information about preparing your system for installing LiveCycle ES, including system requirements,
see the Preparing to Install LiveCycle ES guide.
About the installation, configuration, and deployment process
Installing, configuring, and deploying LiveCycle ES involves the following processes:
Installing: You install LiveCycle ES by running the installation program. Installing LiveCycle ES places
all of the required files onto your computer, within one installation directory structure. The default
installation directory is C:\Adobe\LiveCycle8 (Windows) or /opt/adobe/LiveCycle8 (Linux or UNIX);
however, you can install the files to a different directory. In this guide, the default installation directory
is referred to as [LiveCycleES root]. (See “Installing the Solution Component Files” on page 12.)
Configuring and assembling: Configuring LiveCycle ES modifies a variety of settings that determine
how LiveCycle ES works. Assembling the product places all of the installed components into several
deployable EAR and JAR files, according to your configuration instructions. You configure and assemble
the components for deployment by running LiveCycle Configuration Manager. (See “Configuring
LiveCycle ES for Deployment” on page 16.) You can configure and assemble multiple LiveCycle ES
solution components at the same time.
Deploying: Deploying the product involves deploying the assembled EAR files and supporting files to
the WebLogic Server on which you plan to run your LiveCycle ES solution. If you have configured and
assembled multiple solution components, the deployable components are packaged within the
deployable EAR files. Components and LiveCycle ES archive files (LCAs) are packaged as JAR files.
Initializing the LiveCycle ES database: Initializing the database to be used with LiveCycle ES creates
tables for use with Adobe User Management and other components. Deploying any solution
component that connects to the LiveCycle ES database requires you to initialize the LiveCycle ES
database after the deployment process. (See “Configuration tasks: Automatic configuration” on
page 17.)
Selecting tasks for configuring and deploying LiveCycle ES
After you perform an installation, you can run LiveCycle Configuration Manager to perform a variety of
tasks:
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
●
Configure application server properties to support LiveCycle ES
●
Validate application server configuration
●
Deploy LiveCycle ES EAR files
9
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES component deployment
●
Validate the LiveCycle ES component deployment
●
Configure the LiveCycle Reader Extensions ES Rights credential
●
Import the LiveCycle ES Samples
Introduction
Upgrading to LiveCycle ES
10
If you install Reader Extensions ES, you can also specify and import the Reader Extensions ES Rights
credential required for applying usage rights to PDF documents.
Although you can use LiveCycle Configuration Manager to configure the application server and set up
data sources to the database, you may prefer to complete these steps manually.
Here are reasons to configure your application server manually [You may want to configure your
application server manually for these reasons]:
●
You have other applications running on the application server and are concerned about possible
conflicting configurations.
●
Corporate security procedures for configuration management dictate finer control.
●
You are performing deployments where automatic configuration is not available.
In the manual configuration case, you will do the following tasks:
●
Use LiveCycle Configuration Manager to configure LiveCycle ES components to get the required font
and temp directories.
●
Manually configure the application server, configure datasources, and deploy LiveCycle ES EAR files.
●
Run LiveCycle Configuration Manager to initialize the database.
Upgrading to LiveCycle ES
Before installing LiveCycle ES for upgrading from LiveCycle 7.x and later, ensure that you have completed
the tasks described in Preparing to Upgrade to LiveCycle ES at
www.adobe.com/go/learn_lc_upgradePreparation.
Installation, configuration, and deployment lists
This section includes lists that you can use to step through the installation and configuration process. A list
is provided for installing and configuring when using either the automatic method or the manual method.
The automatic method refers to using LiveCycle Configuration Manager to configure LiveCycle ES,
configuring the application server, and deploying the solution components to the server. You would use
the automatic method if you want to have limited input into the installation, configuration, and
deployment of LiveCycle ES.
The manual method refers to using LiveCycle Configuration Manager to only configure LiveCycle ES and
initialize (bootstrap) the database. Configuring the application server, connecting to the database, and
deploying to the server is done by the administrator manually by following the instructions later in this
document. You would use the manual method if you want to have precise input into the installation,
configuration, and deployment of LiveCycle ES. For example, this method may be used in a locked-down
server environment.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Introduction
Automatic installation and deployment list
11
Automatic installation and deployment list
The following list includes the steps required for installing LiveCycle ES solution components using the
automatic method. WebLogic Server must be installed before you perform the installation.
●
Ensure that you have the required software installed in the target environment. For more information,
see Preparing to Install LiveCycle ES.
●
Run the installation program. (See “Installing the Solution Component Files” on page 12.)
●
Run LiveCycle Configuration Manager and select all the tasks on the Task Selection screen. This step
will configure and assemble the LiveCycle ES EAR files, configure application server settings, deploy the
EAR files and other components to the application server, initialize the LiveCycle ES database, and
verify the deployment. (See “Configuring LiveCycle ES for Deployment” on page 16.)
●
Access LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 41.)
●
Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 44.)
Manual installation and deployment list
The following list includes the steps required for installing LiveCycle ES using the manual method. Your
application server must be installed and configured before you perform the installation.
●
Ensure that you have the required software installed and configured in the target environment. For
more information, see Preparing to Install LiveCycle ES at www.adobe.com/go/learn_lc_prepareInstall.
●
Run the installation program. (See “Installing the Solution Component Files” on page 12.)
●
Run LiveCycle Configuration Manager and select the Configure LiveCycle ES EARs task. This step will
configure and assemble LiveCycle ES. For more information, see “Configuring LiveCycle ES for
Deployment” on page 16.
●
Configure WebLogic Server settings. A variety of settings must be configured. (See “Manually
Configuring WebLogic Server” on page 22.)
●
Deploy the EAR files to the application server. You can do this manually or use
LiveCycle Configuration Manager. (See “Manually Deploying to WebLogic Server” on page 36.)
●
Run LiveCycle Configuration Manager to deploy LiveCycle ES component files, and optionally deploy
product samples. (See “Configuring LiveCycle ES for Deployment” on page 16.)
●
Access LiveCycle Administration Console and User Management. (See “Accessing LiveCycle
Administration Console” on page 41.)
●
Configure LDAP access. (See “Configuring LiveCycle ES to access LDAP” on page 44.)
2
Installing the Solution Component Files
This chapter describes how to use the installation program to install LiveCycle ES on a Windows, Linux, or
UNIX operating system.
Before you install the solution components, you must ensure that your environment includes the software
and hardware required to run LiveCycle ES. You should also understand the installation options and have
prepared the environment as required. (See Preparing to Install LiveCycle ES.)
This chapter covers the following topics:
●
“Installing the product files” on page 12
●
“Viewing the error log” on page 15
Installing the product files
When you run an installation program, you need the following information:
●
The serial number for the solution components you are installing
●
The type of installation and configuration you are performing
Note: To successfully install, you need read and write permissions for the installation directory. The
following installation directories are the defaults; however, you can specify a different directory as
required:
●
(Windows) C:\Adobe\LiveCycle8\
●
(Linux and UNIX) /opt/adobe/livecycle8/
When installing on Linux, the installation program uses the logged-in user's home directory as a
temporary directory for storing files. As a result, messages such as the following text may appear in the
console:
WARNING: could not delete temporary file /home/<username>/ismp001/1556006
When you complete the installation, you must manually delete the temporary files.
Caution: Ensure that the temporary directory for your operating system meets the minimum
requirements as outlined in Preparing to Install LiveCycle. The temporary directory is one of the
following locations:
●
(Windows) TMP or TEMP path as set in the environment variables
●
(Linux and UNIX) Logged-in user’s home directory
The InstallShield command line parameter -is:tempdir is not supported with the
LiveCycle ES installer. To work around this limitation, use the TMP environment variable to point
to a disk that has the required amount of free space.
On Linux systems, you can install, configure, and deploy as a non-root user:
●
(Solaris) /var/tmp
12
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for WebLogic
Installing to a Windows staging platform for deployment on Linux or UNIX
13
Note: When you are installing the solution components on a Linux or UNIX operating system, you must be
logged in as the root user to successfully install the solution components to the default location,
which is /opt/adobe/LiveCycle8/. If you are logged in as a non-root user, you must change the
installation directory to one for which you have permissions (read-write-execute privileges). For
example, you could change the directory to home/adobe/livecycle8.
Installing to a Windows staging platform for deployment on Linux or UNIX
LiveCycle ES can be installed and configured on Windows for deployment on a Linux or UNIX platform. You
can use this functionality for installing to a locked-down Linux environment. For example, a locked-down
environment would not have XWindows installed. When you run the installation program on Windows,
you can choose a Linux or UNIX operating system as the target platform for deploying LiveCycle ES. The
installation program installs binaries for AIX, Linux, or Solaris that are also used by
LiveCycle Configuration Manager when you configure the product.
The Windows computer can then be used as a staging location for the deployable objects, which can be
copied to a Linux or UNIX computer for deployment to the application server. The application server that
you are targeting must be consistent with what you choose during installation and configuration
regardless of the operating system.
Note: If your installation includes LiveCycle PDF Generator ES and you will use the native application
conversion feature, the host and target operating system must be Windows.
Installing LiveCycle ES
This section covers the initial installation of LiveCycle ES. For information about configuration and
deployment, see “Configuring LiveCycle ES for Deployment” on page 16.
Note: To avoid permission issues during the deployment, ensure that you are logged in as the user who
will run the WebLogic process when you run the LiveCycle ES installer and
LiveCycle Configuration Manager.
➤ To install LiveCycle ES:
1. Navigate to the /livecycle_server/8.0 directory of the installation media.
2. Start the installation program:
●
(Windows) Double-click the win_livecycle8_setup.exe file.
●
(Linux, UNIX) From a command prompt, type the file name appropriate for your operating system:
./aix_livecycle8_setup.bin
./linux_livecycle8_setup.bin
./solaris_livecycle8_setup.bin
3. When prompted, select the language for the installation to use, and then click OK.
4. On the Welcome screen, click Next.
5. On the Destination screen, accept the default directory as listed or click Browse and navigate to the
directory where you want to install the solution component, and then click Next.
Note: If you type in the name of a directory that does not exist, it will be created for you.
Adobe LiveCycle ES
Installing the Solution Component Files
Installing and Deploying LiveCycle ES for WebLogic
Installing LiveCycle ES
14
Caution: When you install the solution component, you can specify a different installation location. If you
are installing on Linux or UNIX, the directory you specify should not contain any spaces; if it
does, the installation program does not install the solution component.
6. Type a serial number in the text box and click Add. If you have licensed multiple solution components,
repeat this step for each serial number you have. After you add all the serial numbers to the list, click
Next.
Tip: To reset the serial number, click Clear.
7. Read the Product License Agreement. If you agree, select I accept to the terms of the license
agreement, and then click Next.
8. (Windows staging only) Select the operating system for which you plan to configure LiveCycle ES and
click Next.
Note: At this point, you can specify to use Windows as a staging platform for your deployment. You can
select Linux or a UNIX operating system as the target for deployment even if you are installing
on Windows. For more details see “Installing to a Windows staging platform for deployment on
Linux or UNIX” on page 13.
9. (PDF Generator ES for Windows only) Select the appropriate option on the PDF Generator ES screen:
●
If you select Yes, enable native application support for PDF Generator ES, the software will
check the version of Adobe Acrobat® you have installed. If you do not have Acrobat installed, accept
the prompt to install Acrobat 8.1 now.
If you have an unsupported version of Acrobat installed, complete the LiveCycle ES installation,
uninstall Acrobat, and then install Acrobat 8.1 from the LiveCycle ES installation media by following
the instructions in the procedure “Configuring Acrobat 8.1 for PDF Generator ES” on page 40.
●
If you are installing in a clustered environment, select No, do not enable native application
support for PDF Generator ES and then go to step 11.
10. (PDF Generator ES for Windows only) Confirm that you have Acrobat installed and click Next.
11. Review the installation details and click Install. The installation program displays the progress of the
installation. A summary screen appears when the solution component installation is completed.
12. Review the release notes that are displayed and click Next.
13. Select Start LiveCycle Configuration Manager and then click Finish.
Note: Selecting the Start option starts LiveCycle Configuration Manager, allowing you to complete your
configuration and deployment immediately. If you are not ready to run
LiveCycle Configuration Manager immediately, ensure that Start
LiveCycle Configuration Manager is not selected when you click Finish. You can start
LiveCycle Configuration Manager later, when you are ready. (See “Running
LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18.)
When you are ready to proceed with the configuration and deployment, see “Configuring
LiveCycle ES for Deployment” on page 16.
Note: (PDF Generator ES for Windows only) If you did not choose to install Acrobat 8.1 using the
LiveCycle ES installer, you must complete the steps listed in “Configuring Acrobat 8.1 for
PDF Generator ES” on page 40.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Installing the Solution Component Files
Viewing the error log
15
Viewing the error log
If any errors occur during the installation, the installation program creates a log file called log.txt, which
contains the error messages. The log file is located in the [LiveCycleES root] directory.
For information about errors that may occur during installation, see “Troubleshooting” on page 69.
Next steps
You must now configure LiveCycle ES for deployment. (See “Configuring LiveCycle ES for Deployment” on
page 16.)
3
Configuring LiveCycle ES for Deployment
This chapter describes how to use LiveCycle Configuration Manager to perform any of the following tasks:
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
●
Configure application server properties to support LiveCycle ES
●
Validate the application server configuration
●
Deploy LiveCycle ES EAR files
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES components
●
Validate the LiveCycle ES component deployment
●
Configure the LiveCycle Reader Extensions ES Rights credential
●
Import the LiveCycle ES Samples
This chapter contains the following sections:
●
“About LiveCycle Configuration Manager” on page 16
●
“Deploying LiveCycle ES into a distributed environment” on page 18
●
“Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18
●
“Uninstalling EAR files” on page 20
This chapter assumes that you have prepared your environment for hosting LiveCycle ES and installed the
solution component files. If you have not done this, see the Preparing to Install LiveCycle ES guide and
“Installing the Solution Component Files” on page 12.
About LiveCycle Configuration Manager
LiveCycle Configuration Manager is a wizard-like tool used to configure, deploy and validate LiveCycle ES
components for deployment to the application server. You have the option of using
LiveCycle Configuration Manager to configure the application server and deploy the product EAR files to
the application server.
LiveCycle Configuration Manager is installed with the solution component files when you run the
LiveCycle ES installation program. When you run LiveCycle Configuration Manager, you specify the
LiveCycle ES solution components you are configuring, as well as the tasks you want
LiveCycle Configuration Manager to perform.
You can start LiveCycle Configuration Manager from the installation program to configure solution
components during the installation process, or you can start LiveCycle Configuration Manager any time
after the installation. If you are planning to use LiveCycle Configuration Manager to configure the
application server or deploy to the application server, the application server must be started to enable
LiveCycle Configuration Manager to perform configuration tasks on it.
You can configure an application server that is installed on a different computer than the one on which
you are running LiveCycle Configuration Manager. However, an application server must also be installed
(but does not have to be running) on the LiveCycle Configuration Manager computer so that
16
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring LiveCycle ES for Deployment
Configuration tasks: Automatic configuration
17
LiveCycle Configuration Manager can use the application server library files. For more information, see
“Installing to a Windows staging platform for deployment on Linux or UNIX” on page 13.
Configuration tasks: Automatic configuration
LiveCycle Configuration Manager provides an interface that prompts you for information so that it can
automatically accomplish the following tasks:
1. Configure LiveCycle ES EAR files for deploying to the application server.
2. Configure application server properties, such as creating Java™ Message Service (JMS) topics and
queues, and configuring the Java Virtual Machine (JVM) settings and data sources so that the
application server can run LiveCycle ES.
3. Validate that the application server is configured correctly for running LiveCycle ES server solution
components.
4. Deploy LiveCycle ES EAR files to the application server.
5. Initialize the database. This is a process that prepares the installed and configured database for use
with LiveCycle ES by populating it with the schemas and data required to support LiveCycle ES services.
You only need to initialize the database the first time you deploy the product.
6. Deploy LiveCycle ES components and archive files to the application server.
7. Validate components and archive file deployment.
8. Configure the LiveCycle Reader Extensions ES Rights credential.
9. Import LiveCycle ES Samples.
Optionally, step 2 (configure application server properties) and step 4 (deploy EAR files) can be performed
manually (without using LiveCycle Configuration Manager).
Regardless of whether all of the tasks are performed automatically by LiveCycle Configuration Manager or
only some are performed manually, the tasks must be performed in the order in which they are listed.
Configuration tasks: Manual configuration
To manually configure the application server and deploy the EAR files, you perform the following tasks:
1. Run LiveCycle Configuration Manager and select the task to configure and assemble LiveCycle ES
solution component properties and assemble them into EAR files for deploying to the application
server.
2. Manually configure the application server by following the instructions in this document. (See
“Manually Configuring WebLogic Server” on page 22.)
3. Deploy the LiveCycle ES EAR files by following the instructions in this document. (See “Manually
Deploying to WebLogic Server” on page 36.)
4. Run LiveCycle Configuration Manager and select the tasks to initialize the database, deploy
components and archives, and validate component and archive deployment.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebLogic
Deploying LiveCycle ES into a distributed environment
18
5. Verify that the deployed LiveCycle ES services and solution components are available and operational
by logging in to LiveCycle Administration Console.
Deploying LiveCycle ES into a distributed environment
If the Managed Server is on a different server, and not on the server with the Admin Server, you must
manually deploy the LiveCycle EAR files. If you attempt to deploy with LiveCycle Configuration Manager,
you will receive an error message indicating that the deployment failed.
Running LiveCycle Configuration Manager to configure and
deploy LiveCycle ES
When you run LiveCycle Configuration Manager, you can select the tasks that you want the program to
perform automatically.
Note: Using LiveCycle Configuration Manager to deploy LiveCycle ES solution components to remote
servers is supported only for node-managed application servers, and not for stand-alone
application servers.
Tip: LiveCycle Configuration Manager verifies the values that are specified on each screen when you click
Next. If it cannot validate a value, a warning appears, the property on the screen turns red, and you
cannot proceed until you enter a valid value.
When LiveCycle Configuration Manager completes the configuration, it places the files to be deployed to
the application server (adobe-livecycle-native weblogic-[OS].ear, adobe-livecycle weblogic.ear, and
adobe-workspace-client.ear) in the following directory:
●
(Windows) [LiveCycleES root]\configurationManager\export
●
(Linux, UNIX) [LiveCycleES root]/configurationManager/export
If you plan to manually deploy LiveCycle ES to the application server, you can find the files in the
appropriate directory. (See “Uninstalling LiveCycle ES” on page 52.)
If you are configuring a remote application server, ensure that an application server is also installed on the
LiveCycle Configuration Manager computer so that LiveCycle Configuration Manager can use the
application server library files.
➤ To perform configuration or deployment tasks using LiveCycle Configuration Manager:
1. Start the application server.
2. Start LiveCycle Configuration Manager by navigating to the [LiveCycleES root]/configurationManager/
bin directory and entering the following command:
●
(Windows) ConfigurationManager.bat
●
(Linux and UNIX) ./ConfigurationManager.sh
3. On the Welcome screen, click Next.
4. On the Upgrade Selection screen, ensure that Upgrade LiveCycle 7.x is not selected, and then click
Next.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebLogic
Saving configurations in LiveCycle Configuration Manager
19
5. On the Solution Component screen, select the LiveCycle ES solution components to configure and
deploy and click Next.
6. On the Task Selection screen, select all the tasks you want to perform and click Next.
Note: If you do not want to configure the application server and deploy LiveCycle ES using
LiveCycle Configuration Manager, select the Configure LiveCycle ES task only. After
completing this task in LiveCycle Configuration Manager, you must configure the application
server, deploy the configured EAR files, and return to LiveCycle Configuration Manager to
initialize the database, and deploy and validate the component files. (See “Next steps” on
page 21.)
Caution: Do not import the LiveCycle ES Samples if you are doing either of the following tasks:
●
If you are deploying LiveCycle ES to a production system. Importing the samples creates
users with default passwords, which may be a security concern for your production
environment.
●
If you are deploying either the Connector for EMC Documentum service or the
Connector for IBM FileNet service and you want to import LiveCycle ES Samples into the
Documentum repository or FileNet object store, you need to skip this step. You can import
the samples after you configure, enable, and activate the ECM to be the repository provider
using LiveCycle Administration Console. For more information, see “Configuring the
Connector for EMC Documentum service” on page 46 or “Configuring the
Connector for IBM FileNet service” on page 49.
7. Follow the instructions on the LiveCycle Configuration Manager screens. For more information about
the content or input required for any screen, press the F1 key on your keyboard to view Help for that
screen.
Note: LiveCycle Configuration Manager requires you to enter the IP address, or qualified host name, of the
server running the application server. The default value of localhost will not work.
Caution: LiveCycle Configuration Manager cannot configure WebSphere Application Server if global
security is enabled — you must do this manually (see “Configuring WebSphere Application
Server with global security enabled” on page 24).
During configuration, you are required to provide the location of the JDBC drivers for your database. The
sections that follow provide the location of these drivers. The Oracle and DB2 drivers are in the [LiveCycleES
root]/lib/db/[database] directory. If you have not already done so, install the SQL Server database driver.
➤ To install the SQL Server database driver:
1. Download the SQL Server 2005 JDBC 1.1 database driver from the Microsoft website.
2. (Windows) Run the file. Extract the files to a temporary directory (referred to as the [SQL_root] directory
in the remainder of this section).
3. (Linux) Extract the *.tar.gz files to a temporary directory (referred to as the [SQL_root] directory in the
remainder of this section). The JDBC driver file is [SQL_root]/sqljdbc_1.1/enu/sqljdbc.jar.
Saving configurations in LiveCycle Configuration Manager
If you have set a series of configuration options in LiveCycle Configuration Manager, you can save the
configuration information so that if you run LiveCycle Configuration Manager again, you can use the same
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebLogic
Uninstalling EAR files
20
configuration settings. When you run LiveCycle Configuration Manager again, you can select the saved
configuration and fields will be populated with the saved information.
Configuration information is saved with the .properties file name extension.
You can use LiveCycle Configuration Manager to revert all the current values back to the default values.
➤ To save a configuration:
1. In LiveCycle Configuration Manager, select Display Menu at the bottom of the screen.
2. Select Configurations > Save As.
3. Navigate to the directory where you want to save your configuration, type a name for the
configuration, and click Save.
➤ To open a saved configuration:
1. In LiveCycle Configuration Manager, select Display Menu at the bottom of the window, if it is not
already selected.
2. Select Configurations > Open.
3. Select the configuration you want to use and click Open.
➤ To revert to default values:
1. In LiveCycle Configuration Manager, select Display Menu at the bottom of the window, if it is not
already selected.
2. Select Configurations > Reset to Defaults.
Uninstalling EAR files
To redeploy a LiveCycle ES solution component, you must first uninstall the LiveCycle ES-related
applications from the application server.
For example, if you have assembled LiveCycle ES solution components again to configure solution
component properties differently and the previous adobe-livecycle-weblogic.ear file is already deployed,
you must uninstall it before deploying the newly assembled EAR files.
➤ To uninstall the ear files:
1. Start the Administration Server and the Managed Server.
2. Start WebLogic Server Administration Console by typing http://localhost:7001/console in
the URL line of a web browser.
3. In the navigation tree, select Deployments > Applications.
4. Click Lock and Edit.
5. Select the LiveCycle application box.
6. On the Deploy tab, click Stop Application.
Adobe LiveCycle ES
Configuring LiveCycle ES for Deployment
Installing and Deploying LiveCycle ES for WebLogic
Next steps
21
7. Click Delete for the stopped application, click Yes, and then click Continue.
8. Repeat steps 5 to 7 for the other deployed LiveCycle ES components.
9. Click Save, and then click Activation changes.
10. Stop and start the Administration Server and the Managed Server.
After uninstalling the EAR file, you may need to reconfigure your EAR file and redeploy. See “Running
LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18.
Next steps
If you used LiveCycle Configuration Manager to configure and deploy LiveCycle ES, you can now do the
following tasks:
●
Verify the deployment. (See “Final setup for LiveCycle Rights Management ES” on page 41.)
●
Access LiveCycle Administration Console. (See “Accessing LiveCycle Administration Console” on
page 41.)
●
Configure LiveCycle solution components to access LDAP. (See “Configuring LiveCycle ES to access
LDAP” on page 44.)
●
Uninstall LiveCycle ES. (See “Uninstalling LiveCycle ES” on page 52.)
If you did not configure your application server for deployment, you must now configure your application
server. (See “Manually Configuring WebLogic Server” on page 22.)
4
Manually Configuring WebLogic Server
This chapter describes how to manually configure WebLogic Server to prepare for the deployment of
LiveCycle ES.
Note: You must have configured your WebLogic Server according to the instructions in the “Configuring
WebLogic Server” chapter of Preparing to Install LiveCycle ES at
www.adobe.com/go/learn_lc_prepareInstall.
Note: This chapter assumes that you have started the WebLogic Administration Server, Node Manager,
and the Managed Server.
Note: The Adobe LiveCycle Configuration manager uses a different naming convention for JMS queues
and topics than provided in this manual configuration section. For a complete listing of the
differences search the Support Knowledgebase for the technote entitled Different naming
conventions used for JMS queues and topics.
This chapter includes the following information:
●
“Modifying class files” on page 22
●
“Configuring the JVM arguments” on page 24
●
“Increasing the WebLogic Server stuck thread time-out” on page 23
●
“Configuring database connectivity” on page 24
●
“Configuring JMS resources for WebLogic Server” on page 32
Modifying class files
LiveCycle ES requires the JDBC driver for your database and the pop3 JAR file for email support to be
correctly set up for WebLogic Server.
➤ To copy the JDBC drivers and JAR files:
1. Under the [appserverdomain] directory, create a new directory called idplib.
2. Copy the JDBC drivers for your database from the [LiveCycleES root]\lib\db directory to the
[appserverdomain]/idplib directory. For Microsoft SQL Server, download the JDBC drivers from the
Microsoft website.
Note: For the specific version of the JDBC drivers, see Preparing to Install LiveCycle ES.
3. Copy the pop3.jar library from the [LiveCycleES root]\lib\weblogic directory to the
[appserverdomain]/idplib directory.
➤ To modify the class path of a managed server:
1. To access the WebLogic Administration Console, type http://[host name]:[port]/console in
the URL line of a web browser, where [port] is the non-secure listening port. By default, this port
value is 7001.
22
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Increasing the WebLogic Server stuck thread time-out
23
2. On the login screen, type your WebLogic user name and password and click Log In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server
name.
5. In the Settings for Server pane, click the Configuration tab and the Server Start tab.
6. In the Class Path box, type the location and file name for the following JAR files in the order shown:
●
pop3.jar
●
weblogic.jar (WebLogic Server JAR file)
●
tools.jar (WebLogic Server JAR file)
●
ojdbc.jar (JDBC driver file)
For example, enter the following text:
C:\Adobe\LiveCycle8\lib\weblogic\pop3.jar;C:\bea\weblogic92\server\lib\
weblogic.jar;C:\bea\jrockit90_150_04\lib\tools.jar;C:\Adobe\LiveCycle8\
lib\db\oracle\ojdbc14.jar
7. In the Arguments box, add the following arguments separated by a comma delimiter:
-Djava.security.policy=[WebLogicHome]\server\lib\weblogic.policy
-Dadobeidp.RootDirectory=[AppServerdomain]
-Djava.net.preferIPv4Stack=true
-Dfile.encoding=utf8
Replace WebLogicHome with the WebLogic home directory, as shown in this example:
-Djava.security.policy=\opt\bea\weblogic92\server\lib\weblogic.policy
Replace AppServerdomain with the domain directory, as shown in this example:
-Dadobeidp.RootDirectory=\opt\bea\user_projects\domains\base_domain\
8. Click Save and then click Activate Changes.
Increasing the WebLogic Server stuck thread time-out
Depending on your deployment, LiveCycle ES EAR files can get large. To avoid EAR file deployment
time-outs, you must increase the WebLogic Server stuck thread maximum time-out value. This value is the
length of time that the WebLogic Administration Server will treat a long running thread as still active. After
this threshold is reached, WebLogic Server will attempt to remove this thread.
➤ To configure the transaction and stuck thread time-outs:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Log In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server
name.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring the JVM arguments
24
5. In the Settings for Server pane, click the Configuration tab and the Tuning tab.
6. In the Stuck Thread Max Time box, type 1200.
7. Click Save and then click Activate Changes.
Configuring the JVM arguments
Whether you are using the BEA JRockit JVM under Windows or Linux, or the Sun JVM under Solaris, you
must increase the memory allocation for the virtual machine from 512 MB to 1024 MB.
➤ Increase the memory allocation for the JVM of a managed server:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Under Change Center, click Lock & Edit.
3. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server
name.
4. On the next screen, click the Configuration tab and the Server Start tab.
5. In the Arguments box, append this information to the end of the current content:
●
(Solaris) -Xms256m -Xmx1024m -XX:MaxPermSize=256m
●
(Windows, Linux) -Xms256m -Xmx1024m
6. Click Save and then click Activate Changes.
7. Restart WebLogic managed server.
Configuring database connectivity
This section describes how to configure the JDBC data source for your LiveCycle ES database.
Configuring Oracle database connectivity
To enable WebLogic Server and your LiveCycle ES deployment to connect to the Oracle 10g database, you
must create a database connection for WebLogic Server by setting up a connection pool and a data
source.
➤ To create a new data source for Oracle:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain and then click Log
In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring Oracle database connectivity
25
5. On the next screen, set the following properties:
●
In the Name box and JNDI name box, type IDP_DS.
●
In the Database Type list, select Oracle.
●
In the Database Driver list, select Oracle’s Driver (Thin) Versions: 9.0.1,9.2.0,10.
6. Click Next and, on the next screen, select Supports Global Transactions and Emulate Two-Phase
Commit.
7. Click Next and, on the next screen, define the following properties that apply to the Oracle database
that you created during your LiveCycle ES installation preparations:
Database Name: The name of the database you have created.
Host Name: The name or IP address of the computer on which Oracle is running.
Port: Keep the default value.
Database User Name: The name of the user you created on the Oracle database.
Password and Confirm Password: The password associated with the user.
8. Click Next and then click Test Configuration to verify the configuration settings
Note: If the test is successful, a “Connection test succeeded” message will appear. Click Next. Otherwise,
review the error message that appears and modify the settings as required until the test succeeds.
9. On the next screen, select the server that the data source will connect to (in this case, the managed
server).
10. Click Finish.
➤ To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click IDP_DS.
2. On the next screen, click the Configuration tab and the Connection Pool tab.
3. In the Maximum Capacity box, type 100.
4. Click Save and then click Activate Changes.
5. Restart WebLogic managed server.
➤ To create a new data source for Oracle for LiveCycle Rights Management ES:
Note: This procedure applies only if you have installed LiveCycle Rights Management ES.
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Sign In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New.
5. On the next screen, set the following properties:
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring DB2 database connectivity
●
In the Name box, type RM_DS.
●
In the JNDI Name box, type EDC_DS.
●
In the Database Type list, select Oracle.
●
In the Database Driver list, select Oracle’s Driver (Thin) Versions: 9.0.1,9.2.0,10.
26
6. Click Next and, on the next screen, select Supports Global Transactions and Emulate Two-Phase
Commit.
7. Click Next and, on the next screen, define the following properties that apply to the Oracle database
you created during your LiveCycle ES install preparations:
Database Name: The name of the database you have created.
Host Name: The name or IP address of the computer on which Oracle is running.
Port: Keep the default value.
Database User Name: The name of the user you created on the Oracle database.
Password and Confirm Password: The password associated with the user.
8. Click Next and then click Test Configuration to verify the configuration settings.
Note: If the test is successful, a “Connection test succeeded” message will appear. Click Next. Otherwise,
review the error message that appears and modify the settings as required until the test succeeds.
9. On the next screen, select the server to which the data source will connect (in this case, the managed
server).
10. Click Finish.
➤ To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click IDP_DS.
2. On the next screen, click the Configuration tab and the Connection Pool tab, and set the following
properties:
●
In the Initial Capacity box, type 10.
●
In the Maximum Capacity box, type 30.
●
In the Capacity Increment box, type 5.
●
In the Statement Cache Size box, type 100.
3. Click Save and then click Activate Changes.
4. Restart WebLogic managed server.
Configuring DB2 database connectivity
To enable WebLogic Server and your LiveCycle ES deployment to connect to the DB2 database, you must
create a database connection for WebLogic Server by setting up a connection pool and a data source.
➤ To Install the DB2 database driver:
●
Copy the db2jcc.jar, db2jcc_license_cu.jar file from one of these locations to the
[appserverdomain]/idplib directory:
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring DB2 database connectivity
27
●
The java directory under your [dbserver root] directory (for example, [dbserver root]/ibm/Sqllib/java
(Windows) or [dbserver root]/java (Linux or UNIX)).
●
[LiveCycleES root]\lib\db\db2
➤ To create a new data source for DB2:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Log In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New.
5. On the next screen, set the following properties:
●
In the Name box and the JNDI name box, type IDP_DS.
●
In the Database Type list, select DB2.
●
In the Database Driver list, select Other.
6. Click Next and, on the next screen, select Supports Global Transactions and Emulate Two-Phase
Commit.
7. Click Next and, on the next screen, define the following properties that apply to the database you
created during your LiveCycle ES install preparations:
Database Name: The name of the database you have created.
Host Name: The name or IP address of the computer on which DB2 is running.
Port: Database port. The default is 50000.
Database User Name: The name of the user you created on the DB2 database.
Password and Confirm Password: The password associated with the user.
8. Click Next and, on the next screen, set the following properties:
●
In the Driver Class Name box, type weblogic.jdbc.db2.DB2Driver.
●
In the URL box, type jdbc:bea:db2://[host name]:[port].
●
In the Properties box, type user=<userid> (userid as mentioned in Database User
Name).
9. Click Test Configuration to verify the configuration settings.
Note: If the test is successful, a “Connection test succeeded” message will appear. Click Next. Otherwise,
review the error message that appears and modify the settings as required until the test succeeds.
10. On the next screen, select the server that the data source will connect to (in this case, the managed
server).
11. Click Finish and Activate Changes.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring DB2 database connectivity
28
➤ To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click IDP_DS.
2. On the next screen, click the Configuration tab and the Connection Pool tab.
3. In the Maximum Capacity box, type 100.
4. Click Save and then click Activate Changes.
5. Restart WebLogic managed server.
➤ To create a new data source for DB2 for LiveCycle Rights Management ES:
Note: This procedure applies only if you have installed LiveCycle Rights Management ES.
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Sign In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New.
5. On the next screen, set the following properties:
●
In the Name box, type RM_DS.
●
In the JNDI Name box, type EDC_DS.
●
In the Database Type list, select DB2.
●
In the Database Driver list, select Other.
6. Click Next and, on the next screen, select Supports Global Transactions and Emulate Two-Phase
Commit.
7. Click Next and, on the next screen, define the following properties that apply to the DB2 database you
created during your LiveCycle ES install preparations:
Database Name: The name of the database you have created.
Host Name: The name or IP address of the computer on which DB2 is running.
Port: Database port. The default is 50000.
Database User Name: The name of the user you created on the DB2 database.
Password and Confirm Password: The password associated with the user.
8. Click Next and, on the next screen, set the following properties:
●
In the Driver Class Name box, type weblogic.jdbc.db2.DB2Driver.
●
In the URL box, type jdbc:bea:db2://[hostname]:[port].
●
In the Properties box, type user=<userid> (userid as mentioned in Database User
Name).
Note: Driver Class Name, URL, and Properties will vary depending on the DB2 driver you installed.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring SQL Server database connectivity
29
9. Click Test Configuration to verify the configuration settings.
Note: If the test is successful, a “Connection test succeeded” message will appear. Click Next.
Otherwise, review the error message that appears and modify the settings as required until the
test succeeds.
10. On next screen, select the server that the data source will connect to (in this case, the managed server).
11. Click Finish and Activate Changes.
Configuring SQL Server database connectivity
To enable WebLogic Server and your LiveCycle ES deployment to connect to the SQL Server database, you
must create a database connection for WebLogic Server by setting up a connection pool and a data
source.
➤ To install the SQL Server database driver:
●
If you have not done so already, download the SQL Server 2005 JDBC Driver 1.1 from the following
location on the Microsoft website:
http://www.microsoft.com/downloads/details.aspx?familyid=6d483869-816a-44cb-9787-a866235
efc7c&displaylang=en
Follow the instructions on the website for downloading and installing the driver. Take note of the
directory location where you install the driver on your system.
➤ To add the sqljdbc.jar file to the class path:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Sign In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server
name.
5. On the next screen, click the Configuration tab and the Server Start tab.
6. In the Class Path box, type the location and file name for the sqljdbc.jar file to class path, such as in this
example:
DOMAIN_HOME\idplib\sqljdbc.jar
where DOMAIN_HOME is location of the base domain, such as
c:/bea/user_projects/domains/base_domain
7. Click Save and then click Activate Changes.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring SQL Server database connectivity
30
➤ To create a new data source for SQL Server:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Sign In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > JDBC > click Data Sources and, in the right pane, click New.
5. On the next screen, set the following properties:
●
In the Name box and the JNDI Name box, type IDP_DS.
●
In the Database Type list, select MS SQL Server.
●
In the Database Driver list, select Microsoft's MS SQL Server Driver (Type 4) Versions:2005.
6. Click Next and, on the next screen, select Supports Global Transactions and Emulate Two-Phase
Commit.
7. Click Next, and on the next screen, define the following properties that apply to the SQL Server
database you created during your LiveCycle ES install preparations:
Database Name: The name of the database you have created.
Host Name: The name or IP address of the computer on which SQL Server is running.
Port: The database port. The default is 1433.
Database User Name: The name of the user you created on the SQL Server database.
Password and Confirm Password: The password associated with the user.
8. Click Next and then click Test Configuration to verify the configuration settings.
Note: If the test is successful, a “Connection test succeeded” message will appear. Click Next. Otherwise,
review the error message that appears and modify the settings as required until the test succeeds.
9. On the next screen, select the server that the data source will connect to (in this case, the managed
server.)
10. Click Finish and then click Activate Changes.
➤ To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click IDP_DS.
2. On the next screen, click the Configuration tab and the Connection Pool tab.
3. In the Maximum Capacity box, type 100.
4. Click Save and then click Activate Changes.
5. Restart WebLogic managed server.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Configuring SQL Server database connectivity
31
➤ To create a new data source for SQL Server for LiveCycle Rights Management ES:
Note: This procedure applies only if you have installed LiveCycle Rights Management ES.
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Sign In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New.
5. On the next screen, set the following properties:
●
In the Name box, type RM_DS.
●
In the JNDI Name box, type EDC_DS.
●
In the Database Type list, select MS SQL Server.
●
In the Database Driver box, select Microsoft's MS SQL Server Driver (Type 4) Versions:2005.
6. Click Next and, on the next screen, select Supports Global Transactions and Emulate Two-Phase
Commit.
7. Click Next and, on the next screen, define the following properties that apply to the SQL Server
database you created during your LiveCycle ES install preparations:
Database Name: The name of the database you have created.
Host Name: The name or IP address of the computer on which SQL Server is running.
Port: The database port. The default is 1433.
Database User Name: The name of the user you created on the SQL Server database.
Password and Confirm Password: The password associated with the user.
8. Click Next and, if using Integrated Security, type integratedSecurity=true in the Properties box.
9. Click Test Configuration to verify the configuration settings.
Note: If the test is successful, a “Connection test succeeded” message will appear. Click Next.Otherwise
review the error message that appears and modify the settings as required until the test succeeds.
10. On the next screen, select the server that the data source will connect to (in this case, the managed
server).
11. Click Finish.
➤ To configure the connection pool settings:
1. Under Change Center, click Lock & Edit.
2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click EDC_DS.
3. On the next screen, click the Configuration and the Connection Pool tab, and set the following
properties:
●
In the Initial Capacity box, type 10.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
●
In the Maximum Capacity box, type 30.
●
In the Capacity Increment box, type 5.
●
In the Statement Cache Size box, type 100.
Configuring JMS resources for WebLogic Server
32
4. Click Save and then click Activate Changes.
5. Restart WebLogic managed server.
➤ To configure integrated security on Windows:
To use integrated security to make a trusted connection with SQL Server:
1. Under Change Center, click Lock & Edit.
2. Under Domain Structure, click [base_domain] > Services > JDBC > Data Sources and, in the right
pane, click IDP_DS.
3. On the next screen, click the Configuration tab and the Connection Pool tab, and in the Properties
box, type integratedSecurity=true.
4. Under Domain Structure, click [base_domain] > Services > JDBC > Data Sources and, in the right
pane, click RM_DS.
5. On the next screen, click the Configuration tab and the Connection Pool tab, and in the Properties
box, type integratedSecurity=true.
6. Add the sqljdbc_auth.dll file to the Windows systems path on the computer that is running the
application server. The sqljdbc_auth.dll file is located with the Microsoft SQL JDBC 1.1 driver
installation (the default is <InstallDir>/sqljdbc_1.1/enu/auth/x86).
7. Set SQL Server’s Security from Mixed mode to Windows Authentication only.
Configuring JMS resources for WebLogic Server
You must configure JMS resources for WebLogic Server by performing the following tasks:
●
Create a JMS Server and a persistent JMS store and configure the JDBC store and assign it to a JMS
server.
●
Create JMS destinations.
●
Create JMS connection factories and queues, and then enable XA on the connection factories.
➤ To create a JMS server and persistent JMS store:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Log In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Services > Messaging > JMS Servers and, in the right pane, click New.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Creating JMS destinations
33
5. On the next screen, set the following properties:
●
In the Name box, type IDPJMSServer.
●
Beside the Persistent Store box, click Create a New Store.
6. On the next screen, in the Type list, select JDBC Store.
7. Click Next and, on the next screen, set the following properties:
●
In the Name box, type IDPJDBCStore.
●
In the Target list, select your managed server.
●
In the Data Source list, select IDP_DS
8. Click Finish and, on the next screen, in the Persistent Store list, select IDPJDBCStore.
9. Click Next.
10. On the next screen, assign the JMS Server to your managed server.
11. In the Target list, select your managed server and then click Finish.
Creating JMS destinations
To create a JMS destination (that is, a queue or a topic), you must first create JMS system modules.
You must also create a subdeployment, which is a mechanism by which targetable JMS resources can be
grouped together and targeted to a specific server. Ideally, all JMS resources should be grouped with
connection factories so that the queues and connections are co-located and thereby reduce network
traffic. Also, if the JMS servers are identified as migratable in a cluster, the server can move with all
resources, which are grouped together.
For each JMS resource, you need a subdeployment that can then be assigned to a server. One
subdeployment is adequate for all of the queues.
➤ To create a JMS destination:
1. Start the WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser.
2. Type the user name and password that you created for the WebLogic Server domain, and then click
Log In.
3. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click New.
4. On the next screen, in the Name box, type IDPJMSModule.
5. Click Next and, under Targets on the next screen, select your managed server.
6. Click Next and, on the next screen, select Would you like to add resources to this JMS system
module?.
7. Click Finish and then click Activate Changes.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Creating JMS destinations
34
➤ To create the JMS queues:
1. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click
IDPJMSModule.
2. Click New and, on the next screen, select Queue.
3. Click Next and, on the next screen, set the following properties:
●
In the Name box and the JNDI Name box, type adobe_PECommandQueue.
●
In the Template list, select None (default).
4. Click Next and, in the Subdepoyments list on the next screen, select IDP_JMS_SubDeployment.
If this selection does not exist, click Create a New Subdeployment and, in the Subdeployment Name
box, type IDP_JMS_SubDeployment and click OK.
Note: You only need to create a subdeployment once. For each additional queue, select the same
subdeployment rather than create a new one. This subdeployment will also be used for topics.
5. In the Targets list, select IDPJMSServer and then click Finish.
6. Repeat steps 2 to 5 for each of the following queues, replacing the queue name and JNDI name in step
3.
JMS queue name
JNDI name
adobe_PEDCommandQueue
adobe_PEDCommandQueue
adobe_JobManagerQueue
adobe_JobManagerQueue
➤ To add failover queue destinations:
1. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click
IDPJMSModule.
2. On the next screen, click adobe_PECommandQueue.
3. On the next screen, click the Configuration tab and the Delivery Failure tab, and set the following
properties:
●
In the Redelivery Limit box, type 5.
●
In the Expiration Policy list, select Redirect.
●
In the Error Destination list, select adobe_PEDCommandQueue.
4. Click Save.
➤ To create the JMS topics:
1. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click
IDPJMSModule.
2. Click New and, on the next screen, select Topic.
Adobe LiveCycle ES 8.0
Manually Configuring WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Next step
35
3. Click Next and, on the next screen, set the following properties:
●
In the Name box, type adobe_TaskEventTopic.
●
In the JNDI Name box, type adobe_TaskEventTopic.
4. Click Next and, in the Subdeployments list on the next screen, select IDP_JMS_SubDeployment.
5. In the Targets list, select IDPJMSServer and then click Finish.
➤ To create the JMS connection factories:
1. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click
IDPJMSModule.
2. Click New and, on the next screen, select Connection Factory.
3. Click Next and, on the next screen, set the following properties:
●
In the Name box, type IDPQueueConnectionFactory.
●
In the JNDI Name box, type IDPQueueConnectionFactory.
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. In the Targets list, select IDPJMSServer and then click Finish.
7. Repeat steps 2 to 6 for each of the following connection factories, replacing the name and JNDI name,
as shown in the table, in step l.
Topic connection factory
JNDI name
IDPTopicConnectionFactory
IDPTopicConnectionFactory
JobManagerQueueConnectionFactory
JobManagerQueueConnectionFactory
➤ To enable XA on the JMS connection factories:
1. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click
IDPJMSModule.
2. On the next screen, click IDPQueueConnectionFactory.
3. On the next screen, click the Configuration tab and the Transactions tab.
4. Select XA Connection Factory Enabled and click Save.
5. Repeat steps 1 to 4 for the IDPTopicConnectionFactory and the JobManagerQueueConnectionFactory.
6. Under Change Center, click Activate Changes.
Next step
You must now deploy the LiveCycle ES EAR files to the application server. (See “Manually Deploying to
WebLogic Server” on page 36.)
5
Manually Deploying to WebLogic Server
This chapter describes how to deploy LiveCycle ES solution components to WebLogic Server:
●
“About deploying LiveCycle ES solution components” on page 36
●
“Deploying to WebLogic Server” on page 37
About deploying LiveCycle ES solution components
Before you deploy LiveCycle ES, ensure that you have performed these tasks:
●
Installed the required software and files, and know the location of the directories you will be working
with. If you have not completed this task, see Preparing to Install LiveCycle ES, at
http://www.adobe.com/go/learn_lc_prepareInstall.
●
Run LiveCycle Configuration Manager to configure and assemble LiveCycle ES solution components
according to your system and application server requirements. If you need to add a solution
component to your deployment, you can run LiveCycle Configuration Manager to make the changes
and then redeploy the updated EAR file.
If you are deploying LiveCycle ES for the first time, you must initialize LiveCycle ES by using
LiveCycle Configuration Manager after you deploy the product.
If you are using an external web server, see your web server documentation for information about the
configuration that is required to allow access to the application server.
WebLogic Server directory name
This chapter refers to the WebLogic Server home directory as [appserver root]. The home directory is the
same as the one specified for the WL_INSTALL_ROOT environment variable. Similarly, [LiveCycleES root]
refers to the location where LiveCycle ES components are installed. (See “Conventions used in this
document” on page 7.)
Summary of deployable components
During the deployment process, you must deploy the following EAR files:
●
adobe-livecycle-native-weblogic-[OS].ear
●
adobe-livecycle-weblogic.ear
●
adobe-workspace-client.ear
After LiveCycle ES is configured with LiveCycle Configuration Manager (required), these files are located in
the [LiveCycleES root]/configurationManager/export directory.
36
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Manually Deploying to WebLogic Server
Deploying to WebLogic Server
37
Deploying to WebLogic Server
You deploy LiveCycle ES components to WebLogic Server by deploying the component EAR files to the
application server using WebLogic Server Administrative Console.
Before deploying to WebLogic Server, you must start the application server on your computer. After
deploying the required components, you must stop and restart the application server before starting any
services.
➤ To deploy the EAR files:
1. To access the WebLogic Administration Console, type http://localhost:7001/console in the
URL line of a web browser.
2. Type the user name and password that was used when creating to WebLogic Server configuration and
click Log In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, click Deployments and then, in the right pane, click Install.
5. On the Install Application Assistant pane, click a drive and navigate to the deployment EAR files to
install.
6. Select the EAR file and click Next.
7. Select Install this deployment as an application and click Next.
8. Select a deployment target from the list provided (in this case, choose the managed server name).
9. Click Next and accept the default settings, and then click Finish.
10. Under Change Center, click Activate Changes.
11. In the right pane, click the application you just installed.
12. Click Start and select Servicing all requests from the menu.
13. In the right pane, click Yes.
14. Under Change Center, click Activate Changes.
15. Repeat steps 5 - 14 for each of the EAR files listed in “Summary of deployable components” on page 36.
16. When the deployment is complete, restart WebLogic. (See “Restarting WebLogic Server” on page 37.)
Restarting WebLogic Server
After you make all your configuration changes, you need to restart WebLogic for the changes to take
affect. The WebLogic Managed Server and the WebLogic Administration Server need to be restarted. The
Node Manager does not need to be restarted.
➤ To stop WebLogic Managed Server:
1. From the WebLogic Server Administration Console, under Domain Structure, click the domain name.
Adobe LiveCycle ES
Manually Deploying to WebLogic Server
Installing and Deploying LiveCycle ES for WebLogic
Restarting WebLogic Server
38
2. Click the Control tab.
3. Select the check box beside the server you want to stop, click Shutdown, and select one of the
following options:
When work completes: Initiates a graceful shutdown of the selected server, causing the Managed
Server to notify its subsystems to complete all in-work requests. A graceful shutdown gives the
WebLogic Server subsystems time to complete certain application processing currently in progress.
Force Shutdown Now: Initiates a forced shutdown, causing the Managed Server to instruct
subsystems to immediately drop in-work requests.
4. At the WebLogic Server Administration Console prompt, click Yes to confirm the command.
You can verify that the Managed Server has been shut down by viewing the table at the bottom of the
Control tab. The table displays a list of all of the servers and indicates their current state.
➤ To stop WebLogic Administration Server:
1. From a command prompt, navigate to BEA_HOME\user_projects\domains\[appserverdomain]\bin.
2. Type the following command:
●
(Windows) stopWebLogic.cmd
●
(Linux, UNIX) ./stopWebLogic.sh
3. Enter the WebLogic user name and password.
➤ To restart WebLogic Administration Server:
1. From a command prompt, navigate to BEA_HOME/user_projects/domains/[appserverdomain].
2. Type the following command:
●
(Windows) startWebLogic.cmd
●
(Linux, UNIX) ./startWebLogic.sh
3. Enter the WebLogic user name and password.
➤ To restart WebLogic Managed Server (if it did not start automatically):
1. When the WebLogic Administration Server has started, log in to the WebLogic Server Administration
Console.
2. Click Lock & Edit.
3. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed
server.
4. On the next screen, click the Control tab.
5. Select the check box beside the managed server you want to start, and then click Start.
6. Click Yes.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Manually Deploying to WebLogic Server
Next steps
39
Next steps
You must run LiveCycle Configuration Manager to initialize the database, and deploy the components and
LiveCycle ES archive files (LCAs). You can also choose to validate the component and LCA deployment. (See
“Running LiveCycle Configuration Manager to configure and deploy LiveCycle ES” on page 18.)
6
Post-Deployment Activities
This chapter describes how to verify the deployment by accessing LiveCycle Administration Console and
checking the application server log files. It also describes how to get started using LiveCycle ES solution
components and services after they have been installed, configured, and deployed to your application
server:
●
“Configuring Acrobat 8.1 for PDF Generator ES” on page 40
●
“Final setup for LiveCycle Rights Management ES” on page 41
●
“Verifying the deployment and accessing LiveCycle Administration Console” on page 41
●
“Accessing solution component web applications” on page 42
●
“Accessing User Management” on page 43
●
“Configuring LiveCycle ES to access LDAP” on page 44
●
“Setting PDF Generator ES Watched Folder performance parameters” on page 44
●
“Configuring FIPS mode” on page 45
●
“Configuring HTML digital signature” on page 46
●
“Configuring the Connector for EMC Documentum service” on page 46
●
“Configuring the Connector for IBM FileNet service” on page 49
●
“Uninstalling LiveCycle ES” on page 52
After you have configured the settings in this chapter, for additional information about configuring your
LiveCycle ES environment for development and production, see Administering LiveCycle ES at
help.adobe.com/en_US/livecycle/es/admin_guide.pdf.
Configuring Acrobat 8.1 for PDF Generator ES
Note: This functionality is only supported on the Windows platform.
If you did not choose to install Acrobat 8.1 using the LiveCycle ES installer, the following procedure needs
to be completed to set up Acrobat 8.1 for use with PDF Generator ES.
➤ To configure Acrobat 8.1 for use with PDF Generator ES:
1. If a previous version (8.0 or earlier) of Acrobat is installed, uninstall it using Add or Remove Programs in
the Windows Control Panel.
2. Navigate to one of the following folders on the LiveCycle ES installation media:
●
additional\acrobat\efg\
●
additional\acrobat\jpn\
3. Install Acrobat 8.1 by running the AutoPlay.exe file.
4. Navigate to the additional\scripts folder on the LiveCycle ES installation media.
5. Run the following batch file:
40
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Final setup for LiveCycle Rights Management ES
41
Acrobat_for_PDFG_Configuration.bat [LiveCycleES root]
➤ To validate the Acrobat 8.1 installation:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat.
2. If the PDF file opens successfully, Acrobat 8.1 is installed correctly. If the PDF fails to open correctly,
uninstall Acrobat and reinstall it.
Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after Acrobat installation is
complete, and disable the automatic updates for Acrobat.
Set the environment variable, Acrobat_PATH to point to Acrobat.exe (for example, C:\Program
Files\Adobe\Acrobat 8.0\Acrobat\Acrobat.exe.
Final setup for LiveCycle Rights Management ES
LiveCycle Rights Management ES requires the application server to be configured to use SSL. For the
configuration instructions, see Administering LiveCycle ES at
help.adobe.com/en_US/livecycle/es/admin_guide.pdf.
Verifying the deployment and accessing LiveCycle Administration
Console
You can verify the deployment by logging in to LiveCycle Administration Console. If you cannot log in,
LiveCycle ES is running on the application server and the default user has been created in the database.
You can review the application server log files to ensure that components were deployed correctly or to
determine the cause of any deployment issues you may encounter.
Accessing LiveCycle Administration Console
LiveCycle Administration Console is the web-based portal for accessing a variety of configuration pages
that let you set run-time properties that control the way LiveCycle ES operates. When you log in to
LiveCycle Administration Console, you can access User Management, Watched Folder and Email client
configuration, and administrative configuration options for other services. LiveCycle Administration
Console also provides access to Archive Administration, which administrators use for managing archives
and deploying services to a production environment.
The default user name and password for logging in to LiveCycle Administration Console is administrator
and password. After you log in the first time, access User Management and change the password.
Before you access LiveCycle Administration Console, LiveCycle ES must be deployed and running on your
application server.
For information about using LiveCycle Administration Console, see Archive Administration Help (available
from the Help menu of the LiveCycle Administration Console window).
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Viewing the log files
42
➤ To access LiveCycle Administration Console:
1. Type the following URL in a web browser:
http://[host name]:[port]/adminui
The default port number for WebLogic Server is 7001. (When you created a new managed server, you
may have set a different port.)
2. In the User Name field, type administrator and, in the Password field, type password.
3. After logging in, you can click Services to access the service administration pages or click Settings to
access the pages on which you can administer settings for different solution components.
Viewing the log files
Events, such as run-time or startup errors, are recorded to the application server log files. If you have
problems deploying to the application server, you can use the log files to help you find the problem. You
can open the log files using any text editor.
Accessing solution component web applications
After LiveCycle ES is deployed, you can access the web applications associated with the following solution
components:
●
LiveCycle Reader Extensions ES
●
LiveCycle Workspace ES
●
LiveCycle Rights Management ES
After accessing the web applications using the default administrator permissions to ensure that they are
accessible, you can create additional users and roles so that others can log in and use the applications. For
information, see User Management Help at www.adobe.com/go/learn_lc_adminUM.
➤ To access the Reader Extensions ES web application:
Note: You must apply a Reader Extension credential and apply the user roles for a new user. For more
information, see the SSL Configuration chapter in Administrating LiveCycle ES.
1. Open a web browser and enter this URL:
http://localhost:[port]/ReaderExtensions
(local deployment using the default port), where [port] is the port assigned to the Managed
WebLogic Server.
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 role “Reader Extensions Web Application”.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Accessing Rights Management ES:
43
➤ To access Workspace ES:
1. Open a web browser and enter this URL:
http://localhost:[port]/workspace
(local deployment using the default port), where [port] is the port assigned to the Managed
WebLogic Server.
2. Log in using the default user name and password:
User name: administrator
Password: password
Accessing Rights Management ES:
You must create a user with the role “RM end user console” in User Management and log in to the
Rights Management ES administrator or end user applications using the login information associated with
that user.
➤ To access the Rights Management ES end-user web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/edc/Login.do
where [port] is the port assigned to the Managed WebLogic Server.
Note: The administrator user cannot access the Rights Management ES end user web application. You can
create new users using the LiveCycle ES Administrative UI.
➤ To access the Rights Management ES administration web application:
1. Open a web browser and enter this URL:
http://[server]:[port]/adminui
where [port] is the port assigned to the Managed WebLogic Server.
Accessing User Management
User Management allows administrators to maintain a database of all users and groups, synchronized with
one or more third-party user directories. User Management provides authentication, authorization, and
user management for LiveCycle ES solution components, including Reader Extensions ES, Workspace ES,
Rights Management ES, LiveCycle Process Management ES, and LiveCycle Forms ES.
➤ To access User Management:
1. Log in to LiveCycle Administration Console.
2. From the home page of LiveCycle Administration Console, click Settings.
3. On the Settings page, click User Management.
Note: For information about configuring users with User Management, click User Management Help in
the upper-right corner of the User Management page.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Configuring LiveCycle ES to access LDAP
44
Configuring LiveCycle ES to access LDAP
Use the following procedure as a guideline when configuring User Management to support
authentication using LDAP.
➤ To configure User Management with LDAP (Enterprise Domain):
1. Type http://[host name]:[port]/adminui in the URL line of a web browser and log in. (See
“Accessing LiveCycle Administration Console” on page 41.)
2. Click Settings > User Management > Domain Management and click New Enterprise Domain.
3. In the ID box, type a unique identifier for the domain.
4. In the Name box, type a descriptive name for the domain.
5. Click Add Authentication and, in the Authentication Provider list, select LDAP.
6. Click OK.
7. Click Add Directory, and under Profile Name, select a name for your LDAP profile.
8. Click Next.
9. Specify values in the Server, Port, SSL, and Binding boxes as required. For details on the settin.gs, see
Directory settings in User Management Help at www.adobe.com/go/learn_lc_adminUM.
10. Under Populate Page With, select a directory settings option, such as Default Sun ONE values.
11. Click Next and configure the User Settings as required. For details about the settings, see Directory
settings in User Management Help.
12. Click Next configure the Group Settings as required. For details about the settings, see Directory
settings in User Management Help.
13. (Optional) Test your configuration:
●
Click Test.
●
In the Test Directory pane, in the Find box, enter an object name and, in the using box, select the
object’s type, such as Login ID.
●
Click Test. If successful, your object’s details will be displayed, and then click Back.
14. Click Finish to exit the New Directory page, and click OK again to exit.
Setting PDF Generator ES Watched Folder performance
parameters
To avoid java.io.IOException error messages indicating that not enough disk space is available to perform
PDF conversions using a watched folder, you can modify the settings for PDF Generator ES in LiveCycle
Administration Console.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Configuring FIPS mode
45
➤ To set performance parameters for PDF Generator ES:
1. Log in to LiveCycle Administration Console and click Services > Archive Administration > Service
Management > PDFGConfigService.
2. Set the following values:
●
PDFG Cleanup Scan Seconds: 1800
●
Job Expiration Seconds: 6000
3. Increase Server conversion timeout from the default of 270 to a higher value, such as 450.
4. Click Save.
5. Restart the server.
Configuring FIPS mode
LiveCycle ES provides a FIPS mode to restrict data protection to Federal Information Processing Standard
(FIPS) 140-2 approved algorithms using the RSA BSAFE Crypto-C 2.1 encryption module.
If you did not enable this option using LiveCycle Configuration Manager during the LiveCycle ES
configuration or if you enabled it but want to turn it off, you can change this setting through LiveCycle
Administration Console.
To modify FIPS mode, you must restart the server.
FIPS mode does not support encryption algorithms used in Acrobat versions earlier than 7.0. If FIPS mode
is enabled and you use the Encryption service to encrypt the PDF using a password with a compatibility
level set to Acrobat 5, the encryption attempt will fail with an error.
In general, when FIPS is enabled, the Assembler service will not apply password encryption to any
document. If this is attempted, a FIPSModeException is thrown indicating that "Password encryption
is not permitted in FIPS mode." Additionally, the Document Description XML (DDX)
PDFsFromBookmarks element is not supported in FIPS mode when the base document is
password-encrypted.
➤ To turn FIPS mode on or off:
1. Log in to LiveCycle Administration Console.
2. Browse to Settings > Core System > Configurations > Core Configurations.
3. Select Enable FIPS to enable FIPS mode or deselect it to disable it.
4. Click OK.
5. Restart the application server.
Note: LiveCycle ES software does not validate code to ensure FIPS compatibility. It provides a FIPS
operation mode so that FIPS-approved algorithms are used for cryptographic services from the
FIPS-approved libraries (RSA).
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Configuring HTML digital signature
46
Configuring HTML digital signature
To use the HTML digital signature feature of LiveCycle Forms ES, you must complete the following
procedure.
➤ To enable HTML digital signature:
1. Manually deploy the [LivecycleES root]/deploy/adobe-forms-ds.ear file to your application server.
2. Log in to LiveCycle ES Administrator Console.
3. Select Service > Livecycle Forms ES.
4. Select HTML Digital Signature Enabled.
Configuring the Connector for EMC Documentum service
If you installed the Connector for EMC Documentum service as part of your LiveCycle ES solution,
complete the following procedure to configure the service to connect to the Documentum repository.
➤ To configure Connector for EMC Documentum:
1. Locate the adobe-component-ext.properties file in the
[BEA HOME]/user_projects/domains/Adobe_LiveCycle folder. If the file does not exist, you must create
it. Add a new system property that provides the location of the Documentum Content Server config
folder and the following Documentum Foundation Classes JAR files:
●
dfc.jar
●
dfcbase.jar
The new system property should take this form:
[component id]_[component version].ext=[JAR files and/or folders]
For example, using default Content Server and Documentum Foundation Classes installations, you add
the following system property on a new line, with no line breaks, and end the line with a carriage
return, to the file:
com.adobe.livecycle.ConnectorforEMCDocumentum_8.0.3174.1.156395.1.ext
=C:/Documentum/Config,C:/Program Files/Documentum/Shared/dfc.jar,
C:/Program Files/Documentum/Shared/dfcbase.jar
You can determine the version of the component by logging in to the LiveCycle Administration
Console and navigating to Services > Archive Administration > Service Management, and then
searching for the component. The version number is listed in the Component Version column.
2. If WebLogic Server is not currently running, start the server. Otherwise, stop and then restart the server.
3. Open a web browser and enter this URL:
http://localhost:7001/adminui (local deployment using the default port)
4. Log in using the default user name and password:
User name: administrator
Password: password
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Configuring the Connector for EMC Documentum service
47
5. Navigate to Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings.
6. Type all of the required Documentum repository information. To use Documentum as your repository
provider, in the Repository Service Provider Information area, select EMC Documentum Repository
Provider, and then click Save. For more information about the Documentum repository information,
see Documentum Administration Help at www.adobe.com/go/learn_lc_adminDocumentum.
7. (Optional) Navigate to Repository Credentials Settings, click Add, specify the Docbase information,
and then click Save. For more information about the Documentum repository information, see
Documentum Administration Help at www.adobe.com/go/learn_lc_adminDocumentum.
8. Navigate to Services > Archive Administration > Service Management, select the following services,
and then click Start:
●
EMCDocumentumAuthProviderService
●
EMCDocumentumContentRepositoryConnector
●
EMCDocumentumRepositoryProvider
If any of the services do not start correctly, check the settings entered in step 6.
9. Do one of the following tasks:
●
To use the Documentum Authorization service (EMCDocumentumAuthProviderService) to display
content from a Documentum repository in the Resources view of Workbench ES, continue with this
procedure. Using the Documentum Authorization service overrides the default LiveCycle ES
authorization and must be configured to log in to Workbench ES using Documentum credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES using the LiveCycle ES super
administrator credentials (by default, Administrator and password). You have now completed the
required steps for this procedure. The credentials provided in step 6 are used for accessing the
default repository in this case and use the default LiveCycle ES authorization service.
10. Restart WebLogic Server.
11. Log in to the LiveCycle Administration Console, navigate to Settings > User Management > Domain
Management, and click New Enterprise Domain.
12. Type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a
descriptive name for the domain.
13. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom, and select EMCDocumentumAuthProvider.
●
Click OK.
14. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP.
●
Click OK.
15. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
●
Creating the XDP MIME format in your Documentum repository
48
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
For details about the settings, see User Management Help at
www.adobe.com/go/learn_lc_adminUM.
●
Configure the user settings, click Next, configure group settings, as required, and then click Next.
For details about the settings, see User Management Help at
www.adobe.com/go/learn_lc_adminUM.
16. Click OK to exit the Add Directory page, and click OK again.
17. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
To verify the status of the synchronization, click Refresh and view the status in the Current Sync State
column.
18. Click Settings > User Management > Users and Groups.
19. Search for users that were synchronized from LDAP. Select one or more users, click Assign Role, select
one or more LiveCycle ES roles, and then click OK. Click OK a second time to confirm the role
assignment. Repeat this step for all users you assign roles to. For more information about assigning
LiveCycle ES roles, see User Management Help at www.adobe.com/go/learn_lc_adminUM.
20. Start Workbench ES and log in using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The Documentum repository should now be visible in the Resources view within Workbench ES. If you
do not log in using the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 6.
After you configure your Connector for EMC Documentum service, you should see Administering
LiveCycle ES at www.adobe.com/go/learn_lc_administration for information on correctly configuring
Workbench ES functions properly with your Documentum repository.
Creating the XDP MIME format in your Documentum repository
Before users can store and retrieve XDP files from a Documentum repository, you must do one of these
tasks:
●
Create a corresponding XDP format in each repository where users will access XDP files.
●
Configure the Connector for EMC Documentum service to use a Documentum Administrator account
when accessing the Documentum repository. In this case, the XDP format is created by the
Connector for EMC Documentum service whenever it is required.
➤ To create the XDP format on Documentum Content Server using Documentum Administrator:
1. Log in to Documentum Administrator.
2. Click Formats.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Configuring the Connector for IBM FileNet service
49
3. Select File > New > Format.
4. Type the following information into the corresponding fields:
Name: xdp
Default File Extension: xdp
Mime Type: application/xdp
5. Repeat steps 1 - 4 for all other Documentum repositories where users will store XDP files.
➤ To configure the Connector for EMC Documentum service to use a Documentum Administrator:
1. Open a web browser and enter this URL:
http://localhost:7001/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings.
4. In the Documentum Principal Credentials Information area, update the following information and then
click Save:
User Name: [Documentum Administrator user name]
Password: [Documentum Administrator password]
5. Click Repository Credentials Settings.
6. Select a repository from the list or, if none exist, click Add.
7. Type the following information:
Repository Name: [Repository Name]
Repository Credentials User Name: [Documentum Administrator user name]
Repository Credentials Password: [Documentum Administrator password]
8. Click Save.
9. Repeat steps 7 - 9 for all repositories where users will store XDP files.
Configuring the Connector for IBM FileNet service
If you installed the Connector for IBM FileNet service as part of your LiveCycle ES solution, complete the
following procedure to configure the service to connect to the FileNet object store.
➤ To configure Connector for IBM FileNet:
1. Locate the adobe-component-ext.properties file in the
[BEA HOME]/user_projects/domains/Adobe_LiveCycle folder. If the file does not exist, you must create
it. Add a new system property that provides the location of the following Application Engine JAR files:
●
activation.jar
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
●
javaapi.jar
●
log4j-1.2.8.jar
●
mailapi.jar
●
p8cjares.jar
●
soap.jar
●
xercesimpl.jar
●
xml-apis.jar
Configuring the Connector for IBM FileNet service
50
The new system property should take this form:
[component id]_[component version].ext=[JAR files and/or folders]
For example, using a default Application Engine installation, add the following system property on a
new line, with no line breaks, and end the line with a carriage return, to the file:
com.adobe.livecycle.ConnectorforIBMFileNet_8.0.3174.1.156395.1.ext=
C:/Program Files/FileNet/lib2/activation.jar,
C:/Program Files/FileNet/lib2/javaapi.jar,
C:/Program Files/FileNet/lib2/log4j-1.2.8.jar,
C:/Program Files/FileNet/lib2/mailapi.jar,
C:/Program Files/FileNet/lib2/p8cjares.jar,
C:/Program Files/FileNet/lib2/soap.jar,
C:/Program Files/FileNet/lib2/xercesImpl.jar,
C:/Program Files/FileNet/lib2/xml-apis.jar
You can determine the version of the component by logging in to LiveCycle Administration Console
and navigating to Services > Archive Administration > Service Management, and then searching
for the component. The version number is listed in the Component Version column.
2. If WebLogic Server is not currently running, start the server. Otherwise, stop and then restart the server.
3. Open a web browser and enter this URL:
http://localhost:7001/adminui (local deployment using the default port)
4. Log in using the default user name and password:
User name: administrator
Password: password
5. Navigate to Services > LiveCycle ES Connector for IBM FileNet > Configuration Settings.
6. Type all of the required FileNet repository information and, in the Repository Service Provider
Information area, select IBM FileNet Repository Provider, and then click Save. For more information
about the FileNet repository information, see FileNet Administration Help at
http://www.adobe.com/go/learn_lc_adminFileNet.
Note: The credentials you provide during this step are validated when the IBM FileNet repository
services are started in the next step. If the credentials are invalid, an error is thrown and the
services will fail to start.
7. Navigate to Services > Archive Administration > Service Management, click the following services,
and then click Start:
●
IBMFileNetAuthProviderService
●
IBMFileNetContentRepositoryConnector
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
●
Configuring the Connector for IBM FileNet service
51
IBMFileNetRepositoryProvider
If any of the services do not start correctly, check the settings entered in step 6.
8. Do one of the following tasks:
●
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a
FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the
FileNet Authorization service overrides the default LiveCycle ES authorization and must be
configured to log in to Workbench ES using FileNet credentials.
●
To use the LiveCycle ES repository, log in to Workbench ES using the LiveCycle ES super
administrator credentials (by default, Administrator and password). You have now completed
the required steps for this procedure. The credentials provided in step 6 use the default LiveCycle ES
authorization service for accessing the default repository in this case.
9. Restart WebLogic Server.
10. Log in to the LiveCycle Administration Console, navigate to Settings > User Management > Domain
Management, and click New Enterprise Domain.
11. Type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a
descriptive name for the domain.
12. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom, and select IBMFileNetAuthProviderService.
●
Click OK.
13. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP.
●
Click OK.
14. Add an LDAP directory:
●
Click Add Directory.
●
In the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
For details about the settings, see User Management Help at
http://www.adobe.com/go/learn_lc_adminUM.
●
Configure the user settings, click Next, configure group settings, as required, and then click Next.
For details about the settings, see User Management Help at
http://www.adobe.com/go/learn_lc_adminUM.
15. Click OK to exit the Add Directory page, and click OK again.
Adobe LiveCycle ES
Post-Deployment Activities
Installing and Deploying LiveCycle ES for WebLogic
Uninstalling LiveCycle ES
52
16. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
To verify the status of the synchronization, click Refresh and view the status in the Current Sync State
column.
17. Click Settings > User Management > Users and Groups.
18. Search for users that were synchronized from LDAP. Select one or more users, click Assign Role, select
one or more LiveCycle ES roles, and then click OK. Click OK a second time to confirm the role
assignment. Repeat this step for all users you want to assign roles to. For more information about
assigning LiveCycle ES roles, see User Management Help at
http://www.adobe.com/go/learn_lc_adminUM.
19. Start Workbench ES and log in using the following credentials:
Username: [username]@[repository_name]
Password: [password]
The FileNet object store should now be visible in the Resources view within Workbench ES. If you do
not log in using the [email protected] name, Workbench ES attempts to log in to the default
repository specified in step 6.
After you configure your Connector for IBM FileNet service, you should see Administering LiveCycle ES at
www.adobe.com/go/learn_lc_administration for information on correctly configuring Workbench ES
functions properly with your FileNet repository.
Uninstalling LiveCycle ES
The uninstall program located in the [LivecycleES root] directory does not remove any files that you
deployed to your application server.
Caution: By running the uninstall program, all of the contents within the product installation directory are
subject to removal without further warning. Before proceeding, back up any data you do not
want to lose.
➤ To remove the files from your computer:
1. Invoke the uninstall program:
●
(Windows) Perform these tasks:
●
●
●
Use Add or Remove Programs in the Windows Control Panel.
●
Remove Adobe LiveCycle ES.
●
Remove Adobe Acrobat 8.1 Professional (if installed with PDF Generator ES).
Alternatively, you can complete these manual steps:
●
cd [LivecycleES root]/_uninst/server
●
Double-click the livecycle8_uninstall.exe file.
(Linux and UNIX) From a terminal, type ./livecycle8_uninstall.bin (you may need to make
this binary an executable file).
2. Follow the on-screen instructions in the uninstall program, and then click Finish.
7
Manually Configuring BAM Server for LiveCycle ES
This section describes the tasks that must be performed to manually install and configure
LiveCycle Business Activity Monitoring ES for use with LiveCycle ES:
●
“Configuring WebLogic Server for BAM Server” on page 53
●
“Creating a managed server for Business Activity Monitoring ES” on page 54
●
“Creating and configuring the BAM Server metadata database” on page 55
●
“Configuring Process Management ES for BAM Server” on page 57
●
“Deploying BAM Server to the WebLogic Server” on page 58
●
“Configuring LDAP settings for BAM Server” on page 61
●
“Using the BAM Dashboard” on page 65
●
“Uninstalling Business Activity Monitoring ES” on page 66
These instructions use the following naming conventions for common file paths.
Name
Description
Default value
[appserver root]
The home directory of the
application server for
Business Activity Monitoring ES.
WebLogic on Windows: C:\bea
[LiveCycleES root]
WebLogic on Linux: /opt/bea
The location where the LiveCycle ES Windows: C:\Adobe\LiveCycle8
services are installed
Linux and UNIX: /opt/adobe/livecycle8
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux and UNIX). Any platform-specific information is indicated as required.
Configuring WebLogic Server for BAM Server
If you are installing LiveCycle Process Management ES and manually deploying to the WebLogic Server,
you must manually configure a separate WebLogic Server so that BAM Server runs correctly. You must
perform the following tasks:
●
If you have not already done so, create a separate WebLogic Server instance in the same domain for
hosting BAM Server.
●
If you have not already done so, create a database for Business Activity Monitoring ES.
●
Configure the connection to the BAM Server metadata database.
●
Configure the connection to the LiveCycle ES database.
●
Modify the WebLogic Server JVM.
53
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Adding required JAR files to the lib directory
54
Adding required JAR files to the lib directory
Copy the following files to your [appserver root]/User_projects/<user_domain>/lib directory:
●
<weblogic home>/common/lib/log4j.jar
●
<weblogic home>/server/lib/consoleapp/APP-INF/lib/commons_logging.jar
Creating a managed server for Business Activity Monitoring ES
You will need to create a managed server for BAM Server. Each managed server must then be assigned to a
machine.
➤ To create a managed server in an existing domain:
1. If you have not already done so, under Change Center in the Administration Console, click Lock & Edit.
2. Under Domain Structure, click Environment > Servers.
3. In the Servers table, click New.
4. Under Create a New Server, specify the values for the properties:
●
In the Server Name box, type the name of the server.
●
In the Server Listen Port box, type the port number from which you want to access the server
instance (for example, type 8001).
●
Select No, this is a stand-alone server.
5. Click Next, review the configuration options you have chosen and then click Finish.
➤ To create and configure a new machine:
1. In the Administration Console, under Domain Structure, click Environment > Machines and, in the
right pane, click New.
2. In the Name box, type a name for the new machine. This name is used to identify the machine within
the WebLogic Server domain. This name does not have to correspond to the machine network name.
3. In the Machine OS list, select your operating system and click OK. Verify that the new machine is
displayed in the Machines table.
4. Under Domain Structure, click Environment > Servers, and in the right pane, click the managed server
that you created for BAM Server.
5. Click the Configuration tab and click the General tab.
6. In the Machine list, select the machine you just created and then click Save.
7. Click Activate Changes.
8. Shut down and restart the servers by starting Node Manager, Administration Server, and Managed
Server.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring the WebLogic Server JVM
55
Configuring the WebLogic Server JVM
You must configure the WebLogic Server Java™ Virtual Machine (JVM) so that it can support BAM Server.
➤ To configure the WebLogic Server JVM:
1. Click Lock and Edit.
2. Under Domain Structure, click Domain Name > Environment > Servers and, in the right pane, click
the server created for BAM Server.
3. Click the Server Start tab and, in the Java Home box, type the location of your JDK version, as shown
in these examples:
●
(Windows) C:\bea\jdk1.5.0_04
●
(Linux) /opt/bea/jdk150_04
4. In the Arguments box, type the following:
-Dfile.encoding=UTF8 -XX:MaxPermSize=256M -Xms256m -Xmx1024m
5. Click Save and then click Activate Changes.
6. Restart the BAM Server.
Creating and configuring the BAM Server metadata database
You must create a Business Activity Monitoring ES metadata database to store the definitions of the
process metrics that BAM Server monitors, as well as the details of any alerts and object run-time data that
need to be persisted to disk.
Because Business Activity Monitoring ES metadata can grow quite large, you must allocate at least 50 MB
for the BAM Server metadata database. For production deployments, allocate at least 200 MB.
BAM Server can require specific settings for some aspects of the Business Activity Monitoring ES metadata
database configuration. The settings depend on the type of application server that is hosting BAM Server
and the type of database server used to store the Business Activity Monitoring ES metadata.
User accounts
You must also create a user account that BAM Server can use to connect to the
Business Activity Monitoring ES metadata database. The user account must have create, modify, and
update privileges on the database.
For Oracle, you must also create a user account that BAM Server can use to connect to the metadata
database. The user account must have create, modify, and update privileges on the database. Assign the
roles CONNECT and RESOURCE, and the ACCESS_ANY_WORKSPACE, CREATE_ANY_VIEW and
UNLIMITED_TABLESPACE system privileges. The database user account must be associated with a
tablespace that you create specifically for Business Activity Monitoring ES metadata.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring your database environment
Configuring your database environment
If you are using DB2 as the Business Activity Monitoring ES metadata database, you must create an
environment variable that contains the name of the associated DB2 instance. You also must include the
path to the DB2 shared libraries in the library path variable.
The following examples show commands for configuring the environment variables. Use the command
that corresponds with your operating system. You may need to modify the command according to the
location where you installed DB2.
Example: Commands to configure environment variables on Windows
The following commands apply to a DB2 instance named DB2, with DB2 library files installed in
C:\SQLLIB\BIN:
set DB2INSTANCE=DB2
set PATH=C:\SQLLIB\BIN;%PATH%
Example: Commands to configure environment variables on Solaris
The following commands apply to a DB2 instance named db2fs, with DB2 library files installed in
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LD_LIBRARY_PATH=/opt/IBM/db2/V8.1/lib:${LD_LIBRARY_PATH}
Example: Commands to configure environment variables on AIX
The following commands apply to a DB2 instance named db2f.
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LIBPATH=/opt/IBM/db2/V8.1/lib:${LIBPATH}
Configuring the connection to the BAM Server metadata database
You must configure a data source on WebLogic Server for the BAM Server metadata database so that
BAM Server can retrieve information about process metrics that it needs to monitor.
➤ To create the connection to the BAM Server metadata database:
1. Start the Node Manager, Administration Server and Managed Server.
2. Type http://[host name]:[port]/console in the URL line of a web browser (for example,
http://localhost:7001/console) to start WebLogic Server Administration Console.
3. Click Lock and Edit.
4. Under Domain Structure, click Services > JDBC > Data sources and, in the right pane, click New.
5. In the Name box and the JNDI Name box, type com.celequest.metadata.metaDatasource
6. In the Database Type list, select the type of database you are using to store BAM Server metadata.
56
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring Process Management ES for BAM Server
57
7. In the Database Driver list, select the appropriate database driver, and then click Next:
●
(MS SQL Server) Microsoft MS SQL Server Driver (Type 4)
●
(Oracle) Oracle’s Driver (Thin) versions 9.x, 10
8. On the next screen, deselect Supports Global Transactions and then click Next.
9. Specify values for the following properties, and then click Next:
Database Name: The name of the database (SQL Server) or database instance (Oracle).
Host Name: The network name or IP address of the database host computer.
Port: The port used by the database host computer.
Database User Name: The name of a user account that can access the database.
Password and Confirm Password: The password that corresponds with the user name you
provided.
10. On the next screen, click Test Configuration to verify the configuration settings.
11. Click Finish.
➤ To configure the connection pool:
1. Under Domain Structure, click Services > JDBC > Data sources and, in the right pane, click the data
source you created.
2. On the next screen, click the Configuration tab and the Connection Pool tab.
3. Click Lock and Edit.
4. In the Maximum Capacity box, type 200.
5. Accept the default values for all of the remaining properties, and then click Save.
6. Click the Targets tab, select the BAM Server, click Save, and then click Activate Changes.
➤ To configure the connection to the LiveCycle ES database:
1. Click Lock and Edit.
2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click IDP_DS.
3. On the next screen, click the Targets tab and then select both the BAM Server and the LC8 server.
4. Click Activate Changes.
Configuring Process Management ES for BAM Server
You can configure Process Management ES to connect to BAM Server using LiveCycle Administration
Console. You must specify the server on which the LiveCycle ES server and BAM Server are running and the
user account information with which to access BAM Server.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Deploying BAM Server to the WebLogic Server
58
➤ To configure Process Management ES for BAM Server:
1. Log in to LiveCycle Administration Console.
2. Click Services > LiveCycle Process Management ES > Server Settings > BAM Configuration
Settings.
3. Type values for the following properties:
BAM Host: The host name or IP address of the server on which BAM Server is running. The default
value is localhost.
BAM Port: The service port of the application server on which BAM Server is running. The default
value is 8080.
LiveCycle Server Host: The host name or IP address of the server on which the LiveCycle ES server
is running. The default value is localhost.
LiveCycle Server SOAP Port: The service port of the application server on which the LiveCycle ES
server is running. The default value is 8080.
User Name: (Optional) The user name of the administrator user account that
Process Management ES uses to access BAM Server. The default user name is system.
Note: If you specify the user name for a different user account, you must ensure that the user has
complete administrative privileges for BAM Server. For information about administering
BAM Server user accounts, see Using BAM Workbench.
Password: (Optional) A valid password for the user name specified above. The default password is
manager.
4. Click Save and restart the LiveCycle ES server.
Deploying BAM Server to the WebLogic Server
You use WebLogic Server Administration Console to deploy the BAM Server EAR file to the
WebLogic Server. The BAM Server EAR file (CAS_Adobe.ear) that you need to deploy is installed in the
[LiveCycle root]/deploy directory.
After you deploy the BAM Server EAR file, modify the configuration of the JDBC connection pool to
increase its maximum capacity.
Note: Ensure that you deploy the EAR file to the WebLogic Server application server that you configured
for BAM Server.
➤ To deploy BAM Server to WebLogic Server:
1. Start the Administration Server and, if applicable, the managed server.
2. Log in to WebLogic Server Administration Console by typing
http://[host name]:[port]/console in the URL line of a web browser (for example, type
http://localhost:7001/console).
3. Click Lock and Edit.
4. Under Domain Structure, click Deployments and, in the right pane, click Install.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Deploying BAM Server to the WebLogic Server
59
5. Click Upload your files, browse to the [LiveCycle root]/deploy directory, select the CAS_Adobe.ear file,
and then click Upload.
6. If more than one valid file path is displayed, select the most appropriate path.
7. In the Choose Targeting style list, select Install this deployment as an application, then click Next.
8. In the Select Deployment target list, select the server that was created for BAM Server in “Creating a
managed server for Business Activity Monitoring ES” on page 54, then click Next.
9. Click Next, then click Finish then Save.
10. Click Activate changes and then start the application.
➤ To configure the BAM Server system settings:
1. Start BAM Workbench by typing http://[host name]:[BAM port]/bam/workbench in the URL
line of a web browser.
2. On the login page, enter the system manager user name and password. These values are the defaults:
Username: system
Password: manager
3. Navigate to Workbench > Administration console > System settings.
4. In the Configure list, select Checkpoint Configuration.
5. Select Enable Checkpoint.
6. In the Recovery Log Directory field, type the path to the BAM logging directory; for example, type the
following directory:
[appserver root]/server/all/log
7. In the Configure list, select Logging.
8. In the Logging Directory field, type the path to the BAM logging directory; for example, type the
following directory:
[appserver root]/server/all/log
9. In the Configure list, select System Control and ensure that Recover State on Restart is selected.
10. In the Configure list, select SMTP Configuration and enter the following parameters:
Host: The URL to the SMTP host.
Address: The IP address for the SMTP host.
User: The account user name.
Password: The account user password.
11. Click OK.
12. Restart the LiveCycle ES server and BAM Server.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Deploying BAM Server to the WebLogic Server
60
➤ To import the LiveCycle ES metadata definitions:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. On the login page, type the system manager user name and password. These values are the defaults:
Username: system
Password: manager
3. Click the Administration Console tab and click Import/Export.
4. Select Import Metadata from a JAR file (upload) and enter the full path to the location of the
Business Activity Monitoring ES metadata template that is appropriate for the type of database that
you are using for the LiveCycle ES database:
●
(DB2) adobeimport_DB2.jar
●
(Oracle) adobeimport_Oracle.jar
●
(SQL Server) adobeimport_SQLServer.jar
These files are installed in the [LiveCycle root]/deploy directory.
5. Click Upload and then click OK to import the file.
➤ (Oracle) To update the JDBC Query:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. On the login page, type the system manager user name and password. These values are the defaults:
Username: system
Password: manager
3. Click the Application Workbench tab and click events to see a list of events.
4. Double-click Adobe event and then click Edit This Event.
5. In the JDBC Query box, type in the following code:
select uuid,major_version,minor_version,"descriptor",state,service_uuid,
component_oid,update_time,create_time from tb_sc_service_configuration
where monitor='1'
6. Click Resubmit Query.
7. Click the Polling tab and, in the Incrementing Field list, select update_time. Notice the Initial Value
(such as 2000-01-01 00:00:00); you may need this info later.
8. Click Save this Event.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring LDAP settings for BAM Server
61
Configuring LDAP settings for BAM Server
In addition to manually creating users and user permissions, Business Activity Monitoring ES lets you
import user information from supported LDAP providers. You can schedule automatic synchronizations or
perform manual synchronizations with the LDAP server to automatically update the existing users and
roles.
When synchronizing with the LDAP server, the user base DN, login identification and password, full name,
description, and email address properties are cached in the BAM Server metadata database.
When BAM Server imports users from the LDAP server, LDAP groups are converted to
Business Activity Monitoring ES roles. Users are assigned roles according to the group they belong to in
LDAP. For more information, see “Limitations of BAM Server LDAP connectivity” on page 61.
Note: BAM Server integrates with any LDAP provider that supports the LDAP version 3 protocol.
Limitations of BAM Server LDAP connectivity
The following limitations apply to the BAM Server connectivity with the LDAP server:
●
You can configure a connection to only one LDAP server.
●
BAM Server creates roles based on groups that are defined on the LDAP server. When BAM Server
encounters a group for which a role is not yet created, it creates the role and assigns it a set of zero
permissions. You can later modify the permissions as required. (See “Configuring LDAP role mapping”
on page 64.)
●
If BAM Server imports a user and the user does not belong to a group to which a
Business Activity Monitoring ES role corresponds, the user is created but remains unassigned to any
roles.
●
You cannot change the role that a user is assigned to if the user is imported from the LDAP server. Role
assignments for imported users can be accomplished by making changes to the LDAP server. However,
you can assign manually-created users to roles that are created based on LDAP groups.
Best practices for BAM Server LDAP connectivity
When setting up the BAM Server connectivity with the LDAP server, it is strongly recommended you
adhere to the following best practices:
●
If the connection to the LDAP server is not secure, you should use SSL.
●
For authentication, Simple Authentication and Security Layer (SASL) is the recommended method and
is well supported by LDAP.
●
For security reasons, the access permissions of the LDAP synchronization user should be limited to
querying the LDAP server. For more information on the synchronization user, see “Configuring
automatic LDAP synchronization” on page 62.
Caution: The password for this user is stored in the BAM Server metadata using reversible symmetric
encryption. Therefore, anyone with access to the metadata can obtain this password.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring automatic LDAP synchronization
62
Configuring automatic LDAP synchronization
You can schedule the automatic synchronization of BAM Server with the LDAP server. Synchronization
ensures that the user accounts and role definitions that BAM Server caches in the BAM Server metadata
database are up to date with the content of the LDAP server.
During synchronization, BAM Server creates new roles based on any new groups in the LDAP server and
removes existing roles based on any groups that have been removed from the LDAP server since the
previous synchronization.
Note: Roles are removed even if users that were created manually are assigned to the roles. For these
users, if the roles are removed due to synchronization, the user accounts still exist but are no longer
assigned to the roles.
➤ To configure automatic LDAP synchronization:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab and then click System Settings.
3. Click the LDAP Synchronization tab.
4. Select LDAP Enabled if it is not already selected.
5. Specify values for the following properties:
Initial Context Factory: The JNDI name through which BAM Server connects to the LDAP server.
The default value is com.sun.jndi.ldap.LdapCtxFactory. You probably do not need to
change this value.
LDAP Server: The DNS name or IP address of the LDAP server.
LDAP Port: The port on which the LDAP server is running. The default port is typically 389.
However, if you select the SSL option, the default port is typically 636. You must confirm with your
LDAP administrator which port to specify.
LDAP SSL: Select this option if the LDAP server is configured to use SSL. Selecting this option may
affect the LDAP Port setting.
LDAP Authentication: The authentication method used by the LDAP server. Select one of the
following options:
●
Simple
●
SASL (Simple Authentication and Security Layer). Select this option for Sun ONE.
●
Compare Encrypted Password
LDAP Principal DN Prefix: For the simple authentication method, the text you specify will be
inserted before the user's login name:
●
For LDAP servers that require DN login, set this to the appropriate property value followed by an
equal sign (for example, cn= or uid=).
●
For Active Directory, leave this value blank.
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:
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring LDAP user mapping
63
,ou=Users,dc=domain,dc=name
●
For Active Directory, which requires a simple login with an email address, set this to an at symbol
(@) followed by the domain name that is set for Active Directory.
LDAP Synchronization User: The user that binds to the server and reads the lists of users and roles.
For security purposes, you must specify a user account that can only read the LDAP directory.
LDAP Synchronization Password: The password associated with the user specified for the LDAP
Synchronization User option.
6. Click Test Connection. The connection and the user mapping and role mapping configuration are
tested. If the connection settings are correct, a message will indicate that the connection was
successful. If you have not yet configured LDAP User Mapping and LDAP Role Mapping, the message
returns an error.
7. To set the LDAP Synchronization Schedule, use the Add Schedule, Edit Schedule, and Remove
Schedule buttons to create the schedule you want.
Note: You should set synchronization for a time when the fewest number of users are likely to be
logged in.
8. Click OK.
Configuring LDAP user mapping
You can configure the user mapping parameters that determine which users are imported and
synchronized from the LDAP server. The parameters you specify depend on the LDAP server provider that
you are using.
➤ To configure the LDAP user mapping parameters:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab, and then click System Settings.
3. Click the LDAP User Mapping tab and specify values for the following parameters:
LDAP User Base DN: The root of the tree that will be searched for users, for example:
●
(Sun ONE) OU=people,DC=your domain,DC=com
●
(Active Directory) CN=Users,DC=yourdomain,DC=com
LDAP User Search Filter: The format that is appropriate for the type of LDAP server you are using.
For example, your LDAP server could have a special group for Business Activity Monitoring ES users.
This filter could then ensure that only users with this group membership are imported.
LDAP User LoginID: The login ID of the indicated provider. This value will become the user’s login
ID in Business Activity Monitoring ES.
LDAP User Full Name: Enter cn if you are using either Sun ONE or Active Directory.
LDAP User Description: Enter description if you are using either Sun ONE or Active Directory.
LDAP User PrimaryEmail: Enter userPrincipalName. This refers to the user’s email address in
the LDAP directory.
LDAP User EncryptedPassword: Enter the password associated with the specified user if you are
using either Sun ONE or Tivoli. Leave blank for Active Directory.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configuring LDAP role mapping
64
4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are
imported successfully.
5. Click OK.
Configuring LDAP role mapping
You can configure the role mapping parameters that determine which groups or roles are imported or
synchronized, or both. The parameters you specify depend on the LDAP server provider you are using.
➤ To configure the LDAP role mapping parameters:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab and then click System Settings.
3. Click the LDAP Role Mapping tab and specify values for the following parameters:
LDAP Role Base DN: The format that is appropriate for the type of LDAP server you are using:
●
(Sun ONE) OU=Groups,DC=your domain,DC=com
●
(Active Directory) CN=Users,DC=yourdomain,DC=com
LDAP Role Search Filter: The format that is appropriate for the type of LDAP server you are using:
●
(Sun ONE) (&(objectclass=groupOfUniqueNames))
●
(Active Directory) (&(objectclass=group))
LDAP Role LoginID: Enter cn if you are using either Sun ONE or Active Directory.
LDAP Role Full Name: Enter displayname if you are using either Sun ONE or Active Directory.
LDAP Role Description: Enter description if you are using either Sun ONE or Active Directory.
LDAP Role Member: The name of the multivalued property that contains role members:
●
(Sun ONE) uniqueMember
●
(Active Directory) member
LDAP Role Member is: Use one of the following options:
●
Distinguished Name if the role member properties identify users by distinguished names,
such as cn=jadmin,ou=people,dc=your domain,dc=com.
●
Login identification if the role member properties identify users by the value of the
property used as the Business Activity Monitoring ES login ID.
4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are
imported successfully.
5. Click OK.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Manually Configuring BAM Server for LiveCycle ES
Manually synchronizing with the LDAP server
65
Manually synchronizing with the LDAP server
You can manually synchronize BAM Server with the LDAP server at any time. Synchronization requests are
queued to prevent concurrent synchronizations.
➤ To manually synchronize with the LDAP server:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line
of a web browser.
2. Click the Administration Console tab and then click System Settings.
3. Click the LDAP Synchronization tab.
4. Click Synchronize Now. The time required to synchronize depends on your environment. A message
appears when the synchronization is complete.
5. Click OK.
Using the BAM Dashboard
When a process is activated and immediately invoked, the process instance is not registered on the
corresponding BAM Dashboard. BAM Server requires several seconds after a process is activated before it
can monitor the process for activity. After you activate a process, wait several seconds before invoking it.
If you install BAM Server after LiveCycle ES has run a process, you will have to populate BAM Dashboard.
Populating BAM Dashboard initializes BAM Server to begin polling the LiveCycle ES database. When this
process is enabled, the AdobeView can be created from the information gathered from the LiveCycle ES
database. In the case of a clean LiveCycle ES installation, the database will be empty and no view will be
created.
➤ To populate BAM Dashboard:
1. Navigate to Workbench > Application Workbench > Events.
2. Find AdobeEvent in the Events list and restart the event, select disable dependencies, and then click
enable all.
3. Select "Disable dependencies" on all the events other than the AdobeEvent and the System Events that
start with VC.
4. Select Enable Only this object during the Enabling ActivityInstanceStartedEvents.
5. Enable all ActivityInstanceCompletedEvents.
6. Select Enable Only this object during the Enabling ProcessInstanceStartedEvents.
7. Enable all ProcessInstanceCompletedEvent, all QueueEvent, all TaskCompletedEvent, all
TaskReassignedEvent, and all TaskSpentTimeOnQueueEvent.
8. Navigate to Workbench > Application Workbench > Views.
9. Find AdobeView in the Views list and restart the view.
Adobe LiveCycle ES
Manually Configuring BAM Server for LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Additional documentation
66
10. Click disable dependencies and then click enable all. There will be a delay while the list of existing
orchestrations is populated.
When BAM Dashboard has been populated, you can log in to BAM Dashboard to view the LiveCycle ES
processes.
➤ To log in to BAM Dashboard:
1. Type the URL to the dashboard in a web browser. For example, type this URL:
http://[host name]:[port]/bam/login/dashboard.htm
2. Log in as an administrator. The default administrator account for BAM Server uses the following
credentials:
Username: system
Password: manager
Additional documentation
You can access additional information on LiveCycle Business Activity Monitor here:
●
Business Activity Monitor - Dashboard at www.adobe.com/go/learn_lc_bamdashboard
●
Business Activity Monitor - Server at www.adobe.com/go/learn_lc_bamserver
●
Business Activity Monitor - Workbench at www.adobe.com/go/learn_lc_bamworkbench
Uninstalling Business Activity Monitoring ES
You must uninstall BAM Server completely before attempting to reinstall.
➤ To uninstall BAM Server:
1. Undeploy and delete the old BAM Server EAR file using WebLogic Server Administration Console.
2. Delete all of the files from the recovery log directory and logging directory that have names similar to
the following patterns:
●
filestore*.dat
●
DEFAULTRECOVERYLOGGER_*
●
chkpoint*
3. Review the contents of the [appserver root]\bin folder and, if any chkpoint* files exist, delete them.
4. Use your database management tools to drop the database tables that store the BAM Server metadata.
Alternatively, you may want to create a new BAM Server metadata database.
8
Advanced Production Configuration
This section describes advanced tuning for LiveCycle Output ES, LiveCycle Forms ES and
LiveCycle PDF Generator ES. This section should only be completed on a production system by an
advanced application server administrator.
LiveCycle Output ES and LiveCycle Forms ES
The current default value for PoolMax is 4. The actual value to set would depend upon the hardware
configuration and the expected usage in your environment.
For optimal use, we recommend that the lower limit of PoolMax must not be less than the number of CPUs
available and the upper limit must be determined by the load pattern on your server. Generally, the upper
limit should be set to twice the number of CPUs on the server.
➤ To modify the existing PoolMax value:
1. Edit the WebLogic startup script using a text editor.
2. Add the following properties for ConvertPdf:
●
com.adobe.convertpdf.bmc.POOL_MAX=4
●
com.adobe.convertpdf.bmc.MAXIMUM_REUSE_COUNT=5000
●
com.adobe.convertpdf.bmc.REPORT_TIMING_INFORMATION=true
●
com.adobe.convertpdf.bmc.CT_ALLOW_SYSTEM_FONTS=true
3. Add the following properties for XMLFM:
●
com.adobe.xmlform.bmc.POOL_MAX=4
●
com.adobe.xmlform.bmc.MAXIMUM_REUSE_COUNT=5000
●
com.adobe.xmlform.bmc.REPORT_TIMING_INFORMATION=true
●
com.adobe.xmlform.bmc.CT_ALLOW_SYSTEM_FONTS=true
LiveCycle PDF Generator ES
LiveCycle PDF Generator ES is capable of doing multiple PDF conversions simultaneously for certain types
of input files. This is enforced through the use of stateless session beans.
EJB Pool Size Configuration
Four different stateless session beans exist for enforcing independent pool sizes for the following types of
input files:
●
Adobe PostScript® and Encapsulated PostScript (EPS) files
●
Image files (such as BMP, TIFF, PNG, JPEG etc.)
●
OpenOffice files
67
Adobe LiveCycle ES
Advanced Production Configuration
Installing and Deploying LiveCycle ES for WebLogic
●
EJB Pool Size Configuration
68
All other file types (except HTML files) like Microsoft Office files, Photoshop, PageMaker, and
FrameMaker files
The pool size for HTML-to-PDF conversions is not managed through the use of stateless session beans.
The default pool size for PostScript and EPS files and for Image files is set to 3, and the default pool size for
OpenOffice and other file types (except HTML) is set to 1.
You can configure the PS/EPS and Image pool-size to a different value, based on your server hardware
configuration, such as the number of CPUs, the number of cores within each CPU, and so on. However, it is
mandatory for the OpenOffice and other file types pool size to be left unchanged (that is, one) for proper
functioning of PDF Generator ES.
This section describes how the pool size for PS2PDF and Image2PDF can be configured for each of the
supported application-servers.
The text below assumes that the following two LiveCycle ES application EARs have been deployed on the
application server:
●
adobe-livecycle-<app-server>.ear
●
adobe-livecycle-native-<app-server>-<platform>.ear
Here, <app-server> should be replaced with the name of the application server on which LiveCycle ES has
been deployed in lowercase (such as “jboss”, “weblogic”. or “websphere”), and <platform> should be
replaced with one of the four strings – “x86_win32”, “x86_linux”, “sparc_sunos”, or “powerpc_aix” –
depending on whether you are running your application server on Windows, Linux, SunOS™, or AIX
operating system.
➤ To configure the pool size for PS2PDF and Image2PDF:
1. Open adobe-livecycle-weblogic.ear in WinRAR.
2. Navigate to the following path, opening nested JAR files in WinRAR successively:
adobe-pdfg-bmc-invoker-ejb.jar > META-INF
3. Extract weblogic-ejb-jar.xml to any suitable location on the file system and open it in a plain text editor,
such as Notepad or vi.
4. In the XML, navigate to the node with the following path (expressed in the standard XPath notation):
weblogic-ejb-jar / weblogic-enterprise-bean
5. Choose the weblogic-enterprise-bean node for which the ejb-name node is set to the value
ImageToPDFInvoker.
6. Further navigate down to stateless-session-descriptor/pool an d set the
max-beans-in-free-pool and initial-beans-in-free-pool nodes to the appropriate value
(that is, the new pool size for Image2PDF conversions).
7. Repeat steps 5 and 6 for the PS2PDF pool size (if required). The ejb-name node for PS2PDF
conversions is set to PSToPDFInvoker.
8. Save your changes and repackage the entire EAR structure in the original form.
9. Redeploy the modified EAR file in WebLogic Server. You can use the WebLogic Administration Console
to perform this task. You will be prompted to restart WebLogic.
A
Troubleshooting
This section discusses possible issues you may encounter when installing and deploying LiveCycle ES, and
suggests steps for avoiding or working around them.
Getting help
This section describes the steps you should take prior to contacting Adobe Support. If, after reviewing the
LiveCycle ES documentation, you have not resolved your issues, contact Adobe Support. To help expedite
your service, have the following information available:
●
What were you doing when the problem occurred?
●
Can you repeat the problem?
●
Was an error message displayed when the problem occurred? Did you observe anything else?
●
If you disable the Show Friendly HTTP Error Messages option in Internet Explorer (Tools > Options >
Advanced), do the errors persist?
Installation considerations
If you are having problems installing, configuring, or deploying LiveCycle ES, make certain that you have
carefully followed the instructions in these LiveCycle ES documents:
●
Preparing to Install LiveCycle ES
●
Installing and Deploying LiveCycle ES for your application server
●
Administering LiveCycle ES
If you have installed and configured everything according to the documentation, review the following
sections for issues similar to those you are experiencing.
Application server considerations
Check the following application server settings prior to contacting Adobe Support:
●
Total transaction lifetime timeout: 300
●
Initial heap size: 256
●
Maximum heap size: 1024 Mb
●
Prepared statement cache: 100
●
Database connection pool maximum: IDP_DS is 100 and RM_DS is 30
●
Topics and queues connection factories
●
Connection pool maximum connections: 50
69
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Database initialization considerations
70
Database initialization considerations
If you are having problems initializing the LiveCycle ES server, consider the following possibilities:
●
Database instances must contain only alphanumeric characters in their names.
●
(Linux and UNIX) Database instances must not exceed the platform-specific threshold of 8 characters.
If the initialization fails at the beginning of the process, check for the following conditions:
●
The LiveCycle ES database has already been created and the user has full rights to it.
●
The database server is accessible when you ping it.
●
The database is empty, that is, it has no tables, sequences, views or index tables.
●
The JNDI name for IDP_DS has been created.
If initialization fails while writing to the Registry, check the application server logs for errors pertaining to
the queues and topics. If errors exist, verify that the queues and topics have been configured properly.
LiveCycle Configuration Manager hangs when re-deploying a LiveCycle ES
EAR file
LiveCycle Configuration Manager may hang at an incomplete stage when re-deploying a LiveCycle ES EAR
file, and fail to deploy the new EAR file.
This problem arises occasionally when WebLogic Server does not release a currently deployed EAR file. To
correct this issue, stop LiveCycle Configuration Manager, manually remove the existing version of the
LiveCycle ES EAR file that you want to update, stop and restart the administrative and managed
WebLogic Servers, then run LiveCycle Configuration Manager to deploy the new EAR file.
Troubleshooting with log files
This section describes how to troubleshoot LiveCycle ES using the log files.
LiveCycle Configuration Manager log file
By default, the LiveCycle Configuration Manager log file is located in
[LiveCycleES root]\ConfigurationManager\log and is named lcm.0.log (or similar). The log files are useful for
LiveCycle Configuration Manager failure analysis and may be required when dealing with Adobe
Enterprise Support.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebLogic
Scheduler service configuration for nondefault JNDI URLs
71
Scheduler service configuration for nondefault JNDI URLs
To function correctly, the Scheduler service may require some additional configuration.
Non-clustered environments
This is the JNDI URL for the IDP_DS that is managed by your application server:
org.quartz.dataSource.idp.java.naming.provider.url
if the JNDI URL differs from the default JNDI URL for the application server (that is, for WebLogic:
t3://localhost:7001).
➤ To set the scheduler properties
1. Create a new file called dscscheduler.properties
2. Set the values of the above properties as necessary for the app server node. For example:
org.quartz.dataSource.idp.java.naming.provider.url =
t3://localhost:7001/
org.quartz.jobstore.isClustered = true
org.quartz.scheduler.instanceId = AUTO
3. Add the JVM argument -Dadobe.idp.scheduler.properties=[Path to this
file]/dscscheduler.properties to the application server startup scripts/configuration.
Error messages
This section contains a list of error messages specific to LiveCycle ES and their definitions.
PDF Generator ES on Windows fails when converting native files
PDF Generator ES running on a Windows operating system may fail when converting native files (for
example, from Microsoft Word to PDF), giving an exception in the log file similar to this:
INFO [PDF Generator] Application server started as user: SYSTEM
This problem arises if you did not use the same user account for all of Microsoft Office, PDF Generator ES,
Acrobat for PDF Generator ES, and your application server process.
To correct this problem, change the user for the Weblogic for Adobe LiveCycle service to be the same as
the user for Microsoft Office.
➤ To set the user for the Weblogic for Adobe LiveCycle service:
1. Select Start > Control Panel > Administrative Tools > Computer Management > Services and
Applications > Services.
2. Double click on the Weblogic for Adobe LiveCycle service, then select the Log On tab.
3. Select This account, then type the user name and password that runs Microsoft Office and click OK.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebLogic
Class not found
72
Class not found
If you see this error, check the following issues:
●
Is the class path setting invalid or missing?
●
Is the JAR file obsolete?
●
Is there a compilation problem in the class?
JNDI name not found
If you see this error, check the following issues:
●
If the symptom is an exception stack trace showing
javax.naming.NameNotFoundException: jdbc/<badName>
check that the expected name is spelled correctly. If it is not, you must fix the code.
➤ To correct most common JNDI exceptions:
1. Check the JNDI tree on the LiveCycle ES application server. Does the name used appear in the tree?
●
If yes, it is most likely that your code has not properly set up the InitialContext object being
used for the lookup and the lookup is being done on a JNDI tree that is not the one the resource is
listed in. Refer to the property values to use in the Installing and Deploying LiveCycle ES document for
your application server.
●
If no, continue to step 2.
2. Does the resource appear in the JNDI tree under a name other than that listed in the lookup?
●
If yes, you are using the wrong lookup name. Provide the correct name.
●
If no, continue to step 3.
3. Review the application server logs during startup. If the application server has been configured to
make this resource available but something is going wrong, an exception will be shown here. Is there
an exception?
●
If yes, review the exception and stack trace. If the NameNotFoundException is a symptom of
another problem based on your investigation of the server logs, move on to the troubleshooting
steps for that problem.
●
If no, continue to step 4.
4. If the resource is not listed in the JNDI tree, and there is no exception at startup to explain why it isn’t
available, the most probable issue is that the application server has not been configured properly to
make that resource available. Review the application server configuration. Has it been configured to
make this resource available?
●
If no, see Installing and Deploying LiveCycle ES for your application server.
●
If yes, this is not one of the common problems that cause this issue. Contact Adobe Support.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Exceptions thrown when initializing the LiveCycle ES database multiple times
73
Exceptions thrown when initializing the LiveCycle ES database multiple
times
When you initialize the LiveCycle ES database after it has already been initialized, exceptions may be
thrown indicating that the POF schema has been initialized.
This error can be safely ignored.
XMLForm.exe permission error
This section explains how to a correct UNIX and Linux permission issue with Forms ES if the following error
message is logged:
Cannot add execute permission on file /[path_to_XMLForm.exe]
To correct this issue, ensure that the swap space on UNIX and Linux servers is at least 3 GB.
WebLogic JTA time-out error
This section explains how to correct a WebLogic time-out issue if you receive the following error message:
<Warning> <com.adobe.workflow.AWS> <ap-sun4> <Server_127> <[ACTIVE]
ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <BEA1-58E59A31956BB0D8F0AB> <> <1178316054656> <000000>
<javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested
exception is: javax.ejb.TransactionRolledbackLocalException: EJB
Exception: ; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 299 seconds
To correct this issue, increase the WebLogic JTA time-out value to a value greater than 300 seconds.
See “Configuring the WebLogic transaction time-out” in Preparing to Install LiveCycle for details about
setting this value.
Failure to deploy adobe-livecycle-weblogic
This section explains how to correct a WebLogic EAR file deployment issue if you receive the following
error message:
Could not start application adobe-livecycle-weblogic.
com.adobe.livecycle.cdv.CDVException[ALC-LCM-030-113]: Failed to deploy
EAR.
If you receive this error, check the WebLogic Administration Console to ensure that it is not locked (that is,
the Lock & Edit button is selected). If it is locked, LiveCycle Configuration Manager will show the
deployment process as 16% complete and the WebLogic Administration Console will show the EAR file as
deployed, but in an installed state. If the WebLogic Administration Console is not locked,
LiveCycle Configuration Manager can deploy the EAR files.
To correct this issue, go to the WebLogic Administration Console, ensure that it is unlocked, and redeploy
the EAR files.
Adobe LiveCycle ES
Troubleshooting
Installing and Deploying LiveCycle ES for WebLogic
Client connection through a proxy server to WebLogic Server on Windows fails
74
Client connection through a proxy server to WebLogic Server on Windows
fails
A client attempting to connect through a proxy server to WebLogic Server running on a Windows
operating system fails with error 1005.
To correct this problem, you must contact BEA support and obtain the appropriate patch for your version
of WebLogic Server to address issue CR297073, then apply the patch to your LiveCycle ES installation. The
following procedure describes how to apply and verify the patch.
➤ To apply and verify the patch for BEA issue CR297073:
1. Log into the WebLogic Server Administration Console.
2. Click on Environment > Servers, click on your server, then click on the Server Start tab.
3. Click Lock & Edit, then in the Class Path property, add the appropriate path for your server at the front
of the property. For example, add the path:
C:\bea\patch_weblogic920\profiles\default\sys_manifest_classpath\
weblogic_patch.jar;
4. Click Save, then Activate Changes.
5. Restart the WebLogic Server.
6. Verify the patch by checking the log file for the LiveCycle ES server (for example,
C:\bea\user_projects\domains\base_domain\servers\server1\logs\server1.log). A log message similar
to the following verifies that the patch is active:
<Nov 16, 2007 11:13:24 AM PST> <Info> <Management> <BEA-141107> <Version:
WebLogic Temporary Patch for CR297073 Mon Jan 22 12:19:24 2007 WebLogic
Server 9.2 Fri Jun 23 20:47:26 EDT 2006 783464 >
Failure to deploy due to PermGen Space error
This section explains how to correct a WebLogic EAR file deployment issue if you receive the following
error message:
java.lang.OutOfMemoryError: PermGen space
If you receive this error you should increase the PermGen space from 256 to 512. You can change this value
using the WebLogic Administration Console.
Unexpected end of file error
This section explains how to correct the following error condition with LiveCycle ES Forms and LiveCycle
ES Output:
com.adobe.idp.DocumentError: java.net.SocketException: Unexpected end of file
from server at com.adobe.idp.Document.passivateInitData(Document.java:867)
If you receive this error, ensure the Document MaxInlineSize parameter is set to a value which is smaller
than IIOP message size parameter defined in the WebLogic Server.
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