All LiveCycle ES 8.0.1 Solution Components LiveCycle Designer ES version 8.1 LiveCycle Production Print ES version 8.0 LiveCycle Data Services 2.5 Adobe Flex Builder 2.0.1 Hot Fix 2 or higher or Adobe Flex SDK 2.0.1 Hot Fix 2 or higher
If you intend to use a combination of these products you must ensure that all versions are at the same version level as on this list. Adobe does not support mixing versions from different columns.

7 of 47

LiveCycle version 7.2/7.2.2
The 7.2 final release of LiveCycle includes the following products:
LiveCycle 7.2.2 Final release.
(English, French, German & Japanese) Replaces all previous versions of LiveCycle 7.2
LiveCycle Assembler 7.2.2 * LiveCycle Forms 7.2.2 * LiveCycle Form Manager 7.2.2 * LiveCycle PDF Generator 7.2.2 * LiveCycle Workflow 7.2.2 * LiveCycle Workflow Designer 7.2.2 * LiveCycle Document Security 7.2.2 * LiveCycle Reader Extensions 7.2.2 * LiveCycle Policy Server 7.2.2 *
LiveCycle 7.2 Final release.

(English)

LiveCycle Assembler 7.2.1 LiveCycle Forms 7.2 LiveCycle Form Manager 7.2 LiveCycle PDF Generator 7.2 LiveCycle Workflow 7.2.1 LiveCycle Workflow Designer 7.2.1 LiveCycle Document Security 7.2 LiveCycle Reader Extensions 7.2 LiveCycle Policy Server 7.2
* Recommended version. If you intend to use a combination of these products you must ensure that all versions are at the same version level as on this list. Adobe does not support mixing these versions with earlier releases of LiveCycle. Adobe LiveCycle Designer 7.1 is the Designer version for use with the 7.2 and 7.2.2 releases.

8 of 47

LiveCycle ES
LiveCycle ES version 8.0.1 is the first release of the platform strategy of LiveCycle. All Solution Components are compatible at the version level
Previous LiveCycle 7 releases
The below list provides compatibility informations for LiveCycle 7.0.x and 7.1 product releases including Acrobat\Reader. For detailed compatibility informations consult documentation for each product.
Designer 7 Acrobat 7 Products Reader 7 Forms 7 PRINT 7 X X X X X X X X X X X ADSS 7 PDFG 7 X X X X X X X X X X X AWS 7
Acrobat 7 Reader 7 Designer 7 Forms 7 RES7 ADSS 7 APS 7 AWS 7 AFM 7 PDFG 7 PRINT 7 Legend
X X X X X X X X X X X X X X X X X X X X X X X X X X X X

X X X X X X X X X X

X X X X X X X N X X

X X X X X X N X

X - Fully support all features P - Partial support for some features N - No support

9 of 47

Third-party Patch Support
(version 1.1 7th December 2006) Adobe LiveCycles third party reference platforms are a specific patch level of third party infrastructure that is current during the release of each version of Adobe LiveCycle. This is documented in the product guides and the LiveCycle Software Compatibility Matrix for reference. Adobe will support urgent or recommended patches released by third party vendors upon their release assuming that they guarantee backward compatibility with infrastructure versions that Adobe LiveCycle supports. Adobe will only support the patches that are released after the reference platform patch level Adobe documents in the product guides/Compatibility matrix. In some cases Adobe will not be able to support significant third party updates that change major functionality (thereby not having good backward compatibility). For details on the supported updates please see the references below for the specific vendors product and the patch types we will support. In some circumstances beyond Adobes control, third party patches that claim backward compatibility may have negative impacts on the Adobe products or customer environments and as such Adobe recommends that customers assess the impact of any urgent patch from a third party before applying it on critical systems. Adobe will work with third parties using reasonable business efforts to resolve such issues either via the normal Adobe support programs or via the third party rectifying backward compatibility in their patch. This does not guarantee that a newly released third party patch that will be supported by Adobe shall work as documented by the vendor or with Adobe LiveCycle.
Also refer to Adobe Enterprise Support for technotes that relate to third party patches.
Supported patch definitions as defined by vendor: Operating Systems: Microsoft Windows Service Packs and Critical Updates1 IBM AIX Service Packs and PTF(s) except for RTE updates2 Sun Solaris (patchadd) Patches3 RedHat Linux Cumulative Updates4 and updates marked critical Novell SuSE Linux Cumulative recommended and Critical Security Updates Java Application Servers: IBM WebSphere Fix Packs BEA WebLogic Patches RedHat JBoss Application Server - None (JDK updates - as recommended by the application server vendor or in the case where there are a range of versions the one that Adobe certified or later) Databases: MYSQL - None

10 of 47

IBM DB2 Fix Packs and APARs Oracle Database Patch sets Microsoft SQL Server - Updates Directory Servers: SunOne Directory Server Service Packs Microsoft ActiveDirectory as part of the OS update Novell eDirectory Product Updates Content Management Systems: Documentum Fix Packs and Hot Fixes IBM Content Manager Fix Packs and iFix(s) FileNet Service Packs Web Browsers Microsoft Internet Explorer Service Packs and Updates Netscape Navigator - Patch Mozilla/FireFox Security Updates that change the double dot version5

How to determine if a configuration is supported: A configuration is supported if the infrastructure components match the software listed below for the specific version of LiveCycle you have deployed. Any patches/fix packs you have applied must also conform to the [Third-party Patch Support] section above.
* Restrictions: Any investigations into issues that arise in environments where there are unsupported infrastructure components will not be covered by the Adobe Enterprise Support Service Level Agreements (SLAs). The complexity and uncertainty in these environments may also mean that Adobe's experience and/or expertise will be limited. If the issue shows indications that it is unrelated to and/or not caused by the unsupported components, the issue will be investigated** and resolution options may include product modification (patch).***. If the issue is found to be related to/caused by the unsupported infrastructure Adobe Enterprise support will require the customer replicate the issue in a completely supported environment for continued support and potential patch creation. In this case the patch would be for the supported configuration***.
For Example (hypothetically): If a customer has implemented LiveCycle Forms ES on WebSphere 6.1.0.5/Redhat ES 4.0 on a VMWare image Adobe would provide support on the Forms/WebSphere/Redhat Linux aspects but not on items that may relate to the VMWare image specifically such as performance difference between a native Linux and a VMWare image environment.
** In situations where a customer reports an issue in an environment, Adobe Enterprise Support will proceed with the investigation in the Adobe Labs with a supported environment only. If the issue is evaluated by Enterprise Support to be related to the unsupported infrastructure support will also require that the customer replicate the issue in a supported environment. If the issue cannot be replicated in a supported environment Enterprise Support will not be able to resolve the issue. It will be up to the customer to either workaround the issue, find a resolution provided by the infrastructure vendors or move to a supported environment.
*** Adobe will only create patches for supported environments. It will be up to the customer to try the patch on the unsupported infrastructure if they wish to use it in that environment. Adobe will not build, test or document how to apply the patch on anything other then a supported environment.

Certified LC8 LDAP List Sun ONE 5.1 Sun ONE 5.2 Microsoft Active Directory 2000 Microsoft Active Directory 2003 IBM Tivoli Directory Server 6.0 Novell eDirectory 8.7.3 Email support Exchange 2000 Exchange 2003 Lotus Notes/Domino 6/7 SendMail (included with RedHat 4) Novel GroupWise 6/7

15 of 47

IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM WebSphere 6.1.0.5* (Base Edition & Network Deployment Edition) Oracle 10g JDK supplied with application server P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHZ processor

AIX 5L 5.3

BEA WebLogic 9.2, (Advantage & Premium) Solaris 9 and 10 (SPARC Architectures) IBM WebSphere 6.1.0.5 (Base Edition & Network Deployment Edition)
Sun JDK supplied with application server
Oracle 9i Oracle 10g IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 10g Sun UltraSPARC IIe, 650 MHz processor
JDK supplied with application server
* MS SQL Server 2005 SP2 support was added with LiveCycle ES version 8.0.1 Service Pack 1b **Business Activity Monitoring ES and Business Activity Monitoring ES Extended are not LiveCycle ES Foundation based Solution Components but have the same Platform support as LiveCycle ES Foundation based Solution Components. 1. 2. 3. 4. 5. Foundation is a subcomponent of all the above Solution Components except Business Activity Monitoring ES. Assembler is a subcomponent of Forms ES, Output ES, and PDF Generator ES. Workspace is a subcomponent of Process Management ES. Business Activity Monitoring ES is included with Process Management ES. Database Driver Support for LiveCycle ES Foundation based Solution Components The products listed in this document that require a database support the following database drivers: All supported combinations with MySQL 3.1.12 (mysql-connector-java-3.1.12-bin.jar) All supported combinations with DB2 All supported combinations with Oracle9i/10g All supported combinations with MS SQL Server 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) R2 driver 10.2.0.2 (Thin) (ojdbc14.jar) or later R2 driver. (Microsofts) Microsoft SQL Server 2005 1.1 JDBC Driver

16 of 47

Compatibility Notes LiveCycle ES Version 8.0.1Browser Support

1. Browser Support

LiveCycle ES End user UI:
Policy Server (Browser only) PDF-G (Browser only) Operating System Browsers Microsoft Windows Vista Microsoft Internet Explorer 7 or later Firefox 2.0.0.1 or later Windows 2000 Flash Player 9* Microsoft Internet Explorer 6.0 or later Firefox 2.0.0.1 or later Windows XP Flash Player 9* Microsoft Internet Explorer 6.0 or later Firefox 2.0.0.1 or later Windows Server 2003 Flash Player 9* Microsoft Internet Explorer 6.0 or later Firefox 2.0.0.1 or later Mac OS X v 10.4.x Flash Player 9* Firefox 2.0.0.1 or later (Not for Workspace) (PowerPC) Safari 2.x or later (**Workspace requires 3.0.3 or later) Mac OS X v 10.4.x Flash Player 9* Firefox 2.0.0.1 or later (Not for Workspace) (Intel) Safari 2.x or later (**Workspace requires 3.0.3 or later) Note: or later includes major revisions. So Microsoft Internet Explorer 6.0 or later also covers Microsoft Internet Explorer 7.0 Note: **Workspace ES 8.0.1 with SP1b supports IE and Firefox on Windows but only Safari 3.0.3 or later on the Mac, pre SP1b does not support Safari. Covers: Workspace (Flash required) Reader Extensions (Flash required) Player Flash Player 9*

LiveCycle Forms ES:

Operating System Windows XP Player n/a Browsers Microsoft Internet Explorer 6.0 or later Microsoft Internet Explorer 7.0 or later Firefox 1.5 or later Netscape 8.0 or later Firefox 1.5 or later Firefox 1.5 or later Netscape 8.0 or later Safari 2.0 or later Safari 2.0 or later
Windows Server 2003 Linux/Intel Mac OS X v.10.1.x, 10.2.x, 10.3.x, or 10.4.x (PowerPC) Mac OS X v.10.4.x (Intel)

n/a n/a n/a n/a

LiveCycle Business Activity Monitoring ES:
Operating System Player Browsers Microsoft Windows Vista Flash Player 9* Microsoft Internet Explorer 7 or later Windows 2000 Flash Player 9* Microsoft Internet Explorer 6.0 or later Windows XP Flash Player 9* Microsoft Internet Explorer 6.0 or later Note: or later includes major revisions. So Microsoft Internet Explorer 6.0 or later also covers Microsoft Internet Explorer 7.0

17 of 47

LiveCycle ES Administration UI:
Operating System Microsoft Windows Vista Windows 2000 Windows XP Windows Server 2003 Linux/Intel Player n/a n/a n/a n/a n/a Browsers Microsoft Internet Explorer 7 or later Firefox 2.0.0.1 or later Microsoft Internet Explorer 6.0 or later Firefox 2.0.0.1 or later Microsoft Internet Explorer 6.0 or later Firefox 2.0.0.1 or later Microsoft Internet Explorer 6.0 or later Firefox 2.0.0.1 or later Firefox 2.0.0.1 or later

J2SDK version 1.4.2_04 or later (JDK 1.4.1_10 is not supported) Default Sun JDK included with the WebLogic Server Install Requires a minimum of IBM JDK 1.4.2 SR3 ** J2SDK version 1.4.2_04 or later (JDK 1.4.1_10 is not supported) Default Sun JDK included with the WebLogic Server Install Requires a minimum of IBM JDK 1.4.2 SR3 **
BEA WebLogic 8.1, Service Pack 5 (Advantage & Premium) IBM WebSphere 5.1.1.5* (Base Edition & Network Deployment Edition) JBoss 3.2.5
Intel Pentium 3 or x86 equivalent, 1GHz processor
LiveCycle: Assembler 7.2.1 Forms 7.2 Form Manager 7.2 PDF Generator 7.2 Workflow 7.2.1 Document Security 7.2 Reader Extensions 7.2 Policy Server 7.2
Red Hat Enterprise Linux AS 2.1 or 3.0 SUSE Linux Enterprise Server 9.0
BEA WebLogic 8.1, Service Pack 5 (Advantage & Premium) IBM WebSphere 5.1.1.5* (Base Edition & Network Deployment Edition) IBM WebSphere 5.1.1.5* (Base Edition & Network Deployment Edition) IBM WebSphere 5.1.1.5 * (Base Edition & Network Deployment Edition) BEA WebLogic 8.1, Service Pack 5 (Advantage & Premium)
IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 10g MySQL4.1 MS SQL Server 2000 SP3a Oracle 9i Oracle 10g IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 10g MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 10g IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 10g Oracle 9i Oracle 10g

AIX 5L 5.2 or 5.3

Requires a minimum of IBM JDK 1.4.2 SR3 ** Sun JDK shipped with WebSphere as the default JVM. Default Sun JDK included with the WebLogic Server Install
P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHZ processor Sun UltraSPARC IIe, 650 MHz processor

Solaris 8 or 9

22 of 47
* LiveCycle Workflow requires IBM MQ Series 5.3 CSD 11 or later as the JMS provider when used with IBM WebSphere 5.1.1.x. This will not be required in with WebSphere 6.0 when it is supported with LiveCycle. All LiveCycle products that need to interoperate with Workflow in this case also support MQSeries as the JMS provider. ** May require an IBM patch or depending on the Fix Pack may be included. Please see IBM documentation to decide which to deploy in your environment. 1. Database Driver Support for 7.2/7.2.1 The products listed in this document that require a database support the following database drivers: All supported combinations with MySQL 3.0.15-ga (mysql-connector-java-3.0.15-ga-bin.jar) All supported combinations with DB2 All supported combinations with Oracle9i/10g Windows-JBoss- MS SQL Server Windows-WebLogic- MS SQL Server Windows-WebSphere- MS SQL Server Linux -JBoss- MS SQL Server Linux -WebSphere- MS SQL Server 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) 10.1.0.4 (Thin) (ojdbc14.jar) SQL Server 2000 JDBC Driver (msbase.jar, mssqlserver.jar, msutil.jar) DataDirect JDBC Driver licensed with WebLogic for MS SQL Server. Embedded JDBC Driver with WebSphere for MS SQL Server.Linux -JBoss-MS SQL SQL Server 2000 JDBC Driver (msbase.jar, mssqlserver.jar, msutil.jar) Embedded JDBC Driver with WebSphere for MS SQL Server.

