Professional Documents
Culture Documents
Installweblogic
Installweblogic
Adobe LiveCycle ES
February 2009 Update 1 (8.2)
2009 Adobe Systems Incorporated. All rights reserved. Adobe LiveCycle ES Update 1 (8.2) Installing and Deploying LiveCycle ES for WebLogic for Microsoft Windows, UNIX, and Linux Edition 2.3, February 2009 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 BSAFE and/or TIPEM software by RSA Security, Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). This product includes software developed by the IronSmith Project (http://www.ironsmith.org/). This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/). This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). This product includes copyrighted software developed by E. Wray Johnson for use and distribution by the Object Data Management Group (http://www.odmg.org/). Portions Eastman Kodak Company, 199- and used under license. All rights reserved. Kodak is a registered trademark and Photo CD is a trademark of Eastman Kodak Company. Powered by Celequest. Copyright 2005-2008 Adobe Systems Incorporated. All rights reserved. Contains technology distributed under license from Celequest Corporation. Copyright 2005 Celequest Corporation. All rights reserved. Single sign-on, extending Active Directory to Adobe LiveCycle ES provided by Quest Software www.quest.comlidentity-management in a subsequent minor release that is not a bug fix (i.e., version 1.1 to 1.2 but not 1.1.1 to 1.1.2) of the Licensee Product that incorporates the Licensed Product. The Spelling portion of this product is based on Proximity Linguistic Technology. Copyright 1989, 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1990 Merriam-Webster Inc. Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 2003 Franklin Electronic Publishers Inc. Copyright 2003 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 2004 Franklin Electronic Publishers, Inc. Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1991 Dr.Lluis de Yzaguirre I Maura Copyright 1991 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
Copyright 1990 Munksgaard International Publishers Ltd. Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1995 Van Dale Lexicografie bv Copyright 1996 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1990 IDE a.s. Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 2004 Franklin Electronics Publishers, Inc. Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1992 Hachette/Franklin Electronic Publishers, Inc. Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 2004 Bertelsmann Lexikon Verlag Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 2004 MorphoLogic Inc. Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1990 Williams Collins Sons & Co. Ltd. Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 1993-95 Russicon Company Ltd. Copyright 1995 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Copyright 2004 IDE a.s. Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA. Notice to U.S. Government End Users. The Software and Documentation are Commercial Items, as that term is defined at 48 C.F.R. 2.101, consisting of Commercial Computer Software and Commercial Computer Software Documentation, as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. 227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60, 60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 8
Whats in this document?............................................................................................................................................................ 8 Who should read this document? ............................................................................................................................................ 8 Additional information...............................................................................................................................................................10
Introduction ............................................................................................................................... 11
About the LiveCycle ES installation, configuration, and deployment process......................................................11 Selecting tasks for configuring and deploying LiveCycle ES........................................................................................11 Upgrading to LiveCycle ES........................................................................................................................................................12 Automatic installation and deployment list.................................................................................................................13 Manual installation and deployment list.......................................................................................................................13
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Contents
5
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Contents
6
Troubleshooting ......................................................................................................................103
Getting help ................................................................................................................................................................................ 103 Installation considerations .............................................................................................................................................. 103 Application server considerations ................................................................................................................................ 103 LiveCycle Configuration Manager hangs when redeploying an EAR file ....................................................... 104 Address a high number of concurrent calls .............................................................................................................. 104 Troubleshooting with log files.............................................................................................................................................. 104 LiveCycle Configuration Manager log file.................................................................................................................. 105 Deleting the application server transaction log file ............................................................................................... 105 Scheduler service configuration for nondefault JNDI URLs....................................................................................... 105 Non-clustered environments.......................................................................................................................................... 105 Error messages ........................................................................................................................................................................... 105 Bean already exists ............................................................................................................................................................. 105 Class not found .................................................................................................................................................................... 106 JNDI name not found ........................................................................................................................................................ 106 Exceptions thrown when initializing the database multiple times .................................................................. 107 XMLForm.exe permission error...................................................................................................................................... 107 J2CA0081E: Method cleanup error on SQL Server.................................................................................................. 107 Database initialization fails on WebLogic .................................................................................................................. 107 WebLogic JTA time-out error.......................................................................................................................................... 108 Failure to deploy adobe-livecycle-weblogic............................................................................................................. 108 Client connection through a proxy server to WebLogic Server fails................................................................ 108 Failure to deploy due to PermGen Space error........................................................................................................ 109 Unexpected end of file error........................................................................................................................................... 109 OutOfMemoryError: Java heap space error............................................................................................................... 109 CORBA COMM_FAILURE exception.............................................................................................................................. 110 Connector for EMC Documentum error ..................................................................................................................... 110 Failure to deploy EAR files ............................................................................................................................................... 110 Failure to deploy solution components ..................................................................................................................... 110 Deploying LiveCycle ES in a distributed environment.......................................................................................... 111 Improving Windows Server Performance with LDAP............................................................................................ 111 Could not start/create deployment errors on Solaris ............................................................................................ 112 PDF Generator ES considerations........................................................................................................................................ 112 Configuring PDF Generator ES to convert MS Office files to PDF format....................................................... 112 Microsoft Visio 2007 default macro settings cause conversion time-out ...................................................... 112
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic 7
Common properties........................................................................................................................................................... 120 Configure LiveCycle ES properties................................................................................................................................ 122 Configure or validate application server properties .............................................................................................. 124 Deploy LiveCycle properties ........................................................................................................................................... 125 Initialize LiveCycle properties......................................................................................................................................... 125 Initialize BAM properties .................................................................................................................................................. 125 Deploy LiveCycle Components properties................................................................................................................ 126 Command line interface usage...................................................................................................................................... 127 Examples usage ......................................................................................................................................................................... 130 Error logs ...................................................................................................................................................................................... 130 Next steps..................................................................................................................................................................................... 130
Adobe LiveCycle Barcoded Forms ES Adobe LiveCycle Business Activity Monitoring Adobe LiveCycle ES Connector for EMC Documentum Adobe LiveCycle ES Connector for IBM FileNet Adobe LiveCycle ES Connector for IBM Content Manager Adobe LiveCycle Content Services ES Adobe LiveCycle Digital Signatures ES Adobe LiveCycle Forms ES Adobe LiveCycle Foundation Adobe LiveCycle Output ES Adobe LiveCycle PDF Generator ES Adobe LiveCycle PDF Generator 3D ES Adobe LiveCycle Process Management ES Adobe LiveCycle Reader Extensions ES Adobe LiveCycle Rights Management ES
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
[appserver root]
These installation locations are examples. Your installation location may be different. WebLogic Server on Windows: C:\bea\weblogic92\ C:\bea\wlserver_10.0\ WebLogic Server on Linux and Solaris: /opt/bea/weblogic92 /opt/bea/wlserver10.0 WebLogic Server on AIX: /usr/bea/weblogic92 /usr/bea/weblogic10.0 or,
server1 for WebLogic Server WebLogic Server on Windows: C:\bea WebLogic Server on Linux and UNIX: /opt/bea
The name of the server configured on your application server. The install directory for WebLogic Server as specified for the BEA_HOME environment variable.
[appserverdomain]
WebLogic Server on Windows: The domain that you configured on C:\bea\user_projects\domains\base_d WebLogic Server. omain WebLogic Server on Linux and UNIX: /opt/bea/user_projects/domains/base _domain
[dbserver root]
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.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Additional information
The resources in this table can help you learn more about LiveCycle ES. For information about General information about LiveCycle ES and the solution components See LiveCycle ES Overview
Whats new in this LiveCycle ES (Enterprise Suite) Whats New release LiveCycle ES terminology LiveCycle ES solution components Other services and products that integrate with LiveCycle ES Installing Adobe LiveCycle Workbench ES Upgrading to LiveCycle ES from a previous version. Performing administrative tasks for LiveCycle ES All the documentation available for LiveCycle ES LiveCycle ES Glossary Adobe LiveCycle ES Adobe Developer Connection Installing Your Development Environment Preparing to Upgrade to LiveCycle ES Upgrading to LiveCycle ES for WebLogic Administering LiveCycle ES LiveCycle ES documentation
LiveCycle ES release information and last-minute Release Notes changes that occur to the product Patch updates, technical notes, and additional information about this product version LiveCycle Technical Support
Introduction
This chapter provides information to help you understand the type of installation and deployment you should perform, and information that will help you understand the installation, configuration, and deployment process:
About the LiveCycle ES installation, configuration, and deployment process on page 11 LiveCycle ES installation, configuration, and deployment lists on page 12
For information about preparing your system for installing LiveCycle ES, including system requirements, see Preparing to Install LiveCycle ES.
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
11
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Introduction
Upgrading to LiveCycle ES 12
Initialize the LiveCycle ES database Deploy LiveCycle ES component deployment Validate the LiveCycle ES component deployment Configure the LiveCycle Reader Extensions ES Rights credential (optional) Import the LiveCycle ES Samples (optional)
If you install Reader Extensions ES, you can also specify and import the Reader Extensions ES Rights credential that is required for applying usage rights to PDF documents. Although you can use LiveCycle Configuration Manager to configure the application server and set up data sources to the database, you may prefer to complete these steps 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.
Use LiveCycle Configuration Manager to configure LiveCycle ES components with the required font and temp directories Manually configure the application server, configure data sources, and deploy LiveCycle ES EAR files Run LiveCycle Configuration Manager to initialize the database Run LiveCycle Configuration Manager to deploy LiveCycle ES components and validate the LiveCycle ES component deployment. Configure Reader Extensions ES credentials and import the LiveCycle ES Samples through LiveCycle Configuration Manager.
Upgrading to LiveCycle ES
Before you install LiveCycle ES for upgrading from LiveCycle 7.x and later, ensure that you completed the tasks that are described in Preparing to Upgrade to LiveCycle ES.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Introduction
Automatic installation and deployment list 13
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.
Ensure that you have the required software installed in the target environment. (See Preparing to Install LiveCycle ES (Single Server)). Run the installation program. (See Installing the Solution Component Files on page 14.) Run LiveCycle Configuration Manager and select all the tasks on the Task Selection screen. This step configures and assembles the LiveCycle ES EAR files, configures application server settings, deploys the EAR files and other components to the application server, initializes the LiveCycle ES database, and verifies the deployment. (See Configuring LiveCycle ES for Deployment on page 19.) Access the LiveCycle Administration Console and User Management. (See Accessing LiveCycle Administration Console on page 49.) (Optional) Configure LDAP access. (See Configuring LiveCycle ES to access LDAP on page 61.)
Ensure that you have the required software installed and configured in the target environment. (See Preparing to Install LiveCycle ES (Single Server). Run the installation program. (See Installing the Solution Component Files on page 14.) Run LiveCycle Configuration Manager and select the Configure LiveCycle ES EARs task. This task configures and assembles LiveCycle ES. (See Configuring LiveCycle ES for Deployment on page 19.) Manually configure the WebLogic Application Server. (See Manually Configuring WebLogic Server on page 27). 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 45.) Run LiveCycle Configuration Manager to deploy LiveCycle ES component files, initialize the LiveCycle ES database, and (optionally) deploy product samples. (See Configuring LiveCycle ES for Deployment on page 19.) Access LiveCycle Administration Console and User Management. (See Accessing LiveCycle Administration Console on page 49.) (Optional) Configure LDAP access. (See Configuring LiveCycle ES to access LDAP on page 61.)
Installing the product files on page 14 Viewing the error log on page 18
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:
When installing on Linux, the installation program uses the logged-in user's home directory as a temporary directory for storing files. As a result, messages such as the following text may appear in the console:
WARNING: could not delete temporary file /home/<username>/ismp001/1556006
When you complete the installation, you must manually delete the temporary files. Caution: Ensure that the temporary directory for your operating system meets the minimum requirements as outlined in Preparing to Install LiveCycle ES (Single Node). The temporary directory is one of the following locations:
(Windows) TMP or TEMP path as set in the environment variables (UNIX) Logged-in users home directory
On UNIX systems, you can install, configure, and deploy as a non-root user:
14
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
(Solaris) /var/tmp
Note: When you are installing the solution components on a Linux or UNIX operating system, you must be logged in as the root user to successfully install the solution components to the default location, which is /opt/adobe/LiveCycle8.2/. If you are logged in as a non-root user, change the installation directory to one that you have permissions (read-write-execute privileges) for. For example, you can change the directory to /home/[username]/livecycle8.2. Temporary files are generated in the system default temp directory or in the directory that you specified. In certain instances, the generated temporary files may remain after the installer is closed. You can choose to remove these files manually.
Installing 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 19. Note: To avoid permission issues during deployment, ensure that you run the LiveCycle ES installer and LiveCycle Configuration Manager as the same user who will run the WebLogic server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. Navigate to the ./livecycle_server/8.2 directory of the installation media. 2. If you are installing on AIX or Linux and you are not installing directly from a release DVD, set executable permissions on the installation file by typing one of the following commands at the command prompt:
chmod 007 linux_livecycle8_setup.bin
(Windows) Double-click the win_livecycle8_setup.exe file. (UNIX) From a command prompt, type the file name that is appropriate for your operating system:
./linux_livecycle8_setup.bin ./solaris_livecycle8_setup.bin
If you are installing on a Windows staging platform for deployment to UNIX, start the Windows executable. Specify the following additional arguments to redirect the LiveCycle ES installer temporary directory to an alternate, non-default location:
-cp:p stage.jar -is:tempdir [path to alternate temporary directory]
4. When prompted, select the language for the installation to use and click OK. 5. On the Welcome screen, click Next. If you have a previous version of LiveCycle ES 8.0.x the Update Installation screen appears. 6. Select one of the following options and then click Next:
Upgrade Existing Installation to LiveCycle ES v8.2: Choose this option if you intend to upgrade from LiveCycle ES 8.0.x to LiveCycle ES 8.2. Ensure that the directory shown on the screen corresponds with the existing version of LiveCycle ES; otherwise, browse to the correct directory. Choosing this option ensures that information from the existing installation, such as the product serial number, is used. LiveCycle Configuration Manager performs the actual upgrade tasks when the installation process is complete. It is important that you back up your existing environment before you upgrade. (See LiveCycle ES Database and GDS Backup and Recovery in Administering LiveCycle ES.)
Note: If you choose to upgrade the existing LiveCycle ES, go to the Upgrading to LiveCycle ES 8.2 from 8.0.x document for your application server and follow the instructions for upgrading in that document.
Install LiveCycle ES v8.2: Choose this option to install a new, separate instance of LiveCycle ES 8.2. If you choose this option, your previous installation of LiveCycle ES will not be upgraded or removed.
7. On the Installation Location screen, accept the default directory as listed or click Browse and navigate to the directory where you intend to install the solution component, and then click Next. Note: If you type the name of a directory that does not exist, it is created for you. Caution: When you install the solution component, you can specify a different installation location. If you are installing on Linux or UNIX, the directory you specify should not contain any spaces; otherwise, the installation program does not install the solution component.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
8. Type a serial number in the text box and click Add. If you have licensed multiple solution components, repeat this step for each serial number you have. After you add all the serial numbers to the list, click Next. Note: If you chose to upgrade an existing installation to LiveCycle ES 8.2, the serial number or numbers already appear in the Solution Component License Type list. You do not need to add a serial number; just click Next to continue. Tip: You can reset the serial number by clicking Clear. 9. Read the Adobe LiveCycle ES Server License Agreement and select I accept to the terms of the license agreement. If you do not accept the license agreement, you cannot continue. 10. Click Next and then select the JAVA SE SDK location. You can browse the correct SDK location or you can continue with the default and click Next. 11. (Windows only) On the OS Selection screen, select the operating system that you plan to configure LiveCycle ES for and click Next. Note: At this point, you can specify to use Windows as a staging platform for your deployment. You can select a UNIX operating system as the target for deployment even if you are installing on Windows. (See Installing on a Windows staging platform for deployment on Linux or UNIX on page 15.) 12. (PDF Generator ES or PDF Generator 3D ES for Windows only) Select the appropriate option on the PDF Generator ES screen:
Yes, enable native application support for PDF Generator ES: Select this option if Acrobat 9.0 is installed. If you do not have Acrobat installed, install it now.
Note: PDF Generator 3D ES requires native application support to convert 3D files to PDF. If you have an unsupported version of Acrobat installed, complete the LiveCycle ES installation, uninstall Acrobat, and then install Acrobat 9.0 from the LiveCycle ES installation media by following the instructions in the procedure Configuring Acrobat 9.0 on page 55.
No, do not enable native application support for LiveCycle PDF Generator ES: Select this option if you do not intend to use the native application functionality.
13. (PDF Generator ES for or PDF Generator 3D ES Windows only) Confirm that you have Acrobat installed and click Next. 14. On the Pre-installation Summary Details screen, review the details and click Install. The installation program displays the progress of the installation. 15. Review the release notes that are displayed and click Next. 16. Review the details of the Post-installation summary screen. Select Start LiveCycle Configuration Manager and then click Finish. Note: Selecting the Start LiveCycle Configuration Manager option starts LiveCycle Configuration Manager, which allows you to complete your configuration and deployment immediately. If you are not ready to run LiveCycle Configuration Manager, ensure that Start LiveCycle Configuration Manager is not selected when you click Finish. You can start LiveCycle Configuration Manager later, when you are ready. (See Configuring LiveCycle ES for Deployment on page 19.)
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Note: (PDF Generator ES or PDF Generator 3D ES for Windows only) If you did not choose to install Acrobat 9.0 using the LiveCycle ES installer, you need to complete the steps in Configuring Acrobat 9.0 on page 55.
Next steps
You must now configure LiveCycle ES for deployment. (See Configuring LiveCycle ES for Deployment on page 19.)
Configure LiveCycle ES solution components in an EAR file for deploying to the application server Configure application server properties to support LiveCycle ES Validate application server configuration Deploy LiveCycle ES EAR files Initialize the LiveCycle ES database Deploy LiveCycle ES component Validate the LiveCycle ES component deployment (Optional) Configure the LiveCycle Reader Extensions ES Rights credential (if Reader Extensions ES is installed) Initialize BAM metadata for LiveCycle ES Business Activity Monitoring (if Business Activity Monitoring is installed) (Optional) Import the LiveCycle ES Samples into LiveCycle ES
This chapter assumes that you prepared your environment for hosting LiveCycle ES and installed the solution component files. If you have not done this task, see Preparing to Install LiveCycle ES Single Node and Installing the Solution Component Files on page 14.
19
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
LiveCycle ES configuration task Configure LiveCycle ES Configure application server Validate application server configuration Deploy LiveCycle ES EARs Initialize LiveCycle ES database Initialize Business Activity Monitoring Deploy LiveCycle ES components Validate LiveCycle ES component deployment Validate server connection Validate LiveCycle ES server connection Validate database connection Configure Reader Extensions ES Import Samples
LCM GUI Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No
LCM CLI
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
If you use LiveCycle Configuration Manager to deploy the EAR files, LiveCycle Configuration Manager accesses these files and deploys them to the application server. If you manually deploy the LiveCycle ES EAR files, you can access the files in this directory and deploy them to the application server. After LiveCycle Configuration Manager configures the LiveCycle ES EAR files, you may rename the EAR files to a custom file name (for example, to specify in the file name a version identifier, or any other information required by standard practices in the local J2EE environment). LiveCycle Configuration Manager does not support deployment or undeployment of EAR files with custom file names. If your EAR files use a custom file name, you must manually deploy and undeploy them to the application server (for example, when you deploy the initial custom-named EAR files, and when applying any later changes such as service packs or patches). Note: If you previously deployed LiveCycle ES files, you must first undeploy the product EAR files from the application server. However, if you use LiveCycle Configuration Manager to deploy EAR files, it automatically undeploys previously deployed files before deploying updated files. If errors occur during this process, you can undeploy the EAR files manually. (See Uninstalling LiveCycle ES on page 84.) If you are configuring a remote application server, ensure that an application server is also installed on the same computer as LiveCycle Configuration Manager so that LiveCycle Configuration Manager can use the application server library files.
To configure, upgrade to, and deploy LiveCycle ES:
Tip: You can press F1 in LiveCycle Configuration Manager to view Help information for the screen you are viewing. This Help contains details that may not be included in this document and are specific to the context of each screen in LiveCycle Configuration Manager. 1. If you did not start LiveCycle Configuration Manager automatically from the installation program, navigate to the [LiveCycleES root]/configurationManager/bin directory and enter the appropriate command:
2. If prompted, select a language and click OK. 3. On the Welcome screen, click Next. 4. On the Upgrade task selection screen, ensure that Upgrade from LiveCycle ES is not selected, then click Next to continue. Caution: If you want to upgrade an existing LiveCycle ES installation, do not continue this procedure. For upgrade information and procedures, see the Preparing for Upgrading to LiveCycle ES guide applicable to your current version of LiveCycle ES and the Upgrading to LiveCycle ES guide applicable to your application server. 5. On the Solution Component Selection screen, select the LiveCycle ES solution components that you installed and plan to deploy, and then click Next. 6. On the Task Selection screen, select all the tasks you want to perform and click Next. Note: If you do not plan to configure the application server and deploy LiveCycle ES automatically by using LiveCycle Configuration Manager, do not select the Configure application server,
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Validate application server configuration, and Deploy LiveCycle ES EARs tasks. However, you must manually configure the application server by completing the steps provided in Manually Configuring WebLogic Server on page 27. Caution: Do not select the Configure application server option if you previously configured your application server cluster manually. Selecting this option for a manually configured application server cluster can cause LiveCycle ES errors or failure. 7. On the Configure LiveCycle ES (1 of 3) screen, click Configure. When the EAR files are configured, click Next. 8. On the Configure LiveCycle ES (2 of 3) screen, set the directories that LiveCycle ES will use to access fonts and store temporary data that is associated with processing jobs:
(Optional) To change the default location of the Adobe server fonts directory, type the path or browse to the directory. (Optional) Specify a directory for the Customer fonts directory box. The directory contains any additional fonts that you have licensed and installed. (Optional) To change the default location of the System fonts directory, type the path or browse to the directory. (Optional) To specify the Location of the temporary directory, click Browse. (Optional) To enable FIPS, ensure that Enable FIPS is selected. Select this option only if you require the Federal Information Processing Standards (FIPS) to be enforced.
9. After you specify the directories, click Next. 10. On the Configure LiveCycle ES (3 of 3) screen, add the location of the GDS directory path by doing one of these tasks:
Type the location of the GDS directory. Click Browse and navigate to the location of the GDS directory.
Note: If you do not specify a specific location for the global document storage root directory, a default value is used. 11. Click Next, click Configure to configure the LiveCycle ES EARs with this directory information and, after the configuration is complete, click Next. 12. (Content Services ES only) On the LiveCycle Content Services ES Configuration screen, set the parameters that Content Services ES will use:
Deploy Type: Select Single Server or . Content storage root directory: Specify the root directory that is used by Content Services ES. WebLogic: Select the version of WebLogic Server that is installed (10.X or 9.X).
13. On the Configure LiveCycle ES Summary screen, click Next. 14. On the Deploy LiveCycle ES EARs screen, click Deploy. 15. (LiveCycle ES Connector for EMC Documentum, LiveCycle ES Connector for IBM FileNet, or LiveCycle ES Connector for IBM Content Manager only) On the Configure LiveCycle ES Connectors screen, press F1, follow the instructions in the Help dialog box, and then click Next.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
16. On the Application Server Configuration Details screen, provide the information for the fields (mandatory fields are denoted by an asterisk) and then click Verify Server Connection. When the verification has completed successfully, click Next. Press F1 for details about the required information. Note: 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. 17. On the Application Server Configuration Selection screen, select the tasks for LiveCycle Configuration Manager to perform and then click Next. Press F1 for details about the required information. 18. On the Server Settings Configuration screen, provide the information for the fields, and then click Next. Press F1 for details about the required information. If you are configuring your server settings manually, without exiting LiveCycle Configuration Manager, perform the tasks that are described in the section Manually Configuring WebLogic Server on page 27. 19. On the Datasource Configuration screen, provide the information for the fields and then click Test Database Connection. When the connection is tested successfully, click Next. Press F1 for details about the required information. Note: If you are using Microsoft SQL Server for your database, you must download the appropriate database drivers as described in Preparing to Install LiveCycle ES (Single Server). You can choose to manually configure data sources instead of having LiveCycle Configuration Manager configure them. Select Manually configure datasource in the WebLogic Server Administration Console before continuing, then, without exiting LiveCycle Configuration Manager, go to the WebLogic administrative console and configure data sources, as needed, by following the instructions in the Manually Configuring WebLogic chapter in Installing and Deploying LiveCycle ES for WebLogic. 20. (If you selected Configure Server Settings only) On the Application Server Configuration screen, click Configure. Restart the server if you are prompted to do so. When the process is completed, click Next. 21. (If you selected Configure Datasource only) On the Application Server Configuration Validation screen, select the tasks for validating and then click Validate. When the process is completed, click Next. 22. On the Deploy LiveCycle ES EARs screen, select the EAR files to deploy and the virtual host to deploy to, and then click Deploy. This operation may take several minutes to complete. Restart the server if you are prompted to do so. When the deployment has completed successfully, click Next. Caution: If you configured a non-default GDS directory in step 10, you must restart the WebLogic Server before you deploy the LiveCycle ES EAR files. 23. On the LiveCycle ES Database Initialization screen, verify that the host (using the IP address) and port information matches the host and port information for a LiveCycle ES server , and then click Initialize. The database initialization task creates tables in the database, adds default data to the tables, and creates basic roles in the database. Restart the server if you are prompted to do so. When the initialization has completed successfully, click Next. Note: The port on this screen refers to the managed server instead of the admin server port.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
24. (Business Activity Monitoring only) On the Initialize Business Activity Monitoring screen, provide the information for the following fields: Database type: The database on which BAM metadata is running. BAM Host: The name or IP address of the computer that hosts the application server on which BAM server is running. BAM HTTP Port: The HTTP service port that the database uses (for example, 7001). BAM Administrator User ID: The administrator ID that is required to log in to BAM Workbench. The default user ID is system. BAM Administrator Password: The password to log in to the BAM Workbench. The default password is manager. 25. (Business Activity Monitoring only) Click Initialize to begin the initialization process and, when initialization is complete, click Next to continue. 26. On the LiveCycle ES Server Information screen, in the Password box, type password. (This password is the default administrator password; it is recommended that you change the password later.) 27. Click Verify Server Connection to ensure that the information for the default application server is correct and, when the verification has completed successfully, click Next. Note: The server information that appears on this screen represents default values for the deployment. Verifying the server connection helps narrow troubleshooting in case failures occur in the deployment or validation. If the connection test passes but deployment or validation fails in the next few steps, connectivity issues can be eliminated from the troubleshooting process. 28. On the LiveCycle Component Deployment screen, click Deploy. The components that are deployed at this time are Java archive files that plug into the LiveCycle ES service container for purposes of deploying, orchestrating, and executing services. Click View Progress Log to view the deployment progress and, when the deployment has completed successfully, click Next. 29. On the LiveCycle Component Deployment Validation screen, click Validate. LiveCycle Configuration Manager validates that the LiveCycle components (Java archive files) are deployed to and running on the LiveCycle ES server. Click View Progress Log to view the validation progress and, wen the validation has completed successfully, click Next. 30. (Reader Extensions ES only) On the LiveCycle Reader Extensions ES Credential Configuration screen, specify the details that are associated with the Rights credential that activates the solution component services: LiveCycle Reader Extensions ES Rights credential: The path and file name of the Rights credential (.pfx or .p12 file type). LiveCycle Reader Extensions ES Rights credential password: The password that is associated with the credential. This password was provided with the credential file. Name for the configured Rights Credential: The name (or alias) that LiveCycle Configuration Manager gives the credential when it is configured. This name appears in the Reader Extensions ES web interface, and the alias that is used to reference the credential through SDK calls. You can create any unique name for the Rights credential. Tip: You can skip this step at this time by selecting Configure later using LiveCycle Administration Console. You can configure the Rights credential by using LiveCycle Administration Console after you
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
complete the deployment. (After logging in to LiveCycle Administration Console, click Home > Settings >Trust Store Management > Local Credentials.) Click Configure and then click Next. 31. (Optional) On the LiveCycle ES Samples Import screen, click Import. When the import has completed successfully, click Next or click Skip LiveCycle Samples Import to import the samples at a later time. 32. On the Summary page, review the tasks performed and click Next. The Next steps screen displays URL and login information. 33. Click Exit.
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. Under Domain Structure, click Deployments. 4. Under Change Center, click Lock and Edit. 5. Select the LiveCycle application box and select the LiveCycle applications, such as (adobe-livecycle-native-weblogic-[OS], adobe-livecycle-weblogic, adobe-workspace-client). 6. On the Deploy tab, click Stop Application. 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 Activate Changes. 10. Stop and start the Administration Server and the Managed Server. After you uninstall the EAR file, you may need to reconfigure your EAR file and redeploy it if you have added something that requires additional JVM or JMS settings. You should also run LiveCycle Configuration Manager to migrate essential and non-essential data, reinitialize the database, and deploy LiveCycle ES components.
Next steps
Now that you have configured and deployed LiveCycle ES, you can do the following tasks:
Verify the deployment. (See Verifying the deployment and accessing LiveCycle Administration Console on page 49.) Access LiveCycle Administration Console. (See Accessing LiveCycle Administration Console on page 49.)
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configure PDF Generator ES or PDF Generator 3D ES. (See Configuring LiveCycle PDF Generator ES or 3D ES on page 53.) Perform the final setup for Rights Management ES. (See Final setup for LiveCycle Rights Management ES on page 61.) Configure LiveCycle ES solution components to access LDAP. (See Configuring LiveCycle ES to access LDAP on page 61.) Perform watched folder performance-tuning for PDF Generator ES. (See Setting PDF Generator ES or 3D ES watched folder performance parameters on page 62.) Enable FIPS mode. (See Enabling FIPS mode on page 64.) Enable HTML digital signatures. (See Configuring HTML digital signature on page 64.) Configuring Connector for EMC Documentum, Connector for IBM Content Manager, or Connector for IBM FileNet. (See Configuring the Connector for EMC Documentum service on page 65, Configuring the Connector for IBM FileNet service on page 69, or Configuring the LiveCycle ES Connector for IBM Content Manager on page 80.) Set environment variables for PDF Generator ES. (See Setting environment variables on page 54.) Uninstall LiveCycle ES. (See Uninstalling LiveCycle ES on page 84.)
Modifying class files on page 27 Configuring the JVM arguments on page 29 Increasing the WebLogic Server stuck thread time-out on page 28 Configuring database connectivity on page 30 Configuring JMS resources for WebLogic Server on page 41
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 the System Requirements for Installing LiveCycle ES chapter in Preparing to Install LiveCycle ES (Single Server). 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. (SQL Server only) Modify the domain_name/bin/startWebLogic.sh or startWebLogic.cmd script by adding the SQL server JAR file location in the class path, as shown in this example:
set CLASSPATH=C:\bea\user_projects\domains\base_domain\idplib\sqljdbc.jar
2. To access the WebLogic Server 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. 3. On the login screen, type your WebLogic user name and password and click Log In.
27
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
4. Under Change Center, click Lock & Edit. 5. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server name. 6. In the Settings for Server pane, click the Configuration tab > Server Start tab. 7. 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)
Note: For WebLogic 9.2, you must manually change the location of the tools.jar file to where you installed the Sun JDK.
For example, in a Windows environment using WebLogic 10.0, enter the following text:
C:\Adobe\LiveCycle8.2\lib\weblogic\pop3.jar;C:\bea\wlserver_10.0\server\lib\ weblogic.jar;C:\bea\jrockit90_150_04\lib\tools.jar;C:\Adobe\LiveCycle8.2\lib \db\oracle\ojdbc14.jar
For example, in a UNIX environment using WebLogic 10.0, enter the following text:
/opt/adobe/livecycle8.2/lib/weblogic/pop3.jar:/opt/bea/wlserver_10.0/server/ lib/weblogic.jar:/opt/jrockit-jdk1.5.0_06/lib/tools.jar:/opt/adobe/livecycle 8.2/lib/db/oracle/ojdbc14.jar
Note: When using WebLogic 9.2, modify the above examples to use the directory called weblogic92 instead of wlserver_10.0. The above examples specfiy the Oracle JDBC driver file. If you are using another database, this JAR file will be specified accordingly. 8. In the Arguments box, add the following arguments separated by a space delimiter
-Dadobeidp.RootDirectory=[AppServerdomain] -Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true -Djava.security.policy=[WebLogicHome]\server\lib\weblogic.policy
If you are using IPv6, replace - Djava.net.preferIPv4Stack=true with -Djava.net.preferIPv6Stack=true. Replace [WebLogicHome] with the WebLogic home directory, as shown in this example:
-Djava.security.policy=\opt\bea\weblogic92\server\lib\weblogic.policy
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 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. On the Configuration tab, click on the Tuning tab. 6. In the Stuck Thread Max Time box, type 1200 and then click Save. 7. Under Domain Structure, click your domain name. 8. On the Configuration tab, click the JTA tab. 9. In the Timeout Seconds box, enter 300. 10. Click Save and then click Activate Changes.
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 click LogUnder 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 > Server Start tab. 5. In the Arguments box, append this information to the end of the current content:
(Solaris using 32-bit JVM) -Xms256m -Xmx1024m -XX:MaxPermSize=256m (Solaris using 64-bit JVM) -Xms256m -Xmx1792m -XX:MaxPermSize=256m (Windows, Linux 32-bit) -Xms256m -Xmx1024m (Windows, Linux 64-bit) -Xms256m
-Xmx1792m
6. Click Save and then click Activate Changes. 7. Restart WebLogic managed server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 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. On the next screen, click the Configuration tab > 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\ojdbc14.jar
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 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 JNDI name box, type IDP_DS. In the Database Type list, select Oracle. In the Database Driver list, select Oracles Driver (Thin) Versions: 9.0.1,9.2.0,10.
6. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
7. Click Next and 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 appears. 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) and then 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 30. 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 Rights Management ES installed. 1. Under Change Center, click Lock & Edit. 2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New. 3. 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 Oracle. In the Database Driver list, select Oracles Driver (Thin) Versions: 9.0.1,9.2.0,10.
4. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
5. Click Next and 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. 6. Click Next and then click Test Configuration to verify the configuration settings. Note: If the test is successful, a Connection test succeeded message appears. Click Next. Otherwise, review the error message that appears and modify the settings as required until the test succeeds. 7. On the next screen, select the server that the data source will connect to (in this case, the managed server) and then click Finish.
To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click RM_DS. 2. On the next screen, click the Configuration tab > Connection Pool tab, and set the following properties:
In the Initial Capacity box, type 1. In the Maximum Capacity box, type 20. 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.
Copy the mysql-connector-java-3.1.12-bin.jar driver file from the [DVD_root]/third_party/jdbc directory on the installation DVD to the [appserverdomain]/idplib directory.
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 click Log In. 3. Under Change Center, click Lock & Edit.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 JNDI name box, type IDP_DS. In the Database Type list, select MYSQL. In the Database Driver list, select MySQL's Driver (Type 4) Versions:using com.mysql.jdbc.Driver.
6. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit. 7. Click Next and define the following properties that apply to the database 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 MySQL is running Port: Keep the default value Database User Name: The name of the user you created on the MySQL 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 appears. 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) and then 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 > Connection Pool tab. 3. In the Maximum Capacity box, type 30. 4. Click Save and then click Activate Changes. 5. Restart WebLogic managed server.
To create a new data source for MySQL for LiveCycle Rights Management ES:
Note: This procedure applies only if you have Rights Management ES installed. 1. Under Change Center, click Lock & Edit. 2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New. 3. 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 MYSQL.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
In the Database Driver list, select MySQL's Driver (Type 4) Versions:using com.mysql.jdbc.Driver.
4. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit. 5. Click Next and define the following properties that apply to the MySQL 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 MySQL is running Port: Keep the default value Database User Name: The name of the user you created on the MySQL database Password and Confirm Password: The password associated with the user 6. Click Next and then click Test Configuration to verify the configuration settings. Note: If the test is successful, a Connection test succeeded message appears. Click Next. Otherwise, review the error message that appears and modify the settings as required until the test succeeds. 7. On the next screen, select the server that the data source will connect to (in this case, the managed server) and then click Finish.
To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click RM_DS or EDC_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 1. In the Maximum Capacity box, type 20. In the Capacity Increment box, type 5. In the Statement Cache Size box, type 100. Click Save and then click Activate Changes.
Copy the db2jcc.jar and db2jcc_license_cu.jar files from one of these locations to the [appserverdomain]/idplib directory:
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
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 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. On the next screen, click the Configuration tab > Server Start tab. 6. In the Class Path box, type the location and file name for the db2jcc.jar file to class path, such as in this example:
DOMAIN_HOME\idplib\db2jcc.jar
7. Repeat step 6 for the db2jcc_license_cu.jar file. 8. Click Save and then click Activate Changes.
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 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 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 set the following properties:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
In the Driver Class Name box, type com.ibm.db2.jcc.DB2Driver In the URL box, type jdbc:db2://[host name]:[port]/db2_db_instance_name 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 appears. 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.
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 > Connection Pool tab. 3. In the Maximum Capacity box, type 30. 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 installed Rights Management ES. 1. Under Change Center, click Lock & Edit. 2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New. 3. 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.
4. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit. 5. Click Next and 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 6. Click Next and set the following properties:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
In the Driver Class Name box, type com.ibm.db2.jcc.DB2Driver In the URL box, type jdbc:db2://[host name]:[port]/db2_db_instance_name In the Properties box, type user=<userid> (userid as mentioned in Database User
Name).
7. Click Test Configuration to verify the configuration settings. Note: If the test is successful, a Connection test succeeded message appears. Click Next. Otherwise, review the error message that appears and modify the settings as required until the test succeeds. 8. On next screen, select the server that the data source will connect to (in this case, the managed server). 9. Click Finish and Activate Changes.
To configure the connection pool settings:
1. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click RM_DS. 2. On the next screen, click the Configuration tab > Connection Pool tab. 3. In the Maximum Capacity box, type 20. 4. Click Save and then click Activate Changes. 5. Restart WebLogic managed server.
If you have not done so already, download the SQL Server 2005 JDBC Driver 1.1 from the Microsoft DownLoad Center. Follow the instructions on the website for downloading and installing the driver. Make a note of the directory location where you install the driver on your system.
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 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. On the next screen, click the Configuration tab > Server Start tab.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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
1. Under Change Center, click Lock & Edit. 2. Under Domain Structure, click Services > JDBC > click Data Sources and, in the right pane, click New. 3. 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 MS SQL Server. In the Database Driver list, select Microsoft's MS SQL Server Driver (Type 4) Versions:2005.
4. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit. 5. 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). 6. Click Next and 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 7. Click Next and then click Test Configuration to verify the configuration settings. Note: If the test is successful, a Connection test succeeded message appears. Click Next. Otherwise, review the error message that appears and modify the settings as required until the test succeeds. 8. On the next screen, select the server that the data source will connect to (in this case, the managed server.) 9. 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 > Connection Pool tab. 3. In the Maximum Capacity box, type 30. 4. Click Save and then click Activate Changes.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Note: This procedure applies only if you have Rights Management ES installed. 1. Under Change Center, click Lock & Edit. 2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click New. 3. 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.
4. Click Next and select Supports Global Transactions and Emulate Two-Phase Commit. 5. Click Next and 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 6. Click Next and, if using Integrated Security, type integratedSecurity=true in the Properties box. Note: If you set this value to true, you must ensure that you configured your SQL Server to use Integrated Security. (See Preparing to Install LiveCycle ES (Single Server).) 7. Click Test Configuration to verify the configuration settings. Note: If the test is successful, a Connection test succeeded message appears. Click Next.Otherwise review the error message that appears and modify the settings as required until the test succeeds. 8. On the next screen, select the server that the data source will connect to (in this case, the managed server) and then 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 RM_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 1. In the Maximum Capacity box, type 20. In the Capacity Increment box, type 5.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
4. Click Save and then click Activate Changes. 5. Restart WebLogic managed server.
To map the Windows login to the LiveCycle ES database user:
Note: You must already have a user account created and associated with your Windows domain. 1. Using Microsoft SQL Server Management Studio, connect to the database server that hosts the LiveCycle ES database. 2. Set the Authentication mode to Windows authentication. 3. Under Security > Logins, create a new account for the Windows domain user and select Windows authentication. 4. On the Login - New screen, click User Mapping and set the database and default schema for the new user. 5. Select db_owner as the Database role and click OK. To verify that you created the user, expand the LiveCycle ES database in the navigation tree and click Security > Users. The new user is listed there.
To configure integrated security on Windows:
1. Start the WebLogic Server Administration Console by typing http://[host name]:[port]/console in the URL line of a web browser. Note: Start the application server by using the Windows domain user. If WebLogic Server is running as a service, it should be started by using the Windows domain user account. 2. Type the user name and password that you created for the WebLogic Server domain and click Log In. 3. Under Change Center, click Lock & Edit. 4. Under Domain Structure, click [base_domain] > Services > JDBC > Data Sources and, in the right pane, click IDP_DS. 5. On the next screen, click the Configuration tab > Connection Pool tab and, in the Properties box, type integratedSecurity=true. 6. Under Domain Structure, click [base_domain] > Services > JDBC > Data Sources and, in the right pane, click RM_DS. 7. On the next screen, click the Configuration tab > Connection Pool tab and, in the Properties box, type integratedSecurity=true. 8. On the computer where the application server is installed, add sqljdbc_auth.dll to the Windows systems path (C:\Windows). Note: The sqljdbc_auth.dll file is in the same location as the Microsoft SQL JDBC 1.1 driver installation (default is [InstallDir]/sqljdbc_1.1/enu/auth/x86).
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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.
Caution: If the JMS data source is different from IDP_DS (for example, a separate database or MQSeries), some JMS messages may be lost upon recovery from a system failure. This may include jobs that are waiting to be processed or processes that have previously failed. To avoid this issue, configure the JMS data source to use the same database instance as IDP_DS.
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 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. 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 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 then, in the Persistent Store list, select IDPJDBCStore. 9. Click Next and assign the JMS Server to your managed server and select your managed server from the Target list. 10. Click Finish and then click Activate Changes.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 click Log In. 3. Under Change Center, click Lock & Edit. 4. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click New. 5. On the next screen, in the Name box, type IDPJMSModule. 6. Click Next and, under Targets, select your managed server. 7. Click Next and select Would you like to add resources to this JMS system module? 8. Click Finish and then click the Advanced Targeting tab.
To create the JMS queues:
1. Under Change Center, click Lock & Edit. 2. Under Domain Structure, click Services > Messaging > JMS Modules and, in the right pane, click IDPJMSModule. 3. Click New and, on the next screen, select Queue. 4. Click Next and set the following properties:
In the Name box and JNDI Name box, type adobe_PECommandQueue. In the Template list, select None (default).
5. Click Next and, in the Subdepoyments list, 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 then click OK. Note: You need to create a subdeployment only once. For each additional queue, select the same subdeployment instead of creating a new one. This subdeployment will also be used for topics. 6. In the Targets list, select IDPJMSServer, and then click Finish. 7. Repeat steps 3 to 6 for each of the queues in the table, replacing the queue name and JNDI name in step 4. JMS queue name adobe_PEDCommandQueue adobe_JobManagerQueue JNDI name adobe_PEDCommandQueue adobe_JobManagerQueue
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 > 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. 3. Click Next and, in the Name box and JNDI box, type adobe_TaskEventTopic. 4. Click Next and, in the Subdeployments list, 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 then select Connection Factory. 3. Click Next and, in the Name box and JNDI box, type IDPQueueConnectionFactory. 4. Click Next and then click Advanced Targeting. 5. In the Subdeployments list, 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. Topic connection factory IDPTopicConnectionFactory JobManagerQueueConnectionFactory JNDI name IDPTopicConnectionFactory JobManagerQueueConnectionFactory
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 > 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 steps
You must now deploy the LiveCycle ES EAR files to the application server. (See Manually Deploying to WebLogic Server on page 45.)
About deploying LiveCycle ES solution components on page 45 Deploying to WebLogic Server on page 46
Installed the required software and files, and know the location of the directories you will be working with. If you did not complete this task, see Preparing to Install LiveCycle ES (Single Server). Run LiveCycle Configuration Manager to configure and assemble LiveCycle ES solution components according to your system and application server requirements. To add a solution component to your deployment, you can run LiveCycle Configuration Manager to make the changes and then redeploy the updated EAR file.
If you are deploying LiveCycle ES for the first time, initialize the database by using LiveCycle Configuration Manager after you deploy the product. If you are using an external web server, see your web server documentation for information about the configuration that is required to allow access to the application server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
After LiveCycle ES is configured with LiveCycle Configuration Manager (required), these files are located in the [LiveCycleES root]/configurationManager/export directory.
1. To access the WebLogic Server 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, 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, select the managed server name). 9. Click Next, accept the default settings, and then click Finish. 10. Under Change Center, click Activate Changes. 11. In the right pane, select the check box for the application you just installed. 12. Click Start and, in the menu, select Servicing all requests. 13. In the right pane, click Yes and, under Change Center, click Lock & Edit. 14. Repeat steps 5 to 13 for each of the EAR files listed in Summary of deployable components on page 45. 15. When the deployment is complete, restart WebLogic. (See Restarting WebLogic Server on page 46.)
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. In the WebLogic Server Administration Console, under Domain Structure, click the domain name. 2. Click the Control tab and select the check box beside the server you want to stop. 3. Click Shutdown and select one of these 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 that is currently in progress. Force Shutdown Now: Initiates a forced shutdown, which causes 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 shut down by viewing the table at the bottom of the Control tab. The table displays a list of all the servers and indicates their current state.
To stop WebLogic Administration Server:
3. Enter the WebLogic user name and password (if you enabled security when installing WebLogic).
To restart WebLogic Administration Server:
3. Enter the WebLogic user name and password (if you enabled security when installing WebLogic).
To restart WebLogic Managed Server:
1. When the WebLogic Administration Server has started, log in to the WebLogic Server Administration Console. 2. Under Change Center, 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 and select the check box beside the managed server you want to start. 5. Click Start and then click Yes.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Next steps
You must run LiveCycle Configuration Manager to initialize the database, and deploy the components and LiveCycle ES archive files (LCAs). You can also choose to validate the component and archive file deployment. (See Configuring and deploying LiveCycle ES on page 20.)
Post-Deployment Activities
This chapter describes how to verify the deployment by accessing the LiveCycle Administration Console and checking the application server log files. It also describes how to get started using LiveCycle ES solution components and services after they are installed, configured, and deployed to your application server:
Verifying the deployment and accessing LiveCycle Administration Console on page 49 Accessing solution component web applications on page 50 Accessing the Content Services ES repository on page 52 Accessing User Management on page 52 Configuring LiveCycle PDF Generator ES or 3D ES on page 53 Final setup for LiveCycle Rights Management ES on page 61 Configuring LiveCycle ES to access LDAP on page 61 Setting PDF Generator ES or 3D ES watched folder performance parameters on page 62 Enabling FIPS mode on page 64 Configuring HTML digital signature on page 64 Configuring the Document Management service for LiveCycle Content Services ES on page 65 Configuring the Connector for EMC Documentum service on page 65 Configuring the Connector for IBM FileNet service on page 69 Configuring the LiveCycle ES Connector for IBM Content Manager on page 80 Uninstalling LiveCycle ES on page 84
After you configure the settings in this chapter, for additional information about configuring your LiveCycle ES environment for development and production, see Administering LiveCycle ES.
49
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Viewing the log files 50
Console also provides access to Applications and Services, which administrators use for managing archives and deploying services to a production environment. The default user name and password for logging in is administrator and password. After you log in the first time, access User Management and change the password. If you have upgraded, the user name and password remain the same as when they were set by the administrator when was configured. Before you access LiveCycle Administration Console, LiveCycle ES must be deployed and running on your application server. For information about using LiveCycle Administration Console, see Applications and Services Administration Help.
To access LiveCycle Administration Console:
The default port number for WebLogic Server is 7001. (When you created a new managed server, you may have set a different port.Manager server uses a default port of 8001) 2. In the User Name box, type administrator and, in the Password box, type password. 3. After you log in, click Services to access the service administration pages or click Settings to access the pages on which you can administer settings for different solution components.
LiveCycle Reader Extensions ES LiveCycle Workspace ES LiveCycle Rights Management ES LiveCycle Content Services ES
After accessing the web applications by using the default administrator permissions to ensure that they are accessible, you can create additional users and roles so that others can log in and use the applications. (See User Management Help.)
To access the Reader Extensions ES web application:
Note: You must apply a Reader Extensions ES credential and apply the user roles for a new user. (See Configuring SSL in Administering LiveCycle ES.)
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Accessing Rights Management ES 51
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 Reader Extensions Web Application role .
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
To access the Content Services ES web application:
Note: You must apply the LiveCycle Contentspace Administrator or LiveCycle Contentspace roles for a new user to login to this web application. To do this, you must create the users in User Management and grant them the appropriate role. 1. Open a web browser and enter this URL:
http://localhost:[port]/contentspace (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
1. Open a web browser and enter this URL: http://[server]:[port]/edc/Login.do where [port] is the port assigned to the WebLogic Managed Server. Note: The administrator user cannot access the Rights Management ES end-user web application. You can create new users by using LiveCycle Administration Console.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Accessing User Management 52
1. Open a web browser and enter this URL: http://[server]:[port]/adminui where [port] is the port assigned to the Managed WebLogic Server. 2. Click Services > LiveCycle Rights Management ES. For information about setting up users and roles for Rights Management ES, see Administering LiveCycle ES.
To assign the LiveCycle Rights Management End User role:
1. Log in to LiveCycle Administration Console. (See Accessing LiveCycle Administration Console on page 49.) 2. Click Settings > User Management > Users and Groups. 3. In the Find box, type all and, in the In list, select Groups. 4. Click Find and, for the required domains, click All Principals in the list that appears. 5. Click the Role Assignments tab and click Find Roles. 6. In the list of roles, select the check box next to LiveCycle Rights Management End User. 7. Click OK and then click Save.
1. Log in to LiveCycle Administration Console. 2. On the home page, click Settings > User Management. Note: For information about configuring users with User Management, click User Management Help in the upper-right corner of the User Management page.
File Transfer Protocol (FTP) Web-based Distributed Authoring and Versioning (WebDAV) Common Internet File Services (CIFS)
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring LiveCycle PDF Generator ES or 3D ES 53
1. Open a web browser and enter this URL: ftp://[server name]:[port] Note: The default port for the Content Services ES repository is port 8021. 2. Log in using your user name and password. Note: You can not log in to the Content Services ES repository by FTP using the Mozilla FireFox browser. Use another browser (for example, Internet Explorer) to access the Content Services ES repository by FTP.
To access the Content Services ES repository using WebDAV:
1. Open Windows Explorer and navigate to My Network Places . 2. Right click and select Add a network place. 3. Enter the following network address: http://[server name]:[port]/contentspace/webdav 4. Log in using your user name and password.
To access the Content Services ES repository using CIFS:
Note: Your Content Services ES repository must be previously configured to support CIFS access. 1. On a computer running the Windows operating system, click Start > Run. 2. Enter the following: \\[server name]a Note: You will not be asked for a user name or password.
Setting environment variables on page 54 Configuring the application server to use HTTP proxy server on page 54 Setting the Adobe PDF Printer as the default printer on page 55 Configuring Acrobat 9.0 on page 55 Installing East Asian characters in Windows on page 56 Adding fonts to PDF Generator ES or PDF Generator 3D ES on page 57 Installing the IPP client on page 60
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Setting environment variables 54
Example
C:\Program Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe C:\Program Files\Adobe\FrameMaker7.1\FrameMaker.exe C:\WINDOWS\Notepad.exe C:\Program Files\OpenOffice.org 2.0 C:\Program Files\Adobe\PageMaker 7.0\PageMaker.exe C:\Program Files\WordPerfect Office 12\Programs\wpwin12.exe
Note: The environment variable OpenOffice_PATH is set to the installation folder instead of the path to the executable. You do not need to set up the paths for Microsoft Office applications such as Word, PowerPoint, Excel, Visio, and Project, or for AutoCAD. The Generate PDF service starts these applications automatically if they are installed on the server.
To create a new Windows environment variable:
1. Select Start > Control Panel > System. 2. Click the Advanced tab and click Environment Variables. 3. In the System variables section, click New. 4. Enter the environment variable name you need to set (for example, enter Photoshop_PATH). This folder is the one that contains the executable file. For example, type the following code:
D:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe To set the PATH variables on Linux or UNIX (OpenOffice only):
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Setting the Adobe PDF Printer as the default printer 55
Complete the following procedure to start your application server with HTTP proxy host setting.
To add the setting to stand-alone WebLogic:
1. Stop WebLogic if it is running. 2. From command line, edit the startWebLogic script in the C:\Bea\user_projects\[your-domain]\bin directory:
(Windows)
set PROXY_SETTINGS=-Dhttp.proxyHost=<hostname> -Dhttp.proxyPort=[port]
(Linux, UNIX)
PROXY_SETTINGS=-Dhttp.proxyHost=<hostname> -Dhttp.proxyPort=[port]
1. Select Start > Printers and Faxes. 2. In the Printers and Faxes window, right-click Adobe PDF and select Set as Default Printer.
1. If an earlier version (8.1 or earlier) of Acrobat is installed, uninstall it by using Add or Remove Programs in the Windows Control Panel. 2. Acrobat 9.0 Professional Extended is provided with the LiveCycle ES media or as an option for ESD download.
If you are using the media, insert the Acrobat 9.0 Professional Extended CD. If you are using the ESD downloads, download Acrobat 9.0 Professional Extended from your ESD location.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Installing East Asian characters in Windows 56
4. Navigate to the additional\scripts folder on the LiveCycle ES installation media. 5. Run the following batch file:
Acrobat_for_PDFG_Configuration.bat [LiveCycleES root]
6. Open Acrobat and select Help > Check for updates > Preferences. 7. Deselect Automatically check for Adobe updates.
To validate the Acrobat 9.0 Professional Extended installation:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat. If the PDF file opens successfully, Acrobat 9.0 Professional Extended is installed correctly. 2. If the PDF file does not open correctly, uninstall Acrobat and reinstall it. Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after the Acrobat installation is completed and disable the automatic updates for Acrobat. Set the Acrobat_PATH environment variable to point to Acrobat.exe (such as C:\Program Files\ Adobe\Acrobat 9.0\Acrobat\Acrobat.exe).
To configure native application support:
1. Install and validate Acrobat as described in the previous procedure. 2. Set Adobe PDF printer as the default printer. 3. (PDF Generator 3D ES) Register the DLL file located at [LiveCycle8.2 root]\plugins\x86win32\ PDFG3dAddin.dll.
1. Select Start > Control Panel and open Regional and Language Options. 2. Click the Languages tab and select Install Files for East Asian Languages. 3. Click the Advanced tab and select all the options under Code Page Conversion Tables. If converted PDF files are still missing fonts, verify that the Arial Unicode MS (TrueType) font (ARIALUNI.TTF) is present in the C:\WINDOWS\Fonts directory.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Adding fonts to PDF Generator ES or PDF Generator 3D ES 57
Non-Adobe applications
The following list contains non-LiveCycle ES applications that PDF Generator ES or PDF Generator 3D ES can use for PDF generation on the server side:
Microsoft Office Excel Microsoft Office PowerPoint Microsoft Office Project Microsoft Office Visio Microsoft Office Publisher AutoDesk AutoCAD Corel WordPerfect Adobe Photoshop CS Adobe FrameMaker Adobe PageMaker Adobe Acrobat Professional Extended
Note: In addition to these applications, your list may include additional applictions that you added. Of the above applications, the OpenOffice Suite (which includes Writer, Calc, Draw, and Impress) is available on Windows, Solaris, and Linux platforms, whereas other applications are available on Windows only.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring HTML to PDF conversions 58
OpenOffice Fonts Troubleshooting Guide at http://www.openoffice.org/FAQs/fontguide.html. Some of the text in this guide is applicable only to OpenOffice 1.x and therefore may be obsolete for OpenOffice 2.x Importing Fonts into OpenOffice 2.1 at http://openoffice.blogs.com/openoffice/2007/02/ font_import_wiz.html. Even though this blog mentions OpenOffice 2.1, the instructions that are mentioned should be applicable to OpenOffice 2.2 and later.
1. Install and validate Acrobat as described in Configuring Acrobat 9.0 on page 55. 2. Locate the pdfgen.api file in the [LiveCycle8.2 root]\plugins\x86win32 directory and copy it to [Acrobat9.0 root]\Acrobat\plug_ins directory.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring HTML to PDF conversions 59
Caution: The HTML-to-PDF conversion will fail if a zipped input file contains HTML files with double-byte characters in the filenames. To avoid this problem, do not use double-byte characters when naming HTML files. 1. Copy the Unicode font to any of the following directories as appropriate for your system:
Windows [Windows root]\windows\fonts [Windows root]\winnt\fonts UNIX /usr/X/lib/X11/fonts/TrueType /usr/openwin/lib/X11/fonts/TrueType /usr/share/fonts/default/TrueType /usr/X11R6/lib/X11/fonts/ttf /usr/X11R6/lib/X11/fonts/truetype /usr/X11R6/lib/X11/fonts/TrueType /usr/X11R6/lib/X11/fonts/TTF /Users/cfqauser/Library/Fonts /System/Library/Fonts /Library/Fonts /Users/ + System.getProperty(<user name>, root) + /Library/Fonts System.getProperty(JAVA_HOME) + /lib/fonts
2. Modify the font-name mapping in the cffont.properties file located in the [LiveCycle8.2 root]/adobe-generatepdf-dsc.jar file:
Unpackage this archive, and locate the cffont.properties file and open it in an editor. In the comma-separated list of Java font names, add a map to your Unicode system font for each font type, as shown in these examples where kochi mincho is the name of your Unicode system font:
dialog=Arial, Helvetica, kochi mincho dialog.bold=Arial Bold, Helvetica-Bold, kochi mincho ...
Save and close the properties file, and then repackage and redeploy the adobe-generatepdf-dsc.jar file.
Note: On a Japanese operating system, specify the font mapping in the cffont.properties.ja file as well, which takes precedence over the standard cffont.properties file. Tip: Fonts in the list are searched from left to right, using the first font found. HTML-to-PDF conversion logs return a list of all the font names that are found in the system. To determine the font name you need to map, add the font to one of the directories above, restart the server and run a conversion. You can determine from the log files the font name to use for mapping. To embed the font in the generated PDF files, set the embedFonts property in the cffont.properties file to true (the default is false).
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Installing the IPP client 60
1. Ensure that you successfully installed PDF Generator ES on your server. 2. From a Windows client computer, enter the following URL in your web browser, where [server] is the name of the server where you installed PDF Generator ES and [port] is the application server port used:
http://[server]:[port]/pdfg-ipp/install
3. On the Configure Internet Port screen, select Use the specified user account and provide the credentials of a LiveCycle user who has the PDFG Administrator/User role. This user must also have an email address that can be used to receive the converted files. To have this security setting apply to all users on the client computer, select Use the same security options for all users, and then click OK. Upon successful installation, a dialog box appears, indicating that The Printer Adobe LiveCycle PDF Generator ES has been successfully installed. 4. Click OK. You will now have a printer named Adobe LiveCycle PDF Generator ES in your list of available printers.
To configure IPP Printer on Windows using the native Add Printer wizard:
1. Click Start > Printers and Faxes and double-click Add Printer. 2. Click Next, select A network printer, or a printer attached to another computer, and then click Next. 3. Select Connect to a printer on the internet or on a home or office network and type the following URL for the IPP printer, where [server] is the server name and [port] is the port number where the server is running:
http://[server]:[port]/pdfg-ipp/printer
4. On the Configure Internet Port screen, select Use the specified user account and provide valid User Management credentials. 5. In the Printer Driver Select box, choose any standard PostScript-based printer driver (for example, HP Color LaserJet PS). 6. Complete the installation by choosing appropriate options (for example, setting this printer as default). Note: The user credentials used while adding the printer must have a valid email ID configured in User Management to receive the response.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Final setup for LiveCycle Rights Management ES 61
7. Configure the email services sendmail service. Provide a valid SMTP server and authentication information in the services configuration options.
To install and configure the PDF Generator ES IPP Client using Proxy server port forwarding
1. Configure port forwarding on the CC Proxy server on a particular port to the LiveCycle ES server, and disable the authentication at proxy server level (since LiveCycle ES uses its own authentication). If a client connects to this Proxy server on the forwarded port, then all the requests will be forwarded to the LiveCycle ES server. 2. Install PDFG-IPP printer using the following URL:
http://[proxy server]:[forwarded port]/pdfg-ipp/install.
3. Provide the necessary credentials for authentication of the IPP printer. 4. The IPP printer will be installed on the client machine which you can use for PDF conversion using the firewall protected LiveCycle ES server.
1. Open a web browser, navigate to http://[host name]:[port]/adminui and log in. (See Accessing LiveCycle Administration Console on page 49.) 2. Click Settings > User Management > Domain Management, and then click New Enterprise Domain. 3. In the ID box, type a unique identifier for the domain and, in the Name box, type a descriptive name for the domain. Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100 single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See Adding enterprise domains in User Management Help.) Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for the ID. (See Adding enterprise domains in User Management Help.) 4. Click Add Authentication and, in the Authentication Provider list, select LDAP. 5. Click OK. 6. Click Add Directory and, in the Profile Name box, type a name for your LDAP profile.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Setting PDF Generator ES or 3D ES watched folder performance parameters 62
7. Click Next. 8. Specify values in the Server, Port, SSL, and Binding boxes, and in the Populate Page with box, select a directory settings option such as Default Sun ONE values. (See Directory settings in User Management Help.) 9. (Optional) Test your configuration:
Click Test. The screen displays a message indicating either a successful server test or any configuration errors that exist.
10. Click Next and configure the User Settings as required. (See Directory settings in User Management Help.) 11. (Optional) Test your configuration:
Click Test. In the Test Search Filter box, verify the search filter or specify a new search filter, and then click Submit. The screen displays a list of entries that match the search criteria. Click Close to return to the User Settings screen.
12. Click Next configure the Group Settings as required. (See Directory settings in User Management Help.) 13. (Optional) Test your configuration:
Click Test. In the Test Search Filter box, verify the search filter or specify a new search filter, and then click Submit. The screen displays a list of entries that match the search criteria. Click Close to return to the Group Settings screen.
14. Click Finish to exit the New Directory page and then click OK to exit.
To configure User Management with LDAP (Local Domain):
1. Open a web browser, navigate to http://[host name]:[port]/adminui, and log in. (See Accessing LiveCycle Administration Console on page 49.) 2. Click Settings > User Management > Domain Management, and then click New Local Domain.
1. Log in to LiveCycle Administration Console and click Services > Applications and Services > Service Management. 2. In the list of services, navigate to and click PDFGConfigService, and then set the following values:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring WebLogic to use samples 63
PDFG Cleanup Scan Seconds: 1800 Job Expiration Seconds: 6000 Server Conversion Timeout: Change the default of 270 to a higher value, such as 450.
1. To log in to the WebLogic Server Administration Console, in a browser, type http://localhost:7001/console. 2. Click Lock and Edit. 3. Click Services > Messaging > JMS Modules and, in the right pane, click IDPJMSSystem. 4. On the Configuration tab, under Summery of Resources, click New. 5. Select Queue and click Next. 6. Enter the name as testQueue and the JNDI name as queue/testQueue. 7. Click Next and ensure that the template is set to None. 8. Click Next and, on the next screen, click Advanced Targeting. 9. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment. 10. Under Targets, select IDPJMSServer and then click Finish.
To create a topic:
1. On the Configuration tab, under Summary of Resources, click New. 2. Select Topic and click Next. 3. Enter the name as testTopic and the JNDI name as testTopic. 4. Click Next and ensure that the template is set to None. 5. Click Next and, on the next screen, click Advanced Targeting. 6. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment. 7. Under Targets, select IDPJMSServer and then click Finish.
To create a connection factory:
1. On the Configuration tab, under Summery of Resources, click New. 2. Select Connection Factory and click Next.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Enabling FIPS mode 64
3. Enter the name as ConnectionFactory and the JNDI name as ConnectionFactory. 4. Click Next and ensure that the template is set to None. 5. Click Next and, on the next screen, click Advanced Targeting. 6. In the Subdeployments list on the next screen, select IDP_JMS_SubDeployment. 7. Under Targets, select IDPJMSServer and then click Finish.
1. Log in to LiveCycle Administration Console. 2. Click Settings > Core System > Core Configurations > Configurations. 3. Select Enable FIPS to enable FIPS mode or deselect it to disable FIPS mode. 4. Click OK and restart the application server. Note: LiveCycle ES software does not validate code to ensure FIPS compatibility. It provides a FIPS operation mode so that FIPS-approved algorithms are used for cryptographic services from the FIPS-approved libraries (RSA).
1. Manually deploy the [LivecycleES root]/deploy/adobe-forms-ds.ear file to your application server. 2. Log in to LiveCycle Administration Console and click Service > LiveCycle Forms ES. 3. Select HTML Digital Signature Enabled and then click Save.
Adobe LiveCycle ES
Post-Deployment Activities
65
Installing and Deploying LiveCycle ES for WebLogic Configuring the Document Management service for LiveCycle Content Services ES
1. Log in to LiveCycle Administration Console and click Services > Applications and Services > Service Management. 2. In the list, select DocumentManagementService. 3. On the Configuration tab, in the HTTP Port box, specify the port number you are using, and then click Save.
1. Locate the adobe-component-ext.properties file in the [BEA HOME]/user_projects/domains/Adobe_LiveCycle folder (if the file does not exist, create it). 2. Add a new system property that provides the following Documentum Foundation Classes JAR files (and for the Connector for EMC Documentum 5.3 only, the location of the Documentum Content Server config folder):
dfc.jar (Connector for EMC Documentum 5.3) dfcbase.jar (Connector for EMC Documentum 6.0) aspectjrt.jar log4j.jar
[component id].ext=[JAR files and/or folders]
The new system property should take on this form: For example, using default Content Server and Documentum Foundation Classes installations, add to the file one of the following system properties on a new line, with no line breaks, and end the line with a carriage return:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the Connector for EMC Documentum service 66
Note: The above text contains formatting characters for line breaks. If you copy and paste this text, you must remove the formatting characters. 3. If WebLogic Server is not currently running, start the server. Otherwise, stop and then restart the server. 4. Open a web browser and enter this URL: http://localhost:8001/adminui (local deployment using the default port) 5. Log in using the default user name and password: User name: administrator Password: password 6. Navigate to Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings and perform these tasks:
Type all the required Documentum repository information. To use Documentum as your repository provider, under Repository Service Provider Information, select EMC Documentum Repository Provider, and then click Save. (For more information, click the Help link in the upper-right corner of the page in the EMC Documentum Help. )
7. (Optional) Navigate to Services > LiveCycle ES Connector for EMC Documentum > Repository Credentials Settings, click Add, specify the Docbase information, and then click Save. (For more information, click Help in the upper-right corner.) 8. Navigate to Services > Applications and Services > Service Management and select these services:
9. Click Start. If any of the services do not start correctly, check the settings entered in step 6. 10. Do one of the following tasks:
To use the Documentum Authorization service (EMCDocumentumAuthProviderService) to display content from a Documentum repository in the Resources view of Workbench ES, continue with this procedure. Using the Documentum Authorization service overrides the default LiveCycle ES authorization and must be configured to log in to Workbench ES using Documentum credentials. To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super administrator credentials (by default, Administrator and password).
You have now completed the required steps for this procedure. Use the credentials provided in step 6 for accessing the default repository in this case and use the default LiveCycle ES authorization service. 11. Restart WebLogic Server. 12. Log in to LiveCycle Administration Console and click Settings > User Management > Domain Management. 13. Click New Enterprise Domain, and type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a descriptive name for the domain.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the Connector for EMC Documentum service 67
Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100 single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See Adding enterprise domains in User Management Help.) Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for the ID. (See Adding enterprise domains in User Management Help.) 14. Add a custom authentication provider:
Click Add Authentication. In the Authentication Provider list, select Custom. Select EMCDocumentumAuthProvider and then click OK.
Click Add Authentication. In the Authentication Provider list, select LDAP, and then click OK.
Click Add Directory. In the Profile Name box, type a unique name, and then click Next. Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select User for the Binding option, you must also specify values for the Name and Password fields. (Optional) Select Retrieve Base DN to retrieve base domain names, as required. Click Next, configure the user settings, click Next, configure group settings, as required, and then click Next.
For details about the settings, click User Management Help in the upper-right corner of the page. 17. Click OK to exit the Add Directory page and then click OK again. 18. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups in your LDAP network and the speed on your connection, the synchronization process may take several minutes. (Optional) To verify the status of the synchronization, click Refresh and view the status in the Current Sync State column. 19. Navigate to Settings > User Management > Users and Groups. 20. Search for users that were synchronized from LDAP and perform these tasks:
Select one or more users and click Assign Role. Select one or more LiveCycle ES roles and click OK. Click OK a second time to confirm the role assignment.
Repeat this step for all users that you assign roles to. For more information , click User Management Help in the upper-right corner of the page.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the Connector for EMC Documentum service 68
21. Start Workbench ES and log in by using the following credentials: Username: [username]@[repository_name] Password: [password] The Documentum repository should now be visible in the Resources view within Workbench ES. If you do not log in using the username@repository name, Workbench ES attempts to log in to the default repository specified in step 6. 22. (Optional) If you intend to install the LiveCycle ES Samples for Connector for EMC Documentum, create a Documentum repository named Samples, and then install the samples in that repository. After you configure the Connector for EMC Documentum service, it is recommended that you see Administering LiveCycle ES for information about configuring Workbench ES functions properly with your Documentum repository. Creating the XDP MIME format in your Documentum repository Before users can store and retrieve XDP files from a Documentum repository, you must do one of these tasks:
Create a corresponding XDP format in each repository where users will access XDP files. Configure the Connector for EMC Documentum service to use a Documentum Administrator account when accessing the Documentum repository. In this case, the Connector for EMC Documentum service uses the XDP format whenever it is required.
To create the XDP format on Documentum Content Server using Documentum Administrator:
1. Log in to Documentum Administrator. 2. Click Formats and then select File > New > Format. 3. Type the following information in the corresponding fields: Name: xdp Default File Extension: xdp Mime Type: application/xdp 4. Repeat steps 1 to 3 for all other Documentum repositories where users will store XDP files.
To configure the Connector for EMC Documentum service to use a Documentum Administrator:
1. Open a web browser and enter this URL: http://localhost:[port]/adminui (local deployment using the default port) 2. Log in using the default user name and password: User name: administrator Password: password 3. Click Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the Connector for IBM FileNet service 69
4. Under Documentum Principal Credentials Information, update the following information and then click Save: User Name: [Documentum Administrator user name] Password: [Documentum Administrator password] 5. Click Repository Credentials Settings, select a repository from the list or, if none exist, click Add. 6. Provide the appropriate information in the corresponding fields and then click Save: Repository Name: [Repository Name] Repository Credentials User Name: [Documentum Administrator user name] Repository Credentials Password: [Documentum Administrator password] 7. Repeat steps 5 to 6 for all repositories where users will store XDP files.
Configuring the connector using FileNet 3.5 on page 69 Configuring the connector using FileNet 4.0.1 on page 72)
1. Locate the adobe-component-ext.properties file in the [BEA HOME]/user_projects/domains/ Adobe_LiveCycle folder (if the file does not exist, create it) 2. Add a new system property that provides the location of the following FileNet Application Engine JAR files:
activation.jar javaapi.jar log4j-1.2.8.jar mailapi.jar p8cjares.jar soap.jar xercesimpl.jar xml-apis.jar (optional) pe.jar
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 3.5 70
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service. The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system, add to the file the following system property on a new line, with no line breaks, and end the line with a carriage return: Note: The following text contains formatting characters for line breaks. If you copy this text to a location outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext= C:/Program Files/FileNet/lib2/activation.jar, C:/Program Files/FileNet/lib2/javaapi.jar, C:/Program Files/FileNet/lib2/log4j-1.2.8.jar, C:/Program Files/FileNet/lib2/mailapi.jar, C:/Program Files/FileNet/lib2/p8cjares.jar, C:/Program Files/FileNet/lib2/soap.jar, C:/Program Files/FileNet/lib2/xercesImpl.jar, C:/Program Files/FileNet/lib2/xml-apis.jar, C:/Program Files/FileNet/lib2/pe.jar
Note: Add the text C:/Program Files/FileNet/lib2/pe.jar only if your deployment uses the IBMFileNetProcessEngineConnector service. 3. If WebLogic Server is not currently running, start the server. Otherwise, stop and then restart the server. 4. Open a web browser and enter this URL: http://localhost:7001/adminui (local deployment using the default port) 5. Log in using the default user name and password: User name: administrator Password: password 6. Click Services > LiveCycle ES Connector for IBM FileNet. 7. Provide all the required FileNet repository information and, under Repository Service Provider Information, select IBM FileNet Repository Provider. If your deployment uses the optional process engine service, under Process Engine Settings, select Use Process Engine Connector Service and specify the process engine settings. For more information, click the Help link on the upper-right corner of the page. Note: The credentials you provide in this step are validated later when you start the IBM FileNet repository services. If the credentials are not valid, an error is thrown and the services will not start. 8. Click Save and then navigate to Services > Applications and Services > Service Management. 9. Select the check box next to each of the following services and then click Start:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 3.5 71
If any of the services do not start correctly, verify the settings entered in step 7. 10. Do one of the following tasks:
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the FileNet Authorization service overrides the default LiveCycle ES authorization and must be configured to log in to Workbench ES by using FileNet credentials. To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super administrator credentials (by default, Administrator and password). The credentials provided in step 7 use the default LiveCycle ES authorization service for accessing the default repository in this case.
11. Restart WebLogic Server. 12. Log in to LiveCycle Administration Console and click Settings > User Management > Domain Management. 13. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a descriptive name for the domain. Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100 single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See Adding enterprise domains in User Management Help.) Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for the ID. (See Adding enterprise domains in User Management Help.) 14. Add a custom authentication provider:
Click Add Authentication. In the Authentication Provider list, select Custom. Select IBMFileNetAuthProviderService and then click OK.
Click Add Authentication. In the Authentication Provider list, select LDAP and then click OK.
Click Add Directory. In the Profile Name box, type a unique name, and then click Next. Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select User for the Binding option, you must also specify values for the Name and Password fields. (Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished, click Next. Configure the user settings, click Next, configure group settings as required, and then click Next. For details about the settings, click the Help link in the upper-right corner of the page.
17. Click OK to exit the Add Directory page and then click OK again.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 72
18. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups in your LDAP network and the speed on your connection, the synchronization process may take several minutes. (Optional) To verify the status of the synchronization, click Refresh and view the status in the Current Sync State column. 19. Navigate to Settings > User Management > Users and Groups. 20. Search for users that were synchronized from LDAP and perform these tasks:
Select one or more users and click Assign Role. Select one or more LiveCycle ES roles and click OK. Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the upper-right corner of the page. 21. Start Workbench ES and log in using the following credentials: Username: [username]@[repository_name] Password: [password] The FileNet object store should now be visible in the Resources view within Workbench ES. If you do not log in using username@repository_name, Workbench ES attempts to log in to the default repository specified in step 7. 22. (Optional) If you intend to install the LiveCycle ES samples for Connector for IBM FileNet, create a FileNet object store named Samples and then install the samples in that object store. After you configure your Connector for IBM FileNet service, it is recommended that you see Administering LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet repository.
To configure the connector using FileNet 4.0.1 and CEWS transport: on page 72 To configure the connector using FileNet 4.0.1 and EJB transport: on page 76
1. In the WebLogic Server Administration Console, under Domain Structure, click Environment > Servers and, in the right pane, click the name of your server. 2. Click the Configuration tab and then click Server Start. 3. Under Change Center, click Lock & Edit. 4. In the Arguments box, enter the following text:
-Dwasp.location=/<configuration files location>
For example, using a default FileNet Application Engine installation on a Windows operating system, add this Java option:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 73
-Dwasp.location=C:/Progra~1/FileNet/AE/CE_API/wsi
5. Click Save. 6. Locate the adobe-component-ext.properties file in the [BEA_HOME]/user_projects/domains/Adobe_LiveCycle folder (if the file does not exist, create it). 7. Add a new system property that provides the location of these FileNet Application Engine JAR files:
javaapi.jar log4j-1.2.13.jar soap.jar wasp.jar builtin_serialization.jar wsdl_api.jar jaxm.jar jaxrpc.jar saaj.jar jetty.jar runner.jar p8cjares.jar Jace.jar (optional) pe.jar
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service. The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system, add the following system property on a new line with no line breaks and end the line with a carriage return: Note: The following text contains formatting characters for line breaks. If you copy this text to a location outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext= C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar, C:/Program Files/FileNet/AE/CE_API/lib2/log4j-1.2.13.jar, C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/soap.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/wasp.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/wsdl_api.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxm.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxrpc.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/saaj.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/jetty.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/runner.jar, C:/Program Files/FileNet/AE/CE_API/lib2/p8cjares.jar, C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar, C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 74
Note: Add C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar only if your deployment uses the IBMFileNetProcessEngineConnector service. 8. (FileNet Process Engine Connector only) Using a text editor, create a file with the following content as a single line and end the line with a carriage return:
RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/ wsi/FNCEWS40DIME/
9. Save the file as WCMApiConfig.properties in a separate folder, and add the location of the folder that contains the WCMApiConfig.properties file to the adobe-component-ext.properties file. For example, if you save the file as c:/pe_config/WCMApiConfig.properties, add the path c:/pe_config to the adobe-component-ext.properties file. 10. If a custom JAAS configuration file is being used, add the following lines in the custom JAAS configuration file:
FileNetP8 {weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true;}; FileNetP8WSI {com.filenet.api.util.WSILoginModule required;}; FileNetP8Engine {weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true;}; FileNetP8Server {weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin=true;};
Tip: You can determine whether a custom JAAS configuration file is used from the value of the -Djava.security.auth.login.config property in the application server start command. 11. (FileNet Process Engine Connector only) If your deployment uses the FileNet Process Engine Connector, do one of these tasks, as applicable to your configuration:
If your deployment uses a custom JAAS file, add the following line to the custom JAAS file:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
If your deployment does not use a custom JAAS file, use a text editor to create a file with the following content:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
Save the file as jaas.conf.WSI and add the location of the file as the following Java option in the WebLogic Server start command:
-Djava.security.auth.login.config=<JAAS file location>
For example, if you save the file as C:/pe_config/jaas.conf.WSI, add the following Java option:
-Djava.security.auth.login.config=C:/pe_config/jaas.conf.WSI
12. If WebLogic Server is not currently running, start the server. Otherwise, stop and then restart the server. 13. Open a web browser and enter this URL: http://localhost:7001/adminui (local deployment using the default port) 14. Log in using the default user name and password: User name: administrator Password: password
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 75
15. Click Services > LiveCycle ES Connector for IBM FileNet. 16. Provide all of the required FileNet repository information and, under Repository Service Provider Information, select IBM FileNet Repository Provider. If your deployment uses the optional process engine service, under Process Engine Settings, select Use Process Engine Connector Service and specify the process engine settings. For more information, click the Help link in the upper-right corner of the page. Note: The credentials that you provide in this step are validated later when you start the IBM FileNet repository services. If the credentials are not valid, an error is thrown and the services will not start. 17. Click Save and navigate to Services > Applications and Services > Service Management. 18. Select the check box next to each of these services and then click Start:
If any of the services do not start correctly, verify the settings entered in step 16. 19. Do one of the following tasks:
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the FileNet Authorization service overrides the default LiveCycle ES authorization and must be configured to log in to Workbench ES by using FileNet credentials. To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super administrator credentials (by default, Administrator and password). The credentials provided in step 16 use the default LiveCycle ES authorization service for accessing the default repository in this case.
20. Restart WebLogic Server. 21. Log in to LiveCycle Administration Console and click Settings > User Management > Domain Management. 22. Click New Enterprise Domain and then type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a descriptive name for the domain. Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100 single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See Adding enterprise domains in User Management Help.) Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for the ID. (See Adding enterprise domains in User Management Help.) 23. Add a custom authentication provider:
Click Add Authentication. In the Authentication Provider list, select Custom. Slect IBMFileNetAuthProviderService and then click OK.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 76
Click Add Authentication. In the Authentication Provider list, select LDAP and then click OK.
Click Add Directory and, in the Profile Name box, type a unique name, and then click Next. Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select User for the Binding option, you must also specify values for the Name and Password fields. (Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished, click Next. Configure the user settings, click Next, configure group settings as required, and then click Next. For details about the settings, click Help link in the upper-right corner of the page.
26. Click OK to exit the Add Directory page, and then click OK again. 27. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups in your LDAP network and the speed on your connection, the synchronization process may take several minutes. (Optional) To verify the status of the synchronization, click Refresh and view the status in the Current Sync State column. 28. Navigate to Settings > User Management > Users and Groups. 29. Search for users that were synchronized from LDAP and perform these tasks:
Select one or more users and click Assign Role. Select one or more LiveCycle ES roles and click OK. Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the upper-right corner of the page. 30. Start Workbench ES and log in using the following credentials: User name: [username]@[repository_name] Password: [password] The FileNet object store should now be visible in the Resources view within Workbench ES. If you do not log in using the username@repository name, Workbench ES attempts to log in to the default repository specified in step 16. 31. (Optional) If you intend to install the LiveCycle ES Samples for Connector for IBM FileNet, create a FileNet object store named Samples and install the samples in that object store. After you configure your Connector for IBM FileNet service, it is recommended that you see Administering LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet repository.
To configure the connector using FileNet 4.0.1 and EJB transport:
1. Locate the adobe-component-ext.properties file in the [BEA_HOME]/user_projects/domains/Adobe_LiveCycle folder (if the file does not exist, create it).
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 77
2. Add a new system property that provides the location of the following FileNet Application Engine JAR files:
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service. The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet Application Engine installation on a Windows operating system, add the following system property on a new line, with no line breaks, and end the line with a carriage return: Note: The following text contains formatting characters for line breaks. If you copy this text to a location outside this document, remove the formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext= C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar, C:/Program Files/FileNet/AE/CE_API/lib2/log4j-1.2.13.jar, C:/Program Files/FileNet/AE/CE_API/lib2/p8cjares.jar, C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar, C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar
Note: Add C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar only if your deployment uses the IBMFileNetProcessEngineConnector service. 3. (FileNet Process Engine Connector only) Using a text editor, create a file with the following content as a single line and end the line with a carriage return:
RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/ wsi/FNCEWS40DIME/
4. Save the file you created as WCMApiConfig.properties in a separate folder, and add the location of the folder that contains the WCMApiConfig.properties file to the adobe-component-ext.properties file. For example, if you save the file as c:/pe_config/WCMApiConfig.properties, add the path c:/pe_config to the adobe-component-ext.properties file. 5. If a custom JAAS configuration file is being used, add the following lines in the custom JAAS configuration file:
FileNetP8 { weblogic.security.auth.login. UsernamePasswordLoginModule required authOnLogin=true; }; FileNetP8WSI { com.filenet.api.util.WSILoginModule required; }; FileNetP8Engine { weblogic.security.auth.login. UsernamePasswordLoginModule required authOnLogin=true; }; FileNetP8Server { weblogic.security.auth.login. UsernamePasswordLoginModule required authOnLogin=true; };
Tip: You can determine whether a custom JAAS configuration file is used from the value of the -Djava.security.auth.login.config property in the application server start command.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 78
6. (FileNet Process Engine Connector only) If your deployment uses the FileNet Process Engine Connector, do one of these tasks, as applicable to your configuration:
If your deployment uses a custom JAAS file, add the following line to the custom JAAS file:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
If your deployment does not use a custom JAAS file, use a text editor to create a file with the following content:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
Save the file as jaas.conf.WSI and add the location of the file as the following Java option in the WebLogic Server start command:
-Djava.security.auth.login.config=<JAAS file location>
For example, if you save the file as C:/pe_config/jaas.conf.WSI add the following Java option:
-Djava.security.auth.login.config=C:/pe_config/jaas.conf.WSI
7. If WebLogic Server is not currently running, start the server. Otherwise, stop and then restart the server. 8. Open a web browser and enter this URL:
http://localhost:7001/adminui (local deployment using the default port)
9. Log in using the default user name and password: User name: administrator Password: password 10. Click Services > LiveCycle ES Connector for IBM FileNet. 11. Provide all of the required FileNet repository information and, under Repository Service Provider Information, select IBM FileNet Repository Provider. If your deployment uses the optional process engine service, under Process Engine Settings, select Use Process Engine Connector Service and specify the process engine settings. For more information, click the Help link in the upper-right corner of the page. Note: The credentials you provide during this step are validated later when you start the IBM FileNet repository services. If the credentials are not valid, an error is thrown and the services will not start. 12. Click Save. 13. Under FileNet DSC Configuration Information, in the Port Number box, enter the port number where Content Engine is running. The default port is 7001. 14. Click Save and then navigate to Services > Applications and Services > Service Management. 15. Select the check box next to each of these services and then click Start:
If any of the services do not start correctly, verify the settings entered in step 11.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 79
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a FileNet object store in the Resources view of Workbench ES, continue with this procedure. Using the FileNet Authorization service overrides the default LiveCycle ES authorization and must be configured to log in to Workbench ES by using FileNet credentials. To use the LiveCycle ES repository, log in to Workbench ES by using the LiveCycle ES super administrator credentials (by default, Administrator and password). The credentials provided in step 11 use the default LiveCycle ES authorization service for accessing the default repository in this case.
17. Restart WebLogic Server. 18. Log in to LiveCycle Administration Console and click Settings > User Management > Domain Management. 19. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a descriptive name for the domain. Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100 single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See Adding enterprise domains in User Management Help.) Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for the ID. (See Adding enterprise domains in User Management Help.) 20. Add a custom authentication provider:
Click Add Authentication and, in the Authentication Provider list, select Custom. Select IBMFileNetAuthProviderService and click OK.
Click Add Authentication. In the Authentication Provider list, select LDAP and then click OK.
Click Add Directory and, in the Profile Name box, type a unique name, and then click Next. Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select User for the Binding option, you must also specify values for the Name and Password fields. (Optional) Select Retrieve Base DN to retrieve base domain names as required. When finished, click Next. Configure the user settings, click Next, configure group settings,as required, and then click Next. For information, click the Help link in the upper-right corner of the page.
23. Click OK to exit the Add Directory page, and then click OK again. 24. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups in your LDAP network and the speed on your connection, the synchronization process may take several minutes. (Optional) To verify the status of the synchronization, click Refresh and view the status in the Current Sync State column.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 80
25. Navigate to Settings > User Management > Users and Groups. 26. Search for users that were synchronized from LDAP and perform these tasks:
Select one or more users and click Assign Role. Select one or more LiveCycle ES roles,and click OK. Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the upper-right corner of the page. 27. Start Workbench ES and log in using the following credentials: User name: [username]@[repository_name] Password: [password] The FileNet object store should now be visible in the Resources view within Workbench ES. If you do not log in by using the username@repository name, Workbench ES attempts to log in to the default repository specified in step 11. 28. (Optional) If you intend to install the LiveCycle ES Samples for Connector for IBM FileNet, you must create a FileNet object store named Samples and install the samples in that object store. After you configure your Connector for IBM FileNet service, it is recommended that you see Administering LiveCycle ES for information about configuring Workbench ES functions properly with your FileNet repository.
1. Locate the adobe-component-ext.properties file in the [BEA HOME]/user_projects/domains/Adobe_LiveCycle folder. If the file does not exist, create it. Add a new system property that provides the location of the following IBM II4C JAR Files, Config folder that contains the IBM II4C property files and a ZIP file from DB2 Universal Database Client installation:
Clio4CM.jar cmb81.jar cmbcm81.jar cmbdb281.jar cmbdb2c81.jar cmbfed81.jar cmbfedc81.jar cmbicm81.jar cmbicmc81.jar cmbicmcup.jar cmbjdbc81.jar
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 81
cmbjdbcc81.jar cmblog4j81.jar cmbsdk81.jar cmbservlets81.jar cmbtag81.jar cmbupes81.jar cmbutil81.jar cmbutilfed81.jar cmbutilicm81.jar cmbutiljdbc81.jar cmbview81.jar cmbwas81.jar cmbwcm81.jar cmbwebservices.jar cmbxmlmap.jar cmbxmlservice.jar common.jar common.resources.jar ecore.jar ecore.resources.jar ecore.xmi.jar icmadm81.jar icmrm81.jar icmsdk81.jar jcache.jar log4j-1.2.8.jar NLVLog.jar xalan.jar xerces.jar xsd.jar xsd.resources.jar cmgmt (copy this folder and its contents) db2java.zip
[component id].ext=[JAR files and/or folders]
The new system property look like this structure: For example, using a default DB2 Universal Database Client and II4C installation, in the file, add the following system property on a new line, with no line breaks, and end the line with a carriage return:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 82
com.adobe.livecycle.ConnectorforIBMCM.ext= C:/Program Files/IBM/db2cmv8/lib/Clio4CM.jar, C:/Program Files/IBM/db2cmv8/lib/cmb81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbcm81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbdb281.jar, C:/Program Files/IBM/db2cmv8/lib/cmbdb2c81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbfed81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbfedc81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbicm81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbicmc81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbicmcup.jar, C:/Program Files/IBM/db2cmv8/lib/cmbjdbc81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbjdbcc81.jar, C:/Program Files/IBM/db2cmv8/lib/cmblog4j81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbsdk81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbservlets81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbtag81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbupes81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbutil81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbutilfed81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbutilicm81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbutiljdbc81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbview81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbwas81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbwcm81.jar, C:/Program Files/IBM/db2cmv8/lib/cmbwebservices.jar, C:/Program Files/IBM/db2cmv8/lib/cmbxmlmap.jar, C:/Program Files/IBM/db2cmv8/lib/cmbxmlservice.jar, C:/Program Files/IBM/db2cmv8/lib/common.jar, C:/Program Files/IBM/db2cmv8/lib/common.resources.jar, C:/Program Files/IBM/db2cmv8/lib/ecore.jar, C:/Program Files/IBM/db2cmv8/lib/ecore.resources.jar, C:/Program Files/IBM/db2cmv8/lib/ecore.xmi.jar, C:/Program Files/IBM/db2cmv8/lib/icmadm81.jar, C:/Program Files/IBM/db2cmv8/lib/icmrm81.jar, C:/Program Files/IBM/db2cmv8/lib/icmsdk81.jar, C:/Program Files/IBM/db2cmv8/lib/jcache.jar, C:/Program Files/IBM/db2cmv8/lib/log4j-1.2.8.jar, C:/Program Files/IBM/db2cmv8/lib/NLVLog.jar, C:/Program Files/IBM/db2cmv8/lib/xalan.jar, C:/Program Files/IBM/db2cmv8/lib/xerces.jar, C:/Program Files/IBM/db2cmv8/lib/xsd.jar, C:/Program Files/IBM/db2cmv8/lib/xsd.resources.jar, C:/Program Files/IBM/db2cmv8/cmgmt, C:/Program Files/IBM/SQLLIB/java/db2java.zip
2. If WebLogic Server is not currently running, start the server; otherwise, stop and then restart the server. You can now connect to the IBM Content Manager data store from the IBMCMConnectorService Property Sheets by using the Use User Credentials as the login mode. You have now completed the required steps for this procedure.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Configuring the connector using FileNet 4.0.1 83
(Optional) If you want to connect to IBM Content Manager data store from IBMCMConnectorService Property Sheets by using the Use Credentials From Process Context as the login mode, complete the following procedure.
To connect using Use Credentials from process context login mode:
1. Open a web browser and enter this URL: http://localhost: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 IBM Content Manager > Configuration Settings. 4. Type all of the required repository information and click Save. For more information about the IBM Content Manager repository information, click the Help link in the upper-right corner of the page. 5. Do one of the these tasks:
To use the IBM Content Manager Authorization service (IBMCMProviderService) to use content from an IBM Content Manager data store, in the Processes view of Workbench ES, continue with this procedure. Using the IBM Content Manager Authorization service overrides the default LiveCycle ES authorization and must be configured to log in to Workbench ES by using IBM Content Manager credentials. To use the System Credentials provided in step 7 to use content from an IBM Content Manager data store, in the Processes view of Workbench ES, log in to Workbench ES by using the LiveCycle ES super administrator credentials (by default, Administrator and password). You have now completed the required steps for this procedure. The System Credentials that are provided in step 7 use the default LiveCycle ES authorization service for accessing the default repository in this case.
6. Log in to the LiveCycle Administration Console, and click Settings > User Management > Domain Management. 7. Click New Enterprise Domain and type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a descriptive name for the domain. Note: When using DB2 for your LiveCycle ES database, the maximum permitted length of the ID is 100 single-byte (ASCII) characters or 50 double-byte characters or 25 four-byte characters. (See Adding enterprise domains in User Management Help.) Note: When using MySQL for your LiveCycle ES database, use only single-byte (ASCII) characters for the ID. (See Adding enterprise domains in User Management Help.) 8. Add a custom authentication provider:
Click Add Authentication. In the Authentication Provider list, select Custom, and then select IBMCMAuthProviderService and click OK.
Click Add Authentication. In the Authentication Provider list, select LDAP and then click OK.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Uninstalling LiveCycle ES 84
Click Add Directory. In the Profile Name box, type a unique name, and then click Next. Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select User for the Binding option, you must also specify values for the Name and Password fields. (Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished, click Next. Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the above settings, click the Help link in the upper-right corner of the page. 11. Click OK to exit the Add Directory page and click OK again. 12. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups in your LDAP network and the speed on your connection, the synchronization process may take several minutes. 13. To verify the status of the synchronization, click Refresh and view the status in the Current Sync State column. 14. Navigate to Settings > User Management > Users and Groups. 15. Search for users that were synchronized from LDAP and do these tasks:
Select one or more users and click Assign Role. Select one or more LiveCycle ES roles and click OK. Click OK a second time to confirm the role assignment.
Repeat this step for all users that you want to assign roles to. For more information, click the Help link in the upper-right corner of the page. 16. Start Workbench ES and log in using the following credentials: Username: [username]@[repository_name] Password: [password] The IBM Content Manager data store can now be used in the Processes view within Workbench ES when the login mode for IBMCMConnectorService orchestrable components is selected as Use Credentials from process context. After you configure your Connector for IBM Content Manager service, it is recommended that you see Administering LiveCycle ES.
Uninstalling LiveCycle ES
The uninstall program located in the [LivecycleES root] directory does not remove the files that you deployed to your application server. Caution: By running the uninstall program, all the contents within the product installation directory are subject to removal without further warning. Before you proceed, back up any data you do not want to lose.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Post-Deployment Activities
Uninstalling a LiveCycle ES solution component 85
Remove Adobe LiveCycle ES. Remove Adobe Acrobat 9.0 Professional (if installed with PDF Generator ES). cd [LivecycleES root]/_uninst/server Double-click the livecycle8_uninstall.exe file.
(Linux and UNIX) From a terminal, type ./livecycle8_uninstall.bin (you may need to make this binary an executable file by typing a command, such as chmod 777).
2. Follow the on-screen instructions in the uninstall program, and then click Finish.
Stop and undeploy the existing LiveCycle ES EAR files from your application server. Run LiveCycle Configuration Manager to reconfigure and redeploy the LiveCycle ES EAR files and solution components (omitting the eliminated component).
1. Stop and undeploy the LiveCycle ES EAR files from your application servers administration utility. See Uninstalling EAR files on page 25. 2. Run LiveCycle Configuration Manager. See Configuring and deploying LiveCycle ES on page 20. 3. On the Solution Component Selection screen, select only those components to redeploy or if the previously installed components are selected, deselect the component to remove. 4. On the Task Selection screen, select the following tasks and the click Next:
5. Perform the tasks on the remaining screens, review the Next Steps, and then click Exit. If you are uninstalling Output ES, you will need to perform the following tasks to complete its removal from your LiveCycle ES environment:
Log in to Workbench ES and uninstall the Output service via the Components view. Remove any related samples.
Configuring the keystore on page 86 Creating a managed server for Business Activity Monitoring on page 87 Configuring the keystore on page 86 Creating the bam.properties file on page 87 Creating and configuring the BAM Server metadata database on page 89 Configuring Process Management ES for BAM Server on page 91 Deploying a Business Activity Monitoring application to the WebLogic Server on page 91 Configuring LDAP settings for BAM Server on page 93 Using BAM Dashboard on page 97 Uninstalling Business Activity Monitoring on page 98
The instructions in this document use the following naming conventions for common file paths.
'
Description The home directory of the application server for Business Activity Monitoring.
[LiveCycleES root]
The location where the LiveCycle ES Windows: C:\Adobe\LiveCycle8.2 services are installed Linux and UNIX: /opt/adobe/livecycle8.2
Most of the information about directory locations in this document is cross-platform (all file names and paths are case-sensitive on Linux and UNIX). Platform-specific information is indicated as required.
1. Copy the admin.jks keystore file from [LiveCycleES root]/LiveCycle_ES_SDK\misc\ Business_Activity_Monitoring\keystore to a location that will be called [Admin Keystore Location]. The default password is 40fd2442fa. 2. Copy the user_sample.jks keystore file from [LiveCycleES root]/LiveCycle_ES_SDK\ misc\Business_Activity_Monitoring\keystore to a location that will be called [User Keystore Location]. The default password is 8deb5102f8.
86
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
It is strongly recommended that you create you own user keystore. To create a user keystore, do the following: 1. Refer to Working with Encryption Configuration in LiveCycle Workbench ES Help for information on how to create a Java Keystore. 2. Specify the location of your user keystore with the system setting property called Keystore Location in your bam.properties file. (See Creating the bam.properties file on page 87.)
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. Configure the connection to the BAM Server metadata database. Configure the connection to the LiveCycle ES database. Modify the WebLogic Server JVM.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. If you have not already done so, under Change Center in the WebLogic Server Administration Console, click Lock & Edit. 2. Under Domain Structure, click Environment > Servers and, in the Servers table, click New. 3. 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 to access the server instance from (for example, type 8001). Select No, this is a stand-alone server.
4. Click Next, review the configuration options you chose and then click Finish.
To create and configure a new computer:
1. In the WebLogic Server Administration Console, under Domain Structure, click Environment > Servers and, in the right pane, click the managed server that you created for BAM Server. 2. Click the Configuration tab > General tab. 3. In the Machine list, select the LiveCycle ES computer, and then click Save. 4. Click Activate Changes. 5. Shut down and restart the servers by starting Node Manager, Administration Server, and Managed Server.
1. Under Change Center in the WebLogic Server Administration Console, click Lock & 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:
5. Click Save and then click Activate Changes. 6. Start BAM Server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
User accounts
You must create a dedicated user account that BAM Server can use to connect to the BAM Server metadata database. For details on the required user permissions, please consult Preparing to Install LiveCycle ES (Single Server).
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. If not already started, start the Node Manager, Administration Server, and Managed Servers. 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. Under Change Center, 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. 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) Oracles Driver (Thin) versions 9.x, 10 (MySQL) MySQL's Driver (Type 4) Versions using com.mysql.jdbc.Driver
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, and then 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 > Connection Pool tab. 3. Under Change Center, click Lock and Edit. 4. In the Initial Capacity box, type 1 and, in the Maximum Capacity box, type 20. 5. Accept the default values for all 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. Uncer Change Center, Click Lock and Edit. 2. Under Domain Structure, click Services > JDBC > Data Sources and, in the right pane, click IDP_DS.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
3. On the next screen, click the Targets tab and then select both the BAM Server and the LiveCycle ES server. 4. Click Save and then click Activate Changes.
<use-java-context>false</use-java-context>
1. Log in to LiveCycle Administration Console. 2. Click Services > LiveCycle Process Management ES > Server Settings > BAM Configuration Settings. 3. Type values for the following properties: BAM Host: The host name or IP address of the server that BAM Server is running on. The default value is localhost. BAM Port: The service port of the application server that BAM Server is running on. LiveCycle Server Host: The host name or IP address of the server that the LiveCycle ES server is running on. The default value is localhost. LiveCycle Server SOAP Port: The service port of the application server that the LiveCycle ES server is running on. For WebLogic this value is typically 8001. User Name: (Optional) The user name of the administrator user account that Process Management ES uses to access BAM Server. The default user name is system. Note: If you specify the user name for a different user account, ensure that the user has complete administrative privileges for BAM Server. For information about administering BAM Server user accounts, see LiveCycle Workbench ESHelp. Password: (Optional) A valid password for the user name specified above. The default password is manager. 4. Click Save and restart the LiveCycle ES server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. If not already started, 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. Under Change Center, click Lock and Edit. 4. Under Domain Structure, click Deployments and, in the right pane, click Install. 5. Click Upload your files, browse to the [LiveCycle root]/deploy directory, select the Lava_Adobe-weblogic.ear file, and then click Next. 6. In the Choose Targeting style list, select Install this deployment as an application, and then click Next. 7. In the Select Deployment target list, select the server that was created for BAM Server in Creating a managed server for Business Activity Monitoring on page 87, and then click Next. 8. Click Next, click Finish, and then Save. 9. 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 When you log in for the first time, you are prompted to configure the system settings. 3. Click Open system settings. 4. In the Configure list, select Checkpoint Configuration and then ensure that Enable Checkpoint is selected. 5. In the Configure list, select System Control and then ensure that Recover State on Restart is selected. 6. In the Configure list, select Encryption Configuration. 7. Specify a password in the Keystore Password and User PrivateKey Password boxes. The default user keystore password is 8deb5102f8. 8. Click OK.
To import the LiveCycle ES metadata definitions:
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line of a web browser.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
2. On the login page, type the system manager user name and password. These values are the defaults: Username: system Password: manager 3. Click the Administration Console tab and click Import/Export. 4. Select Import Metadata from a JAR file on the server and enter the full path to the location of the Business Activity Monitoring metadata template that is appropriate for the type of database that you are using for the LiveCycle ES database:
These files are installed in the [LiveCycle root]/deploy directory. 5. Click OK to import the file.
You can configure a connection to only one LDAP server. BAM Server creates roles based on groups that are defined on the LDAP server. When BAM Server encounters a group that a role is not yet created for, it creates the role and assigns it a set of zero permissions. You can later modify the permissions as required. (See Configuring LDAP role mapping on page 96.) If BAM Server imports a user and the user does not belong to a group that a Business Activity Monitoring role corresponds to, the user is created but remains unassigned to any roles. You cannot change the role that a user is assigned to if the user is imported from the LDAP server. Role assignments for imported users can be accomplished by making changes to the LDAP server. However, you can assign manually-created users to roles that are created based on LDAP groups.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
If the connection to the LDAP server is not secure, you should use SSL. For authentication, Simple Authentication and Security Layer (SASL) is the recommended method and is well supported by LDAP. For security reasons, the access permissions of the LDAP synchronization user should be limited to querying the LDAP server. (See Configuring automatic LDAP synchronization on page 94.)
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.
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line of a web browser. 2. Click the Administration Console tab and then click System Settings. 3. Click the LDAP Synchronization tab and then select LDAP Enabled if it is not already selected.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
4. Specify values for the following properties: Initial Context Factory: The JNDI name through which BAM Server connects to the LDAP server. The default value is com.sun.jndi.ldap.LdapCtxFactory. You probably do not need to change this value. LDAP Server: The DNS name or IP address of the LDAP server. LDAP Port: The port that the LDAP server is running on. The default port is typically 389. However, if you select the SSL option, the default port is typically 636. Confirm with your LDAP administrator which port to specify. LDAP SSL: Select this option if the LDAP server is configured to use SSL. Selecting this option may affect the LDAP Port setting. LDAP Authentication: The authentication method that is used by the LDAP server. Select one of the following options:
Simple SASL (Simple Authentication and Security Layer). Select this option for Sun ONE. Compare Encrypted Password
LDAP Principal DN Prefix: For the simple authentication method, the text you specify will be inserted before the user's login name:
For LDAP servers that require DN login, set this to the appropriate property value followed by an equal sign (for example, cn= or uid=). For Active Directory, leave this value blank.
LDAP Principal DN Suffix: For the simple authentication method, the text you specify will be inserted after the user's login name:
For LDAP servers that require DN login, set this to the appropriate chain of values; the first character of the suffix must be a comma (","), as shown in the example:
,ou=Users,dc=domain,dc=name
For Active Directory, which requires a simple login with an email address, set this to an at symbol (@) followed by the domain name that is set for Active Directory.
LDAP Synchronization User: The user that binds to the server and reads the lists of users and roles. For security purposes, you must specify a user account that can only read the LDAP directory. LDAP Synchronization Password: The password that is associated with the user that is specified for the LDAP Synchronization User option. 5. Click Test Connection. The connection and the user-mapping and role-mapping configuration are tested. If the connection settings are correct, a message indicates that the connection was successful. If you did not yet configure LDAP User Mapping and LDAP Role Mapping, the message returns an error. 6. To set the LDAP Synchronization Schedule, use the Add Schedule, Edit Schedule, and Remove Schedule buttons to create the schedule you want, and then click OK. Note: You should set synchronization for a time when the fewest number of users are likely to be logged in.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line of a web browser. 2. Click the Administration Console tab, and then click System Settings. 3. Click the LDAP User Mapping tab and specify values for the following parameters: LDAP User Base DN: The root of the tree that will be searched for users, as shown is these examples:
LDAP User Search Filter: The format that is appropriate for the type of LDAP server you are using. For example, your LDAP server can have a special group for Business Activity Monitoring users. This filter can then ensure that only users with this group membership are imported. LDAP User LoginID: The login ID of the indicated provider. This value becomes the users login ID in Business Activity Monitoring. LDAP User Full Name: Enter cn if you are using either Sun ONE or Active Directory. LDAP User Description: Enter description if you are using either Sun ONE or Active Directory. LDAP User PrimaryEmail: Enter userPrincipalName. This refers to the users email address in the LDAP directory. LDAP User EncryptedPassword: Enter the password that is associated with the specified user if you are using either Sun ONE or Tivoli. Keep the default value for Active Directory. 4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are imported successfully, and then click OK.
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line of a web browser. 2. Click the Administration Console tab and then click System Settings.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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 (Sun ONE) (&(objectclass=groupOfUniqueNames)) (Active Directory) (&(objectclass=group))
LDAP Role Search Filter: The format that is appropriate for the type of LDAP server you are using:
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:
property that is used as the Business Activity Monitoring login ID. 4. Click the LDAP Synchronization tab and click Test Connection to verify whether the users are imported successfully, and then click OK.
1. Start BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line of a web browser. 2. Click the Administration Console tab and then click System Settings. 3. Click the LDAP Synchronization tab and then click Synchronize Now. The time that is required to synchronize depends on your environment. A message appears when the synchronization is complete. 4. Click OK.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
If you install BAM Server after LiveCycle ES has run a process, you must populate BAM Dashboard. Populating BAM Dashboard initializes BAM Server to begin polling the LiveCycle ES database. When this process is enabled, the AdobeView can be created from the information that is gathered from the LiveCycle ES database. In the case of a clean LiveCycle ES installation, the database will be empty and no view will be created.
To populate BAM Dashboard:
1. Log in to BAM Workbench by typing http://[host name]:[port]/bam/workbench in the URL line of a web browser. 2. Click Application Workbench > Events. 3. In the Events list in the right pane, find ActivityInstanceStartedEvent and ActivityInstanceCompletedEvent. 4. Disable each event by clicking the arrow button on the Status column and selecting Disable dependencies. 5. Enable the events by clicking the arrow button in the Status column and selecting Enable all. 6. Repeat steps 3 to 5 for ProcessInstanceStartedEvent and ProcessInstanceCompletedEvent. 7. Repeat steps 3 to 5 for all remaining events except AdobeEvent, VC_SYSTEM_EVENTS, and VC_TASK_EVENTS. When BAM Dashboard has been populated, you can log in to BAM Dashboard to view the LiveCycle ES processes.
To log in to BAM Dashboard:
1. Type the URL to the dashboard in a web browser. For example, type this URL:
http://[host name]:[port]/bam/login/dashboard.htm
2. Log in as an administrator. The default administrator account for BAM Server uses the following credentials: Username: system Password: manager
Additional documentation
You can access additional information about Business Activity Monitoring in these documents:
Using Business Activity Monitoring Dashboard Business Activity Monitoring Server Reference LiveCycle Workbench ES Help
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
1. Undeploy and delete the old BAM Server EAR file using WebLogic Server Administration Console . 2. Delete all the files from the recovery log directory and logging directory that have names similar to the following patterns:
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.
1. Using a text editor, edit the WebLogic startup script. 2. Add the following properties for ConvertPdf :
Adobe PostScript and Encapsulated PostScript (EPS) files Image files, such as BMP, TIFF, PNG, and JPEG files
100
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
OpenOffice files All other file types (except HTML files), such as Microsoft Office, Photoshop, PageMaker, and FrameMaker files
The pool size for HTML-to-PDF conversions is not managed through the use of stateless session beans. The default pool size for PostScript and EPS files and for image files is set to 3, and the default pool size for OpenOffice and other file types (except HTML) is set to 1. You can configure the PS/EPS and image pool size to a different value based on your server hardware configuration, such as the number of CPUs, the number of cores within each CPU, and so on. However, it is mandatory that the pool size for the OpenOffice and other file types be left unchanged at 1 for proper functioning of PDF Generator ES. This section describes how the pool size for PS2PDF and Image2PDF can be configured for each of the supported application servers. The text that follows assumes that the following two LiveCycle ES application EARs are deployed on the application server:
adobe-livecycle-weblogic.ear adobe-livecycle-native-weblogic-[platform].ear
where [platform] should be replaced with one of the following strings, depending on your operating system:
1. Open adobe-livecycle-weblogic.ear in WinRAR. 2. Go to the following path, opening nested JAR files one after another in WinRAR: adobe-pdfg-bmc-invoker-ejb.jar > META-INF 3. Extract 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 code, go to the node that has 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. Go to stateless-session-descriptor/pool and 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. If required, repeat steps 5 and 6 for the PS2PDF pool size. The ejb-name node for PS2PDF conversions is set to PSToPDFInvoker.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
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.
Troubleshooting
This section discusses issues you may encounter when installing and deploying LiveCycle ES, and suggests steps for avoiding or working around them.
Getting help
This section describes the steps you should take prior to contacting Adobe Support. If, after reviewing the LiveCycle ES documentation, you have not resolved your issues, contact Adobe Support. To help expedite your service, have the following information available:
What were you doing when the problem occurred? Can you repeat the problem? Was an error message displayed when the problem occurred? Did you observe anything else? If you disable the Show Friendly HTTP Error Messages option in Internet Explorer (Tools > Options > Advanced), do the errors persist?
Installation considerations
If you have problems installing, configuring, or deploying LiveCycle ES, ensure that you carefully follow the instructions in these LiveCycle ES documents:
Preparing to Install LiveCycle ES Installing and Deploying LiveCycle ES document for your application server Administering LiveCycle ES
If you installed and configured everything according to the documentation, review the following sections for issues similar to those you are experiencing.
Total transaction lifetime timeout: 300 Initial heap size: 256 Maximum heap size: 1024 Mb Prepared statement cache: 100 Database connection pool maximum: IDP_DS is 30, RM_DS is 20, BAM metadata database is 20 Topics and queues connection factories maximum pool connections: 50
103
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Database initialization considerations 104
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, ensure that the following conditions exist:
The LiveCycle ES database is already created and the user has full rights to it. The database server is accessible when you ping it. The database is empty; that is, it has no tables, sequences, views, or index tables. The JNDI name for IDP_DS is created.
If initialization fails while writing to the Registry, check the application server logs for errors pertaining to the queues and topics. If errors exist, verify that the queues and topics are configured properly. Note: If, when restarting WebLogic Server 10, a JMSPool warning message appears that indicates an error occurred while making the initial connection to the JMS resource, the message can be safely ignored. The server retries the connection later. If this message persists, verify your JMS configuration setting and restart the application server.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
LiveCycle Configuration Manager log file 105
Non-clustered environments
If the JNDI URL differs from the default JNDI URL for the application server (that is, for WebLogic: t3://localhost:7001), this is the JNDI URL for the IDP_DS that is managed by your application server:
org.quartz.dataSource.idp.java.naming.provider.url To set the scheduler properties
1. Create a new file named dscscheduler.properties 2. Set the values of the above properties as necessary for the app server node, such as the following values:
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 describes error messages that are specific to LiveCycle ES and how to resolve the underlying problems.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Class not found 106
If this error occurs in either the LiveCycle Configuration Manager log or WebLogic Server Administration Console, and the resource does not appear to exist in the WebLogic Administration Console, correct the exception by following these steps.
To correct this exception:
1. Go to the [appserverdomain]/config/jms/ directory. 2. Delete the idp_jms_module_[server_name]-jms.xml file. 3. Run LiveCycle Configuration Manager and configure JMS resources again by choosing the following options:
On the Task Selection screen, select Configure Application Server. On the Application Server Configuration Selection screen, select Configure JMS.
Is the class path setting invalid or missing? Is the JAR file obsolete? Is there a compilation problem in the class?
If the expected name is not spelled correctly, you must fix the code.
To correct the most common JNDI exceptions:
1. Check the JNDI tree on the LiveCycle ES application server. Does the name used appear in the tree?
If yes, it is most likely that your code does not properly set up the InitialContext object being used for the lookup, and the lookup is being done on a JNDI tree that is not the one that the resource is listed in. See the property values to use in the Installing and Deploying LiveCycle ES document for your application server If no, continue to step 2.
2. Does the resource appear in the JNDI tree under a name other than that listed in the lookup?
If yes, you are using the wrong lookup name. Provide the correct name. If no, continue to step 3.
3. Review the application server logs during startup. If the application server is configured to make this resource available but something is going wrong, an exception is shown here. Is there an exception?
If yes, review the exception and stack trace. If the NameNotFoundException is a symptom of another problem based on your investigation of the server logs, go to the troubleshooting steps for that problem. If no, continue to step 4.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Exceptions thrown when initializing the database multiple times 107
4. If the resource is not listed in the JNDI tree, and no exception appears at startup to explain why it is not available, most likely the application server is not configured properly to make that resource available. Review the application server configuration. Is it configured to make this resource available?
If no, see the Installing and Deploying LiveCycle ES document for your application server. If yes, this is not one of the common problems that cause this issue. Contact Adobe Support.
To resolve this issue, ensure that the swap space on UNIX and Linux servers is at least 3 GB.
You must update to SQL Server 2005 JDBC driver version 1.2. Obtain this driver from the Microsoft Download Center.
1. Locate the IDP_DS-3079-jdbc.xml file in the [appserverdomain]/config/jdbc directory and open it in an editor. 2. Locate the line <jndi-name></jndi-name> and delete it.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
WebLogic JTA time-out error 108
To resolve 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 ES.
To resolve this issue, check the WebLogic Server Administration Console to ensure that it is not locked, which is indicated by the Lock & Edit button being selected. If it is locked, LiveCycle Configuration Manager shows the deployment process as 16% complete and the WebLogic Server Administration Console shows the EAR file as deployed but in an installed state. If the WebLogic Server Administration Console is not locked, LiveCycle Configuration Manager can deploy the EAR files. To resolve this issue, go to the WebLogic Server Administration Console, ensure that it is unlocked, and redeploy the EAR files.
1. Log in to the WebLogic Server Administration Console and, under Domain Structure, click Environment > Servers. 2. In the right pane, click your server, and then click the Server Start tab. 3. Click Lock & Edit and then, in the Class Path box, add the appropriate path for your server at the front of the property. For example, add this path:
C:\bea\patch_weblogic920\profiles\default\sys_manifest_classpath\ weblogic_patch.jar;
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Failure to deploy due to PermGen Space error 109
4. Click Save and then click Activate Changes. 5. Restart the WebLogic Server. 6. Verify the patch by checking the log file for the LiveCycle ES server, such as C:\bea\user_projects\ domains\base_domain\servers\server1\logs\server1.log. A log message similar to the following message 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 >
To resolve this issue, increase the PermGen space from 256 to 512. You can change this value from the WebLogic Server Administration Console.
To resolve this issue, ensure that the Document MaxInlineSize parameter is set to a value that is smaller than the IIOP message size parameter defined in WebLogic Server.
1. Log in to the WebLogic Server Administration Console and, under Domain Structure, click Environment > Servers. 2. In the right pane, click your server, and then click the Server Start tab. 3. Click Lock & Edit. 4. In the left pane, click [domain name]and, in the right pane, click the JTA tab. 5. In the Timeout Seconds box, type 300 (or higher).
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
CORBA COMM_FAILURE exception 110
The value in bold is a colon-delimited list of the time-out values in milliseconds that should be set according to your system requirements. The values from left to right are as follows:
Initial wait time if a transport TCP read returns 0 bytes Maximum cumulative wait time if a transport TCP read returns 0 bytes Maximum cumulative wait time if a transport TCP read of a GIOP header returns 0 bytes Backoff percentage used to compute the amount of time to wait on a subsequent transport TCP read of 0 bytes
If this occurs, add the following entry to the [DMAPI_CONFIGURATION] section of the dmcl.ini file:
'local_clean_on_init=F'
On a Windows server, by default the dmcl.ini file is located in the [Windows Installation Drive]\WINDOWS folder. Restart the LiveCycle ES server for this change to take affect.
Go to [appserverdomain] and open startWeblogic.cmd in an editor. Locate [JAVA_HOME] and add the following parameter:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Deploying LiveCycle ES in a distributed environment 111
Note: LiveCycle Configuration Manager does not support using and admin erver if amanaged server is not configured.
1. Exit LiveCycle Configuration Manager. 2. Manually deploy the EAR files.(See Manually Deploying to WebLogic Server on page 45.) 3. Run LiveCycle Configuration Manager and select the tasks only after you deploy LiveCycle ES EAR files.
1. Start the registry editor by selecting Start > Run and, in the Open box, type regedit, and then click OK. 2. Go to the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. In the right pane of the registry editor, look for the TcpTimedWaitDelay value name. If the name does not appear, select Edit > New > DWORD Value to add it. 4. In the name box, type TcpTimedWaitDelay. 5. If you do not see an insertion point and New Value # inside the box, right-click inside the right panel, select Rename from the menu and then, in the name box, type TcpTimedWaitDelay. 6. Repeat steps 4 and 5for the following value names: MaxUserPort, MaxHashTableSize, and MaxFreeTcbs. 7. Double-click inside the right pane to set the TcpTimedWaitDelay value; under Base, select Decimal and, in the Value box, type 30. 8. Double-click inside the right pane to set the MaxUserPort value; under Base, select Decimal and, in the Value box, type 65534. 9. Double-click inside the right pane to set the MaxHashTableSize value; under Base, select Decimal and, in the Value box, type 65536.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Troubleshooting
Could not start/create deployment errors on Solaris 112
10. Double-click inside the right pane to set the MaxFreeTcbs value; under Base, select Decimal and, in the Value box, type 16000. Caution: Serious problems may occur if you modify the registry incorrectly by using Registry Editor or by another method. These problems may require that you reinstall your operating system. Modify the registry at your own risk.
Microsoft has documented the required steps in a knowledgebase article on the Microsoft Help and Support site.
In Visio 2007, click Tools > Trust Center > Macro Settings and select either of the following options and then click OK:
Installing LiveCycle ES on page 113 Error logs on page 118 Next steps on page 118
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 19 or Appendix - LCM Command Line Interface on page 119. 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 install CLI and LiveCycle Configuration Manager.
To install LiveCycle ES:
1. Open a command prompt and navigate to the /livecycle_server/8.2 directory of the installation media. 2. Run the following command on a single line:
(Windows)win_livecycle8_setup.exe -cp:p stage.jar -console; ..\..\third_party\jdbc\mysql-connector-java-3.1.12-bin.jar run -console (Linux) ./linux_livecycle8_setup.bin -cp:p stage.jar -console (UNIX) ./solaris_livecycle8_setup.bin -cp:p stage.jar -console
Note: Specify the following additional arguments to redirect the LiveCycle ES installer temporary directory to an alternate, non-default location:
-cp:p stage.jar -is:tempdir [path to alternate temporary directory]
113
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Prompt Select a language to be used for this wizard. [X] 1 - English [ ] 2 - French [ ] 3 - German [ ] 4 - Japanese To select an item, enter its number, or [0] when you are finished: [ ] Adobe LiveCycle ES Welcome to Adobe LiveCycle ES The installation wizard will install Adobe LiveCycle ES (Enterprise Suite) server version 8.2. To continue, choose Next. Adobe LiveCycle ES Adobe Systems Incorporated http://www.adobe.com/products/livecycle/ Press 1 for Next, 3 to Cancel, or 5 to Redisplay [1] Adobe LiveCycle ES Adobe LiveCycle ES Install Location Please specify a directory or press Enter to accept the default directory. Destination Directory For Windows is [C:\Adobe\LiveCycle8.2] Destination Directory for Unix/Linux is [/opt/adobe/livecycle8.2]
Description Select the language for the installation to use by entering a value between 1 and 4. The selection will then be displayed in brackets ([X]). Enter [0] when you finish selecting a language.
On the Destination screen, press Enter to accept the default directory or type the new installation directory location. Note: If you type the name of a directory that does not exist, it will be created for you. Caution: When you install the solution components, you can specify a different installation location. If you are installing on Linux or UNIX, the directory you specify should not contain any spaces; if it does, the installation program does not install the solution component. Enter 1 to continue the installation. Enter a serial number. The components that you are licensed for will be displayed.
Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to Redisplay [1] Adobe LiveCycle ES Serial Number [ ]
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Prompt [ ] 1 - Add [ ] 2 - Clear [X] 3 - Finish To select an item enter its number, or 0 when you are finished: [0]
Description If you have licensed multiple solution components, enter 1 to add another serial number. You will then be prompted for another serial number as in the previous step. Repeat this step for each serial number that you have. Enter 0 when you finish entering serial numbers. Note: To reset the serial number, enter 2.
Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to Redisplay [1] Adobe LiveCycle ES Note: This prompt is only provided for Windows. Type of Installation Please choose from the following options: [ ] 1 - Turnkey The turnkey installation automatically performs all of the tasks required to install and configure LiveCycle ES components on a single (non-clustered) WebLogic Application Server running on Windows with a preconfigured MySQL database. [ ] 2 - Manual The manual method lets you install the files and then run LiveCycle Configuration Manager to configure the EAR file and other components. However, you must manually install, configure, and start your application server as well as create and configure the database before running LiveCycle Configuration Manager and deploying to the application server. To select an item enter its number, or 0 when you are finished: [ ] Note: This prompt is only provided for Windows. Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [ ] Press ENTER to read the text [Type q to quit] Please choose from the following options: [ ] 1 - I accept the terms of the license agreement. [X] 2 - I do not accept the terms of the license agreement. To select an item enter its number, or 0 when you are finished: [0]
Enter 1 to continue the installation. Select an installation type. By default, Turnkey installation is selected. Enter 0 when you are have made your selection.
The Product License Agreement will display. Press enter to read the agreement. If you agree with the terms of the Product License Agreement, enter 1. Enter [0] when you are done with the Product License Agreement.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Prompt Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] Adobe LiveCycle ES Java SE SDK Location Select the location of your Java SDK. Version 1.5.0 or later is required. Browse... [ ] C:\Program Files\Java\jdk1.5.0_11 Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] Adobe LiveCycle ES LiveCycle PDF Generator ES Native Application Support LiveCycle PDF Generator ES can convert Microsoft Office Word, Adobe Photoshop, AutoCAD, and other native application files to Adobe PDF. Please choose from the following options: For detailed information about native application support, please see the documentation. [ ] 1 - Yes, enable native application support for LiveCycle PDF Generator ES [X] 2 - No, do not enable native application support for LiveCycle PDF Generator ES (select this option for clustered deployments) To select an item enter its number, or 0 when you are finished: [ ] Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] Adobe LiveCycle ES MySQL will be installed to use the following available port. To override this selection, enter a different port number and click Test to verify the port is available. Port: [3306] Port: [3306] [ ] 1 - Test [ ] 2 - Reset [X] 3 - Finish To select an item enter its number, or 0 when you are finished: [0]
Description Enter 1 to continue the installation. Type a new Java SE SDK directory location or press enter to accept the default directory. Note: This prompt is only provided for Windows. Press enter to continue the installation. (PDF Generator ES for Windows Only) If you enter 1 to enable native application support for PDF Generator ES, the software will check the version of Adobe Acrobat you have installed. If you do not have Acrobat installed, accept the prompt to install Acrobat 9.0 now. If you are installing in a clustered environment, enter 2 and do not enable native application support for PDF Generator ES. Enter [0] when you are done making your selection.
Press Enter to continue the installation. Press Enter to accept the default port number or type a new port number. Note: This prompt is only provided for Windows. To test the port number, enter 1 and then enter 3 to finish. A message will display the result of the test. To reset the port number to the default value, enter 2. Enter 0 when you have completed selecting and testing port numbers. Note: This prompt is only provided for Windows.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Prompt The password entered gives full access to all functionality of the database. MySQL adobe/root User Password Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] Adobe LiveCycle ES Pre-installation Summary Please read the summary information below. Adobe LiveCycle ES will be installed in the following location: /opt/adobe/livecycle8.2 With the following features:
Description Enter a unique database password. Note: This prompt is only provided for Windows. Enter 1 to continue the installation. Press 1 to install LiveCycle ES. Pre-installation summary -> Please read the summary information. LiveCycle ES will be installed in the following location with the following features.The installation progress will display. Note: The installation location and solution components specified will vary depending on your license key and your specified installation directory.
Adobe LiveCycle Foundation Adobe LiveCycle Configuration Manager LiveCycle ES SDK Adobe LiveCycle Forms ES Adobe LiveCycle Reader Extensions ES Adobe LiveCycle Process Management ES Adobe LiveCycle ES Business Activity Monitoring Adobe LiveCycle Output ES Adobe LiveCycle Rights Management ES Adobe LiveCycle Digital Signatures ES Adobe LiveCycle PDF Generator ES Adobe LiveCycle PDF Generator 3D ES Adobe LiveCycle Barcoded Forms ES Adobe LiveCycle ES Connector for IBM FileNet Adobe LiveCycle ES Connector for EMC Documentum Adobe LiveCycle ES Connector for IBM Content Manager
Press ENTER to read the text. Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Prompt Press ENTER to read the test (Type q to quit). Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] Please choose from the following options: [X] 1 - Start LiveCycle Configuration Manager. [ ] 2 - Not Start LiveCycle Configuration Manager. To select an item enter its number, or 0 when you are finished: [0] Press 3 to Finish or 5 to Redisplay [3]
Post Installation Details are displayed. Enter 1 to start LiveCycle Configuration Manager or 2 and then [0] to end the installation.
Error logs
If an error occurs, you can review the adobe_lc8.2_server_install.log in the system temporary directory (TEMP or TMP). For information about errors that may occur during the installation, see Troubleshooting on page 103.
Next steps
You must now configure LiveCycle ES for deployment. (See Configuring LiveCycle ES for Deployment on page 19 or Appendix - LCM Command Line Interface on page 119.)
Order of operations
The LiveCycle Configuration Manager CLI must follow the same order of operations as the GUI version of LiveCycle Configuration Manager. Ensure that you use the CLI operations in this order: 1. Configure LiveCycle ES. 2. Configure the Application Server. 3. Deploy LiveCycle ES. 4. Initialize LiveCycle ES. 5. Initialize LiveCycle ES Business Activity Monitoring. 6. Deploy LiveCycle ES Components. Caution: You must restart your WebLogic Server after you complete your LiveCycle Configuration Manager CLI operations.
119
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Common properties
The common properties are as follows: WebLogic specific properties: Required for the Configure the Application Server, Deploy LiveCycle, Validate Application Server Topology and Validate Application Server Configurations operations. LiveCycle Server specific properties: Required for the Initialize LiveCycle and Deploy LiveCycle Components operations. The properties in the table are required for following operations:
targetServer.name targetServer.adminHost
targetServer.adminPort
Integer
targetServer.adminUserID
String
targetServer.adminPassword
String
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Property localServer.appServerRootDir
Values Default: (Windows on WebLogic Server 9.2) C:\bea\weblogic92 (Windows on WebLogic Server 10.0) C:\bea\wlserver_10.0 (Linux, Solaris on WebLogic Server 9.2) /opt/bea/weblogic92 (Linux, Solaris on WebLogic Server 10.0) /opt/bea/wlserver_10.0 (AIX on WebLogic Server 9.2) /usr/bea/weblogic92 (AIX on WebLogic Server 10.0) /usr/bea/wlserver_10.0
Description The root directory of the application server instance that you are configuring locally (that you plan to deploy LiveCycle ES to or that you will use to communicate with a remote server that you plan to deploy LiveCycle ES to)
targetServer.appServerRootDir
Default: (Windows on WebLogic Server 9.2) C:\bea\weblogic92 (Windows on WebLogic Server 10.0) C:\bea\wlserver_10.0 (Linux, Solaris on WebLogic Server 9.2) /opt/bea/weblogic92 (Linux, Solaris on WebLogic Server 10.0) /opt/bea/wlserver_10.0 (AIX on WebLogic Server 9.2) /usr/bea/weblogic92 (AIX on WebLogic Server 10.0) /usr/bea/wlserver_10.0
The root directory of the application server instance you are configuring on a remote server (that you plan to deploy LiveCycle ES to)
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
LCPort excludedSolutionComponents
Integer Choose a value: String. Values include: ALC-LFS-Forms, ALC-LFS-BusinessActivityMonito ring, ALC-LFS-ConnectorEMCDocume ntum, ALC-LFS-ConnectorIBMFileNet, ALC-LFS-ConnectorIBMContent Manager, ALC-LFS-ContentServices, ALC-LFS-DigitalSignatures, ALC-LFS-DataCapture, ALC-LFS-Output, ALC-LFS-PDFGenerator, ALC-LFS-PDFGenerator3D, ALC-LFS-ProcessManagement, ALC-LFS-ReaderExtensions, ALC-LFS-RightsManagement
customerFontsDir
String
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Property systemFontsDir
Values String
Description Location of the system fonts directory. Multiple system fonts locations can be entered using a semicolon as separator. These paths must be accessible from the server being deployed to.
LCTempDir
String
Location of the temporary directory. This path must be accessible from the server being deployed to. The global document storage (GDS) root directory. Specify a path to an NFS shared directory used to store long-lived documents and to share them among all cluster nodes. Specify this property only when deploying LiveCycle ES products in a clustered environment. This path must be accessible from the server being deployed to.
LCGlobalDocStorageDir
String
enableFIPS
Enabling the Federal Information Processing Standards (FIPS) option restricts data protection to FIPS 140-2 approved algorithms using the RSA BSAFE Crypto-J 3.5.2 encryption module with FIPS 140-2 validation certificate #590. Set this value to true only if you require FIPS to be enforced. Required if you are configuring LiveCycle Content Services ES only. Specify the root directory used by Content Services ES.
contentServices.rootDir
String
contentServices.targetWLVersion
Required if you are configuring LiveCycle Content Services ES only. Specify the version of WebLogic Server used.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Configure Application Server Validate Application Server Topology Validate Application Server Configurations Validate Database Connectivity
Note: You must configure the WebLogic specific properties section. For more information, see Common properties on page 120. Property jvm.initialHeapSize Values Default: 512 jvm.maxHeapSize Default: 1024 Description The initial heap size, in MB, for the JVM The maximum heap size, in MB, for the JVM
jms.MEClusterName classpath.targetServer.javaHom e
String String
(Cluster only) The JMS ME cluster name Configuration of target application server requires the location of the JAVA_HOME that is used to run the target application server. This path must be accessible from the server being configured.
classpath.targetServer.pop3Jar Path
String
Path to the Pop3 JAR file that is accessible to the target application server. This path must be accessible from the server being configured.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Property datasource.dbType
datasource.dbName datasource.dbHost
String String
The name of the database The host name or IP address of the server where the database is located The database port LiveCycle ES will use when communicating with the database The user ID LiveCycle ES will use when accessing the database The password associated with the database user ID JDBC driver in the application server lib directory. This path must be valid and accessible from the server being configured. Local JDBC driver. This value is used for testing direct database connection.
datasource.dbPort
Integer
datasource.local.driverPath
String
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Note: LiveCycle ES Business Activity Monitoring is an optional solution component with LiveCycle ES. Property BAMHost Values String Description The host name of the server where Business Activity Monitoring is deployed and running The port number BAM Server uses to listen for requests The Business Activity Monitoring administrator user ID to use when connecting to BAM Server The Business Activity Monitoring administrator password to use when connecting to BAM Server The type of database LiveCycle ES is using to capture Business Activity Monitoring data
BAMPort BAMAdminUserID
Integer String
BAMAdminPassword
String
databaseType
Deploy LiveCycle Components Validate LiveCycle Component Deployment Validate LiveCycle Server
Note: You must configure the LiveCycle Server Information section. (See Common properties on page 120.) Property LCAdminUserID Values String Description The user ID to assign to the LiveCycle administrator user. This User ID is used to log in to LiveCycle Administration Console. The password to assign to the LiveCycle administrator user. This password is used to log in to LiveCycle Administration Console.
LCAdminPassword
String
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
where:
-f [propertyFile] is a property file containing the required arguments. For more information on creating a property file, see Command line interface property file on page 119.
where:
-targetServer_AdminPassword [password]: Allows you to set the administrator password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file. -f [propertyFile] : A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119.
-skip [configurationsToSkipList]: This is an optional parameter which allows you to list the application server components you do not want to configure. Specify the excluded components in a comma separated list. Valid options are JMS, Datasource, or Core.
where:
-f [propertyFile]: A property file containing the required arguments. For more information
on creating a property file, see Command line interface property file on page 119.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
initializeLiveCycle -f [propertyFile]
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119.
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119.
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119. -targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119. -targetServer_AdminPassword [password]: Allows you to set the administrator password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.
where:
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119. -datasource_dbPassword [password]: Allows you to set the database user password on the command line. If this argument is present, it will override the datasource.dbPassword property in the property file.
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119. -targetServer_AdminPassword [password]: Allows you to set the administrator password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119. -targetServer_AdminPassword [password]: Allows you to set the administrator password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.
where:
-f [propertyFile]: A property file containing the required arguments. For instructions on creating a property file, see Command line interface property file on page 119. -targetServer_AdminPassword [password]: Allows you to set the administrator password
on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.
Adobe LiveCycle ES
Installing and Deploying LiveCycle ES for WebLogic
Examples usage
From the C:\Adobe\LiveCycle8.2\configurationManager\bin, type:
./configurationManagerCLI ConfigureLiveCycle -f cli_propertyFile.txt
Error logs
If an error occurs, you can review the CLI error logs located in the [LiveCycleES root]\configurationManager\log folder. The log file generated has a naming convention such as lcmCLI.0.log where the number in the file name (0) increments when the log files are rolled over.
Next steps
If you used LiveCycle Configuration Manager CLI to configure and deploy LiveCycle ES, you can now do the following tasks:
Verify the deployment. (See Final setup for LiveCycle Rights Management ES on page 61.) Access LiveCycle Administration Console. (See Accessing LiveCycle Administration Console on page 49.) Configure LiveCycle ES solution components to access LDAP. (See Configuring LiveCycle ES to access LDAP on page 61.) Uninstall LiveCycle ES. (See Uninstalling LiveCycle ES on page 84.)
If you did not configure your application server for deployment, you must now configure your application server. (See Manually Configuring WebLogic Server on page 27.)