Installing and Configuring LiveCycle for WebSphere

Installing and Configuring LiveCycle for WebSphere
bc
Installing and Configuring
LiveCycle for WebSphere
Adobe® LiveCycle™
March 2008
Version 7.2
© 2008 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle™ 7.2 Installing and Configuring LiveCycle for WebSphere® for Microsoft® Windows®, Linux®, and UNIX®
Edition 1.4, March 2008
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names and company logos in sample material or in the sample forms included in this software are for
demonstration purposes only and are not intended to refer to any actual organization.
Adobe, the Adobe logo, Acrobat, Kozuka Gothic, Kozuka Mincho, LiveCycle, Minion, Myriad, PhotoShop, PostScript, and Reader are either
registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
BEA WebLogic Server is a registered trademark of BEA Systems, Inc.
IBM, AIX, DB2, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel and Pentium are registered trademarks of Intel Corporation in the U.S. and other countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
MacIntosh is a trademark of Apple Computer, Inc., registered in the United States and other countries.
Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc. in the United States and other countries.
Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.
Red Hat and JBoss are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
Sun, Java, JavaScript, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. Products bearing
SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
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 software is based in part on the work of the Independent JPEG Group.
Portions copyright 1992, 1993 Simmule Turner and Rich Salz. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Portions Copyright (C) 1991, 1999 Free Software Foundation, Inc. The JBOSS, OmniORB, and JacORB libraries are licensed under the GNU
Library General Public License, a copy of which is included with this software.
This product contains either BISAFE and/or TIPEM software by RSA Data Security, Inc.
This product includes software developed by Brian M. Clapper [email protected]
Portions of this code are licensed from Apple Computer, Inc. under the terms of the Apple Public Source License, Version 2. The source code
version of these portions and the license are available at http://www.opensource.apple.com/apsl/.
Portions based in part on the work of the FreeType team.
Powered by Celequest. Contains technology distributed under license from Celequest Corporation. Copyright 2005 Celequest Corporation.
All rights reserved.
This product includes software developed by the Jaxen Project (http://www.jaxen.org/).
This Program was written with MacApp®: ©1985-1988 Apple Computer, Inc. APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER,
EITHER EXPRESS OR IMPLIED, REGARDING THIS PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS
FOR ANY PARTICULAR PURPOSE. The MacApp software is proprietary to Apple Computer, Inc. and is licensed to Adobe for distribution only
for use in combination with Adobe software.
Portions licensed under the Mozilla Public License Version 1.1, available at www.mozilla.org. Software distributed under the License is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language
governing rights and limitations under the License.
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
Preface ........................................................................................................................................ 10
What’s in this guide? ...................................................................................................................................................................10
Who should read this guide? ...................................................................................................................................................10
Conventions used in this guide...............................................................................................................................................10
Related documentation .............................................................................................................................................................11
Updated LiveCycle product information.......................................................................................................................12
1
Before You Install ...................................................................................................................... 13
About the installation, configuration, and deployment process................................................................................13
Starting and stopping WebSphere..................................................................................................................................14
Accessing WebSphere Administrative Console..........................................................................................................14
Viewing the JVM system output and error logs..........................................................................................................15
Methods for installing, configuring, and deploying LiveCycle products.................................................................15
Upgrading LiveCycle products................................................................................................................................................16
About Watched Folder installation........................................................................................................................................16
System requirements..................................................................................................................................................................16
Supported software ..............................................................................................................................................................16
Platform and software combinations .............................................................................................................................18
Minimum hardware requirements ..................................................................................................................................19
Additional requirements for LiveCycle PDF Generator Elements and
LiveCycle PDF Generator Professional .....................................................................................................................19
Additional requirements for LiveCycle PDF Generator for PostScript................................................................20
Installation, configuration, and deployment checklists .................................................................................................20
Automatic installation and deployment checklist.....................................................................................................20
Manual installation and deployment checklist ...........................................................................................................21
Updated LiveCycle product information.......................................................................................................................22
2
Installing LiveCycle Products.................................................................................................... 23
Installing LiveCycle PDF Generator........................................................................................................................................23
Configuring JVM for LiveCycle PDF Generator on WebSphere 6.1......................................................................25
Installing LiveCycle products ...................................................................................................................................................26
Installing LiveCycle Print............................................................................................................................................................28
Installing Watched Folder .........................................................................................................................................................29
Viewing the error log ..................................................................................................................................................................29
Next steps........................................................................................................................................................................................29
3
Preparing Your Environment.................................................................................................... 30
Creating the database ................................................................................................................................................................30
Creating an Oracle database..............................................................................................................................................30
Creating a DB2 database .....................................................................................................................................................31
Configuring a DB2 database for concurrent usage ...................................................................................................32
Creating a SQL Server database........................................................................................................................................33
Installing JTA stored procedures................................................................................................................................33
Enabling XA transactions for Windows Server 2003...........................................................................................34
Preparing the application server ............................................................................................................................................35
Installing WebSphere Application Server .....................................................................................................................35
Creating an application server instance ........................................................................................................................36
4
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Contents
5
Creating an endorsed directory........................................................................................................................................37
Configuring the shared libraries.......................................................................................................................................37
Increasing the SOAP time-out .................................................................................................................................................38
Updating the web server configuration files .....................................................................................................................39
Preparing WebSphere MQ ........................................................................................................................................................39
Installing the required software .......................................................................................................................................39
Configuring WebSphere MQ .............................................................................................................................................42
Installing database drivers ........................................................................................................................................................44
Next step..........................................................................................................................................................................................45
Part I: Automatic Configuration and Deployment
4
Automatically Configuring LiveCycle Products ...................................................................... 47
About Configuration Manager ................................................................................................................................................47
Configuration tasks ...............................................................................................................................................................47
Configuration modes............................................................................................................................................................48
Running Configuration Manager more than once ....................................................................................................48
Determining the application server SOAP port.................................................................................................................49
Performing a typical configuration........................................................................................................................................49
Performing a custom configuration ......................................................................................................................................53
Configuring and assembling LiveCycle products ......................................................................................................54
Changing the application server settings .....................................................................................................................57
Validating application server settings............................................................................................................................60
Automatically deploying LiveCycle products..............................................................................................................60
Initializing the database ......................................................................................................................................................62
Verifying deployed LiveCycle products .........................................................................................................................63
Enabling XA for LiveCycle PDF Generator connection factories.................................................................................64
Uninstalling EAR files ..................................................................................................................................................................64
Next step..........................................................................................................................................................................................65
5
Post-deployment ....................................................................................................................... 66
Accessing Administrator............................................................................................................................................................66
Accessing User Management ..................................................................................................................................................67
LiveCycle Assembler post-deployment tasks ....................................................................................................................67
Verifying the LiveCycle Assembler deployment.........................................................................................................67
LiveCycle Forms post-deployment tasks .............................................................................................................................68
Verifying the LiveCycle Forms deployment .................................................................................................................68
LiveCycle Print post-deployment tasks ................................................................................................................................69
Verifying deployment...........................................................................................................................................................69
Deploying and running the PrintIVS web application..............................................................................................69
Running the Print Submitter application ......................................................................................................................70
Running the Form Server Module API Print application..........................................................................................71
LiveCycle Form Manager post-deployment tasks ............................................................................................................71
Accessing the LiveCycle Form Manager end-user pages........................................................................................71
LiveCycle PDF Generator post-deployment tasks ............................................................................................................72
Setting up job sources .........................................................................................................................................................72
Setting Adobe PDF Printer as the default printer ......................................................................................................72
Installing fonts.........................................................................................................................................................................72
Setting the LiveCycle PDF Generator conversion time-out....................................................................................73
Next Step .........................................................................................................................................................................................74
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Contents
6
Part II: Manual Configuration, and Deployment
6
Configuring LiveCycle Products for Deployment ................................................................... 76
Next step..........................................................................................................................................................................................79
7
Manually Configuring WebSphere 5.1.1.5 .............................................................................. 80
Disabling the CORBA time-out..........................................................................................................................................80
Configuring the JVM arguments ......................................................................................................................................81
Configuring the server transaction time-out...............................................................................................................81
Updating the web server configuration files ...............................................................................................................81
Connecting WebSphere to the LiveCycle database ........................................................................................................82
Configuring Oracle 9i or Oracle 10g................................................................................................................................82
Configuring DB2 ....................................................................................................................................................................83
Configuring SQL Server .......................................................................................................................................................85
Configuring embedded messaging or WebSphere MQ ................................................................................................86
Configuring JMS resources for WebSphere with embedded messaging..........................................................86
Configuring JMS resources for WebSphere MQ .........................................................................................................93
Configuring JMS resources ..........................................................................................................................................93
Creating WebSphere MQ topic destinations.........................................................................................................95
Configuring WebSphere MQ JMS provider for Watched Folder ................................................................. 100
Checking your WebSphere MQ configuration ......................................................................................................... 101
Next step....................................................................................................................................................................................... 101
8
Manually Configuring WebSphere 6.0.2.9 ............................................................................103
Disabling the CORBA time-out ............................................................................................................................................. 103
Configuring the JVM arguments ......................................................................................................................................... 104
Configuring the server transaction time out................................................................................................................... 104
Configuring the data source for WebSphere 6.0.2.9 .................................................................................................... 104
Configuring the Oracle data source ............................................................................................................................. 105
Configuring the DB2 data source.................................................................................................................................. 106
Configuring the SQL Server data source .................................................................................................................... 107
Configuring embedded messaging ................................................................................................................................... 108
Next step....................................................................................................................................................................................... 115
9
Manually Deploying to WebSphere 5.1.1.5...........................................................................116
About deploying LiveCycle products................................................................................................................................. 116
WebSphere directory name ............................................................................................................................................ 116
Summary of deployable components......................................................................................................................... 116
Deploying to WebSphere....................................................................................................................................................... 117
Starting the application .......................................................................................................................................................... 119
Verifying the LiveCycle Forms deployment..................................................................................................................... 119
Viewing log files......................................................................................................................................................................... 120
Next step....................................................................................................................................................................................... 120
10 Manually Deploying to WebSphere 6.0.2.9...........................................................................121
About deploying LiveCycle products................................................................................................................................. 121
WebSphere directory name ............................................................................................................................................ 121
Summary of deployable components......................................................................................................................... 122
Deploying to WebSphere....................................................................................................................................................... 122
Starting the application .......................................................................................................................................................... 124
Verifying the LiveCycle Forms deployment..................................................................................................................... 124
Viewing log files......................................................................................................................................................................... 125
Next step....................................................................................................................................................................................... 125
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Contents
7
11 Initializing the Database .........................................................................................................126
Next step....................................................................................................................................................................................... 127
Part III: Post-Deployment Configuration
12 Configuring LiveCycle Products to Access LDAP ..................................................................129
Configuring LiveCycle products with LDAP .................................................................................................................... 129
Configuring LiveCycle products with LDAPS .................................................................................................................. 130
13 Configuring SSL on WebSphere .............................................................................................131
Creating a local user account................................................................................................................................................ 131
Creating an SSL Credential .................................................................................................................................................... 132
Configuring WebSphere to use local OS registry instead of LDAP ......................................................................... 134
Configuring the WebSphere connection time-out....................................................................................................... 134
Configuring SSL on WebSphere........................................................................................................................................... 134
Next step....................................................................................................................................................................................... 137
Part IV: Additional LiveCycle Workflow Configuration
14 Configuring WebSphere 5.1.1.5 for BAM Server...................................................................139
Creating the BAM metadata database .............................................................................................................................. 139
User accounts ....................................................................................................................................................................... 139
Creating environment variables for DB2.................................................................................................................... 139
Configuring WebSphere for BAM Server .......................................................................................................................... 140
Installing database drivers for BAM Server................................................................................................................ 140
Configuring the connection to the BAM metadata database ............................................................................ 141
Creating a JAAS authentication alias for the BAM metadata database on DB2 .................................... 141
Creating the JDBC provider for the BAM metadata database...................................................................... 141
Creating the data source for the BAM metadata database........................................................................... 142
Testing the database connection ........................................................................................................................... 143
Creating the integration data source .......................................................................................................................... 143
Testing the database connection ........................................................................................................................... 145
Configuring WebSphere parameters........................................................................................................................... 145
Optional WebSphere JVM parameters........................................................................................................................ 147
Creating a virtual host alias ............................................................................................................................................. 147
Deploying BAM Server to WebSphere............................................................................................................................... 148
Next Step ...................................................................................................................................................................................... 150
15 Configuring WebSphere 6.0.2.9 for BAM Server...................................................................151
Creating the BAM metadata database .............................................................................................................................. 151
User accounts ....................................................................................................................................................................... 151
Creating environment variables for DB2.................................................................................................................... 151
Configuring WebSphere for BAM Server .......................................................................................................................... 152
Installing database drivers for BAM Server................................................................................................................ 152
Configuring the connection to the BAM metadata database ............................................................................ 152
Creating a JAAS authentication alias for the BAM metadata database on DB2 .................................... 153
Creating the JDBC provider for the BAM metadata database...................................................................... 153
Creating the data source for the BAM metadata database........................................................................... 154
Testing the database connection ........................................................................................................................... 156
Creating the Integration data source .......................................................................................................................... 156
Testing the Integration database connection.................................................................................................... 157
Configuring WebSphere parameters........................................................................................................................... 157
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Contents
8
Optional WebSphere JVM parameters........................................................................................................................ 159
Deploying BAM Server to WebSphere ........................................................................................................................ 160
Next Step ...................................................................................................................................................................................... 163
16 Getting Started with BAM Server ...........................................................................................164
Configuring LiveCycle Workflow Server for BAM Server............................................................................................. 164
Accessing BAM Workbench and BAM Dashboard ....................................................................................................... 164
Configuring BAM Server ......................................................................................................................................................... 165
Configuring the SMTP settings ...................................................................................................................................... 165
Importing LiveCycle Workflow metadata definitions............................................................................................ 166
Starting the JDBC agent ................................................................................................................................................... 166
Configuring LDAP settings for BAM Server ............................................................................................................... 167
Limitations of BAM Server LDAP connectivity ................................................................................................... 167
Best practices for BAM Server LDAP connectivity............................................................................................. 167
Configuring automatic LDAP synchronization .................................................................................................. 168
Configuring LDAP user mapping............................................................................................................................ 169
Configuring LDAP role mapping............................................................................................................................. 170
Manually synchronizing with the LDAP server .................................................................................................. 171
Next steps..................................................................................................................................................................................... 171
17 Installing LiveCycle Workflow Designer ................................................................................172
Installing LiveCycle Workflow Designer ........................................................................................................................... 172
Connecting to application servers using non-default ports...................................................................................... 173
Uninstalling LiveCycle Workflow Designer...................................................................................................................... 174
Next steps..................................................................................................................................................................................... 174
A
Supported Platform and Software Combinations ................................................................175
B
Fonts Installed with the Font Manager Module ....................................................................179
C
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder ...............180
Summary of tasks ...................................................................................................................................................................... 180
Deploying QPACs and creating a workflow process .................................................................................................... 181
Using dynamic or static DDX files ................................................................................................................................. 181
Configuring an Assembler QPAC in a workflow process...................................................................................... 182
Creating and configuring a watched folder .................................................................................................................... 184
Creating a JobConfig.xml file................................................................................................................................................ 185
Preparing PDF and DDX files................................................................................................................................................. 187
Submitting the LiveCycle Assembler job for processing............................................................................................ 188
D
Developing Forms for LiveCycle.............................................................................................189
Publishing files from client software.................................................................................................................................. 189
Designing forms for LiveCycle products........................................................................................................................... 189
Using dynamic forms with LiveCycle products........................................................................................................ 190
Embedding fonts in PDF/A-compliant forms ........................................................................................................... 190
E
Uninstalling LiveCycle Products.............................................................................................191
Removing the product files ................................................................................................................................................... 191
F
Upgrading LiveCycle Products to Version 7.2 or 7.2.1 .........................................................192
Upgrade guidelines .................................................................................................................................................................. 192
Updating your application server ................................................................................................................................. 193
Using automatic or turnkey installations for upgrading ...................................................................................... 193
Configuring using Configuration Manager during the upgrade process ...................................................... 193
Summary of manual upgrade process............................................................................................................................... 193
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Contents
9
LiveCycle Forms and LiveCycle Print.................................................................................................................................. 194
Upgrading from Adobe Form Server 6.0 to LiveCycle Forms 7.2 ...................................................................... 194
LiveCycle Forms and LiveCycle Print 7.x to LiveCycle Forms and LiveCycle Print 7.2 ...................................... 195
LiveCycle Form Manager ........................................................................................................................................................ 198
LiveCycle Assembler, LiveCycle Workflow, and Watched Folder............................................................................. 200
LiveCycle Workflow Designer ............................................................................................................................................... 203
BAM Server for LiveCycle Workflow ................................................................................................................................... 203
About the BAM Server upgrade utility ........................................................................................................................ 204
LiveCycle PDF Generator ........................................................................................................................................................ 205
LiveCycle Document Security ............................................................................................................................................... 208
LiveCycle Reader Extensions ................................................................................................................................................. 210
LiveCycle Policy Server ............................................................................................................................................................ 213
G
Enhancing Server Performance ..............................................................................................215
Optimizing inline documents and impact on JVM memory...................................................................................... 215
Increase the maximum memory allocated to the JVM................................................................................................ 216
Cleaning up temporary files in the Global storage directory .................................................................................... 217
DB2 configuration settings .................................................................................................................................................... 217
Improving Windows Server Performance with LDAP .................................................................................................. 217
Index .........................................................................................................................................219
Preface
This guide is one of several resources available to help you learn about the Adobe® LiveCycle™ suite of
products. LiveCycle products help automate and accelerate the flow of business-critical information to and
from customers, partners, constituents, and employees.
What’s in this guide?
This guide provides information about how to install and configure the following LiveCycle products on
Microsoft® Windows®, Linux®, IBM® AIX®, and Sun™ Solaris™, and how to deploy the products to a IBM
WebSphere® Application Server:
●
Adobe LiveCycle Assembler 7.2.1
●
Adobe LiveCycle Forms 7.2
●
Adobe LiveCycle Form Manager 7.2
●
Adobe LiveCycle PDF Generator 7.2 Professional, LiveCycle PDF Generator 7.2 Elements, and
LiveCycle PDF Generator 7.2 for PostScript®
●
Adobe LiveCycle Print 7.2
●
Adobe LiveCycle Workflow 7.2.1
This guide also provides information about how to install and configure Watched Folder 1.1.
Who should read this guide?
This guide provides information for administrators or developers responsible for installing, configuring,
administering, or deploying LiveCycle products. The information provided is based on the assumption that
anyone reading this guide is familiar with application servers, Linux, Windows, AIX, or Solaris operating
systems, MySQL, Oracle®, DB2®, or SQL Server database servers, and web environments.
Conventions used in this guide
This guide uses the following naming conventions for common file paths.
Name
Default value
Description
[LiveCycle root]
Windows:
C:\Adobe\LiveCycle\
The installation directory that is used
for all LiveCycle products. The
installation directory contains
subdirectories for Adobe
Configuration Manager, product
SDKs, and each LiveCycle product
installed (along with the product
documentation).
Linux and UNIX®:
/opt/adobe/livecycle/
10
Adobe LiveCycle
Preface
Installing and Configuring LiveCycle for WebSphere
Related documentation
Name
Default value
Description
[product root]
Windows:
C:\Adobe\LiveCycle\Assembler
C:\Adobe\LiveCycle\pdfgenerator
C:\Adobe\LiveCycle\Workflow
C:\Adobe\LiveCycle\Forms
C:\Adobe\LiveCycle\Print
C:\Adobe\LiveCycle\Formmanager
The directories where
product-specific directories and files
(such as documentation, uninstall
files, samples, and license
information) are located.
11
Linux, UNIX:
/opt/adobe/livecycle/assembler
/opt/adobe/livecycle/pdfgenerator
/opt/adobe/livecycle/workflow
/opt/adobe/livecycle/forms
/opt/adobe/livecycle/print
/opt/adobe/livecycle/formmanager
[appserver root]
Windows:
WebSphere 5.1.1.5:
C:\Program Files\WebSphere\AppServer
The home directory of the
application server that runs the
LiveCycle products.
WebSphere 6.0.2.9:
C:\Program Files\IBM\WebSphere\
AppServer
Linux and UNIX:
WebSphere 5.1.1.5:
/opt/WebSphere/AppServer
WebSphere 6.0.2.9:
/opt/IBM/WebSphere/AppServer
[dbserver root]
Depends on the database type and your
specification during installation.
The location where the LiveCycle
database server is installed.
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux). Any platform-specific information is indicated as required.
Related documentation
This guide contains instructions for deploying LiveCycle products to WebSphere Application Server. The
Installing and Configuring LiveCycle guides for other supported application servers can be accessed at:
www.adobe.com/support/documentation/en/livecycle/
The resources in this table can help you learn about and get started using LiveCycle products.
Adobe LiveCycle
Preface
Installing and Configuring LiveCycle for WebSphere
Updated LiveCycle product information
12
For information about
See
General information about a product and
how it integrates with other Adobe products
Overview guides for each product
The product architecture, how to use the APIs,
and how to develop custom applications for
use with the products
The developer guides for each product. For example,
Developing Custom Application for LiveCycle Workflow
or Developing Applications for LiveCycle Assembler.
The EJB API, including descriptions and
explanations of its classes and methods.
The API Reference for each product. Most API
References are installed as JavaDocs with each
product. However, some API references are provided
as PDF documents with the product.
The syntax for the Document Description XML
(DDX) grammar and related XML grammars
supported by LiveCycle Assembler
Document Description XML Reference
Setting up and administering Watched Folders
Watched Folder Administration Help
Managing access to the Adobe Administrator
user interface
User Management Administration Help
How to use LiveCycle Workflow Designer
Creating Workflows or LiveCycle Workflow Designer Help
Using the LiveCycle Workflow SDK to create
Quick Process Action Components (QPACs)
that invoke methods in the LiveCycle product
EJB APIs
The QPAC guides, available with the LiveCycle
Workflow SDK. For example Using LiveCycle Assembler
QPACs or Using LiveCycle Forms QPACs.
Other services and products that integrate
with LiveCycle products
www.adobe.com
Patch updates, technical notes, and additional
information on this product version
www.adobe.com/support/products/enterprise
/index.html
For information about additional documentation available for each of the LiveCycle products, see the
doc_map.pdf files located in each [product root]/documentation folder.
Note: When copying and pasting strings directly from this guide, you may copy the tag <CR> if the
instructions span a line in the guide.
Updated LiveCycle product information
Adobe Systems has posted a Knowledge Center article to communicate any updated LiveCycle product
information with customers. You can access the article at:
www.adobe.com/support/products/enterprise/knowledgecenter/c4811.pdf.
1
Before You Install
This chapter describes how to prepare your system for installing LiveCycle products:
●
“About the installation, configuration, and deployment process” on page 13
●
“Methods for installing, configuring, and deploying LiveCycle products” on page 15
●
“Installing and deploying multiple LiveCycle products” on page 16
●
“System requirements” on page 16
●
“Installation, configuration, and deployment checklists” on page 20
●
“Updated LiveCycle product information” on page 22
Before you begin installing LiveCycle products on your application server, visit the Adobe LiveCycle
product download page at the following location to make certain you have the latest version of the
software:
www.adobe.com/support/products/enterprise/support_downloads.html
About the installation, configuration, and deployment process
Installing, configuring, and deploying LiveCycle products involves the following processes:
Installing: Installing the products places all of the required files onto your computer, within one
installation directory structure. You install the products by running the installation program. The
default installation directory is C:\Adobe\LiveCycle (Windows) or /opt/adobe/livecycle (Linux or UNIX);
however, you can install the files to a different directory. In this guide, the default installation directory
is referred to as [LiveCycle root]. In order for multiple LiveCycle products to work with one another, you
must install all of the products in the same [LiveCycle root] location. This enables you to assemble the
multiple LiveCycle products into one EAR file. (See “Installing LiveCycle Products” on page 23.)
Configuring and assembling: Configuring the products modifies a variety of settings that determine
how the products work. Assembling the products packages all of the installed components that the
products need into a deployable EAR file, according to your configuration instructions. You configure
and assemble the products for deployment by running Configuration Manager. (See “Configuring
LiveCycle Products for Deployment” on page 76.) You can configure and assemble multiple LiveCycle
products at the same time.
Deploying: Deploying the products involves deploying the assembled EAR file and a few other
configured files to the WebSphere application server on which you plan to run your LiveCycle solution.
If you have configured and assembled multiple products, most of the deployable components for the
multiple products are packaged within the single deployable LiveCycle.ear file.
Initializing the LiveCycle database: Initializing the LiveCycle database creates tables for use with
Adobe User Management and certain LiveCycle products. Deploying any LiveCycle product that
connects to the LiveCycle database requires you to initialize the LiveCycle database after the
deployment process. (See “Initializing the Database” on page 126.)
13
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Starting and stopping WebSphere
14
Starting and stopping WebSphere
Several procedures in this chapter require you to stop and start the instance of WebSphere where you
want to deploy LiveCycle products. If you are unsure whether or not the application server has been
started, you can first view the WebSphere Application Server’s status.
➤ To view the WebSphere Application Server’s status:
1. From a command prompt, navigate to the [appserver root]/bin directory.
2. Enter the following command, replacing server_name with the name of the WebSphere Application
Server:
●
(Windows) serverStatus.bat server_name
●
(Linux, UNIX)serverStatus.sh server_name
➤ To start WebSphere:
1. From a command prompt, navigate to the [appserver root]/bin directory.
2. Enter the following command, replacing server_name with the name of the WebSphere Application
Server:
●
(Windows) startServer.bat server_name
●
(Linux, UNIX) startServer.sh server_name
➤ To stop WebSphere:
1. From a command prompt, navigate to the [appserver root]/bin directory.
2. Enter the following command, replacing server_name with the name of the WebSphere Application
Server:
●
(Windows) stopServer.bat server_name
●
(Linux, UNIX) stopServer.sh server_name
Accessing WebSphere Administrative Console
Several procedures in this chapter require you to access the administrative console of the WebSphere
Application Server.
➤ To access WebSphere Administrative Console:
1. Start the WebSphere Application Server.
2. In the URL line of a web browser, type the appropriate URL:
●
(WAS 5.1.1.5) http://<hostname>:<port>/admin
●
(WAS 6.0.2.9) http://<hostname>:<port>/ibm/console
If you are administering the server you are currently using, you can replace <hostname> with
localhost. The port value will depend on the application server, and whether Global Security is
enabled. The default port value for WebSphere 5.1.1.5 is 9090, the default port value for WebSphere
6.0.2.9 is 9060, and if Global Security is enabled the default SSL port value is 9043.
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Viewing the JVM system output and error logs
15
3. If WebSphere Global Security is enabled, type the WebSphere user ID and password in the boxes
provided.
4. Click Log In.
Viewing the JVM system output and error logs
The JVM system output and error logs are valuable tools for troubleshooting problems with your server.
➤ To view the JVM system output and error logs:
1. Log into WebSphere Administrative Console.
2. In the navigation tree, select Troubleshooting > Logs and Trace.
3. Select the name of the application server.
4. Click JVM Logs.
5. Click the Runtime tab and click View under either System.out (to view the JVM system output log) or
System.err (to view the error log). If any of the selections are unavailable, you can view them from the
Configuration tab by specifying the System.out and System.err file names. For example, type:
${Server_LOG_ROOT}/SystemOut.log and ${Server_LOG_ROOT}/SystemErr.log
Note: You must restart the server for these changes to take effect.
Methods for installing, configuring, and deploying LiveCycle
products
You can use one of the following methods for installing, configuring, and deploying LiveCycle products as
well as initializing the database:
Automatic: The automatic method lets you install the files, and then run Configuration Manager to
automatically perform the following tasks:
●
Configure and assemble LiveCycle products for deployment
●
Configure your application server settings for LiveCycle products
●
Automatically deploy LiveCycle products to your application server
●
Initialize database schemas for deployed LiveCycle products
●
Verify the deployed LiveCycle products
However, you must manually install your application server before running Configuration Manager.
Manual: The manual method lets you install the files, and then run Configuration Manager to
configure the application server, the EAR file and other components, and deploy the EAR file. You can
also choose to configure your application server and deploy your EAR file manually. However, you must
manually install and, once configured, start your application server as well as create and configure the
database before running Configuration Manager and deploying to the application server. You must
also run Configuration Manager a second time (after deployment) to initialize the database. (See
“Manual installation and deployment checklist” on page 21.)
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Before You Install
Upgrading LiveCycle products
16
Installing and deploying multiple LiveCycle products
To deploy more than one of the LiveCycle products discussed in this guide so that they interoperate, you
need to install the products in the same location, assemble them in a single EAR file, and then deploy the
EAR file.
Upgrading LiveCycle products
For information on upgrading LiveCycle products, refer to “Upgrading LiveCycle Products to Version 7.2
or 7.2.1” on page 192 in this guide.
About Watched Folder installation
Both LiveCycle Assembler and LiveCycle PDF Generator can use watched folder functionality as a method
for initiating jobs for processing. However, LiveCycle Assembler and LiveCycle PDF Generator use different
watched folder technologies.
LiveCycle Assembler uses a service called Watched Folder, which you install separately and configure with
LiveCycle Workflow using Configuration Manager. This service is included in the deployable LiveCycle.ear
file.
LiveCycle PDF Generator uses an embedded watched folder functionality, which does not require a
separate installation. The configuration tasks required for LiveCycle PDF Generator watched folders is
included in the “LiveCycle PDF Generator post-deployment tasks” on page 72.
All other installation and configuration references to Watched Folder in this guide pertain to the service
that is used by LiveCycle Workflow and LiveCycle Assembler.
System requirements
This section includes details about the software and hardware that is required for running LiveCycle
products.
Supported software
This table provides a summary of the application servers, web browsers, and JDK versions that LiveCycle
products support. For a complete list, see “Supported Platform and Software Combinations” on page 175.
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Supported software
Required software
Supported version
Operating system
●
Microsoft Windows Server™ 2003 Enterprise Edition or Standard Edition
●
(LiveCycle Workflow Designer) Microsoft Windows XP Service Pack 2
●
Sun Solaris 9 (WebSphere 5.x only)
●
IBM AIX 5L 5.2 or 5.3
●
SUSE™ Linux Enterprise Server 9.0 i386 (32-bit)
●
Red Hat® Linux Advanced Server 2.1 or 3.0
17
Note: LiveCycle PDF Generator Elements and
LiveCycle PDF Generator Professional are only supported on
Microsoft Windows Server 2003.
For the latest operating system versions supported by IBM WebSphere, see:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006921
Application server
●
IBM WebSphere 5.1.1.5 (WebSphere MQ 5.3.0.1, with fixpack CSD10 or
later, is also required for all Workflow implementations, moderate or large
volume servers, or servers with multiple LiveCycle product installations.)
●
IBM WebSphere 6.0.2.9
For information on the WebSphere updates you need to apply to
WebSphere 5.1.1.5 or WebSphere 6.0.2.9, see “Installing WebSphere
Application Server” on page 35.
Note: Your application server must have an active Internet connection to
access LiveCycle Administrator.
Web browser
●
Microsoft Internet Explorer 6.0 for Windows
●
Netscape 7.1 or higher for Windows
●
Netscape 7.2 or higher for Linux
●
Mozilla 1.8 or higher for Windows and Linux
●
Safari 1.2.3, Safari 1.3, Safari 2.0 (end-user support for Macintosh only)
●
(LiveCycle Forms) Firefox 1.0
Note: LiveCycle PDF Generator only supports Microsoft Internet Explorer
6.0.
JDK
●
JDK issued by IBM that is installed with WebSphere, with the Java SDK
1.4.2 SR3 Cumulative Fix applied. You can obtain the patch at:
www-1.ibm.com/support/docview.wss?rs=180&uid=swg24011069
●
(Solaris 9) Sun JDK build 1.4.2_08-b03 20050517
You must create or set the JAVA_HOME environment variable to point to the
location where Java™ is installed. Ensure that the Java 2 Standard Edition
(J2SE) installation \bin directory is in the PATH environment variable. (This is
not required for LiveCycle PDF Generator and LiveCycle Assembler.)
Database
●
IBM DB2 8.2 (Version 8.1 Fix Pack 7)
●
Microsoft SQL Server 2000 SP 3
●
Oracle 9i
●
Oracle 10g
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Platform and software combinations
Required software
Supported version
Database driver
●
IBM DB2 - db2jcc.jar and db2jcc_license_cu.jar
●
Microsoft SQL Server 2000 - base.jar, sqlserver.jar, util.jar
Note: You must use the database drivers provided with WebSphere
rather than those supplied by Microsoft. By default these files are
installed in the [appserver root]/lib directory.
LDAP server
●
Microsoft SQL Server 2000 for BAM - msbase.jar, mssqlserver.jar, and
msutil.jar
●
Oracle - ojdbc14.jar, version 10.2.0.1
●
Sun ONE 5.1, 5.2
●
Microsoft Active Directory 2000
●
Microsoft Active Directory 2003
●
Novell® eDirectory 8.7
Platform and software combinations
This table summarizes the software combination and database combination supported for IBM
WebSphere 5.1.1.5 and IBM WebSphere 6.0.2.9. For a complete list of supported software on each
operating system, see “Supported Platform and Software Combinations” on page 175.
Note: LiveCycle PDF Generator Elements and LiveCycle PDF Generator Professional only run on the
Windows Server 2003 Enterprise Edition platform.
IBM WebSphere 5.1.1.5
Operating system
Database
Microsoft Windows Server 2003 Enterprise Edition or
Standard Edition
IBM DB2 8.2 (Version 8.1 Fix Pack 7)
Microsoft Windows Server 2003 Enterprise Edition or
Standard Edition
Microsoft SQL Server 2000 SP 3
IBM AIX 5.2
IBM DB2 8.2 (Version 8.1 Fix Pack 7)
Sun Solaris 9
IBM DB2 8.2 (Version 8.1 Fix Pack 7)
IBM WebSphere 6.0.2.9
Operating system
Database
Microsoft Windows Server 2003 Enterprise Edition or
Standard Edition
Microsoft SQL Server 2000 SP 3
IBM AIX 5.3
IBM DB2 8.2 (Version 8.1 Fix Pack 7)
Red Hat AS 3.0
IBM DB2 8.2 (Version 8.1 Fix Pack 7)
18
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Minimum hardware requirements
19
Minimum hardware requirements
The table in this section lists the supported operating systems and corresponding hardware. For any
installation, these settings are recommended as a minimum:
●
Disk space for installation: 3 GB per product, except LiveCycle PDF Generator, which requires 3.5 GB
●
System temp space during installation: 3 GB
●
Memory for running the products: 1 GB per product for each CPU, except LiveCycle PDF Generator,
which requires 1.5 GB per CPU
Operating system
Minimum hardware requirement
Windows Server 2003 Enterprise Edition or
Standard Edition
Intel® Pentium® 3 or x86 equivalent, 1GHz processor
Sun Solaris 9 (WebSphere 5.x only)
Sun UltraSPARC® IIe, 650 MHz processor
IBM AIX 5L 5.2 or 5.3
P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHz
processor
SUSE Linux Enterprise Server 9.0 i386 (32-bit)
Pentium 3 or x86 equivalent, 1GHz processor
Red Hat Linux Advanced Server 2.1 or 3.0
Pentium 3 or x86 equivalent, 1GHz processor
Additional requirements for LiveCycle PDF Generator Elements and
LiveCycle PDF Generator Professional
LiveCycle PDF Generator Elements and LiveCycle PDF Generator Professional must be installed on
Microsoft Windows Server 2003 with the en_US locale. The Windows user who installs the product must
have administrative rights, and must be the same user who installed Microsoft Office on that computer.
Before installing LiveCycle PDF Generator Elements or LiveCycle PDF Generator Professional, you must
ensure that Adobe Acrobat® Professional or Acrobat Standard is not installed. If Acrobat is installed, you
must uninstall it and restart the computer. However, Adobe Reader® can be installed.
Before installing LiveCycle PDF Generator Elements or LiveCycle PDF Generator Professional, you must
also install the software that supports the file formats for which PDF conversion support is required.
LiveCycle PDF Generator Elements and LiveCycle PDF Generator Professional can be extended to convert
these additional file types to PDF files using the following applications:
●
Microsoft Office 2000, XP, or 2003
●
(LiveCycle PDF Generator Professional) Microsoft Office Visio 2003
●
(LiveCycle PDF Generator Professional) Microsoft Project 2003
●
(LiveCycle PDF Generator Professional) AutoCAD 2005
●
Corel WordPerfect 12
●
Adobe Photoshop® CS2
Before completing an automatic installation of LiveCycle PDF Generator on Windows, ensure that the
Service Control Manager command line tool, sc.exe, is installed in the Windows environment variable.
Some Windows servers do not have this software preinstalled. By default, the sc.exe file is installed in the
\Windows\system32 directory.
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Additional requirements for LiveCycle PDF Generator for PostScript
20
LiveCycle PDF Generator Professional and LiveCycle PDF Generator Elements must be installed on the
same server where it needs to be configured and deployed.
Additional requirements for LiveCycle PDF Generator for PostScript
LiveCycle PDF Generator for PostScript is supported on all of the operating systems listed in “Supported
software” on page 16.
To install LiveCycle PDF Generator for PostScript on Linux or UNIX, ensure that the bc tool (an arbitrary
precision calculator language) is installed on the computer. You can download the GNU bc tool from
www.gnu.org/software/bc/bc.html.
Installation, configuration, and deployment checklists
This section includes checklists that you can use to step through the installation and configuration
process. A checklist is provided for installing and configuring when using either the automatic method or
the manual method.
Before starting the installation, ensure that the JAR files are not associated with WinZip or any other
application other than the Java application launcher.
Automatic installation and deployment checklist
The following table includes the steps required for installing LiveCycle products using the automatic
method. Your application server must be installed before you perform the installation.
Perform this type of installation if you are installing the products in a production environment.
Note: If you are installing multiple LiveCycle products, ensure that they are all installed before running
Configuration Manager to configure and deploy them.
Task
Topic
Ensure that you have the required software
installed in the target environment.
“System requirements” on page 16
Run the installation program.
“Installing LiveCycle Products” on page 23
Create the database to use with
User Management and configure data source
information for the application server.
“Preparing Your Environment” on page 30
Run Configuration Manager and select the Typical “Configuring LiveCycle Products for
Deployment” on page 76
Configuration Wizard. This will configure and
assemble the products, configure application
server settings, deploy the products to the
application server, initialize the LiveCycle database,
and verify the deployment.
Access Administrator and User Management.
“Accessing Administrator” on page 66
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Manual installation and deployment checklist
21
Task
Topic
Configure LDAP access.
“Configuring LiveCycle Products to Access
LDAP” on page 129
Configure SSL on the application server, if
required.
“Configuring SSL on WebSphere” on
page 134
(LiveCycle Workflow) Create the BAM metadata
database and configure the application server for
BAM Server.
“Configuring WebSphere 5.1.1.5 for BAM
Server” on page 139 or “Configuring
WebSphere 6.0.2.9 for BAM Server” on
page 151
Check the log file.
“Viewing log files” on page 120 or
“Viewing log files” on page 125
Manual installation and deployment checklist
The following table includes the steps required for installing LiveCycle products using the manual method.
Your application server must be installed before you perform the installation.
Note: If you are installing multiple products, ensure that they are all installed before running
Configuration Manager to configure and deploy them.
Task
Topic
Ensure that you have the required software
installed in the target environment.
“System requirements” on page 16
Run the installation program.
“Installing LiveCycle Products” on page 23
Create the database to use with User Management “Preparing Your Environment” on page 30
and install and prepare the application server.
Run Configuration Manager and select the Custom “Configuring LiveCycle Products for
Deployment” on page 76
Configuration Wizard. This will configure and
assemble the products.
Configure WebSphere settings. A variety of settings “Manually Configuring WebSphere
5.1.1.5” on page 80 or “Manually
must be configured.
Configuring WebSphere 6.0.2.9” on
page 103
Deploy the product deployment files to the
application server.
“Manually Deploying to WebSphere
5.1.1.5” on page 116 or “Manually
Deploying to WebSphere 6.0.2.9” on
page 121
Run Configuration Manager to initialize the
database.
“Initializing the Database” on page 126
Access Administrator and User Management.
“Accessing Administrator” on page 66
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle for WebSphere
Updated LiveCycle product information
22
Task
Topic
Configure LDAP access.
“Configuring LiveCycle Products to Access
LDAP” on page 129
Configure SSL on the application server, if
required.
“Configuring SSL on WebSphere” on
page 134
(LiveCycle Workflow) Create the BAM metadata
database and configure the application server for
BAM Server.
“Configuring WebSphere 5.1.1.5 for BAM
Server” on page 139 or “Configuring
WebSphere 6.0.2.9 for BAM Server” on
page 151
Check the log file.
“Viewing log files” on page 120 or
“Viewing log files” on page 125
Updated LiveCycle product information
Adobe Systems has posted a Knowledge Center article to communicate any updated LiveCycle product
information with customers. You can access the Knowledge Center article at:
www.adobe.com/support/products/enterprise/knowledgecenter/c4811.pdf
2
Installing LiveCycle Products
This chapter describes how to use the installation program to install LiveCycle products on a Windows,
Linux, or UNIX operating system.
If you are installing LiveCycle PDF Generator (all versions), see Installing LiveCycle PDF Generator.
Note: If you are installing multiple LiveCycle products we recommend you install LiveCycle PDF Generator
first. If you install LiveCycle PDF Generator after installing other LiveCycle products you must
complete the steps in “To install LiveCycle PDF Generator with previously installed LiveCycle
products:” on page 24.
If you are installing any of the following LiveCycle products, see “Installing LiveCycle products” on page 26:
●
LiveCycle Assembler
●
LiveCycle Forms
●
LiveCycle Form Manager
●
LiveCycle Workflow
If you are installing LiveCycle Print (for use with LiveCycle Forms), see “Installing LiveCycle Print” on
page 28.
Note: You must install LiveCycle Forms prior to installing LiveCycle Print.
If you are installing Watched Folder (for use with LiveCycle Workflow and LiveCycle Assembler), see
“Installing Watched Folder” on page 29.
Before you install the products, you must ensure that your environment includes the software and
hardware required to run LiveCycle products. You should also understand the installation options and
have prepared the environment as required. (See “Before You Install” on page 13.)
If you are installing to a location where a LiveCycle product is already installed, install the new product, run
Configuration Manager to reassemble the products, undeploy the deployed product from the application
server, and then redeploy the files to the application server.
Installing LiveCycle PDF Generator
The procedure in this section applies to LiveCycle PDF Generator Professional,
LiveCycle PDF Generator Elements, and LiveCycle PDF Generator for PostScript.
When you run the installation program, you need the following information:
●
The serial number for the product you are installing.
●
The type of installation and configuration you are performing. (See “Methods for installing,
configuring, and deploying LiveCycle products” on page 15.)
23
Adobe LiveCycle
Installing LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Installing LiveCycle PDF Generator
24
Note: To successfully install, you need read and write permissions on the installation directory. The
following are the default installation directories, although you can specify a different directory as
required:
●
Windows: C:\Adobe\LiveCycle\
●
Linux and UNIX: /opt/adobe/livecycle/
If you are installing LiveCycle PDF Generator Professional or LiveCycle PDF Generator Elements, ensure
that Acrobat is not installed on the computer.
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 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.
Tip: To improve the speed of installation, disable any on-access virus scanning software for the duration of
the installation.
If you are installing on WebSphere 6.1, you must manually configure some Java Virtual Machine (JVM)
parameters after you have installed and configured LiveCycle PDF Generator. (See “Configuring JVM for
LiveCycle PDF Generator on WebSphere 6.1” on page 25.)
➤ To install LiveCycle PDF Generator with previously installed LiveCycle products:
If you installed other LiveCycle products previously you must complete these steps before installing
LiveCycle PDF Generator.
1. From the Windows services panel, select the WebSphere service hosting the LiveCycle applications.
2. Stop the service if it is running.
3. Right-click the service and open the properties.
4. Select the Log On tab.
5. Select This account.
6. Enter the user name and password used when installing the Microsoft Office and Adobe Acrobat
applications
7. Start the WebSphere service hosting the LiveCycle applications.
➤ To install LiveCycle PDF Generator for manual deployment:
1. At the root level of the installation media, start the installation program:
●
(Windows) Double-click the .exe file.
●
(Linux, UNIX) From a command prompt, type: file_name.bin
Note: You may have to change the permissions on the install program under Linux or UNIX. To do so,
type: chmod +x filename.bin
2. If prompted, select a language for the installation program and click OK.
Adobe LiveCycle
Installing LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Configuring JVM for LiveCycle PDF Generator on WebSphere 6.1
25
3. On the Welcome screen, click Next.
4. Type the serial number in the text box and click Next.
5. (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) On the Adobe
LiveCycle PDF Generator 7.2 preinstallation requirements screen, review the preinstallation
requirements and click Next.
6. If you are prompted to disable on-access virus scanning software, click Next. It is recommended that
you disable any virus scanning software during the installation process to improve the speed of the
installation.
7. Read the Product License Agreement, select I accept the terms of the license agreement, and then
click Next.
8. Accept the default directory as listed or click Browse and navigate to the directory where you want to
install the product, and then click Next.
Note: If you type in the name of a directory that does not exist, it will be created for you.
9. If prompted, select the application server you are deploying the product to and click Next.
10. (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) On the Corel WordPerfect
screen, browse to the Corel WordPerfect executable file (if installed) and click Next or, if Corel
WordPerfect is not installed, click Next.
11. (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) On the Adobe Photoshop
screen, browse to the Adobe Photoshop executable file (if installed) and click Next or, if Photoshop is
not installed, click Next.
12. Review the installation details, and then click Install. The installation program displays the progress of
the installation. A summary screen appears when the product installation is completed.
13. Ensure that the Start Configuration Manager option is not selected, and then click Finish.
Caution: Do not run Configuration Manager until you have installed all of the products you require and
have prepared your environment. (See “Preparing Your Environment” on page 30.) After you
have completed installing all of the products and preparing your environment, you only need to
run Configuration Manager once to configure and assemble the deployable components. If you
add another LiveCycle product later, you can run Configuration Manager again to configure,
assemble and deploy the product modules. (See “Configuring LiveCycle Products for
Deployment” on page 76.)
Configuring JVM for LiveCycle PDF Generator on WebSphere 6.1
After you have installed and configured LiveCycle PDF Generator on your WebSphere 6.1 application
server, you must manually configure the com.ibm.websphere.ejbcontainer.poolSize Java
Virtual Machine (JVM) parameter according to the product you have installed.
➤ To configure JVM for LiveCycle PDF Generator on WebSphere 6.1:
1. Open and log into WebSphere Administrative Console.
2. Navigate to Console > Application Servers > [server name] > Java and Process Management >
Process Definition > Java Virtual Machine > Custom Properties.
Adobe LiveCycle
Installing LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Installing LiveCycle products
26
3. Select New and, in the Name box, enter the following line:
com.ibm.websphere.ejbcontainer.poolSize
4. In the Value box, enter the value appropriate for your product:
●
(PDF Generator Professional and PDF Generator Elements)
pdfg-all#aaes-ejb.jar#Dequeue=1,1:pdfg-all#adobe-PsToPdfEjb.jar#PsToPdfD
equeue=1,3:*=40,100
●
(PDF Generator PostScript)
pdfg-ps-all#adobe-PsToPdfEjb.jar#PsToPdfDequeue=1,3:*=40,100
5. Restart the WebSphere Application Server.
Installing LiveCycle products
This section applies only to LiveCycle Assembler, LiveCycle Forms, LiveCycle Form Manager, and
LiveCycle WorkFlow.
When you run an installation program, you need the following information:
●
The serial number for the product you are installing.
●
The type of installation and configuration you are performing. (See “Methods for installing,
configuring, and deploying LiveCycle products” on page 15.)
Note: To successfully install, you need read and write permissions on the installation directory. The
following are the default installation directories, although you can specify a different directory as
required:
●
Windows: C:\Adobe\LiveCycle\
●
Linux and UNIX®: /opt/adobe/livecycle/
Note: If you select Japanese when installing LiveCycle Forms on a Japanese localized computer, the
character set is not updated. You can change this setting post-deployment by using Administrator
to access the Internationalization settings. This ensures that Japanese characters render properly.
(See “Accessing Administrator” on page 66.)
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 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 that you are using has a
minimum of 3 GB of free space available for the installation program:
●
(Windows) TMP or TEMP path as set in the Environment Variables
●
(Linux) Logged-in user’s home directory
●
(Solaris, WebSphere 5.x) /var/tmp
●
(AIX) /tmp
Adobe LiveCycle
Installing LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Installing LiveCycle products
27
➤ To install LiveCycle products for manual deployment:
1. Navigate to the root directory of the installation media. For Workflow navigate to the
AdobeLiveCycleWorkflow7.2 directory.
2. Start the installation program:
●
(Windows) Double-click the .exe file.
●
(Linux, UNIX) From a command prompt, type: file_name.bin
Caution: When you are installing the product on a Linux or UNIX operating system, you must be logged in
as the root user to successfully install the product to the default location, /opt/adobe/livecycle/.
If you are logged in as a non-root user, you must change the installation directory to one for
which you have permissions (for example, $HOME/adobe/livecycle).
3. If prompted, select a language for the installation program and click OK.
4. On the Welcome screen, click Next.
5. On the Read Before Install screen, if you are upgrading from a previous version, ensure that you have
complied with the upgrade instructions, and then click Next. If you are not upgrading, click Next.
6. Type the serial number in the text box and click Next.
7. If you are prompted to disable on-access virus scanning, click Next. It is recommended that you disable
any virus scanning software during the installation process to improve the speed of the installation.
8. Read the Product License Agreement, select I accept the terms of the license agreement, and then
click Next.
Note: Depending on the product you are installing, the next two steps may appear in reverse order.
9. Select the application server you are deploying the product to and click Next.
10. Accept the default directory as listed or click Browse and navigate to the directory where you want to
install the product, and then click Next.
Note: If you type in the name of a directory that does not exist, it will be created for you.
Caution: When you install the product, 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 product.
11. Review the installation details, and then click Install. The installation program displays the progress of
the installation. A summary screen appears when the product installation is completed.
12. Ensure that the Start Configuration Manager option is not selected, and then click Finish.
Caution: Do not run Configuration Manager until you have installed all of the products you require and
have prepared your environment. (See “Preparing Your Environment” on page 30.) After you
have completed installing all of the products and preparing your environment, you only need to
run Configuration Manager once to configure and assemble the deployable components. If you
add another LiveCycle product later, you can run Configuration Manager again to configure,
assemble and deploy the product modules. (See “Configuring LiveCycle Products for
Deployment” on page 76.)
Adobe LiveCycle
Installing LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Installing LiveCycle Print
28
Note: If you installed LiveCycle Workflow, you can now install Watched Folder. (See “Installing Watched
Folder” on page 29.)
Note: If you installed LiveCycle Forms, you can now install LiveCycle Print. (See “Installing LiveCycle Print”
on page 28.)
Installing LiveCycle Print
Before installing LiveCycle Print you must first install LiveCycle Forms. (See “Installing LiveCycle Products”
on page 23.)
➤ To install LiveCycle Print:
1. At the root level of the installation media, start the installation program:
●
(Windows) Double-click the adobe_livecycle_print_7_2.exe file.
●
(Linux, UNIX) From a command prompt, type: adobe_livecycle_print_7_2.bin
Note: You may have to change the permissions on the install program under Linux or UNIX. To do so,
type: chmod +x filename.bin
2. If prompted, select a language for the install program and click OK.
3. On the Welcome screen, click Next.
4. On the Read Before Install screen, if you are upgrading from a previous version, ensure that you have
complied with the upgrade instructions, and then click Next. If you are not upgrading, click Next.
5. Type the serial number in the text box and click Next.
6. Read the Product License Agreement, select I accept the terms of the license agreement, and then
click Next.
7. Accept the default directory as listed or click Browse and navigate to the [LiveCycle root] directory
where you installed LiveCycle Forms.
Note: You must install LiveCycle Print in the same [LiveCycle root] directory as LiveCycle Forms.
8. Review the installation details, and then click Install. The installation program displays the progress of
the installation. A summary screen appears when the product installation is completed.
9. Ensure that the Start Configuration Manager option is not selected, and then click Finish.
Caution: Do not run Configuration Manager until you have installed all of the products you require and
have prepared your environment. (See “Preparing Your Environment” on page 30.) After you
have completed installing all of the products and preparing your environment, you only need to
run Configuration Manager once to configure and assemble the deployable components. If you
add another LiveCycle product later, you can run Configuration Manager again to configure,
assemble and deploy the product modules. (See “Configuring LiveCycle Products for
Deployment” on page 76.)
Note: In order to test your installation with the LiveCycle Print sample applications, you need to deploy
the adobe-printSubmitter.ear file. (See “Deploying and running the PrintIVS web application” on
page 69.)
Adobe LiveCycle
Installing LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Installing Watched Folder
29
Installing Watched Folder
Installing Watched Folder places the files required for configuration and deployment onto your computer.
Ensure that you have already installed LiveCycle Workflow and LiveCycle Assembler before performing this
procedure.
➤ To install Watched Folder:
1. From the Watched Folder directory on the Adobe LiveCycle Assembler installation DVD, start the
installation program:
●
(Windows) Double-click the setupwin32.exe file.
●
(AIX) From a command prompt, type: setupaix.bin
●
(Linux) From a command prompt, type: setupLinux.bin
●
(Solaris, WebSphere 5.x) From a command prompt, type: setupSolaris.bin
2. If prompted, select a language for the installation and click OK.
3. Click Next on the Welcome screen.
4. If you want to increase the speed of the installation, disable any virus scanning software, and then click
Next.
5. Read the Product License Agreement, select I accept the terms of the license agreement, and then
click Next.
6. Accept the default location, or click Browse and navigate to the location where you want to install
Watched Folder, and then click Next.
7. Review the installation details, and then click Install. A summary screen appears when the product
installation is completed.
8. Ensure that the Start Configuration Manager option is not selected, and then click Finish.
Caution: Do not run Configuration Manager until you have installed all of the products you require and
have prepared your environment. (See “Preparing Your Environment” on page 30.) After you
have completed installing all of the products and preparing your environment, you only need to
run Configuration Manager once to configure and assemble the deployable components. If you
add another LiveCycle product later, you can run Configuration Manager again to configure,
assemble and deploy the product modules. (See “Configuring LiveCycle Products for
Deployment” on page 76.)
Viewing the error log
If any errors occur during the installation, the installation program creates a log file called log.txt, which
contains the error messages. The log file is located in the [LiveCycle root] directory.
Next steps
You must now prepare your database and application server for hosting LiveCycle products. (See
“Preparing Your Environment” on page 30.)
3
Preparing Your Environment
This chapter describes how to prepare your environment for hosting LiveCycle products. You must
perform the tasks provided in this chapter before you configure LiveCycle products:
●
“Creating the database” on page 30
●
“Preparing the application server” on page 35.
Creating the database
This section describes how to set up the database that stores LiveCycle configuration information and
run-time data. The procedures described in this section apply to all LiveCycle products that use User
Management. If you previously configured the database for deploying other LiveCycle products, you do
not need to perform the tasks again.
Note: User Management is an optional feature for LiveCycle Forms.
If this is the first installation of a LiveCycle product, you must create an empty database. All of the tables
required to support LiveCycle products will be created by Configuration Manager when you initialize the
database. (See “Initializing the Database” on page 126.)
Before creating the database, you must ensure that you have read the preinstallation requirements and
have the required software installed. (See “Before You Install” on page 13.)
For information on creating the BAM metadata database for LiveCycle Workflow Server, see “Creating the
BAM metadata database” on page 139.
Creating an Oracle database
If you prefer not to use the default database that was created when you installed Oracle 9i or 10g, create a
new database using the Database Configuration Assistant tool.
If any of the LDAP directories that the new database will synchronize with for authenticating LiveCycle
users includes records with UTF-8 characters, you must create a database that uses the UTF-8 character set.
You must also create a new user on the database and assign it the DBA, CONNECT and RESOURCE roles, as
well as the ACCESS_ANY_WORKSPACE, UNLIMITED TABLESPACE, and CREATE VIEW system privileges. For
deployments on Linux and UNIX, the user name must not exceed 8 characters and, on Windows, it must
not exceed 12 characters.
The user name and password of the new user you create on the database is used again when you create
the data source.
For information about using Oracle 9i or 10g, see the Oracle 9i or 10g user documentation.
30
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Creating a DB2 database
31
Creating a DB2 database
Create a DB2 database by running the script provided in this section. The script is tuned for a system that
will use 1 GB of memory for the database. If your system has a different amount of memory dedicated for
the database, see the DB2 documentation for details on configuring your system settings.
You must also create a user with SYSADM and DBADM privileges that can be used when configuring the
data source on the application server. For information about creating a user, see the DB2 documentation.
For deployments on Linux and UNIX, the user name must not exceed 8 characters and, on Windows, it
must not exceed 12 characters.
The user name and password of the new user you create on the database is used again when you create
the data source.
After you create the database, you must configure it to enable concurrent usage. (See “Configuring a DB2
database for concurrent usage” on page 32.)
➤ To create a DB2 database:
1. On the computer that hosts DB2, create a new text file that includes the following DB2 script:
create database dbname using codeset utf-8 territory default;
connect to dbname;
CREATE BUFFERPOOL "BP8K" SIZE 50000 PAGESIZE 8192 NOT EXTENDED STORAGE;
connect reset;
connect to dbname;
CREATE TEMPORARY TABLESPACE DBNAME_TEMP_8K IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING
('DB2_root\DBNAME_TEMP')
EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE DBNAME_DATA_8K IN DATABASE PARTITION GROUP
IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING
(FILE'DB2_root\DBNAME_DATA'9000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL
BP8K;
commit work;
connect reset;
connect to dbname;
alter bufferpool ibmdefaultbp immediate size 96000;
alter bufferpool bp8k immediate size 32000;
commit work;
connect reset;
update db cfg for dbname using dbheap 4000;
update db cfg for dbname using logbufsz 2048;
update db cfg for dbname using locklist 2000;
update db cfg for dbname using chngpgs_thresh 40;
update db cfg for dbname using logfilsiz 4000;
deactivate database dbname;
activate database dbname;
2. Make the following changes to the script:
●
Replace the instances of dbname and DBNAME with the name that you want for the LiveCycle
database.
●
Replace DB2_root with the path to the root directory where DB2 is installed.
●
Ensure that no commands include line breaks and each command is terminated by a semicolon (“;”).
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
●
Configuring a DB2 database for concurrent usage
Change 9000 in the following line based on your database size:
(FILE'DB2_root\DBNAME_DATA'9000)
This number specifies the minimum number of pages required to initialize the database. You can
also change this number using the DB2 administration tools after initializing the database.
3. Save the text file in a location that DB2 Command Line Processor can access.
4. Open a command prompt.
5. (Windows) Enter the following command to open DB2 Command Line Processor:
db2cmd
6. Enter the following command to run the script:
db2 -tf <path_to_script_file>/<script_file_name>
Configuring a DB2 database for concurrent usage
If you are using a DB2 database, you must configure it for multiple-user scenarios.
➤ To configure the DB2 database for concurrent usage:
1. Start DB2 Control Center:
●
(Windows) Select Start > Programs > IBM DB2 > General Administration Tools > Control
Center.
●
(Linux and UNIX) From a command prompt, enter the command: db2jcc
2. In the DB2 Control Center object tree, click All Databases.
3. Right-click the database you created for LiveCycle products and click Configuration Advisor.
4. Follow the steps in the Configuration Advisor wizard and ensure that the properties in the following
table are set.
DB2 property
Required value
Workload type
Mixed
Average number of SQL transactions Fewer than 10
per unit of work
Database Administration Priority
Faster transaction performance
Populated Database
Set according to the current state of the database. The
database is not populated if the database has not yet been
initialized using Configuration Manager.
Isolation Level
Cursor Stability
32
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Creating a SQL Server database
33
Creating a SQL Server database
You can create a SQL Server database that LiveCycle products will use to store run-time and configuration
data. For information on creating a SQL Server database, refer to the SQL Server documentation. LiveCycle
products support SQL Server 2000 SP3a.
Create a SQL Server database and create a user with DB_OWNER privileges that can be used when
configuring the data source on the application server. For information about creating the database and
user, see the SQL Server documentation.
The SQL Server database can be configured with the Windows or SQL Server authentication types. For
LiveCycle products, the authentication type must be set to SQL Server.
You must also install JTA stored procedures on SQL Server. The embedded Connect JDBC driver is shipped
with WebSphere Application Server in two parts. The JAR files are included in the main product installation
and are updated automatically when the application server is updated. However, the stored procedures
for JTA are found on a CD that is separate from the main installation. Because the stored procedures for JTA
must reside on your machines running SQL Server, which might be separate from your machines that run
WebSphere Application Server, you must install the stored procedures manually. (See Installing JTA stored
procedures.) If SQL Server runs on Windows 2003, you need to enable XA transactions at the operating
system level. (See “Enabling XA transactions for Windows Server 2003” on page 34.)
Installing JTA stored procedures
The database driver that LiveCycle products deployed to WebSphere use to connect to the SQL Server
database require stored procedures for JTA on the SQL Server computer. You need to obtain and install
updated SQL Server install files for JTA stored procedures.
➤ To install JTA stored procedures:
1. Download the ConnectJDBC33-JTA.zip file from the
ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm website. This
file applies to SQL Server 2000 when connecting from WebSphere version 5.1 and later.
2. Extract the ConnectJDBC33-JTA.zip file to a directory on the SQL Server computer.
3. Copy the sqljdbc.dll file from the [extracted location]\SQLServer JTA\32-bit directory to the [install
directory]\Microsoft SQL Server\MSSQL\Binn directory, where [install directory] is the location where
SQL Server is installed.
Note: If the SQL Server computer uses a 64-bit architecture, copy the sqljdbc.dll file from the [extracted
location]\SQLServer JTA\64-bit directory.
4. Log into SQL Server 2000 Query Analyzer using a user account that is a member of the sysadmin group.
The default member is sa.
5. In the menu of available databases, ensure that master is selected.
6. Open the instjdbc.sql file from the [extracted location]\SQLServer JTA\32-bit directory, and then
execute it.
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Creating a SQL Server database
34
Note: If the SQL Server computer uses a 64-bit architecture, execute the instjdbc.sql file from the
[extracted location]\SQLServer JTA\64-bit directory
If you are running this query for the first time, you will see several messages that indicate “xp_xxx”
cannot be dropped. These messages are warnings and do not indicate that the installation failed. The
last message should read “instxa.sql completed successfully”.
The instjdbc.sql script generates many messages. In general, these messages can be ignored, however,
the system administrator should scan the output for any messages that may indicate an execution
error. The last message should indicate that instjdbc.sql ran successfully. The script fails when there is
insufficient space available in the master database to store the JDBC XA procedures or to log changes
to existing procedures.
7. Ensure that MS DTC is started for SQL Server 2000:
●
Start SQL Server Service Manager.
●
In the Services list, select Distributed Transaction Coordinator.
●
Click Start/Continue.
●
If you want MS DTC to start automatically when the computer starts, select Auto-start service
when OS starts.
Enabling XA transactions for Windows Server 2003
If you are running SQL Server 2000 on Windows Server 2003 (Standard Edition or Enterprise Edition), XA
transactions must be enabled at the operating system level. Before you perform the tasks in this section,
you must verify whether XA transactions are already enabled for Windows Server 2003.
To enable XA transactions on the operating system, you need to perform the following tasks:
●
Enable XA transactions for the MS DTC
●
Create a registry entry for the sqljdbc.dll database drivers file that you are using
➤ To enable XA transactions for MS DTC:
1. Select Start > Programs > Administrative Tools > Component Services.
2. Select Component Services > Computers.
3. Right-click the computer name that you want to support for XA transactions and click Properties.
4. Click the MSDTC tab and click Security Configuration.
5. Under Security Settings, select Enable XA Transactions.
6. Click OK, and then click OK again.
➤ To create registry entries for the driver file:
1. Use a registry editor (such as regedit) to navigate to the registry key named
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL.
2. Create a new String Value registry named value that has the following properties:
●
Name: sqljdbc.dll
●
Type: String (REG_SZ)
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
●
Preparing the application server
35
Value: The full path name (including the file name) of the DLL file:
[install directory]\Microsoft SQL Server\MSSQL\Binn\sqljdbc.dll
3. Restart the computer so that the changes to the registry take effect.
Preparing the application server
You must install the application server that you will use to run LiveCycle products. You also need to
perform some preliminary configuration on the application server.
Installing WebSphere Application Server
You must install either WebSphere version 5.1.1.5 or 6.0.2.9 for running LiveCycle products. The
administrator user account that is being used to perform the WebSphere installation must have a user
name less than 12 characters.
IBM WebSphere 5.1.1.5
The WebSphere embedded messaging server is supported for use in development environments where
server workloads are expected to be low. However, in production environments you must install
WebSphere MQ. The embedded messaging server option is not required when WebSphere MQ is installed.
(See “Configuring JMS resources for WebSphere MQ” on page 93.)
Installing Fix Pack 1 upgrades your installation of WebSphere Application Server 5.1 to version 5.1.1. You
can obtain the Fix Pack from IBM at this location:
www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg24007195
Installing Cumulative Fix 5 upgrades version 5.1.1 to version 5.1.1.5. You can obtain Cumulative Fix 5 from
IBM at this location:
//www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006879#5115
IBM WebSphere 6.0.2.9
If you are running WebSphere Application Server 6.0.2, installing Fix Pack 9 upgrades your installation to
version 6.0.2.9. You can obtain the Fix Pack from IBM at this location:
www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006876
Installing the CORBA Fix Pack
The following Fix Pack is required. In order to install this Fix Pack you must have Administrative rights in
Windows, or be the Actual Root User in a UNIX environment, and be logged in with the same authority
level when unpacking a fix, Fix Pack or Refresh Pack.
➤ To install the CORBA Fix Pack
1. Download and install the Update Installer from the IBM website:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24008401
2. Download the 6.0.2.9-WS-WAS-IFPK30872.pak Fix Pack file from the following link:
http://www-1.ibm.com/support/docview.wss?uid=swg24013680
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Creating an application server instance
36
3. Unzip the Update Installer to the [appserver root]/updateinstaller/maintenance directory.
4. If WebSphere is currently started, stop it.
5. Run the Update Installer by typing updateinstaller/update in a command prompt.
6. Follow the wizard with all default settings (if the wizard needs to upgrade the IBM JVM, follow the
prompts to relaunch the wizard). Make sure to select the CORBA Fix Pack file as the maintenance pack
to install.
7. Restart WebSphere.
Creating an application server instance
You can create an application server instance to run LiveCycle products instead of using the default server,
named server1. A separate application server provides a separate Java virtual machine for running
LiveCycle products.
Note: If you are using LiveCycle Workflow Business Activity Monitor, you need to create an application
server instance for running BAM Server that is separate from the instance that runs
LiveCycle Workflow Server and the other LiveCycle products.
WebSphere needs to be running when you perform this task.
The procedure you use to create an application server instance depends on the version of WebSphere that
you are using:
●
WebSphere Application Server 5.1.1.5
●
WebSphere Application Server 6.0.2.9. For this version of WebSphere, you can either install a new
instance of the WebSphere product and use the default server, or create a new profile on an existing
server.
●
WebSphere Application Server Network Deployment 6.0.2.9
➤ To create an application server instance on WebSphere 5.1.1.5:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers.
2. Click New.
3. In the Server name box, type a name for the server instance.
4. Click Next, and then click Finish.
5. Save your settings to the master configuration.
➤ To create a profile on WebSphere 6.0.2.9:
1. From a command prompt, change the current directory to [appserver root]/bin/ProfileCreator.
2. Start the WebSphere Profile Creation wizard by entering the following command:
●
(Windows) pctWindows.exe
●
(AIX) pctAIX.bin
●
(Linux) pctLinux.bin
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Creating an endorsed directory
37
3. On the Welcome panel, click Next.
4. In the Profile Name box, type a name for the profile or accept the default, and click Next.
5. Click Next to accept the default directory to store the profile.
6. In the Node Name box, type the DNS name or IP address of this server, and click Next.
7. Note the port number used for the SOAP connector, and click Next.
You will need to know this port number when you run Configuration Manager to configure the
application server.
8. (Windows) Specify whether you want to run the server as a Windows service, and then specify the user
account to run the service and click Next.
9. Review the profile summary and click Next.
➤ To create an application server instance on WebSphere 6.0.2.9 Network Deployment:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers.
2. Click New.
3. In the Server name box, type a name for the server instance.
4. Click Next, and then click Finish.
Creating an endorsed directory
You must create an endorsed directory in the WebSphere directory.
➤ To create an endorsed directory:
1. Navigate to the [appserver root]/java/jre/lib directory and create a directory called endorsed.
2. Copy the following files from the [LiveCycle root]/components/um/endorsed directory to the endorsed
directory you just created:
●
dom3-xercesImpl-2.4.0.jar
●
dom3-xml-apis-2.4.0.jar
●
xalan-2.4.1.jar
3. (Solaris, WebSphere 5.x) In the [appserver root]/java/jre/lib/endorsed directory, delete the xml.jar file.
Note: If the xml.jar file is deleted, the FormsIVS sample application will not run.
Configuring the shared libraries
You must copy a LiveCycle JAR file to the WebSphere directory and then configure WebSphere shared
libraries. You also need to configure a new classloader that uses the shared library.
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Increasing the SOAP time-out
38
➤ To configure the shared library files:
1. Copy the DocumentServicesLibrary.jar file from the [LiveCycle
root]/components/csa/websphere/lib/adobe directory to the [appserver root]/optionalLibraries
directory.
2. In the WebSphere Administrative Console navigation tree, select Environment > Shared Libraries and
click New.
3. On the Configuration page, specify the following information:
●
In the Name box, type DocumentServicesLibrary.
●
In the Classpath box, type
[appserver root]/optionalLibraries/DocumentServicesLibrary.jar.
4. Click OK, and then save your changes to the Master Configuration.
➤ To configure the classloader:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers.
2. Click the server instance that you are configuring (for example, server1).
3. (WebSphere 5.1.1.5) In the Configuration tab under Additional Properties, click ClassLoader.
4. (WebSphere 6.0.2.9) In the Configuration tab under Server Infrastructure > Java and Process
Management click ClassLoader.
5. Click New, in the Class loader mode list, keep the default value Parent_First, and click OK.
6. On the page that appears, click the Classloader Id link of the newly created classloader instance.
7. On the page that appears, under Additional Properties, click Libraries and click Add.
8. In the Library Name list, select DocumentServicesLibrary and click OK.
9. Save your changes to the Master Configuration.
Increasing the SOAP time-out
You must increase the default SOAP time-out by editing the soap.client.props file.
WebSphere 5.1.1.5
Edit the soap.client.props file. You can find the file under:
[appserver root]/AppServer/properties (for stand-alone server)
[appserver root]/DeploymentManager/properties (for managed servers)
WebSphere 6.0.2.9
Edit the soap.client.props file. You can find the file under:
[appserver root]/AppServer/profiles/<profile name>/properties (for stand-alone server)
[appserver root]/DeploymentManager/profiles/<profile name>/properties (for managed servers)
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Updating the web server configuration files
39
The default value for the com.ibm.SOAP.requestTimeout property is 180 seconds. You must change the
value to 1800, and then restart the server or the deployment manager and all of the nodes.
Updating the web server configuration files
This section applies to LiveCycle Workflow only.
Before running Configuration Manager, you must update the web server configuration files on
WebSphere.
➤ To update the web server configuration files for WebSphere 5.1.1.5:
1. In the WebSphere Administrative Console navigation tree, select Environment > Update Web Server
Plugin.
2. Click OK.
Preparing WebSphere MQ
This section applies only to LiveCycle Form Manager, LiveCycle Workflow, LiveCycle PDF Generator,
and Watched Folder (for use with LiveCycle Workflow and LiveCycle Assembler).
If you are using WebSphere 5.1.1.5 as your application server, you must install WebSphere MQ in
production environments and in development environments where server workloads are expected to be
high. In development environments where you expect low server workloads, you can use the WebSphere
embedded messaging server.
This section describes how to configure WebSphere MQ 5.3.0.1 in a non-clustered environment.
In this guide, [MQ_root] indicates the location at which WebSphere MQ is installed. The default installation
location varies depending on the operating system you are using:
●
(Windows) c:\Program Files\ibm\WebSphere MQ
●
(Solaris, Linux) /opt/mqm
●
(AIX) /usr/mqm
Installing the required software
You must install all of the required software according to the following procedure before proceeding with
the rest of the instructions in this section.
Note: WebSphere MQ and WebSphere Application Server do not need to be installed on the same
computer.
➤ To install the required software:
1. Ensure that the patch levels are correct for the operating system. Computers running AIX require
version 51-007 or later.
2. If you are installing WebSphere MQ on a computer that is running WebSphere Application Server, stop
the application server before the installation.
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Installing the required software
40
3. If you are installing WebSphere MQ on a computer that has WebSphere Application Server installed, go
to the [appserver root]\bin directory and run the setupCmdLine script to ensure that the environment
variables are set correctly.
4. If you are installing WebSphere MQ on a computer that does not have WebSphere Application Server
installed, install WebSphere MQ Client and Java Messaging on the machine where WebSphere
Application Server is installed.
5. Proceed to “To install WebSphere MQ on Windows:” on page 40 or “To install WebSphere MQ on UNIX:”
on page 40.
➤ To install WebSphere MQ on Windows:
1. Start the WebSphere MQ 5.3.0.1 installer.
2. If you are installing WebSphere MQ on a computer that does not have WebSphere Application Server
or Embedded Messaging installed, proceed to step 4.
If you are installing WebSphere MQ on a computer that has WebSphere Application Server installed
with Embedded Messaging, you are prompted to either modify or remove it. Select Remove, click Next
and, when prompted to either keep or remove existing queues, select Keep.
3. After the removal of the Embedded Messaging server is complete, start the installer again and select a
Custom installation.
4. On the Features panel of the installer, ensure that Server, Client, Java Messaging, and Development
Toolkit are all selected for installation and proceed with the installation. If you have installed
WebSphere MQ on a computer that does not have WebSphere Application Server installed, you must
also install WebSphere MQ Client and Java Messaging on the computer running WebSphere
Application Server.
5. When the installation is complete, the Prepare WebSphere MQ Wizard appears. Use the wizard to
configure MQ for your environment.
6. Proceed to “To complete the post-installation tasks:” on page 40.
➤ To install WebSphere MQ on UNIX:
1. Read and follow the WebSphere MQ Quick Beginnings document for the operating system on which
you plan to install WebSphere MQ.
2. When given the option, install Server, Client, and Java Messaging.
3. If you have installed WebSphere MQ on a computer that does not have WebSphere Application Server
installed, install WebSphere MQ Client and Java Messaging on the computer running WebSphere
Application Server.
4. Proceed to “To complete the post-installation tasks:” on page 40.
➤ To complete the post-installation tasks:
1. (Windows) Stop WebSphere MQ and use Task Manager to stop any tasks that begin with “amq”.
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Installing the required software
41
2. From a command prompt, install Fix Pack 10 (formerly CSD10). Fix Pack 10 is required for the
installation of the Java Messaging support, which is required by LiveCycle products. You can obtain the
Fix Pack from IBM at this location:
http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=CS
D10&uid=swg24009688&loc=en_US&cs=utf-8&lang=en
3. Define a local user and add the user to the mqm group, which was created during the WebSphere MQ
install. The user name must be less than 12 characters long. You will later select this user when
configuring the JMS connection factories in WebSphere Application Server.
On Windows, the WebSphere MQ install creates both the mqm group and a user named
MUSR_MQADMIN. Do not alter this user, because WebSphere MQ uses it to run some services. If you
have altered this user, run the following command from the [MQ_root]\bin folder to reset it:
amqmsrvn -regserver
4. (UNIX) Log on using the mqm user account you created and update the CLASSPATH,
MQ_JAVA_INSTALL_PATH, MQ_JAVA_DATA_PATH, and LD_LIBRARY_PATH, as required, from a
command prompt. For example, under Solaris, the paths could look like:
●
export
CLASSPATH=/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mqj
ms.jar:/opt/mqm/java/lib/connector.jar:/opt/mqm/java/lib/jms.jar:/opt/mq
m/java/lib/jndi.jar:/opt/mqm/java/lib/jta.jar:/opt/mqm/java
●
export MQ_JAVA_INSTALL_PATH=/opt/mqm/java
●
export MQ_JAVA_DATA_PATH=/var/mqm
●
export LD_LIBRARY_PATH=/opt/mqm/java/lib
5. Copy the following scripts from the [LiveCycle root]/configurationManager/scripts/mq_server directory
to the [MQ_root]/bin directory:
●
configure_MQ
●
LC_Queues.mqsc
●
setMqClasspath
●
start_MQ
Note: (UNIX) Copy the scripts using the mqm user account you created when you installed WebSphere
MQ.
6. Copy the LC_JmsDefs.scp script from the [LiveCycle root]/configurationManager/scripts/mq_server
directory to the [MQ_root]/Java/bin directory.
Note: (UNIX) Copy the scripts using the mqm user account you created when you installed WebSphere
MQ.
7. From a command prompt, run the following script:
●
(Windows) From the directory containing the configure_MQ.bat file, enter the following command:
configure_MQ.bat queue_manager_name
where queue_manager_name is an appropriate queue manager name for the node.
●
(UNIX) From the directory containing the configure_MQ.sh file, enter the following command:
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere MQ
42
configure_MQ.sh queue_manager_name MQ_root MQ_Java_data_path
where queue_manager_name is an appropriate queue manager name for the node, MQ_root is
the location at which WebSphere MQ is installed (by default, /usr/mqm), and
MQ_Java_data_path is the data install path (by default, /var/mqm).
Note: If you close or lose this prompt for any reason, you must run the setMqClasspath script by
entering the following command in any subsequent command windows that you use to
administer WebSphere MQ:
●
(Windows) setMqClasspath.bat
●
(UNIX) setMqClasspath.sh MQ_root MQ_Java_data_path
Note: (UNIX) Run the script using the mqm user account you created when you installed WebSphere
MQ.
Configuring WebSphere MQ
After you install WebSphere MQ, you must configure it so that the application server can access it.
➤ To configure WebSphere MQ:
1. Create the cfstore directory, the location of the directory will differ depending on your operating
system:
●
(Windows) C:\cfstore
●
(UNIX) /opt/cfstore
2. (UNIX) Under the /opt/cfstore directory create two additional directories named jms and topic.
3. Modify the JMSAdmin.config file, located in the [MQ_root]\Java\bin directory:
●
Uncomment the
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory setting,
and comment out the rest of the INITIAL_CONTEXT_FACTORY settings. This is the setting to use a
filestore. If you want to use LDAP or WebSphere JNDI, see the appropriate IBM documentation.
●
Set the PROVIDER_URL property and create the corresponding directory on your computer:
●
(Windows) PROVIDER_URL=file:/C:/cfstore
●
(UNIX) PROVIDER_URL=file:/opt/cfstore
Note: If you are running on Windows, ensure that the path does not contain backslash characters (\).
Replace any backslash characters with forward slash characters (/).
4. Create JMS definitions by navigating to the [MQ_root]\java\bin directory from the command prompt
that you used in step 7 of “To complete the post-installation tasks:” on page 40, and then running the
script:
JMSAdmin < LC_JmsDefs.scp
Note: (UNIX) Run the script using the mqm user account you created when you installed WebSphere
MQ.
5. Start the MQ services or daemons by navigating to the [MQ_root]/bin directory and entering the
following command:
●
(Windows) start_MQ.bat queue_manager_name
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
●
Configuring WebSphere MQ
43
(UNIX) start_MQ.sh queue_manager_name port
Note: (UNIX) Run the script using the mqm user account you created when you installed WebSphere
MQ.
The port number you provide will be required when configuring WebSphere Application Server
queues and topics, so be sure to select an available port. The default port number for WebSphere MQ is
1414.
If you receive a message that the queue manager is already running, ignore this message. If you need
to restart MQ services or daemons, run the start_MQ script again.
6. (Windows) Start the message listener service:
●
Select Start > All Programs > IBM WebSphere MQ > WebSphere MQ Services.
●
Expand WebSphere MQ Services and right-click the queue manager you created in step 7 of “To
complete the post-installation tasks:” on page 40.
●
Select New > Listener.
●
On the Parameters tab, set Protocol to TCP, set Port to an available port number, set Local Address
to the address of the computer where MQ is installed, and then click OK.
●
To start the listener, in the right-hand pane, right-click the listener you just created and select
All Tasks > Start.
7. (Windows) Add a custom service in MQ Services by selecting Start > All Programs > IBM Websphere
MQ > Websphere MQ Services
8. (Windows) Click Websphere MQ Services > [your queue manager], right-click Custom Services, and
select New > Custom Service.
9. (Windows) Specify the following values for the properties in the dialog box:
●
Service Name: queue_manager_name Broker
●
Start Command: strmqbrk -m queue_manager_name
●
End Command: endmqbrk -m queue_manager_name
●
Execution: COMMAND
●
Startup: AFTER
10. (Windows) Right-click your queue manager, and then select All Tasks > Stop.
11. (Windows) Right-click your queue manager, and then select All Tasks > Start.
Note: To properly start MQ, use the MQ Services Console to ensure that both the listener and the
broker are started.
12. (UNIX) Start the broker by running the following command from the [MQ root]/bin directory:
strmqbrk -m queue_manager_name
Note: (UNIX) Run the script using the mqm user account you created when you installed WebSphere
MQ.
13. (Optional) Verify the publish-subscribe setup by navigating to the [MQ_root]\java\bin directory and
running the PSIVTRun.bat (Windows) or the PSIVTRun.sh file (UNIX) by entering the following
command:
Adobe LiveCycle
Preparing Your Environment
Installing and Configuring LiveCycle for WebSphere
Installing database drivers
44
PSIVTRun –nojndi –m queue_manager_name -t
Note: (UNIX) Run the script using the mqm user account you created when you installed WebSphere
MQ.
14. Verify that the administration channel exists on WebSphere MQ for the Queue manager by navigating
to the [MQ_root]/bin directory and performing the following steps:
●
Run the runmqsc queue_manager_name command.
●
Ensure that the SYSTEM.ADMIN.SVRCONN channel exists by entering the following command:
dis chl (SYSTEM.ADMIN*) all
●
If the channel does not exist, create it by entering the following command:
define channel(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN)
●
Ensure that security is disabled by entering the following command:
alter channel(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) mcauser('mqm')
●
Refresh the security cache by entering the following command:
refresh security(*)
●
Exit by entering the command: end
Note: (UNIX) Run the script using the mqm user account you created when you installed WebSphere
MQ.
15. If all of the preceding steps were successful, restart WebSphere Application Server.
16. Set the MQ_INSTALL_ROOT environment variable for each node to the location of the MQ installation.
To do this, log into WebSphere Administrative Console (by default, http://server_name:9090/admin)
and, in the navigation tree, select Environment > Manage WebSphere Variables. In the right pane,
select MQ_INSTALL_ROOT, set the Value property to the location where you installed WebSphere MQ,
click OK, and then save your changes to the master configuration.
Installing database drivers
You must install database drivers to the installation directories of the application server. Drivers are
required to enable Configuration Manager and the application server to connect to the LiveCycle
database. You must install the drivers for the type of database that you use for the LiveCycle database.
You do not need to install a SQL Server driver. The SQL Server driver that is installed with WebSphere is
used for connectivity with SQL Server.
➤ To install the Oracle driver:
1. Download the driver for Oracle 9i or 10g from the
www.oracle.com/technology/software/htdocs/distlic.html?url=http://www.oracle.com/technology/so
ftware/tech/java/sqlj_jdbc/htdocs/jdbc101040.html website.
2. In the ${WAS_INSTALL_ROOT} directory, create a directory named db_driver.
3. Copy the ojdbc14.jar file that you downloaded to the ${WAS_INSTALL_ROOT}/db_driver directory.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Preparing Your Environment
Next step
45
➤ To install the DB2 driver:
1. In the ${WAS_INSTALL_ROOT} directory, create a directory named db_driver.
2. Copy the db2jcc_license_cu.jar and db2jcc.jar files from the java directory under your [dbserver root]
directory, for example [dbserver root]/ibm/Sqllib/java (Windows) or [dbserver root]/java (Linux), to the
${WAS_INSTALL_ROOT}/db_driver directory.
Next step
You must now configure the product for deployment using the instructions for either an automatic
configuration or a manual configuration. (See “Automatically Configuring LiveCycle Products” on page 47
or “Configuring LiveCycle Products for Deployment” on page 76.)
Part I: Automatic Configuration and Deployment
This section of the guide describes how to automatically configure and deploy your LiveCycle products.
For information on the manual configuration and deployment of the products, see “Manual Configuration,
and Deployment” on page 75.
46
4
Automatically Configuring LiveCycle Products
This chapter describes how to use Configuration Manager to automatically configure and assemble
LiveCycle products and deploy the products to the application server, or to manually configure and
assemble LiveCycle products and automatically perform the remaining tasks of configuring the
application server and deploying the LiveCycle products.
This chapter assumes that you have prepared your environment for hosting LiveCycle products and
installed the products. If you have not done this, see “Preparing Your Environment” on page 30 and
“Installing LiveCycle Products” on page 23.
About Configuration Manager
Configuration Manager is a wizard-like tool that you can use to automatically perform all of the tasks
required for getting LiveCycle products running on the application server.
Configuration Manager is installed with every LiveCycle product. The instance of Configuration Manager
installed with a LiveCycle 7.2 product can be used with all other LiveCycle 7.2 products. When you run
Configuration Manager, you specify the LiveCycle products you are configuring, as well as the type of
application server that you are leveraging in the solution.
You can start Configuration Manager from the installation program to configure the products during the
installation process, or you can start Configuration Manager any time after the installation to configure the
products. The application server must be started to enable Configuration Manager to perform
configuration tasks on the application server.
You can configure an application server that is installed on a different computer than the one on which
you are running Configuration Manager. However, the application server must also be installed on the
Configuration Manager computer so that Configuration Manager can use the application server library
files.
Configuration tasks
Configuration Manager provides a wizard-like interface that prompts you for information so that it can
automatically accomplish the following tasks:
1. Configure and assemble LiveCycle product properties and assemble them in an EAR file for deploying
to the application server.
2. Configure application server properties so that the application server can run LiveCycle products.
3. Validate that the application server is configured correctly for running LiveCycle products.
4. Deploy LiveCycle products to the application server. Deploying to remote servers is only supported for
node-managed application servers, and not for stand-alone application servers.
5. Bootstrap the database so that the database can store the run-time data that deployed LiveCycle
products generate.
6. Verify that the deployed LiveCycle products are available and operational.
47
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Configuration modes
48
Optionally, steps 2 (configure application server properties) and 4 (deploy LiveCycle products) can be
performed manually (without using Configuration Manager). (See “Configuration modes” on page 48.)
Regardless of whether all of the tasks are performed automatically by Configuration Manager or some are
performed manually, the tasks must be performed in the order in which they are listed.
Configuration modes
Configuration Manager can run in two different modes:
Typical Configuration Wizard: In this mode, Configuration Manager performs all of the tasks required
to get LiveCycle products running on the application server. When configuring the LiveCycle product
properties, Configuration Manager uses all of the default values.
Custom Configuration Wizard: In this mode, you can select the tasks that you want Configuration
Manager to perform automatically. When configuring the LiveCycle product properties, you can use
the default values or specify custom values.
The Custom Configuration Wizard mode is useful when you want to perform some of the configuration
steps manually, and some automatically. For example, if you want to configure the application server
manually and use Configuration Manager to automatically perform the remaining configuration tasks, you
could follow these steps:
1. Run Configuration Manager in the Custom Configuration Wizard mode and use it to configure and
assemble LiveCycle products in an EAR file.
2. Manually configure the application server.
3. Run Configuration Manager again in the Custom Configuration Wizard mode to validate the
application server, deploy LiveCycle products, initialize the database, and verify that the products are
available and operational.
Running Configuration Manager more than once
Configuration Manager stores the values that you enter for configuration properties and lets you skip
configuration properties. This is useful when you run Configuration Manager more than once.
Stored property values
Configuration Manager stores all of the values (except for passwords) that you enter in its configuration
screens to prevent you from having to retype the values. When you subsequently run Configuration
Manager, you can use the previously-entered values as defaults for the configuration properties.
Do Not Apply option
Some of the Configuration Manager screens have a Do Not Apply option. When you select the Do Not
Apply option, Configuration Manager does not set the properties that are associated with the screen, and
preserves the current configuration.
You should only select the Do Not Apply option if you have previously set the properties associated with
the screen. If some of the properties are not set, subsequent Configuration Manager tasks can fail.
For example, when configuring the application server, a Configuration Manager screen collects
information about the LiveCycle database so that Configuration Manager can configure the data source on
the application server. Later, when performing the Bootstrap Database task, Configuration Manager uses
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Automatically Configuring LiveCycle Products
Determining the application server SOAP port
49
the data source to connect to the database and initialize the database schemas. If the database screen is
always skipped, the data source is not created and the Bootstrap Database task fails.
Caution: Selecting Do Not Apply is not the same as not specifying any property values. Selecting Do Not
Apply does not configure any values and the previous values are retained.
Determining the application server SOAP port
Some Configuration Manager screens require you to provide the SOAP port of the application server. Use
the procedures in this topic to determine what port is used for SOAP connections with the application
server.
➤ To determine the SOAP port on WebSphere 5.1.1.5:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers >
[serverName]
2. On the Configuration tab, under Additional Properties, click End Points.
3. Click SOAP_CONNECTOR_ADDRESS, and then see the value in the Port box.
➤ To determine the SOAP port on WebSphere 6.0.2.9:
1. In the navigation panel of the WebSphere Administrative Console, select Servers > Application Servers
> [serverName] > Communications > Ports.
2. See the value in the SOAP_CONNECTOR_ADDRESS box.
Performing a typical configuration
In a typical configuration, Configuration Manager automatically performs all of the tasks required to get
LiveCycle products running on the application server.
If you want Configuration Manager to automatically perform only a subset of the configuration tasks, see
“Performing a custom configuration” on page 53.
Note: If you have previously performed a typical configuration and deployed LiveCycle.ear, you must first
uninstall the product EAR files. (See “Uninstalling EAR files” on page 64.)
If you are configuring a remote application server, ensure that the application server is installed on the
Configuration Manager computer so that Configuration Manager can use the application server library
files.
Caution: Some of the screens in this procedure have a Do Not Apply option. Selecting Do Not Apply is not
the same as not specifying any property values. Selecting Do Not Apply does not configure any
values and the previous values are retained.
Tip: Configuration Manager verifies the values specified on each screen when you click Next. If it cannot
validate a value, the property on the screen turns red and you cannot proceed until you enter a valid
value.
Before performing a typical configuration, you must have already created the LiveCycle database and
prepared the application server. (See “Preparing Your Environment” on page 30.)
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Performing a typical configuration
50
Note: If you are configuring the application server for running LiveCycle PDF Generator, you must
perform a manual configuration on WebSphere MQ after Configuration Manager completes the
automatic configuration. (See “Enabling XA for LiveCycle PDF Generator connection factories” on
page 64.)
➤ To perform a typical configuration:
1. Start the application server.
2. Start Configuration Manager by navigating to the [LiveCycle root]/configurationManager directory and
entering the following command:
●
(Windows) ConfigurationManager.exe
●
(Linux, UNIX) ConfigurationManager.bin
3. On the Welcome screen, click Next.
4. Select Typical Configuration Wizard and click Next.
5. If prompted, on the Configuration Preferences screen, select either Use Previously Entered Values or
Revert to Default Values, and then click Next. The Configuration Preferences screen only appears if
you have previously run Configuration Manager.
6. On the Product Selection screen, select Foundation, select the products that you want to configure
and deploy, and then click Next.
7. (LiveCycle Forms) On the Adobe User Management Selection screen, select either LiveCycle Forms
with User Management and Administration or LiveCycle Forms without User Management and
Administration, and then click Next.
8. On the Configuration and Assemble Products screen, click Next.
9. Ensure that WebSphere is selected, and then click Next.
10. Review the Application Configuration and Assembly Summary information and click Back to change
any settings or click Next to continue. When you continue, Configuration Manager configures the
LiveCycle product properties using the default values and assembles the products into the
LiveCycle.ear file and, for LiveCycle PDF Generator, the additional pdfg-all.ear or pdfg-ps-all.ear file.
11. Click Next when the configuration and assembly is complete.
12. (WebSphere 5.1.1.5) On the Java Home Selection screen, type the path or browse to the directory
where the JDK is installed, and then click Next.
Note: You must use the JDK that is included with the application server.
13. On the Application Server Configuration Details screen, specify values for the following properties, and
then click Next:
●
Deploy Type: Specifies whether you are deploying to a standalone computer or to a cluster. Select
Standalone.
●
Remote Server: (WebSphere 6.0.2.9) Select this option only if the application server is running on a
different computer than the computer that is running Configuration Manager.
●
Hostname: The fully qualified name or IP address of the computer that hosts the application server.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Performing a typical configuration
51
●
SOAP Port: The port used to provide access to the SOAP service on the application server. The
default port is 8880. (See “Determining the application server SOAP port” on page 49).
●
Server Instance Name: The name of the application server that you want to configure. The name of
the default server instance that is created upon installing the application server is server1.
●
Username and Password: (Optional) If the application server requires user credentials to perform
administration tasks, the user name and password of an application server administration account.
●
Local Application Server Root Directory: The root directory of the application server installation
on the computer that is running Configuration Manager. For example, for WebSphere 5.1.1.5 under
Windows the directory is C:\Program Files\WebSphere\AppServer.
Caution: The Remote Server property cannot be used to configure LiveCycle PDF Generator Professional
or LiveCycle PDF Generator Elements because Acrobat cannot be installed remotely. However,
the property can be used to configure LiveCycle PDF Generator for PostScript.
14. On the Configure Application Server for LiveCycle screen, click Next.
15. On the JVM Settings screen, specify values for the following properties of the JVM that runs the
application server, and then click Next:
●
Do Not Apply: Select this option if you do not want to configure JVM properties at this time. If you
select this option, you do not need to provide values for the remaining properties on this screen.
●
Initial Heap Size: The initial amount of memory allocated for the JVM. Specify 512.
●
Maximum Heap Size: The maximum amount of memory that can be dynamically allocated for the
JVM. Specify 1024.
●
Additional JVM Arguments: Any additional arguments you require.
Note: Initial Heap Size and Maximum Heap Size must not be greater than 2048. For more information
about setting these values, see “Optimizing inline documents and impact on JVM memory” on
page 215.
16. (LiveCycle PDF Generator, LiveCycle Form Manager, LiveCycle Workflow) On the JMS settings screen,
specify values for the properties of the Java messaging service (JMS) that you are using on the
application server, and then click Next:
Note: For WebSphere 6.0.2.9, WebSphere MQ is not supported.
●
Do Not Apply: Select this option if you do not want to configure JMS servers at this time. If you
select this option, you do not need to provide values for the remaining properties on this screen.
●
Queue Manager Type: The type of JMS mechanism to configure on WebSphere.
●
Queue Manager Name: (WebSphere MQ) The queue manager name that you provided when you
configured WebSphere MQ. (See “Preparing WebSphere MQ” on page 39.)
●
Queue Manager Hostname: (WebSphere MQ) The fully qualified name or IP address of the
computer where WebSphere MQ is installed.
●
Port: (WebSphere MQ) The port used to access the queue manager.
●
Username and Password: (WebSphere MQ) Either the user name and password that can access the
Embedded JMS service, or the user name and password of the WebSphere MQ user that you created
and added to the mqm group. (See “Preparing WebSphere MQ” on page 39.)
●
Remote Queue Manager Root Directory: (WebSphere MQ) If MQ was installed on this machine,
specify the location of the MQ server root directory, if MQ was installed on another machine, specify
the location of the MQ client on this machine.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Performing a typical configuration
52
17. On the Datasource Creation screen, specify values for the following properties of the LiveCycle
database so that Configuration Manager can configure the database connection on the application
server, and then click Next:
●
Do Not Apply: Select this option if you do not want to configure the database connection at this
time. If you select this option, you do not need to provide values for the remaining properties on
this screen.
●
Datasource: The JNDI name of the data source to create on the application server. Select IDP_DS.
●
DB Type: The type of database you are using for the LiveCycle database.
●
DB Name: The name of the database.
●
DB Server Hostname: The name or IP address of the computer that hosts the database server.
●
Port: The port used to access the database service.
●
DB Username: The name of the user account that you created for LiveCycle products to access the
LiveCycle database.
●
DB Password: The password for the user account specified for DB Username.
●
JDBC driver in local application server lib: The name and path of the driver file that the
application server uses to connect to the database. If the driver consists of more than one file, you
only need to specify the main file, as specified in the following list:
●
(DB2) ${WAS_INSTALL_ROOT}/db_driver/db2jcc.jar
●
(Oracle) ${WAS_INSTALL_ROOT}/db_driver/ojdbc14.jar
●
(SQL Server) [appserver root]/lib/sqlserver.jar
18. On the Database Connection Tester screen, click Test Database Now to verify that Configuration
Manager can connect to the database and, when the test is successful, click Next.
19. On the Configure Application Server screen, click Apply Settings Now and, when the task is complete,
click Next.
20. Restart the application server to ensure that the settings are in effect and on the Application
Server/Cluster Restart screen, click Next.
21. On the Validate Application Server settings screen, click Next.
22. On the Deploy LCM.ear screen, click Execute and, when the deployment is complete, click Next.
23. On the Validate Application Server Settings screen, click Validate Settings Now and, when the task is
complete, click Next.
24. On the Deploy LiveCycle screen, click Next.
25. On the Confirm Products to Deploy screen, select the archives that you are deploying and click Next.
26. On the Deploy Products screen, click Deploy Products Now and, when the deployment is complete,
click Next.
27. On the Application Server URL screen, type the URL that Configuration Manager can use to connect to
the application server in the Application Server Base URL box, and then click Next. The URL must be
in the following format:
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Performing a custom configuration
53
http://[host name]:[port]
where [host name] is the name or IP address of the computer that hosts the application server, and
[port] is the HTTP service port that the application server uses (for example,
http://locahost:9080).
Note: To verify the port number to use for this setting, navigate to Application servers > [server],
select the Configuration tab, then click Communications > Ports and look for the
WC_defaulthost value.
28. On the Prepare database for LiveCycle screen, click Next.
29. On the Database Initialization screen, click Initialize Database Now and, when the task is complete,
click Next.
30. On the Verify the installation screen, click Next.
31. On the Verify Deployed Products screen, click Run Product Tests Now and, when the task is complete,
click Next.
32. On the Tasks Complete screen, click Finish.
Performing a custom configuration
In a custom configuration, you can select the tasks that you want Configuration Manager to perform
automatically. If you want Configuration Manager to automatically perform all of the configuration tasks,
see “Performing a typical configuration” on page 49.
Note: Using Configuration Manager to deploy LiveCycle products to remote servers is only supported for
node-managed application servers, and not for stand-alone application servers.
The following procedure explains how to use Configuration Manager to select the tasks that you want to
perform. After you select the tasks, proceed to the subsequent topics in this chapter for information about
how to use the screens that appear for completing each task.
Tip: Configuration Manager verifies the values specified on each screen when you click Next. If it cannot
validate a value, the property on the screen turns red and you cannot proceed until you enter a valid
value.
➤ To perform a custom configuration:
1. Start the application server.
2. Start the Configuration Manager by navigating to the [LiveCycle root]/configurationManager directory
and entering the following command:
●
(Windows) ConfigurationManager.exe
●
(Linux, UNIX) ConfigurationManager.bin
3. On the Welcome screen, click Next.
4. Select Custom Configuration Wizard and click Next.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Configuring and assembling LiveCycle products
54
5. If prompted, on the Configuration Preferences screen, select either Use Previously Entered Values or
Revert to Default Values, and then click Next. The Configuration Preferences screen only appears if
you have previously run Configuration Manager.
6. On the Product Selection screen, select Foundation, select the products that you want to configure
and deploy, and then click Next.
7. (LiveCycle Forms) On the Adobe User Management Selection screen, select either LiveCycle Forms
with User Management and Administration or LiveCycle Forms without User Management and
Administration, and then click Next.
8. If prompted, select the version of WebSphere that you are using to run LiveCycle products, and then
click Next.
9. On the Task Selection screen, select the tasks that you want Configuration Manager to automatically
perform, and then click Next.
The screen that appears next depends on the first task that you selected. If you selected more than one
task, the screens for the next task will appear immediately following the completion of the screens for
the preceding task. For information on how to complete the Configuration Manager screens for each
task, see the corresponding section:
●
“Configuring and assembling LiveCycle products” on page 54
●
“Changing the application server settings” on page 57
●
“Validating application server settings” on page 60
●
“Automatically deploying LiveCycle products” on page 60
●
“Initializing the database” on page 62
●
“Verifying deployed LiveCycle products” on page 63
Configuring and assembling LiveCycle products
The procedure in this section is a continuation of the procedure for performing a custom configuration.
(See “Performing a custom configuration” on page 53.)
When you select the Configure and Assemble products task for Configuration Manager to perform
automatically, follow the procedure in this section to complete the Configuration Manager screens that
appear.
When Configuration Manager completes the configuration of the product, it places the deployable files
(LiveCycle.ear and adobe-FontManager.ear, adobe-printSubmitter.ear for LiveCycle Print, and, for
LiveCycle PDF Generator, pdfg-all.ear or pdfg-ps-all.ear) in the following directory:
●
(Windows) [LiveCycle root]\configurationManager\export
●
(Linux, UNIX) [LiveCycle root]/configurationManager/export
➤ To configure and assemble LiveCycle products:
1. On the Configure and Assemble products screen, click Next.
2. If prompted, select the version of WebSphere you have installed.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Configuring and assembling LiveCycle products
55
3. (Optional) On the Data Manager Module Configuration screen, if you are using SSL security on your
application server, select Enable SSL and type the SSL credential password.
If you have not yet set up your SSL credential, you can type a password here and use it when you create
an SSL credential. (See “Configuring SSL on WebSphere” on page 134.)
4. Enter a directory to use for Adobe LiveCycle products temp file, and then click Next.
Note: (Linux and UNIX) If you are logged in as a non-root user, specify a directory under your home
directory.
For more information on the Adobe LiveCycle products temp file, see “Optimizing inline documents
and impact on JVM memory” on page 215.
5. On the Data Manager Module Configuration continued screen, accept the default values for the
following properties or specify new values, and then click Next:
●
Local storage sweep interval (in seconds): The amount of time between attempts to delete any
files that are no longer needed and were used to pass the document data between LiveCycle
services running on the same computer.
●
Global storage sweep interval (in seconds): The amount of time between attempts to delete any
obsolete files that were used to pass the document data between LiveCycle services running on the
different computers. Specify this property only when deploying LiveCycle products in a clustered
environment.
●
Default maximum inline size (in bytes): The maximum number of bytes kept in memory when
passing documents between different LiveCycle components. Documents that exceed this
maximum are stored on the hard drive. Use this property for performance tuning. (See “Optimizing
inline documents and impact on JVM memory” on page 215.)
●
Default disposal time-out (in seconds): The maximum amount of time during which a document
being passed between different LiveCycle components is considered active. After this time has
passed, any files used to store this document are subject to removal. Use this property to control the
usage of disk space.
●
Use NFS protocol (Windows only): Select this option when deploying LiveCycle products in a
clustered environment. Additional NFS software should be installed on your computer running
Windows before enabling this option. This option does not affect deployments on Linux or UNIX.
●
Global storage directory: A path to a shared directory used to store long-lived documents that are
passed between LiveCycle products. LiveCycle Workflow uses this directory to share process-related
files among cluster nodes. LiveCycle Form Manager uses this directory to store index files used for
full-text searches. Using an NFS shared directory can help to improve performance.
(LiveCycle PDF Generator) When LiveCycle PDF Generator is running as a service, to specify a
network folder for the Global storage directory property, you must use the network address of the
folder, and not the path of a mapped drive. For example, \\computer_name\temp is the network
address of the temp folder on the computer named computer_name.
For more information on the Global storage directory property, see “Optimizing inline documents
and impact on JVM memory” on page 215.
6. (LiveCycle Forms, LiveCycle Form Manager, LiveCycle Workflow, LiveCycle Assembler) (Optional) On the
Font Manager Module Configuration screen, select fonts for LiveCycle Forms to use in addition to the
fonts that are included with the product. In the Fonts directory box, type the path or browse to the
directory that contains the fonts to add, and then click Next.
Note: Your right to use fonts provided by parties other than Adobe is governed by the license
agreements provided to you by such parties in connection with those fonts, and is not covered
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Configuring and assembling LiveCycle products
56
under your license to use Adobe software. Adobe recommends that you review and ensure you
are in compliance with all applicable non-Adobe license agreements before using non-Adobe
fonts with Adobe software, particularly with respect to use of fonts in a server environment.
7. (LiveCycle Assembler) (Optional) On the Assembler Security Group configuration screen, specify the
type of security you want to implement controlling permission to execute Assembler DDX jobs, and
then click Next. Two types of user authentication are available:
●
Type an asterisk (*) to allow any user with a valid entry in the LDAP system to log in.
●
Leave the field blank to allow any user to log in.
8. (LiveCycle Forms, LiveCycle Form Manager, LiveCycle Workflow) (Optional) On the Form Server Module
Configuration screen, accept the default values for the following properties or specify new values, and
then click Next:
●
Validation UI: The type of UI to use on HTML forms if a validation error occurs. If you select List, all
validation errors on the form are displayed as links. If you select MessageBox, each error message is
displayed in a dialog box controlled by clicking next and previous buttons. The location of the list or
buttons depends on the option selected for Validation Reporting.
●
Validation Reporting: The location in which the validation messages are displayed. Select one of
the following options:
●
Frame Left - Displays validation messages within a frame on the left side of the web browser.
●
Frame Right - Displays validation messages within a frame on the right side of the web browser.
●
Frame Top - Displays validation messages within a frame at the top of the web browser.
●
Frame Bottom - Displays validation messages within a frame at the bottom of the web browser.
●
No Frame Left - Displays validation messages in the same window on the left side of the web
browser.
●
No Frame Right - Displays validation messages in the same window on the right side of the web
browser.
●
No Frame Top - Displays validation messages in the same window at the top of the web
browser.
●
No Frame Bottom - Displays validation messages in the same window at the bottom of the web
browser.
●
None - Does not display validation messages.
●
No UI - Returns the validation messages through the API (with data). The validation messages
are not displayed on-screen.
●
No UI With Form - Returns the validation messages through the API (with the form). The
validation messages are not displayed on-screen.
●
Validation Border: The frame border size (in pixels) when Validation Reporting is set to Frame Left,
Frame Right, Frame Top, or Frame Bottom. The frame border size must be equal to or greater than 0.
●
Output Type: The type of HTML output returned to the web browser. Select Full HTML to render
the form within full HTML tags (a complete HTML page) or select Form Body to render the form
within div tags (not a complete HTML page).
●
Locale: The language to be used for validation messages sent to client devices, such as web
browsers, as part of HTML transformations. The default value is English (United States). For
information on applicable values, see “Language and Locale Combinations” in the Developing
Custom Applications guide that is installed with LiveCycle Forms.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Changing the application server settings
57
●
Charset: The character set used to encode the output byte stream. This property is dependent on
the sFormPreference parameter specified through the API. For HTML transformations, the Form
Server Module supports character encoding values defined by the java.nio.charset package. To view
a list of supported values, go to http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html.
●
Cache Enabled: Select this option to optimize performance. This option works with the form
design’s caching property. For information on configuring this value in the form design, see Adobe
LiveCycle Designer Help.
9. (LiveCycle Forms, LiveCycle Form Manager, LiveCycle Workflow) (Optional) On the XMLForm Module
Configuration screen, accept the default values for the following properties or specify new values, and
then click Next:
●
Pool Max: The maximum number of processes that can be running. The recommended value for
PoolMax is the total number of CPUs * 2 + constant (1 or 2). When the PoolMax limit is reached,
service instances are created from PoolSize.
●
Trace Level: The trace level. The following options are available:
●
●
None - Tracing is not enabled.
●
Enter/Exit - Messages are logged each time a method is entered and exited.
●
Parameters - Messages are logged each time a method is entered and exited, and the value of
all parameters passed into each method is logged.
●
Details - Messages are logged each time a method is entered and exited, the value of all
parameters passed into each method and any extra messages are logged.
Report timing information: Select this option to monitor the start and end time of calls. You can
use this information for performance tuning.
10. On the Application Configuration and Assembly Summary screen, review the configuration details, and
then click Next.
11. On the Configure and Assemble Products Summary screen, click Next.
12. On the Tasks Completed screen, click Next (if you selected another task for Configuration Manager to
perform) or click Finish to close Configuration Manager.
Changing the application server settings
The procedure in this section is a continuation of the procedure for performing a custom configuration.
(See “Performing a custom configuration” on page 53.)
When you select the Change Application Server settings task for Configuration Manager to perform
automatically, follow the procedure in this section to complete the Configuration Manager screens that
appear for the task.
Note: If you are configuring the application server for running LiveCycle PDF Generator, you must
perform a manual configuration on WebSphere MQ after Configuration Manager completes the
automatic configuration. (See “Enabling XA for LiveCycle PDF Generator connection factories” on
page 64.)
If you are configuring a remote application server, ensure that the application server is installed on the
Configuration Manager computer so that Configuration Manager can use the application server library
files.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Changing the application server settings
58
Caution: Some of the screens in this procedure have a Do Not Apply option. Selecting Do Not Apply is not
the same as not specifying any property values. Selecting Do Not Apply does not configure any
values and the previous values are retained.
➤ To configure the application server:
1. On the Application Server Configuration Details screen, specify values for the following properties, and
then click Next:
●
Deploy Type: Specifies whether you are deploying to a standalone computer or to a cluster. Select
Standalone.
●
Remote Server: (WebSphere 6.0.2.9) Select this option only if the application server is running on a
different computer than the computer that is running Configuration Manager.
●
Hostname: The fully qualified name or IP address of the computer that hosts the application server.
●
SOAP Port: The port used to provide access to the SOAP service on the application server. The
default port is 8880. (See “Determining the application server SOAP port” on page 49).
●
Server Instance Name: The name of the application server that you want to configure. The name of
the default server instance that is created upon installing the application server is server1.
●
Username and Password: (Optional) If the application server requires user credentials to perform
administration tasks, the user name and password of an application server administration account.
●
Local Application Server Root Directory: The root directory of the application server installation
on the computer that is running Configuration Manager. For example, for WebSphere 5.1.1.5 under
Windows the directory is C:\Program Files\WebSphere\AppServer.
Caution: The Remote Server property cannot be used to configure LiveCycle PDF Generator Professional
or LiveCycle PDF Generator Elements because Acrobat cannot be installed remotely. However,
the property can be used to configure LiveCycle PDF Generator for PostScript.
2. On the Change Application Server settings page, click Next.
3. On the Configure Application Server for LiveCycle screen, click Next.
4. On the JVM Settings screen, specify values for the following properties of the JVM that runs the
application server, and then click Next:
●
Do Not Apply: Select this option if you do not want to configure JVM properties at this time. If you
select this option, you do not need to provide values for the remaining properties on this screen.
●
Initial Heap Size: The initial amount of memory allocated for the JVM. Specify 512.
●
Maximum Heap Size: The maximum amount of memory that can be dynamically allocated for the
JVM. Specify 1024.
●
Additional JVM Arguments: Any additional arguments you require.
Note: Initial Heap Size and Maximum Heap Size must not be greater than 2048. For more information
about setting these values, see “Optimizing inline documents and impact on JVM memory” on
page 215.
5. (LiveCycle PDF Generator, LiveCycle Form Manager, LiveCycle Workflow) On the JMS settings screen,
specify values for the properties of the Java messaging service (JMS) that you are using on the
application server, and then click Next:
Note: For WebSphere 6.0.2.9, WebSphere MQ is not supported.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Changing the application server settings
59
●
Do Not Apply: Select this option if you do not want to configure JMS servers at this time. If you
select this option, you do not need to provide values for the remaining properties on this screen.
●
Queue Manager Type: The type of JMS mechanism to configure on WebSphere.
●
Queue Manager Name: (WebSphere MQ) The queue manager name that you provided when you
configured WebSphere MQ. (See “Preparing WebSphere MQ” on page 39.)
●
Queue Manager Hostname: (WebSphere MQ) The fully qualified name or IP address of the
computer where WebSphere MQ is installed.
●
Port: (WebSphere MQ) The port used to access the queue manager.
●
Username and Password: (WebSphere MQ) Either the user name and password that can access the
Embedded JMS service, or the user name and password of the WebSphere MQ user that you created
and added to the mqm group. (See “Preparing WebSphere MQ” on page 39.)
●
Remote Queue Manager Root Directory: (WebSphere MQ) If MQ was installed on this machine,
specify the location of the MQ server root directory, if MQ was installed on another machine, specify
the location of the MQ client on this machine.
6. On the Datasource Creation screen, specify values for the following properties of the LiveCycle
database so that Configuration Manager can configure the database connection on the application
server, and then click Next:
●
Do Not Apply: Select this option if you do not want to configure the database connection at this
time. If you select this option, you do not need to provide values for the remaining properties on
this screen.
●
Datasource: The JNDI name of the data source to create on the application server. Select IDP_DS.
●
DB Type: The type of database you are using for the LiveCycle database.
●
DB Name: The name of the database.
●
DB Server Hostname: The name or IP address of the computer that hosts the database server.
●
Port: The port used to access the database service.
●
DB Username: The name of the user account that you created for LiveCycle products to access the
LiveCycle database.
●
DB Password: The password for the user account specified for DB Username.
●
JDBC driver in local application server lib: The name and path of the driver file that the
application server uses to connect to the database. If the driver consists of more than one file, you
only need to specify the main file, as specified in the following list:
●
(DB2) ${WAS_INSTALL_ROOT}/db_driver/db2jcc.jar
●
(Oracle) ${WAS_INSTALL_ROOT}/db_driver/ojdbc14.jar
●
(SQL Server) [appserver root]/lib/sqlserver.jar
7. On the Database Connection Tester screen, you can click Test Database Now to verify the database
settings, or click Next to continue.
8. On the Configure Application Server screen, click Apply Settings Now to configure your application
server, and, when the task is complete, click Next.
9. Restart the application server and, on the Application Server/Cluster Restart screen, click Next (if you
selected another task for Configuration Manager to perform) or click Finish to close Configuration
Manager.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Validating application server settings
60
Validating application server settings
When you select the Validate Application Server settings task for Configuration Manager to perform,
follow the procedure in this section to complete the Configuration Manager screens that appear for the
task.
The procedure in this section is a continuation from the Change Application Server Settings task. If you are
continuing directly from step 9 in the previous section, the Configuration Manager will jump to step 2
below.
Note: If you did not restart the application server after changing the application server settings using
Configuration Manager, restart it before validating the settings.
When Configuration Manager validates application server settings, it deploys and communicates with the
applications in the LCM.ear file.
If you are running Configuration Manager solely to perform the Validate Application Server Settings task,
you will need to perform steps 2 through 8 in the previous section prior to performing the validation steps
in this section.
If you are validating a remote application server, ensure that the application server is installed on the
Configuration Manager computer so that Configuration Manager can use the application server library
files.
Caution: Some of the screens in this procedure have a Do Not Apply option. Selecting Do Not Apply is not
the same as not specifying any property values. Selecting Do Not Apply does not configure any
values and the previous values are retained.
➤ To validate application server settings:
1. On the Validate Application Server settings screen, click Next.
2. On the Deploy LCM.ear screen, click Execute or click Next.
3. On the Validate Application Server Settings screen, click Validate Settings Now and, when the task is
complete, click Next (if you selected another task for Configuration Manager to perform) or click Finish
to close Configuration Manager.
Note: When validating, you must not have any LiveCycle applications running other than the LCM.
Automatically deploying LiveCycle products
The procedure in this section is a continuation of the procedure for performing a custom configuration.
(See “Performing a custom configuration” on page 53.)
When you select the Deploy Products task for Configuration Manager to perform, follow the procedure in
this section to complete the Configuration Manager screens that appear for automatically deploying
LiveCycle products to the application server.
Note: If you are redeploying LiveCycle.ear, you must first uninstall product EAR files. (See “Uninstalling EAR
files” on page 64.)
Note: Using Configuration Manager to deploy LiveCycle products to remote servers is only supported for
node-managed application servers, and not for stand-alone application servers.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Automatically deploying LiveCycle products
61
If you are continuing directly from a previous task, Configuration Manager will jump to step 2 below.
If you are running Configuration Manager solely to perform the Deploy products task, you will need to
perform all of the steps in this section.
Note: Perform this procedure only after you have configured the application server.
If you are deploying to a remote application server, ensure that the application server is installed on the
Configuration Manager computer so that Configuration Manager can use the application server library
files.
If you want to deploy LiveCycle products manually, see “Manually Deploying to WebSphere 5.1.1.5” on
page 116 or “Manually Deploying to WebSphere 6.0.2.9” on page 121.
Note: (LiveCycle Workflow) Configuration Manager does not deploy BAM Server. For information about
manually deploying BAM Server, see “Deploying BAM Server to WebSphere” on page 148 or
“Deploying BAM Server to WebSphere” on page 160.
➤ To automatically deploy LiveCycle products:
1. On the Application Server Configuration Details screen, specify values for the following properties, and
then click Next:
●
Deploy Type: Specifies whether you are deploying to a standalone computer or to a cluster. Select
Standalone.
●
Remote Server: (WebSphere 6.0.2.9) Select this option only if the application server is running on a
different computer than the computer that is running Configuration Manager.
●
Hostname: The fully qualified name or IP address of the computer that hosts the application server.
●
SOAP Port: The port used to provide access to the SOAP service on the application server. The
default port is 8880. (See “Determining the application server SOAP port” on page 49).
●
Server Instance Name: The name of the application server that you want to configure. The name of
the default server instance that is created upon installing the application server is server1.
●
Username and Password: (Optional) If the application server requires user credentials to perform
administration tasks, the user name and password of an application server administration account.
●
Local Application Server Root Directory: The root directory of the application server installation
on the computer that is running Configuration Manager. For example, for WebSphere 5.1.1.5 under
Windows the directory is C:\Program Files\WebSphere\AppServer.
Caution: The Remote Server property cannot be used to configure LiveCycle PDF Generator Professional
or LiveCycle PDF Generator Elements because Acrobat cannot be installed remotely. However,
the property can be used to configure LiveCycle PDF Generator for PostScript.
2. On the Deploy LiveCycle screen, click Next.
3. On the Confirm Products to Deploy screen, select the archives that you are deploying and click Next.
4. On the Deploy Products screen, click Deploy Products Now, and, when the task is complete, click
Next.
5. Click Next (if you selected another task for Configuration Manager to perform) or click Finish to close
Configuration Manager.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Initializing the database
62
Initializing the database
The procedure in this section is a continuation of the procedure for performing a custom configuration.
(See “Performing a custom configuration” on page 53.)
When you select the Bootstrap Database task for Configuration Manager to perform, follow the procedure
in this section to complete the Configuration Manager screens that appear for initializing the LiveCycle
database.
If you are continuing directly from a previous task, Configuration Manager will jump to step 3 below.
If you are running Configuration Manager solely to perform the Bootstrap database task, you will need to
perform all of the steps in this section.
Note: There is no method for manually initializing the database.
If you are using User Management with LiveCycle products, you must run Configuration Manager to
initialize the database for integration with User Management. When you run Configuration Manager, the
application server must be running. Initializing the database is a process that prepares a database for use
with LiveCycle products by creating tables and optionally adding data to them. You only need to initialize
the database the first time you deploy the product.
If you have deployed LiveCycle products to a remote application server, ensure that the application server
is installed on the Configuration Manager computer so that Configuration Manager can use the
application server library files.
This section assumes that you have configured the database for integration with the product and have
deployed the product to the application server. If you have not done this, see “Preparing Your
Environment” on page 30, and “Manually Deploying to WebSphere 5.1.1.5” on page 116 or “Manually
Deploying to WebSphere 6.0.2.9” on page 121.
➤ To initialize the database:
1. On the Application Server URL screen, type the URL that Configuration Manager can use to connect to
the application server in the Application Server Base URL box, and then click Next. The URL must be
in the following format:
http://[host name]:[port]
where [host name] is the name or IP address of the computer that hosts the application server, and
[port] is the HTTP service port that the application server uses (for example,
http://locahost:9080).
2. On the Prepare database for LiveCycle screen, click Next.
3. On the Deploy LCM.ear screen, click Execute or click Next.
4. On the Database Initialization screen, click Initialize Database Now, and, when the task is complete,
click Next.
5. Click Next (if you selected another task for Configuration Manager to perform) or click Finish to close
Configuration Manager.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Verifying deployed LiveCycle products
63
Verifying deployed LiveCycle products
The procedure in this section is a continuation of the procedure for performing a custom configuration.
(see “Performing a custom configuration” on page 53.)
When you select the Verify Deployed Products task for Configuration Manager to perform, follow the
procedure in this section to complete the Configuration Manager screens that appear for verifying that the
LiveCycle services are accessible and functioning.
If you are continuing directly from a previous task, Configuration Manager will jump to step 3 below.
If you are running Configuration Manager solely to perform the Verify Deployed Products task, you will
need to perform all of the steps in this section.
If you are verifying the deployment to a remote application server, ensure that the application server is
installed on the Configuration Manager computer so that Configuration Manager can use the application
server library files.
Tip: You can perform this procedure if you have deployed LiveCycle products manually or automatically
with Configuration Manager.
➤ To verify deployed LiveCycle products:
1. On the Application Server URL screen, type the URL that Configuration Manager can use to connect to
the application server in the Application Server Base URL box, and then click Next. The URL must be
in the following format:
http://[host name]:[port]
where [host name] is the name or IP address of the computer that hosts the application server, and
[port] is the HTTP service port that the application server uses (for example,
http://locahost:9080.)
Note: To verify the port number to use for this setting, navigate to Application servers > [server],
select the Configuration tab, then click Communications > Ports and look for the
WC_defaulthost value.
2. On the Application Server Configuration Details screen, specify values for the following properties, and
then click Next:
●
Deploy Type: Specifies whether you are deploying to a standalone computer or to a cluster. Select
Standalone.
●
Remote Server: (WebSphere 6.0.2.9) Select this option only if the application server is running on a
different computer than the computer that is running Configuration Manager.
●
Hostname: The fully qualified name or IP address of the computer that hosts the application server.
●
SOAP Port: The port used to provide access to the SOAP service on the application server. The
default port is 8880. (See “Determining the application server SOAP port” on page 49).
●
Server Instance Name: The name of the application server that you want to configure. The name of
the default server instance that is created upon installing the application server is server1.
●
Username and Password: (Optional) If the application server requires user credentials to perform
administration tasks, the user name and password of an application server administration account.
●
Local Application Server Root Directory: The root directory of the application server installation
on the computer that is running Configuration Manager. For example, for WebSphere 5.1.1.5 under
Windows the directory is C:\Program Files\WebSphere\AppServer.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Automatically Configuring LiveCycle Products
Enabling XA for LiveCycle PDF Generator connection factories
64
Caution: The Remote Server property cannot be used to configure LiveCycle PDF Generator Professional
or LiveCycle PDF Generator Elements because Acrobat cannot be installed remotely. However,
the property can be used to configure LiveCycle PDF Generator for PostScript.
3. On the Verify the installation screen, click Next.
4. On the Deploy LCM.ear screen, click Execute or click Next.
5. On the Verify Deployed Products screen, click Run Product Tests Now, and, when the task is complete,
click Next.
6. Click Finish.
Enabling XA for LiveCycle PDF Generator connection factories
If you used Configuration Manager to automatically configure WebSphere MQ for
LiveCycle PDF Generator, you must manually enable XA for AESTopicConnectionFactory.
➤ To enable XA transactions:
1. In the navigation tree of the WebSphere Administrative Console, click Resources > WebSphere MQ
JMS Provider.
2. In the right pane, set the scope to Cell and click Apply.
3. Click WebSphere MQ Queue Connection Factories.
4. Select AESQueueConnectionFactory.
5. Select the XA enabled option, and click OK.
6. Save your changes to the master configuration.
Uninstalling EAR files
If you need to redeploy a LiveCycle product, you must first uninstall the LiveCycle, LiveCycle Configuration
Manager, and Font Manager Module applications from the application server.
For example, if you have assembled LiveCycle products again to configure product properties differently,
and the previous LiveCycle.ear file is already deployed, you need to uninstall the LiveCycle, LCM, and Font
Manager Module applications before deploying the newly assembled EAR file.
➤ To uninstall the ear files:
1. Start the application server.
2. Start WebSphere Administrative Console by typing http://hostname:port/admin in the URL line
of a web browser.
3. In the navigation tree, select Applications > Enterprise Applications.
Adobe LiveCycle
Automatically Configuring LiveCycle Products
Installing and Configuring LiveCycle for WebSphere
Next step
65
4. Select the LiveCycle, LCM, Font Manager Module applications, as well as any other installed LiveCycle
applications (see “Summary of deployable components” on page 116 or “Summary of deployable
components” on page 122), and then click Stop.
5. Select the LiveCycle, LCM, Font Manager Module applications, as well as any other installed LiveCycle
applications (see “Summary of deployable components” on page 116 or “Summary of deployable
components” on page 122), and then click Uninstall.
6. Save your changes to the Master Configuration and restart your application server.
After uninstalling the ear file, you will need to reconfigure your ear file and redeploy, see “Performing a
typical configuration” on page 49 or “Performing a custom configuration” on page 53.
Next step
You can now access Administrator and User Management. (See “Post-deployment” on page 66, “Accessing
Administrator” on page 66, and “Accessing User Management” on page 67.)
You can also now configure LiveCycle products to access LDAP. (See “Configuring LiveCycle Products to
Access LDAP” on page 129.)
If you are using SSL for authentication, you can configure SSL on the application server. (See “Configuring
SSL on WebSphere” on page 131.)
If you are using LiveCycle Workflow, you can now install LiveCycle Workflow Designer. (See “Installing
LiveCycle Workflow Designer” on page 172.)
5
Post-deployment
This chapter describes how to get started using your LiveCycle products after they have been installed,
configured, and deployed to your application server:
●
“Accessing Administrator” on page 66
●
“Accessing User Management” on page 67
●
“LiveCycle Assembler post-deployment tasks” on page 67
●
“LiveCycle Forms post-deployment tasks” on page 68
●
“LiveCycle Print post-deployment tasks” on page 69
●
“LiveCycle Form Manager post-deployment tasks” on page 71
●
“LiveCycle PDF Generator post-deployment tasks” on page 72
Accessing Administrator
Administrator is the web-based portal for accessing a variety of configuration pages that let you set
run-time properties that control the way LiveCycle products operate. When you log into Administrator,
you can access User Management, Adobe JMX Monitor, Watched Folder configuration (installed with
Watched Folder), Process Manager and server settings (installed with LiveCycle Workflow), and
administrative configuration options for other LiveCycle products.
The default user name and password for logging into Administrator is administrator and password. After
you log in the first time, you can access User Management and change the password.
Before you access Administrator, the LiveCycle products must be deployed and running on your
application server.
For information on using Administrator, see Adobe Administration Help (available from the Help menu of
the Administrator window).
➤ To access Administrator:
1. Type the following URL in a web browser:
http://[host name]:[port]/adminui
The default port number for WebSphere is 9080.
2. In the User Name field, type administrator and, in the Password field, type password.
3. After logging in, you can click Services to access the LiveCycle product Administrator pages, or
Settings to access the User Management pages.
66
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
Accessing User Management
67
Accessing User Management
User Management allows administrators to maintain a database for all users and groups that are
synchronized with one or more third-party user directories. User Management provides authentication,
authorization, and user management for LiveCycle products, including LiveCycle PDF Generator,
LiveCycle Assembler, LiveCycle Form Manager, LiveCycle Forms, and LiveCycle Workflow.
User Management allows you to enable single sign-on (SSO) between LiveCycle products and Netegrity
SiteMinder protected applications using Security Assertion Markup Language (SAML). When SSO is
implemented, the LiveCycle user login pages are not required and do not appear if the user has already
been authenticated via their company portal.
For information about using User Management, see Adobe User Management Administration Help
(available from the Help menu of the User Management window).
➤ To access User Management:
1. From the home page of Administrator, click Settings.
2. On the Settings page, click User Management.
Note: For information about configuring users with User Management, click User Management Help
in the upper right corner of the User Management page.
➤ (LiveCycle Forms) To access Administrator without User Management:
●
Type the following URL in a web browser:
http://[host name]:[port]/FormServerAdmin/settings.html
LiveCycle Assembler post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle Assembler.
Verifying the LiveCycle Assembler deployment
You can verify that LiveCycle Assembler is deployed and running properly by deploying the prebuilt
sample. (See the Samples Guide for LiveCycle Assembler, located in the
[LiveCycle root]/Assembler/samples/docs directory.)
➤ To deploy the LiveCycle Assembler sample to WebSphere:
1. Copy the websphere.sample-assembler7.ear file from the
[LiveCycle root]/Assembler/samples/build/prebuilt directory to the [appserver root]/installableApps
directory.
2. In the WebSphere Administrative Console navigation tree, select Applications > Install New
Application.
3. Click Browse to navigate to the [appserver root]/InstallableApps directory, and then select
websphere.sample-assembler7.ear.
4. Click Next, accept the default values that are displayed on each screen, and then click Finish.
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
LiveCycle Forms post-deployment tasks
68
5. Click Save to Master Configuration, and then click Save.
6. Type the following URL in a web browser:
http://localhost:9080/adobe/livecycle/samples/assembler7/
7. Click About Assembler and confirm that the LiveCycle Assembler information is returned to the Result
window.
You can now create applications for LiveCycle Assembler. (See the Developing Applications for LiveCycle
Assembler guide.)
LiveCycle Forms post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle Forms.
You can now create custom applications for LiveCycle Forms. (See the Developing Custom Applications
guide.) For details on the Form Server Module, see the Form Server Module API Reference. For details on the
XML Form Module API, see the XML Form Module API Reference.
You can optionally install LiveCycle Print to enable LiveCycle Forms to output forms as Adobe PostScript,
Printer Control Language (PCL), and Zebra Programming Language (ZPL) print streams, in addition to PDF
and HTML forms. Without LiveCycle Print, LiveCycle Forms cannot output forms as print streams. Instead,
LiveCycle Forms sends forms across a network and renders them to client devices, such as web browsers,
as PDF or HTML forms.
Verifying the LiveCycle Forms deployment
You can verify that LiveCycle Forms is deployed and running properly by accessing the Installation
Verification Sample application that is installed with the product.
➤ To access the Installation Verification Sample:
1. Start WebSphere Administrative Console from its Start menu group.
2. In the navigation tree, select Applications > Install New Application.
3. Click Browse to navigate to the [LiveCycle root]/components/forms/samples/common/ directory,
select the FormsIVS.ear file, and then click Next.
4. Accept all of the default values on each subsequent screen and, on the Summary page, click Finish.
5. Click Save to Master Configuration and then click Save.
6. In the navigation tree, select Applications > Enterprise Applications, and then select FormsIVS.
7. Click Start. The red “X” next to the name of each application changes to a green arrow, indicating that
the application is running.
8. Type the following URL in a web browser:
http://[host name]:[port]/FormsIVS
where [host name] is the name of the server on which Forms has been deployed. If you are invoking
FormsIVS on the server itself, provide the server name instead of “localhost”.
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
LiveCycle Print post-deployment tasks
69
Note: For information about using the sample application, click the Help link in the Samples page in
the web browser.
LiveCycle Print post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle Print.
Verifying deployment
You can verify that LiveCycle Print is deployed and running properly using any of the following methods:
●
Deploying and running the Print Installation and Verification Sample (PrintIVS) web application.
●
Running the Print Submitter console application (you do not have to deploy this application).
Both of these applications invoke LiveCycle Print by using the LiveCycle Print API (this API consumes
the LiveCycle Print web service).
●
Running the Forms Installation and Verification Sample (FormsIVS) application. If LiveCycle Print is
deployed, the Output format list contains three additional options: PostScript, ZPL, and PCL. For
information about the Installation Verification Sample application, see “Verifying the LiveCycle Forms
deployment” on page 68.
In addition to running the two sample print applications, you can also invoke LiveCycle Print by using the
Form Server Module API Print application. This sample Print application is a console application that
invokes LiveCycle Print by using the Form Server Module API. (See “Running the Form Server Module API
Print application” on page 71.)
Deploying and running the PrintIVS web application
The PrintIVS web application is packaged in the adobe-printSubmitter.ear file, which is located in the
[LiveCycle root]/components/print/common/ear directory. After you run Configuration Manager, the
PrintIVS is deployed by default and is located in the [LiveCycle root]/configurationManager/export
directory.
To run this application, you must understand the print specification because this application requires the
same values as the print specification. (See “About the print specification” in the LiveCycle Print Getting
Started guide.)
➤ To deploy and run the PrintIVS web application:
1. [LiveCycle root]/components/print/common/earStart WebSphere Administrative Console from its Start
menu group.
2. In the navigation tree, select Applications > Install New Application.
3. Click Browse to navigate to the [LiveCycle root]/components/print/common/ear directory, select the
adobe-printSubmitter.ear file, and then click Next.
4. Accept all of the default values on each subsequent screen and, on the Summary page, click Finish.
5. Click Save to Master Configuration and then click Save.
6. In the navigation tree, select Applications > Enterprise Applications, and then select PrintIVS.
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
Running the Print Submitter application
70
7. Click Start. The red “X” next to the name of each application changes to a green arrow, indicating that
the application is running.
8. To run the sample application, type http://[host name]:[port]/PrintIVS in the URL line of a
web browser.
9. Enter the required values and click Print.
Running the Print Submitter application
The Print Submitter application consists of the lcprint.bat (Windows) or lcprint.sh (UNIX or Linux) file,
which is located in the [LiveCycle root]/components/print/samples/common/lcprint directory.
You can run the Print Submitter application from a command prompt to invoke LiveCycle Print.
➤ To run the Print Submitter application:
1. From a command prompt, navigate to the [LiveCycle root]/components/print/samples/common/lcprint
directory.
If you have not installed to the default directory, create a new environment variable named
LiveCycleRoot and set the value to the installation directory used on your system.
2. Enter the following command:
lcprint <-d,--dataFile filename> <-f,--specFile filename> <-s,--server
server:port>
The first argument, which is optional, is a fully qualified path to the data file. A series of data files
accompanies LiveCycle Print and are located in the
[LiveCycle root]/components/print/samples/common/lcprint /data directory.
Most of these files contain multiple records. For example, PurchaseOrder_batch_25.xml contains 25
records. You can create multiple print streams by using a data file that contains multiple records. (See
“Working with multiple data records” in the LiveCycle Print Getting Started guide.)
The second argument is a fully qualified path to the print specification that is sent to LiveCycle Print.
You can amend the PrintSpecTemplate.xml file and use this file. The PrintSpecTemplate.xml file is
located in the same directory as the lcprint.bat file. (See “About the print specification” in the
LiveCycle Print Getting Started guide.)
One value that you must specify within the print specification is the location of the form design on
which a print stream is based. Sample form designs are located in the
[LiveCycle root]/components/print/samples/common/lcprint /forms directory.
The third argument, which is required, specifies the server name and port.
You can also use the Print Submitter console application to retrieve information about a previous
request. To perform this task, use the following command:
lcprint <-r,--result requestId>
where requestId is a string value, such as 59572cd82, that specifies a request identifier. This
command returns result data that specifies the status of a request. (See “About result data” in the
LiveCycle Print Getting Started guide.)
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
Running the Form Server Module API Print application
71
Running the Form Server Module API Print application
The Form Server Module API Print application uses the Form Server Module API to invoke LiveCycle Print
from a command prompt. (See “Working with the Form Server Module” in the LiveCycle Print Getting
Started guide.)
The Form Server Module API Print application consists of a Java file named FsPrint.java, which is located in
the [LiveCycle root]/components/print/samples/common/fsprint directory. If you are using Windows, you
must run the fsprint.bat file located in this directory. If you are using UNIX or Linux, you must run the
fsprint.sh file.
Note: The Form Server Module API Print application creates a SOAPClient object that specifies a valid
SOAP endpoint. The default SOAP endpoint in the FsPrint.java file is configured for the default SOAP
endpoint that JBoss uses. If LiveCycle Forms is deployed on a different J2EE application server, you
must edit the FsPrint.java file by commenting and uncommenting the appropriate SOAP endpoint.
For more information about using a SOAPClient object, see the LiveCycle Forms Developing
Custom Applications guide.
➤ To run the Form Server Module API Print application:
1. From a command prompt, navigate to the application
[LiveCycle root]/components/print/samples/common/fsprint directory.
If you have not installed to the default directory, create a new environment variable named
LiveCycleRoot and set the value to the installation directory used on your system.
2. Enter the following command:
fsprint <-argument 1> <-argument2>
The first argument is a fully qualified path to the form design (an XDP file). You can use a sample form
design that is located in the [LiveCycle root]/components/print/samples/common/lcprint/forms
directory.
The second argument, which is optional, defines the print stream destination. For example, you can
define a file URI to a PostScript file. If this value is not specified, output is written to the standard output.
This value is similar to the PrintURI element that is located in the print specification. (See “About the
print specification” in the LiveCycle Print Getting Started guide.)
Tip: The source code for the Form Server Module API Print application is located in the FsPrint.java file. You
can open this file to see the application logic that invokes LiveCycle Print by using the Form Server
Module API.
LiveCycle Form Manager post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle Form Manager.
Accessing the LiveCycle Form Manager end-user pages
After you configure User Management to connect to your organization’s LDAP server, users can access the
LiveCycle Form Manager end-user pages by going to the following URL:
http://[host name]:[port]/fm
The default port number for WebSphere is 9080.
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
LiveCycle PDF Generator post-deployment tasks
72
You can also access the end-user pages using the default administration user name (Administrator)
and password (password).
For information about using the LiveCycle Form Manager end-user pages, see LiveCycle Form Manager Help
(available from the Help menu of the LiveCycle Form Manager window).
LiveCycle PDF Generator post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle PDF Generator.
Setting up job sources
You can configure LiveCycle PDF Generator to accept jobs from watched folders, email, and the web UI
(sample code). (See LiveCycle PDF Generator Administration Help.)
Additionally, LiveCycle PDF Generator can accept jobs submitted with the LiveCycle PDF Generator web
services interface. To enable this, the sample web services client application installed with
LiveCycle PDF Generator requires developer modifications before it can be used for job submission. For
more information on configuring these job sources, see the LiveCycle PDF Generator Developing Custom
Applications guide.
Setting Adobe PDF Printer as the default printer
This section applies to LiveCycle PDF Generator Professional and Elements only.
You must set up the Adobe PDF Printer as the default printer on the server.
➤ To set up Adobe PDF Printer as the default printer:
1. Navigate to the printer panel in your operating system.
2. Set Adobe PDF as the default printer.
Installing fonts
You can install the fonts that are used in documents converted by LiveCycle PDF Generator. Fonts may be
referenced by PostScript or EPS documents, or they may be referenced by native file formats, such as those
used by Microsoft Word or Microsoft Excel.
To make additional fonts available to any application, install the fonts using one of these methods:
●
●
Install the fonts in the appropriate folder:
●
(Windows) C:\Windows\Fonts
●
(AIX) /user/lpp/X11/lib/X11/fonts
●
(Solaris, WebSphere 5.x) /usr/openwin/lib/X11/fonts
●
(Linux) /usr/X11R6/lib/X11/fonts
Using Configuration Manager, on the Font Manager Module Configuration screen, browse to the
directory that contains the fonts and then redeploy the Font Manager Module. For information about
deploying the Font Manager Module, see “Configuring LiveCycle Products for Deployment” on
page 76.
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for WebSphere
Setting the LiveCycle PDF Generator conversion time-out
73
For a list of fonts installed with the Font Manager Module, see “Fonts Installed with the Font Manager
Module” on page 179.
Note: Fonts in the Font Manager Module are not available to the native applications that
LiveCycle PDF Generator uses to convert native file formats. Such native applications include
Microsoft Word and Acrobat. To make a font available to native applications, you must install it in
the system font folder. If your LiveCycle PDF Generator server is clustered, the font must be installed
on each computer used to host native applications.
Satisfying font references
This section applies to LiveCycle PDF Generator Elements and LiveCycle PDF Generator Professional only.
For font references in a native file, LiveCycle PDF Generator Elements and
LiveCycle PDF Generator Professional use the native application with the Adobe PDF printer to convert a
native file format to PDF. The native application satisfies font references from the C:\Windows\Fonts
directory.
For font references in a PDF document, these products attempt to satisfy the font references from the
following sources in the following order:
●
Fonts embedded in the PDF document
●
Font Manager Module
●
C:\WINDOWS\Fonts
Setting the LiveCycle PDF Generator conversion time-out
You can configure LiveCycle PDF Generator conversion time-out settings at the application server level or
job source level. If the time-out setting is configured at more than one level, the lowest level is applicable.
For details about configuring the setting at the application server level, see “Manually Configuring
WebSphere 5.1.1.5” on page 80 or “Manually Configuring WebSphere 6.0.2.9” on page 103.
➤ To set the conversion time-out settings at the job source level:
●
In Administrator, select Create PDF and, in the Specify a timeout box, type a value in seconds. By
default, this value is read from the server.aes.properties file.
➤ To set the conversion time-out settings for watched folders and email sources:
1. In Administrator, select Services > Adobe LiveCycle PDF Generator > Configuration Files > Export
Configuration.
2. Select Download entire configuration and click Download. By default, this value is read from the
server.aes.properties file.
3. Edit the native2pdfconfig.xml file in a text editor and set the <timeout> level.
4. Upload your changes by selecting Import Configuration, browsing to the location of the
native2pdfconfig.xml file, and then clicking Import.
Note: The time-out level for the web services APIs is read from the server.aes.properties file.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Post-deployment
Next Step
74
Next Step
If you have installed and configured LiveCycle Workflow, you must now configure the JBoss application
server for BAM Server. (See “Configuring WebSphere 5.1.1.5 for BAM Server” on page 139 or “Configuring
WebSphere 6.0.2.9 for BAM Server” on page 151.)
Part II: Manual Configuration, and Deployment
This section of the guide describes how to manually configure and deploy your LiveCycle products.
For information on the automatic configuration and deployment of the products, see “Automatic
Configuration and Deployment” on page 46.
75
6
Configuring LiveCycle Products for Deployment
This chapter describes how to configure LiveCycle products for deployment.
This chapter assumes that you have installed LiveCycle products. If you have not installed the products, see
“Installing LiveCycle Products” on page 23.
The instance of Configuration Manager that is installed with one LiveCycle product can be used with all
LiveCycle products. When you run Configuration Manager, you can specify the LiveCycle products that you
are configuring as well as the type of application server that you are leveraging in the solution. You can
also set run-time properties for LiveCycle products and enable or disable security.
If you are already running one or more LiveCycle products, you must configure and assemble those
existing products with the new one that you want to configure. To do this, you must undeploy the
previously deployed products and select all of the products that you want to assemble during
configuration. The previously deployed products are then included in the LiveCycle.ear file and deployed
with the new product when you deploy the file to the application server.
Note: To assemble multiple LiveCycle products, each product must be installed in the same
[LiveCycle root] directory.
When Configuration Manager completes the configuration of the products, it places the files to be
deployed to the application server (LiveCycle.ear, adobe-FontManager.ear, and the product-related ear
files) in the following directory:
●
(Windows) [LiveCycle root]\configurationManager\export
●
(Linux, UNIX) [LiveCycle root]/configurationManager/export
➤ To configure the products for deployment:
1. Navigate to the [LiveCycle root]/configurationManager directory and start Configuration Manager:
●
(Windows) Double-click ConfigurationManager.exe.
●
(Linux, UNIX) From a command prompt, type: ConfigurationManager.bin
2. If prompted, select a language for Configuration Manager and click OK.
3. On the Configuration Manager Welcome screen, click Next.
4. Select Custom Configuration Wizard and click Next.
5. If prompted, on the Configuration Preferences screen, select either Use Previously Entered Values or
Revert to Default Values, and then click Next.
6. Select the application server you have installed, select Foundation and the products that you want to
configure, and then click Next.
7. (LiveCycle Forms) On the Adobe User Management Selection screen, select either LiveCycle Forms
with User Management and Administration or LiveCycle Forms without User Management and
Administration, and then click Next.
8. Ensure that only Configure and assemble LiveCycle products is selected, and then click Next.
76
Adobe LiveCycle
Configuring LiveCycle Products for Deployment
Installing and Configuring LiveCycle for WebSphere
77
9. On the Configure and Assemble products screen, click Next.
10. If prompted, select the version of WebSphere you have installed.
11. (Optional) On the Data Manager Module Configuration screen, if you are using SSL security on your
application server, select Enable SSL and type the SSL credential password.
If you have not yet set up your SSL credential, you can type a password here and use it when you create
an SSL credential. (See “Configuring SSL on WebSphere” on page 134.)
12. Enter a directory to use for Adobe LiveCycle products temp file, and then click Next.
Note: (Linux and UNIX) If you are logged in as a non-root user, specify a directory under your home
directory.
For more information on the Adobe LiveCycle products temp file, see “Optimizing inline documents
and impact on JVM memory” on page 215.
13. On the Data Manager Module Configuration continued screen, accept the default values for the
following properties or specify new values, and then click Next:
●
Local storage sweep interval (in seconds): The amount of time between attempts to delete any
files that are no longer needed and were used to pass the document data between LiveCycle
services running on the same computer.
●
Global storage sweep interval (in seconds): The amount of time between attempts to delete any
obsolete files that were used to pass the document data between LiveCycle services running on the
different computers. Specify this property only when deploying LiveCycle products in a clustered
environment.
●
Default maximum inline size (in bytes): The maximum number of bytes kept in memory when
passing documents between different LiveCycle components. Documents that exceed this
maximum are stored on the hard drive. Use this property for performance tuning. (See “Optimizing
inline documents and impact on JVM memory” on page 215.)
●
Default disposal time-out (in seconds): The maximum amount of time during which a document
being passed between different LiveCycle components is considered active. After this time has
passed, any files used to store this document are subject to removal. Use this property to control the
usage of disk space.
●
Use NFS protocol (Windows only): Select this option when deploying LiveCycle products in a
clustered environment. Additional NFS software should be installed on your computer running
Windows before enabling this option. This option does not affect deployments on Linux or UNIX.
●
Global storage directory: A path to a shared directory used to store long-lived documents that are
passed between LiveCycle products. LiveCycle Workflow uses this directory to share process-related
files among cluster nodes. LiveCycle Form Manager uses this directory to store index files used for
full-text searches. Using an NFS shared directory can help to improve performance.
(LiveCycle PDF Generator) When LiveCycle PDF Generator is running as a service, to specify a
network folder for the Global storage directory property, you must use the network address of the
folder, and not the path of a mapped drive. For example, \\computer_name\temp is the network
address of the temp folder on the computer named computer_name.
For more information on the Global storage directory property, see “Optimizing inline documents
and impact on JVM memory” on page 215.
14. (LiveCycle Forms, LiveCycle Form Manager, LiveCycle Workflow, LiveCycle Assembler) (Optional) On the
Font Manager Module Configuration screen, select fonts for LiveCycle Forms to use in addition to the
Adobe LiveCycle
Configuring LiveCycle Products for Deployment
Installing and Configuring LiveCycle for WebSphere
78
fonts that are included with the product. In the Fonts directory box, type the path or browse to the
directory that contains the fonts to add, and then click Next.
Note: Your right to use fonts provided by parties other than Adobe is governed by the license
agreements provided to you by such parties in connection with those fonts, and is not covered
under your license to use Adobe software. Adobe recommends that you review and ensure you
are in compliance with all applicable non-Adobe license agreements before using non-Adobe
fonts with Adobe software, particularly with respect to use of fonts in a server environment.
15. (LiveCycle Assembler) (Optional) On the Assembler Security Group configuration screen, specify the
type of security you want to implement controlling permission to execute Assembler DDX jobs, and
then click Next. Two types of user authentication are available:
●
Type an asterisk (*) to allow any user with a valid entry in the LDAP system to log in.
●
Leave the field blank to allow any user to log in.
16. (LiveCycle Forms, LiveCycle Form Manager, LiveCycle Workflow) (Optional) On the Form Server Module
Configuration screen, accept the default values for the following properties or specify new values, and
then click Next:
●
Validation UI: The type of UI to use on HTML forms if a validation error occurs. If you select List, all
validation errors on the form are displayed as links. If you select MessageBox, each error message is
displayed in a dialog box controlled by clicking next and previous buttons. The location of the list or
buttons depends on the option selected for Validation Reporting.
●
Validation Reporting: The location in which the validation messages are displayed. Select one of
the following options:
●
Frame Left - Displays validation messages within a frame on the left side of the web browser.
●
Frame Right - Displays validation messages within a frame on the right side of the web browser.
●
Frame Top - Displays validation messages within a frame at the top of the web browser.
●
Frame Bottom - Displays validation messages within a frame at the bottom of the web browser.
●
No Frame Left - Displays validation messages in the same window on the left side of the web
browser.
●
No Frame Right - Displays validation messages in the same window on the right side of the web
browser.
●
No Frame Top - Displays validation messages in the same window at the top of the web
browser.
●
No Frame Bottom - Displays validation messages in the same window at the bottom of the web
browser.
●
None - Does not display validation messages.
●
No UI - Returns the validation messages through the API (with data). The validation messages
are not displayed on-screen.
●
No UI With Form - Returns the validation messages through the API (with the form). The
validation messages are not displayed on-screen.
●
Validation Border: The frame border size (in pixels) when Validation Reporting is set to Frame Left,
Frame Right, Frame Top, or Frame Bottom. The frame border size must be equal to or greater than 0.
●
Output Type: The type of HTML output returned to the web browser. Select Full HTML to render
the form within full HTML tags (a complete HTML page) or select Form Body to render the form
within div tags (not a complete HTML page).
Adobe LiveCycle
Configuring LiveCycle Products for Deployment
Installing and Configuring LiveCycle for WebSphere
Next step
79
●
Locale: The language to be used for validation messages sent to client devices, such as web
browsers, as part of HTML transformations. The default value is English (United States). For
information on applicable values, see “Language and Locale Combinations” in the Developing
Custom Applications guide that is installed with LiveCycle Forms.
●
Charset: The character set used to encode the output byte stream. This property is dependent on
the sFormPreference parameter specified through the API. For HTML transformations, the Form
Server Module supports character encoding values defined by the java.nio.charset package. To view
a list of supported values, go to http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html.
●
Cache Enabled: Select this option to optimize performance. This option works with the form
design’s caching property. For information on configuring this value in the form design, see Adobe
LiveCycle Designer Help.
17. (LiveCycle Forms, LiveCycle Form Manager, LiveCycle Workflow) (Optional) On the XMLForm Module
Configuration screen, accept the default values for the following properties or specify new values, and
then click Next:
●
Pool Max: The maximum number of processes that can be running. The recommended value for
PoolMax is the total number of CPUs * 2 + constant (1 or 2). When the PoolMax limit is reached,
service instances are created from PoolSize.
●
Trace Level: The trace level. The following options are available:
●
●
None - Tracing is not enabled.
●
Enter/Exit - Messages are logged each time a method is entered and exited.
●
Parameters - Messages are logged each time a method is entered and exited, and the value of
all parameters passed into each method is logged.
●
Details - Messages are logged each time a method is entered and exited, the value of all
parameters passed into each method and any extra messages are logged.
Report timing information: Select this option to monitor the start and end time of calls. You can
use this information for performance tuning.
18. On the Application Configuration and Assembly Summary screen, review the configuration details, and
then click Next.
19. On the Configure and Assemble Products Summary screen, click Next.
20. On the Tasks Completed screen, click Next (if you selected another task for Configuration Manager to
perform) or click Finish to close Configuration Manager.
Next step
You must now configure your application server. (See “Manually Configuring WebSphere 5.1.1.5” on
page 80 or “Manually Configuring WebSphere 6.0.2.9” on page 103.)
7
Manually Configuring WebSphere 5.1.1.5
This chapter describes how to manually configure the application server to prepare for the manual
deployment of LiveCycle products in a non-clustered environment. For information on how to
automatically configure your application server, see “Automatically Configuring LiveCycle Products” on
page 47.
The procedures in this chapter are for configuring the application server for all LiveCycle products. If a
specific product requires a different process, the steps are highlighted. If you previously configured your
application server for deploying other LiveCycle products, you do not need to perform the procedures in
this chapter again.
This chapter assumes that you have installed your LiveCycle products, configured your database, and
created a database user account. If you have not done this, see “Preparing Your Environment” on page 30.
Before configuring WebSphere and deploying LiveCycle products, you must perform the following tasks:
●
Configure various WebSphere and database settings. (See“Configuring Oracle 9i or Oracle 10g” on
page 82, “Configuring DB2” on page 83, or “Configuring SQL Server” on page 85)
●
Configure JMS resources for WebSphere. (See “Configuring JMS resources for WebSphere with
embedded messaging” on page 86.)
Before configuring WebSphere and deploying LiveCycle products, you must have the following tasks
completed:
●
Install WebSphere. For the supported versions, see “Supported software” on page 16.
●
Ensure that WebSphere is running. If your web server is not running on the application server, you must
update the web server configuration to allow access to the application server.
●
Disable the CORBA time-out. (See “Disabling the CORBA time-out” on page 80.)
●
Configure JVM arguments to enable UTF-8 encoding. (See “Configuring the JVM arguments” on
page 81.)
●
(LiveCycle PDF Generator, LiveCycle Assembler) Configure the server transaction time-out. (See
“Configuring the server transaction time-out” on page 81.)
●
(LiveCycle Workflow) Update the web server configuration file. (See “Updating the web server
configuration files” on page 81.)
Disabling the CORBA time-out
You need to disable the CORBA time-out setting on WebSphere. This procedure does not apply if you are
only installing LiveCycle Workflow.
➤ To disable the CORBA time-out:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers >
[server name] > Configuration > Container Services > ORB Service.
2. In the Request timeout box, type 0.
3. Click Apply and, under Save to Master Configuration, click Save.
80
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring the JVM arguments
81
Configuring the JVM arguments
You must configure the JVM arguments on your application server.
➤ To configure JVM arguments:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers >
[server name].
2. On the Configuration tab, under Additional Properties, click Process Definition.
3. Under Additional Properties, click Java Virtual Machine and, in the Generic JVM arguments box, type
the following code:
-Djava.awt.headless=true
(LiveCycle Workflow and LiveCycle Form Manager) Also add the following code:
-Dadobe.workflow.engine.publish-process-events=false
-Dadobe.workflow.scheduler.java.naming.provider.url=
iiop://<host name>:<bootstrap address port>
(LiveCycle Form Manager) Also add the following code:
-Dorg.apache.lucene.writeLockTimeout=10000
4. Click Apply, click Apply again, and then save your changes to the Master Configuration.
Configuring the server transaction time-out
This section applies to LiveCycle Assembler and LiveCycle PDF Generator only.
You must configure the server transaction time-out setting on WebSphere.
Note: The default transaction time-out, which is 600 seconds, is set during the product configuration
using Configuration Manager. (See “Configuring LiveCycle Products for Deployment” on page 76.)
➤ To configure the server transaction time-out:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers >
[server name].
2. Under Additional Properties, select Transaction Service.
3. In the Total transaction lifetime timeout box, type 600.
4. Click OK, click Save, and then, under Save to Master Configuration, click Save.
5. Restart WebSphere.
Updating the web server configuration files
This section applies to LiveCycle Workflow only.
You must update the web server configuration files on WebSphere.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Connecting WebSphere to the LiveCycle database
82
➤ To update the web server configuration file:
1. In the WebSphere Administrative Console navigation tree, select Environment > Update Web Server
Plugin.
2. Click OK.
Connecting WebSphere to the LiveCycle database
You must configure the data source to connect Websphere to your LiveCycle deployment:
●
“Configuring Oracle 9i or Oracle 10g” on page 82
●
“Configuring DB2” on page 83
●
“Configuring SQL Server” on page 85
Configuring Oracle 9i or Oracle 10g
To enable WebSphere and your LiveCycle deployment to connect to the Oracle database, you must
complete the following tasks:
●
Configure JDBC information
●
Configure J2C authentication information
●
Create a data source on WebSphere
Before performing the following procedures, you must have already create an Oracle database and a user
on the database. (See “Creating an Oracle database” on page 30.)
➤ To create a data source on WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Environment > Manage WebSphere
Variables.
2. To set the variable scope, select Cell and click Apply.
3. Click New, in Name box type ORACLE_JDBC_DRIVER_PATH and, in the Value box, type:
${WAS_INSTALL_ROOT}/db_driver
This directory was created when you prepared the WebSphere environment. (See “Installing database
drivers” on page 44.)
4. Click Apply, and then save your changes to the Master Configuration.
5. In the navigation tree, select Resources > JDBC Providers.
6. For Scope, select Cell and click Apply.
7. Click New, select Oracle JDBC Driver in the list, click Apply, and then click Apply again.
8. Under Additional Properties, select Data Sources.
9. Click New and, in the Name box, type a name for the data source (for example, LiveCycleDS).
10. In the JNDI Name field, type IDP_DS and click Apply.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring DB2
83
11. Under Related Items, select J2C Authentication Data Entries.
12. Click New and, in the Alias box, type a name (for example, MyAlias).
13. Type the user ID and password that corresponds with the user you created on the database, click
Apply, click OK, and then save your changes to the Master Configuration.
14. Navigate back to Resources > JDBC Providers > Oracle JDBC Driver > Data Sources > LiveCycleDS.
15. Under General Properties, set both Component-managed Authentication Alias and
Container-managed Authentication Alias to [computer_name]/MyAlias.
16. Under Additional Properties, click Custom Properties and select URL.
17. In the Value box, type the following value:
jdbc:oracle:thin:@[server-name]:1521:[service-name]
where [server-name] is your Oracle 9i or Oracle 10g server name and [service-name] is your
database.
18. Click Apply, and then save your changes to the Master Configuration.
19. To test the data source connection, navigate to Resources > JDBC Providers > Oracle JDBC Driver >
Data Sources.
20. Select the checkbox next to the data source you created and click Test Connection. A message is
displayed describing the test results.
Configuring DB2
To enable WebSphere and your LiveCycle deployment to connect to the DB2 database, you must complete
the following tasks:
●
Configure JDBC information.
●
Configure J2C authentication information.
●
Create a data source on WebSphere.
Before performing the following procedures, you must have already created a DB2 database and a user on
the database. (See “Creating a DB2 database” on page 31.)
➤ To set up a data source on WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Environment > Manage WebSphere
Variables.
2. To set the variable scope, select Cell and click Apply. The scope needs to be the same as the scope of
the JDBC provider that you configure later in this task.
3. Click New, in Name box type DB2_JDBC_DRIVER_PATH and, in the Value box, type:
${WAS_INSTALL_ROOT}/db_driver
This directory was created when you prepared the WebSphere environment. (See “Installing database
drivers” on page 44.)
4. Click OK, and then save your changes to the Master Configuration.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring DB2
84
5. In the navigation tree, select Resources > JDBC Providers.
6. For Scope, select Cell and in the right panel, click New, select DB2 Universal JDBC Driver Provider in
the list, click Apply, and then click Apply again.
7. Under Additional Properties, select Data Sources.
8. Click New and type a name for the data source (for example, LiveCycleDS).
9. In the JNDI Name box, type IDP_DS, and then click Apply.
10. Under Related Items, select J2C Authentication Data Entries.
11. Click New and, in the Alias box, type a name (for example, MyAlias).
12. Type the user ID and password that correspond with the user credentials that can access the database
and click Apply.
13. Save your changes to the Master Configuration.
14. Navigate back to Resources > JDBC Providers > DB2 Universal JDBC Driver Provider > Data
Sources and select the name for the data source (for example, LiveCycleDS).
15. Under General Properties, set both Component-managed Authentication Alias and
Container-Managed Authentication Alias to [computer_name]/MyAlias.
16. From Mapping-Configuration Alias, select DefaultPrincipalMapping and click Apply.
17. Under Additional Properties, click Custom Properties and specify values for the following properties:
●
databaseName: The database name of the DB2 database in which the LiveCycle database resides.
●
serverName: The name or IP address of the DB2 server to which you are connecting.
●
portNumber: The port of the DB2 server to which you are connecting. The default value is 50000.
●
resultSetHoldability: Specifies whether cursors remain open after a commit operation. Set to 1.
●
driverType: Determines which driver to use for connections. Set to 4.
18. (LiveCycle PDF Generator) Navigate back to JDBC Providers > DB2 Universal JDBC Driver Provider >
Data Sources > LiveCycleDS.
19. (LiveCycle PDF Generator) Under Additional Properties, select Connection Pool and, in the Max
Connections box, type 30.
20. (LiveCycle PDF Generator) Click Apply, click OK, and then click Save.
21. Save your changes to the Master Configuration.
22. Restart the application server so that it picks up the db2jdbc jar files.
23. To test the data source connection, navigate to Resources > JDBC Providers > DB2 Universal JDBC
Driver Provider > Data Sources.
24. Select the checkbox next to the data source you created and click Test Connection.
A message is displayed describing the test results. If the test connection fails and you are using
WebSphere variables for the path to the db2jdbc jar files, try providing the full file system path to the
files.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring SQL Server
85
25. If you already had a data source configured and created a new one, stop and restart the application
server.
Configuring SQL Server
To enable WebSphere and your LiveCycle deployment to connect to the SQL Server database, you must
complete the following tasks:
●
Configure JDBC information
●
Configure J2C authentication information
●
Create a data source on WebSphere
Before performing the following procedures, you must have already created a SQL Server database and a
user on the database. (See “Creating a SQL Server database” on page 33.)
➤ To configure JDBC information:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. For Scope, select Cell and click Apply.
3. Click New. From the JDBC Providers menu, select WebSphere embedded ConnectJDBC driver for
MS SQL Server and click Apply.
4. In the Name box, type: SQL Server JDBC Provider
5. In the Implementation Classname box, type:
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource
6. Click OK.
➤ To configure J2C authentication information:
1. In the WebSphere Administrative Console navigation tree, select Security > JAAS Configuration >
J2C Authentication Data.
2. Click New and, in the Alias box, enter a name for the alias (for example, SQLServer).
3. In the User ID box, enter the user name of the user account you created on the database and, in the
Password box, enter the corresponding password.
4. Click Apply, click OK, and then save to the Master Configuration.
➤ To configure a SQL Server data source:
1. In the WebSphere Administrative Console navigation tree, select Security > JAAS Configuration >
J2C Authentication Data.
2. Click SQL Server JDBC Provider and, under Additional Properties, select Data Sources.
3. Click New.
4. In the Name box, enter a name for the data source (for example, LiveCycleDS).
5. In the JNDI Name box, type: IDP_DS
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging or WebSphere MQ
86
6. In the Datasource Helper Classname box, type:
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper
7. In the Component-managed Authentication Alias and Container-managed Authentication Alias
menus, select the SQL Server alias that you created in step 2.
8. In the Mapping-Configuration Alias menu, select DefaultPrincipalMapping and click Apply.
9. Under Additional Properties, click Connection Pool, change the value of Max Connections to 30,
and then click OK.
10. Under Additional Properties, click Custom Properties, click serverName and, in the Value box, type
the name of the server where your SQL Server database resides, and then click OK.
11. In Custom Properties, click databaseName and, in the Value box, enter the name of your SQL Server
database, and then click OK.
12. In Custom Properties, click Select Method and, in the Value box, type cursor, and then click OK.
13. In Custom Properties, click enable2Phase.
14. In the value box, type true and click OK.
15. In Custom Properties, ensure that preTestSQLString is set to an appropriate value.
16. In Custom Properties, click SendStringParameterAsUnicode.
17. In the Value box, type true and click OK.
18. Save your changes to the Master Configuration.
19. Test your connection by navigating to Resources > JDBC Providers > SQL Server JDBC Provider >
Data Sources and clicking Test Connection.
Configuring embedded messaging or WebSphere MQ
Depending on the LiveCycle products that you are installing and the version of WebSphere that you are
using, you will need to install and configure either WebSphere embedded messaging or WebSphere MQ.
If you are using WebSphere 5.1.1.5 with LiveCycle Workflow or LiveCycle Form Manager, or installing
LiveCycle PDF Generator to work with LiveCycle Workflow, you must install and configure WebSphere MQ.
(See “Configuring JMS resources for WebSphere MQ” on page 93.)
If you are using WebSphere 5.1.1.5 with LiveCycle products other than LiveCycle Workflow or
LiveCycle Form Manager, you must configure WebSphere embedded messaging. (See “Configuring JMS
resources for WebSphere with embedded messaging” on page 86.)
Note: If you are using LiveCycle Forms, you do not need to configure embedded messaging or WebSphere
MQ.
Configuring JMS resources for WebSphere with embedded messaging
To configure JMS resources for WebSphere using embedded messaging, you must complete the following
tasks:
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere with embedded messaging
●
Add required queues to the WebSphere embedded JMS server.
●
Set up WebSphere queue connection factories.
●
Set up WebSphere topic connection factories
●
Set up Websphere queue destinations
●
Set up WebSphere topic destinations
●
Set up WebSphere listener ports
87
This section describes how to manually configure JMS resources for WebSphere. You can also use
Configuration Manager to automatically perform this task. (See “Automatically Configuring LiveCycle
Products” on page 47.)
➤ To add required queues to the WebSphere embedded JMS server:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers.
2. Select the server that you are configuring (for example, server1) and, under Additional Properties,
select Server Components.
3. Select JMS Servers and add the following queues to the Queue names list.
Queue name
Applicable LiveCycle products
adobe_ObjectDeleteQueue
LiveCycle Form Manager or LiveCycle Workflow
adobe_PECommandQueue
LiveCycle Form Manager or LiveCycle Workflow
adobe_PEDCommandQueue
LiveCycle Form Manager or LiveCycle Workflow
adobe_PEDLongLivedQueue
LiveCycle Form Manager or LiveCycle Workflow
adobe_PEInteractionQueue
LiveCycle Form Manager or LiveCycle Workflow
adobe_PELongLivedQueue
LiveCycle Form Manager or LiveCycle Workflow
adobe_PEScheduledMsgQueue
LiveCycle Form Manager or LiveCycle Workflow
AESJobQueue
LiveCycle PDF Generator
PDFGCompletedJobsQueue
LiveCycle PDF Generator
4. Click OK.
➤ To set up WebSphere queue connection factories:
1. In the WebSphere Administrative Console navigation tree, select Resources > WebSphere JMS
Provider.
2. In the Configuration tab, under Scope, select Cell and click Apply.
3. Under Additional Properties, click WebSphere Queue Connection Factories and click New.
4. (LiveCycle Workflow, LiveCycle Form Manager) Specify the following values for the properties and click
OK:
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere with embedded messaging
●
Name: QueueConnectionFactory
●
JNDI Name: QueueConnectionFactory
●
Mapping-Configuration Alias: DefaultPrincipalMapping
●
XA enabled: Deselect the check box.
88
5. (LiveCycle Workflow, LiveCycle Form Manager) In the table, select the connection factory you created.
6. (LiveCycle Workflow, LiveCycle Form Manager) Under Additional Properties, click Connection Pool
and, in the Max Connections box, type 30, and then click OK.
7. (LiveCycle PDF Generator) In the Name box, type AESQueueConnectionFactory and, in the JNDI
Name box, type jms/QueueConnectionFactory, and then click OK.
8. Save your changes to the Master Configuration.
➤ To set up WebSphere topic connection factories:
1. In the WebSphere Administrative Console navigation tree, select Resources > WebSphere JMS
Provider, and create the following topic connection factories by completing steps 2 to 8 for each
connection factory.
(LiveCycle Workflow, LiveCycle Form Manager)
Topic connection factory
JNDI Name
Scope
Port
TopicConnectionFactory
TopicConnectionFactory
Node
POFConnectionFactory
POFConnectionFactory
Node
RegistryTopicConnectionFactory
RegistryTopicConnectionFactory
Cell
Topic connection factory
JNDI Name
Scope
Port
AESTopicConnectionFactory
jms/TopicConnectionFactory
Node
QUEUED
QUEUED
(LiveCycle PDF Generator)
2. Set the Scope as indicated in the table in step 1.
3. Under Additional Properties, click WebSphere Topic Connection Factories and click New.
4. In the Name and JNDI name boxes, type the values as indicated in the table above.
5. For all of the topic connection factories, in the Mapping-Configuration Alias list, select
DefaultPrincipalMapping.
6. Set the Port as indicated in the table above and click OK.
7. Under Additional Properties, click Connection Pool and, in the Max Connections box, type the
following value and click OK:
●
(LiveCycle PDF Generator) 10
●
(All other LiveCycle products) 30
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere with embedded messaging
89
8. Under Additional Properties, click Session Pools and, in the Max Connections box, type the following
value and click OK:
●
(LiveCycle PDF Generator) 10
●
(All other LiveCycle products) 30
9. Save your changes to the Master Configuration.
➤ To set up Websphere queue destinations:
1. In the WebSphere Administrative Console navigation tree, select Resources > WebSphere JMS
Provider, and create the following queue destinations by completing steps 2 to 4 for each queue
destination.
(LiveCycle Workflow, LiveCycle Form Manager)
Queue destination
JNDI name
Scope
adobe_ObjectDeleteQueue
adobe_ObjectDeleteQueue
Cell
adobe_PECommandQueue
adobe_PECommandQueue
Cell
adobe_PEDCommandQueue
adobe_PEDCommandQueue
Cell
adobe_PEDLongLivedQueue
adobe_PEDLongLivedQueue
Cell
adobe_PEInteractionQueue
adobe_PEInteractionQueue
Cell
adobe_PELongLivedQueue
adobe_PELongLivedQueue
Cell
adobe_PEScheduledMsgQueue
adobe_PEScheduledMsgQueue
Cell
Queue destination
JNDI name
Scope
AESJobQueue
queue/AESJobQueue
Node
PDFGCompletedJobsQueue
queue/PDFGCompletedJobsQueue
Node
(LiveCycle PDF Generator)
2. Set the Scope as indicated in the table in step 1.
3. Under Additional Properties, select WebSphere Queue Destinations and click New.
4. In the Name and JNDI Name boxes, type the values as indicated in the table in step 1, and then click
OK.
➤ To set up WebSphere topic destinations:
1. In the WebSphere Administrative Console navigation tree, select Resources > WebSphere JMS
Provider, and create the following topic destinations by completing steps 2 to 7 for each topic
destination.
(LiveCycle Form Manager, LiveCycle Workflow)
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere with embedded messaging
Name and Topic destination
JNDI Name
Scope
adobe_POFObjectTopic
topic/adobe_POFObjectTopic
Node
adobe_POFSchemaTopic
topic/adobe_POFSchemaTopic
Node
adobe_ProcessEventTopic
topic/adobe_ProcessEventTopic
Node
adobe_TaskEventTopic
topic/adobe_TaskEventTopic
Node
adobe_TemplateEventTopic
topic/adobe_TemplateEventTopic
Node
adobe_RegistryCacheMonitorTopic
topic/adobe_RegistryCacheMonitorTopic
Cell
Name and Topic destination
JNDI Name
Scope
AesConfigUpdatesTopic
topic/AesConfigUpdatesTopic
Node
Name and Topic destination
JNDI Name
Scope
WatchedFolderConfigManagerTopic
topic/WatchedFolderConfigManagerTopic
Node
90
(LiveCycle PDF Generator)
(Watched Folder)
2. Set the Scope as indicated in the table in step 1.
3. Under Additional Properties, select WebSphere Topic Destinations and click New.
4. In the Name, JNDI name, and Topic boxes, type the values as indicated in the table in step 1.
5. In the Priority list, select APPLICATION DEFINED.
6. In the Expiry list, select APPLICATION DEFINED.
7. In the Persistence list, select PERSISTENT.
For adobe_RegistryCacheMonitorTopic, in the Persistence list, select NON PERSISTENT.
For AesConfigUpdatesTopic, in the Persistence list, select APPLICATION DEFINED.
➤ To set up WebSphere listener ports:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers and,
in the table, select the server instance that you are configuring.
2. Under Additional Properties, select Message Listener Service and create the following listener ports
by completing steps 3 to 4 for each listener port.
(LiveCycle Workflow, LiveCycle Form Manager)
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere with embedded messaging
91
Listener port
Connection factory JNDI name
Destination JNDI name
AdobeMDBListener
QueueConnectionFactory
queue/adobe_PECommand
Queue
AdobeMDBPATListener
TopicConnectionFactory
topic/adobe_POFObjectTopic
AdobeTemplateEventMDB
TopicListener
TopicConnectionFactory
topic/adobe_TemplateEvent
Topic
AdobeMDBTopicListener
TopicConnectionFactory
topic/adobe_ProcessEventType
adobe_RegistryCacheMonitor
MDBPort
RegistryTopicConnection
Factory
topic/adobe_RegistryCache
MonitorTopic
adobe_TaskEventTopicListener TopicConnectionFactory
topic/adobe_TaskEventTopic
(LiveCycle PDF Generator)
Listener port
Connection factory JNDI name
Destination JNDI name
DequeuePort
jms/QueueConnectionFactory
queue/AESJobQueue
ConfigUpdatesListenerPort
jms/TopicConnectionFactory
topic/AesConfigUpdatesTopic
PDFGCompletedJobsListener
Port
jms/QueueConnectionFactory
queue/PDFGCompletedJobs
Queue
PsDequeuePort
jms/QueueConnectionFactory
queue/AESJobQueue
Listener port
Connection factory JNDI name
Destination JNDI name
WatchedFolderTopicListener
jms/TopicConnectionFactory
topic/WatchedFolderConfig
ManagerTopic
(Watched Folder)
3. Under Additional Properties, select Listener Ports and click New.
4. In the Name, Connection factory JNDI name, and Destination JNDI name boxes, type the values as
indicated in the table above, and then set the Initial State to Started.
5. For PsDequeuePort, in the Maximum Sessions box, type 3.
6. In the Maximum messages box, type the following value and click OK:
●
(LiveCycle PDF Generator) 1
●
(All other LiveCycle products) 5
7. In the Maximum retries box, type the following value and click OK:
●
(LiveCycle PDF Generator) 0
●
(All other LiveCycle products) 10
8. Save your changes to the Master Configuration.
9. Shut down and restart the WebSphere Application Server.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere with embedded messaging
92
➤ To configure JMS resources for Watched Folder:
1. In the Websphere Administrative console navigation tree, select Servers > Application Servers.
2. Select the server where you want to deploy the LiveCycle.ear file (the default is server1) and, under
Additional Properties, select Message Listener Service.
3. Select Listener Port, and then select New Listener Port.
4. Type the following information for New Listener Port:
●
Name: AdobeWatchedFolderTopicListener
●
Initial State: Started
●
Description: For WatchedFolder MDB
●
Connection factory JNDI name: TopicConnectionFactory
●
Destination JNDI name: topic/WatchedFolderConfigManagerTopic
5. Click Apply, and then click Save.
6. In the navigation tree, select either Resources > Websphere JMS Provider or Websphere MQ JMS
Provider.
7. Depending on your selection in the previous step, perform the following steps:
●
●
Websphere JMS Provider
●
For Scope, select Node, and then click Apply.
●
Under Additional Properties, select Websphere Topic Destinations, and then click New.
●
Type the following information for Topic Destination:
●
Name: WatchedFolderConfigManagerTopic
●
JNDI Name: topic/WatchedFolderConfigManagerTopic
●
Topic: WatchedFolderConfigManagerTopic
Websphere MQ JMS Provider
●
For Scope, select Server, and then click Apply.
●
Under Additional Properties, select Websphere MQ Topic Destinations, and then click New.
●
Type the following information for Topic Destination:
●
Name: WatchedFolderConfigManagerTopic
●
JNDI Name: topic/WatchedFolderConfigManagerTopic
●
Category: LiveCycle
●
Persistence: PERSISTENT
●
Base Topic Name: MQJMS/ADOBE/WATCHEDFOLDER/CONFIG_MANAGER_TOPIC
8. Click Apply, and then click Save.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
93
Configuring JMS resources for WebSphere MQ
This section describes how to configure JMS resources for WebSphere MQ. This section assumes that you
have already installed and prepared WebSphere MQ for deployment. (See “Preparing WebSphere MQ” on
page 39.)
Configuring JMS resources
This section applies to LiveCycle Form Manager, LiveCycle Workflow, and LiveCycle PDF Generator
only.
You must create four destinations and connection factories for WebSphere MQ, as described in the
following sections:
●
“Creating WebSphere MQ queue destinations” on page 93
●
“Creating WebSphere MQ topic destinations” on page 95
●
“Creating a queue connection factory” on page 96
●
“Creating topic connection factories” on page 98
●
“Configuring WebSphere MQ JMS provider for Watched Folder” on page 100
If you are using WebSphere 5.1.1.5 as your application server with LiveCycle Workflow, you must configure
WebSphere MQ 5.3.0.1.
This section describes how to configure WebSphere MQ 5.3.0.1 in a non-clustered environment.
In this document, [MQ_root] indicates the location where WebSphere MQ is installed. The default install
location varies depending on the operating system you are using:
●
(Windows) c:\Program Files\ibm\WebSphere MQ
●
(Solaris, Linux) /opt/mqm
●
(AIX) /usr/mqm
Before you perform the procedures in this section, you must have already installed WebSphere MQ and
performed preliminary configurations.
Creating WebSphere MQ queue destinations
The following procedure describes how to create the queue destinations required for WebSphere MQ.
➤ To create the WebSphere MQ queue destinations:
1. In the navigation tree of the WebSphere Administrative Console, click Resources > WebSphere MQ
JMS Provider.
2. In the right pane, under Scope, select Cell and click Apply.
3. Click WebSphere MQ Queue Destinations.
4. Click New and create the following queue destinations by completing step 5 for each queue
destination.
(LiveCycle Workflow, LiveCycle Form Manager)
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
Queue destination name
JNDI name
Base queue name
adobe_ObjectDeleteQueue
queue/adobe_ObjectDeleteQueue
ADOBE.WORKFLOW.OBJECT
_DELETE.QUEUE
adobe_PECommandQueue
queue/adobe_PECommandQueue
ADOBE.WORKFLOW.PE
_COMMAND.QUEUE
adobe_PEDCommandQueue
queue/adobe_PEDCommandQueue
ADOBE.WORKFLOW.PED
_COMMAND.QUEUE
adobe_PEDLongLivedQueue
queue/adobe_PEDLongLivedQueue
ADOBE.WORKFLOW.PED
_LONGLIVED.QUEUE
adobe_PEInteractionQueue
queue/adobe_PEInteractionQueue
ADOBE.WORKFLOW.PE
_INTERACTION.QUEUE
adobe_PELongLivedQueue
queue/adobe_PELongLivedQueue
ADOBE.WORKFLOW.PE
_LONGLIVED.QUEUE
adobe_PEScheduledMsg
Queue
queue/adobe_PEScheduledMsg
Queue
ADOBE.WORKFLOW.PE
_SCHEDULEDMSG.QUEUE
(LiveCycle PDF Generator)
Queue destination name
JNDI name
Base queue name
AESJobQueue
queue/AESJobQueue
ADOBE.PDFG.AESJOB.
QUEUE
PDFGCompletedJobsQueue
queue/PDFGCompletedJobsQueue
ADOBE.PDFG.PDFG
COMPLETEDJOBS.QUEUE
94
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
95
5. Specify the following values for the properties, and then click OK:
●
Scope: Cell
●
Category: LiveCycle
●
Base Queue Manager Name: queue_manager_name (queue manager created in step 4. on page
93)
●
Queue Manager Host: MQ_host
●
Queue Manager Port: MQ_port (port specified in step 5. on page 42 for UNIX or in step 6. on page
43 for Windows)
●
Server Connection Channel Name: SYSTEM.DEF.SVRCONN
●
User ID: MQ_userid (as created in step 3. on page 41)
●
Password: password for MQ_userid
Creating WebSphere MQ topic destinations
The following procedure describes how to create the topic destinations required for WebSphere MQ.
➤ To create the WebSphere MQ topic destinations:
1. In the navigation tree of the WebSphere Administrative Console, click Resources > WebSphere MQ
JMS Provider.
2. In the right pane, set the Scope as indicated in the table below.
3. Select WebSphere MQ Topic Destinations.
4. Click New and create the following topic destination by completing step 5 for each topic destination.
(LiveCycle Workflow, LiveCycle Form Manager)
Scope
Name
JNDI name
Base topic name
Cell
adobe_Registry
CacheMonitorTopic
topic/adobe_Registry
CacheMonitorTopic
MQJMS/ADOBE/EBXML/REGISTRY
_CACHE_MONITOR_TOPIC
Server
adobe_POFObject
Topic
topic/adobe_POFObject
Topic
MQJMS/ADOBE/WORKFLOW/POF
_ OBJECT_TOPIC
Server
adobe_POFSchema topic/adobe_POFSchema
Topic
Topic
MQJMS/ADOBE/WORKFLOW/POF
_ SCHEMA_TOPIC
Server
adobe_Process
EventTopic
topic/adobe_Process
EventTopic
MQJMS/ADOBE/WORKFLOW/PROCESS
_EVENT_TOPIC
Server
adobe_TaskEvent
Topic
topic/adobe_TaskEvent
Topic
MQJMS/ADOBE/WORKFLOW/TASK
_ EVENT_TOPIC
Server
adobe_Template
EventTopic
topic/adobe_Template
EventTopic
MQJMS/ADOBE/WORKFLOW/
TEMPLATE_EVENT_TOPIC
(LiveCycle PDF Generator)
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
Scope
Name
JNDI name
Base topic name
Cell
AesConfigUpdates
Topic
topic/AesConfigUpdates
Topic
MQJMS/ADOBE/PDFG/
AESCONFIGUPDATES_TOPIC
96
(Watched Folder)
Scope
Name
JNDI name
Base topic name
Server
WatchedFolder
ConfigManager
Topic
topic/WatchedFolder
ConfigManagerTopic
MQJMS/ADOBE/WATCHEDFOLDER/
CONFIG/_MANAGER_TOPIC
5. Specify the following values for the properties, and then click OK:
●
Scope: Scope (Scope specified in step 4. on page 95)
●
Category: LiveCycle
●
Persistence: PERSISTENT
●
Name: Name (name specified in step 4. on page 95)
●
JNDI name: JNDI name (JNDI name specified in step 4. on page 95)
●
Base topic name: Base topic name (base topic name specified in step 4. on page 95)
Creating a queue connection factory
The procedures in this section describe how to configure a J2C Authentication Data Entry (for the local
user you created in step 3. on page 41), and a queue connection factory for WebSphere MQ.
When you complete this procedure, you must also configure the session pools and connection pool. (See
“To configure the session pool:” on page 97 and “To configure the connection pool:” on page 97.)
➤ To create a J2C Authentication Data Entry:
1. In the navigation tree of the WebSphere Administration Console, click Security > JAAS Configuration
> J2C Authentication Data.
2. In the right pane, click New.
3. Set the Alias property to a meaningful name, such as mquser.
4. Set the User ID and Password properties to the user name and password you created in step 3. on
page 41.
5. Click OK and save your changes to the master configuration.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
97
➤ To create a queue connection factory:
1. In the navigation tree of the WebSphere Administrative Console, click Resources > WebSphere MQ
JMS Provider.
2. In the right pane, set Scope to Cell and click Apply.
3. Click WebSphere MQ Queue Connection Factories.
4. Click New, specify the following values for the properties of the new queue connection, and then click
OK.
●
(LiveCycle Workflow, LiveCycle Form Manager) Name: QueueConnectionFactory
●
(LiveCycle Workflow, LiveCycle Form Manager) JNDI Name: QueueConnectionFactory
●
(LiveCycle PDF Generator) Name: AESQueueConnectionFactory
●
(LiveCycle PDF Generator) JNDI Name: jms/QueueConnectionFactory
●
Category: LiveCycle
●
Container-managed Authentication Alias: MQ_user_alias (alias you created in step 3. on page 96)
●
Queue Manager: queue_manager_name
●
Host: MQ_host
●
Port: MQ_port
●
Channel: SYSTEM.DEF.SVRCONN
●
Transport Type: CLIENT
●
XA enabled: Deselect the check box for QueueConnectionFactory.
●
XA enabled: Select the check box for AESQueueConnectionFactory.
➤ To configure the session pool:
1. Click the name of the queue connection factory that you just created.
2. In the Additional Properties section, click Session Pools.
3. Specify the following values for the properties of the session pool, and then click OK.
●
Connection Timeout: 180
●
Max Connections: 10
●
Min Connections: 10
➤ To configure the connection pool:
1. Click the name of the queue connection factory that you just created.
2. In the Additional Properties section, click Connection Pool.
3. Specify the following values for the properties of the connection pool, and then click OK.
●
Connection Timeout: 180
●
Max Connections: 10
●
Min Connections: 10
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
98
Creating topic connection factories
The following procedure describes how to create topic connection factories for WebSphere MQ. When you
complete this procedure, you must also configure the session pools and connection pools. (See “To
configure the session pools:” on page 99 and “To configure the connection pools:” on page 99.)
➤ To create a topic connection factory:
1. In the navigation tree of the WebSphere Administrative Console, click Resources > WebSphere MQ
JMS Provider.
2. In the right pane, set Scope to either Cell or Server, as indicated in the table below.
3. Select WebSphere MQ Topic Connection Factories.
4. Click New and create the following topic connection factories by completing step 5 for each topic
connection.
(LiveCycle Workflow, LiveCycle Form Manager)
Scope
Name
JNDI name
Category
Cell
RegistryTopicConnectionFactory
RegistryTopicConnectionFactory
LiveCycle
Server
POFConnectionFactory
POFConnectionFactory
LiveCycle
Server
TopicConnectionFactory
TopicConnectionFactory
LiveCycle
(LiveCycle PDF Generator)
Scope
Name
JNDI name
Category
Cell
AESTopicConnectionFactory
jms/TopicConnectionFactory
LiveCycle
5. Specify the following values for the properties, and then click OK:
●
Container-managed Authentication Alias: MQ_user_alias (alias you created in step 3. on page 96)
●
Host: MQ_host
●
Port: MQ_port
●
Transport Type: CLIENT
●
Channel: SYSTEM.DEF.SVRCONN
●
Queue Manager: queue_manager_name
●
Broker Control Queue: SYSTEM.BROKER.CONTROL.QUEUE
●
Broker Queue Manager: queue_manager_name
●
Broker Publication Queue: SYSTEM.BROKER.DEFAULT.STREAM
●
Broker Subscription Queue: SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
●
Broker CC Subscription Queue: SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
●
Broker Version: Basic
●
Clone Support: Deselect the check box
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
99
➤ To configure the connection pools:
1. Click the name of one of the topic connection factories that you just created.
2. In the Additional Properties section, click Connection Pool.
3. Specify the following values for the properties of the connection pool, and then click OK:
●
Connection Timeout: 180
●
Max Connections: 10
●
Min Connections: 10
4. Repeat this procedure for each of the topic connection factories.
➤ To configure the session pools:
1. Click the name of one of the topic connection factories that you just created.
2. Under the Additional Properties section, click Session Pools.
3. Specify the following values for properties of the session pool, and then click OK:
●
Connection Timeout: 180
●
Max Connections: 10
●
Min Connections: 10
4. Repeat this procedure for each of the topic connection factories.
Configuring the listener ports
You must configure several listener ports for each server defined in WebSphere Application Server.
➤ To configure the listener ports:
1. In the navigation tree of the WebSphere Administrative Console, click Servers > Application Servers.
2. In the right pane, click the name of the server.
3. Click Message Listener Service.
4. Click Listener Ports.
5. Click New and create the following listener ports by completing step 6 for each listener port.
(LiveCycle Workflow, LiveCycle Form Manager)
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Configuring JMS resources for WebSphere MQ
100
Name
Connection factory JNDI
name
AdobeMDBListener
QueueConnectionFactory
queue/adobe_PECommand
Queue
AdobeMDBPATListener
TopicConnectionFactory
topic/adobe_POFObjectTopic
AdobeMDBTopicListener
TopicConnectionFactory
topic/adobe_ProcessEventType
AdobeTemplateEventMDBTopic
Listener
TopicConnectionFactory
topic/adobe_TemplateEventTopic
adobe_RegistryCacheMonitor
MDBPort
RegistryTopicConnection
Factory
topic/adobe_RegistryCacheMonitor
Topic
adobe_TaskEventTopicListener
TopicConnectionFactory
topic/adobe_TaskEventTopic
Connection factory JNDI
name
Destination JNDI name
Destination JNDI name
(LiveCycle PDF Generator)
Name
DequeuePort
jms/QueueConnection
Factory
queue/adobe_AESJobQueue
ConfigUpdatesListenerPort
jms/TopicConnection
Factory
topic/AESConfigUpdatesTopic
PDFGCompletedJobsListener
Port
jms/QueueConnection
Factory
queue/PDFGCompletedJobsQueue
PsDequeuePort
jms/QueueConnection
Factory
queue/adobe_AESJobQueue
(Watched Folder)
Listener port
WatchedFolderTopicListener
Connection factory JNDI
name
Destination JNDI name
jms/TopicConnection
Factory
topic/WatchedFolderConfig
ManagerTopic
6. Specify the following values for the properties, and then click OK:
●
Initial State: Started
●
Maximum sessions: 5
●
Maximum retries: 10
●
Maximum messages: 1
Configuring WebSphere MQ JMS provider for Watched Folder
The following procedure describes how to configure WebSphere MQ JMS providers for Watched Folder.
Adobe LiveCycle
Manually Configuring WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Checking your WebSphere MQ configuration
101
➤ To configure Websphere MQ for Watched Folder:
1. Run the JMSAdmin tool to create JMS MQ Definitions for WatchedFolderConfigManagerTopic.
2. Navigate to the [MQ_Root]/java/bin directory (where [MQ_Root] is the installation of your Websphere
MQ). The default location of [MQ_Root] is C:\Program Files\ibm\WebSphere MQ or /usr/mqm.
3. From a command prompt, enter the following command:
●
(Linux, UNIX) JMSAdmin
●
(Windows) JMSAdmin.exe
4. From the InitCtx> prompt, type:
DEFINE T(topic/WatchedFolderConfigManagerTopic) bver(V1)
TOPIC(MQJMS/ADOBE/WATCHEDFOLDER/CONFIG_MANAGER_TOPIC)
5. From the InitCtx> prompt, type: END
Note: If you receive the message “unable to bind object”, ensure that you have write access to the
cfstore/topic directory.
Checking your WebSphere MQ configuration
Before proceeding with installing other products, check that WebSphere MQ is configured properly.
➤ To check your configuration:
1. Stop and start WebSphere Application Server.
2. In the WebSphere Administrative Console navigation tree, click Resources > WebSphere MQ JMS
Provider.
3. Click WebSphere MQ Queue Destinations.
4. Click one of the queues that you created using this guide.
5. Under Additional Properties, click MQ Config and check that no errors are appearing in the Messages
area at the top of the page.
6. Repeat steps 4 and 5 for each queue that you created using this document.
7. In the navigation tree, click Servers > Application Servers.
8. In the right pane, click the name of the server.
9. Click Message Listener Service.
10. Click Listener Ports and check that all of the listener ports are started.
Next step
If you are installing and configuring LiveCycle Workflow and plan to install and configure BAM Server as
well, you must now manually configure WebSphere for use with BAM Server. (See “Configuring
WebSphere 5.1.1.5 for BAM Server” on page 139.)
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Manually Configuring WebSphere 5.1.1.5
Next step
102
If you are not installing LiveCycle Workflow, you must now deploy the products to the application server
database. (See “Manually Deploying to WebSphere 5.1.1.5” on page 116.)
8
Manually Configuring WebSphere 6.0.2.9
This chapter describes how to manually configure the application server to prepare for the manual
deployment of LiveCycle products in a non-clustered environment. For information on how to
automatically configure your application server, see “Automatically Configuring LiveCycle Products” on
page 47.
The procedures in this chapter are for configuring the application server for all LiveCycle products. If a
specific product requires a different process, the steps are highlighted. If you previously configured your
application server for deploying other LiveCycle products, you do not need to perform the procedures in
this chapter again.
This chapter assumes that you have configured your database and created a database user account. If you
have not done this, see “Preparing Your Environment” on page 30.
Before configuring the WebSphere application server, you must complete the following tasks:
●
Install WebSphere. For information on the supported versions, see “Supported software” on page 16.
●
Create an endorsed directory and copy the LiveCycle JAR files to the WebSphere computer. (See
“Creating an endorsed directory” on page 37 and “Configuring the shared libraries” on page 37.)
●
Disable the CORBA time-out. (See “Disabling the CORBA time-out” on page 103.)
●
Configure the JVM arguments to enable UTF-8 encoding. (See “Configuring the JVM arguments” on
page 104.)
●
(LiveCycle Forms, LiveCycle PDF Generator, LiveCycle Assembler) Configure the server transaction
time-out. (See “Configuring the server transaction time out” on page 104.)
You configure the application server by completing the following tasks:
●
Configure various WebSphere and database settings. (See “Configuring the data source for WebSphere
6.0.2.9” on page 104.)
●
Configure JMS resources for WebSphere. (See “Configuring embedded messaging” on page 108.)
Disabling the CORBA time-out
You need to disable the CORBA time-out setting on WebSphere. This procedure does not apply if you are
only installing LiveCycle Workflow.
➤ To disable the CORBA time-out:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application servers, and
select the server instance you are configuring (for example, server1).
2. Under Container Settings, expand Container Services and click ORB Service.
3. Set Request timeout to 0 and click OK.
4. Save the master configuration by clicking Save, and then clicking Save again.
103
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring the JVM arguments
104
Configuring the JVM arguments
This section applies to LiveCycle Workflow and LiveCycle Form Manager only.
You must configure the JVM arguments on your application server.
➤ To configure the JVM arguments:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers >
[server name].
2. Under Server Infrastructure, select Java and Process Management > Process Definition.
3. Under Additional Properties, click Java Virtual Machine and, in the Generic JVM arguments box, type
the following code:
-Djava.awt.headless=true
(LiveCycle Workflow, LiveCycle Form Manager) Also add the following code:
-Dadobe.workflow.engine.publish-process-events=false
-Dadobe.workflow.scheduler.java.naming.provider.url=
iiop://<host name>:<bootstrap address port>
(LiveCycle Form Manager) Also add the following code:
-Dorg.apache.lucene.writeLockTimeout=10000
4. Click Apply, click OK, and then save the Master Configuration.
5. Restart WebSphere.
Configuring the server transaction time out
This section applies to LiveCycle Assembler and LiveCycle PDF Generator only.
You must configure the server transaction time-out setting on WebSphere.
Note: The default transaction time-out, which is 600 seconds, is set during the product configuration
using Configuration Manager. (See “Configuring LiveCycle Products for Deployment” on page 76.)
➤ To configure the server transaction time out:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Server >
[server name].
2. Click Container Settings, select Transaction Service and then click the Configuration tab.
3. Under General Properties, in the Total transaction lifetime timeout box, type 600.
4. Click OK.
Configuring the data source for WebSphere 6.0.2.9
You must configure your data source to connect WebSphere to your LiveCycle deployment:
●
“Configuring the Oracle data source” on page 105
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
●
“Configuring the DB2 data source” on page 106
●
“Configuring the SQL Server data source” on page 107
Configuring the Oracle data source
105
Configuring the Oracle data source
Before performing the following procedure, you must have already created an Oracle database and user
on the database. (See “Creating an Oracle database” on page 30).
➤ To create a data source on WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. For Scope, select Cell and click Apply.
3. Click New and select the following values:
●
Oracle in Step 1
●
Oracle JDBC Driver in Step 2
●
Connection pool data source in Step 3
4. Click Next and click Apply.
5. Under General Properties, in the Class path box, type
[appserver root]/db_driver/ojdbc14.jar
Note: For the Native library path property, leave the box blank.
6. Click Apply.
7. Under Additional Properties, select Data sources.
8. Click New and type a name for the data source (for example, LiveCycleDS).
9. In the JNDI Name box, type IDP_DS and then click Apply.
10. In the URL box, type jdbc:oracle:thin:@[server-name]:1521:[service-name] (where
[server-name] is your Oracle 9i or Oracle 10g server name and [service-name] is your database),
and then click Apply.
11. Under Related Items, select J2EE Connector Architecture (J2C) authentication data entries.
12. Click New and, in the Alias box, type a name (for example, MyAlias).
13. Type the user ID and password that correspond with the user you created on the database, click Apply,
and then click OK.
14. Save your changes to the Master Configuration.
15. Navigate back to JDBC Providers > Oracle JDBC Driver > Data Sources and select LiveCycleDS.
16. Under General Properties, set both Component-managed authentication alias and
Container-managed authentication to [computer_name]/MyAlias and click Apply.
17. From Mapping-configuration alias, select DefaultPrincipalMapping and click Apply.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring the DB2 data source
106
18. Save your changes to the Master Configuration.
19. Select Resources > JDBC Providers > Oracle JDBC Driver > Data Sources.
20. Select the IDP_DS datasource and click TestConnection.
Configuring the DB2 data source
Before performing the following procedure, you must have already created a DB2 database and user on
the database. (See “Creating a DB2 database” on page 31.)
➤ To create a data source on WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. For Scope, select Cell and click Apply.
3. Click New and select the following values:
●
DB2 in Step 1
●
DB2 Universal JDBC Driver Provider in Step 2
●
Connection pool data source in Step 3
4. Click Next and click Apply.
5. Under General properties, in the Class path box, type:
[appserver root]/db_driver/db2jcc_license_cu.jar
[appserver root]/db_driver/db2jcc.jar
Note: For the Native library path property, leave the box blank.
6. Under Additional Properties, select Data Sources.
7. Click New and type a name for the data source (for example, LiveCycleDS).
8. In the JNDI Name box, type IDP_DS.
9. Under Additional Properties, click DB2 Universal data source properties and set the following
properties:
●
Database name: The database name of the DB2 database in which the LiveCycle database resides.
●
Driver type: Set to 4.
●
Server name: The name of the DB2 server to which you are connecting.
●
Port number: The port number of the DB2 server to which you are connecting. The default is
50000.
10. Click Apply.
11. Under Related Items, select J2EE Connector Architecture (J2C) authentication data entries.
12. Click New and, in the Alias box, type a name (for example, MyAlias).
13. Type the user ID and password that correspond with the user you created on the database, and then
click Apply.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring the SQL Server data source
107
14. Save your changes to the Master Configuration.
15. Navigate back to JDBC Providers > DB2 Universal JDBC Driver Provider > Data Sources and select
the name for the data source (for example, LiveCycleDS).
16. Under General Properties, set both Component-managed authentication alias and
Container-managed authentication to [computer_name]/MyAlias.
17. From Mapping-configuration alias, select DefaultPrincipalMapping and click Apply.
18. (LiveCycle PDF Generator, LiveCycle Workflow, LiveCycle Form Manager) Perform the following steps:
●
Navigate back to JDBC Providers > DB2 Universal JDBC Driver Provider > Data Sources and
select the name for the data source (for example, LiveCycleDS).
●
Under Additional Properties, select Connection pool properties and, in the Maximum
connections box, type 30.
●
Click Apply.
19. Save your changes to the Master Configuration.
20. Test the data source connection by navigating to JDBC Providers > DB2 Universal JDBC Driver
Provider > Data Sources.
21. Select the check box next to the data source you created and click Test Connection. A message is
displayed describing the test results.
22. If you already had a data source configured and have created a new one, stop and restart the
application server.
Configuring the SQL Server data source
Before performing the following procedure, you must have already created a SQL Server database and
user on the database. (See “Creating a SQL Server database” on page 33.)
➤ To create a data source on WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Security > Global Security > JAAS
Configuration > J2C Authentication Data.
2. Click New and, in the Alias box, type a name for the alias (for example, SQLServer).
3. In the User ID box, type the user name of the user account you created on the database and, in the
Password box, type the corresponding password.
4. Click Apply, click OK, and then save to the Master Configuration.
5. In the navigation tree, select Resources > JDBC Providers.
6. Click Cell and click Apply.
7. Click New and select the following values:
●
SQL Server in Step 1
●
WebSphere embedded ConnectJDBC driver for MS SQL Server in Step 2
●
Connection pool data source in Step 3
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
108
8. Click Next and click Apply.
9. Under General properties, in the Class path box type:
[appserver root]/lib/util.jar
[appserver root]/lib/base.jar
[appserver root]/lib/sqlserver.jar
Note: For the Native library path property, leave the box blank.
10. In the Name box, type WebSphere embedded ConnectJDBC driver for MS SQL Server.
11. In the Description box, type WebSphere embedded ConnectJDBC driver for MS SQL
Server.
12. In the Implementation Classname box, type
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource and click OK.
13. Click SQL Server JDBC Provider and, under Additional Properties, select Data Sources.
14. Click New and, in the Name box, type a name for the data source (for example, LiveCycleDS).
15. In the JNDI Name box, type IDP_DS.
16. Under General Properties, set both Component-managed authentication alias and
Container-managed authentication to the alias you created in step 2 and click Apply.
17. In the Mapping-configuration alias menu, select DefaultPrincipalMapping and click Apply.
18. Under Connect JDBC data source properties, type the name of your database name, server name, and
port number.
19. Under Additional Properties, click Connection Pool, change the value of Maximum connections to
30, and then click OK.
20. Save your changes to the Master Configuration.
21. Test your connection by navigating to Resources > JDBC Providers > SQL Server JDBC Provider >
Data Sources and clicking Test Connection.
Configuring embedded messaging
You configure embedded messaging by configuring JMS resources for WebSphere:
●
Add and configure Buses and Bus Members.
●
Add required queues to the WebSphere embedded JMS server.
●
Set up WebSphere queue connection factories.
●
Set up WebSphere topic connection factories.
●
Set up WebSphere queue destinations.
●
Set up WebSphere topic destinations.
●
Set up WebSphere activation specifications.
●
Set up JVM Arguments.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
109
➤ To add and configure buses and bus members:
1. In the WebSphere Administrative Console navigation tree, select Service integration > Buses.
2. Click New and, in the New Buses window, under General Properties, type IDP_JMS_BUS and click OK.
3. Save your changes to the Master configuration.
4. Select the new bus by clicking IDP_JMS_BUS.
5. Click Bus members and click Add.
6. Select the server or cluster to be added. In a non-clustered server environment, you would typically
select the server name of this server.
7. Click Next, review the configuration, and then click Finish.
8. Save your changes to the Master Configuration.
9. Click the message engine created (for example, [computer name][node].[server name]-IDP_JMS_BUS)
and, under Additional Properties, click Data store.
10. In the Data souce JNDI Name box, type IDP_DS.
11. In the Schema name box, type the admin user name for the DB admin, which is being used on the J2EE
Connector Architecture (J2C) authentication data entries page, and then click OK.
Note: This step allows WebSphere to automatically create its own messaging tables in the database in
order to aid in the backup and recovery of the messaging service. For more information, see
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.
pmc.express.doc/ref/rjm0640_.html.
12. Save your changes to the Master Configuration.
➤ To add required queues to the WebSphere embedded JMS server:
1. In the WebSphere Administrative Console navigation tree, select Service Integration > Buses >
IDP_JMS_BUS > Destinations.
2. For each queue listed in the following table, perform steps 3 to 5.
Queue Name
Applicable LiveCycle product
ADOBE.WORKFLOW.OBJECT_DELETE.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
ADOBE.WORKFLOW.PE_COMMAND.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
ADOBE.WORKFLOW.PED_COMMAND.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
ADOBE.WORKFLOW.PED_LONGLIVED.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
ADOBE.WORKFLOW.PE_INTERACTION.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
ADOBE.WORKFLOW.PE_LONGLIVED.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
ADOBE.WORKFLOW.SCHEDULEDMSG.QUEUE
LiveCycle Form Manager or LiveCycle Workflow
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
Queue Name
Applicable LiveCycle product
ADOBE.PDFG.AESJOB.QUEUE
LiveCycle PDF Generator
ADOBE.PDFG.PDFGCOMPLETEDJOBS.QUEUE
LiveCycle PDF Generator
110
3. Click New, select Queue, and then click Next.
4. In the Identifier box, type the name of the appropriate queue and click Next.
5. Under Bus members, select [computer name][node].[server name]-IDP_JMS_BUS and click Next.
6. Click Finish.
7. Save your changes to the Master Configuration.
➤ To add required topics to the WebSphere embedded JMS server:
1. In the WebSphere Administrative Console navigation tree, select Service Integration > Buses >
IDP_JMS_BUS > Destinations.
2. For each topic listed in the following table, perform steps 3 to 5.
Topic Name
Applicable LiveCycle product
MQJMS/ADOBE/WORKFLOW/POF_OBJECT_TOPIC
LiveCycle Form Manager or LiveCycle Workflow
MQJMS/ADOBE/WORKFLOW/POF_SCHEMA_TOPIC
LiveCycle Form Manager or LiveCycle Workflow
MQJMS/ADOBE/WORKFLOW/
PROCESS_EVENT_TOPIC
LiveCycle Form Manager or LiveCycle Workflow
MQJMS/ADOBE/WORKFLOW/TASK_EVENT_TOPIC
LiveCycle Form Manager or LiveCycle Workflow
MQJMS/ADOBE/WORKFLOW/
TEMPLATE_EVENT_TOPIC
LiveCycle Form Manager or LiveCycle Workflow
MQJMS/ADOBE/EBXML/
REGISTRYCACHE_MONITOR_TOPIC
LiveCycle Form Manager or LiveCycle Workflow
MQJMS/ADOBE/PDFG/AESCONFIGUPDATES_TOPIC
LiveCycle PDF Generator
MQJMS/ADOBE/WATCHEDFOLDER/
CONFIG_MANAGER_TOPIC
Watched Folder
3. Click New, select Topic Space, and then click Next.
4. In the Identifier box, type the name of the appropriate topic and click Finish.
5. Save your changes to the Master Configuration.
➤ To set up WebSphere queue connection factories:
1. In the WebSphere Administrative Console navigation tree, select Resources > JMS Providers >
Default messaging.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
111
2. For Scope, select Cell and click Apply.
3. Under Connection Factories, click JMS Queue Connection Factory.
4. (LiveCycle Workflow, LiveCycle Form Manager) Click New, set the following properties, and then click
OK:
●
Name: QueueConnectionFactory
●
JNDI Name: QueueConnectionFactory
●
Category: LiveCycle
●
Bus Name: IDP_JMS_BUS
5. (LiveCycle PDF Generator) Click New, set the following properties, and then click OK:
●
Name: AESQueueConnectionFactory
●
JNDI Name: jms/QueueConnectionFactory,
●
Category: LiveCycle
●
Bus Name: IDP_JMS_BUS
6. (LiveCycle Workflow, LiveCycle Form Manager) Select the QueueConnectionFactory created in step 4
and, under Additional Properties, click Connection pool properties and, in the Maximum
connections box, type 30, and then click OK.
7. Save your changes to the Master Configuration.
➤ To set up WebSphere topic connection factories:
1. For each topic connection factory listed in the following tables, perform steps 2 to 7.
LiveCycle Form Manager or LiveCycle Workflow
Name
JNDI Name
Scope
TopicConnectionFactory
TopicConnectionFactory
Server
POFConnectionFactory
POFConnectionFactory
Server
RegistryTopicConnectionFactory RegistryTopicConnectionFactory Cell
LiveCycle PDF Generator
Name
JNDI Name
Scope
AESTopicConnectionFactory
jms/TopicConnectionFactory
Cell
2. In the WebSphere Administrative Console navigation tree, select Resources > JMS Providers >
Default messaging.
3. For Scope, select the scope as indicated in the table in step 1.
4. Under Connection Factories, select JMS Topic Connection Factory and click New.
5. In the Name box and JNDI name box, type the names as indicated in the table in step 1.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
112
6. In the Category box, type LiveCycle.
7. In the Bus box, type IDP_JMS_BUS and click OK.
8. Save your changes to the Master Configuration.
➤ To set up WebSphere queue destinations:
1. In the WebSphere Administrative Console navigation tree, select Resources > JMS Providers >
Default Messaging.
2. For Scope, select Cell and click Apply.
3. Under Destinations, click JMS queue and create the following queue destinations by completing steps
4 to 7 for each queue destination.
LiveCycle Form Manager or LiveCycle Workflow
Name
JNDI name
Queue name
adobe_ObjectDeleteQueue
queue/
adobe_ObjectDeleteQueue
ADOBE.WORKFLOW.
OBJECT_DELETE.QUEUE
adobe_PECommandQueue
queue/
adobe_PECommandQueue
ADOBE.WORKFLOW.
PE_COMMAND.QUEUE
adobe_PEDCommandQueue
queue/
adobe_PEDCommandQueue
ADOBE.WORKFLOW.
PED_COMMAND.QUEUE
adobe_PEDLongLivedQueue
queue/
adobe_PEDLongLivedQueue
ADOBE.WORKFLOW.
PED_LONGLIVED.QUEUE
adobe_PEInteractionQueue
queue/
adobe_PEInteractionQueue
ADOBE.WORKFLOW
PE_INTERACTION.QUEUE
adobe_PELongLivedQueue
queue/
adobe_PELongLivedQueue
ADOBE.WORKFLOW.
PE_LONGLIVED.QUEUE
adobe_PEScheduledMsgQueue queue/
adobe_PEScheduledMsgQueue
ADOBE.WORKFLOW.
PE_SCHEDULEDMSG.QUEUE
LiveCycle PDF Generator
Name
Queue name
JNDI name
AESJobQueue
ADOBE.PDFG.AESJOB.QUEUE
queue/AESJobQueue
PDFGCompletedJobsQueue
ADOBE.PDFG.
PDFGCOMPLETEDJOBS.QUEUE
queue/
PDFGCompletedJobsQueue
4. Click New, in the Name box, type the name as indicated in the table in step 3.
5. In the Bus name box, select IDP_JMS_BUS.
6. In the JNDI name box, type the name as indicated in the table in step 3.
7. In Queue name box, select the name as indicated in the table in step 3.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
113
8. Save your changes to the Master Configuration.
➤ To set up WebSphere topic destinations:
1. For each topic destination listed in the following tables, perform steps 2 to 6.
LiveCycle Form Manager or LiveCycle Workflow
Name
JNDI Name
Topic Name / Topic Space
Scope
adobe_POFObject
Topic
topic/
adobe_POFObjectTopic
MQJMS/ADOBE/WORKFLOW/
POF_OBJECT_TOPIC
Server
adobe_POFSchema
Topic
topic/
adobe_POFSchemaTopic
MQJMS/ADOBE/WORKFLOW/
POF_SCHEMA_TOPIC
Server
adobe_ProcessEvent
Topic
topic/
adobe_ProcessEventTopic
MQJMS/ADOBE/WORKFLOW/
PROCESS_EVENT_TOPIC
Server
adobe_TaskEvent
Topic
topic/
adobe_TaskEventTopic
MQJMS/ADOBE/WORKFLOW/
TASK_EVENT_TOPIC
Server
MQJMS/ADOBE/WORKFLOW/
TEMPLATE_EVENT_TOPIC
Server
adobe_TemplateEvent topic/
Topic
adobe_TemplateEventTopic
adobe_RegistryCache topic/
MQJMS/ADOBE/EBXML/
MonitorTopic
adobe_RegistryCacheMonitorTopic REGISTRYCACHE_MONITOR_
TOPIC
Cell
LiveCycle PDF Generator
Name
JNDI Name
Topic Name / Topic Space
Scope
AesConfigUpdates
Topic
topic/AesConfigUpdatesTopic
MQJMS/ADOBE/PDFG/
AESCONFIGUPDATES_TOPIC
Cell
JNDI Name
Topic Name / Topic Space
Scope
MQJMS/ADOBE/WATCHED
FOLDER/CONFIG_MANAGER
_TOPIC
Server
Watched Folder
Name
WatchedFolderConfig topic/WatchedFolderConfig
ManagerTopic
ManagerTopic
2. Select Resources > JMS Providers > Default messaging.
3. Set the Scope as indicated in the table in step 1 and click Apply.
4. Under Destinations, click JMS Topic and click New.
5. In the Name, JNDI Name, Topic Name, and Topic Space boxes, type the information as indicated in
the table in step 1.
6. In the Bus name list, select IDP_JMS_BUS.
7. Save your changes to the Master Configuration.
Adobe LiveCycle
Manually Configuring WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Configuring embedded messaging
114
➤ To set up WebSphere activation specifications:
1. For each activation specification listed in the following tables, perform steps 2 to 9.
All LiveCycle products
Name / JNDI Name
Type
Destination JNDI name
Scope
PECommand_AS
Queue
queue/adobe_PECommandQueue
Cell
Task_Event_AS
Topic
topic/adobe_TaskEventTopic
Server
RegistryCache_AS
Topic
topic/adobe_RegistryCacheMonitorTopic
Cell
Name / JNDI Name
Type
Destination JNDI name
Scope
WatchedFolderConfig
Manager_AS
Topic
topic/WatchedFolderConfigManagerTopic
Server
Name / JNDI Name
Type
Destination JNDI name
Scope
Dequeue_AS
Queue
queue/AESJobQueue
Cell
ConfigUpdates_AS
Topic
topic/AesConfigUpdatesTopic
Server
PDFGCompletedJobs_AS
Queue
queue/PDFGCompletedJobsQueue
Cell
PsDequeue_AS
Queue
queue/AESJobQueue
Cell
Watched Folder
LiveCycle PDFG
2. Navigate to Resources > JMS Providers > Default messaging.
3. Set scope as indicated in the table in step 1 and click Apply.
4. Under Activation Specifications, click JMS activation specifications and click New.
5. Navigate to General Properties > Administration.
6. In the Name and JNDI name boxes, type the information as indicated in the table in step 1.
7. Navigate to General Properties > Destination.
8. In the Destination Type and Destination JNDI name boxes, type the information as indicated in the
table in step 1.
9. In the Bus name box, type IDP_JMS_BUS.
10. Save your changes to the Master Configuration.
➤ To set up JVM arguments:
1. Navigate to Servers > Application servers > [server] and select the Configuration tab.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Manually Configuring WebSphere 6.0.2.9
Next step
115
2. Select Server Infrastructure > Java and Process Management > Process Definition > Java Virtual
Machine.
3. In the Initial Heap Size box, type 512.
4. In the Maximum Heap Size box, type 1024.
5. Save your changes to the Master Configuration.
6. Restart WebSphere.
Next step
If you are installing and configuring LiveCycle Workflow and you plan to install and configure BAM Server
as well, you must now configure WebSphere 6.0.2.9 for use with BAM Server. (See “Configuring WebSphere
6.0.2.9 for BAM Server” on page 151.)
Otherwise, you must now deploy the products to the application server database. (See “Manually
Deploying to WebSphere 6.0.2.9” on page 121.)
9
Manually Deploying to WebSphere 5.1.1.5
This chapter describes how to configure the WebSphere Application Server for LiveCycle products and
deploy the applications.
●
“About deploying LiveCycle products” on page 116
●
“Deploying to WebSphere” on page 117
●
“Starting the application” on page 119
●
“Viewing log files” on page 120
About deploying LiveCycle products
Before you deploy LiveCycle products, ensure that you have met the following requirements:
●
You have installed the required software and files and know the location of the directories you will be
working with. (See “System requirements” on page 16.)
●
You have run Configuration Manager to configure and assemble the products according to your system
and application server requirements. If you need to make any further changes to the properties after
deployment, you can run Configuration Manager to make the changes, and then redeploy the updated
EAR file. (See “Configuring LiveCycle Products for Deployment” on page 76.)
If you are using an external web server, see your web server documentation for information on the
configuration required to allow access to the application server.
WebSphere directory name
This chapter refers to the WebSphere home directory as [appserver root]. The home directory is the same as
the one specified for the WAS_INSTALL_ROOT environment variable. Similarly, [LiveCycle root] refers to
the location where LiveCycle products and components are installed.
Summary of deployable components
This table lists the deployable components for LiveCycle products.
Component
LiveCycle product
adobe-FontManager.ear
All
LCM.ear
All
LiveCycle.ear
All
adobe-Assembler7.ear
LiveCycle Assembler
FormsIVS.ear
LiveCycle Forms
pdfg-all.ear
LiveCycle PDF Generator Professional and
LiveCycle PDF Generator Elements
116
Adobe LiveCycle
Manually Deploying to WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Deploying to WebSphere
Component
LiveCycle product
pdfg-ps-all.ear
LiveCycle PDF Generator for PostScript
adobe-printSubmitter.ear
LiveCycle Print
117
Deploying to WebSphere
You deploy LiveCycle products to WebSphere by placing the library file in the WebSphere directory,
configuring a shared library, and then deploying the EAR file to the application server using WebSphere
Administrative Console.
Before deploying to WebSphere, you must start the application server on your computer. After deploying
the required components, you must stop and restart the application server before starting any services.
➤ To deploy the EAR files:
1. Copy the following files from the [LiveCycle root]/configurationManager/export directory to the
[appserver root]/installableApps directory:
●
LiveCycle.ear
●
adobe-FontManager.ear
●
(LiveCycle Assembler) adobe-Assembler7.ear
●
(LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements)pdfg-all.ear
●
(LiveCycle PDF Generator for PostScript) pdfg-ps-all.ear
2. Copy the LCM.ear file from the [LiveCycle root]/configurationManager/deploy/websphere directory to
the [appserver root]/installableApps directory.
➤ To deploy the adobe-FontManager.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select
adobe-FontManager.ear, and then click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
4. Click Save to Master Configuration, and then click Save.
➤ To deploy the LiveCycle.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select LiveCycle.ear, and
then click Open.
3. Click Next and accept the default values that are displayed on the first two screens.
4. (LiveCycle Assembler) On the Provide JNDI Names for Bean screen, for the
AdobeIDP2UI_MonitorComponent EJB, type the JNDI Name,
ejb/AdobeIDP2UI_MonitorComponent, and then click Next.
Adobe LiveCycle
Manually Deploying to WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Deploying to WebSphere
118
5. Accept the default values that are displayed on each screen, and then click Finish.
6. Click Save to Master Configuration, and then click Save.
➤ To deploy the LCM.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select LCM.ear, and then
click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
4. Click Save to Master Configuration, and then click Save.
➤ (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) To deploy the
pdfg-all.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select pdfg-all.ear, and then
click Open.
3. Click Next, accept the default values that are displayed on the first two screens and, on the third screen,
select Deploy EJBs, and then click Finish.
4. Click Save to Master Configuration, and then click Save.
➤ (LiveCycle PDF Generator for PostScript) To deploy the pdfg-ps-all.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select pdfg-ps-all.ear, and
then click Open.
3. Click Next, accept the default values that are displayed on the first two screens and, on the third screen,
select Deploy EJBs, and then click Finish.
4. Click Save to Master Configuration, and then click Save.
➤ (LiveCycle Assembler) To deploy the adobe-Assembler7.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select
adobe-Assembler7.ear, and then click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
4. Click Save to Master Configuration, and then click Save.
Adobe LiveCycle
Manually Deploying to WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Starting the application
119
Starting the application
After deploying the products, you need to start the applications. When the red “X” beside the name of the
application changes to a green arrow, the application has been deployed and started successfully.
WebSphere displays an error message if it cannot start the application.
For information about WebSphere error messages, refer to your WebSphere Application Server
documentation.
➤ To start an application in WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Applications > Enterprise
Applications.
2. Select any or all of the LiveCycle applications that you want to start.
3. Click Start. The red “X” beside the status of each application changes to a green arrow, indicating that
the application is running.
Verifying the LiveCycle Forms deployment
You can verify that LiveCycle Forms has been deployed properly and is running by deploying the
Installation Verification sample application that is installed with the product.
The sample application file (FormsIVS.ear) is located in the
[LiveCycle root]/components/forms/samples/common directory.
Note: For information about using the sample application, click the Help link in the Samples page in the
web browser.
➤ To deploy the LiveCycle Forms Installation and Verification sample application:
1. In the WebSphere Administrative Console navigation tree, select Applications > Install New
Application.
2. Click Browse to navigate to the [LiveCycle root]/components/forms/samples/common directory, select
FormsIVS.ear, and then click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
4. Click Save to Master Configuration, and then click Save.
5. In the navigation tree, select Applications > Enterprise Applications, and then select FormsIVS.
6. Click Start. The red “X” beside the name of each application changes to a green arrow, indicating that
the application is running.
7. Start the application by typing http://hostname:portnumber/FormsIVS in the URL line of a
web browser.
Adobe LiveCycle
Manually Deploying to WebSphere 5.1.1.5
Installing and Configuring LiveCycle for WebSphere
Viewing log files
120
Viewing log files
Events, such as run-time or startup errors, are recorded to the application server log files. If you have
problems deploying to the application server, you can use the log files to help you find the problem. You
can open the log files using any text editor.
The following log files are located in the [appserver root]/logs/servername directory:
●
SystemErr.log
●
SystemOut.log
●
StartServer.log
Next step
You must now initialize the database using Configuration Manager. (See “Initializing the Database” on
page 126.)
10
Manually Deploying to WebSphere 6.0.2.9
This chapter describes how to deploy your LiveCycle products to WebSphere 6.0.2.9:
●
“About deploying LiveCycle products” on page 121
●
“Deploying to WebSphere” on page 122
●
“Starting the application” on page 124
●
“Viewing log files” on page 125
About deploying LiveCycle products
Before you deploy LiveCycle products, ensure that you have met the following requirements:
●
You have installed the required software and files and know the location of the directories you will be
working with. (See “System requirements” on page 16.)
●
You must run Configuration Manager to configure and assemble the products according to your
system and application server requirements. If you need to make any further changes to the properties
after deployment, you can run Configuration Manager to make the changes, and then redeploy the
updated EAR file. (See “Configuring LiveCycle Products for Deployment” on page 76.)
If you are deploying a product for the first time, you must initialize the database after you deploy the
product.
If you are using an external web server, see your web server documentation for information regarding the
configuration required to allow access to the application server.
WebSphere directory name
This chapter refers to the WebSphere Application Server home directory as [appserver root]. The home
directory is the same as the one specified for the WAS_INSTALL_ROOT environment variable. Similarly,
[LiveCycle root] refers to the location where LiveCycle products and components are installed. (See
“Conventions used in this guide” on page 10.)
121
Adobe LiveCycle
Manually Deploying to WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Summary of deployable components
122
Summary of deployable components
During the deployment process, you need to deploy the following components for LiveCycle products.
Component
LiveCycle product
adobe-FontManager.ear
All
LCM.ear
All
LiveCycle.ear
All
adobe-Assembler7.ear
LiveCycle Assembler
FormsIVS.ear
LiveCycle Forms
pdfg-all.ear
LiveCycle PDF Generator Professional and
LiveCycle PDF Generator Elements
pdfg-ps-all.ear
LiveCycle PDF Generator for PostScript
adobe-printSubmitter.ear
LiveCycle Print
Deploying to WebSphere
You deploy LiveCycle products to WebSphere by deploying the component EAR files to the application
server using WebSphere Administrative Console.
Before deploying to WebSphere, you must start the application server on your computer. After deploying
the required components, you must stop and restart the application server before starting any services.
➤ To deploy the EAR files:
1. Copy the following files from the [LiveCycle root]/configurationManager/export directory to the
[appserver root]/installableApps directory:
●
LiveCycle.ear
●
adobe-FontManager.ear
●
(LiveCycle Assembler) adobe-Assembler7.ear
●
(LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements)pdfg-all.ear
●
(LiveCycle PDF Generator for PostScript) pdfg-ps-all.ear
2. Copy the LCM.ear file from the [LiveCycle root]/configurationManager/deploy/websphere directory to
the [appserver root]/installableApps directory.
➤ To deploy the adobe-FontManager.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select
adobe-FontManager.ear, and then click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
Adobe LiveCycle
Manually Deploying to WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Deploying to WebSphere
123
4. Save the master configuration by clicking Save, and then clicking Save again.
➤ To deploy the LiveCycle.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select LiveCycle.ear, click
Open, and then click Next.
3. On the Preparing for the application installation screen, select Generate Default Bindings.
4. Click Next and accept the default values that are displayed on each screen, and then click Finish.
5. Save the Master Configuration by clicking Save, and then clicking Save again.
➤ To deploy the LCM.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select LCM.ear, and then
click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
4. Save the master configuration by clicking Save, and then clicking Save again.
➤ (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) To deploy the
pdfg-all.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select pdfg-all.ear, and then
click Open.
3. Click Next, accept the default values that are displayed, and then click Finish.
4. Save the master configuration by clicking Save, and then clicking Save again.
➤ (LiveCycle PDF Generator for PostScript) To deploy the pdfg-ps-all.ear file:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select pdfg-ps-all.ear, and
then click Open.
3. Click Next, accept the default values that are displayed, and then click Finish.
4. Save the master configuration by clicking Save, and then clicking Save again.
➤ (LiveCycle Assembler) To deploy the adobe-Assembler7.ear:
1. In the navigation tree, select Applications > Install New Application.
2. Click Browse to navigate to the [appserver root]/InstallableApps directory, select
adobe-Assembler7.ear, and then click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
Adobe LiveCycle
Manually Deploying to WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Starting the application
124
4. Save the master configuration by clicking Save, and then clicking Save again.
Starting the application
After deploying the product, you need to start the applications. When the red “X” beside the name of the
application changes to a green arrow, the application has been deployed and started successfully.
WebSphere displays an error message if it cannot start the application.
For information about WebSphere error messages, refer to your WebSphere Application Server
documentation.
➤ To start an application in WebSphere:
1. In the WebSphere Administrative Console navigation tree, select Applications > Enterprise
Applications.
2. Select any or all of the LiveCycle applications that you want to start.
3. Click Start. The red “X” beside the status of each application changes to a green arrow, indicating that
the application is running.
Verifying the LiveCycle Forms deployment
You can verify that LiveCycle Forms has been deployed properly and is running by deploying the
Installation Verification sample application that is installed with the product.
The sample application (FormsIVS.ear) is in the [LiveCycle root]/components/forms/samples/common
directory.
Note: For information about using the sample application, click the Help link in the Samples page in the
web browser.
➤ To deploy the LiveCycle Forms Installation and Verification sample application:
1. In the WebSphere Administrative Console navigation tree, select Applications > Install New
Application.
2. Click Browse to navigate to the [LiveCycle root]/components/forms/samples/common directory, select
FormsIVS.ear, and then click Open.
3. Click Next, accept the default values that are displayed on each screen, and then click Finish.
4. Save the master configuration by clicking Save, and then clicking Save again.
5. In the navigation tree, select Applications > Enterprise Applications, and then select FormsIVS.
6. Click Start. The red “X” beside the name of each application changes to a green arrow, indicating that
the application is running.
7. Start the application by typing http://hostname:portnumber/FormsIVS in the URL line of a
web browser.
Adobe LiveCycle
Manually Deploying to WebSphere 6.0.2.9
Installing and Configuring LiveCycle for WebSphere
Viewing log files
125
Viewing log files
Events, such as run-time or startup errors, are recorded to the application server log files. If you have
problems deploying to the application server, you can use the log files to help you find the problem. You
can open the log files using any text editor.
The following log files are located in the [appserver root]/profiles/default/logs/servername directory:
●
SystemErr.log
●
SystemOut.log
●
StartServer.log
Next step
You must now initialize the database using Configuration Manager. (See “Initializing the Database” on
page 126.)
11
Initializing the Database
This chapter describes how to manually initialize the LiveCycle database.
If you are using User Management with LiveCycle products, you must run Configuration Manager to
initialize the database for integration with User Management. When you run Configuration Manager, the
application server must be running. Initializing the database is a process that prepares a database for use
with LiveCycle products by creating tables and optionally adding data to them. You only need to initialize
the database the first time you deploy the product.
During database initialization, provide an SSL-enabled port only if the application server has trusted SSL
certificates. If the application server does not have trusted SSL certificates, a non-SSL enabled port must be
provided to complete database initialization. (See “Configuring SSL on WebSphere” on page 131.)
This chapter assumes that you have configured the Livecycle database for integration with the product
and have deployed the product to the application server. If you have not done this, see “Preparing Your
Environment” on page 30 and “Manually Deploying to WebSphere 5.1.1.5” on page 116 or “Manually
Deploying to WebSphere 6.0.2.9” on page 121.
➤ To initialize the database:
1. Start the application server.
2. Start Configuration Manager by navigating to the [LiveCycle root]/configurationManager directory and
entering the following command:
●
(Windows) ConfigurationManager.exe
●
(Linux, UNIX) ConfigurationManager.bin
3. On the Welcome screen, click Next.
4. On the Configuration Mode screen, select Custom Configuration Wizard and click Next.
5. If prompted, on the Configuration Preferences screen, select either Use Previously Entered Values or
Revert to Default Values, and then click Next.
6. On the Product Selection screen, select Foundation, select the products that you want to configure
and deploy, and then click Next.
7. Select the version of WebSphere that you are using to run LiveCycle products and click Next.
8. On the Task Selection screen, select Bootstrap database and click Next.
Note: You must only select the Bootstrap database; no other options are required.
9. On the Application Server Configuration Details screen, specify values for the following properties, and
then click Next:
●
Deploy Type: Specifies whether you are deploying to a standalone computer or to a cluster. Select
Standalone.
●
Remote Server: (WebSphere 6.0.2.9) Select this option only if the application server is running on a
different computer than the computer that is running Configuration Manager.
126
Adobe LiveCycle
Initializing the Database
Installing and Configuring LiveCycle for WebSphere
Next step
127
●
Hostname: The fully qualified name or IP address of the computer that hosts the application server.
●
SOAP Port: The port used to provide access to the SOAP service on the application server. The
default port is 8880. (See “Determining the application server SOAP port” on page 49).
●
Server Instance Name: The name of the application server that you want to configure. The name of
the default server instance that is created upon installing the application server is server1.
●
Username and Password: (Optional) If the application server requires user credentials to perform
administration tasks, the user name and password of an application server administration account.
●
Local Application Server Root Directory: The root directory of the application server installation
on the computer that is running Configuration Manager. For example, for WebSphere 5.1.1.5 under
Windows the directory is C:\Program Files\WebSphere\AppServer.
Caution: The Remote Server property cannot be used to configure LiveCycle PDF Generator Professional
or LiveCycle PDF Generator Elements because Acrobat cannot be installed remotely. However,
the property can be used to configure LiveCycle PDF Generator for PostScript.
10. On the Application Server URL screen, type the URL that Configuration Manager can use to connect to
the application server in the Application Server Base URL box, and then click Next. The URL must be
in the following format:
http://[host name]:[port]
where [host name] is the fully qualified domain name or IP address of the computer that hosts the
application server, and [port] is the HTTP service port that the application server uses. (for example,
http://locahost:9080).
11. On the Prepare database for LiveCycle screen, click Next.
12. On the Deploy LCM.ear screen, click Next.
13. On the Database Initialization screen, click Initialize Database Now and, when the task is complete,
click Next.
14. On the Tasks Completed screen, click Finish.
Next step
You can now access User Management and Administrator. (See “Post-deployment” on page 66.)
You can also configure LiveCycle products to access LDAP. (See “Configuring LiveCycle Products to Access
LDAP” on page 129.)
If you are using LiveCycle Workflow, you can now install LiveCycle Workflow Designer. (See “Installing
LiveCycle Workflow Designer” on page 172.)
Part III: Post-Deployment Configuration
This section of the guide describes the additional configuration tasks that you need to perform after
LiveCycle products are deployed to the application server and the LiveCycle database is initialized.
128
12
Configuring LiveCycle Products to Access LDAP
This chapter describes how to configure LiveCycle products with LDAP or LDAP over SSL (LDAPS).
●
“Configuring LiveCycle products with LDAP” on page 129
●
“Configuring LiveCycle products with LDAPS” on page 130
Caution: If you are installing and deploying more than one LiveCycle product, you must consult the
appropriate Installing and Configuring guide to obtain specific SSL and security settings for each
of the LiveCycle products you have installed.
Configuring LiveCycle products with LDAP
Use the following procedure as a guideline when configuring User Management to support
authentication using LDAP.
➤ To configure User Management with LDAP:
1. Open a web browser, navigate to http://[host name]:[port]/adminui, and log in. (See
“Accessing Administrator” on page 66.)
2. Select Settings > User Management > Domain Management and click New Domain.
3. In the ID box, type a unique identifier for the domain.
4. In the Name box, type a descriptive name for the domain.
5. Click Add Authentication and, in the Authentication Provider list, select LDAP.
Note: JAAS has been deprecated for User Management in LiveCycle 7.2.
6. Click OK.
7. Click Add Directory.
8. Under Populate Page With, select a directory settings option such as Default Sun ONE values.
9. Specify values in the Server, Port, SSL and Binding boxes as required. For details on the settings, see
Directory settings in the online help.
10. Configure the User Settings and Group Settings as required. For details on the settings, see Directory
settings in the online help.
11. (Optional) Test your configuration:
●
Click Test.
●
On the Test Directory pane, in the Find box, enter an object name and, in the using box, select the
object’s type, such as Login ID.
●
Click Test. If successful, your object’s details will be displayed, then click Back.
12. Click OK to exit the Add Directory page, and click OK again to exit.
129
Adobe LiveCycle
Configuring LiveCycle Products to Access LDAP
Installing and Configuring LiveCycle for WebSphere
Configuring LiveCycle products with LDAPS
130
Configuring LiveCycle products with LDAPS
Use the following procedure as a guideline when configuring User Management to support
authentication using LDAPS.
➤ To configure User Management with LDAPS:
1. Enable SSL on the directory server. For details, see the documentation provided by your directory
vendor.
2. Export a client certificate from the directory server.
3. Use the keytool program to import the client certificate file into the default JVM certificate store. The
procedure for this varies depending on your JVM and client install paths. For example, if you are using
JDK 1.4.2, from a command prompt, type the following code:
keytool -import -file client_certificate -alias myalias -keystore
[appserver root]/jdk142_08/jre/lib/security/cacerts
When prompted, enter the password (for Java, the default password is changeit). You will receive a
message stating that the certificate was imported successfully.
4. Enable SSL in User Management. To access the User Management settings, select Settings > User
Management in the Administrator pages. When configuring the directory settings, select Yes for the
SSL property, and change the Port property accordingly. The default port number is 636.
Troubleshooting
If you experience problems when using SSL, use an LDAP browser to check whether it can access the LDAP
system when using SSL. If the LDAP browser cannot access the LDAP system, the issue is related to the
configuration of your certificate and application server. If the LDAP browser can access the LDAP system,
User Management is not configured properly.
13
Configuring SSL on WebSphere
This chapter describes how to create SSL credentials and configure SSL on the application server to
enhance the security of communication with your application server.
The information in this chapter applies to WebSphere version 5.1.1.5 and version 6.0.2.9.
Note: It is recommended that you complete the installation, configuration and deployment of your
LiveCycle products and ensure that the products are running correctly before configuring SSL on
the application server.
It is important to ensure that the security settings configured on the application server and in the
LiveCycle.ear file are consistent.
Caution: If you are installing and deploying more than one LiveCycle product, you must consult the
appropriate Installing and Configuring guide to obtain specific SSL and security settings for each
of the LiveCycle products you have installed.
If you have not already enabled SSL in the Data Manager Module (assembled as part of the LiveCycle.ear
file), run Configuration Manager to reconfigure and reassemble the products with SSL enabled, and then
redeploy the LiveCycle.ear file. The SSL password that you specify in Configuration Manager must match
the password that you provide when configuring SSL on the application server. (See “Configuring
LiveCycle Products for Deployment” on page 76.)
To configure SSL on the application server, you must perform the following tasks:
●
“Creating an SSL Credential” on page 132
●
“Creating a local user account” on page 131
●
“Configuring the WebSphere connection time-out” on page 134
Creating a local user account
For enabling SSL, WebSphere needs access to a user account in the local OS user registry that has
permission to administer the system:
●
(Windows) You must create a new Windows user that is part of the Administrators group and has the
privilege to act as part of the operating system. (See “To create a Windows user for WebSphere:” on
page 132.
●
(Linux, UNIX) The user can be a root user or another user with root privileges. When you enable SSL on
WebSphere, you use the server identification and password of this user.
➤ To create a Linux or UNIX user for WebSphere:
1. Log in as the root user.
2. Create a new user by entering the following command in a command prompt:
●
(Linux, and Solaris on WebSphere 5.x) useradd
●
(AIX) mkuser
131
Adobe LiveCycle
Configuring SSL on WebSphere
Installing and Configuring LiveCycle for WebSphere
Creating an SSL Credential
132
3. Set the password of the new user by entering passwd in the command prompt.
4. (Linux, and Solaris on WebSphere 5.x) For WebSphere Application Server Local OS security registry to
work a shadow password file must exist. The shadow password file is usually named /etc/shadow and is
based on the /etc/passwd file. If the shadow password file does not exist, an error occurs after enabling
global security and configuring the user registry as Local OS. Create a shadow password file by entering
pwconv (with no parameters) in the command prompt.
5. Open the group file from the /etc directory in a text editor.
6. Add the user that you created in step 2, to the root group.
7. Save and close the file.
8. (UNIX with SSL enabled) Start and stop WebSphere as the root user.
➤ To create a Windows user for WebSphere:
1. Log into Windows using an administrator user account.
2. Select Start > Control Panel > Administrative Tools > Computer Management.
3. Expand Local Users and Groups, right-click Users, and then select New User.
4. Type a user name and password in the appropriate boxes, and type any other information you require
in the remaining boxes.
5. Deselect User must change password at next login, click Create, and then click Close.
6. Click Users, right-click the user that you just created, and then select Properties.
7. Click the Member Of tab, and then click Add.
8. In the Enter the object names to select box, type Administrators, click Check Names to ensure
that the group name is correct, and then click OK.
9. Click OK.
10. Select Start > Control Panel > Administrative Tools > Local Security Policy >
11. Expand Local Policies and click User Rights Assignment.
12. Right-click Act as Part of the Operating System and select Properties.
13. Click Add User or Group.
14. In the Enter the object names to select box, type the name of the user that you created in step 4, click
Check Names to ensure that the name is correct, and then click OK.
15. Click OK to close the Act as part of the operating system Properties dialog box.
Creating an SSL Credential
To configure SSL on WebSphere, you need an SSL credential for authentication. You can use the IBM Key
Management tool that is installed with WebSphere to perform the following tasks to create a credential:
Adobe LiveCycle
Configuring SSL on WebSphere
Installing and Configuring LiveCycle for WebSphere
Creating an SSL Credential
133
●
Create a keystore file and use it to store a new self-signed certificate and associated private key.
●
Export the certificate, and then add it to the same keystore as a signer certificate. The same keystore is
used as the key file and the trust file in the WebSphere SSL configuration.
➤ To create an SSL credential:
1. Open a command prompt and navigate to [appserver root]/etc.
2. Run the IBM Key Management tool by entering the following command:
●
(Windows) [appserver root]\bin\ikeyman.bat
●
(Linux, UNIX) [appserver root]/bin/ikeyman.sh
3. Select Key Database File > New.
4. From Key database type, select JKS.
5. Click Browse and navigate to the [appserver root]/etc directory.
6. In the File Name box, type ads-credentials.jks, click Save, and then click OK.
7. In the Password Prompt window, type a password, and then retype the same password in the
Confirm Password box. This password must match the SSL credential password for the SSL property
that is set for the Data Manager Module that is set using Configuration Manager. (See “Configuring
LiveCycle Products for Deployment” on page 76.)
8. Click OK.
9. From the menu in the Key database content area, select Personal Certificates.
10. Open the Create New Self-Signed Certificate window by clicking New Self-Signed.
11. In the Key Label box, type ads-credentials
12. Specify values for Organization, Organization Unit, Country or region, and Validity Period.
13. Edit the Common Name value to be the name of the local user account that you created. (See
“Creating a local user account” on page 131.)
14. Click OK.
15. In the list, select the ads-credentials certificate, click Extract Certificate.
16. Under Data type, select Base64-encoded ASCII data.
17. Under Certificate file name, type ads-cert.arm
18. Under Location, type [appserver root]/etc and click OK.
19. From the menu in the Key database content area, select Signer Certificates, and then click Add.
20. In the Certificate file name box, click Browse, select the ads-cert.arm created in step 17, and then
click Open.
21. Click OK.
22. In the Enter a Label dialog box, type ads-credentials-cert
Adobe LiveCycle
Configuring SSL on WebSphere
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere to use local OS registry instead of LDAP
134
23. Click OK.
24. Select Key Database File > Exit.
Configuring WebSphere to use local OS registry instead of LDAP
If you are not using LDAP, you must configure WebSphere to use the local OS registry.
➤ To configure custom properties:
1. Ensure that WebSphere is running.
2. In WebSphere Administrative Console, navigate to Local OS. For WebSphere 5.1.1.5 select Security >
User Registries > Local OS. For WebSphere 6.0.2.9, select Security > Global Security, and under User
Registries, select Local OS.
3. Perform the following steps:
●
In the Server User ID box, type the name of the user account that you created using the
instructions in “Creating a local user account” on page 131.
●
In the Server User Password box, type the user password for the user entered for Server User ID.
4. Click OK and then save your changes.
Configuring the WebSphere connection time-out
This section applies to LiveCycle Assembler and LiveCycle PDF Generator under WebSphere 5.1.1.5
only.
You must configure a connection time out value for the application server.
➤ (LiveCycle Assembler, LiveCycle PDF Generator) To configure custom properties:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers and
click the [server name].
2. Under Additional Properties, select Web Container and select HTTP transports.
3. Select 9443 and, under Additional Properties, select Custom Properties, and then click New.
4. In the Name box, type ConnectionIOTimeout and, in the Value box, type 120.
5. Click OK, and then click New.
6. In the Name box, type ConnectionKeepAliveTimeout and, in the Value box, type 120.
7. Click OK and save your changes to the Master Configuration.
8. Restart the server.
Configuring SSL on WebSphere
You must enable SSL for the application server.
Adobe LiveCycle
Configuring SSL on WebSphere
Installing and Configuring LiveCycle for WebSphere
Configuring SSL on WebSphere
135
➤ To enable SSL on WebSphere:
1. Navigate to LTPA by selecting Security > Authentication Mechanisms > LTPA. In WebSphere 6.0.2.9,
select Security > Global Security, and under Authentication, expand Authentication Mechanisms
and select LTPA.
2. Perform the following steps:
●
In the Password box, type the password that you specified when you created the ads-credential.jks
file, as described in “Creating an SSL Credential” on page 132.
●
In the Confirm Password box, type the password again.
●
In the Timeout box, type 10. This is the time (in minutes) after which the LTPA token will expire. This
time must be greater than the Cache Timeout property of WebSphere Global Security. You set the
Cache Timeout property in step 5.
3. Click OK.
4. In the navigation tree, select Security > Global Security.
5. Perform the following steps:
●
Select Enabled (or Enable global security) and Issue Permission Warning.
●
Deselect Enforce Java 2 Security, User Domain Qualified IDs (or Use domain-qualified IDs).
●
Deselect Enforce fine-grained JCA Security (if available).
●
Deselect Use FIPS (or Use the Federal Information Processing Standard (FIPS)).
●
Set Cache Timeout to 600.
●
In the Active Protocol list, select CSI and SAS.
●
In the Active Authentication Mechanisms list, select LTPA (Light weight Third Party
Authentication).
●
In the Active User Registries list, select the user registry you are using.
6. Click OK. If you are prompted to enter Local OS login information, type the information required as you
did in step 2.
7. In the navigation tree, select Security > SSL.
8. Under SSL Configuration Repertoires, click New (or New JSSE repertoire) and perform the following
steps:
●
In the Alias box, type AdsSSL
●
In the Key File Name box, type [appserver root]/etc/ads-credentials.jks
●
In the Key File Password box, type the password you used when you created the
ads-credentials.jks file (step 7. on page 133).
●
From Key File Format, select JKS.
●
In the Trust File Name box, type [appserver root]/etc/ads-credentials.jks
●
In the Trust File Password box, type the password you used when you created the
ads-credentials.jks file (step 7. on page 133).
●
From Trust File Format, select JKS.
●
If you are configuring the server for LiveCycle PDF Generator, select Client Authentication,
otherwise ensure Client Authentication is not selected.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Configuring SSL on WebSphere
Configuring SSL on WebSphere
136
9. Click OK, and save the configuration.
10. Navigate to CSIv2 inbound authentication. In WebSphere 5.1.1.5, select Security > Authentication
Protocol > CSIv2 Inbound Authentication. In WebSphere 6.0.2.9, select Security > Global Security,
and under Authentication, expand Authentication Protocol and select CSIv2 inbound
authentication.
11. Set Basic Authentication to Supported and Client Certificate Authentication to Required, and
then click OK.
12. Navigate to CSIv2 outbound authentication. In WebSphere 5.1.1.5, select Security > Authentication
Protocol > CSIv2 Outbound Authentication. In WebSphere 6.0.2.9, select Security > Global
Security, and under Authentication, expand Authentication Protocol and select CSIv2 outbound
authentication.
13. Set Basic Authentication to Supported and Client Certificate Authentication to Required, and
then click OK.
14. Navigate to CSIv2 inbound transport. In WebSphere 5.1.1.5, select Security > Authentication
Protocol > CSIv2 Inbound Transport. In WebSphere 6.0.2.9, select Security > Global Security, and
under Authentication, expand Authentication Protocol and select CSIv2 inbound transport.
15. Set Transport to SSL-Required and SSL Settings to localhost/AdsSSL, and then click OK.
16. Navigate to CSIv2 outbound transport. In WebSphere 5.1.1.5, select Security > Authentication
Protocol > CSIv2 Outbound Transport. In WebSphere 6.0.2.9, select Security > Global Security, and
under Authentication, expand Authentication Protocol and select CSIv2 outbound transport.
17. Set Transport to SSL-Required and SSL Settings to localhost/AdsSSL, and then click OK.
18. Navigate to SAS inbound transport. In WebSphere 5.1.1.5, select Security > Authentication Protocol
> SAS Inbound Transport. In WebSphere 6.0.2.9, select Security > Global Security, and under
Authentication, expand Authentication Protocol and select SAS inbound transport.
19. Set SSL Settings to localhost/AdsSSL, and then click OK.
20. Navigate to SAS outbound transport. In WebSphere 5.1.1.5, select Security > Authentication
Protocol > SAS Outbound Transport. In WebSphere 6.0.2.9, select Security > Global Security and
under Authentication expand Authentication Protocol and select SAS outbound transport.
21. Set SSL Settings to localhost/AdsSSL, and then click OK.
22. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers and
click the [server name].
23. Under Container Settings, expand Web container settings and select Web container.
24. Click Web container transport chains, and then click WCInboundDefaultSecure.
25. Click SSL Inbound Channel (SSL_2) and select the SSL repertoire as localhost/AdsSSL.
26. Click OK and save your changes to the Master Configuration.
27. Stop and restart WebSphere. WebSphere Administrative Console now displays a login dialog box in
which you are required to type the user name and password that you specified in step 2.
Adobe LiveCycle
Configuring SSL on WebSphere
Installing and Configuring LiveCycle for WebSphere
Next step
137
28. (WebSphere 5.1.1.5)(LiveCycle Form Manager, LiveCycle Workflow) In the navigation tree, select
Resources > WebSphere JMS Provider and, under Additional Properties, select WebSphere Queue
Connection Factories.
29. (WebSphere 6.0.2.9)(LiveCycle Form Manager, LiveCycle Workflow) In the navigation tree, select
Resources > JMS Providers > Default messaging and, under Connection Factories, select JMS queue
connection factory, and then select QueueConnectionFactory.
30. (WebSphere 5.1.1.5)(LiveCycle Form Manager, LiveCycle Workflow) In the Component-managed
Authentication Alias and Container-managed Authentication Alias lists select, [computer
name]/myAlias and click OK. Repeat this step for each queue you created.
31. (WebSphere 6.0.2.9)(LiveCycle Form Manager, LiveCycle Workflow) In the Component-managed
authentication Alias list, select [computer name]/myAlias and click OK.
32. (LiveCycle Form Manager, LiveCycle Workflow) Under Related Items, select J2C Authentication Data
Entries and ensure that the database user has root privileges, and then click OK.
33. (LiveCycle Form Manager, LiveCycle Workflow) Save your changes to the Master Configuration.
34. (LiveCycle Form Manager, LiveCycle Workflow) Stop and restart WebSphere.
Next step
If you are installing LiveCycle Workflow Business Activity Monitor, you can now configure an application
server for hosting BAM Server. (See “Configuring WebSphere 5.1.1.5 for BAM Server” on page 139 or
“Configuring WebSphere 6.0.2.9 for BAM Server” on page 151.) You can also install
LiveCycle Workflow Designer. (See “Installing LiveCycle Workflow Designer” on page 172.)
Part IV: Additional LiveCycle Workflow Configuration
This section of the guide describes the additional configuration required for LiveCycle Workflow
installations.
138
14
Configuring WebSphere 5.1.1.5 for BAM Server
This chapter only applies to LiveCycle Workflow licenses that permit the use of
Business Activity Monitor.
This chapter describes how to create the BAM metadata database, configure BAM Server for WebSphere
5.1.1. 5, and deploy the BAM Server application. BAM Server is a component of LiveCycle Workflow.
This chapter assumes that you have configured the LiveCycle database. If you have not done this, see
“Preparing Your Environment” on page 30.
Creating the BAM metadata database
You must create a LiveCycle Workflow Business Activity Monitor metadata database to store the
definitions of the process metrics that BAM Server monitors, as well as the details of any alerts and object
run-time data that need to be persisted to disk.
Because Business Activity Monitor metadata can grow quite large, you must allocate at least 50 MB for the
BAM metadata database. For production deployments, allocate at least 200 MB.
BAM Server can require specific settings for some aspects of the Business Activity Monitor metadata
database configuration. The settings depend on the type of application server that is hosting BAM Server
and the type of database server used to store the Business Activity Monitor metadata.
User accounts
You must also create a user account that BAM Server can use to connect to the Business Activity Monitor
metadata database. The user account must have create, modify, and update privileges on the database.
For Oracle, the database user account must be associated with a tablespace that you create specifically for
Business Activity Monitor metadata.
Creating environment variables for DB2
If you are using DB2 as the Business Activity Monitor metadata database, you must create an environment
variable that contains the name of the associated DB2 instance. You also need to include the path to the
DB2 shared libraries in the library path variable.
The following examples show commands for configuring the environment variables. Use the command
that corresponds with your operating system. You may need to modify the command according to the
location where you installed DB2.
Example 14.1 Commands to configure environment variables on Windows
The following commands apply to a DB2 instance named DB2, with DB2 library files installed in
C:\SQLLIB\BIN:
set DB2INSTANCE=DB2
set PATH=C:\SQLLIB\BIN;%PATH%
139
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere for BAM Server
140
Example 14.2 Commands to configure environment variables on Solaris
The following commands apply to a DB2 instance named db2fs, with DB2 library files installed in
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LD_LIBRARY_PATH=/opt/IBM/db2/V8.1/lib:${LD_LIBRARY_PATH}
Example 14.3 Commands to configure environment variables on AIX
The following commands apply to a DB2 instance named db2fs, with DB2 library files installed in
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LIBPATH=/opt/IBM/db2/V8.1/lib:${LIBPATH}
Configuring WebSphere for BAM Server
If you are installing LiveCycle Workflow and you are using Business Activity Monitor, you must manually
configure WebSphere so that BAM Server runs correctly.
You must perform the following tasks:
●
If you have not already done so, create an application server for running BAM Server. (See “Creating an
application server instance” on page 36.)
●
Install the database drivers on the application server that you created for BAM Server. (See “Installing
database drivers for BAM Server” on page 140.)
●
Configure the connection to the BAM metadata database. (See “Configuring the connection to the
BAM metadata database” on page 141.)
●
Create the integration data source. (See “Creating the integration data source” on page 143.)
●
Set application server parameters. (See “Configuring WebSphere parameters” on page 145.)
Installing database drivers for BAM Server
To enable WebSphere to connect to the BAM metadata database, you must install the database drivers to
the computer where WebSphere is installed. The Oracle and DB2 drivers (if required) were already copied
into the ${WAS_INSTALL_ROOT}/db_driver directory in “Installing database drivers” on page 44.
You will also have to remove the ojdbc14.jar file from the [appserver root]/appserver/lib directory of the
WebSphere application server.
➤ To install database drivers for SQL Server:
1. Navigate to the directory named ${WAS_INSTALL_ROOT}/db_driver.
2. Download the SQL Server 2000 Driver for JDBC from www.microsoft.com/sql/downloads. This
download installs the required msbase.jar, mssqlserver.jar, and msutil.jar files.
Note: You may already have these drivers installed on the computer that hosts the database. (See
“Installing JTA stored procedures” on page 33.)
3. Copy the mssqlserver.jar, msbase.jar, and msutil.jar files into the ${WAS_INSTALL_ROOT}/db_driver
directory.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring the connection to the BAM metadata database
141
Configuring the connection to the BAM metadata database
You must configure a data source on WebSphere for the BAM metadata database so that BAM Server can
retrieve information about process metrics that it needs to monitor:
●
(DB2) Create a JAAS authentication alias for the BAM metadata database. (See “Creating a JAAS
authentication alias for the BAM metadata database on DB2” on page 141.)
●
Create the JDBC connection pool. (See “Creating the JDBC provider for the BAM metadata database”
on page 141.)
●
Create the data source. (See “Creating the data source for the BAM metadata database” on page 142.)
Creating a JAAS authentication alias for the BAM metadata database on DB2
If you are storing BAM metadata in a DB2 database, you must create a JAAS authentication alias for a user
account that can access the BAM metadata database.
➤ To create a JAAS authentication alias for the BAM metadata database on DB2:
1. Start WebSphere Application Server.
2. In the WebSphere Administrative Console navigation panel, select Security > JAAS Configuration >
J2C Authentication Data.
3. On the J2C Authentication Data Entries page, click New.
4. On the page that appears, specify values for the following properties, and then click OK:
●
Alias: A name for the alias. Type BAMDB2
●
User ID: The user name for the user account that can access the BAM metadata database on DB2.
●
Password: The password associated with the specified User ID.
●
Description: (Optional) A description of the alias.
Creating the JDBC provider for the BAM metadata database
You must create the JDBC provider that you use to create the connection to the BAM metadata database.
➤ To create the JDBC provider:
1. Start WebSphere Application Server.
2. In the WebSphere Administrative Console navigation panel, select Resources > JDBC Providers.
3. In the Server box of the Scope area, enter the name of the server instance you created for BAM Server
and click New.
4. From the JDBC Provider menu, select the database driver according to the type of database you are
using to store BAM metadata, and then click Apply:
●
(Oracle) Select Oracle JDBC Driver.
●
(DB2) Select DB2 Universal JDBC Driver Provider.
●
(SQL Server) Select WebSphere embedded ConnectJDBC driver for MS SQL Server.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring the connection to the BAM metadata database
142
5. In the Classpath box, add the file paths after any other entries in the box according to the type of
database that you are using to store BAM metadata. If you need to add more than one classpath,
ensure that you include a carriage return after each path:
●
Oracle:
{WAS_INSTALL_ROOT}/db_driver/ojdbc14.jar
●
DB2:
{WAS_INSTALL_ROOT}/db_driver/db2jcc.jar
{WAS_INSTALL_ROOT}/db_driver/db2jcc_license_cu.jar
●
SQL Server:
{WAS_INSTALL_ROOT}/db_driver/mssqlserver.jar
{WAS_INSTALL_ROOT}/db_driver/msbase.jar
{WAS_INSTALL_ROOT}/db_driver/msutil.jar
Note: Ensure that you do not delete any existing entries in the Classpath box.
6. Click OK at the bottom of the tab.
7. Save your changes to the Master Configuration.
Creating the data source for the BAM metadata database
You must create a data source so that BAM Server can connect to the BAM metadata database.
➤ To create the data source for the BAM metadata database:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. Click the JDBC provider that you created for the BAM metadata database.
3. In the Additional Properties table, select Data Sources.
4. Click New, specify the following values for the properties, and then click OK:
●
Name: com.celequest.metadata.metaDatasource
●
JNDI Name: jdbc/com.celequest.metadata.metaDatasource
●
Container managed persistence: Deselect this option
●
Datasource Helper Class Name: (Oracle 10g only)
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
●
Container-managed Authentication Alias: (DB2) BAMDB2 (See “Creating a JAAS authentication
alias for the BAM metadata database on DB2” on page 141.)
5. On the Data Sources page, click com.celequest.metadata.metaDatasource, and then click Custom
Properties.
6. (Oracle) Click URL, type the following value for the URL property, and then click OK:
jdbc:oracle:thin:@[host_name]:[port]:[BAM_DB_Name]
where[host_name] is the name of the computer on which Oracle is running,[port] is the port used
to access the Oracle database and [BAM_DB_Name] is the name of the BAM Oracle database.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Creating the integration data source
143
7. (SQL Server, DB2) Specify values for the following properties according to the type of database you are
using to store the BAM metadata:
●
DB2:
serverName: The computer name or IP address of the computer hosting DB2.
portNumber: The port used to access DB2. The default value is 50000.
databaseName: [BAM_DB_Name] (See “Creating the BAM metadata database” on page 139.)
●
SQL Server:
serverName: The host name or IP address of the machine running the database.
portNumber: The port used to access SQL Server. The default value is 1433.
databaseName: [BAM_DB_Name] (See “Creating the BAM metadata database” on page 139.)
8. On the Custom Properties page, click New, specify values for the following properties, and then click
OK:
●
Name: user (This property is case-sensitive and must be in lowercase.)
●
Value: The user name of the account that can access the BAM metadata database. (See “Creating
the BAM metadata database” on page 139.)
●
Description: (Optional) A description for the property.
9. On the Custom Properties page, click New, specify values for the following properties, and then click
OK:
●
Name: password (This property is case-sensitive and must be in lowercase.)
●
Value: The password for the user account that can access the BAM metadata database
●
Description: (Optional) A description for the property.
10. Save the changes to the Master Configuration.
Testing the database connection
You should test the JDBC provider configuration using the test connection feature in WebSphere.
➤ To test the database connection:
1. In the WebSphere Administrative Console navigation tree, select JDBC Providers > [Provider] >
Data Sources.
2. Select the com.celequest.metadata.metaDatasource provider.
3. Click Test Connection.
The Message box at the top of the page displays the results of the test. If the test fails, use the
WebSphere error reporting features to locate the cause of the problem.
Creating the integration data source
You must create a data source so that BAM Server can connect to the LiveCycle database.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Creating the integration data source
144
➤ To create the data source for the LiveCycle database:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. Click the JDBC provider that you created for the BAM metadata database.
3. In the Additional Properties table, select Data Sources.
4. Click New, specify the following values for the properties, and then click Apply:
●
Name: com.celequest.adobe
●
JNDI Name: jdbc/com.celequest.adobe
●
Container managed persistence: Deselect
●
Datasource Helper Class Name: (Oracle 10g only)
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
5. Click Custom Properties.
6. (Oracle) Click URL, type the following value for the URL property, and then save your changes to the
master configuration:
jdbc:oracle:thin:@[host_name]:[port]:[BAM_DB_Name]
where [host_name] is the name of the computer on which Oracle is running, and [port] is the port
used to access the Oracle database and [BAM_DB_Name] is the name of the LiveCycle database.
7. (DB2) Specify values for the following properties according to the type of database you are using to
store the BAM metadata:
serverName: The computer name or IP address of the computer hosting DB2.
portNumber: The port used to access DB2. The default value is 50000.
databaseName: The LiveCycle database name.
8. (SQL Server) Specify values for the following properties according to the type of database you are using
to store the BAM metadata:
serverName: The host name or IP address of the machine running the database.
portNumber: The port used to access SQL Server. The default value is 1433.
databaseName: The LiveCycle database name.
9. Under Related Items, select J2C Authentication Data Entries.
10. Click New and, in the Alias box, type a name (for example, MyAliasLiveCycle).
11. Enter the user account [LiveCycle DB Admin] and the associated password, click Apply, and then
click OK.
12. Save the changes to the Master Configuration.
13. Navigate back to JDBC Providers > [BAM metadata database] > Data Sources and select
com.celequest.adobe.
14. In the Component-managed Authentication Alias box, select the JAAS authentication alias that points
to the Adobe LiveCycle database that you entered in step 10, and then click OK.
15. Save the changes to the Master Configuration.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere parameters
145
Testing the database connection
You should test the JDBC provider configuration using the test connection feature in WebSphere.
➤ To test the database connection:
1. In the WebSphere Administrative Console navigation tree, select JDBC Providers > [Provider] >
Data Sources.
2. Select the com.celequest.adobe provider.
3. Click Test Connection.
The Message box at the top of the page displays the results of the test. If the test fails, use the
WebSphere error reporting features to locate the cause of the problem.
Configuring WebSphere parameters
You must configure several WebSphere server parameters to support BAM Server.
➤ To set application server parameters:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers and
click the name of the application server on which you will deploy BAM Server.
2. Click the Configuration tab and, under Additional Properties, click Process Definition.
3. On the Process Definition page, under Additional Properties, click Java Virtual Machine.
4. On the Java Virtual Machine configuration page, specify values in the Initial Heap and Maximum
Heap boxes.
These settings depend on your system capabilities and you should set them as high as possible. The
minimum recommended values are 128 and 512.
5. Add the following text in the Generic JVM Arguments box to configure UTF-8 support:
-Dfile.encoding=utf8
6. Under Additional Properties, click Custom Properties, click New, and then specify values for the
following property:
●
Name: com.celequest.metadata.jdbcDriver.
●
Value: Specify one of the following values, depending on the type of database you use to store BAM
metadata:
●
(Oracle) oracle.jdbc.driver.OracleDriver
●
(SQL Server) com.microsoft.jdbc.sqlserver.SQLServerDriver
●
(DB2) com.ibm.db2.jcc.DB2Driver
7. Click OK to apply your changes and return to the Custom Properties page.
8. Click New to create the com.celequest.metadata.jdbcURL property and type the name and value for
the custom property:
●
Name: com.celequest.metadata.jdbcURL.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
●
Configuring WebSphere parameters
146
Value: Specify one of the following values, depending on the type of database used to store BAM
metadata:
●
DB2:
jdbc:
db2://[host_name]:[port][BAM _DB_Name]:user=[username];password=
[password];
where[host_name] is the name of the computer on which DB2 is running, [port] is the port
used to access the DB2 database represented by the [BAM _DB_Name] in the URL,[username] is
the name of the user account used to access the database, and [password] is the password for
the user name specified for the [USERNAME] parameter.
●
SQL Server:
jdbc:microsoft:sqlserver://[host_name]:[port];databaseName=
[BAM _DB_Name];selectMethod=Cursor;user=[BAM _DB_Admin];
password=[password]
where[host_name] is the name of the computer on which SQL Server is running, [port] is the
port used to access the SQL Server database represented by the [BAM _DB_Name] in the URL, and
[password] is the password for the [BAM _DB_Admin]user account.
●
Oracle:
jdbc:oracle:thin:[BAM _DB_Admin]/[password]@[host_name]:[port]:
[BAM _DB_Name]
where[password] is the password for the user account name specified for the database user
[BAM _DB_Admin], [host_name] is the name of the computer on which Oracle is running,
[port] is the port used to access the Oracle database, represented by the [BAM _DB_Name]in the
URL.
This value must match the Oracle URL you specified in the data source for the BAM metadata
database. (See “Creating the data source for the BAM metadata database” on page 142.)
9. (Optional) Click New to create a new property for specifying optional JVM properties that are related to
the BAM metadata database, and type the name and value for the custom property:
●
Name: Type the name of the property using the following format:
com.celequest.property.[PARAMETER]
●
Value: Type the value for the property.
For information about optional JVM property names and values, see “Optional WebSphere JVM
parameters” on page 147.
10. Repeat step 9 for each optional JVM property that you want to specify.
11. Click OK and save your changes to the Master Configuration.
12. Return to the main server page by clicking the server name at the top of the page, and then click
Transaction Service under Additional Properties.
13. On the Transaction Service page, in the Total transaction lifetime timeout box, type 600.
14. Click OK to return to the Custom Properties page.
15. Save your changes to the Master Configuration.
16. Restart WebSphere.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Optional WebSphere JVM parameters
147
Optional WebSphere JVM parameters
You can set several optional JVM parameters that are related to the Business Activity Monitor metadata
database, including language, country, and collation strength. These JVM parameters are expressed using
custom properties of the Java virtual machine. The custom properties have the following attributes:
●
Name: com.celequest.property.[PARAMETER]
●
Value:[VALUE]
This table provides valid values for [PARAMETER] and [VALUE].
Parameter
Description
LANGUAGE
The ISO language code for the server.
For example, to set the language to Portuguese, the custom property named
com.celequest.property.LANGUAGE has the value PT.
COUNTRY
The ISO country code for the server.
LOCALESORT
This option specifies whether locale-sensitive string comparisons are performed.
Valid values are true and false:
●
Specify true if you want locale-sensitive string comparisons performed.
●
Specify false if you do not want locale-sensitive string comparisons
performed.
The default value is false.
STRENGTH
The level of collation strength, which is the extent to which non-English
characters are compared and collated.
Valid values (in order of least discriminating to most discriminating) are primary,
secondary, tertiary, and identical. The default value is tertiary.
For more information about collation parameters, see the Sun Java
documentation at http://java.sun.com/j2se/1.4.2/docs/api/java/util/Locale.html.
Note: This setting is functional only if LOCALESORT is set to true.
DECOMPOSITION
The mode of collation decomposition. Valid values are none, canonical, and
full. The default value is canonical.
For more information about collation parameters, see the Sun Java
documentation at http://java.sun.com/j2se/1.4.2/docs/api/java/util/Locale.html
Note: This setting is functional only if LOCALESORT is set to true.
Creating a virtual host alias
You need to create a host alias for the port that provides access to the BAM Server service. After you create
the alias, you need to use Administrator to update the LiveCycle Workflow Server settings with the new
URL for BAM Server.
➤ To create a virtual host alias:
1. In the WebSphere Administrative Console navigation tree, select Environment > Virtual Hosts.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Deploying BAM Server to WebSphere
148
2. Click default host.
3. Under Additional Properties, click Host Aliases.
4. Click New, specify the following values for the properties, and click OK:
●
Name: *
●
Value: 9091
5. Save your changes to the master configuration.
Deploying BAM Server to WebSphere
You need to deploy the BAM Server EAR file (CAS_Adobe.ear) to the application server that you configured
for running BAM Server. You also need to deploy the BAM Server integration EAR file (CQIntegration.ear) to
the application server that you configured for running LiveCycle Workflow Server.
On Windows, to avoid deployment issues, you need to predeploy the BAM Server EAR file. Before you
perform the following procedure, ensure that any previous installations of BAM Server are stopped and
uninstalled, and that WebSphere Application Server is not running.
➤ (Windows) To predeploy the BAM Server EAR file:
1. Create a working directory, such as c:\wrk.
2. Create a temporary directory, such as c:\tmp.
3. Create a destination directory, such as c:\bam.
4. Copy the CAS_Adobe.ear file from the [LiveCycle_root]/components/bam/common directory to the
working directory you created.
5. From a command prompt, change the current working directory to the [appserver root]/AppServer/bin
directory.
6. Enter the following command to create a new EAR file with deployed EJBs:
ejbDeploy.bat [working_directory]/CAS_Adobe.ear
[temporary_directory]
[destination_directory]/CAS_websphere_deploy.ear
where [working_directory] is the working directory you created, [temporary_directory] is
the temporary directory you created, and [destination_directory] is the destination directory
you created.
This command creates a new EAR file named CAS_websphere_deploy.ear in the
[destination_directory] directory.
Note: When the command is completed, ensure that the command shell indicates that 0 errors
occurred. It is acceptable if there is one warning and one info message.
➤ To deploy the BAM Server EAR file:
1. Start WebSphere Application Server and the BAM application server instance that you created in
“Creating an application server instance” on page 36.
Adobe LiveCycle
Configuring WebSphere 5.1.1.5 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Deploying BAM Server to WebSphere
149
2. In the WebSphere Administrative Console navigation tree, select Applications > Enterprise
Applications.
3. Click Install.
4. Specify the path to the Business Activity Monitor EAR file, and then click Next:
●
(Windows) Specify the EAR file that was created when you predeployed the BAM Server EAR file,
which is [destination_directory]/CAS_websphere_deploy.ear.
●
(Linux, UNIX) Specify [LiveCycle_root]/components/bam/common/CAS_Adobe.ear.
The first of a series of configuration pages appears.
5. Select Generate Default Bindings, and then click Next.
6. In the Directory to Install Application box, type the server-side directory path where you want to
install the application and then click Next.
7. In the Deploy EJBs Option - Database Type menu, select the type of database that you are using to
store BAM metadata, and then click Next:
●
(DB2) Select DB2UDB_V81.
●
(SQL Server) Select MSSQLSERVER_2000.
●
(Oracle) Select ORACLE_V9I.
8. Click Step 6.
9. Select both the ejb-jar.xml and web.xml files.
10. Under Clusters and Servers, select the instance that you created for the BAM server, and click Apply.
Ensure that these modules are now pointing to the BAM server instance and click Next.
11. Click Step 8 to view the Summary page.
12. Click Finish.
➤ To deploy the CQIntegration.ear file:
1. In the WebSphere Administrative Console navigation tree, select Applications > Install New
Application.
2. Click Browse to navigate to the [LiveCycle root]/components/bam/common directory, and select the
CQIntegration.ear file. You do not need to type a context root value.
3. Click Next. On the first screen, select Generate Default Bindings and click Next.
4. On the Application Security Warnings screen, click Continue.
5. Click Step 2 and, under Listener Port for the BAM Integration EJB module, type:
AdobeTemplateEventMDBTopicListener
6. Click Step 4.
7. Select both the ejb-jar.xml and web.xml modules.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere 5.1.1.5 for BAM Server
Next Step
150
8. Under Clusters and Servers, select the server instance that you created for running
LiveCycle Workflow Server, and then click Apply. Ensure that these modules are now pointing to the
LiveCycle server instance and click Next.
9. Click Finish.
10. Click Save to Master Configuration, and then click Save.
➤ To start the CQIntegration.ear
1. In the WebSphere Administrative Console navigation tree, select Applications > Enterprise
Applications.
2. Select BAM Integration and click Start.
Next Step
You must now configure the BAM properties on LiveCycle Workflow Server and BAM Server. (See “Getting
Started with BAM Server” on page 164.)
15
Configuring WebSphere 6.0.2.9 for BAM Server
This chapter only applies to LiveCycle Workflow licenses that permit the use of
Business Activity Monitor.
This chapter describes how to create the BAM metadata database, configure BAM Server for WebSphere
6.0.2.9, and deploy the BAM Server application. BAM Server is a component of LiveCycle Workflow.
This chapter assumes that you have configured the LiveCycle database. If you have not done this, see
“Preparing Your Environment” on page 30.
Creating the BAM metadata database
You must create a LiveCycle Workflow Business Activity Monitor metadata database to store the
definitions of the process metrics that BAM Server monitors, as well as the details of any alerts and object
run-time data that need to be persisted to disk.
Because Business Activity Monitor metadata can grow quite large, you must allocate at least 50 MB for the
BAM metadata database. For production deployments, allocate at least 200 MB.
BAM Server can require specific settings for some aspects of the Business Activity Monitor metadata
database configuration. The settings depend on the type of application server that is hosting BAM Server
and the type of database server used to store the Business Activity Monitor metadata.
User accounts
You must also create a user account that BAM Server can use to connect to the Business Activity Monitor
metadata database. The user account must have create, modify, and update privileges on the database.
Creating environment variables for DB2
If you are using DB2 as the Business Activity Monitor metadata database, you must create an environment
variable that contains the name of the associated DB2 instance. You also need to include the path to the
DB2 shared libraries in the library path variable.
The following examples show commands for configuring the environment variables. Use the command
that corresponds with your operating system. You may need to modify the command according to the
location where you installed DB2.
Example 15.1 Commands to configure environment variables on Windows
The following commands apply to a DB2 instance named DB2, with DB2 library files installed in
C:\SQLLIB\BIN:
set DB2INSTANCE=DB2
set PATH=C:\SQLLIB\BIN;%PATH%
151
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere for BAM Server
152
Example 15.2 Commands to configure environment variables on AIX
The following commands apply to a DB2 instance named db2fs, with DB2 library files installed in
/opt/IBM/db2/V8.1/lib:
export DB2INSTANCE=db2fs
export LIBPATH=/opt/IBM/db2/V8.1/lib:${LIBPATH}
Configuring WebSphere for BAM Server
If you are installing LiveCycle Workflow and you are using Business Activity Monitor, you must manually
configure WebSphere so that BAM Server runs correctly.
You must perform the following tasks:
●
If you have not already done so, create an application server for running BAM Server. (See “Creating an
application server instance” on page 36.)
●
Install the database drivers on the application server that you created for BAM Server. (See “Installing
database drivers for BAM Server” on page 152.)
●
Create the integration data source. (See “Creating the Integration data source” on page 156.)
●
Configure the connection to the BAM metadata database. (See “Configuring the connection to the
BAM metadata database” on page 152.)
●
Set application server parameters. (See “Configuring WebSphere parameters” on page 157.)
Installing database drivers for BAM Server
To enable WebSphere to connect to the BAM metadata database, you must install the database drivers to
the computer where WebSphere is installed. The Oracle and DB2 drivers (if required) were already copied
into the ${WAS_INSTALL_ROOT}/db_driver directory in “Installing database drivers” on page 44.
You will also have to remove the ojdbc14.jar file from the [appserver root]/appserver/lib directory of the
WebSphere application server.
➤ To install database drivers for SQL Server:
1. Navigate to the directory named ${WAS_INSTALL_ROOT}/db_driver.
2. Download the SQL Server 2000 Driver for JDBC from www.microsoft.com/sql/downloads. This
download installs the required msbase.jar, mssqlserver.jar, and msutil.jar files.
Note: You may already have these drivers installed on the computer that hosts the database. (See
“Installing JTA stored procedures” on page 33.)
3. Copy the mssqlserver.jar, msbase.jar, and msutil.jar files into the ${WAS_INSTALL_ROOT}/db_driver
directory.
Configuring the connection to the BAM metadata database
You must configure a data source on WebSphere for the BAM metadata database so that BAM Server can
retrieve information about process metrics that it needs to monitor:
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring the connection to the BAM metadata database
153
●
(DB2) Create a JAAS authentication alias for the BAM metadata database. (See “Creating a JAAS
authentication alias for the BAM metadata database on DB2” on page 153.)
●
Create the JDBC connection pool. (See “Creating the JDBC provider for the BAM metadata database”
on page 153.)
●
Create the data source. (See “Creating the data source for the BAM metadata database” on page 154.)
Creating a JAAS authentication alias for the BAM metadata database on DB2
If you are storing BAM metadata in a DB2 database, you must create a JAAS authentication alias for a user
account that can access the BAM metadata database.
➤ To create a JAAS authentication alias for the BAM metadata database on DB2:
1. Start WebSphere Application Server.
2. In the WebSphere Administrative Console navigation panel, select Security > Global Security > JAAS
Configuration > J2C Authentication Data.
3. On the J2C Authentication Data Entries page, click New.
4. On the page that appears, specify values for the following properties, and then click OK:
●
Alias: A name for the alias. Type BAMDB2
●
User ID: The user name for the user account that can access the BAM metadata database on DB2.
●
Password: The password associated with the specified User ID.
●
Description: (Optional) A description of the alias.
Creating the JDBC provider for the BAM metadata database
You must create the JDBC provider that you use to create the connection to the BAM metadata database.
➤ To create the JDBC provider:
1. Start WebSphere Application Server.
2. In the WebSphere Administrative Console navigation panel, select Resources > JDBC Providers.
3. In the JDBC providers area, select the scope you created for the BAM server, click Apply and then click
New.
4. From the JDBC Provider menu, select the database driver according to the type of database you are
using to store BAM metadata.
5. (Oracle) Select the following values:
●
Oracle in Step 1
●
Oracle JDBC Driver in Step 2
●
Connection pool data source in Step 3
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring the connection to the BAM metadata database
6. (DB2) Select the following values:
●
DB2 in Step 1
●
DB2 Universal JDBC Driver Provider in Step 2
●
Connection pool data source in Step 3
7. (SQL Server) Select the following values:
●
SQL Server in Step 1
●
WebSphere embedded ConnectJDBC driver for MS SQL Server in Step 2
●
Connection pool data source in Step 3
8. Click Next, and then click Apply.
9. In the Classpath box, add the file paths after any other entries in the box according to the type of
database that you are using to store BAM metadata. If you need to add more than one classpath,
ensure that you include a carriage return after each path:
●
Oracle:
{WAS_INSTALL_ROOT}/db_driver/ojdbc14.jar
●
DB2:
{WAS_INSTALL_ROOT}/db_driver/db2jcc.jar
{WAS_INSTALL_ROOT}/db_driver/db2jcc_license_cu.jar
●
SQL Server:
{WAS_INSTALL_ROOT}/db_driver/mssqlserver.jar
{WAS_INSTALL_ROOT}/db_driver/msbase.jar
{WAS_INSTALL_ROOT}/db_driver/msutil.jar
Note: Ensure that you do not delete any existing entries in the Classpath box.
10. Click OK at the bottom of the tab.
11. Save your changes to the Master Configuration.
Creating the data source for the BAM metadata database
You must create a data source so that BAM Server can connect to the BAM metadata database.
➤ To create the data source for the BAM metadata database:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. Click the JDBC provider that you created for the BAM metadata database.
3. In the Additional Properties table, select Data Sources.
4. Click New, specify the following values for the properties:
●
Name: com.celequest.metadata.metaDatasource
●
JNDI Name: jdbc/com.celequest.metadata.metaDatasource
●
Container managed persistence: Select this option
154
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
●
Configuring the connection to the BAM metadata database
155
Datasource Helper Class Name: (Oracle 10g only)
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
●
Container-managed Authentication Alias: (DB2) BAMDB2 (See “Creating a JAAS authentication
alias for the BAM metadata database on DB2” on page 153.)
5. (Oracle) Click URL, type the following value for the URL property, and then click Apply:
jdbc:oracle:thin:@[host name]:[port]:[BAM DB Name]
where [host_name] is the name of the computer on which Oracle is running, and [port] is the port
used to access the Oracle database and [BAM DB Name] is the name of the Oracle database.
6. (Oracle) Under Related Items, select J2EE Connector Architecture (J2C) authentication data entries.
7. (Oracle) Click New and, in the Alias box, type a name (for example, MyAlias).
8. (Oracle) Use the [BAM DB Admin] for the user account, and the associated password, click Apply, and
then click OK.
9. (SQL Server, DB2) Specify values for the following properties according to the type of database you are
using to store the BAM metadata:
●
DB2:
serverName: The computer name or IP address of the computer hosting DB2.
portNumber: The port used to access DB2. The default value is 50000.
databaseName: [BAM DB Name] (See “Configuring WebSphere for BAM Server” on page 152.)
●
SQL Server:
serverName: The host name or IP address of the machine running the database.
portNumber: The port used to access SQL Server. The default value is 1433.
databaseName: [BAM DB Name] (See “Configuring WebSphere for BAM Server” on page 152.)
10. Click Apply, then under Additional Properties, click Custom Properties.
11. On the Custom Properties page, click New, specify values for the following properties, and then click
OK:
●
Name: user (This property is case-sensitive and must be in lowercase.)
●
Value: The user name of the account that can access the BAM metadata database. (See
“Configuring WebSphere for BAM Server” on page 152.)
●
Description: (Optional) A description for the property.
12. On the Custom Properties page, click New, specify values for the following properties, and then click
OK:
●
Name: password (This property is case-sensitive and must be in lowercase.)
●
Value: The password for the user account that can access the BAM metadata database
●
Description: (Optional) A description for the property.
13. Save the changes to the Master Configuration.
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Creating the Integration data source
156
Testing the database connection
You should test the JDBC provider configuration using the test connection feature in WebSphere.
➤ To test the database connection:
1. In the WebSphere Administrative Console navigation tree, select JDBC Providers > [Provider] > Data
Sources.
2. Select the com.celequest.metadata.metaDatasource provider.
3. Click Test Connection.
The Message box at the top of the page displays the results of the test. If the test fails, use the
WebSphere error reporting features to locate the cause of the problem.
Creating the Integration data source
You must create a data source so that BAM Server can connect to the LiveCycle database.
➤ To create the data source for the LiveCycle database:
1. In the WebSphere Administrative Console navigation tree, select Resources > JDBC Providers.
2. Click the JDBC provider that you created for the BAM metadata database.
3. Under Additional Properties, select Data Sources.
4. Click New, specify the following values for the properties, and then click OK:
●
Name: com.celequest.adobe
●
JNDI Name: jdbc/com.celequest.adobe
●
Container managed persistence: Select this option
●
Datasource Helper Class Name: (Oracle 10g Only)
com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
5. (Oracle) Click URL, type the following value for the URL property, and then click Apply:
jdbc:oracle:thin:@[host]:[port]:[database]
where [host] is the name of the computer on which Oracle is running, [port] is the port used to
access the Oracle database and [database] is the name of the LiveCycle database.
6. (DB2) Specify values for the following properties and click Apply:
●
serverName: The computer name or IP address of the computer hosting DB2.
●
portNumber: The port used to access DB2. The default value is 50000.
●
databaseName: The LiveCycle database name.
7. (SQL Server) Specify values for the following properties and click Apply:
●
serverName: The host name or IP address of the machine running the database.
●
portNumber: The port used to access SQL Server. The default value is 1433.
●
databaseName: The LiveCycle database name.
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere parameters
157
8. Under Related Items, select J2EE Connector Architecture (J2C) authentication data entries.
9. Click New and, in the Alias box, type a name (for example, MyAliasLiveCycle).
10. Enter the user account [LiveCycle DB Admin], and the associated password, click Apply and then click
OK.
11. Save your changes to the Master Configuration.
12. Navigate back to JDBC Providers > [BAM metadata database] > Data Sources and select
com.celequest.adobe.
13. In the Component-managed Authentication Alias box, select the JAAS authentication alias that
points to the Adobe LiveCycle database (MyAliasLiveCycle), and then click OK.
14. Save the changes to the Master Configuration.
Testing the Integration database connection
You should test the JDBC provider configuration using the test connection feature in WebSphere.
➤ To test the database connection:
1. In the WebSphere Administrative Console navigation tree, select JDBC Providers > [Provider] > Data
Sources.
2. Select com.celequest.adobe.
3. Click Test Connection.
The Message box at the top of the page displays the results of the test. If the test fails, use the
WebSphere error reporting features to locate the cause of the problem.
Configuring WebSphere parameters
You must configure several WebSphere server parameters to support BAM Server.
➤ To set application server parameters:
1. In the WebSphere Administrative Console navigation tree, select Servers > Application Servers and
click the name of the application server on which you will deploy BAM Server.
2. Click the Configuration tab and, under Server Infrastructure, expand Java and Process Management,
and then click Process Definition.
3. On the Process Definition page, under Additional Properties, click Java Virtual Machine.
4. On the Java Virtual Machine configuration page, specify values in the Initial Heap and Maximum
Heap boxes.
These settings depend on your system capabilities and you should set them as high as possible. The
minimum recommended values are 128 and 512.
5. Add the following text in the Generic JVM Arguments box to configure UTF-8 support:
-Dfile.encoding=utf8
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere parameters
158
6. Click Apply.
7. Under Additional Properties, click Custom Properties, click New, and then specify values for the
following property:
●
Name: com.celequest.metadata.jdbcDriver.
●
Value: Specify one of the following values, depending on the type of database you use to store BAM
metadata:
●
(Oracle) oracle.jdbc.driver.OracleDriver
●
(SQL Server) com.microsoft.jdbc.sqlserver.SQLServerDriver
●
(DB2) com.ibm.db2.jcc.DB2Driver
8. Click OK to apply your changes and return to the Custom Properties page.
9. Click New to create the com.celequest.metadata.jdbcURL property and type the name and value for
the custom property:
●
Name: com.celequest.metadata.jdbcURL.
●
Value: Specify one of the following values, depending on the type of database used to store BAM
metadata:
●
DB2:
jdbc:
db2://[host_name]:[port]/[BAM DB Name]:user=[username];password=
[password];
where[host_name] is the name of the computer on which DB2 is running, [port] is the port
used to access the DB2 database represented by the [BAM DB Name] in the URL, [username] is
the name of the user account used to access the database, and [password] is the password for
the user name specified for the [username] parameter.
●
SQL Server:
jdbc:microsoft:sqlserver://[host_name]:[port];databaseName=
[BAM DB Name]
;selectMethod=Cursor;user=[BAM DB Admin];password=[password]
where[host_name] is the name of the computer on which SQL Server is running, [port] is the
port used to access the SQL Server database, and [password] is the password for the [BAM DB
Admin] user account.
●
Oracle:
jdbc:oracle:thin:[BAM DB Admin]/[password]@[host name]:[port]:
[BAM DB Name]
where[password] is the password for the user account name specified for the database user [BAM
DB Admin], [host_name] is the name of the computer on which Oracle is running, and [port] is
the port used to access the Oracle database, represented by the [BAM DB Name] in the URL.
This value must match the Oracle URL you specified in the data source for the BAM metadata
database. (See “Creating the data source for the BAM metadata database” on page 154.)
10. (Optional) Click New to create a new property for specifying optional JVM properties that are related to
the BAM metadata database, and type the name and value for the custom property:
●
Name: Type the name of the property using the following format:
com.celequest.property.[PARAMETER]
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
●
Optional WebSphere JVM parameters
159
Value: Type the value for the property.
For information about optional JVM property names and values, see “Optional WebSphere JVM
parameters” on page 159.
11. Repeat step 10 for each optional JVM property that you want to specify.
12. Click OK and save your changes to the Master Configuration.
13. Return to the main server page by clicking the server name at the top of the page, under Container
Settings, expand Container Services and then click Transaction Service.
14. On the Transaction Service page, in the Total transaction lifetime timeout box, type 600.
15. Click OK to return to the Custom Properties page.
16. Save your changes to the Master Configuration.
17. Restart WebSphere.
Optional WebSphere JVM parameters
You can set several optional JVM parameters that are related to the Business Activity Monitor metadata
database, including language, country, and collation strength. These JVM parameters are expressed using
custom properties of the Java virtual machine. The custom properties have the following attributes:
●
Name: com.celequest.property.[PARAMETER]
●
Value:[VALUE]
This table provides valid values for [PARAMETER] and [VALUE].
Parameter
Description
LANGUAGE
The ISO language code for the server.
For example, to set the language to Portuguese, the custom property named
com.celequest.property.LANGUAGE has the value PT.
COUNTRY
The ISO country code for the server.
LOCALESORT
This option specifies whether locale-sensitive string comparisons are performed.
Valid values are true and false:
●
Specify true if you want locale-sensitive string comparisons performed.
●
Specify false if you do not want locale-sensitive string comparisons
performed.
The default value is false.
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Deploying BAM Server to WebSphere
Parameter
Description
STRENGTH
The level of collation strength, which is the extent to which non-English
characters are compared and collated.
160
Valid values (in order of least discriminating to most discriminating) are primary,
secondary, tertiary, and identical. The default value is tertiary.
For more information about collation parameters, see the Sun Java
documentation at http://java.sun.com/j2se/1.4.2/docs/api/java/util/Locale.html.
Note: This setting is functional only if LOCALESORT is set to true.
DECOMPOSITION
The mode of collation decomposition. Valid values are none, canonical, and
full. The default value is canonical.
For more information about collation parameters, see the Sun Java
documentation at http://java.sun.com/j2se/1.4.2/docs/api/java/util/Locale.html
Note: This setting is functional only if LOCALESORT is set to true.
Deploying BAM Server to WebSphere
You need to deploy the BAM Server EAR file (CAS_Adobe.ear) to the application server that you configured
for running BAM Server. You also need to deploy the BAM Server integration EAR file (CQIntegration.ear) to
the application server that you configured for running LiveCycle Workflow Server.
On Windows, to avoid deployment issues, you need to predeploy the BAM Server EAR file. Before you
perform the following procedure, ensure that any previous installations of BAM Server are stopped and
uninstalled, and that WebSphere Application Server is not running.
➤ (Windows) To predeploy the BAM Server EAR file:
1. Create a working directory, such as c:\wrk.
2. Create a temporary directory, such as c:\tmp.
3. Create a destination directory, such as c:\bam.
4. Copy the CAS_Adobe.ear file from the [LiveCycle_root]/components/bam/common directory to the
working directory you created.
5. From a command prompt, change the current working directory to the [appserver root]/AppServer/bin
directory.
6. Enter the following command to create a new EAR file with deployed EJBs:
ejbDeploy.bat [working_directory]/CAS_Adobe.ear
[temporary_directory] [destination_directory]/CAS_websphere_deploy.ear
where [working_directory] is the working directory you created, [temporary_directory] is
the temporary directory you created, and [destination_directory] is the destination directory
you created.
This command creates a new EAR file named CAS_websphere_deploy.ear in the
[destination_directory] directory.
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Deploying BAM Server to WebSphere
161
Note: When the command is completed, ensure that the command shell indicates that 0 errors
occurred. It is acceptable if there is one warning and one info message.
➤ To deploy the BAM Server EAR file:
1. Start WebSphere Application Server and the BAM application server instance that you created in
“Creating an application server instance” on page 36.
2. In the navigation tree, select Applications > Install New Application.
3. Click Browse to navigate to the [appserver root]/InstallableApps directory, and specify the path to the
Business Activity Monitor EAR file, and then click Next:
●
(Windows) Specify the EAR file that was created when you predeployed the BAM Server EAR file,
which is [destination_directory]/CAS_websphere_deploy.ear.
●
(Linux, UNIX) Specify [LiveCycle_root]/components/bam/common/CAS_Adobe.ear.
4. Select Generate Default Bindings, and then click Next.
5. In the Directory to Install Application box, type the server-side directory path where you want to
install the application, and then click Next.
6. In Map modules to servers:
●
Select both the ejb-jar.xml and web.xml files.
●
Under Clusters and Servers, select the server instance that you created for running
LiveCycle Workflow Server, and then click Apply. Ensure that these modules are now pointing to the
BAM server instance and click Next.
7. In the Deploy EJBs Option - Database Type menu, select the type of database that you are using to
store BAM metadata, and then click Next:
●
(DB2) Select DB2UDB_V81.
●
(SQL Server) Select MSSQLSERVER_2000.
●
(Oracle) Select ORACLE_V9I.
Note: (Windows) The Deploy EJBs Option - Database Type step will not appear during the
installation.
8. Provide JNDI Names for Beans, and verify that the JNDI box is set to pre-populated using
ejb/PublishRowSession and click Next.
9. Accept the default values by clicking Next until Summary page appears, and then click Finish.
Note: (Websphere 6.0.2.9) You may receive a Resource Warning message, you can safely ignore it
10. Save your changes to the Master Configuration.
11. Restart the BAM server.
Before configuring the JMS Activation Specification and deploying the CQIntegration.ear to WebSphere
you must return to the application server that you configured for running LiveCycle Workflow Server.
Adobe LiveCycle
Configuring WebSphere 6.0.2.9 for BAM Server
Installing and Configuring LiveCycle for WebSphere
Deploying BAM Server to WebSphere
162
➤ To set up the JMS Activation Specification:
1. In the WebSphere administrative console navigation tree, click Resources > JMS Providers > Default
messaging.
2. Under Scope select Server, and click Apply.
3. Under Activation Specifications, click JMS activation specification.
4. Click New, specify the following values, and then click OK:
Under Administration specify:
Name: Template_Event_AS
JNDI Name: Template_Event_AS
Under Destination specify:
Destination Type: Topic
Destination JNDI name: topic/adobe_TemplateEventTopic.
Bus name: select IDP_JMS_BUS
Under Additional specify:
Maximum bath size: 1
Maximum concurrent endpoints: 10
5. Click OK.
6. Click Save to Master Configuration, and then click Save.
➤ To deploy the CQIntegration.ear file:
1. In the WebSphere Administrative Console navigation tree, select Applications > Install New
Application.
2. Click Browse to navigate to the [LiveCycle root]/components/bam/common directory, and select the
CQIntegration.ear file. You do not need to type a context root value.
3. Click Next. On the first screen, select Generate Default Bindings and click Next.
4. On the Application Security Warnings screen, click Continue.
5. Click Step 2: Map modules to servers:
●
Select both the ejb-jar.xml and web.xml files.
●
Under Clusters and Servers, select the server instance that you created for running
LiveCycle Workflow Server, and then click Apply. Ensure that these modules are now pointing to the
BAM server instance and click Next.
6. Click Step 3: Provide listener bindings for message-driven beans, and under Bindings:
●
Select Activation Specification.
●
In the JNDI name box, type the event name associated with the template event topic specified in
step 4 of To set up the JMS Activation Specification. For example type Template_Event_AS.
7. Click Step 5: Summary, and then click Finish.
Adobe LiveCycle
Installing and Configuring LiveCycle for WebSphere
Configuring WebSphere 6.0.2.9 for BAM Server
Next Step
163
8. Click Save to Master Configuration, and then click Save.
Next Step
You must now configure the BAM properties on LiveCycle Workflow Server and BAM Server. (See “Getting
Started with BAM Server” on page 164.)
16
Getting Started with BAM Server
This chapter describes how to perform the initial configuration of LiveCycle Workflow Server to enable
BAM Server to monitor process activity. You must configure settings on both LiveCycle Workflow Server
and BAM Server:
●
“Configuring LiveCycle Workflow Server for BAM Server” on page 164
●
“Configuring BAM Server” on page 165
Configuring LiveCycle Workflow Server for BAM Server
You can configure LiveCycle Workflow Server to connect to BAM Server using Administrator. You must
specify the server on which BAM Server is running and the user account information with which to access
BAM Server.
➤ To configure LiveCycle Workflow Server for BAM Server:
1. Log into Administrator. (See “Accessing Administrator” on page 66.)
2. Click Services, and then click Adobe LiveCycle Workflow.
3. Click Server Settings, and then click BAM Configuration Settings.
4. Specify values for the following properties:
●
Host: The host name or IP address of the server on which BAM Server is running. The default value is
localhost.
●
Port: The service port of the application server on which BAM Server is running. (For WebSphere
5.1.1.5, type 9091 (see “Creating a virtual host alias” on page 147). For WebSphere 6.0.2.9, you can
find the port value by clicking Servers > Application Servers > [BAM Server] > Ports).
●
User Name: (Optional) The user name of the administrator user account that LiveCycle Workflow
Server uses to access BAM Server. The default user name is system.
Note: If you specify the user name for a different user account, you must ensure that the user has
complete administrative privileges for BAM Server. For information about administering BAM
user accounts, see BAM Workbench Help or the Using LiveCycle Workflow Workbench guide.
●
Password: (Optional) A valid password for the user name specified above. The default password is
manager.
5. Click Save and restart the LiveCycle.ear.
Accessing BAM Workbench and BAM Dashboard
After BAM Server is deployed and running on the application server, you can access BAM Workbench and
Business Activity Monitor (BAM) Dashboard through a web browser. BAM Workbench includes tools for
administering BAM Server and for setting up reports that users view in BAM Dashboard.
164
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring BAM Server
165
A user name and password are required to log into the Business Activity Monitor pages. When you deploy
BAM Server, a default administration account is created with the user name system and password
manager.
Tip: You can create a different user for administration or modify the existing one using BAM Workbench. If
you modify the existing one, you must change the corresponding properties on LiveCycle Workflow
Server. (See “Configuring LiveCycle Workflow Server for BAM Server” on page 164.)
For information on using the tools provided with the administration framework, log into BAM Workbench
and see the Help.
➤ To access BAM Workbench:
1. Start BAM Workbench by typing http://[host name]:[port]/celequest/workbench in the
URL line of a web browser.
2. In the User Name box, type a valid user name, and in the Password box, type the associated password.
You can use the default user name system, and the default password manager.
➤ To access BAM Dashboard:
1. Start BAM Dashboard by typing http://[host name]:[port]/celequest/dashboard in the
URL line of a web browser.
2. In the User Name box, type a valid user name, and in the Password box, type the associated password.
You can use the default user name system, and the default password manager.
Configuring BAM Server
You can configure BAM Server to monitor LiveCycle Workflow processes using BAM Workbench. (See
“Accessing BAM Workbench and BAM Dashboard” on page 164.)
You need to use BAM Workbench to perform the following tasks:
●
Configure the SMTP server settings for sending email messages.
●
Import the metadata definitions used for monitoring LiveCycle Workflow processes.
●
Start the JDBC agent.
●
Configure the LDAP settings for BAM Server.
Configuring the SMTP settings
BAM Server uses an SMTP server to send email messages to Business Activity Monitor users. You must
specify the server on which the SMTP server is running and the user account information with which the
BAM Server can access the SMTP server.
➤ To configure the SMTP settings:
1. Ensure that the LiveCycle Workflow Server and the BAM Server applications are started.
2. Ensure that your BAM metadata database is started.
3. Start BAM Workbench by typing http://[host name]:[port]/celequest/workbench in the
URL line of a web browser.
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
Importing LiveCycle Workflow metadata definitions
166
4. Log in using the user name and password that is configured for Business Activity Monitor
administration. You can use the default user name system, and the default password manager.
5. If this is your first time logging into BAM Workbench, the First Time Setup dialog box appears. If the
dialog box appears, click Open System Settings, and then click the SMTP Configuration tab.
6. Specify values for the following properties:
●
SMTP Host: The network name or IP address of the SMTP server that BAM Server uses to send email
messages.
●
SMTP From Address: The email address that BAM Server uses to receive email messages.
●
SMTP User: The user name for the email account that BAM Server uses.
●
SMTP Password: The password that corresponds with the SMTP user.
7. Select the Checkpoint Configuration tab, and in the Recovery Log Directory box, type the location
of the recovery log directory.
8. Select the Logging tab, and in the Logging Directory box, type the location of the logging directory.
9. Click OK.
Importing LiveCycle Workflow metadata definitions
You must import LiveCycle Workflow metadata definitions to configure the process metrics that
BAM Server monitors. Importing the LiveCycle Workflow metadata file creates the Adobe JDBC agent.
➤ To import LiveCycle Workflow metadata definitions:
1. Ensure that the LiveCycle Workflow Server and the BAM Server applications are running.
2. Ensure that the BAM metadata database is started.
3. Start BAM Workbench by typing http://[host name]:[port]/celequest/workbench in the
URL line of a web browser.
4. Click the Administration Console tab, and then click Import/Export.
5. Select Import Metadata from a JAR file (upload) and type the full path to the location of the
LiveCycle Workflow BAM metadata template that is appropriate for the type of database that you are
using for the LiveCycle database:
●
(SQL Server) adobeimport_SQLServer.jar
●
(Oracle) adobeimport_Oracle.jar
●
(DB2) adobeimport_DB2.jar
These files are installed in the [LiveCycle root]/Workflow/bam/BAMAppTemplate directory.
6. Click OK.
Starting the JDBC agent
You must start the JDBC agent named adobe.
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring LDAP settings for BAM Server
167
➤ To start the JDBC agent:
1. Ensure that the LiveCycle Workflow Server and BAM Server applications are started.
2. Open BAM Workbench in a web browser. (See “Accessing BAM Workbench and BAM Dashboard” on
page 164.)
3. Click the Administration Console tab and, in the left panel, select Agents.
4. In the Agents table, click the icon in the Status column to enable the agent called adobe.
5. When prompted, click Enable All to enable all dependent objects. The status should change to
enabled.
Configuring LDAP settings for BAM Server
In addition to manually creating users and user permissions, Business Activity Monitor lets you to import
user information from supported LDAP providers. You can schedule automatic synchronizations or
perform manual synchronizations with the LDAP server to automatically update the existing users and
roles.
When synchronizing with the LDAP server, the user base DN, login identification and password, full name,
description, and email address properties are cached in the BAM metadata database.
When BAM Server imports users from the LDAP server, LDAP groups are converted to Business Activity
Monitor roles. Users are assigned roles according to the group they belong to in LDAP. For more
information, see “Limitations of BAM Server LDAP connectivity” on page 167.
Note: BAM Server integrates with any LDAP provider that supports LDAP version 3 protocol.
Limitations of BAM Server LDAP connectivity
The following limitations apply to the BAM Server connectivity with the LDAP server:
●
You can configure a connection to only one LDAP server.
●
BAM Server creates roles based on groups that are defined on the LDAP server. When BAM Server
encounters a group for which a role is not yet created, it creates the role and assigns it a set of zero
permissions. You can later modify the permissions as required. (See “Configuring LDAP role mapping”
on page 170.)
●
If BAM Server imports a user and the user does not belong to a group to which a Business Activity
Monitor role corresponds, the user is created but remains unassigned to any roles.
●
You cannot change the role that a user is assigned to if the user is imported from the LDAP server. Role
assignments for imported users can be accomplished by making changes to the LDAP server. However,
you can assign manually-created users to roles that are created based on LDAP groups.
Best practices for BAM Server LDAP connectivity
When setting up the BAM Server connectivity with the LDAP server, it is strongly recommended you
adhere to the following best practices:
●
If the connection to the LDAP server is not secure, you should use SSL.
●
For authentication, Simple Authentication and Security Layer (SASL) is the recommended method and
is well supported by LDAP.
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
●
Configuring LDAP settings for BAM Server
168
For security reasons, the access permissions of the LDAP synchronization user should be limited to
querying the LDAP server. For more information on the synchronization user, see “Configuring
automatic LDAP synchronization” on page 168.
Caution: The password for this user is stored in the BAM Server metadata using reversible symmetric
encryption. Therefore, anyone with access to the metadata can obtain this password.
Configuring automatic LDAP synchronization
You can schedule the automatic synchronization of BAM Server with the LDAP server. Synchronization
ensures that the user accounts and role definitions that BAM Server caches in the BAM metadata database
are up to date with the content of the LDAP server.
During synchronization, BAM Server creates new roles based on any new groups in the LDAP server and
removes existing roles based on any groups that have been removed from the LDAP server since the
previous synchronization.
Note: Roles are removed even if users that were created manually are assigned to the roles. For these
users, if the roles are removed due to synchronization, the user accounts still exist but are no longer
assigned to the roles.
➤ To configure automatic LDAP synchronization:
1. Start BAM Workbench by typing http://[host name]:[port]/celequest/workbench in the
URL line of a web browser.
2. Click the Administration Console tab, and then click System Settings.
3. Click the LDAP Synchronization tab.
4. Select the LDAP Enabled option, if it is not already selected.
5. Specify values for the following properties:
●
Initial Context Factory: The JNDI name through which BAM Server connects to the LDAP server.
The default value is com.sun.jndi.ldap.LdapCtxFactory. You probably do not need to
change this value.
●
LDAP Server: The DNS name or IP address of the LDAP server.
●
LDAP Port: The port on which the LDAP server is running. The default port is typically 389.
However, if you select the SSL option, the default port is typically 636. You must confirm with your
LDAP administrator which port to specify.
●
LDAP SSL: Select this option if the LDAP server is configured to use SSL. Selecting this option may
affect the LDAP Port setting.
●
LDAP Authentication: The authentication method used by the LDAP server. Select one of the
following options:
●
Simple
●
SASL (Simple Authentication and Security Layer). Select this option for Sun ONE.
●
Compare Encrypted Password
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
●
●
Configuring LDAP settings for BAM Server
169
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 ActiveDirectory, 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 (","). For example:
,ou=Users,dc=domain,dc=name
●
For ActiveDirectory, which requires a simple login with an email address, set this to an at symbol
(@) followed by the domain name that is set for ActiveDirectory.
●
LDAP Synchronization User: The user that binds to the server and reads the lists of users and roles.
For security purposes, you must specify a user account that can only read the LDAP directory.
●
LDAP Synchronization Password: The password associated with the user specified for the LDAP
Synchronization User option.
6. Click Test Connection. The connection and the user mapping and role mapping configuration are
tested. If the connection settings are correct, a message will indicate that the connection was
successful. If you have not yet configured LDAP User Mapping and LDAP Role Mapping, the message
returns an error.
7. To set the LDAP Synchronization Schedule, use the Add Schedule, Edit Schedule, and Remove
Schedule buttons to create the desired schedule.
Note: You should set synchronization for a time when the fewest number of users are likely to be
logged in.
8. Click OK.
Configuring LDAP user mapping
You can configure the user mapping parameters that determine which users are imported and
synchronized from the LDAP server. The parameters you specify depend on the LDAP server provider that
you are using.
➤ To configure the LDAP user mapping parameters:
1. Start BAM Workbench by typing http://[host name]:[port]/celequest/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.
4. Specify values for the following parameters:
●
LDAP User Base DN: The root of the tree that will be searched for users. For example:
●
(Sun ONE) OU=people,DC=your domain,DC=com
●
(Active Directory) CN=Users,DC=yourdomain,DC=com
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
Configuring LDAP settings for BAM Server
170
●
LDAP User Search Filter: The format that is appropriate for the type of LDAP server you are using.
For example, your LDAP server could have a special group for Business Activity Monitor users. This
filter could then ensure that only users with this group membership are imported.
●
LDAP User LoginID: The login ID of the indicated provider. This value will become the user’s login
ID in Business Activity Monitor.
●
LDAP User Full Name: Enter cn if you are using either Sun ONE or Active Directory.
●
LDAP User Description: Enter description if you are using either Sun ONE or Active Directory.
●
LDAP User PrimaryEmail: Enter userPrincipalName. This refers to the user’s email address in
the LDAP directory.
●
LDAP User EncryptedPassword: Enter the password associated with the specified user if you are
using either Sun ONE or Tivolie. Leave blank for Active Directory.
5. Click the LDAP Synchronization tab and click Test Connection to see if the users are imported
successfully.
6. Click OK.
Configuring LDAP role mapping
You can configure the role mapping parameters that determine which groups or roles are imported or
synchronized, or both. The parameters you specify depend on the LDAP server provider that you are using.
➤ To configure the LDAP role mapping parameters:
1. Start BAM Workbench by typing http://[host name]:[port]/celequest/workbench in the
URL line of a web browser.
2. Click the Administration Console tab, and then click System Settings.
3. Click the LDAP Role Mapping tab.
4. Specify values for the following parameters:
●
●
LDAP Role Base DN: The format that is appropriate for the type of LDAP server you are using:
●
(Sun ONE) OU=Groups,DC=your domain,DC=com
●
(Active Directory) CN=Users,DC=yourdomain,DC=com
LDAP Role Search Filter: The format that is appropriate for the type of LDAP server you are using:
●
(Sun ONE) (&(objectclass=groupOfUniqueNames))
●
(Active Directory) (&(objectclass=group))
●
LDAP Role LoginID: Enter cn if you are using either Sun ONE or Active Directory.
●
LDAP Role Full Name: Enter displayname if you are using either Sun ONE or Active Directory.
●
LDAP Role Description: Enter description if you are using either Sun ONE or Active Directory.
●
LDAP Role Member: The name of the multivalued property that contains role members:
●
(Sun ONE) uniqueMember
●
(Active Directory) member
Adobe LiveCycle
Getting Started with BAM Server
Installing and Configuring LiveCycle for WebSphere
●
Next steps
171
LDAP Role Member is: Use one of the following options:
●
Distinguished Name, if the role member properties identify users by distinguished names,
such as cn=jadmin,ou=people,dc=your domain,dc=com.
●
Login identification, if the role member properties identify users by the value of the
property used as the Business Activity Monitor login ID.
5. Click the LDAP Synchronization tab and click Test Connection to see if the users are imported
successfully.
6. Click OK.
Manually synchronizing with the LDAP server
You can manually synchronize BAM Server with the LDAP server at any time. Synchronization requests are
queued to prevent concurrent synchronizations.
➤ To manually synchronize with the LDAP server:
1. Start BAM Workbench by typing http://[host name]:[port]/celequest/workbench in the
URL line of a web browser.
2. Click the Administration Console tab, and then click System Settings.
3. Click the LDAP Synchronization tab.
4. Click Synchronize Now. The time required to synchronize depends on your environment. A message
appears when the synchronization is complete.
5. Click OK.
Next steps
You can now install LiveCycle Workflow Designer. (See “Installing LiveCycle Workflow Designer” on
page 172.)
17
Installing LiveCycle Workflow Designer
This chapter describes how to install LiveCycle Workflow Designer.
Installing LiveCycle Workflow Designer
You must run an installation program to install LiveCycle Workflow Designer and to configure a connection
to LiveCycle Workflow Server. When you run the installation program, you need to provide the name of the
server where LiveCycle Workflow Server is deployed.
Before you install LiveCycle Workflow Designer, you must have J2SDK version 1.4.2_05, or a later release of
1.4.2 installed (version 1.4.2_10 is not supported).
When LiveCycle Workflow Server is deployed to WebSphere, the following conditions apply:
●
You must have the WebSphere Pluggable Client installed from the WebSphere installation media
before installing LiveCycle Workflow Designer. When installing the WebSphere Pluggable Client, you
must perform a custom installation and select the Pluggable Application Client. For more information,
see the WebSphere documentation.
●
You must use WebSphere Pluggable Client version 5.1 with WebSphere 5.1.1, and WebSphere
Pluggable Client version 6.0 with WebSphere 6.
●
When installing WebSphere Client on the LiveCycle Workflow Designer computer, you can only
connect to instances of LiveCycle Workflow Server that are deployed to WebSphere. If you reinstall and
configure LiveCycle Workflow Designer to connect to instances of the server that are deployed to other
types of application servers (such as JBoss or WebLogic), attempts to connect to the servers will fail.
●
To use the same client computer to connect to LiveCycle Workflow Server instances that are deployed
to a different type of application server, you must uninstall WebSphere Client and LiveCycle Workflow
Designer, and then reinstall LiveCycle Workflow Designer.
●
If the WebSphere Application Server where LiveCycle Workflow Server is deployed uses SSL/IIOP, you
must disable SSL/IIOP while using LiveCycle Workflow Designer. Otherwise, LiveCycle Workflow
Designer cannot connect to the application server.
LiveCycle Workflow Designer is installed in the following location by default:
●
(Windows) C:\Adobe\LiveCycle\WorkflowDesigner
●
(Linux) /opt/adobe/livecycle/workflow_designer
➤ To install LiveCycle Workflow Designer:
1. At the root level of the installation media, run the installation program by entering the following
command:
●
(Windows) adobe_lc_workflow_721_des.exe
●
(Linux) adobe_lc_workflow_721_des.bin
2. On the Welcome screen, click Next.
3. Read the license agreement, select I accept the terms of the license agreement, and then click Next.
172
Adobe LiveCycle
Installing LiveCycle Workflow Designer
Installing and Configuring LiveCycle for WebSphere
Connecting to application servers using non-default ports
173
4. Accept the default installation directory or click Browse and navigate to the directory where you want
to install the product, and then click Next.
Note: If you type in the name of a directory that does not exist, it will be created for you.
5. Select WebSphere as the type of application server that hosts LiveCycle Workflow Server and click
Next.
6. Navigate to the [ws_client_install_location]/WebSphere/AppClient directory, which is the WebSphere
Pluggable Client directory.
7. In the text box, type the name of the computer running LiveCycle Workflow Server, and then click
Next.
8. Review the installation details, and then click Back to change any settings or click Install to continue.
9. Click Finish.
10. If you are not installing LiveCycle Workflow Designer on the same computer as where LiveCycle
Workflow Server is deployed, ensure that the system clock is set to the correct time.
If the system clock is not within two hours of the correct time for the current time zone, LiveCycle
Workflow Designer will not be able to connect to the application server. The system clock of the
application server must also be set to the correct time.
Connecting to application servers using non-default ports
The default configuration of LiveCycle Workflow Designer uses default JNDI and HTTP ports to connect to
the application server. If the application server uses non-default port numbers, you must manually modify
the LiveCycle Workflow Designer configuration file.
➤ To change the port used for JNDI and HTTP connections:
1. Open the qlc-config.xml file in a text editor from the following location:
●
(Windows) [LiveCycle root]/WorkflowDesigner/qlc/
●
(Linux) [LiveCycle root]/workflow_designer/qlc/
2. Locate the property element with the name attribute of java.naming.provider.url, and
change the URL in the value attribute so that it includes the port that you use for JNDI connections.
For example, the following property element configures the port to use for JNDI connections to
2809: <property name="java.naming.provider.url"
value="iiop://localhost:2809/"/>
3. Locate the application-services element and change the value of the port attribute to the port
that your application server uses for HTTP connections.
For example, the following application-services element configures the port to use for HTTP
connections to 9080: <application-services host="localhost" port="9080"
context="adobe-services"/>
4. Save and close the file.
Adobe LiveCycle
Installing LiveCycle Workflow Designer
Installing and Configuring LiveCycle for WebSphere
Uninstalling LiveCycle Workflow Designer
174
Uninstalling LiveCycle Workflow Designer
LiveCycle Workflow Designer includes an uninstall program that is created during installation. The
uninstall program removes the product files.
➤ To remove LiveCycle Workflow Designer:
1. Start the uninstall program:
●
(Windows) Navigate to [LiveCycle root]/WorkflowDesigner/_uninst/ and double-click uninstall.exe.
●
(Linux) Navigate to [LiveCycle root]/workflow_designer/_uninst/ and run uninstall.bin.
2. If prompted, select a language for the uninstall program and click OK.
3. On the Welcome screen, click Next.
4. Review the summary information and click Uninstall.
5. If a Remove Existing File dialog box appears, select Yes To All.
6. Click Finish.
Next steps
You can now deploy QPACs. (See the Creating Workflows guide or LiveCycle Workflow Designer Help.)
If you have installed Watched Folder and LiveCycle Assembler, you can create workflows that involve
Watched Folder using the LiveCycle Assembler QPACs. (See “Invoking LiveCycle Assembler Using
LiveCycle Workflow and Watched Folder” on page 180.)
A
Supported Platform and Software Combinations
This appendix provides the supported platforms and software combinations for LiveCycle products. For a
summary of the platforms combinations, see “Before You Install” on page 13.
Note: LiveCycle PDF Generator Elements and LiveCycle PDF Generator Professional run only on the
Windows Server 2003 Enterprise Edition platform.
Platform
Application server
JDK
Database
Windows Server
2003, Standard
Edition
JBoss® 3.2.5
J2SDK version 1.4.2_04
MS SQL Server 2000 SP3
JBoss 3.2.5
J2SDK version 1.4.2_04
MySQL 4.1
Windows Server
2003, Enterprise
Edition
JBoss 3.2.5
J2SDK version 1.4.2_04
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 9i
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
BEA WebLogic Server® 8.1
SP5
J2SDK version 1.4.2_08
Oracle 9i
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
MS SQL Server 2000 SP3
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
IBM DB2® 8.2
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
MS SQL Server 2000 SP3
175
Adobe LiveCycle
Supported Platform and Software Combinations
Installing and Configuring LiveCycle for WebSphere
176
Platform
Application server
JDK
Database
Red Hat Linux
Advanced Server
2.1 Update 3
JBoss 3.2.5
J2SDK version 1.4.2_04
MS SQL Server 2000 SP3
JBoss 3.2.5
J2SDK version 1.4.2_04
MySQL 4.1
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 9i
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 10g
JBoss 3.2.5
J2SDK version 1.4.2_04
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 9i
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
JBoss 3.2.5
J2SDK version 1.4.2_04
MySQL 4.1
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 9i
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 10g
JBoss 3.2.5
J2SDK version 1.4.2_04
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 9i
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
MS SQL Server 2000 SP3
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 10g
Red Hat Linux
Advanced Server
3.0
Adobe LiveCycle
Supported Platform and Software Combinations
Installing and Configuring LiveCycle for WebSphere
177
Platform
Application server
JDK
Database
IBM AIX 5.2
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 10g
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 9i
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 10g
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
IBM AIX 5.3
Sun Solaris 8
Sun Solaris 9
Adobe LiveCycle
Supported Platform and Software Combinations
Installing and Configuring LiveCycle for WebSphere
Platform
Application server
178
JDK
Database
SUSE Linux ES 9.0 JBoss 3.2.5
J2SDK version 1.4.2_04
MS SQL Server 2000 SP3
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 9i
JBoss 3.2.5
J2SDK version 1.4.2_04
Oracle 10g
JBoss 3.2.5
J2SDK version 1.4.2_04
MySQL 4.1
BEA WebLogic Server 8.1
SP5
J2SDK version 1.4.2_08
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 5.1.1.5
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
IBM DB2 8.2
(Version 8.1 Fix Pack 7)
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 9i
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
Oracle 10g
IBM WebSphere 6.0.2.9
IBM JDK installed with
WebSphere
MS SQL Server 2000 SP3
B
Fonts Installed with the Font Manager Module
Some modules require access to fonts that are installed with the Font Manager Module. The Font Manager
Module contains a number of bundled fonts that you can use in your custom applications.
The Font Manager Module is not used when converting native documents into PDF documents or when
converting PDF documents into some other format.
You can add fonts to the Font Manager Module, which is subsequently packaged in the LiveCycle.ear file.
For information about adding your own fonts, see “Configuring LiveCycle Products for Deployment” on
page 76.
The following fonts are installed with the Font Manager Module:
●
Adobe Serif MM
●
Kozuka Mincho Std Bold
●
Adobe Sans MM
●
Kozuka Mincho Std Heavy
●
Adobe Ming Std Light
●
Kozuka Mincho Pro-VI Regular
●
Adobe Song Std Light
●
Letter Gothic Std Medium
●
Adobe Myungjo Std Medium
●
Letter Gothic Std Slanted
●
Adobe Pi Std
●
Letter Gothic Std Bold
●
Bell Gothic Std Light
●
Letter Gothic Std Bold Slanted
●
Bell Gothic Std Bold
●
Minion® Pro Italic
●
Bell Gothic Std Black
●
Minion Pro Semibold
●
Courier Std
●
Minion Pro Semibold Italic
●
Courier Std Bold
●
Minion Pro Bold
●
Courier Std Bold Oblique
●
Minion Pro Bold Italic
●
Courier Std Oblique
●
Minion Pro Regular
●
EuroSign (TTF)
●
Myriad® Pro Light
●
Kozuka Gothic® Std Extra Light
●
Myriad Pro Light Italic
●
Kozuka Gothic Std Light
●
Myriad Pro Regular
●
Kozuka Gothic Std Regular
●
Myriad Pro Italic
●
Kozuka Gothic Std Medium
●
Myriad Pro Bold
●
Kozuka Gothic Std Bold
●
Myriad Pro Semibold
●
Kozuka Gothic Std Heavy
●
Myriad Pro Semibold Italic
●
Kozuka Gothic Pro Medium
●
Myriad Pro Bold Italic
●
Kozuka Mincho® Std Extra Light
●
Myriad Pro Black
●
Kozuka Mincho Std Light
●
Myriad Pro Black Italic
●
Kozuka Mincho Std Regular
●
Symbol
●
Kozuka Mincho Std Medium
179
C
Invoking LiveCycle Assembler Using
LiveCycle Workflow and Watched Folder
This appendix describes how to invoke LiveCycle Assembler through LiveCycle Workflow, using the
LiveCycle Assembler QPACs and Watched Folder.
This appendix assumes that you have installed, configured, and deployed LiveCycle Assembler,
LiveCycle Workflow, and Watched Folder.
Note: Watched folders can be implemented for use with LiveCycle PDF Generator, but need to be
configured separately. The contents of this chapter refer only to the Watched Folder service that
integrates LiveCycle Workflow and LiveCycle Assembler. For information on setting up watched
folders for LiveCycle PDF Generator, see LiveCycle PDF Generator Administration Help, available from
the LiveCycle PDF Generator web interface.
Summary of tasks
Using either Watched Folder or a client application you developed, you can direct LiveCycle Workflow to
initiate a workflow that activates a LiveCycle Assembler QPAC.
This section outlines the tasks required to set up a workflow that completes a LiveCycle Assembler process
that is invoked by Watched Folder. The detailed steps required to complete the tasks are located in the
section or document indicated. You must perform the tasks in the order that they are listed in the table.
Note: Do not run Configuration Manager until you have completed installing the files for each of the
products.
Step
Task
See
1
Deploy LiveCycle Assembler QPACs to
LiveCycle Workflow Designer.
Using LiveCycle Assembler QPACs (available
on the LiveCycle Assembler installation DVD
or on the LiveCycle Workflow SDK website)
2
Create and deploy a workflow that includes a
LiveCycle Assembler QPAC.
“Deploying QPACs and creating a workflow
process” on page 181
LiveCycle Workflow Creating Workflows
LiveCycle Workflow Designer Help
3
Create a watched folder on the file system.
“Creating and configuring a watched folder”
on page 184
4
Log into Administrator and create and configure
a watched folder.
“Creating and configuring a watched folder”
on page 184
Watched Folder Administration Help
5
Create a JobConfig.xml file.
“Creating a JobConfig.xml file” on page 185
Watched Folder Administration Help
180
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Deploying QPACs and creating a workflow process
181
Step
Task
See
6
Prepare the test or production collateral, which
includes input PDF files and a DDX file.
“Preparing PDF and DDX files” on page 187
Developing Applications for LiveCycle
Assembler
Document Description XML Reference
7
Submit the LiveCycle Assembler job for
processing.
“Submitting the LiveCycle Assembler job for
processing” on page 188
Developing Custom Applications for
LiveCycle Workflow
Deploying QPACs and creating a workflow process
There are two QPACs used to create workflows for LiveCycle Assembler: the Assembler QPAC and the
CreateDocumentList QPAC. The Assembler QPAC is used for all LiveCycle Assembler workflows, whether
you are using Watched Folder or another method of initiating the process (for example, client applications
or web services).
This section describes how to create a workflow process that uses the Assembler QPAC, including how to
create the required variables and action properties in LiveCycle Workflow Designer. For information on
creating a workflow process that uses the CreateDocumentList QPAC, see the Using LiveCycle Assembler
QPACs guide.
The steps for creating a workflow process that includes an Assembler QPAC are similar to those for creating
any workflow process using LiveCycle Workflow Designer. The procedure here provides details specific to
the Assembler QPAC. For more information on creating workflows, setting up variables, and setting action
properties in a QPAC, see the Creating Workflows and Using LiveCycle Assembler QPACs guides.
Using dynamic or static DDX files
When you submit jobs to Watched Folder for processing by LiveCycle Workflow and LiveCycle Assembler,
you can use a dynamic or a static DDX file. When you create or use an application to submit jobs to
LiveCycle Assembler that uses only the QPAC workflow (without Watched Folder), you must use a static
DDX file.
A workflow that uses a dynamic DDX file processes the DDX file that is included in the input folder in a
watched folder. To use a dynamic DDX file in your workflow process, you must create an <inputddx>
variable and specify it in the action properties of the QPAC.
A workflow that uses a static DDX file processes a particular DDX file that is loaded into the QPAC and used
every time that the process is called by the JobConfig.xml file. To use a static DDX file in your workflow
process, you must browse to the DDX file and load it into the QPAC when you set the action properties for
the workflow. You can use a static DDX if you are using a watched folder, or if you are running the process
using only the QPACs.
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Configuring an Assembler QPAC in a workflow process
182
Configuring an Assembler QPAC in a workflow process
When you create a new workflow process in LiveCycle Workflow Designer, you must create variables that
will be used by the workflow process. When you add the Assembler QPAC to the workflow, you must set
the action properties for the QPAC. The action properties use the variables that you created.
The selections you make on the Action Properties dialog box depend on whether you are using a dynamic
or static DDX file.
Note: The variable names used in this chapter, such as <inputddx> and <inputdocmap>, are
user-defined in LiveCycle Workflow Designer; you can use any name when you create the variable.
Variables for the Assembler QPAC
Variable
Property values
<inputdocmap>
Type: map of document
in: selected
out: not selected
required: not selected
<inputddx>
Type: document
in: selected
out: not selected
required: not selected
(required for dynamic
DDX file only)
<outputmap>
Type: map and document
in: not selected
out: selected
required: not selected
Type: Document
(not required when
in: not selected
Logging Level is set to Off ) out: selected
required: not selected
<joblog>
Action properties for the Assembler QPAC
Type of workflow
Select on Input tab
Using Watched Folder with a Use a Document Variable to load the
dynamic DDX file
DDX file: Click the ellipsis button and
select the <inputddx> variable.
Input Document Map Variable:
Select the <inputdocmap> variable.
Select on Output tab
Output Document Map: Click
the ellipsis button and select the
<outputmap> variable.
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Type of workflow
Configuring an Assembler QPAC in a workflow process
Select on Input tab
Using Watched Folder with a Use the Browse button to locate the
static DDX file
DDX file: Browse to the DDX file that
you want to use.
183
Select on Output tab
Output Document Map: Click
the ellipsis button and select the
<outputmap> variable.
Input Document Map Variable:
Select the <inputdocmap> variable.
Using QPAC only (with a
static DDX file)
Input Document Map: Do not select
Use the Browse button to locate the
DDX file: Browse to the DDX file that
you want to use.
Output Document Map: Click
the ellipsis button and select the
<outputmap> variable.
Note: For information about selecting options on the Configuration tab, see the next section, Error
logging and fail modes in the Assembler QPAC workflows.
Error logging and fail modes in the Assembler QPAC workflows
When you set up a workflow using the Assembler QPAC, you can select the error logging level and the fail
mode that LiveCycle Workflow uses when exceptions occur.
You can set the error logging level to Off (no logging), Normal (brief messages), or Debug (detailed
descriptions of errors). You can associate a process variable (for example, <joblog>) of type Document to
the Output Log Document field in order to store the log messages.
You can set the fail mode to Stall Process or Terminate Process to direct the Assembler QPAC to stall or
terminate a process when an exception occurs in LiveCycle Assembler.
When a job fails with Stall Process selected, the workflow process stalls, but is not terminated. If logging is
set to Normal or Debug, information about the exception appears on the LiveCycle Workflow Stalled
Action page in Administrator. Component administrators should search for the process and terminate it,
and then return to Administrator and delete the stalled action if desired. The logged messages are
displayed on the stalled action page, but not on the process page.
When a job fails with Terminate Process selected, the workflow process terminates when an exception is
thrown. If logging is set to Normal or Debug, information about the exception is written to the log file for
the component for which the exception was thrown. For Watched Folder, the log file is the activity.log file
that is placed in the /failure subdirectory of the configured watched folder.
If you are configuring an Assembler QPAC for use with Watched Folder, you should set the fail mode to
Terminate Process. Watched Folder users may not have access to Administrator, so if processes stall but are
not terminated, users do not receive messages about the exception until the process is terminated. Setting
the fail mode to Terminate Process ensures that error messages are logged to the activity.log file, which is
available in the [watchedfolder]/failure directory (when the logging level is set to Normal or Debug).
For information on setting error logging and fail modes, see Using LiveCycle Assembler QPACs.
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Creating and configuring a watched folder
184
➤ To create a workflow that includes an Assembler QPAC:
1. Deploy the Assembler QPAC to LiveCycle Workflow Designer. (See Using LiveCycle Assembler QPACs.)
2. In LiveCycle Workflow Designer, select File > New > Process Category.
3. Select the new process category and select File > New > Process Type.
4. Right-click the new process type and select New Workflow.
5. Name the workflow and use the default values for the remaining options (synchronous is selected
and the other options are unchecked).
6. Create the variables for the workflow, as described in the “Variables for the Assembler QPAC” on
page 182 table, by clicking the green plus (+) button on the Variables palette. For more information on
creating variables, see LiveCycle Workflow Designer Help.
7. Create a new component category. (See Creating Workflows.)
8. Add the Assembler QPAC (deploy the component) to the new component category, and set the action
properties for the workflow, as described in the “Action properties for the Assembler QPAC” on
page 182 table.
9. Save and deploy the workflow process.
Creating and configuring a watched folder
You must create a directory on your file system that you can configure as a watched folder. After you have
configured the watched folder using the Watched Folder configuration interface, the watched folder
contains the following subdirectories:
/[watchedfolder]
/input
/stage
/failure
/result
/preserve
For information on the subdirectories, see Watched Folder Administration Help.
To submit files for processing, you place them in the /[watched folder]/input directory.
When multiple files need to be included in the LiveCycle Assembler process, do not transfer the individual
files to the input directory; instead, create a separate collection directory, place all of the required files in it
(that is, the input PDF files and, if required, the DDX file), and then place the collection directory in the
input directory of the watched folder.
➤ To create and configure a watched folder:
1. Create a directory to be a watched folder on your file system on your server.
2. Log into Administrator.
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Creating a JobConfig.xml file
185
3. Click Services, click Watched Folder, and then click Watched Folder Management and Status.
4. Click New Watched Folder.
5. In the Watched Folder Name box, type a name for the watched folder. (This does not have to match
the name of the directory you created on the file system in step 1, but it is recommended for tracking
purposes.)
6. In the Watched Folder Path box, type the full path to the directory you created on the file system.
7. In the Include File Pattern(s) box, type the name of the directory you created to contain the input PDF
files (that you will place in the input directory of the watched folder). You can specify more than one file
or name, if you intend to place multiple files and folders in the watched folder.
8. Set the other options according to your requirements. For information on the options available, see
Watched Folder Administration Help.
9. Click OK.
Tip: If you are transferring a large number of source files to the watched folder, it may take several minutes
or longer. It is possible that Watched Folder might scan the watched folder, recognize a new
collection directory, and initiate a workflow process before all of the files in the directory have been
copied over. To avoid this, you must name the collection directory something other than the name
that Watched Folder is scanning for while you copy the directory to the input directory. When all of
the input files have been copied over, you must rename the collection directory to the name specified
in the Watched Folder configuration (the Include File Pattern(s) value).
Creating a JobConfig.xml file
The JobConfig.xml file can be placed at the root of the input directory or inside the collection directory
together with the other collateral files.
If you plan to place multiple jobs (collection directories) in the watched folder for different workflows that
use dynamic DDX files, the JobConfig.xml file must be placed in the individual collection directories that
are submitted to the input directory in the watched folder.
If you plan to submit multiple jobs for the same workflow that uses a static DDX file, you can place the
JobConfig.xml at the root of the input directory. Subsequent incoming jobs use this same JobConfig.xml
file.
To create a JobConfig.xml file, create an XML file similar to the following examples.
Example C.1
A JobConfig.xml file for a dynamic DDX file
<?xml version="1.0" encoding="UTF-8"?>
<process-config xmlns="http://adobe.com/watchedfolder"
xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance"
xsi:schemaLocation="http://adobe.com/watchedfolder
C:\WatchedFolder\schemas\JobConfiguration.xsd">
<process-type>myworkflow</process-type>
<process-variables>
<process-variable>
<filter-pattern>*.pdf</filter-pattern>
<process-variable-type>map</process-variable-type>
<process-variable-name>inputdocmap</process-variable-name>
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Creating a JobConfig.xml file
186
<process-variable-datatype>document</process-variable-datatype>
<process-input>true</process-input>
</process-variable>
<process-variable>
<filter-pattern>*.ddx</filter-pattern>
<process-variable-type>single</process-variable-type>
<process-variable-name>inputddx</process-variable-name>
<process-variable-datatype>document</process-variable-datatype>
<process-input>true</process-input>
</process-variable>
</process-variables>
</process-config>
Example C.2
A JobConfig.xml file for a static DDX file
Use the same JobConfig.xml described previously, but omit the <inputddx> process variable.
<?xml version="1.0" encoding="UTF-8"?>
<process-config xmlns="http://adobe.com/watchedfolder"
xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance"
xsi:schemaLocation="http://adobe.com/watchedfolder
C:\WatchedFolder\schemas\JobConfiguration.xsd">
<process-type>myworkflow</process-type>
<process-variables>
<process-variable>
<filter-pattern>*.pdf</filter-pattern>
<process-variable-type>map</process-variable-type>
<process-variable-name>inputdocmap</process-variable-name>
<process-variable-datatype>document</process-variable-datatype>
<process-input>true</process-input>
</process-variable>
</process-variables>
</process-config>
The content of the JobConfig.xml file maps to the variables and actions defined in the workflow process
described in “Configuring an Assembler QPAC in a workflow process” on page 182.
Node
Description
process-config
The root of the job configuration file.
process-type
The name of the workflow process type. This value must match the
value specified in the workflow process in
LiveCycle Workflow Designer.
process-variables
Contains multiple process-variable nodes.
process-variable
Each process-variable node maps to a variable included in the
workflow process. Its subelements specify property values for each
process variable.
filter-pattern
The pattern used to filter all of the files from the input set that will
be set for the process variable. This pattern matches the type of
files to be processed in relation to the variable.
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Preparing PDF and DDX files
Node
Description
process-variable-type
The type of input variable: single, list, or map.
187
In the example above, list is used for the <inputdocmap>
variable, because the variable specified a series of documents (all
of the files that will be placed in the watched folder). For the
<inputddx> variable, single is specified, because only one file
will be included.
process-variable-name
The name of the workflow variable as defined in the workflow. In
the example above, the variable names match those created in
“Configuring an Assembler QPAC in a workflow process” on
page 182: inputdocmap and inputddx
process-variable-datatype
The type of workflow variable. Two types of variables are
supported: document and xml. This matches the
containedtype attribute of the variable (not the
collectiontype attribute).
process-input
Watched Folder does not currently use this setting. Leave the value
set to true.
For more information on creating the JobConfig.xml file, see Watched Folder Administration Help.
Preparing PDF and DDX files
The PDF files included in the input directory or defined by the Assembler QPAC must correspond to the file
pattern value defined for the source element in the DDX file.
When using Watched Folder with LiveCycle Assembler, you must specify the Input Document Map
variable (as described in “Configuring an Assembler QPAC in a workflow process” on page 182). You must
use the sourceMatch attribute for the source element to define the file pattern. For information on
setting the regular expression pattern for the sourceMatch attribute, see the Document Description XML
Reference.
For example, in the DDX file, the PDF source can be specified in the following ways:
●
Pattern matching for specific file names:
<PDF source="mysource" sourceMatch="appendix[\d]+[.]pdf" select="1-last"/>
●
Pattern matching with wildcard value:
<PDF source="mysource" sourceMatch=".+[.]pdf" select="1-last"/>
In the examples above, pattern-matching matches any input PDF files that begin with the characters
appendix followed by a digit, and then followed with the file name extension .pdf. The wildcard value
matches at least one input PDF file with any characters that include digits and end with .pdf.
For more information on setting the source element in the DDX file, see “Specifying multiple input
streams” in the Developing Applications for LiveCycle Assembler guide and the Document Description XML
Reference.
Adobe LiveCycle
Invoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder
Installing and Configuring LiveCycle for WebSphere
Submitting the LiveCycle Assembler job for processing
188
Submitting the LiveCycle Assembler job for processing
You can submit a LiveCycle Assembler job to Watched Folder programmatically using a batch file that
transfers the package containing the required files to the configured watched folder. (Instructions for
creating a batch file or script to complete this action is beyond the scope of this guide.) You can also
submit a job manually by dragging or copying the package of files to Watched Folder.
If you have created a LiveCycle Assembler workflow in LiveCycle Workflow Designer that does not use
Watched Folder, you can submit the job for processing using a client application that you create using the
LiveCycle Workflow Java API. For information on developing custom client applications for
LiveCycle Workflow, see the Developing Custom Applications for LiveCycle Workflow guide, available with
the LiveCycle Workflow SDK.
You can also submit jobs for processing using a variety of other mechanisms available with
LiveCycle Workflow, such as web services, email, and messaging queues, as well by using online forms. For
more information, see the Developing Custom Applications for LiveCycle Workflow and Developing Custom
QPACs guides.
Note: When NFS sharing is set up for Watched Folder, temporary files and directories related to Watched
Folder jobs are placed in the Global storage directory, but are not automatically deleted when the
job processing is complete. To prevent performance issues, you should regularly remove files with
name Session[NNNN], where NNNN is the workflow process ID from the Global storage directory.
The default location of the Global storage directory is {TempDir]/AdobeDocumentStorage/global. If
[TempDir] is not specified by the user in Configuration Manager, the default location is
java.io.tmpdir.
D
Developing Forms for LiveCycle
This appendix provides information that is useful for form developers, including how to use WebDAV with
LiveCycle Form Manager and which items LiveCycle products require for different types of forms.
Publishing files from client software
Form developers and form owners can use WebDAV-enabled client software to publish and access their
files in the LiveCycle products repository used by LiveCycle Form Manager.
To use WebDAV, your computer must be running file management software (such as Microsoft Windows
Explorer) that can connect to WebDAV servers.
To create a connection to a WebDAV directory, you must specify the URL of the directory. The following
URL is the default URL of the LiveCycle Form Manager repository:
http://[host name]:[port]/appstore/Forms
where[host name] is the name of the computer that is running LiveCycle products and [port] is the port
being used for LiveCycle products.
For example, the form developers in your company use LiveCycle Designer to create forms. The form
developers want to use the Publish menu command in LiveCycle Designer to copy forms and their
supporting files to the LiveCycle products repository. However, they first use Windows Explorer to add a
network place, which creates a connection to the URL of the LiveCycle products repository. The
connection appears as a folder in My Network Places. After adding the network place, the form developers
can use the folder to publish files to the repository.
Designing forms for LiveCycle products
To use forms with LiveCycle products, there may be requirements for the design of the form, the
configuration of LiveCycle products, or both. The following types of forms have special requirements for
use with LiveCycle products:
●
Dynamic forms
●
PDF/A-compliant forms
●
Forms that include subform objects
●
PDF forms created with Acrobat
For information on designing forms for use with LiveCycle Workflow, see the Creating Workflows guide,
which is installed with LiveCycle Workflow.
189
Adobe LiveCycle
Developing Forms for LiveCycle
Installing and Configuring LiveCycle for WebSphere
Using dynamic forms with LiveCycle products
190
Using dynamic forms with LiveCycle products
Dynamic forms can expand or shrink to accommodate the amount of incoming data. Dynamic forms
typically include buttons that request form data from LiveCycle Forms. LiveCycle Forms renders the form
with the data and returns it to the client. The client’s browser is refreshed with the form, which has been
expanded or contracted, depending on the amount of new data.
For example, some forms enable users to query a database by specifying search criteria. The returned data
appears on the same form (a subform) in a table. The returned data determines the number of rows in the
table. To submit the query, the user clicks a button, which sends the request to LiveCycle Forms.
LiveCycle products support the use of the following types of buttons for dynamic forms:
●
One that updates the data on a dynamic form
●
One that returns a PDF document to a client, who can then can save a local copy of the document or
print the document
LiveCycle products use specific button names to recognize these buttons. Dynamic forms must use these
button names. You can use the default names, or you can go to the Administrator pages and configure
LiveCycle products to use different names.
Property
Default
Description and options
Re-render
Button name
RENDERAGAIN
The button name that indicates to LiveCycle products that this
button sends a request to LiveCycle Forms to render the current
form again with updated data.
Print
Button Name
PRINTFORM
The button name that indicates to LiveCycle products that this
button creates a PDF document from the current form and returns
it to the end user.
Embedding fonts in PDF/A-compliant forms
When creating a form design that is intended for the creation of a PDF/A Level 1B-compliant form when
rendered by LiveCycle Forms, all of the fonts used must be embedded in the form design. If the fonts are
not embedded, the rendered form is not PDF/A Level 1B-compliant, although it is a valid PDF form.
Only fonts licensed for a minimum of View and Print usage can be embedded in the form design. The fonts
included in the Font Manager Module meet this criteria.
E
Uninstalling LiveCycle Products
This chapter describe how to uninstall the LiveCycle product files.
Removing the product files
The uninstall program located in the [product root] directory does not remove any files that you deployed
to your application server or modules that are shared with other LiveCycle products.
Caution: By running the uninstall program, all of the contents within the product installation directory are
subject to removal without further warning. Before proceeding, back up any data you do not
want to lose.
➤ To remove the files from your computer:
1. Navigate to the [product root]/_uninst/ directory and start the unstall program:
●
(Windows) Double-click the .exe file. Alternatively, you can use the Add or Remove Programs
function.
●
(Linux, UNIX) From a command prompt, type: file_name.bin
2. If prompted, select a language for the uninstall program and click OK.
3. Follow the on-screen instructions, and then click Finish.
191
F
Upgrading LiveCycle Products to Version 7.2
or 7.2.1
This chapter describes the tasks required to upgrade your current LiveCycle products to version 7.2, or to
version 7.2.1 for LiveCycle Assembler and LiveCycle Workflow.
This document should be used in conjunction with the Installing and Configuring LiveCycle guide or the
Installing and Configuring LiveCycle Security Products guide for your application server. Throughout this
document, specific sections in these installing and configuring guides are listed when more detailed
information is available.
For a complete list of the supported platforms and system requirements for LiveCycle 7.2 products, see the
“Before You Install” chapter in this guide.
This chapter uses the following naming conventions for common file paths:
[LiveCycle root] Refers to the location where LiveCycle products and components earlier than versions
7.2 or 7.2.1 are installed.
[LiveCycle72 root] Refers to the location where LiveCycle products and components with versions 7.2
and 7.2.1 are installed.
The Installing and Configuring LiveCycle guides apply to the following products:
●
LiveCycle Assembler 7.2.1
●
Adobe LiveCycle Forms 7.2
●
Adobe LiveCycle Form Manager 7.2
●
Adobe LiveCycle PDF Generator 7.2
●
Adobe LiveCycle Print 7.2
●
Adobe LiveCycle Workflow 7.2.1
●
Adobe LiveCycle Workflow Designer 7.2.1
●
Watched Folder 1.1
The Installing and Configuring LiveCycle Security Products guides apply to the following products:
●
Adobe LiveCycle Document Security 7.2
●
Adobe LiveCycle Reader Extensions 7.2
●
Adobe LiveCycle Policy Server 7.2
Upgrade guidelines
This section describes guidelines you must follow when upgrading LiveCycle products to version 7.2 or
version 7.2.1.
192
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
Updating your application server
193
Updating your application server
Ensure that you apply the required patches and fix packs to the application server on which you are
running LiveCycle products, and obtain the updated database drivers. Your environment must meet the
system requirements described in the “Support software” chapter in this guide.
Using automatic or turnkey installations for upgrading
For installations for deployment to WebSphere or WebLogic, you can use Configuration Manager to
configure and deploy the product, initialize the database, and verify the deployment.
Before using Configuration Manager to automatically configure LiveCycle products, the existing LiveCycle
components must be undeployed and the application server restarted.
For installations for deployment to JBoss, you can configure the products for deployment and initialize the
database using Configuration Manager, but you must deploy the product components manually. The
turnkey installation option is only supported for upgrading LiveCycle Reader Extensions.
If you are running LiveCycle products that were originally installed using the turnkey installation option,
you can upgrade to version 7.2 or 7.2.1 by following the manual or the auto-configuration upgrade
instructions that are included in this guide. Instructions for upgrading LiveCycle Reader Extensions using
the turnkey installation option are also included in this chapter.
Configuring using Configuration Manager during the upgrade process
It is recommended that you do not automatically configure the WebSphere or WebLogic application
server using Configuration Manager because current configuration settings on your application server
may be overwritten.
During the upgrade process, you will configure some product and application server run-time properties
using Configuration Manager. For upgrades from 7.x versions, you should configure the upgraded product
using the same property values. The “Configuring LiveCycle Products for Deployment” chapter in the
Installing and Configuring guides provides information about the properties that you will configure when
you upgrade the product.
Summary of manual upgrade process
This checklist describes the high-level tasks that you must perform to upgrade from a LiveCycle 7.x
product to a LiveCycle 7.2 or 7.2.1 product. For detailed information, see the specific upgrade procedures
for the product you are upgrading.
The sections referenced in the “See” column are in the Installing and Configuring guides for your
application server, depending on the product you are installing.
Task
See
Back up the database that contains the current
LiveCycle configuration and run-time data.
The database server documentation.
Back up copies of the currently deployed LiveCycle
EAR and WAR files to a separate directory.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
Task
LiveCycle Forms and LiveCycle Print
194
See
(JBoss) Stop services, if applicable (JBoss for Adobe
LiveCycle, MySQL for Adobe LiveCycle, JBoss for
Workflow BAM, AdobeDocumentSecurity, or
AdobeReaderExtensions).
Undeploy LiveCycle components from the application
server.
Refer to the application server documentation.
Uninstall the previous version of LiveCycle products
using the uninstaller program.
The “Uninstalling LiveCycle Products” chapter
Apply the required patches and fix packs to the
application server and obtain the updated database
drivers.
The “Supported software” section of the
“Before You Install” chapter
Install the LiveCycle 7.2 or 7.2.1 product to a new
(non-default) location on your file system. Do not
install to the same directory where your previous
LiveCycle products are installed.
The “Installing LiveCycle Products” chapter
Run Configuration Manager to configure the product.
Apply the configuration data that you used in the
original installation. For WebSphere and WebLogic,
you can automatically deploy the product, initialize
the database, and verify the deployment using
Configuration Manager.
(JBoss) The “Configuring LiveCycle Products
for Deployment” chapter
(JBoss) Deploy the product components to the
application server.
The “Manually deploying to JBoss” chapter
(JBoss) Run Configuration Manager to initialize the
database.
The “Initializing the Database” chapter
(WebLogic, WebSphere) The “Automatically
Configuring LiveCycle Products” or
“Configuring LiveCycle Products for
Deployment” chapter
LiveCycle Forms and LiveCycle Print
This section provides upgrading instructions for LiveCycle Forms 7.2 and LiveCycle Print 7.2.
Note: You must install LiveCycle Forms 7.2 before installing LiveCycle Print 7.2.
Upgrading from Adobe Form Server 6.0 to LiveCycle Forms 7.2
This procedure describes how to upgrade from Adobe Form Server 6.0 to LiveCycle Forms 7.2.
➤ To upgrade from Form Server 6.0 to LiveCycle Forms 7.2:
1. Undeploy the earlier product from the application server. (For information, see your application server
documentation.)
2. Uninstall the earlier product using the uninstaller program. (For information, see the Form Server 6.0
Installation and Configuration Guide.)
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere LiveCycle Forms and LiveCycle Print 7.x to LiveCycle Forms and LiveCycle Print 7.2
195
3. Upgrade the application server and database to ensure that they meet the system and software
requirements for LiveCycle 7.2 products.
4. Install and deploy LiveCycle Forms 7.2, and initialize the database using the instructions in this
document for the manual installation and deployment option. For WebSphere and WebLogic, you can
automatically deploy the product, initialize the database, and verify the deployment using
Configuration Manager.
Note: If you did not include User Management with the installation and configuration of LiveCycle Forms,
you do not need to connect to a database, and you do not need to follow steps to initialize the
database.
LiveCycle Forms and LiveCycle Print 7.x to LiveCycle Forms and
LiveCycle Print 7.2
This procedure describes how to upgrade from LiveCycle Forms 7.0 or 7.1 to LiveCycle Forms 7.2, and from
LiveCycle Print 7.1 to LiveCycle Print 7.2.
It is recommended that you install LiveCycle Forms 7.2 to a new directory so that you do not overwrite the
previously installed version.
➤ To retrieve form configuration properties (for LiveCycle Forms 7.0 or 7.1 configured without User
Management):
1. Type the following URL in a web browser:
http://[host_name]:[port]/FormServerAdmin/settings.html
The default port number for WebLogic is 7001. If you are running a Managed Server, you may have
configured the application server to use a different port number, such as 8001. The default port for
WebSphere is 9080; the default port for JBoss is 8080.
2. Record the settings that appear on this page.
➤ To retrieve form configuration properties (for LiveCycle Forms 7.0 or 7.1 configured with User
Management):
1. Type the following URL in a web browser:
http://[host_name]:[port]/adminui
The default port number for WebLogic is 7001. If you are running a Managed Server, you may have
configured the application server to use a different port number, such as 8001. The default port for
WebSphere is 9080; the default port for JBoss is 8080.
2. Log into Administrator.
3. Click Services, and then click Adobe LiveCycle Forms.
4. Record the settings that appear on this page.
5. These properties must be set for the new installation on the Form Server Module Configuration screen
on Configuration Manager when you install and configure LiveCycle Forms 7.2.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere LiveCycle Forms and LiveCycle Print 7.x to LiveCycle Forms and LiveCycle Print 7.2
196
➤ To upgrade to LiveCycle Forms 7.2 and LiveCycle Print 7.2:
1. Back up the database that currently contains the LiveCycle Forms 7.0 or 7.1 configuration and run-time
data.
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
3. Back up the XDC files from LiveCycle Print 7.1.
4. (JBoss) If your LiveCycle deployment is running on a JBoss Application Server with a MySQL database
that you installed using the turnkey option, stop the JBoss for Adobe LiveCycle service and the MySQL
for Adobe LiveCycle service.
5. Undeploy the following files from your application server:
●
LiveCycle.ear
●
FormsIVS.ear
●
adobe-FontManager.war
●
LCMBootstrapper.war
●
adobe-printSubmitter.ear (LiveCycle Print only)
For information about undeploying from WebLogic or WebSphere, see “Uninstalling EAR files” in the
Installing and Configuring LiveCycle guide.
Note: When the Livecycle.ear file is undeployed, LiveCycle Print 7.1 does not work.
6. Stop the WebLogic Server or WebSphere Application Server.
7. Uninstall the previous versions of LiveCycle products using the uninstaller program. (See “Uninstalling
LiveCycle Products” in the related Installing and Configuring LiveCycle guide.)
8. Upgrade the application server and database to ensure that they meet the system and software
requirements for LiveCycle Forms 7.2.
9. Install LiveCycle Forms 7.2 to a new (non-default) directory (for example, C:\Adobe\LiveCycle72\ or
/opt/adobe/livecycle72/). Follow the instructions in “Installing LiveCycle Products” in the Installing and
Configuring LiveCycle guide.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same root [LiveCycle72 root] directory.
10. Copy the DocumentServicesLibrary.jar file, according to your application server:
●
(WebLogic) From the [LiveCycle72 root]/components/csa/weblogic/lib/adobe directory to the
[appserverdomain]/lib directory.
●
(WebSphere) From the [LiveCycle72 root]/components/csa/websphere/lib/adobe directory to the
[appserver root]/optionalLibraries.
●
(JBoss) From the [LiveCycle72 root]/components/csa/jboss/lib/adobe directory to the
[appserver root]/server/all/lib directory.
Note: Modify the XDC files installed with LiveCycle Print 7.2 to match those that you are using with
version 7.1, and use these modified files. For information about the XDC files included with
LiveCycle Print, see the Getting Started guide and the Editing XDC Files to Customize Printing
Workflows guide for LiveCycle Print.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere LiveCycle Forms and LiveCycle Print 7.x to LiveCycle Forms and LiveCycle Print 7.2
197
11. Start the application server.
12. Configure LiveCycle Forms 7.2 using Configuration Manager. (See the “Configuring LiveCycle Products
for Deployment” chapter in the Installing and Configuring LiveCycle guide.) As you proceed through the
Configuration Manager screens, choose the following options:
●
Configuration Mode: Select Custom Configuration Wizard.
●
Product Selection: Select the application server you are using, as well as Foundation, LiveCycle
Forms, and LiveCycle Print (if applicable).
●
Adobe User Management Selection: Select one of the following options:
●
●
LiveCycle Forms with User Management and Administrator if you used LiveCycle Forms with
User Management in the previous deployment
●
LiveCycle Forms without User Management and Administrator if you did not previously use
LiveCycle Forms with User Management
Task Selection: Select the following options:
●
Configure and Assemble products
●
Bootstrap Database (only if you are including User Management in the configuration)
For WebSphere and WebLogic, also select these options:
●
Deploy products
●
Verify deployed products
13. Follow the instructions on the remaining Configuration Manager screens. Accept the default values in
Configuration Manager whether you are configuring with User Management and Administrator or
without User Management and Administrator.
Note: When prompted to specify the Global Storage Directory location, specify the same location that
you currently use for this directory.
If you are deploying to WebSphere or WebLogic, complete steps 14 and 15. If you are deploying to
JBoss, complete steps 16 and 17.
14. (WebSphere and WebLogic) On the Confirm Products to Deploy screen, select these EAR files:
●
LiveCycle.ear
●
adobe-FontManager.ear.
●
adobe-printSubmitter.ear (LiveCycle Print only)
15. (WebSphere and WebLogic) Follow the instructions on the Configuration Manager screens to initialize
the database and verify the deployed products.
16. (JBoss) Deploy LiveCycle Forms 7.2. (See “Manually Deploying to JBoss” in the Installing and Configuring
LiveCycle guide.)
17. (JBoss) (User Management configuration) Run Configuration Manager to initialize the database. Select
Custom Configuration Wizard, and then select Bootstrap database.
Note: Initializing the database is necessary to add new table columns to the database schema.
Initializing the database does not alter existing data.
18. Deploy the FormsIVS.ear files according to the steps required for your application server. (See
“LiveCycle Forms post-deployment tasks” in the Installing and Configuring LiveCycle guide.)
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Form Manager
198
19. Verify the deployment by following the instructions in “LiveCycle Forms post-deployment tasks” in the
Installing and Configuring LiveCycle guide.
20. Update your application’s class path with the location of these JAR files: formserver-client.jar,
adobe-common.jar, datamanager-client.jar, and AdobeCSAUtils.jar. Add the um-client.jar file to the
application class path if the application passes an InvocationContext object in the Form Server
Module API. For details about these files, see Developing Custom Applications located in the
[LiveCycle72 root]/forms/documentation directory.
➤ To configure LiveCycle Forms (when not using User Management):
1. Type the following URL in a web browser:
http://[host_name]:[port]/FormServerAdmin/settings.html
The default port number for WebLogic is 7001. If you are running a Managed Server, you may have
configured the application server to use a different port number, such as 8001. The default port for
WebSphere is 9080; the default port for JBoss is 8080.
2. Enter the settings that you recorded when you retrieved the LiveCycle Forms configuration settings
from the previous LiveCycle.ear file. (See “To retrieve form configuration properties (for LiveCycle
Forms 7.0 or 7.1 configured without User Management):” on page 195.)
3. Click Save.
Note: The settings modified here are not retained when the application server is restarted.
➤ To configure LiveCycle Forms (when using User Management):
1. Type the following URL in a web browser:
http://[host_name]:[port]/adminui
2. The default port number for WebLogic is 7001. If you are running a Managed Server, you may have
configured the application server to use a different port number, such as 8001. The default port for
WebSphere is 9080; the default port for JBoss is 8080.
3. Log into Administrator.
4. Click Services, and then click Adobe LiveCycle Forms.
5. Enter the settings you recorded when you retrieved the LiveCycle Forms configuration settings from
the previous LiveCycle.ear file. (See “To retrieve form configuration properties (for LiveCycle Forms 7.0
or 7.1 configured with User Management):” on page 195.)
6. Click Save.
LiveCycle Form Manager
This section provides instructions for upgrading from LiveCycle Form Manager 7.0.1 to LiveCycle Form
Manager 7.2. To perform this upgrade, you must update the server components that are deployed to the
application server and initialize the database.
It is recommended that you install LiveCycle Form Manager 7.2 to a new directory so that you do not
overwrite the previously installed version.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Form Manager
199
➤ To upgrade LiveCycle Form Manager 7.0.1 to 7.2:
1. Back up the database that currently contains the LiveCycle Form Manager 7.0.1 configuration and
run-time data.
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
3. (JBoss) If your LiveCycle deployment is running on a JBoss Application Server with a MySQL database
that you installed using the turnkey option, stop the JBoss for Adobe LiveCycle service and the MySQL
for Adobe LiveCycle service.
4. Undeploy the following LiveCycle Form Manager 7.0.1 components by following the instructions in the
Installing and Configuring guide for LiveCycle Form Manager 7.0.1:
●
adobe-FontManager.war
●
LiveCycle.ear
●
LCMBootstrapper.war
For information about undeploying from WebLogic or WebSphere, see “Uninstalling EAR files” in this
Installing and Configuring LiveCycle guide.
5. Stop the WebLogic Server or WebSphere Application Server.
6. Uninstall the previous version of LiveCycle products using the uninstaller program. (See “Uninstalling
LiveCycle Products” in the related Installing and Configuring LiveCycle guide.)
7. Upgrade the application server and database to ensure that they meet the system and software
requirements for LiveCycle 7.2 products.
8. Install LiveCycle Form Manager 7.2 to a new (non-default) directory (for example,
C:\Adobe\LiveCycle72\ or /opt/adobe/livecycle72/). Follow the instructions in “Installing LiveCycle
Products” in the Installing and Configuring LiveCycle guide.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same [LiveCycle72 root] directory.
9. Copy the DocumentServicesLibrary.jar file, according to your application server:
●
(WebLogic) From the [LiveCycle72 root]/components/csa/weblogic/lib/adobe directory to the
[appserverdomain root]/lib directory
●
(WebSphere) From the [LiveCycle72 root]/components/csa/websphere/lib/adobe directory to the
[appserver root]/optionalLibraries directory
●
(JBoss) From the [LiveCycle72 root]/components/csa/jboss/lib/adobe directory to the
[appserver root]/server/all/lib directory
10. Start the application server.
11. Configure LiveCycle Form Manager 7.2 using Configuration Manager. (See “Configuring LiveCycle
Products for Deployment” in the Installing and Configuring LiveCycle guide.) As you proceed through
the Configuration Manager screens, choose the following options:
●
Configuration Mode: Select Custom Configuration Wizard.
●
Product Selection: Select the application server you are using, as well as Foundation and the
product you are configuring.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
●
LiveCycle Assembler, LiveCycle Workflow, and Watched Folder
200
Task Selection: Select the following options:
●
Configure and Assemble products
●
Bootstrap Database
For WebSphere and WebLogic, also select these options:
●
Deploy products
●
Verify deployed products
12. Follow the instructions on the Configuration Manager screens to configure the LiveCycle.ear file.
Ensure that you configure your LiveCycle 7.2 EAR file with the same settings that you chose for version
7.0.1. If you are deploying to WebSphere or WebLogic, complete steps 13 and 14. If you are deploying
to JBoss, complete steps 15 and 16.
Note: When prompted to specify the Global Storage Directory location, specify the same location that
you currently use for this directory.
13. (WebSphere and WebLogic) On the Confirm Products to Deploy screen, select these EAR files:
●
LiveCycle.ear
●
adobe-FontManager.ear
14. (WebSphere and WebLogic) Follow the instructions on the Configuration Manager screens to initialize
the database and verify the deployed products.
15. (JBoss) Deploy LiveCycle Form Manager 7.2 components. (See “Manually Deploying to JBoss” in the
Installing and Configuring LiveCycle guide.)
16. (JBoss) Run Configuration Manager to initialize the database. Select Custom Configuration Wizard,
and then select Bootstrap database. (See “Initializing the Database” in the Installing and Configuring
LiveCycle guide.)
Note: Initializing the database is necessary to add new table columns to the database schema.
Initializing the database does not alter existing data.
17. Verify the deployment by following the instructions in “LiveCycle Form Manager post-deployment
tasks” the Installing and Configuring LiveCycle guide.
Note: You can also verify your installation and configuration by using the samples available at
www.adobe.com/devnet/livecycle/samples.html.
LiveCycle Assembler, LiveCycle Workflow, and Watched Folder
This section describes how to upgrade any or all of the following products:
●
LiveCycle Workflow 7.0.1 or 7.2 to LiveCycle Workflow 7.2.1
●
LiveCycle Assembler 7.2 to LiveCycle Assembler 7.2.1
●
Watched Folder 1.0 to Watched Folder 1.1
If you are upgrading LiveCycle Workflow as a stand-alone product, do not include the steps that pertain to
Watched Folder or LiveCycle Assembler. Watched Folder is intended for use with LiveCycle Assembler and
LiveCycle Workflow; you must install LiveCycle Workflow before installing Watched Folder.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Assembler, LiveCycle Workflow, and Watched Folder
201
To perform this upgrade, you must update the server components that are deployed to the application
server and initialize the database. It is recommended that you install LiveCycle Assembler 7.2.1 to a new
directory so that you do not overwrite the previously installed version.
When you configure LiveCycle Assembler 7.2.1 using Configuration Manager, ensure that you set the
Security Groups option to the same value that you have set for LiveCycle Assembler 7.2. (The value can be
set to an asterisk (*), which only allows users with a valid entry in the LDAP system to log in, or to no value,
which allows any user to log in.)
➤ To upgrade to LiveCycle Assembler 7.2.1, LiveCycle Workflow 7.2.1, and Watched Folder 1.1:
1. Back up the database that currently contains the LiveCycle Workflow 7.0.1 or 7.2 configuration and
run-time data.
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
3. (JBoss) If your LiveCycle deployment is running on a JBoss Application Server with a MySQL database
that you installed using the turnkey option, stop the JBoss for Adobe LiveCycle service and the MySQL
for Adobe LiveCycle service.
4. Undeploy the following files from your application server:
●
LiveCycle.ear
●
adobe-FontManager.war
●
LCMBootstrapper.war
●
adobe-Assembler7.ear (LiveCycle Assembler only)
For information about undeploying from WebLogic or WebSphere, see “Uninstalling EAR files” in the
Installing and Configuring LiveCycle guide.
5. (WebSphere and WebLogic) Stop the application server.
6. Uninstall the previous versions of LiveCycle products using the uninstaller program. (See “Uninstalling
LiveCycle Products” in the Installing and Configuring LiveCycle guide.)
7. Install LiveCycle Assembler 7.2.1 to a new (non-default) directory (for example, C:\Adobe\LiveCycle72\
or /opt/adobe/livecycle72/). Follow the instructions in “Installing LiveCycle Products” in the Installing
and Configuring LiveCycle guide.
8. Install LiveCycle Workflow 7.2.1 to the same directory where you installed LiveCycle Assembler 7.2.1 by
following the instructions in “Installing LiveCycle Products” in the related Installing and Configuring
LiveCycle guide.
Note: You can install LiveCycle Assembler and LiveCycle Workflow in any order.
9. Install Watched Folder to the same directory where you installed LiveCycle Workflow by following the
instructions in “Installing Watched Folder” in the Installing and Configuring LiveCycle guide. LiveCycle
Workflow must already be installed.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same [LiveCycle72 root] directory.
10. Copy the DocumentServicesLibrary.jar file, according to your application server:
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Assembler, LiveCycle Workflow, and Watched Folder
202
●
(WebLogic) From the [LiveCycle72 root]/components/csa/weblogic/lib/adobe directory to the
[appserverdomain]/lib directory.
●
(WebSphere) From the [LiveCycle72 root]/components/csa/websphere/lib/adobe directory to the
[appserver root]/optionalLibraries.
●
(JBoss) From the [LiveCycle72 root]/components/csa/jboss /lib/adobe directory to the [appserver
root]/server/all/lib directory. Copy the adobe-service.xml file from the [LiveCycle72_root]/
configurationManager/deploy/jboss directory to the [appserver root]/server/all/deploy/jms
directory.
11. Start the application server.
12. Configure the LiveCycle products by using Configuration Manager. (See “Configuring LiveCycle
Products for Deployment” in the Installing and Configuring LiveCycle guide.) As you proceed through
the Configuration Manager screens, choose the following options:
●
Configuration Mode: Select Custom Configuration Wizard.
●
Product Selection: Select the application server you are using, and then select Foundation, as well
as all of the products that you installed.
●
Task Selection: Select the following options:
●
Configure and Assemble products
●
Bootstrap Database
For WebSphere and WebLogic, also select these options:
●
Deploy products
●
Verify deployed products
13. Follow the instructions on the remaining Configuration Manager screens. Ensure that you configure
your 7.2.1 EAR file with the same settings you chose for version 7.0.1 or 7.2. If you are deploying to
WebSphere or WebLogic, complete steps 14 and 15. If you are deploying to JBoss, complete steps 16
and 17.
Note: When prompted to specify the Global Storage Directory location, specify the same location that
you currently use for this directory.
14. (WebSphere and WebLogic) On the Confirm Products to Deploy screen, select the archives that you
are deploying:
●
adobe-FontManager.ear
●
LiveCycle.ear
●
adobe-Assembler7.ear (LiveCycle Assembler only)
15. (WebSphere and WebLogic) Follow the instructions on the Configuration Manager screens to initialize
the database and verify the deployed products.
16. (JBoss) Deploy LiveCycle Assembler, LiveCycle Workflow, and Watch Folder 7.2. (See “Manually
Deploying to JBoss” in the Installing and Configuring LiveCycle guide.) These components consist of
these EAR files:
●
LiveCycle.ear
●
adobe-FontManager.ear
●
LCM.ear
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
●
LiveCycle Workflow Designer
203
adobe-Assembler7.ear
17. (JBoss) Run Configuration Manager to reinitialize the database. Select Custom Configuration Wizard,
and then select Bootstrap database. (See “Initializing the Database” in the Installing and Configuring
LiveCycle guide.)
18. Upgrade the Assembler QPAC. (See Upgrading LiveCycle Workflow Designer or the Creating Workflows
guide, available with the LiveCycle Workflow documentation set.)
Note: Initializing the database is necessary to add new table columns to the database schema.
Initializing the database does not alter existing data.
19. Verify the deployment by following the instructions in the “Post Deployment” section in the Installing
and Configuring LiveCycle guide.
Note: You can also verify your installation and configuration by using the samples available at
www.adobe.com/devnet/livecycle/samples.html.
LiveCycle Workflow Designer
You need to use the version of LiveCycle Workflow Designer that LiveCycle Workflow 7.2.1 provides. If you
want to use the new User QPAC with existing workflows, you need to migrate your workflows.
You must upgrade your LiveCycle QPACs from LiveCycle Workflow 7.0.1 or 7.2 to version 7.2.1. See
“Updating components” in the Creating Workflows guide that is included with LiveCycle Workflow
Designer.
➤ To upgrade LiveCycle Workflow Designer:
1. Uninstall LiveCycle Workflow 7.0.1 Designer.
2. Install LiveCycle Workflow 7.2.1 Designer. (See “Installing LiveCycle Workflow Designer” in the Installing
and Configuring LiveCycle guide.)
Note: LiveCycle Workflow 7.2.1 provides an updated User QPAC that includes new features. If any of
your workflows include User actions and you want to use the new features, you must migrate
your workflows. For more information, see the topic “Migrating Workflows from Older Versions”
in the Creating Workflows guide or in LiveCycle Workflow Designer Help.
BAM Server for LiveCycle Workflow
This section describes general best practices to follow when upgrading to a new version of BAM Server.
You must use the BAM Server upgrade utility to upgrade metadata XML files that you export from
LiveCycle Workflow Business Activity Monitor during the upgrade process.
Upgrading BAM Server involves performing the following tasks:
●
Exporting the BAM metadata using BAM Workbench
●
Upgrading the BAM metadata using the BAM Server upgrade utility
●
Undeploying the BAM Server EAR file from the application server
●
Removing recovery log files and dropping existing tables into the BAM metadata database
●
Deploying the BAM Server EAR file that LiveCycle Workflow 7.2.1 provides
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
●
About the BAM Server upgrade utility
204
Importing the upgraded BAM metadata using BAM Workbench
About the BAM Server upgrade utility
The BAM Server upgrade utility upgrades exported metadata files so that they include new features
required for the current product version.
The BAM Server upgrade utility is packaged in the cqupgrade.jar file. When you install LiveCycle Workflow,
this file is located in the [LiveCycle root]/Workflow/bam/CQUpgrade directory.
Note: The upgrade utility generates the message “Error parsing input file” when files cannot be upgraded.
If this error is generated, the file specified in the error message may be damaged. Contact Adobe
Systems for assistance.
Syntax
The following command upgrades metadata files that have been exported to a JAR file:
java -jar cqupgrade.jar -jar -i inJar.jar [-o outJar.jar]
Parameters
You can use the following parameters in the BAM Server upgrade utility command:
inJar.jar: The path to the JAR file that contains the exported metadata to upgrade.
outJar.jar (optional): The path to the upgraded JAR file. If you omit this parameter, the upgraded
files are saved in the JAR file specified in inJar.jar.
The following examples show commands that you can use to upgrade metadata stored in JAR files using
the BAM Server upgrade utility:
●
The following command upgrades the metadata files that are stored in a JAR file named toUpgrade.jar,
which is located in the same directory as cqupgrade.jar:
java -jar cqupgrade.jar -i toUpgrade.jar
●
The following command upgrades the metadata files in the toUpgrade.jar file and saves the upgraded
files to a different JAR file named upgraded.jar. The file is saved in the same directory as cqupgrade.jar:
java -jar cqupgrade.jar -i toUpgrade.jar -o upgraded.jar
➤ To upgrade Business Activity Monitor:
1. Log into BAM Workbench.
2. Click the Administration tab and then click Import/Export.
3. In the Operations menu, select Export Metadata to a JAR File (download).
4. In the File Download dialog box, click Save.
5. Specify a location and file name for the exported JAR file, and click Save.
6. Click Close in the Download Complete dialog box.
7. Click System Settings, and then click the Checkpoint Configuration tab. Note the directory path in
the Recovery Log Directory box. You will need to know where the recovery log directory is at a later
step in this procedure.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle PDF Generator
205
8. Shut down Business Activity Monitor.
9. Use the BAM Server upgrade utility (cqupgrade.jar) to upgrade the metadata that you exported in a
JAR file. (See “About the BAM Server upgrade utility” on page 204.)
10. Undeploy the BAM Server EAR file by following the instructions for your application server:
●
(JBoss) Remove the following directories:
●
[jboss bam root]/server/default/work
●
[jboss bam root]/server/default/tmp
●
[jboss bam root]/server/default/data
●
[jboss bam root]/server/conf/jboss.web
●
(WebSphere) Undeploy the old BAM Server EAR file using WebSphere Administrative Console.
●
(WebLogic) Undeploy the old BAM Server EAR file using WebLogic Server Administration Console.
11. Delete all of the files from the recovery log directory that have names similar to the following patterns:
●
filestore*.dat
●
DEFAULTRECOVERYLOGGER_*
●
chkpoint_.x
12. Use your database management tools to drop the database tables that store the BAM metadata.
Alternatively, you may want to create a new BAM metadata database. For more information about the
BAM metadata database, see “Creating the BAM metadata database” in the Installing and Configuring
LiveCycle guide for your application server.
13. Deploy the new version of BAM Server to the application server. (See “Deploying BAM Server” in the
Installing and Configuring LiveCycle guide.)
14. Log into BAM Workbench.
15. Review the BAM Server configuration settings to determine if updates are required. (See “Getting
Started with BAM Server” in the Installing and Configuring LiveCycle guide.)
16. Click the Administration tab and then click Import/Export.
17. In the Operations menu, select Import Metadata from a JAR File (upload).
18. Click Browse to locate the JAR file that contains the upgraded BAM metadata, and then click OK.
19. Restart the BAM Server instance.
LiveCycle PDF Generator
To upgrade from LiveCycle PDF Generator 7.0.1 or 7.0.2 to LiveCycle PDF Generator 7.2, you must undeploy
the product you are currently using before installing and deploying the new product.
The instructions in this section apply to LiveCycle PDF Generator for PostScript, LiveCycle PDF Generator
Elements, and LiveCycle PDF Generator Professional.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle PDF Generator
206
➤ To upgrade LiveCycle PDF Generator 7.0.2 to LiveCycle PDF Generator 7.2:
1. Back up the database that currently contains the LiveCycle PDF Generator 7.0.1 or 7.0.2 configuration
and run-time data.
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
3. (JBoss) If your LiveCycle PDF Generator deployment is running on a JBoss Application Server with a
MySQL database that you installed using the turnkey option, stop the JBoss for Adobe LiveCycle
service.
4. If you are installing LiveCycle PDF Generator Professional or LiveCycle PDF Generator Elements,
uninstall Adobe Acrobat 7.0.5 from the Add/Remove programs window in the Microsoft Windows
Control Panel, and then reboot your system.
5. Undeploy the following LiveCycle PDF Generator components by following the instructions in the
Installing and Configuring guide for LiveCycle PDF Generator 7.0.2:
●
pdfg-all.ear (or pdfg-ps-all.ear)
●
LiveCycle.ear
●
adobe-FontManager.war
●
LCMBootstrapper.war
For information about undeploying from WebLogic or WebSphere, see “Uninstalling EAR files” in the
Installing and Configuring LiveCycle guide.
6. (WebSphere and WebLogic) Stop the application server.
7. Uninstall the previous versions of LiveCycle products by using the uninstaller program. (See
“Uninstalling LiveCycle Products” in the Installing and Configuring LiveCycle guide.)
8. Install LiveCycle PDF Generator 7.2 to a new (non-default) directory (for example,
C:\Adobe\LiveCycle72\ or /opt/adobe/livecycle72/. Follow the instructions in “Installing LiveCycle
Products” in the Installing and Configuring LiveCycle guide.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same [LiveCycle72 root] directory.
9. Copy the DocumentServicesLibrary.jar file, according to your application server:
●
(WebLogic) From the [LiveCycle72 root]/components/csa/weblogic/lib/adobe directory to the
[appserverdomain]/lib directory
●
(WebSphere) From the [LiveCycle72 root]/components/csa/websphere/lib/adobe directory to the
[appserver root]/optionalLibraries
●
(JBoss) From the [LiveCycle72 root]/components/csa/jboss/lib/adobe directory to the
[appserver root]/server/all/lib directory. Copy the adobe-service.xml file from the [LiveCycle72_root]/
configurationManager/deploy/jboss directory to the [appserver root]/server/all/deploy/jms
directory.
10. Start the application server.
11. Configure the LiveCycle products by using Configuration Manager. (See “Configuring LiveCycle
Products for Deployment” in the Installing and Configuring LiveCycle guide.) As you proceed through
the Configuration Manager screens, choose the following options:
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle PDF Generator
207
●
Configuration Mode: Select Custom Configuration Wizard.
●
Product Selection: Select the application server you are using, and then select Foundation, and
LiveCycle PDF Generator.
●
Task Selection: Select all of the following options:
●
Configure and Assemble products
●
Bootstrap Database
For WebSphere and WebLogic, also select these options:
●
Deploy products
●
Verify deployed products
12. Follow the instructions on the remaining Configuration Manager screens. Ensure that you configure
your LiveCycle 7.2 EAR file with the same settings you chose for version 7.0.2. If you are deploying to
WebSphere or WebLogic, complete steps 13 and 14. If you are deploying to JBoss, complete steps 15
and 16.
Note: When prompted to specify the Global Storage Directory location, specify the same location that
you currently use for this directory.
13. (WebSphere and WebLogic) On the Confirm Products to Deploy screen, select the archives that you are
deploying:
●
pdfg-all.ear (or pdfg-ps-all.ear)
●
adobe-FontManager.ear
●
LiveCycle.ear
14. (WebSphere and WebLogic) Follow the instructions on the Configuration Manager screens to initialize
the database and verify the deployed products.
15. (JBoss) Deploy the LiveCycle PDG Generator 7.2 components:
●
LiveCycle.ear
●
adobe-FontManager.ear
●
LCM.ear
●
pdfg-all.ear (or pdfg-ps-all.ear)
(See “Manually Deploying to JBoss” in the Installing and Configuring LiveCycle guide.)
16. (JBoss) Run Configuration Manager to reinitialize the database. Select Custom Configuration Wizard,
and then select Bootstrap database. (See “Initializing the Database” in the Installing and Configuring
LiveCycle guide.)
Note: Initializing the database is necessary to add new table columns to the database schema.
Initializing the database does not alter existing data.
17. Verify the deployment by following the instructions in “LiveCycle PDF Generator post-deployment
tasks” in the Installing and Configuring LiveCycle guide.
Note: You can also verify your installation and configuration by using the samples available at
www.adobe.com/devnet/livecycle/samples.html.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Document Security
208
➤ To configure JMS Messaging for WebSphere running on Windows:
1. In the WebSphere Administrative Console, delete the JMS queues, topics, and listener ports for each
server.
2. Configure WebSphere MQ by following the instructions in “Configuring JMS resources for WebSphere
MQ” in the Installing and Configuring LiveCycle guide.
3. Run the scripts provided by Configuration Manager to create queues in the MQ installation by
following the instructions in “Preparing WebSphere MQ” in the Installing and Configuring LiveCycle
guide.
4. Run Configuration Manager again and select the Configure the Application Server task. Follow the
instructions on the Configuration Manager screens to configure application server details. (See
“Changing the application server settings” in the Installing and Configuring LiveCycle guide.) As you
proceed through the Configuration Manager screens, choose the following options:
●
JVM Settings: Select Do Not Apply.
●
JMS settings: Specify values for the properties of the MQ service.
●
Datasource Creation: Select Do Not Apply.
5. On the Configure Application Server screen, click Apply Settings Now to configure your application
server, and, when the task is complete, click Next.
6. Restart the application server and, on the Application Server/Cluster Restart screen, click Next if you
selected another task for Configuration Manager to perform, or click Finish to close Configuration
Manager.
7. Verify that the applications start correctly.
LiveCycle Document Security
This section provides instructions for upgrading from LiveCycle Document Security 7.0 or 7.1 to LiveCycle
Document Security 7.2. To perform this upgrade, you must update the server components that are
deployed to the application server.
It is recommended that you install LiveCycle Document Security 7.2 to a new directory so that you do not
overwrite the previously installed version.
➤ To upgrade to LiveCycle Document Security 7.2:
1. Back up the following files and folders:
●
../trust.xml
●
../credentials/
●
../certificates/
●
../CRLs/
●
../keystore
●
../trust.sig
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Document Security
209
3. Undeploy the following LiveCycle Document Security components by following the instructions in the
Installing and Configuring guide for LiveCycle Document Security 7.0 or 7.1:
WebSphere and WebLogic
JBoss
adobe-FontManager.war
adobe-FontManager.bar
adobe-PDFManipulation.war
adobe-PDFManipulation.bar
adobe-TrustManager.war
adobe-TrustManager.bar
DataManagerService.war
AdobeServices.sar
ServicesNatives-2.war
ServicesNatives-2.war
adobe-APSProxy.war
adobe-APSProxy.bar
4. (WebSphere) Set up default users, roles, and login files by following in the instructions in the procedure
“To map users to roles” in the Installing and Configuring LiveCycle Security Products guide. (This
procedure must be completed each time the LiveCycle-security.ear file is redeployed.)
5. Restart the application server.
6. Uninstall the previous version of LiveCycle products by using the uninstaller program. (See
“Uninstalling LiveCycle Products” in the related Installing and Configuring LiveCycle guide.)
7. Install LiveCycle Document Security 7.2 to a new (non-default) directory (for example,
C:\Adobe\LiveCycle72\ or /opt/adobe/livecycle72/. Follow the instructions in “Installing LiveCycle
Products” in the Installing and Configuring LiveCycle Security Products guide.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same [LiveCycle72 root] directory.
8. Copy the DocumentServicesLibrary.jar file, according to your application server:
●
(JBoss) From the [LiveCycle72 root]/components/csa/jboss/lib/adobe directory to the
[appserver root]/server/all/lib directory.
●
(WebLogic) From the [LiveCycle72 root]/components/csa/weblogic/lib/adobe directory to the
[appserver domain]/lib directory.
●
(WebSphere) From the [LiveCycle72 root]/components/csa/websphere/lib/adobe directory to the
[appserver root]/optionalLibraries directory.
9. Configure LiveCycle Document Security 7.2 using Configuration Manager. (See “Configuring LiveCycle
Products”.) As you proceed through the Configuration Manager screens, choose the following options:
●
Configuration Mode: Select Custom Configuration Wizard.
●
Product Selection: Select the application server you are using, as well as Foundation and the
product you are configuring.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
●
LiveCycle Reader Extensions
210
Task Selection: Select the following options:
●
Configure and Assemble products
●
Bootstrap Database
For WebSphere and WebLogic, also select these options:
●
Deploy products
●
Verify deployed products
●
Trust Directory Selection: Select Create a new trust directory.
●
Keystore Selection: Select Create a new keystore and pair.
10. Follow the instructions on the remaining Configuration Manager screens. Ensure that you configure
your 7.2 EAR file with the same settings you chose for version 7.0 or 7.1. If you are deploying to
WebSphere or WebLogic, complete steps 11 and 12. If you are deploying to JBoss, complete steps 13
and 14.
Note: When prompted to specify the Global Storage Directory location, specify the same location that
you currently use for the “Directory for Adobe LiveCycle products” temp file.
11. (WebSphere and WebLogic) On the Confirm Products to Deploy screen, select the archives that you are
deploying:
●
adobe-FontManager.ear
●
LiveCycle.ear
●
LiveCycle-security.ear
12. (WebSphere and WebLogic) Follow the instructions on the Configuration Manager screens to initialize
the database and verify the deployed products.
13. (JBoss) Deploy LiveCycle Document Security 7.2. (See “Manually Deploying to JBoss” in the Installing
and Configuring LiveCycle Security Products guide.)
14. (JBoss) Run Configuration Manager to reinitialize the database. Select Custom Configuration Wizard,
and then select Bootstrap database. (See “Initializing the Database” in the Installing and Configuring
LiveCycle Security Products guide.)
15. Restart the application server.
16. Verify your installation and configuration by using the samples available at
www.adobe.com/devnet/livecycle/samples.html.
LiveCycle Reader Extensions
This section provides instructions for upgrading from LiveCycle Reader Extensions 7.0 or 7.0.2 to LiveCycle
Reader Extensions 7.2. To perform this upgrade, you must update the server components that are
deployed to the application server.
Note: (JBoss) If you previously installed LiveCycle Reader Extensions on Windows for deployment to JBoss
using the turnkey method, see “To upgrade LiveCycle Reader Extensions using the turnkey method”
in the Installing and Configuring LiveCycle Security Products guide for the turnkey upgrade
instructions.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Reader Extensions
211
It is recommended that you install LiveCycle Reader Extensions 7.2 to a new directory so that you do not
overwrite the previously installed version.
If you are using an existing credential, ensure the credential has not expired and is still valid. (See
“LiveCycle Reader Extensions Rights credential” in the Installing and Configuring LiveCycle Security Products
guide.)
Custom applications using existing APIs supported in Adobe Document Services 6.0 for Reader Extensions
are not supported in LiveCycle Reader Extensions 7.2. Custom applications using existing APIs supported
in Adobe Reader Extensions Server 6.1 are supported by and continue to work with LiveCycle Reader
Extensions 7.2.
Digital certificates issued for use with Reader Extensions Server 6.1 are compatible for use with LiveCycle
Reader Extensions 7.2. If you are upgrading from version 6.1 to 7.2, you will not receive a new Rights
credential.
➤ To upgrade LiveCycle Reader Extensions to 7.2:
1. Back up the following files and folders in the [LiveCycle root]/ReaderExtensions/trust directory:
●
../trust.xml
●
../credentials/
●
../certificates/
●
../CRLs/
●
../keystore
●
../trust.sig
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
3. Undeploy the following LiveCycle Reader Extensions components by following the instructions in the
Installing and Configuring guide for LiveCycle Reader Extensions 7.0 or 7.0.2:
WebSphere and WebLogic
JBoss
adobe-FontManager.war
adobe-FontManager.bar
adobe-PDFManipulation.war
adobe-PDFManipulation.bar
adobe-TrustManager.war
adobe-TrustManager.bar
DataManagerService.war
AdobeServices.sar
ServicesNatives-2.war
ServicesNatives-2.war
ares.ear
ares.ear
adobe-CredentialSecurityEJB.ear
adobe-CredentialSecurityEJB.ear
adobe-APSProxy.war
adobe-APSProxy.bar
4. Restart the application server.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Reader Extensions
212
5. Uninstall the previous version of LiveCycle products y using the uninstaller program. (See “Uninstalling
LiveCycle Products” in the related Installing and Configuring LiveCycle guide.)
6. Install LiveCycle Reader Extensions 7.2 to a new (non-default) directory (for example,
C:\Adobe\LiveCycle72\ or /opt/adobe/livecycle72/. Follow the instructions in “Installing LiveCycle
Products” in the Installing and Configuring LiveCycle Security Products guide.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same [LiveCycle72 root] directory.
7. Copy the DocumentServicesLibrary.jar file, according to you application server:
●
(WebLogic) From the [LiveCycle72 root]/components/csa/weblogic/lib/adobe directory to the
[appserver domain]/lib directory.
●
(WebSphere) From the [LiveCycle72 root]/components/csa/websphere/lib/adobe directory to the
[appserver root]/optionalLibraries directory.
●
(JBoss) From the [LiveCycle72 root]/components/csa/jboss/lib/adobe directory to the
[appserver root]/server/all/lib directory.
8. Configure LiveCycle Reader Extensions 7.2 by using Configuration Manager. (See “Configuring
LiveCycle Products” in the Installing and Configuring LiveCycle Security Products guide.) As you proceed
through the Configuration Manager screens, choose the following options:
●
Configuration Mode: Select Custom Configuration Wizard.
●
Product Selection: Select the application server you are using, as well as Foundation and the
product you are configuring.
●
Task Selection: Select the following options:
●
Configure and Assemble products
For WebSphere and WebLogic, also select these options:
●
Deploy products
●
Verify deployed products
●
Trust Directory Selection: Select Create a new trust directory.
●
Keystore Selection: Select Create a new keystore and pair.
9. Follow the instructions on the remaining Configuration Manager screens. Ensure that you configure
your 7.2 EAR file with the same settings you chose for version 7.0 or 7.1. If you are deploying to
WebSphere or WebLogic, complete steps 10 and 11. If you are deploying to JBoss, complete step 12.
Note: When prompted to specify the Global Storage Directory location, specify the same location that
you currently use for the “Directory for Adobe LiveCycle products” temp file.
10. (WebSphere and WebLogic) On the Confirm Products to Deploy screen, select the archives that you are
deploying:
●
adobe-FontManager.ear
●
LiveCycle.ear
●
LiveCycle-security.ear
11. (WebSphere and WebLogic) Follow the instructions on the Configuration Manager screens to initialize
the database and verify the deployed products.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Policy Server
213
12. (JBoss) Deploy LiveCycle Reader Extensions 7.2. (See “Manually Deploying to JBoss” in the Installing and
Configuring LiveCycle Security Products guide.)
13. Restart the application server.
14. Verify the installation and configuration by going to the appropriate URL:
●
(WebLogic) http://[host_name]:7001/ReaderExtensions or
http://[host_name]:8001/ReaderExtensions (Managed Server)
●
(WebSphere) http://[host_name]:9080/ReaderExtensions
●
(JBoss) http://[host_name]:8080/ReaderExtensions
15. Type the user name and password you created when you configured the LiveCycle Reader Extensions
user. (See “Setting up users, roles, and login files” for JBoss or WebLogic or “To map users to roles” for
WebSphere in the Installing and Configuring LiveCycle Security Products guide.)
➤ (JBoss) To upgrade LiveCycle Reader Extensions using the turnkey method:
1. Stop the AdobeReaderExtensions Windows service from the Services window in the Administrative
Tools area of the Windows Control Panel.
2. Verify that port 8080 is not being used.
3. The turnkey installation specifies “localhost” as the host and “8080” as the port for use by JBoss. If JBoss
is already installed, ensure that it is not using port 8080. You cannot configure an alternative host or
port for JBoss during the turnkey installation and configuration process.
4. Install LiveCycle Reader Extensions 7.2 using the turnkey method to a new (non-default) directory (for
example, C:\Adobe\LiveCycle72\). Follow the instructions in “Installing LiveCycle Reader Extensions or
LiveCycle Document Security” in the Installing and Configuring LiveCycle Security Products guide.
5. Verify the installation and configuration by going to the URL
http://[host_name]:8080/ReaderExtensions.
Note: For turnkey installations, the default user name is administrator and the default password is
password. To edit these values, see “Setting up users, roles, and login files” in the Installing and
Configuring LiveCycle Security Products guide.
Note: You can also verify your installation and configuration by using the samples available at
www.adobe.com/devnet/livecycle/samples.html.
LiveCycle Policy Server
This section provides instructions for upgrading from LiveCycle Policy Server 7.0.2 to LiveCycle Policy
Server 7.2. To perform this upgrade, you must update the server components that are deployed to the
application server and initialize the database.
It is recommended that you install LiveCycle Policy Server 7.2 to a new directory so that you do not
overwrite the previously installed version.
➤ To upgrade LiveCycle Policy Server to 7.2:
1. Back up the database that currently contains the LiveCycle Policy Server 7.0.2 configuration and
run-time data.
Adobe LiveCycle
Upgrading LiveCycle Products to Version 7.2 or 7.2.1
Installing and Configuring LiveCycle for WebSphere
LiveCycle Policy Server
214
2. Ensure that you have a back-up copy of the currently deployed LiveCycle EAR and WAR files that are
configured for the current production system that you are planning to upgrade.
3. Undeploy the following LiveCycle Policy Server 7.0.2 components:
●
asn1.jar
●
jsafe.jar
●
jsafeJCE.jar
●
edc-server-spi.jar
●
edc-server.ear
4. Remove the dom*.jar files from the [appserver root]/java/jre/lib/endorsed directory.
5. Uninstall the previous version of LiveCycle products by using the uninstaller program. (See
“Uninstalling LiveCycle Products” in the relevant Installing and Configuring LiveCycle guide.)
6. Install LiveCycle Policy Server 7.2 to a new (non-default) directory (for example, C:\Adobe\LiveCycle72\
or /opt/Adobe/livecycle72/). Follow the instructions in “Installing LiveCycle Products” in the Installing
and Configuring LiveCycle Security Products guide.
Note: If you are installing or upgrading multiple LiveCycle 7.2 products, be sure to install them to the
same [LiveCycle72 root] directory.
7. Deploy LiveCycle Policy Server 7.2. (See the chapter about manually deploying to the application
server in the Installing and Configuring LiveCycle Security Products guide for your application server.)
8. Run Configuration Manager to reinitialize the database. Select Custom Configuration Wizard, and
then select Bootstrap database. (See “Initializing the Database” in the Installing and Configuring
LiveCycle Security Products guide.)
Note: Initializing the database is necessary to add new table columns to the database schema.
Initializing the database does not alter existing data.
9. Configure various run-time settings for LiveCycle Policy Server. (See the “Post-deployment” section of
the Installing and Configuring LiveCycle Security Products guide.)
Note: You can verify your installation and configuration by using the samples available at
www.adobe.com/devnet/livecycle/samples.html.
G
Enhancing Server Performance
This appendix provides general tips that you can use to improve server performance when using LiveCycle
products.
Optimizing inline documents and impact on JVM memory
If you are typically processing documents of a relatively small size, you can improve the performance
associated with the document transfer speed and storage space by implementing the following LiveCycle
product configurations:
●
Increase the maximum inline size for LiveCycle products so that it is larger than the size of most
documents.
●
For processing larger files, specify storage directories that are located on a high-speed disk system or a
RAM disk.
The default maximum inline size and the storage directories (the Adobe LiveCycle products temporary file
directory and the Global storage directory) are properties of the Data Manager Module. You can configure
the Data Manager Module using Configuration Manager. (See “Performing a custom configuration” on
page 53.)
Note: The default maximum inline size is 65536 bytes.
Document size and maximum inline size
When a document that is sent for processing by LiveCycle products is less than or equal to the maximum
inline size, the document is stored on the server inline and the document is serialized as an Adobe
Document object. Storing documents inline can have significant performance benefits. However, if you are
using LiveCycle Workflow, the content may also be stored in the database for tracking purposes, and so
increasing the maximum inline size might affect the database size.
A document that is larger than the maximum inline size is stored on the local file system (in the storage
directories specified using Configuration Manager), and the Adobe Document object that is transferred to
and from the server is only a pointer to that file.
When document content is inlined (that is, less than the maximum inline size), the content is stored in the
database (as part of the Document's serialization payload). So, increasing the maximum inline size might
affect the database size.
JVM maximum heap size
An increase in the maximum inline size requires more memory for storing the serialized documents and so
generally also requires an increase in the JVM maximum heap size. The maximum JVM heap size should
not exceed 2GB.
A heavily-loaded system that is processing a large number of documents can rapidly saturate the JVM
heap memory. To avoid an OutOfMemoryError, the JVM maximum heap size must be increased by an
amount corresponding to the size of the inline documents multiplied by the number of documents that
are typically executed at any given time.
215
Adobe LiveCycle
Enhancing Server Performance
Installing and Configuring LiveCycle for WebSphere
Increase the maximum memory allocated to the JVM
216
JVM maximum heap size increase = (inline documents size) x (average number of documents processed)
Example G.1
Calculating the JVM maximum heap size
In this example, the current JVM maximum heap is set to 512 MB and the maximum inline size is 64 KB. The
server needs to be configured for the scenario where 10 jobs are run simultaneously, and each job has 9
input files and 1 result file (a total of 10 files per job, and 100 files processed simultaneously). All of the files
are under 512 KB in size.
To store all of the files inline, the maximum inline size must be set to at least 512 KB.
The required increase in the JVM maximum heap size is calculated using the following equation:
(512 KB) x (100) = 51200 KB, or 512 MB
The JVM maximum heap size must be increased by 512 MB for a total of 1GB.
Considering heap fragmentation
Setting the size of inline documents to large values raises the risk of an OutOfMemoryError on systems
that are prone to heap fragmentation. To store a document inline, there must be sufficient contiguous
space in the JVM heap memory. Some operating systems, JVMs, and garbage collection algorithms are
prone to heap fragmentation. Fragmentation decreases the amount of contiguous heap space, and can
lead to an OutOfMemoryError even when sufficient total free space exists.
For example, previous operations on the application server have left the JVM heap in a fragmented state,
and the garbage collector is unable to compact the heap sufficiently to regain large blocks of free space.
An OutOfMemoryError can occur even though the JVM maximum heap size has been adjusted for an
increase in maximum inline size.
To account for heap fragmentation, the inline document size must not be set higher than 0.1% of the total
heap size. For example, a JVM maximum heap size of 512 MB can support a maximum inline size of 512 MB
x 0.001 = 0.512 MB, or 512 KB.
Increase the maximum memory allocated to the JVM
This section applies to WebSphere only.
If you are running the LCM or trying to generate EJB deploy code using the command line utility,
ejbdeploy, and an OutOfMemory error occurs, you will have to increase the amount of memory allocated
to the JVM.
➤ To increase the maximum memory allocated to the JVM
1. Edit the ejbdeploy script in the {WAS_install_root}/deploytool/itp/ directory:
●
(Windows) ejbdeploy.bat
●
(Linux) ejbdeploy.sh
Adobe LiveCycle
Enhancing Server Performance
Installing and Configuring LiveCycle for WebSphere
Cleaning up temporary files in the Global storage directory
217
2. Find the -Xmx256M parameter and change it to a higher value such as -Xmx1024M.
3. Save the file.
4. Run ejbdeploy or restart the LCM.
Cleaning up temporary files in the Global storage directory
When a workflow process is executed, temporary files are placed in the Global storage directory, but are
not deleted when the process is complete. These files are placed under subdirectories with the name,
Session[NNNN], where NNNN is the workflow process ID. To prevent running out of disk space, you must
regularly remove the Session directories associated with fully completed processes.
If the Global storage directory is not set explicitly in Configuration Manager, the default location of the
Global storage directory is [TempDir]/AdobeDocumentStorage/global. If [TempDir] is also not specified by
the user in Configuration Manager, the default location is java.io.tmpdir.
DB2 configuration settings
If you are running LiveCycle Form Manager with a DB2 database and the computer stops responding,
check the server log files for deadlock-related messages. If you see such messages in the log files, change
your DB2 configuration parameters. Set the LOCKTIMEOUT parameter to 15, and double the values for the
APPLHEAPSZ, STMTHEAP, and SORTHEAP parameters. You must then restart the database and application
server.
Improving Windows Server Performance with LDAP
Using connection pooling on the search connection can decrease the number of ports need by as much as
50%, since that connection always uses the same credentials for a given domain, and the context and
related objects are closed explicitly.
➤ To configure your Windows Server for connection pooling:
1. 1. Start the registry editor by clicking Start > Run and in the Open box type regedit and click OK.
2. Navigate 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, you can add it by selecting Edit > New > DWORD Value from the menu bar.
4. In the name box, type TcpTimedWaitDelay.
Note: If you do not see the a flashing cursor and New Value # inside the box, right-click inside the
right panel, select Rename from the menu, then in the name box, type TcpTimedWaitDelay.
Adobe LiveCycle
Enhancing Server Performance
Installing and Configuring LiveCycle for WebSphere
Improving Windows Server Performance with LDAP
218
5. Repeat this step 4 for the following value names: MaxUserPort, MaxHashTableSize, and
MaxFreeTcbs.
6. Double-click inside the right pane to set the TcpTimedWaitDelay value. Under Base, select Decimal,
and in the Value box, type 30.
7. Double-click inside the right pane to set the MaxUserPort value. Under Base, select Decimal, and in
the Value box, type 65534.
8. Double-click inside the right pane to set the MaxHashTableSize value. Under Base, select Decimal,
and in the Value box, type 65536.
9. 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 might occur if you modify the registry incorrectly by using Registry Editor or
by using another method. These problems might require that you reinstall your operating
system. Modify the registry at your own risk.
Index
A
accessing
Administrator 66
BAM Workbench and BAM Dashboard 164
Installation Verification Sample application 68
LiveCycle Form Manager end-user pages 71
repository 189
User Management 67
WebSphere Administrative Console 14
action properties, Assembler QPAC 182
activation specifications, WebSphere, setting up 114
adding
fonts for LiveCycle Forms to use 77
queues to embedded JMS server 87, 109
topics to embedded JMS server 110
Adobe Administrator, accessing 66
Adobe Form Server, upgrading to LiveCycle Forms 194
Adobe LiveCycle Assembler
deployment, verifying 67
installing 26
invoking 180
jobs, submitting for processing 188
server transaction time-out, configuring 81, 104
upgrading 200
Adobe LiveCycle database
about initializing 13
connecting WebSphere to 82, 104
creating 30
initializing 126
Adobe LiveCycle Document Security
upgrading 208
Adobe LiveCycle Form Manager
accessing end-user pages 71
installing 26
JMS resource configuration 93
JVM argument configuration 104
upgrading 198
using WebDAV with 189
WebSphere MQ, installing 39
Adobe LiveCycle Forms
deployment, verifying 68, 119, 124
installing 26
PDF/A compliancy 190
upgrading 194
Adobe LiveCycle PDF Generator
additional requirements for 19
conversion time-out, setting 73
installing 23
JMS resources configuration 93
post-deployment 72
server transaction time-out, configuring 81, 104
upgrading 205
WebSphere MQ, installing 39
XA transactions, enabling 64
Adobe LiveCycle Policy Server
upgrading 213
Adobe LiveCycle Print
deployment, verifying 69
installing 28
upgrading 194
Adobe LiveCycle products
automatic deployment 60
configuring and assembling 54
developing forms for 189
documentation resources 11
information updates 12
manual deployment 116, 121
manual installation 23
upgrading to 7.2 or 7.2.1 192
verifying deployment 63
Adobe LiveCycle Reader Extensions
upgrading 210
Adobe LiveCycle Workflow
configuring for BAM Server 164
installing 26
invoking LiveCycle Assembler through 180
JMS resource configuration 93
JVM argument configuration 104
metadata definitions, importing 166
upgrading 200
web server configuration files, updating 39, 81
WebSphere configuration for BAM Server 139, 151
WebSphere MQ, installing 39
Adobe LiveCycle Workflow Business Activity Monitor. See BAM
entries
Adobe LiveCycle Workflow Designer
configuration file, modifying 173
installing 172
JNDI and HTTP ports 173
uninstalling 174
upgrading 203
Adobe PDF Printer, setting as default 72
Adobe User Management
accessing 67
configuring with LDAP 129
adobe-Assembler7.ear file, deploying 118, 123
adobe-FontManager.ear file, deploying 117, 122
adobe-printSubmitter.ear file 69
application servers
configuring 57, 80, 103
connecting to 173
instance on WebSphere, creating 36
settings, verifying 60
supported 17
updating 193
applications, starting in WebSphere 119, 124
arguments, JVM, configuring 81, 104, 114
219
Adobe LiveCycle
Index
Installing and Configuring LiveCycle for WebSphere
Assembler QPAC
about 181
creating workflow process 182
assembling LiveCycle products 54
authentication
alias, JAAS, creating 141, 153
J2C, configuring 85, 96
using LDAP 129, 167
using SSL credential 132
automatic installation
about 15
checklist 20
using to upgrade LiveCycle products 193
B
BAM Dashboard, accessing 164
BAM metadata database
configuring connection to 141, 152
creating 139, 151
DB2 environment variables, creating 139, 151
BAM Server
about upgrade utility 204
configuring 165
configuring LiveCycle Workflow for 164
configuring WebSphere for 140, 152
deploying to WebSphere 148, 160
EAR file, predeploying/deploying 148, 160
synchronizing with LDAP server 168, 171
upgrading for LiveCycle Workflow 203
user account 139, 151
BAM Workbench, accessing 164
bus members, configuring 109
buses, configuring 109
Business Activity Monitor. See BAM entries
C
checking. See verifying
checklists 20
classloader, WebSphere, configuring 38
configuration checklists 20
configuration files
LiveCycle Workflow Designer, modifying 173
web server, updating 39, 81
Configuration Manager
about 47
and directory setting 217
using during upgrade process 193
using for custom configuration 53
using for typical configuration 49
using to configure LiveCycle products 76
configuration properties, retrieving for upgrading 195
configuring
See also installing
about 13
application server 57, 80, 103
BAM Server 165
data sources for WebSphere 82, 104
DB2 database for concurrent usage 32
default JDBC agent 156
220
embedded messaging 108
JMS resources for WebSphere 86, 108
JMS resources for WebSphere MQ 93
job sources 72
LiveCycle products 54
LiveCycle products for deployment 76
LiveCycle Workflow for BAM Server 164
server transaction time-out 81, 104
shared library files 37
SSL on WebSphere 131, 134
User Management with LDAP 129
watched folders 184
WebSphere connection time-out 134
WebSphere for BAM Server 140, 152
WebSphere MQ 42
WebSphere MQ for Watched Folder 100
WebSphere parameters 145, 157
WebSphere to use local OS registry 134
Windows Server for connection pooling 217
workflow process with Assembler QPAC 182
connecting
to application servers 173
WebSphere to LiveCycle database 82, 104
connection factories
enabling XA transactions for 64
WebSphere, creating 87, 96, 110
connection pools, configuring 97, 99
connection time-out, WebSphere, configuring 134
connection, BAM metadata database, configuring 141, 152
conventions, path name 10
conversion time-out, LiveCycle PDF Generator, setting 73
copying
EAR files 117, 122
shared library file 37
CORBA fix pack, installing 35
CORBA time-out, disabling 80, 103
CQIntegration.ear file, deploying 149, 162
CreateDocumentList QPAC 181
creating
application server instance on WebSphere 36
data sources for BAM metadata database 142, 154
data sources on WebSphere 82, 104
databases 30, 139, 151
default JDBC agent 156
endorsed directory 37
JAAS authentication alias 141, 153
JDBC provider 141, 153
JobConfig.xml file 185
local user account for WebSphere 131
SSL credential 132
virtual host alias 147
watched folders 184
WebSphere MQ queue destinations 93
WebSphere MQ topic destinations 95
credentials, SSL, creating 132
D
data sources
creating for BAM metadata database 142, 154
Adobe LiveCycle
Index
Installing and Configuring LiveCycle
creating on WebSphere 82, 104
databases
connection to, testing 143, 145, 156
creating 30, 139, 151
drivers supported 18
drivers, installing for BAM Server 140, 152
drivers, installing to application server 44
initializing 62, 126
operating system supported 18, 175
supported 17
DB2 database
configuration settings 217
configuring for concurrent usage 32
creating 31
data source, creating on WebSphere 83, 106
driver, installing 45
environment variables, creating 139, 151
DDX files
pattern matching 187
workflow use of 181
deploying
about 13, 116, 121
BAM Server to WebSphere 148, 160
Installation Verification sample application 119, 124
LiveCycle Assembler sample 67
LiveCycle products automatically 60
multiple LiveCycle products 16
PrintIVS web application 69
to WebSphere 117, 122
deployment
checklists 20
configuring LiveCycle products for 76
verifying 63
directories
endorsed, creating 37
Global storage 55, 77, 217
WebSphere naming convention 116, 121
document transfer performance, increasing 215
documentation resources 11
DocumentServicesLibrary.jar file, configuring 37
driver file, creating registry entries for 34
dynamic DDX files 181
dynamic forms, button support for 190
E
EAR files
deployable 116, 122
deploying 117, 122
predeploying/deploying 148, 160
uninstalling 64
embedded messaging, configuring 108
endorsed directory, creating 37
environment variables, DB2, creating 139, 151
error logging, Assembler QPAC workflow 183
error logs, viewing 29
F
fail modes, Assembler QPAC workflow 183
files
221
accessing using WebDAV clients 189
See also DDX files, EAR files, JAR files, library files, log files, and
product files
fonts
bundled 179
embedding in PDF/A-compliant forms 190
installing for converted documents 72
selecting for LiveCycle Forms to use 77
Form Server Module API Print application, running 71
forms, designing 189
G
Global storage directory
about 55, 77
temporary files 217
H
hardware requirements 19
host alias, virtual, creating 147
HTTP ports, LiveCycle Workflow Designer 173
I
importing LiveCycle Workflow metadata definitions 166
initializing database 13, 62, 126
installation
checklists 20
methods for 15
Installation and Verification sample, deploying 119, 124
installing
See also configuring
about 13
database drivers for BAM Server 140, 152
database drivers to application server 44
DB2 driver 45
fonts used in converted documents 72
JTA stored procedures 33
LiveCycle products for manual deployment 26
LiveCycle Workflow Designer 172
multiple LiveCycle products 16
using manual method 23
WebSphere 35
WebSphere MQ 39
J
J2C authentication information, configuring 85, 96
JAAS authentication alias, creating 141, 153
JAR files
endorsed directory 37
LiveCycle, copying 37
JDBC agent, creating/configuring default 156
JDBC information, configuring 85
JDBC provider, creating 141, 153
JDK support 17
JMS resources
Activation Specification, setting up 162
configuring for WebSphere 108
configuring for WebSphere MQ 93
configuring with embedded messaging 86
Adobe LiveCycle
Index
Installing and Configuring LiveCycle
JNDI ports, LiveCycle Workflow Designer 173
job sources, configuring 72
JobConfig.xml file, creating for watched folders 185
JTA stored procedures, installing 33
JVM
arguments, configuring 81, 104, 114
heap size, maximum, increasing 215
parameters, WebSphere 147, 159
system logs, viewing 15
L
LCM.ear file, deploying 118, 123
LDAP
configuring for BAM Server 167
configuring User Management with 129
improving Windows Server performance with 217
server support 18
library files, shared, configuring 37
listener ports, WebSphere, configuring 90, 99
listener service, starting 43
LiveCycle. See Adobe LiveCycle
LiveCycle.ear file, deploying 117, 123
local OS registry 134
log files, viewing 15, 29, 120, 125
M
manual installation
about 15
checklist 21
running 23
message listener service, starting 43
multiple LiveCycle products, installing and deploying 16
N
naming conventions, file path 10
O
operating systems
database support 18, 175
supported 17
Oracle database
creating 30
creating data source on WebSphere 105
data source, creating on WebSphere 82
driver, installing 44
OS registry, local 134
P
parameters
WebSphere JVM, configuring 147, 159
WebSphere, configuring 145, 157
PDF files, preparing 187
PDF/A compliant forms, embedding fonts in 190
pdfg-all.ear file, deploying 118, 123
pdfg-ps-all.ear file, deploying 118, 123
performance, Windows Server, improving 217
Print Submitter application, running 70
222
PrintExample BAT and SH files 71
PrintIVS web application, deploying and running 69
processing LiveCycle Assembler jobs 188
product files
removing 191
profile, creating on WebSphere 36
Q
QPACs
creating 12
deploying 181
queue connection factories, WebSphere, creating 87, 96, 110
queue destinations, WebSphere, creating 89, 93, 112
queues, adding to embedded JMS server 87, 109
R
registry entries, creating for driver file 34
registry, OS, local 134
removing. See uninstalling
repository, accessing using WebDAV clients 189
role mapping, LDAP, configuring 170
S
samples
application, deploying 119, 124
data files 70
form designs 70
Form Server Module API Print, running 71
Installation Verification Sample, accessing 68
LiveCycle Assembler, deploying 67
Print Submitter, running 70
PrintIVS web application, running 69
server transaction time-out, configuring 81, 104
session pools, configuring 97, 99
shared library files, configuring 37
SMTP settings, configuring for BAM Server 165
SOAP
connection, time-out, increasing 38
port, establishing for WebSphere 49
software
client, publishing files from 189
combinations for installation 18
requirements 16
SQL Server
creating data source on WebSphere 107
data source, creating on WebSphere 85
database drivers, installing 140, 152
database, creating 33
SSL
configuring on WebSphere 131, 134
credential, creating 132
starting
Administrator 66
applications in WebSphere 119, 124
installation program 26
User Management 67
WebSphere 14
WebSphere MQ listener service 43
Adobe LiveCycle
Index
Installing and Configuring LiveCycle
static DDX files 181
stopping WebSphere 14
submitter.bat file 70
submitting LiveCycle Assembler jobs for processing 188
synchronizing BAM Server with LDAP server 168, 171
system requirements 16
223
uninstalling
EAR files 64
LiveCycle Workflow Designer 174
product files 191
upgrading LiveCycle products 16, 192
user accounts
BAM Server 139, 151
local, creating for WebSphere 131
User Management. See Adobe User Management
user mapping, LDAP, configuring 169
web server configuration files, updating 39, 81
WebDAV clients 189
WebSphere 107
Administrative Console, accessing 14
configuring 5.1.1.5 manually 80
configuring 6.0.2.9 manually 103
configuring connection time-out 134
configuring for BAM Server 140, 152
configuring JMS resources for 86, 108
configuring SSL on 131, 134
configuring to use local OS registry 134
connecting to LiveCycle database 82, 104
deployable components 116, 122
deploying BAM Server to 148, 160
deploying to 117, 122
home directory name 116, 121
installing 35
JVM parameters, configuring 147, 159
log files, viewing 120, 125
parameters, configuring 145, 157
SOAP port, establishing 49
starting and stopping 14
starting applications in 119, 124
WebSphere MQ
configuring 42
configuring JMS resources for 93
installing 39
WebSphere Pluggable Client 172
workflow processes, creating 181
V
X
validating. See verifying
variables, Assembler QPAC 182
verifying
application server settings 60
BAM metadata database connection 143, 145, 156
LiveCycle Assembler deployment 67
LiveCycle Forms deployment 68, 119, 124
LiveCycle Print deployment 69
LiveCycle product deployment 63
WebSphere MQ configuration 101
viewing
application server status 14
JVM system log files 15
log files 29, 120, 125
XA transactions
enabling for LiveCycle PDF Generator 64
enabling for Windows Server 34
XML file, job configuration 185
T
testing. See verifying
time-out, SOAP connection, increasing 38
topic connection factories, WebSphere, creating 88, 98, 111
topic destinations, WebSphere, creating 89, 95, 113
topics, adding to embedded JMS server 110
transaction time-out, server, configuring 81, 104
turnkey installation
using to upgrade LiveCycle products 193
U
W
Watched Folder
about installation of 16
configuring JMS resources for 92
configuring WebSphere MQ for 100
installing 29
invoking LiveCycle Assembler with 180
upgrading 200
WebSphere MQ, installing 39
watched folders
creating and configuring 184
creating JobConfig.xml file for 185
web browser support 17
Was this manual useful for you? yes no
Thank you for your participation!

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

Download PDF

advertisement