23 of 47

Compatibility Notes 7.2/7.2.2
1. Exception Matrix for non Unix products. The following products are not available on Unix environments. PDF-G Workflow Designer 2. The BAM component on JBoss requires a separate instance of JBoss 3.2.6. 3. Browser Support The Administration User Interface for all the products listed in this document support: IE 6.0 and above on Windows 2000 and above Netscape 7.1 and above on Windows 2000 and above Netscape 7.2 and above on Linux Firefox/Mozilla 1.5/1.8 and above on Windows and Linux Note: When administering a cluster IE is the recommended browser. There are known issues with the Admin UI on WebLogic when clustering. Supported browsers for the end user web UI of LiveCycle Assembler are: Internet Explorer 6.0 and above on Windows Netscape 7.2 and above on Windows and Linux Safari 1.2 and above on Macintosh Firefox/Mozilla 1.5/1.8 and above on Windows and Linux Supported browsers for forms rendered with LiveCycle Forms are: Internet Explorer 5.0 and above on Windows Netscape 7.2 and above on Windows and Linux Safari 1.2 and above on Macintosh Firefox/Mozilla 1.5/1.8 and above on Windows and Linux Supported browsers for the end user web UI of LiveCycle Form Manager are: Internet Explorer 5.0 and above on Windows Netscape 7.2 and above on Windows and Linux Safari 1.2 and above on Macintosh Firefox/Mozilla 1.5/1.8 and above on Windows and Linux The supported browser for the end user web UI of LiveCycle Reader Extensions is: For General Distribution 24 of 47 Version 2.0
Internet Explorer 6.0 and above on Windows
The supported browser for the end user web UI of LiveCycle PDF Generator is: Internet Explorer 6.0 and above on Windows Supported browsers for the end user web UI of LiveCycle Policy Server are: Internet Explorer 6.x SP1 and above on Windows Netscape 7.1 and above on Windows and Linux Safari 1.2 and above on Macintosh 4. Recommended Hardware Requirements 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 5. Minimum Evaluation/Sandbox Requirements Adobe LiveCycle 7.2.x supports Evaluation and Development installations on systems that are in some cases less then the minimum recommended hardware configuration. This is to allow consultants and sales engineers to use laptops for their work. Depending on the combination of products required the minimum system specification is: Windows Server 2003 (preferred) or Windows XP Operating System: Adobe LiveCycle Workflow, FormManager, BAM, Forms, Reader Extensions, Designer and Acrobat/Reader JBoss and MYSQL 1.6GHz Pentium 4 or equivalent with 1.5GB of RAM. WebSphere and DB2/Oracle 1.6GHz Pentium 4 or equivalent with 2GB of RAM. WebLogic and Oracle 1.6GHz Pentium 4 or equivalent with 2GB of RAM. Adobe LiveCycle any server individual product plus Acrobat/Reader JBoss and MYSQL 1.0GHz Pentium 4 or equivalent with 1GB of RAM. WebSphere and DB2/Oracle 1.0GHz Pentium 4 or equivalent with 1GB of RAM. WebLogic and Oracle 1.0GHz Pentium 4 or equivalent with 1GB of RAM. Adobe LiveCycle All products JBoss and MYSQL For General Distribution 25 of 47

BEA WebLogic 8.1, Service Pack 4 Solaris 8 or 9 IBM WebSphere 5.1.1.x
Default Sun JDK included with the WebLogic Server Install Latest installed with WebSphere
Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Sun UltraSPARC IIe, 650 MHz processor
LiveCycle Forms 7.0 was only available on the following platforms: o Windows, Jboss, MySQL o RedHat, WebSphere, DB2 o AIX, WebSphere, DB2 o Solaris, WebLogic, Oracle Supported browsers for forms rendered with LiveCycle Forms are: o Internet Explorer 6.0 and above on Windows o Netscape 7.2 and above on Windows and Linux o Safari 1.2 and above on Macintosh o Firefox/Mozilla 1.5/1.8 and above on Windows and Linux See supported database driver list in section [14. Database Driver Support]

28 of 47

LiveCycle Print
LiveCycle Print 7.1 (Requires Forms 7.1 and Designer 7.1)
MySQL 4.1 IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 9i
J2SDK version 1.4.2_04 or later Default Sun JDK included with the WebLogic Server Install Latest installed with WebSphere Latest installed with WebSphere Default Sun JDK included with the WebLogic Server Install
AIX 5L 5.1 or 5.2 Solaris 8 or 9
IBM WebSphere 5.1.1.x Base Edition, Network Deployment Edition BEA WebLogic 8.1, Service Pack 4

29 of 47

IBM WebSphere 5.1.1.x
Latest installed with WebSphere
IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i
See supported database driver list in section [14. Database Driver Support]

30 of 47

LiveCycle Forms for FileNet
Adobe Product Operating system
Microsoft Windows Server 2003, Enterprise Edition Microsoft Windows Server 2003, Standard Edition (32bit edition) Client - Windows 2000 or XP Professional (32bit and 64-bit editions)

FileNet Software

Adobe Software
IBM WebSphere Application Server 5.1.1.x
Default installed with WebSphere
Two Intel 3.0 GHz CPUs with 2 GB of RAM
LiveCycle Forms for FileNet 7.0, 7.1
Intel Pentium, 512 MB of RAM (minimum), 1024 MB recommended, 1 GB of swap space, 400 MB of installation space, 10 MB of temporary space IBM WebSphere Application Server 5.1.1.x Default installed with WebSphere Sun UltraSPARC IIe 650 MHz or higher CPUs with 2 GB of RAM. (Actual requirements will be based on your particular form processing requirements.)
Solaris 9 BEA WebLogic Server 8.1, Service Pack 4 Default Sun JDK included with the WebLogic Server Install

Content Manager P8 3.0 FileNet Business Process Manager P8 3.0 (Optional) ECM Help Workplace Application Integration Toolkit P8 3.0 Application Engine (Workplace) implementation: Application Engine P8 3.0 (Workplace) Process Engine P8 3.0 (Optional)
Adobe LiveCycle Forms 7.x Adobe LiveCycle Reader Extensions 7.x Adobe LiveCycle Designer 7.x Acrobat Professional or Acrobat Standard, version 6.0.2 or 7.0.x, or Adobe Reader 6.0.2 or 7.0.x

31 of 47

LiveCycle Forms for Documentum
Adobe Product Operating system Application Server JDK Minimum Hw requirements
Client Intel Pentium III 450 Mhz or equivalent processor 256 MB of RAM 150 MB of disk space 1024 x 768 or greater monitor resolution Server Intel Xeon 2.8 GHz processor or equivalent 350 MB of disk space for installation 2 CPUs / 2 GB of RAM for running product 1 GB of free disk space for LiveCycle Forms.

Documentum Software

