Adobe® LiveCycle™ 7.2 Installing and Configuring LiveCycle for JBoss® for Microsoft® Windows® and Linux®
Edition 1.1, October 2006
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.
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 bmc@clapper.org.
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/).
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.
What’s in this guide? ..................................................................................................................................................................... 8
Who should read this guide? ..................................................................................................................................................... 8
Conventions used in this guide................................................................................................................................................. 8
Related documentation ............................................................................................................................................................... 9
About Watched Folder installation........................................................................................................................................13
System requirements..................................................................................................................................................................13
Platform and software combinations.............................................................................................................................15
Additional requirements for LiveCycle PDF Generator Elements and
LiveCycle PDF Generator Professional.....................................................................................................................15
Additional requirements for LiveCycle PDF Generator for PostScript................................................................16
Installation, configuration, and deployment checklists.................................................................................................16
Turnkey installation and deployment checklist..........................................................................................................16
Manual installation and deployment checklist...........................................................................................................17
2Installing LiveCycle Products Using the Turnkey Installation ...............................................20
Running the turnkey installation............................................................................................................................................20
Accessing User Management ..................................................................................................................................................27
Verifying the LiveCycle Assembler deployment.........................................................................................................27
LiveCycle Forms post-deployment tasks.............................................................................................................................28
Verifying the LiveCycle Forms deployment .................................................................................................................28
Deploying and running the PrintIVS web application..............................................................................................29
Running the Print Submitter application......................................................................................................................29
Running the Form Server Module API Print application..........................................................................................30
LiveCycle Form Manager post-deployment tasks............................................................................................................31
Accessing the LiveCycle Form Manager end-user pages........................................................................................31
4
Adobe LiveCycleContents
Installing and Configuring LiveCycle for JBoss 5
3Post-deployment (Continued)
LiveCycle PDF Generator post-deployment tasks............................................................................................................31
Setting up job sources .........................................................................................................................................................31
Setting Adobe PDF Printer as the default printer ...................................................................................................... 31
Installing LiveCycle PDF Generator........................................................................................................................................36
Viewing the error log ..................................................................................................................................................................41
5Preparing Your Environment.................................................................................................... 42
Creating the database ................................................................................................................................................................42
Creating a MySQL database ...............................................................................................................................................42
Creating an Oracle database..............................................................................................................................................43
Creating a DB2 database.....................................................................................................................................................44
Configuring a DB2 database for concurrent usage...................................................................................................45
Creating a SQL Server database........................................................................................................................................46
Creating a JMS database on SQL Server ........................................................................................................................46
Preparing the application server ............................................................................................................................................48
Starting and stopping JBoss..................................................................................................................................................... 53
Modifying the JBoss configuration files...............................................................................................................................54
Configuring JBoss for Watched Folder.................................................................................................................................58
Connecting JBoss for LiveCycle products to the LiveCycle database .......................................................................58
Configuring the MySQL data source...............................................................................................................................58
Configuring the Oracle data source................................................................................................................................59
Configuring the DB2 data source.....................................................................................................................................60
Configuring the SQL Server data source .......................................................................................................................61
8Manually Deploying to JBoss....................................................................................................63
About deploying LiveCycle products....................................................................................................................................63
Summary of deployable components............................................................................................................................63
Deploying to JBoss.......................................................................................................................................................................64
Applying the connection pool patch for Watched Folder ............................................................................................65
9Initializing the Database ........................................................................................................... 66
10 Configuring LiveCycle Products to Access LDAP .................................................................... 68
Configuring LiveCycle products with LDAP .......................................................................................................................68
Configuring LiveCycle products with LDAPS.....................................................................................................................69
Adobe LiveCycleContents
Installing and Configuring LiveCycle for JBoss 6
Part III: Post-Deployment Configuration
11 Configuring SSL on JBoss.......................................................................................................... 71
Creating an SSL Credential ....................................................................................................................................................... 71
Configuring SSL on JBoss .........................................................................................................................................................73
12 Manually Configuring JBoss for BAM Server...........................................................................76
Installing JBoss Application Server ........................................................................................................................................76
Creating the BAM metadata database .................................................................................................................................76
User accounts ..........................................................................................................................................................................76
Configuring JBoss for BAM Server..........................................................................................................................................77
Installing database drivers on JBoss for BAM Server.................................................................................................77
Connecting JBoss to the BAM metadata database....................................................................................................78
Connecting JBoss for BAM Server to the LiveCycle database................................................................................80
Customizing port numbers ................................................................................................................................................86
Deploying BAM Server ...............................................................................................................................................................87
Part VI: Additional LiveCycle Workflow Configuration
13 Getting Started with BAM Server .............................................................................................89
Configuring LiveCycle Workflow Server for BAM Server................................................................................................89
Accessing BAM Workbench and BAM Dashboard ..........................................................................................................90
Configuring BAM Server ............................................................................................................................................................90
Configuring the SMTP settings .........................................................................................................................................90
Configuring LDAP settings for BAM Server ..................................................................................................................92
ASupported Platform and Software Combinations ................................................................100
BFonts Installed with the Font Manager Module ....................................................................103
CInvoking LiveCycle Assembler Using LiveCycle Workflow and Watched Folder ...............104
Summary of tasks ...................................................................................................................................................................... 104
Deploying QPACs and creating a workflow process.................................................................................................... 105
Using dynamic or static DDX files................................................................................................................................. 105
Configuring an Assembler QPAC in a workflow process...................................................................................... 106
Creating and configuring a watched folder .................................................................................................................... 108
Creating a JobConfig.xml file................................................................................................................................................ 109
Preparing PDF and DDX files................................................................................................................................................. 112
Submitting the LiveCycle Assembler job for processing............................................................................................ 112
Adobe LiveCycleContents
Installing and Configuring LiveCycle for JBoss 7
DDeveloping Forms for LiveCycle.............................................................................................113
Publishing files from client software.................................................................................................................................. 113
Designing forms for LiveCycle products........................................................................................................................... 113
Using dynamic forms with LiveCycle products........................................................................................................ 114
Embedding fonts in PDF/A-compliant forms ........................................................................................................... 114
Removing the product files from a turnkey installation ............................................................................................. 115
Removing the product files from a manual installation.............................................................................................. 116
FEnhancing Server Performance .............................................................................................. 117
Optimizing inline documents and impact on JVM memory...................................................................................... 117
Cleaning up temporary files in the Global storage directory.................................................................................... 118
Improving Windows Server Performance with LDAP .................................................................................................. 119
Index .........................................................................................................................................120
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® and Linux® and how to deploy the products to a JBoss® 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 and Windows 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.
NameDefault valueDescription
[LiveCycle root]Windows:
C:\Adobe\LiveCycle\
Linux:
/opt/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).
8
Adobe LiveCyclePreface
Installing and Configuring LiveCycle for JBoss Related documentation 9
The directories where
product-specific directories and files
(such as documentation, uninstall
files, samples, and license
information) are located.
The home directory of the
application server that runs the
LiveCycle products.
[jboss bam root]Directory where you have installed JBoss.The home directory of the instance of
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 JBoss. 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.
For information aboutSee
General information about a product and
how it integrates with other Adobe products
The product architecture, how to use the APIs,
and how to develop custom applications for
use with the products
JBoss that runs Business Activity
Monitor (BAM) Server.
Overview guides for each product
The developer guides for each product. For example,
Developing Custom Application for LiveCycle Workflow
or Developing Applications for LiveCycle Assembler.
Adobe LiveCyclePreface
Installing and Configuring LiveCycle for JBoss Updated LiveCycle product information 10
For information aboutSee
The EJB API, including descriptions and
explanations of its classes and methods.
The syntax for the Document Description XML
(DDX) grammar and related XML grammars
supported by LiveCycle Assembler
Setting up and administering Watched FoldersWatched Folder Administration Help
Managing access to the Adobe Administrator
user interface
How to use LiveCycle Workflow DesignerCreating 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
Other services and products that integrate
with LiveCycle products
Patch updates, technical notes, and additional
information on this product version
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.
Document Description XML Reference
User Management Administration Help
The QPAC guides, available with the LiveCycle
Workflow SDK. For example Using LiveCycle Assembler QPACs or Using LiveCycle Forms QPACs.
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:
This chapter describes how to prepare your system for installing LiveCycle products:
● “About the installation, configuration, and deployment process” on page 11
● “Methods for installing, configuring, and deploying LiveCycle products” on page 12
● “Installing and deploying multiple LiveCycle products” on page 12
● “System requirements” on page 13
● “Installation, configuration, and deployment checklists” on page 16
● “Updated LiveCycle product information” on page 18
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:
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);
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 35
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 49.) 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 JBoss 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 66
.)
.)
11
Adobe LiveCycleBefore You Install
Installing and Configuring LiveCycle for JBoss Methods for installing, configuring, and deploying LiveCycle products 12
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:
Turnkey: (Windows/JBoss/MySQL) The turnkey method lets you install the files, and then run
Configuration Manager to configure the EAR file and other components and automatically performs
the following tasks:
● Install and configure the JBoss Application Server and MySQL database.
● Assemble and deploy the products to JBoss.
● Initialize the MySQL database.
The turnkey method does not configure SSL. (See “Turnkey installation and deployment checklist” on
page 16 or “Installing LiveCycle Products Using the Turnkey Installation” on page 20.)
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 17
.)
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.
Note: To install multiple products in the LiveCycle 7.2 product suite, install in the following order:
● LiveCycle PDF Generator
● LiveCycle Assembler, LiveCycle Forms, LiveCycle Form Manager, LiveCycle Print,
For detailed documentation on installing multiple products, refer to the Knowledge Center article
at: www.adobe.com/support/products/enterprise/knowledgecenter/c4811.pdf
Upgrading LiveCycle products
For the latest information on upgrading LiveCycle products, refer to the Knowledge Center article at:
Installing and Configuring LiveCycle for JBoss About Watched Folder installation 13
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 31
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.
Note: If you are running the turnkey installation and configuration, the only prerequisite software
requirement is the Java™ Development Kit (JDK) and a supported web browser. The turnkey
method installs and configures JBoss (which includes the Apache web server) and a MySQL
database.
The JDK is not a prerequisite for LiveCycle PDF Generator. If the JDK is not already installed, the
turnkey installer will install it.
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 100
Required softwareSupported version
Operating system● Microsoft Windows Server™ 2003 Enterprise Edition or Standard
.
Edition
● (LiveCycle Workflow Designer) Microsoft Windows XP Service
Pack 2
● SUSE™ Linux Enterprise Server 9.0 i386 (32-bit)
● Red Hat® Linux Advanced Server 2.1 or 3.0
Note: LiveCycle PDF Generator Elements and
LiveCycle PDF Generator Professional are only supported on
Microsoft Windows Server 2003.
Adobe LiveCycleBefore You Install
Installing and Configuring LiveCycle for JBoss Supported software 14
Required softwareSupported version
Application server
Web browser
JDK
● JBoss Application Server 3.2.5
● JBoss Application Server 3.2.6 (Applicable only for BAM Server,
which is a component of LiveCycle Workflow Server)
Note: Your application server must have an active Internet connection
to access LiveCycle Administrator.
● 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.
● J2SDK version 1.4.2_04 or later version of the 1.4.2 release (version
1.4.2_10 is not supported)
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
● Microsoft SQL Server 2000 SP 3
● MySQL 4.1
● (Turnkey) HSQLDB 1.7.1 used as the JBoss JMS database (HSQLDB
1.7.1 is packaged with JBoss 3.2.5)
● Oracle 9i
● Oracle 10g
Database driver
● IBM DB2 - db2jcc.jar and db2jcc_license_cu.jar
● Microsoft SQL Server 2000 - msbase.jar, mssqlserver.jar, and
msutil.jar
● MySQL - mysql-connector-java-3.0.15-ga-bin.jar
● Microsoft SQL Server 2000 for BAM - msbase.jar, mssqlserver.jar,
and msutil.jar
● Oracle - ojdbc14.jar, version 10.2.0.2
LDAP server● Sun ONE 5.1, 5.2
● Microsoft Active Directory 2000
● Microsoft Active Directory 2003
● Novell® eDirectory 8.7
Note: If you run the turnkey installation, you must not have instances of JBoss Application Server or the
MySQL database server running on the target computer.
Adobe LiveCycleBefore You Install
Installing and Configuring LiveCycle for JBoss Platform and software combinations 15
Platform and software combinations
This table summarizes the software combination and database combination supported for JBoss 3.2.5. For
a complete list of supported software on each operating system, see “Supported Platform and Software
Combinations” on page 100.
Note: LiveCycle PDF Generator Elements and LiveCycle PDF Generator Professional only run on the
Windows Server 2003 Enterprise Edition platform.
Operating systemDatabase
Red Hat Linux Advanced Server 3.0Microsoft SQL Server 2000 SP 3
Microsoft Windows Server 2003 Enterprise Edition or Standard
Edition
MySQL 4.1
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 systemMinimum hardware requirement
Windows Server 2003 Enterprise Edition or
Standard Edition
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.0Pentium 3 or x86 equivalent, 1GHz processor
Intel® 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.
Adobe LiveCycleBefore You Install
Installing and Configuring LiveCycle for JBoss Additional requirements for LiveCycle PDF Generator for PostScript 16
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 a turnkey 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.
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 13.
To install LiveCycle PDF Generator for PostScript on Linux, 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 turnkey 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.
Turnkey installation and deployment checklist
The following table includes the steps required for installing LiveCycle products using the turnkey method.
Perform this type of installation and configuration if you do not yet have an application server installed
and configured and you want to use JBoss, or if you want to quickly and easily get the products installed
and configured for testing or demonstration purposes.
Adobe LiveCycleBefore You Install
Installing and Configuring LiveCycle for JBoss Manual installation and deployment checklist 17
Do not use the turnkey configuration method if you plan to enable SSL. If you require SSL, perform a
manual configuration. (See “Configuring LiveCycle Products for Deployment” on page 49
Ta skTop ic
.)
Ensure that you have the required software installed
in the target environment.
Run the installation program with the turnkey option
enabled for JBoss. The product, JBoss, and MySQL are
installed and configured.
Access Administrator and User Management. “Accessing Administrator” on
Check the log file.“Viewing log files” on page 65
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.
Perform this type of installation if you are installing the product in a production environment.
Note: If you are installing multiple products, ensure that they are all installed before running
Configuration Manager to configure and deploy them.
“System requirements” on page 13
“Installing LiveCycle Products Using
the Turnkey Installation” on page 20
page 26
Ta skTop ic
Ensure that you have the required software installed
in the target environment.
Create the database to use with User Management and
install and prepare the application server.
Run the installation program.“Installing LiveCycle Products” on
Run Configuration Manager and select the Custom
Configuration Wizard. This will configure and assemble
the products.
Configure JBoss settings. A variety of settings must be
configured.
Deploy the product deployment files to the application
server.
Run Configuration Manager to initialize the database.“Initializing the Database” on
Access Administrator and User Management.“Accessing Administrator” on
“System requirements” on page 13
“Preparing Your Environment” on
page 42
page 35
“Configuring LiveCycle Products for
Deployment” on page 49
“Manually Configuring JBoss” on
page 53
“Manually Deploying to JBoss” on
page 63
page 66
page 26
Adobe LiveCycleBefore You Install
Installing and Configuring LiveCycle for JBoss Updated LiveCycle product information 18
Ta skTop ic
Configure LDAP access.“Configuring LiveCycle Products to
Access LDAP” on page 68
Configure SSL on the application server, if required.“Configuring SSL on JBoss” on
page 73
(LiveCycle Workflow) Create the BAM metadata database
and configure the application server for BAM Server.
Check the log file.“Viewing log files” on page 65
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:
“Manually Configuring JBoss for
BAM Server” on page 76
Part I: Turnkey Installation
This section of the guide describes how to complete a turnkey installation of LiveCycle products
For information on the manual configuration and deployment of the products, see “Manual Installation,
Configuration and Deployment” on page 34.
19
Installing LiveCycle Products Using the
2
Tur nk e y In st a ll at io n
This chapter describes how to install LiveCycle products using the turnkey method. The turnkey
installation automatically performs all of the tasks required to install and configure LiveCycle products on
a JBoss Application Server running on Windows.
The turnkey installation performs the following tasks:
● Installs the product files
● Installs a preconfigured version of JBoss 3.2.5 (with Apache web server embedded)
● Installs a preconfigured version of MySQL 4.1
● (LiveCycle PDF Generator) Installs a JDK if not present on the target system
● Starts Configuration Manager
● Configures and assembles the LiveCycle product components
● Deploys all of the required components to JBoss
● Initializes MySQL when installing LiveCycle products that require User Management
Running the turnkey installation
Before running the turnkey installation, ensure that the environment where you are installing and
deploying LiveCycle products meets the system requirements. (See the note under “System requirements”
on page 13.) This includes manually installing the required version of the JDK. During the turnkey
installation, you will be prompted for the JDK root directory. The turnkey installation then installs JBoss
and MySQL automatically.
The turnkey installation specifies “localhost” as the host name, “8080” as the port for use by JBoss, and
“3306” as the port for MySQL. If JBoss and MySQL are already installed, ensure that they are not using these
ports. You cannot configure an alternative host name or port for JBoss or MySQL during the turnkey
installation and configuration process.
By default, the turnkey installation places the LiveCycle product and all of the related components and
software in the \Adobe\LiveCycle directory (referred to as [LiveCycle root]).
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: /opt/adobe/livecycle/
JBoss and MySQL are installed and run from the [LiveCycle root]/jboss and [LiveCycle root]/mysql
directories, but you can specify another directory by either typing in the path or browsing to it.
20
Adobe LiveCycleInstalling LiveCycle Products Using the Turnkey Installation
Installing and Configuring LiveCycle for JBoss Running the turnkey installation 21
The turnkey installation creates the following Windows services:
● JBoss for Adobe LiveCycle
● MySQL for Adobe LiveCycle
● (LiveCycle Workflow) JBoss for Adobe LiveCycle Workflow BAM
These services are used by Configuration Manager during the turnkey installation. The services can be
stopped and started using the Services window in the Administrative Tools area of the Windows Control
Panel.
Note: If JBoss and MySQL are already installed, you must stop their services before running the turnkey
installation.
For the turnkey installation, it is recommended that you accept the default configuration options. If you
prefer to set all of the configuration options, run the manual installation, configuration, and deployment
process. For information about the configuration options, see “Configuring LiveCycle Products for
Deployment” on page 49.
Tip: To improve the speed of the installation, disable any on-access virus scanning software for the
duration of the installation.
Use the following procedure to install all products except LiveCycle PDF Generator. (See “To run the
turnkey installation for LiveCycle PDF Generator:” on page 23)
➤ To run the turnkey installation:
1. At the root level of the installation DVD, double-click the .exe file.
2. If prompted, select a language for the installation program and click OK.
3. Click Next on the Welcome screen.
4. On the Before You Install screen, 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.
Note: Depending on the product you are installing, the next steps may appear in a different order.
7. Select JBoss, select Configure and deploy the product automatically, and then click Next.
8. Read the license information associated with installing JBoss, select I accept the terms of the license agreement, and then click Next.
9. Read the license information associated with installing MySQL, select I accept the terms of the license agreement, and then click Next.
10. If required, type the path to your JDK or click Browse to navigate to its root directory, and then click
Next.
11. Accept the default Adobe directory location 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.
Adobe LiveCycleInstalling LiveCycle Products Using the Turnkey Installation
Installing and Configuring LiveCycle for JBoss Running the turnkey installation 22
12. Review the installation details, and then click Install. A summary screen appears when the product
installation is completed.
13. On the summary screen, you have the following options:
● If you are installing only one LiveCycle product or this is the last LiveCycle product you are installing,
select Launch the Configuration Manager, and then click Finish. Proceed to step 14
● If you plan to install additional LiveCycle products, click Finish to exit the installation program and
.
run the installation programs for the additional products.
14. If prompted, select a language for Configuration Manager and click OK.
15. On the Welcome screen, click Next.
16. On the Configuration Mode screen, select Typical Configuration Wizard and click Next.
17. If prompted, on the Configuration Preferences screen, select either Use Previously Entered Values or
Revert to Default Values, and then click Next.
Note: This screen only appears if you have previously run Configuration Manager.
18. If required, on the Product Selection screen, select JBoss as the type of application server that you are
using.
19. If required, select Foundation and the products that you want to configure and deploy, and then click
Next.
20. (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.
21. On the Configuration and Assemble Products screen, click Next.
22. Review the Application Configuration and Assembly Summary details, and then click Next.
Configuration Manager configures the LiveCycle product properties using the default values and
assembles the products into the LiveCycle.ear file.
23. When the configuration and assembly is complete, click Next.
24. On the Deploy LiveCycle screen, click Next.
25. On the Deploy products summary screen, click Next.
26. In the Application Server Base URL box, type the URL that Configuration Manager can use to connect
to the application server, 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://localhost:8080).
27. On the Prepare database for LiveCycle screen, click Next.
28. On the Deployment Instructions screen, click Next.
Adobe LiveCycleInstalling LiveCycle Products Using the Turnkey Installation
Installing and Configuring LiveCycle for JBoss Running the turnkey installation 23
29. On the Database Initialization screen, click Initialize Database Now to connect your LiveCycle
products to the database, and then click Next.
30. On the Database Initialization screen, click Initialize Database Now and, when the task is complete,
click Next.
31. On the Tasks Completed screen, click Finish.
The product is now deployed to JBoss, and JBoss should be running. If JBoss is not running, you can
start the JBoss for Adobe LiveCycle service by using the Windows Service utility.
By default, the JBoss and MySQL services are installed with the “Manual” startup type. You can modify
this by selecting Start > Administrative Tools > Services, locating these services and changing them to
“Automatic”. Otherwise, when you restart your machine, you will need to start the JBoss and MySQL
services manually.
The JBoss log file (server.log) is located in the [LiveCycle root]/jboss/server/all/log directory. This file
contains information on JBoss activity and progress.
➤ To run the turnkey installation for LiveCycle PDF Generator:
1. At the root level of the installation DVD, double-click the .exe file.
2. If prompted, select a language for the installation program and click OK.
3. Click Next on the Welcome screen.
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 pre-install 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 Adobe directory location 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.
Note: If you are installing multiple LiveCycle products, they must all be installed in the same [LiveCycle
root] directory.
9. Select JBoss, select Configure and deploy the product automatically, and then click Next.
10. If required, type the path to your JDK or click Browse to navigate to its root directory, and then click
Next.
11. Read the license information associated with installing JBoss, select I accept the terms of the license agreement, and then click Next.
Adobe LiveCycleInstalling LiveCycle Products Using the Turnkey Installation
Installing and Configuring LiveCycle for JBoss Running the turnkey installation 24
12. Read the license information associated with installing MySQL, select I accept the terms of the license agreement, and then click Next.
13. (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) Enter the Microsoft Office
administrator user name and password (if installed), and then click Next.
14. (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) On the Corel WordPerfect
screen, browse to the location of the Corel WordPerfect executable file (if installed) and click Next or, if
Corel WordPerfect is not installed, click Next.
15. (LiveCycle PDF Generator Professional, LiveCycle PDF Generator Elements) On the Adobe Photoshop
screen, browse to the location of the Adobe Photoshop executable file (if not installed in the default
directory) and click Next or, if Photoshop is not installed, click Next.
16. Review the installation details, and then click Install. A summary screen appears when the product
installation is completed.
17. On the summary screen you have the following options:
● If you are installing only one LiveCycle product or this is the last LiveCycle product you are installing,
select Launch the Configuration Manager, and then click Finish. Proceed to step 18
● If you plan to install additional LiveCycle products, click Finish to exit the installation program and
.
run the installation programs for the additional products.
18. If prompted, select a language for Configuration Manager and click OK.
19. On the Welcome screen, click Next.
20. Select Typical Configuration Wizard and click Next.
21. If prompted, on the Configuration Preferences screen, select either Use last entered values or Revert
to the default values, and then click Next.
Note: This screen only appears if you have previously run Configuration Manager.
22. If required, select JBoss as the type of application server that you are using.
23. Select Foundation and the products that you want to configure and deploy, and then click Next.
24. On the Configure and Assemble Summary screen, click Next.
25. Review the configuration summary details, and then click Next. Configuration Manager configures the
LiveCycle product properties using the default values and assembles the products into the
LiveCycle.ear file and the additional pdfg-all.ear or pdfg-ps-all.ear file.
26. On the Configure and Assemble Products screen, click Next.
27. In the Application Server Base URL box, type the URL that Configuration Manager can use to connect
to the application server. 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://localhost:8080).
Adobe LiveCycleInstalling LiveCycle Products Using the Turnkey Installation
Installing and Configuring LiveCycle for JBoss Modifying LiveCycle Services 25
28. On the Deploy Products screen, click Next.
29. On the Deployment Instructions screen, click Next.
30. On the Database Initialization screen, click Initialize Database Now to connect your LiveCycle
products to the database, and then click Next.
31. On the Tasks Completed screen, click Finish.
The product is now deployed to JBoss, and JBoss should be running. If JBoss is not running, you can
start the JBoss for Adobe LiveCycle service by using the Windows Service utility.
The JBoss log file (server.log) is located in the [LiveCycle root]/jboss/server/all/log directory. This file
contains information on JBoss activity and progress.
Modifying LiveCycle Services
By default, the turnkey installation configures the JBoss for Adobe LiveCycle and MySQL for Adobe
LiveCycle services to require manual startup. If you want to set these services to start up automatically,
perform the following procedure.
2. Right-click the JBoss for Adobe LiveCycle service and click Properties.
3. From the Startup Type menu, select Automatic, and then click OK.
4. Right-click the MySQL for Adobe LiveCycle service and click Properties.
5. From the Startup Type menu, select Automatic, and then click OK.
6. (LiveCycle Workflow Business Activity Monitor) Right-click the JBoss for Adobe LiveCycle Workflow
BAM and click Properties.
7. From the Startup Type menu, select Automatic, and then click OK.
Next Step
For LiveCycle Forms and LiveCycle Assembler, you can now deploy a sample application to test the
installation and deployment.
the LiveCycle Assembler deployment” on page 27.)
You can also now access Administrator and User Management and begin developing applications for your
LiveCycle product. (See “Post-deployment” on page 26
have installed.)
(See “Verifying the LiveCycle Forms deployment” on page 28 and “Verifying
and the developer guides for the products you
3
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 26
● “Accessing User Management” on page 27
● “LiveCycle Assembler post-deployment tasks” on page 27
● “LiveCycle Forms post-deployment tasks” on page 28
● “LiveCycle Print post-deployment tasks” on page 28
● “LiveCycle Form Manager post-deployment tasks” on page 31
● “LiveCycle PDF Generator post-deployment tasks” on page 31
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 JBoss is 8080.
2. In the User Name field, type
3. After logging in, you can click Services to access the LiveCycle product Administrator pages, or
Settings to access the User Management pages.
administrator and, in the Password field, type password.
26
Adobe LiveCyclePost-deployment
Installing and Configuring LiveCycle for JBoss Accessing User Management 27
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:
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:
1. Navigate to the [LiveCycle root]/Assembler/samples/build/prebuilt directory.
2. Deploy the jboss.sample-assembler7.ear file by copying it to the [appserver root]/server/all/deploy
directory.
4. 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.)
Adobe LiveCyclePost-deployment
Installing and Configuring LiveCycle for JBoss LiveCycle Forms post-deployment tasks 28
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. Copy the FormsIVS.ear file from the [LiveCycle root]/components/forms/samples/
common/ directory to the [appserver root]/server/all/deploy directory.
2. Restart the application server.
3. 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”.
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 28.
Adobe LiveCyclePost-deployment
Installing and Configuring LiveCycle for JBoss Deploying and running the PrintIVS web application 29
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 30.)
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 and also in the
[LiveCycle root]/configurationManager/export directory after you have run Configuration Manager.
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. Copy the adobe-printSubmitter.ear file from the [LiveCycle root]/components/print/samples/
common/printsubmitter directory to the [appserver root]/server/all/deploy directory.
2. To run the sample application, type
web browser.
3. Enter the required values and click Print.
http://[host name]:[port]/PrintIVS in the URL line of a
Running the Print Submitter application
The Print Submitter application consists of the lcprint.bat (Windows) or lcprint.sh (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.
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
Adobe LiveCyclePost-deployment
Installing and Configuring LiveCycle for JBoss Running the Form Server Module API Print application 30
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.)
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 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.
Loading...
+ 93 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.