Documentum Content Server 5.3 Documentum Webtop 5.3 Documentum Desktop 5.3
LiveCycle Forms for Documentum 7.0, 7.1
Microsoft Windows Server 2003, Enterprise Edition Microsoft Windows Server 2003, Standard Edition (32bit edition) Client - Microsoft Windows XP Professional SP2
LiveCycle Designer 7.x Adobe LiveCycle Forms 7.x Adobe LiveCycle Reader Extensions 7.x Acrobat Professional or Acrobat Standard, version 6.0.2 or 7.0.x, or Adobe Reader 6.0.2 or 7.0.x
BEA WebLogic Server 8.1 Service Pack 4

32 of 47

LiveCycle Forms for IBM

IBM Software

IBM DB2 Content Manager Enterprise Edition 8.3 IBM DB2 Information Integrator for Content 8.3 IBM WebSphere Portal 5.1
IBM DB2 UDS Edition V8.2 or V8.1 FixPack 7a IBM DB2 UDS V 8.2 or V8.1 with FixPack 9a IBM DB2 UDS V8.2 or V8.1 with FixPack 7a

Intel Pentium 4 3.0 GHz

LiveCycle Forms for IBM 7.0, 7.1
Red Hat Enterprise Linux 3.0

IBM AIX 5L 5.2

IBM POWER4 1.7 GHz 1 GB of RAM

33 of 47

LiveCycle Workflow
Adobe Product Minimum Hw requirements Supported LDAP servers (for User Management)
LiveCycle Workflow 7.0, 7.0.1,7.2 (See note on 7.0 below)
JBoss 3.2.5 (See additional notes)
J2SDK version 1.4.2_04 or later
MySQL 4.1 IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 8.2 Oracle 9i MySQL 4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.1 Oracle 9i

35 of 47

LiveCycle Form Manager
Minimum Hw requirements Supported LDAP servers (for User Management)
LiveCycle Form Manager 7.0, 7.0.1 (See note on 7.0 below)
MySQL 4.1 IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i
-Pentium 3 or x86 equivalent, 1GHz processor - Minimum 2GB RAM - Minimum 2GB hard disk space for installation - DVD-ROM Drive.

36 of 47

disk space for installation - DVD-ROM Drive. BEA WebLogic 8.1, Service Pack 4 Solaris 8 or 9 IBM WebSphere 5.1.1.x Base Edition, Network Deployment Edition Default Sun JDK included with the WebLogic Server Install Latest installed with WebSphere Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i - Sun UltraSPARC IIe, 650 MHz processor - Minimum 2GB RAM - Minimum 2GB hard disk space for installation - DVD-ROM Drive.
LiveCycle Form Manager 7.0 was only available on the following platforms: o Windows, Jboss, MySQL o RedHat, WebSphere, DB2 o AIX, WebSphere, DB2 o Solaris, WebLogic, Oracle We recommend all customers using Workflow/Form Manager 7.0 to upgrade to 7.0.1 Supported browsers for the user interfaces of Form Manager are: o Internet Explorer 6.0 and above on Windows o Netscape 7.2 and above on Windows and Linux o Safari 1.2 and above on Macintosh o Firefox/Mozilla 1.5/1.8 and above on Windows and Linux See supported database driver list in section [14. Database Driver Support]

37 of 47

LiveCycle Document Security

Certificates

Supported LDAP servers
JBoss 3.2.5 BEA WebLogic 8.1, Service Pack 4 IBM WebSphere 5.1.1.x Base Edition, Network Deployment Edition JBoss 3.2.5 BEA WebLogic 8.1, Service Pack 4 IBM WebSphere 5.1.1.x Base Edition, Network Deployment Edition JBoss 3.2.5
J2SDK version 1.4.2_04 or later Default Sun JDK included with the WebLogic Server Install Latest installed with WebSphere J2SDK version 1.4.2_04 or later Default Sun JDK included with the WebLogic Server Install CertificatesDERencoded X.509 certificate (.cer) files Credentials PKCS#12 files (.pfx files), PKCS #11 files, MSCAPI records CRLsRFC3280.crl files. Intel Pentium 3 or x86 equivalent, 1GHz processor Intel Pentium 3 or x86 equivalent, 1GHz processor

40 of 47

LiveCycle Policy Server
MySQL 4.0.18, 4.0.20 and 4.1.10 IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a Intel Pentium 3 or x86 equivalent, 1GHz processor IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a
LiveCycle Policy Server 7.0,7.0.1,7.0.2 (See note on 7.0 below)
IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.0.18, 4.0.20 and 4.1.10 Oracle 9i Intel Pentium 3 or x86 equivalent, 1GHz processor
IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.0.18, 4.0.20 and 4.1.10 Oracle 9i Intel Pentium 3 or x86 equivalent, 1GHz processor

41 of 47

IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 9i
Solaris 8 or 9 IBM WebSphere 5.1.1.x Base Edition, Network Deployment Edition
Sun UltraSPARC IIe, 650 MHz processor IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i
LiveCycle Policy Server 7.0 was only available on the following platforms: o Windows, Jboss, MySQL o RedHat, WebSphere, DB2 o AIX, WebSphere, DB2 o Solaris, WebLogic, Oracle See supported database driver list in section [14. Database Driver Support]

42 of 47

LiveCycle PDF Generator
MySQL 4.1 IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MS SQL Server 2000 SP3a IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i MySQL 4.1 Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i Oracle 9i IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHZ processor Sun UltraSPARC IIe, 650 MHz processor Intel Pentium 3 or x86 equivalent, 1GHz processor Intel Pentium 3 or x86 equivalent, 1GHz processor
Red Hat Enterprise Linux AS 2.1 or 3.0 LiveCycle PDF Generator 7.0, 7.0.1 (See note below)
JBoss 3.2.5 SUSE Linux Enterprise Server 9.0
LiveCycle PDF Generator 7.0 was only available on the following platforms: o Windows, Jboss, MySQL For General Distribution 43 of 47 Version 2.0

o RedHat, WebSphere, DB2 o AIX, WebSphere, DB2 o Solaris, WebLogic, Oracle LiveCycle PDF Generator is available in three editions. Not all Editions are available on all platform combinations. The Editions are: o Professional (Windows Operating System only) o Elements (Windows Operating System only) o Postscript (All platform combinations) See supported database driver list in section [14. Database Driver Support]

44 of 47

LiveCycle Assembler

LiveCycle Assembler 7.2

45 of 47
IBM DB2 V8.2 or V8.1 FixPack 7a Oracle 9i AIX 5L 5.1 or 5.2 IBM WebSphere 5.1.1.x Base Edition, Network Deployment Edition Latest installed with WebSphere
- P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHZ processor - Minimum 2GB RAM - Minimum 2GB hard disk space for installation - DVD-ROM Drive. - Sun UltraSPARC IIe, 650 MHz processor - Minimum 2GB RAM - Minimum 2GB hard disk space for installation - DVD-ROM Drive.
Additional Notes: See supported database driver list in section [14. Database Driver Support]

46 of 47

Compatibility Notes 7.0.x/7.1 16. Browser Support
The Administration User Interface for all the products listed in this document support: IE 6.x and above on Windows 2000 and above Netscape 7.1 and above on Windows 2000 and above Netscape 7.2 and above on Linux Mozilla 1.8 and above on Windows and Linux.

Database Driver Support

The products listed in this document that require a database support the following database drivers: Windows-JBoss-MySQL 3.0.15 (mysql-connector-java-3.0.15-ga-bin.jar) Windows-JBoss-SQLServer SQL Server 2000 JDBC Driver (msbase.jar, mssqlserver.jar, msutil.jar) Windows-WebLogic-Oracle 9.0.1 (thin) (ojdbc14.jar*) Windows-WebSphere-DB2 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) RHAS 2.1-WebSphere-DB2 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) RHAS 3.0-JBoss-MySQL 3.0.15-ga (mysql-connector-java-3.0.15-ga-bin.jar) RHAS 3.0-WebLogic-Oracle 9.0.1 (thin) (ojdbc14.jar*) SuSE-WebSphere-DB2 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) Solaris-WebSphere-DB2 Solaris-WebLogic-Oracle 9.0.1 (thin) (ojdbc14.jar*) AIX-WebSphere-DB2 8.2 (db2fs.jar, db2jcc.jar, db2jcc_license_cu.jar) AIX-WebSphere-Oracle 9.0.1 (thin) (ojdbc14.jar)

47 of 47

Contents

About This Document.... 5
Whats in this document?..... 5 Who should read this document?..... 6 Additional information...... 6 Conventions used in this guide..... 6

Introduction.... 8

About installing, configuring, and deploying LiveCycle ES.... 8 About upgrading...... 9 How the LiveCycle upgrade works.... 9 Post-deployment upgrade tasks....10 Updating client applications.....10 Updating LiveCycle QPACs.....11 Selecting tasks for configuring and deploying LiveCycle ES...11 Installation, configuration, upgrading, and deployment checklists...12 Automatic installation and deployment checklist....12 Manual installation and deployment checklist....13
Installing the Solution Component Files... 15
Installing Acrobat for LiveCycle PDF Generator ES....15 Installing LiveCycle ES.....16 Viewing the error log.....19 Specifying class path and JAVA_HOME....19 Next steps......20
Manually Configuring WebSphere... 21
Configuring the JVM arguments and properties....21 Configuring WebSphere time-out settings....22 Increasing transaction time-out and ORB service values for PDF Generator ES..23 Configuring throttling for LiveCycle PDF Generator ES....24 Configuring the LiveCycle ES database connectivity....24 Configuring the DB2 data source.....25 Configuring the Oracle data source.....28 Configuring the SQL Server data source....30 Configuring JMS resources for WebSphere....34 Assigning JMS Activation Specification....37 Configuring J2C authentication for JMS....39 SQL Server JMS validation.....40 Restart WebSphere......40 Next step......41
Configuring LiveCycle ES for Deployment... 42
About LiveCycle Configuration Manager....42 Determining the application server SOAP port.....43 Configuring, upgrading to, and deploying LiveCycle ES....43 Manually deploying the EAR files....50 Uninstalling EAR files.....51 Next steps......52
Post-Deployment Activities.... 53
Verifying the deployment and accessing LiveCycle Administration Console...53 Accessing LiveCycle Administration Console....53 Viewing the log files.....54 Deleting working files that contain sensitive data....54 Configuring Acrobat 8.1 for PDF Generator ES.....55 Final setup for LiveCycle Rights Management ES....55 Upgrading to LiveCycle Business Activity Monitoring ES....55 Accessing User Management.....56 Accessing solution component web applications....57 Accessing LiveCycle Rights Management ES....57 Migrating HSM credentials.....58 Enabling FIPS mode.....59 Configuring LiveCycle ES to access LDAP....60 Configuring HTML digital signature....60 Configuring the Connector for EMC Documentum service...61 Creating the XDP MIME format in your Documentum repository...63 Configuring the Connector for IBM FileNet service....64 Setting the Adobe PDF Printer as default for PDF Generator ES...67 Setting environment variables for PDF Generator ES....67 Setting PDF Generator ES watched folder performance parameters...68 Verifying that all languages are displayed after conversion with PDF Generator ES..68 Creating email endpoints for email notifications....69 Uninstalling LiveCycle ES.....69

Post-deployment upgrade tasks 10
Post-deployment upgrade tasks
Some manual steps are required after you complete the upgrade and deployment process to ensure that LiveCycle 7.x properties have been fully migrated to LiveCycle ES and that LiveCycle 7.x client applications can be run in LiveCycle ES. (See Post-Deployment Activities on page 53.)
Updating client applications
Client applications developed using LiveCycle 7.x may need to be updated with new client JAR files in the following circumstances:
LiveCycle 7.x client applications running on WebSphere use the um-client.jar file or are stand-alone and running on Java 1.4 LiveCycle Forms version pre-7.2 client applications on WebSphere LiveCycle 7.x client applications are written for LiveCycle Forms 7.0 or 7.1 (pre-7.2) running on WebSphere.
Client applications using um-client.jar
The LiveCycle 7.x version of the um-client.jar file is not compatible with LiveCycle ES running on WebSphere. If any LiveCycle 7.x client applications use this file, they must be updated to use the LiveCycle ES adobe-usermanager-client.jar file instead of the um-client.jar file from LiveCycle 7.x. After LiveCycle ES is installed, the new um-client.jar file is in the [LiveCycleES root]/LiveCycle_ES_SDK/client-libs/ common directory.
Client applications that will continue to run on Java 1.4
All client applications ran on Java 1.4 in LiveCycle 7.x. If stand-alone LiveCycle 7.x applications (applications running remotely from the LiveCycle server) will be moved to run on Java 5 when you upgrade to LiveCycle ES, the WebSphere 5.1.x or WebSphere 6.0.x client JAR files must be replaced with WebSphere 6.1 client JAR files. If the LiveCycle 7.x client application will continue to run on Java 1.4 after upgrading to LiveCycle ES, this update is not required.
LiveCycle Forms version pre-7.2 client applications
LiveCycle Forms client applications that were developed using a version of LiveCycle Forms earlier than version 7.2 (for example, 7.0 or 7.1) running on WebSphere require the replacement of five LiveCycle Forms 7.2 JAR files. The LiveCycle Forms 7.2 JAR files are included in the LiveCycle ES installation in the following locations in the [LiveCycle ES root]/LiveCycle_ES_SDK/client-libs/upgrade/lc72/components/ directory:
/csa/common/lib/adobe/adobe-common.jar /csa/common/lib/adobe/datamanager-client.jar /csa/websphere/lib/adobe/AdobeCSAUtils.jar /csa/websphere/lib/adobe/DocumentServiceLibrary.jar /forms/common/lib/adobe/formserver-client.jar

Installing the Solution Component Files
This section describes the first phase of setting up a LiveCycle ES system that is running the LiveCycle installation program on a Windows, Linux, or UNIX operating system. A subsequent phase will include running LiveCycle Configuration Manager to configure, upgrade, and deploy LiveCycle ES. Before you install the solution components, you must ensure that your environment includes the software and hardware required to run LiveCycle ES. You should also understand the installation options and have prepared the environment as required. (See Preparing to Upgrade to LiveCycle ES at http://www.adobe.com/go/learn_lc_upgradePreparation.) Note: If you are upgrading any products that use LiveCycle 7.x QPACs (called components in LiveCycle ES), you must upgrade LiveCycle Workflow 7.x to LiveCycle Process Management ES. If Process Management ES is not included in the LiveCycle ES deployment, QPACs cannot be used.
Installing Acrobat for LiveCycle PDF Generator ES
Note: This section applies only if your configuration requires native file format conversion (for example, Microsoft Word to PDF). LiveCycle PDF Generator ES can convert many native file formats to PDF. Such native file formats include Microsoft Word, Microsoft Excel, Microsoft PowerPoint, Microsoft Project, Microsoft Visio, Corel WordPerfect, Adobe Photoshop, Adobe FrameMaker, and Adobe PageMaker. For more information about PDF Generator ES, see the LiveCycle ES Overview at http://www.adobe.com/go/learn_lc_overview If you plan to use PDF Generator ES native application format conversion or optical character recognition (OCR) generation, you must install Acrobat 8.1 on the computer where PDF Generator ES will run before you run the LiveCycle ES installation program. If you do not install Acrobat 8.1 prior to installing LiveCycle ES, you must install Acrobat 8.1 afterward and perform some additional manual tasks. A copy of Acrobat 8.1 is included on the LiveCycle ES DVD. If you do not want to configure PDF Generator ES to support this functionality, you do not need to install or upgrade to Acrobat 8.1. However, it is recommended that you upgrade to Acrobat 8.1 in order to support conversions using Microsoft Office 2007.
To install Acrobat 8.1 for PDF Generator ES:
1. Uninstall any other version of Acrobat by using the Add/Remove Programs window in the Windows Control Panel. 2. Restart your computer if prompted. 3. Navigate to one of the following folders on the LiveCycle ES installation media, depending on your locale:
additional\acrobat\efg\Adobe Acrobat 8 Professional additional\acrobat\jpn\Adobe Acrobat 8 Professional

cd [appserver root].\bin\setupCmdLine.bat
3. Start LiveCycle Configuration Manager by typing the following commands:
cd [LiveCycle_ES_ROOT]/configurationManager/bin ConfigurationManager.bat

Next steps 20

To set the class path and JAVA_HOME on Linux and UNIX:

export PATH=

cd [appserver root]./bin/setupCmdLine.bat
3. Start LiveCycle Configuration Manager by typing the following commands
cd [LiveCycleES root]/configurationManager/bin ConfigurationManager.sh

Next steps

You must now configure and upgrade LiveCycle ES for deployment. (See Configuring LiveCycle ES for Deployment on page 42.)
Manually Configuring WebSphere
This chapter describes how to manually configure the application server to prepare for the manual deployment of LiveCycle ES in a non-clustered environment. If you prefer to have LiveCycle Configuration Manager configure WebSphere, you do not need to complete this chapter; instead, go to Configuring LiveCycle ES for Deployment on page 42. The time at which you perform the tasks in this section depends on whether the target application server for LiveCycle ES is installed on the same computer as the LiveCycle 7.x server or a different computer:
Target application server for LiveCycle ES is on the same computer as LiveCycle 7.x server Do not perform these tasks until you are partway through the LiveCycle ES upgrade using LiveCycle Configuration Manager. When you are prompted by LiveCycle Configuration Manager and the documentation to stop LiveCycle 7.x, you can do so, and then start the application server for LiveCycle ES and configure it. In this case, you must first complete the tasks in the Configuring WebSphere Application Server section of Preparing to Upgrade to LiveCycle ES (at http://www.adobe.com/go/learn_lc_upgradePreparation.
and then complete the tasks in this section. Note: Because the LiveCycle 7.x server and LiveCycle ES target application server cannot be started at the same time on the same computer, performing the tasks in this order minimizes server down time.
Target application server for LiveCycle ES is on a different computer than LiveCycle 7.x server
You can configure the LiveCycle ES application server after you install LiveCycle ES but before you run LiveCycle Configuration Manager. (This order of tasks is reflected in the order of the sections in this document.) Note: You must have configured your WebSphere Application Server according to the instructions in the Configuring WebSphere Application Server chapter of Preparing to Upgrade to LiveCycle ES.

Configuring the JVM arguments and properties
You must configure the JVM arguments and custom properties.
To configure the JVM arguments:
1. In the URL line of a web browser, type the appropriate URL:
http://[host name]:[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 6.1.0.5 is 9060. If Global Security is enabled, the default SSL port value is 9043. 2. If WebSphere Global Security is enabled, type the WebSphere user ID and password in the boxes provided. 3. Click Log In.
Configuring WebSphere time-out settings 22
4. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and, in the right pane, click the server name. 5. Under Server Infrastructure, click Java and Process Management > Process Definition. 6. Under Additional Properties, click Java Virtual Machine. 7. In the Initial Heap Size box, type 256 and, in the Maximum Heap Size box, type 1024. Note: This value depends on the hardware configuration and the available memory. Setting this value to zero (0) might be preferable because it means NOMAX. Setting the value to zero does not mean that the heap grows infinitely large because the initial heap size parameter ensures that the garbage collector runs periodically to limit heap growth. 8. In the Generic JVM arguments box, type -Dfile.encoding=utf8 and then click OK. 9. Under Additional Properties, click Custom Properties, and then click New. 10. In the Name box, type java.net.preferIPv4Stack and, in the Value box, type true. 11. Click OK or Apply. 12. In the Messages box, click Save directly to master configuration. You need to create a J2C Authentication to assign to your data source.
To create a J2C authentication configuration for the data source:
1. In the navigation tree, click Security > Secure administration, applications, and infrastructure. 2. In the right pane, under Authentication, click Java Authentication and Authorization Service > J2C authentication data. 3. Click New. 4. Provide the required information in these boxes: Alias: Type a name appropriate for the database user (for example, type IDP_DS/db2-db2user). User ID: Enter a user ID. This ID is the login credential used to access the database that will be used with the IDP_DS data source (for example, db2user). Password: Type a password for this user. 5. Click OK or Apply. 6. Click Save directly to master configuration.

Configuring WebSphere time-out settings
Creation of a large number of users can be done by using a single invocation of the CreateLocalUsers API. The API is expected to persist all the new users or roll back all changes in the event of a failure. Therefore, the API is required to operate in a single transaction to support rollback. Because a transactions lifetime is limited by the application server settings (usually 30 seconds), the number of inserts that can be performed in the given time frame is limited. As a result, bulk insert APIs, such as CreateLocalUser, fail when the number of users exceeds a certain limit. This limit is decided again by the transactions lifetime.
Increasing transaction time-out and ORB service values for PDF Generator ES 23
You must modify the following time-out settings:
Transaction time-out value CORBA time-out value
To configure transaction time-out:
1. In the WebSphere Administrative Console navigation tree, click Servers > Application servers and, In the right pane, click the server name. 2. Under Container Settings, click Container Services > Transaction Service. 3. Under General Properties, in the Total transaction lifetime timeout box, type 300 (or higher). 4. Ensure that the value in the Maximum transaction timeout box is greater than or equal to the total transaction time-out. 5. Click OK or Apply.
To increase the CORBA time-out value:
1. In the navigation tree, click Servers > Application servers and, in the right pane, click the server name. 2. Under Container Settings, click Container Services > ORB Service. 3. Under General Properties, in the Request timeout box, type 360 and, in the Locate Request Timeout box, type 300. 4. Click OK or Apply. 5. In the Messages box, click Save directly to master configuration.
Increasing transaction time-out and ORB service values for PDF Generator ES
If you installed and deploy PDF Generator ES, you must increase the maximum transaction time-out and ORB service values on WebSphere to ensure that document conversions by PDF Generator ES complete successfully. You can increase the transaction time-out and ORB service value before or after you deploy PDF Generator ES.
To increase the maximum transaction time-out and ORB service values:
1. In the WebSphere Administrative Console navigation tree, click Servers > Application Servers and, in in the right pane, click the server name. 2. Under Container Settings, click Container Services > Transaction Service. 3. In the Maximum transaction timeout box, type 300 (or higher) and, in the Total transaction lifetime timeout box, change 120 to 300. 4. Click OK or Apply. 5. In the Messages box, click Save directly to master configuration.

5. In the Connection area, set the properties as follows:
In the Bus name list, select IDP_JMS_Bus. In the Queue name list, select other, please specify and then type adobe_PECommandQueue in the box that appears. In the Delivery mode list, select Persistent.
6. In the Advanced area, in the Read ahead list, select Inherited from connection factory. 7. Click OK or Apply. 8. Click Save directly to master configuration. 9. Repeat steps 3 through 8 for each of the queues in the following table, replacing the properties under the Connection group set in step 5 with the appropriate values. Name adobe_PEDCommandQueue adobe_PEInteractionQueue adobe_JobManagerQueue Delivery Mode persistent persistent persistent JNDI name queue/adobe_PEDCommandQueue queue/adobe_PEInteractionQueue queue/adobe_JobManagerQueue
Next, you must create a bus destination for each queue defined in To create a queue: on page 36.
To create a bus destination:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS_Bus. 2. On the next screen, under Destination Resources, click Destinations, and then click New.
Assigning JMS Activation Specification 37
3. On the next screen, under Select Destination Type, select Queue and then click Next. 4. In the step 1 pane, in the Identifier box, type adobe_PECommandQueue and then click Next. 5. Click Next, and then click Finish. 6. Click Save directly to master configuration. 7. Repeat steps 3 through 6 for each queue defined in To create a queue: on page 36.
To create the first topic:
1. In the navigation tree, click Resources > JMS > Topics. 2. In the drop-down list in the right pane, select Node (without server) as the level, and then click New. 3. Accept the default or select Default messaging provider and click OK. 4. In the Administration area, set these properties:
In the Name box, type adobe_LAFEventTopic. In the JNDI name box, type topic/adobe_LAFEventTopic.
In the Topic name box, type adobe_LAFEventTopic. In the Bus name list, select IDP_JMS_Bus. In the Topic space list, select Default.Topic.Space.
6. Click OK or Apply. 7. Click Save directly to master configuration. 8. Repeat steps 1 through 7 for the queue in the following table, replacing the Name, JDNI name and Topic name properties. Name and topic name adobe_TaskEventTopic Delivery Mode persistent JNDI name topic/adobe_TaskEventTopic

To create a group:

1. In the navigation tree, click User and Groups > Manage Groups, and then click Create. 2. In the Group name box, type lc8_jms_group, and then click Create.

To create a user:

1. In the navigation tree, click User and Groups > Manage Users, and then click Create. 2. Click Group Membership and click Search. 3. Select the group name lc8_jms_group that was previously created and click Close. 4. In the User ID box, type [authentication for JAAS name]. 5. Add a first and last name in the boxes provided. 6. Type the [JAAS authentication name] as the password, and then click create.

To associate security:

1. In the navigation tree, click Resources > JMS > Activation specifications. 2. Click one of the activation specifications. 3. Under Additional, in the Authentication Alias list, select the JMS authentication alias that was created in To configure J2C authentication: on page 39.
SQL Server JMS validation 40
4. Click OK or Apply. 5. Click Save directly to master configuration. 6. Repeat steps 1 to 5 for all activation specifications.
To assign group privileges to the IDP_JMS Bus:
1. In the navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS Bus. 2. Under Additional Properties, click Security. 3. Under Additional Properties, click Users and groups in the bus connector role. 4. In Bus Connector Role group, use the default or select Group name and type the group name created in To configure J2C authentication: on page 39. 5. Click OK or Apply. 6. Click Save directly to master configuration.
SQL Server JMS validation
Note: Validation is required only for Microsoft SQL Server. The SQL Server JMS setup requires additional verification. This is also required if the JMS/LCM verification fails.
To verify the JMS setup with SQL Server:
1. In the WebSphere Administrative Console navigation tree, click Service Integration > Buses and, in the right pane, click IDP_JMS_BUS. 2. Under Topology, click Messaging Engines. When working, it should display a green arrow. The status for the bus is likely unknown at this point. 3. Select your messaging engine. 4. Under Additional Properties, click Message store. The schema name must match the user name; if it does not, set it to match. To set up the Microsoft SQL Server database and users, see Preparing to Install LiveCycle ES at www.adobe.com/go/learn_lc_prepareInstall. 5. In the Messages box, click Save directly to master configuration. 6. Delete any tables that begin with SIB to ensure there are no conflicts with old bus configurations. 7. Restart WebSphere and retry step 1 to ensure that the bus is running.

If you used LiveCycle Configuration Manager to configure and deploy LiveCycle ES, you can now do the following tasks:
Verify the deployment. (See Verifying the deployment and accessing LiveCycle Administration Console on page 53.) Access LiveCycle Administration Console. (See Accessing LiveCycle Administration Console on page 53.) Upgrading Business Activity Monitoring ES (See Upgrading to LiveCycle Business Activity Monitoring ES on page 55.) Migrate HSM credentials (for LiveCycle Document Security upgrades). (See Migrating HSM credentials on page 58.) Configure LiveCycle solution components to access LDAP. (See Configuring LiveCycle ES to access LDAP on page 60.) Configuring the LiveCycle ES Connectors for ECM systems. (See Configuring the Connector for EMC Documentum service on page 61 or Configuring the Connector for IBM FileNet service on page 64 Set environment variables for PDF Generator ES. (See Setting environment variables for PDF Generator ES on page 67.) Update LiveCycle 7.x applications to ensure LiveCycle ES compatibility. (See Updating client applications on page 10.) Find out about some updates regarding upgrading from LiveCycle 7.x to LiveCycle ES. (See Additional upgrade issues on page 74.) Uninstall LiveCycle ES. (See Uninstalling LiveCycle ES on page 69.)
Post-Deployment Activities
This chapter describes how to verify the deployment by accessing LiveCycle Administration Console and checking the application server log files. It also describes how to get started using LiveCycle ES solution components and services after they are installed, configured, and deployed to your application server:
Verifying the deployment and accessing LiveCycle Administration Console on page 53 Accessing solution component web applications on page 57 Accessing User Management on page 56 Configuring LiveCycle ES to access LDAP on page 60 Setting environment variables for PDF Generator ES on page 67
After you configure the settings in this chapter, see Administering LiveCycle ES at http://www.adobe.com/go/learn_lc_administration for additional information about configuring your LiveCycle ES environment for development and production.
Verifying the deployment and accessing LiveCycle Administration Console

Viewing the log files

Events, such as run-time or startup errors, are recorded to the application server log files. If you have problems deploying to the application server, you can use the log files to help you find the problem. You can open the log files using any text editor. The following log files are in the [appserver root]/profiles/default/logs/servername directory:
SystemErr.log SystemOut.log StartServer.log
Deleting working files that contain sensitive data
During upgrade, all the information is extracted from the LiveCycle Policy Server database and written to working files, from which the information is then migrated into the LiveCycle ES database. The files containing this information remain in the [LiveCycleES root]/configurationManager/working/upgrade directory after the data migration is complete. Some of this data is sensitive information, such as passwords and document encryption keys. After you verify that the upgrade is complete (essential and non-essential data is migrated) and Rights Management ES is working as expected, you must delete the LiveCycle Policy Server migration files. In the [LiveCycleES root]/configurationManager/working/upgrade, directory, delete all the files whose names begin with OrigExported and Intermediate. Approximately 50 files need to be removed. Do not delete the sharedData file.
Configuring Acrobat 8.1 for PDF Generator ES 55
Configuring Acrobat 8.1 for PDF Generator ES
Note: This functionality is supported only on the Windows platform. If you did not choose to install Acrobat 8.1 using the LiveCycle ES installer, you need to complete the following procedure to set up Acrobat 8.1 for use with PDF Generator ES.
1. If a previous version (8.0 or earlier) of Acrobat is installed, uninstall it using Add or Remove Programs in the Windows Control Panel. 2. Navigate to one of the following folders on the LiveCycle ES installation media:
additional\acrobat\efg\ additional\acrobat\jpn\
3. Install Acrobat 8.1 by running the AutoPlay.exe file. 4. Navigate to the additional\scripts folder on the LiveCycle ES installation media. 5. Run the following batch file:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat. 2. If the PDF file opens successfully, Acrobat 8.1 is installed correctly. If the PDF fails to open correctly, uninstall Acrobat and reinstall it. Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after Acrobat installation is complete and disable the automatic updates for Acrobat. Set the environment variable, Acrobat_PATH to point to Acrobat.exe (for example, C:\Program Files\Adobe\Acrobat 8.0\Acrobat\Acrobat.exe).

Creating the XDP MIME format in your Documentum repository
Before users can store and retrieve XDP files from a Documentum repository, you must do one of these tasks:
Create a corresponding XDP format in each repository where users will access XDP files. Configure the Connector for EMC Documentum service to use a Documentum Administrator account when accessing the Documentum repository. In this case, the XDP format is created by the Connector for EMC Documentum service whenever it is required.
To create the XDP format on Documentum Content Server using Documentum Administrator:
1. Log in to Documentum Administrator. 2. Click Formats. 3. Select File > New > Format. 4. Type the following information into the corresponding fields: Name: xdp Default File Extension: xdp Mime Type: application/xdp 5. Repeat steps 1 - 4 for all other Documentum repositories where users will store XDP files.
Configuring the Connector for IBM FileNet service 64
To configure the Connector for EMC Documentum service to use a Documentum Administrator:
1. Open a web browser and enter this URL: http://localhost:9080/adminui (local deployment using the default port) 2. Log in using the default user name and password: User name: administrator Password: password 3. Click Services > LiveCycle ES Connector for EMC Documentum > Configuration Settings. 4. In the Documentum Principal Credentials Information area, update the following information and then click Save: User Name: [Documentum Administrator user name] Password: [Documentum Administrator password] 5. Click Repository Credentials Settings. 6. Select a repository from the list or, if none exist, click Add. 7. Type the following information: Repository Name: [Repository Name] Repository Credentials User Name: [Documentum Administrator user name] Repository Credentials Password: [Documentum Administrator password] 8. Click Save. 9. Repeat steps 7 - 9 for all repositories where users will store XDP files.
Configuring the Connector for IBM FileNet service
If you installed the Connector for IBM FileNet service as part of your LiveCycle ES solution, complete the following procedure to configure the service to connect to the FileNet object store.
To configure Connector for IBM FileNet:
1. Locate the adobe-component-ext.properties file in the [WAS HOME]/AppsServer/profiles/[profile name] folder. If the file does not exist, you must create it. Add a new system property that provides the location of the following Application Engine JAR files:
activation.jar javaapi.jar log4j-1.2.8.jar mailapi.jar p8cjares.jar soap.jar xercesimpl.jar xml-apis.jar
Configuring the Connector for IBM FileNet service 65
The new system property should take this form:
For example, using a default Application Engine installation, add the following system property on a new line, with no line breaks, and end the line with a carriage return, to the file:

Database instances must contain only alphanumeric characters in their names. (Linux and UNIX) Database instances must not exceed the platform-specific threshold of 8 characters. For upgrading to LiveCycle ES, a default schema is associated with each database user. When LiveCycle ES initializes using a database user, the data is populated in the default schema of the user. During upgrade, you must use same user that was used for LiveCycle 7.x. This applies to Oracle, DB2, and SQL Server.
If the initialization fails at the beginning of the process, verify that the following tasks are done:
(Non-turnkey install) The LiveCycle ES database is created and the user has full access rights to it. The database server is accessible when you ping it. The database is empty; that is, it has no tables, sequences, views, or index tables. The JNDI name for IDP_DS is created.
If initialization fails while writing to the Registry, check the application server logs for errors that pertain to the queues and topics. If errors exist, verify that the queues and topics are configured properly.
Troubleshooting with log files

LCM log file

By default, the LCM log file is located in [LiveCycleES root]configurationManger\log and will be named lcm.0.log (or a similar name). The log files are useful for LiveCycle Configuration Manager failure analysis and may be required when dealing with Adobe Enterprise Support.
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 in to WebSphere Administrative Console. 2. In the navigation tree, click Troubleshooting > Logs and Trace, and then click the name of the application server. 3. Click JVM Logs. 4. 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. By default, the files are in the following location: [appserver root]/profiles/[profile_name]/logs/[server_name]
Modifying WebSphere log level 72
Modifying WebSphere log level
You must modify your WebSphere log level to filter out multiple Deprecated usage of direct JNDI lookup of resource IDP_DS messages written to the log file. You can modify SystemOut.log to remove these messages by setting the log level as follows:
*=info:com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl=severe.

EAR files uninstalling 51 environment variables setting for LiveCycle PDF Generator ES 67 setting JAVA_HOME 17, 19 error logs, viewing 19 error messages class not found 72 J2CA0294W warning 73 JNDI name not found 72 exceptions 73
Business Activity Monitoring ES upgrading 55
Hardware Security Module (HSM) credentials, migrating 58
checklists 12 class not found error 72 classpath, specifying 19 client applications, updating 10 component files, installing 15 Configuration Manager about 42 configuring See also installing about configuring LiveCycle ES 8 Acrobat for LiveCycle PDF Generator ES 19
installing See also configuring about installing LiveCycle ES 8 Acrobat for LiveCycle PDF Generator ES 15 checklist for automatic installation 12 checklist for manual installation 13 DB2 driver 25 LiveCycle ES 16 LiveCycle ES to a Windows staging platform 16 solution component files 15
J2CA0294W warning 73 JAR files, updating 10 Java 1.Java SDK 17 JAVA_HOME, setting 17, 19 JNDI name not found error 72 JVM system logs, viewing 71
signature fields 75 SOAP port, establishing for WebSphere 43 solution component files, installing 15
temporary directory 16 troubleshooting application server considerations 70 database initialization considerations 71 getting help 70 installation considerations 70 log files 71 Trust Store 17
LDAP, configuring 60 LiveCycle Configuration Manager performing a configuration 43 LiveCycle. See Adobe LiveCycle log files errors, viewing 19 LCM, viewing 71 troubleshooting 71 log level, modifying for WebSphere 72
um-client.jar 10 uninstalling EAR files 51 LiveCycle ES 69 upgrading about 9 BAM Server 55 LiveCycle Policy Server to LiveCycle Rights Management ES 73 post-deployment tasks 10
manually configuring WebSphere 21 Microsoft Office 15
naming conventions, file path 6 native application format conversion 15
verifying the deployment 53 viewing application server log files 54 error log files 19 JVM system log files 71
optical character recognition (OCR) generation 15
printer settings for LiveCycle PDF Generator ES 74
QPACs, updating 11 watched folder, setting performance parameters for LiveCycle PDF Generator ES 68 web applications, accessing 57 WebSphere SOAP port, establishing 43 WebSphere, configuring manually 21 Windows staging platform 16 working files, deleting 54
remote connection 74 Rights credential, configuring 17