bb c Preparing to Upgrade to LiveCycle ES

bb c Preparing to Upgrade to LiveCycle ES
bc
Preparing to Upgrade to LiveCycle® ES
from LiveCycle 7.x
Adobe® LiveCycle® ES
September 2007
Version 8.0
© 2007 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle® ES 8.0 Preparing to Upgrade to LiveCycle ES for Microsoft® Windows®, Linux®, and UNIX®
Edition 1.2, September 2007
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Acrobat, Flash, Flex, Flex Builder, FrameMaker, LiveCycle, PageMaker, Photoshop, PostScript, and Reader are either
registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
AIX, DB2, IBM, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
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.
BEA WebLogic Server is a registered trademark of BEA Systems, Inc.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the U.S. and other countries.
Java, Solaris, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
JBoss and Red Hat are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft, Windows, Windows Server, and Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.
Novell and SUSE are trademarks or registered trademarks of Novell, Inc. in the United States and other countries.
UNIX is a trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.
All other trademarks are the property of their respective owners.
This product contains either BISAFE and/or TIPEM software by RSA Data Security, Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes code licensed from RSA Data Security.
This product includes software developed by the JDOM Project (http://www.jdom.org/).
Macromedia Flash 8 video is powered by On2 TrueMotion video technology. © 1992-2005 On2 Technologies, Inc. All Rights Reserved.
http://www.on2.com.
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
Portions of this code are licensed from Nellymoser(www.nellymoser.com).
MPEG Layer-3 audio compression technology licensed by Fraunhofer IIS and THOMSON Multimedia (http://www.iis.fhg.de/amm/).
This product includes software developed by L2FProd.com (http://www.L2FProd.com/).
The JBoss library is licensed under the GNU Library General Public LIcense, a copy of which is included with this software.
The BeanShell library is licensed under the GNU Library General Public License, a copy of which is included with this software.
This product includes software developed by The Werken Company.
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
The OpenOffice.org library is licensed under the GNU Library General Public License, a copy of which is included with this software.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 8
Who should read this document? ............................................................................................................................................ 9
Conventions used in this document ....................................................................................................................................... 9
Additional information...............................................................................................................................................................10
1
Introduction to Upgrading LiveCycle ...................................................................................... 11
About the upgrade documentation......................................................................................................................................11
Preparing to Upgrade to LiveCycle ES (this document)...........................................................................................11
Upgrading to LiveCycle ES for JBoss, WebSphere, or WebLogic ..........................................................................12
Upgrading to LiveCycle ES for JBoss Using Turnkey .................................................................................................13
LiveCycle Configuration Manager Help.........................................................................................................................13
Upgrading Applications to LiveCycle ES Using APIs .................................................................................................13
Upgrading task outline...............................................................................................................................................................13
Next steps........................................................................................................................................................................................14
2
Understanding the Changes in LiveCycle ES........................................................................... 15
How the LiveCycle ES upgrade protects your IT investment .......................................................................................15
How Adobe Reader is independent of LiveCycle .......................................................................................................15
About data, process, and API compatibility .................................................................................................................16
Mapping LiveCycle 7.x products to LiveCycle ES solution components..................................................................16
Compatibility between LiveCycle 7.x and LiveCycle ES .................................................................................................18
Form and client compatibility ...........................................................................................................................................19
Data and process compatibility ........................................................................................................................................19
API compatibility....................................................................................................................................................................20
Enabling FIPS mode.....................................................................................................................................................................20
Upgrading your infrastructure ................................................................................................................................................21
Supported operating systems...........................................................................................................................................21
Supported application servers ..........................................................................................................................................21
Supported databases ...........................................................................................................................................................21
Upgrading your LiveCycle 7.x products ...............................................................................................................................22
General considerations for upgrading LiveCycle 7.x products .............................................................................22
Upgrading User Management ..........................................................................................................................................22
Upgrading LiveCycle 7.x products that use User Management ...........................................................................23
Upgrading LiveCycle Workflow ........................................................................................................................................23
Upgrading LiveCycle Business Activity Monitor ........................................................................................................24
Upgrading LiveCycle Form Manager ..............................................................................................................................24
Upgrading LiveCycle Reader Extensions.......................................................................................................................25
Upgrading LiveCycle Forms and LiveCycle Print........................................................................................................25
Upgrading LiveCycle Barcoded Forms...........................................................................................................................25
Upgrading LiveCycle Policy Server..................................................................................................................................26
Upgrading LiveCycle Document Security Server .......................................................................................................26
Upgrading LiveCycle PDF Generator ..............................................................................................................................26
Upgrading LiveCycle Assembler ......................................................................................................................................27
4
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
3
Contents
5
Planning for the Upgrade Process............................................................................................ 28
Overview of the upgrade process ..........................................................................................................................................28
How LiveCycle Configuration Manager upgrades LiveCycle 7.x to LiveCycle ES ...........................................29
About the compatibility layer ...........................................................................................................................................29
Updating client applications....................................................................................................................................................29
LiveCycle Assembler client applications on WebLogic............................................................................................31
Updating LiveCycle QPACs .......................................................................................................................................................31
Transferring IP address and host name................................................................................................................................31
Third-party infrastructure support.........................................................................................................................................31
Microsoft Windows Server..................................................................................................................................................31
Red Hat Enterprise Linux and SUSE Linux.....................................................................................................................32
IBM AIX.......................................................................................................................................................................................32
Sun Solaris ................................................................................................................................................................................33
System requirements for LiveCycle ES .................................................................................................................................33
Minimum hardware requirements ..................................................................................................................................34
Intel x86 compatibility .........................................................................................................................................................35
Recommended hardware requirements .......................................................................................................................35
Supported software ..............................................................................................................................................................35
Web browser support...........................................................................................................................................................37
End-user user interface..................................................................................................................................................37
Administrator user interface........................................................................................................................................38
Additional requirements for Linux or UNIX operating systems............................................................................38
Additional requirements for PDF Generator ES .........................................................................................................39
User account......................................................................................................................................................................39
Acrobat ................................................................................................................................................................................39
Native file conversion software installation...........................................................................................................39
Windows environment variables ...............................................................................................................................39
Service Control Manager command line tool .......................................................................................................40
Additional requirements for Business Activity Monitoring ES ..............................................................................40
LDAP configuration .....................................................................................................................................................................41
Installation considerations........................................................................................................................................................41
Installing from network drives ..........................................................................................................................................41
Manual use of Acrobat restricted .....................................................................................................................................41
Installation and deployment topology considerations .................................................................................................41
Gathering information required before you start ............................................................................................................42
Credentials .........................................................................................................................................................................42
Passwords...........................................................................................................................................................................42
Port information...............................................................................................................................................................42
Server names.....................................................................................................................................................................43
Location of directories ...................................................................................................................................................43
Watched folder locations..............................................................................................................................................44
Next steps........................................................................................................................................................................................44
4
Exporting the LiveCycle 7.x EAR files....................................................................................... 45
Next steps........................................................................................................................................................................................46
5
Backing Up the LiveCycle 7.x Environment............................................................................. 47
Backing up the files and directories associated with LiveCycle 7.x............................................................................47
Backing up the LiveCycle 7.x database ................................................................................................................................48
Dropping the SIB database tables (WebSphere only).....................................................................................................48
Next steps........................................................................................................................................................................................49
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
6
Contents
6
Configuring JBoss Application Server ..................................................................................... 50
Installing the J2SE SDK ...............................................................................................................................................................50
Installing JBoss ..............................................................................................................................................................................51
Using Adobe preconfigured JBoss ..................................................................................................................................51
Manually installing JBoss.....................................................................................................................................................52
Starting and stopping JBoss ..............................................................................................................................................52
Modifying the JBoss configuration files ...............................................................................................................................53
Configuring the LiveCycle ES database connectivity......................................................................................................57
Configuring MySQL for Adobe preconfigured JBoss ................................................................................................58
Configuring the MySQL data source.........................................................................................................................58
Setting MySQL as the JMS data source....................................................................................................................59
Configuring MySQL for manually installed JBoss.......................................................................................................60
Configuring the MySQL data source.........................................................................................................................60
Setting MySQL as the JMS data source....................................................................................................................61
Configuring Oracle for Adobe preconfigured JBoss .................................................................................................62
Configuring the Oracle data source..........................................................................................................................63
Setting Oracle as the JMS data source .....................................................................................................................63
Configuring Oracle for manually installed JBoss........................................................................................................65
Configuring the Oracle data source..........................................................................................................................65
Setting Oracle as the JMS data source .....................................................................................................................66
Configuring SQL Server..............................................................................................................................................................68
Configuring the SQL Server data source .......................................................................................................................68
Configuring JMS with Microsoft SQL Server ..........................................................................................................70
Configuring DB2 for Adobe preconfigured JBoss......................................................................................................72
Configuring the DB2 data source ..............................................................................................................................72
Setting DB2 as the JMS data source..........................................................................................................................73
Configuring DB2 for manually configured JBoss........................................................................................................74
Configuring the DB2 data source ..............................................................................................................................75
Setting DB2 as the JMS data source..........................................................................................................................76
Next steps........................................................................................................................................................................................78
7
Configuring WebSphere Application Server........................................................................... 79
Installing WebSphere Application Server............................................................................................................................79
Installing a Fix Pack to WebSphere 6.1...........................................................................................................................79
Setting the JAVA_HOME and PATH environment variables...................................................................................79
Accessing WebSphere Administrative Console..........................................................................................................81
Directory permissions...........................................................................................................................................................81
Preparing WebSphere Application Server ..........................................................................................................................82
Configuring the LiveCycle ES database connectivity......................................................................................................83
Next steps........................................................................................................................................................................................83
8
Configuring WebLogic Server................................................................................................... 84
Overview..........................................................................................................................................................................................84
LiveCycle ES requirements for WebLogic............................................................................................................................85
Installing WebLogic Server .......................................................................................................................................................85
Installing the J2SE SDK ...............................................................................................................................................................85
Creating the WebLogic Server domain ................................................................................................................................87
WebLogic Administration Server tasks.................................................................................................................................88
Starting Node Manager..............................................................................................................................................................89
Creating a new WebLogic Managed Server ......................................................................................................................89
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
8
Contents
7
Configuring WebLogic Server (Continued)
Configuring WebLogic Server..................................................................................................................................................90
Configuring anonymous admin look-up.......................................................................................................................90
Configuring WebLogic for Web Services.......................................................................................................................91
Configuring the classpath and JVM arguments..........................................................................................................92
Restarting WebLogic...................................................................................................................................................................93
Configuring the LiveCycle ES database connectivity......................................................................................................94
Next steps........................................................................................................................................................................................94
9
Upgrading the Database Server ............................................................................................... 95
Upgrading the MySQL database.............................................................................................................................................96
Creating the LiveCycle ES database ................................................................................................................................96
MySQL database server configuration ...........................................................................................................................97
Migrating the LiveCycle 7.x data to the LiveCycle ES database ............................................................................98
Upgrading SQL Server 2000 to SQL Server 2005 ..............................................................................................................99
Migrating LiveCycle data stored in a 4k pagesize tablespace on DB2......................................................................99
Next steps..................................................................................................................................................................................... 101
10 Creating the LiveCycle ES database .......................................................................................102
Creating a MySQL database .................................................................................................................................................. 102
Creating an Oracle database ................................................................................................................................................. 104
Creating a DB2 database ........................................................................................................................................................ 104
Creating a SQL Server database........................................................................................................................................... 106
Install the SQL Server database driver:........................................................................................................................ 106
Setting up SQL Server for LiveCycle ES ....................................................................................................................... 106
Increasing memory ...................................................................................................................................................... 106
Setting processor priority .......................................................................................................................................... 107
Increasing the recovery interval.............................................................................................................................. 107
Integrated Security....................................................................................................................................................... 107
Sizing your SQL Server database................................................................................................................................... 108
Creating the LiveCycle ES database ............................................................................................................................. 108
Creating the LiveCycle ES user in SQL Server ........................................................................................................... 108
Associating the LiveCycle ES user with the database............................................................................................ 109
Setting the isolation level for the LiveCycle ES database..................................................................................... 109
Next steps..................................................................................................................................................................................... 110
11 Migrating to LiveCycle ES Connector for EMC Documentum ..............................................111
Running LiveCycle Forms 7.x for Documentum with LiveCycle Forms ES ........................................................... 111
Supported Platforms.......................................................................................................................................................... 112
Migrating LiveCycle 7.x Forms for Documentum applications to LiveCycle ES........................................... 112
Developing new applications using samples ................................................................................................................. 114
12 Migrating to LiveCycle ES Connector for IBM FileNet...........................................................115
Running LiveCycle Forms 7.x Connector for FileNet with Forms ES....................................................................... 115
Supported Platforms.......................................................................................................................................................... 115
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES ............................................................... 116
Developing new applications using samples ................................................................................................................. 121
Index .........................................................................................................................................122
About This Document
This document provides the information required to prepare your server environment for upgrading
Adobe® LiveCycle® 7.x products to Adobe LiveCycle ES (Enterprise Suite) on JBoss® Application Server,
IBM® WebSphere® Application Server, or BEA WebLogic Server®.
This document contains several types of information:
●
Information about the changes in LiveCycle ES that may impact your upgrade planning and an
overview of how the upgrade process works, including an outline of the tasks involved.
●
All hardware and software requirements and configurations that must be already in place to ensure a
successful LiveCycle upgrade.
●
All the tasks that must be performed to ensure that the upgrade runs correctly with minimal server
downtime (including exporting LiveCycle 7.x configuration data, backing up the LiveCycle 7.x server,
and setting up the new application server and database, as required).
●
All tasks required to prepare the application server and database for installing LiveCycle ES, including
configuring the supported software versions.
Note: If you are planning to perform an upgrade using the turnkey method, you do not need to perform
many of the steps in this document. It is recommended that you review the sections
“Understanding the Changes in LiveCycle ES” on page 15. However, all preparatory information for
turnkey upgrades, including system requirements, are included in Upgrading to LiveCycle ES for JBoss
Using Turnkey at http://www.adobe.com /go/learn_lc_upgradeTurnkey.
The information in this document applies to upgrading the following LiveCycle 7.x products:
●
Adobe LiveCycle Assembler
●
Adobe LiveCycle Barcoded Forms
●
Adobe LiveCycle Business Activity Monitor
●
Adobe LiveCycle Connector for IBM
●
Adobe LiveCycle Document Security
●
Adobe LiveCycle Form Manager
●
Adobe LiveCycle Forms
●
Adobe LiveCycle PDF Generator
●
Adobe LiveCycle Policy Server
●
Adobe LiveCycle Print
●
Adobe LiveCycle Reader Extensions
●
Adobe LiveCycle Workflow
Additionally, this document contains information that helps you understand which solution components
in LiveCycle ES you need to install to correspond with the LiveCycle 7.x products from which you are
upgrading.
Note: The migration path for moving to LiveCycle Connector for FileNet or Adobe
LiveCycle Connector for EMC Documentum is described separately from the other LiveCycle
products. See“Migrating to LiveCycle ES Connector for EMC Documentum” on page 111 and
“Migrating to LiveCycle ES Connector for IBM FileNet” on page 115.
8
Adobe LiveCycle ES
About This Document
Preparing to Upgrade to LiveCycle ES
Who should read this document?
9
Who should read this document?
This guide provides information for administrators or developers responsible for preparing the application
and database servers for development, staging, and production environments prior to installing,
configuring, upgrading, and deploying LiveCycle ES. The information provided is based on the assumption
that anyone reading this guide is familiar with JBoss, WebLogic, or WebSphere application servers, Red
Hat® Linux®, SUSE™ Linux, Microsoft® Windows®, IBM AIX®, or Sun™ Solaris™ operating systems, MySQL,
Oracle®, DB2®, or SQL Server database servers, and web environments.
This document also provides general information about the upgrading process that helps users estimate
the resources required to upgrade a LiveCycle 7.x environment to LiveCycle ES. Readers interested in
high-level information about the upgrade process can read the following sections: “Understanding the
Changes in LiveCycle ES” on page 15 and “Planning for the Upgrade Process” on page 28.
Conventions used in this document
This guide uses the following naming conventions for common file paths.
Name
Default value
Description
[LiveCycleES root]
Windows:
C:\Adobe\LiveCycle8\
The installation directory that is used for all
LiveCycle ES solution components. The installation
directory contains subdirectories for Adobe
LiveCycle Configuration Manager, the
LiveCycle ES SDK, and each LiveCycle ES solution
component installed (along with the product
documentation). This directory also includes
directories relating to third-party technologies.
Linux:
/opt/adobe/livecycle8/
[LiveCycle7 root]
Windows:
C:\Adobe\LiveCycle\
Linux:
/opt/adobe/livecycle/
[appserver root]
The home directory of the
application server that runs
the LiveCycle ES services.
The installation directory that is used for all
LiveCycle 7.x products. The installation directory
contains subdirectories for product SDKs, and each
LiveCycle product installed (along with the product
documentation).
JBoss on Windows: C:\jboss
JBoss on Linux: /opt/jboss
WebSphere on Windows:
C:\IBM\WebSphere\AppServer
WebSphere on Linux and Solaris:
/opt/IBM/WebSphere/AppServer
WebSphere on AIX:
/usr/IBM/WebSphere/AppServer
WebLogic on Windows: C:\bea\weblogic92\
WebLogic on Linux and Solaris:
/opt/bea/weblogic92
WebLogic on AIX:
/usr/bea/weblogic92
Adobe LiveCycle ES
About This Document
Preparing to Upgrade to LiveCycle ES
Additional information
Name
Default value
BEA_HOME
The install directory for
WebLogic on Windows C:\bea
WebLogic as specified for the WebLogic on Linux and UNIX: /opt/bea
BEA_HOME environment
variable.
10
Description
[appserverdomain] The domain that you
configured on WebLogic.
WebLogic on Windows:
C:\bea\user_projects\domains\base_domain
WebLogic on Linux and UNIX:
/opt/bea/user_projects/domains/base_domain
[dbserver root]
The location where the
LiveCycle ES database server
is installed.
Depends on the database type and your
specification during installation.
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux and UNIX®). Any platform-specific information is indicated as required.
Additional information
The resources in this table can help you learn more about LiveCycle ES.
For information about
See
Performing the upgrade from LiveCycle 7.x
to LiveCycle ES
Upgrading to LiveCycle ES for JBoss at
http://www.adobe.com/go/learn_lc_upgradeJBoss
Upgrading to LiveCycle ES for WebSphere at
http://www.adobe.com/go/learn_lc_upgradeWebSphere
Upgrading to LiveCycle ES for WebLogic at
http://www.adobe.com/go/learn_lc_upgradeWebLogic
Performing the upgrade from LiveCycle 7.x
to LiveCycle ES using the turnkey method
Upgrading to LiveCycle ES for JBoss Using Turnkey at
http://www.adobe.com /go/learn_lc_upgradeTurnkey
Upgrading custom applications to
LiveCycle ES
Upgrading Applications to LiveCycle ES Using APIs at
http://www.adobe.com/go/learn_lc_upgradeProgrammer
Performing administrative tasks for
LiveCycle ES
Administering LiveCycle ES at
http://www.adobe.com/go/learn_lc_administration
Installing Adobe LiveCycle Workbench ES
Installing Your Development Environment at
http://www.adobe.com/go/learn_lc_installWorkbench
Other services and products that integrate
with LiveCycle ES
www.adobe.com
Patch updates, technical notes, and
additional information on this product
version
www.adobe.com/go/learn_lc_support
http://www.adobe.com/cfusion/knowledgebase/index.cfm
1
Introduction to Upgrading LiveCycle
This section provides information about the documentation available to help you understand the upgrade
process, as well as a high -level outline of the tasks involved in the upgrading LiveCycle 7.x products to
LiveCycle ES.
About the upgrade documentation
Several documents are available to help you upgrade your LiveCycle 7.x deployment to a LiveCycle ES
deployment:
●
Preparing to Upgrade to LiveCycle ES
●
Upgrading to LiveCycle ES for JBoss/WebSphere/WebLogic
●
Upgrading to LiveCycle ES for JBoss Using Turnkey
●
LiveCycle Configuration Manager Help
●
Upgrading Applications to LiveCycle ES Using APIs
Preparing to Upgrade to LiveCycle ES (this document)
This document contains all the information you need to prepare your system for upgrading from
LiveCycle 7.x to LiveCycle ES. It includes information on the following topics:
Understanding what has changed from LiveCycle 7.x to LiveCycle ES
LiveCycle ES consists of solution components that offer the functionality that was previously available in
LiveCycle 7.x products. Before upgrading, it is important to understand what solution components you
need to ensure that you can use all the same features in LiveCycle ES that you implemented in LiveCycle
7.x. See “Understanding the Changes in LiveCycle ES” on page 15.
Understanding what happens during the upgrade process
Upgrading from a LiveCycle 7.x environment to a LiveCycle ES environment requires a series of tasks, many
of which are automated by LiveCycle Configuration Manager. To gain an understanding of the automated
and manual tasks involved in upgrading, and how your system is affected, see “Planning for the Upgrade
Process” on page 28.
Hardware and software prerequisites
Many of the software requirements for LiveCycle 7.x have changed for LiveCycle ES. Before upgrading, you
must ensure that your hardware and software meets the requirements of LiveCycle ES. This process may
require updating your database and application servers in place on supported operating systems. You
should also determine whether any updates are required to ensure optimal performance for LiveCycle ES.
See “System requirements for LiveCycle ES” on page 33.
11
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Introduction to Upgrading LiveCycle
Upgrading to LiveCycle ES for JBoss, WebSphere, or WebLogic
12
Installation and deployment topology considerations
Depending on where your current LiveCycle server is running and where you intend to install LiveCycle ES,
there are some installation and deployment options you can consider. To find out about the conditions
associated with the different possible deployment topologies, see “Installation and deployment topology
considerations” on page 41.
Gathering the required information
During the upgrade process, you will be prompted to provide information about your LiveCycle 7.x server
and database, and the target LiveCycle ES environment. For a checklist of the information you will need
during the upgrade process, such as directory paths, file names, and passwords, see “Gathering
information required before you start” on page 42.
Preparing your environment for upgrade
Before you actually install LiveCycle ES and migrate LiveCycle 7.x data and configuration to it, you must
complete several tasks to prepare the LiveCycle ES environment. These tasks include exporting the
LiveCycle 7.x EAR files, backing up all LiveCycle 7.x data and resources, installing and configuring new
supported applications server, and upgrading the database server (if applicable; not all database servers
require upgrading).
This information is covered in the following sections:
●
“Exporting the LiveCycle 7.x EAR files” on page 45
●
“Backing Up the LiveCycle 7.x Environment” on page 47
●
“Configuring JBoss Application Server” on page 50
●
“Configuring WebSphere Application Server” on page 79
●
“Configuring WebLogic Server” on page 84
●
“Upgrading the Database Server” on page 95 (for upgrading LiveCycle Workflow, LiveCycle Form
Manager, LiveCycle Forms with User Management and Administrator, LiveCycle PDF Generator, or
LiveCycle Policy Server.)
●
“Creating the LiveCycle ES database” on page 102 (for upgrading LiveCycle 7.x products that do not
use a database. A database is required for LiveCycle ES.)
When you understand all of the relevant changes between LiveCycle 7.x and LiveCycle ES, and you have
completed all of the tasks described in this document, you can use one of the guides mentioned in the
next two sections to perform the actual upgrade.
Upgrading to LiveCycle ES for JBoss, WebSphere, or WebLogic
The documents Upgrading to LiveCycle ES for JBoss at http://www.adobe.com/go/learn_lc_upgradeJBoss,
Upgrading to LiveCycle ES for WebSphere at http://www.adobe.com/go/learn_lc_upgradeWebSphere, and
Upgrading to LiveCycle ES for WebLogic at http://www.adobe.com/go/learn_lc_upgradeWebLogic provide
the information you need to perform the actual installation and migration steps that make up the upgrade
process. Each guide is specific to the application server you are using.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Introduction to Upgrading LiveCycle
Upgrading to LiveCycle ES for JBoss Using Turnkey
13
Upgrading to LiveCycle ES for JBoss Using Turnkey
The Upgrading to LiveCycle ES for JBoss Using Turnkey document at
http://www.adobe.com /go/learn_lc_upgradeTurnkey includes all the steps required to upgrade to
LiveCycle ES for JBoss and MySQL from LiveCycle 7.x using the turnkey method. The turnkey method
automatically installs, configures, and upgrades the product.
You can upgrade using the turnkey method if you installed LiveCycle 7.x using turnkey and the
LiveCycle 7.x product or products are deployed to the JBoss instance that was included as part of the
turnkey installation.
Perform this type of upgrade to rapidly get a LiveCycle ES system up and running for small-scale
production, demonstration, evaluation, development, or training purposes. The turnkey method installs
and configures a default set of Adobe and third-party products that provide a functioning LiveCycle ES
environment.
Note: If you are planning to perform an upgrade using the turnkey method, you do not need to perform
many of the steps in this document (Preparing to Upgrade to LiveCycle ES). It is recommended that
you review the section “Understanding the Changes in LiveCycle ES” on page 15. However, all
preparatory information for turnkey upgrades, including system requirements, are included in
Upgrading to LiveCycle ES for JBoss Using Turnkey document.
LiveCycle Configuration Manager Help
Part of the upgrade is completed using LiveCycle Configuration Manager, a wizard-like tool that leads you
through the upgrade process, prompting you to input the required information. On each screen of
LiveCycle Configuration Manager, you can press the F1 key to view the Help dialog box for that screen.
For more information about LiveCycle Configuration Manager, see the Upgrading to LiveCycle ES guide for
your application server, described earlier in this section.
Upgrading Applications to LiveCycle ES Using APIs
The Upgrading Applications to LiveCycle ES Using APIs at
http://www.adobe.com/go/learn_lc_upgradeProgrammer document describes the overall API changes
for the LiveCycle services. It provides programmers with summary information that is useful when
upgrading LiveCycle 7.0, 7.1, and 7.2 client applications (designated by 7.x) to LiveCycle ES. It also provides
the mappings between the LiveCycle 7.x and LiveCycle ES APIs, including a mapping between LiveCycle
7.x product names and LiveCycle ES solution components.
Upgrading task outline
This section outlines the tasks involved in the upgrade process, from the planning stage to the
post-deployment stage. The order of the tasks differs slightly depending on whether the application
server on which LiveCycle ES will be deployed is installed on the same computer as the LiveCycle 7.x
computer or a separate computer.
If the LiveCycle ES target application server is installed on a different computer than LiveCycle 7.x, you can
do all the application server configuration steps before you begin the actual upgrade.
If the LiveCycle ES target application server is installed on the same computer as the LiveCycle 7.x server,
you are instructed to complete the application server configuration during the actual upgrade process.
Adobe LiveCycle ES
Introduction to Upgrading LiveCycle
Preparing to Upgrade to LiveCycle ES
Next steps
14
Because both application servers cannot be running at the same time on the same physical computer due
to port conflicts, performing the configuration tasks on the LiveCycle ES target server at the time when
you must stop the LiveCycle 7.x server will minimize server downtime.
To upgrade from LiveCycle 7.x to LiveCycle ES, you must complete the following tasks:
Task
See
Understand upgrade process (high-level section). “Understanding the Changes in LiveCycle ES” on
page 15
Understand the upgrade process and
implications for LiveCycle 7.x QPACs.
“Data and process compatibility” on page 19
Understand the upgrade implications of custom
applications and related APIs.
“Updating client applications” on page 29
Export LiveCycle 7.x EARs.
“Exporting the LiveCycle 7.x EAR files” on page 45
Configure new application servers.
Do this task now only if the LiveCycle 7.x server
and the target LiveCycle ES server are on different
computers.
“Configuring JBoss Application Server” on page 50
or “Configuring WebSphere Application Server” on
page 79 or “Configuring WebLogic Server” on
page 84
Back up all LiveCycle 7.x data, resources,
directories.
“Backing Up the LiveCycle 7.x Environment” on
page 47
Upgrade MySQL or SQL Server database server (if
LiveCycle 7.x product used User Management).
“Upgrading the Database Server” on page 95
Create database (if LiveCycle 7.x product did not
use a database).
“Creating the LiveCycle ES database” on page 102
Install LiveCycle ES.
Upgrading to LiveCycle ES for your application server
Run LiveCycle Configuration Manager to
configure LiveCycle ES and begin upgrading from
LiveCycle 7.x.
Upgrading to LiveCycle ES for your application server,
and LiveCycle Configuration Manager Help
Stop LiveCycle 7.x and configure new application
servers when instructed by the documentation.
The Upgrading to LiveCycle ES document for your
application server tells you when to do this step.
Do this task now only if LiveCycle 7.x server and
target LiveCycle ES server are on the same
computer.
The instructions in this guide describe the
configuration steps required.
Return to LiveCycle Configuration Manager,
complete the migration of data from LiveCycle
7.x to LiveCycle ES, and deploy LiveCycle ES to
the application server.
Upgrading to LiveCycle ES for your application server
and LiveCycle Configuration Manager Help
Repackage client applications as necessary.
Upgrading to LiveCycle ES for your application server
Next steps
Now you can find out more details about what changes have occurred between LiveCycle 7.x and
LiveCycle ES. See “Understanding the Changes in LiveCycle ES” on page 15.
2
Understanding the Changes in LiveCycle ES
To successfully upgrade from LiveCycle 7.x to LiveCycle ES, you must first understand what parts of your IT
organization are involved. This section provides the high-level information required to plan for your
upgrade. After reading this section, more technical readers can continue on to the rest of the document,
which describes the tasks that must be performed and the exceptions that must be considered to ensure a
successful upgrade.
How the LiveCycle ES upgrade protects your IT investment
The upgrade from LiveCycle 7.x to LiveCycle ES is designed to protect your investment in the forms,
processes, and applications that you have built around LiveCycle. By protecting that investment, an IT
administrator can, with a few exceptions, upgrade LiveCycle 7.x to LiveCycle ES without help from the form
authors who created your forms, the process authors who created your processes, and the Java™
developers who created custom applications for LiveCycle. After upgrading to LiveCycle ES, you can
immediately begin to take advantage of the value of LiveCycle ES, rather than having to recreate your
existing solutions.
The LiveCycle upgrade limits the changes so that they affect only the middle tier of your enterprise
infrastructure. If you are using Adobe Reader® with LiveCycle, your organization can continue to use the
existing version of Adobe Reader that you deployed across your clients. If you are using an Oracle or DB2
database in your data tier, you can continue to use it without changing the version. Keeping the LiveCycle
upgrade restricted to your middle tier minimizes the disruption to the rest of your enterprise
infrastructure.
How Adobe Reader is independent of LiveCycle
One of the key features of the upgrade is that the version of Adobe Reader on the client is independent of
the version of LiveCycle on the server. When LiveCycle ES renders a form, it renders it in the version of PDF
that you specify. You can create forms that work best in Adobe Reader 7.x, or you can use new features that
work best with Adobe Reader 8.0. Form authors are warned if they choose to use a feature that is not
appropriate for the particular version of Adobe Reader.
All forms render in LiveCycle ES in the same way that they rendered in LiveCycle 7.x. There are no
significant visible differences between a form rendered by either version of LiveCycle. All the scripts that
you added to your forms will work in LiveCycle ES in the same way that they worked with LiveCycle 7.x. In
addition to the LiveCycle ES features that support multiple versions of Adobe Reader, Adobe Reader itself
also works with multiple versions of LiveCycle. You can roll out Adobe Reader 8.x to your clients without
upgrading your server to LiveCycle ES. Adobe Reader 7.x and Adobe Reader 8.x are compatible with both
LiveCycle 7 and LiveCycle ES.
15
Adobe LiveCycle ES
Understanding the Changes in LiveCycle ES
Preparing to Upgrade to LiveCycle ES
About data, process, and API compatibility
16
About data, process, and API compatibility
On the server, all data will be automatically migrated so that it is available to LiveCycle ES. For example, all
LiveCycle Policy Server 7.x audit records and all historical process data are migrated so that users can run
queries that span the upgrade. The configuration information that LiveCycle ES needs is migrated from
LiveCycle 7.x product configurations to the equivalent areas of LiveCycle ES.
If you have created processes with LiveCycle Workflow 7.x, most processes continue to work without any
changes in LiveCycle ES. For example, if you have created a process that helps your business conform to a
government regulation, the process will work in LiveCycle ES as you originally designed it. For these and all
other processes that come from your LiveCycle 7.x system, end users can log in to the new
Adobe LiveCycle Workspace ES and see all of the processes in the state that they left them.
The APIs exposed in LiveCycle 7.x remain compatible in LiveCycle ES. During the upgrade process, a
compatibility layer is inserted into LiveCycle ES to allow you to use your existing code with LiveCycle ES.
The Java methods that you used in LiveCycle 7.x are maintained, the web service calls are present at the
same URL, and all other programmatic methods of access present in LiveCycle 7.x persist. The
compatibility layer ensures that your organization need not engage developers to upgrade your
LiveCycle 7.x system to LiveCycle ES.
There are some exceptions to the general statements above. Subsequent sections in this document
describe all of the exceptions and provide suggested solutions to each exception that you may encounter.
The next step in understanding the details of the upgrade from LiveCycle 7.x to LiveCycle ES is to
understand how the LiveCycle 7.x products map to the new LiveCycle ES solution components. The
LiveCycle architecture has been reorganized to use components. You must understand the new
components in order to understand where the features you used in LiveCycle 7.x can be found in
LiveCycle ES.
Mapping LiveCycle 7.x products to LiveCycle ES solution
components
The following table maps previous LiveCycle 7.x products with LiveCycle ES solution components.
Previous generation products
LiveCycle ES upgrade path
Additional information
LiveCycle Forms 7.x
Adobe LiveCycle Forms ES
Now dedicated to interactive form
generation in PDF, SWF, or HTML
files. Includes Flash-based Form
Guides and the next generation of
LiveCycle Assembler.
Customers who have Platinum
Maintenance and Support for
LiveCycle Forms 7.x will also receive a
copy of Output ES. Some of the
functionality that was previously
available in LiveCycle Forms 7.x has
now moved to Output ES.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Mapping LiveCycle 7.x products to LiveCycle ES solution components
Previous generation products
LiveCycle ES upgrade path
Additional information
LiveCycle Print 7.x
Adobe LiveCycle Output ES
Now dedicated to dynamic
generation of non-interactive
documents in PDF, PostScript®, PCL,
or ZPL format. Includes the next
generation of LiveCycle Assembler.
Customers who have Platinum
Maintenance and Support for
LiveCycle Print 7.x will also receive a
copy of Forms ES. Some of the
functionality that was previously
available in LiveCycle Print 7.x has
now moved to Forms ES.
LiveCycle PDF Generator 7.x (all
editions)
Adobe LiveCycle
PDF Generator ES
N/A
LiveCycle Assembler 7.x
Adobe LiveCycle
PDF Generator ES
PDF Generator ES is the standard
upgrade target for LiveCycle
Assembler, which is included.
Forms ES or Output ES are optional
upgrade targets.
LiveCycle Barcoded Forms 7.x
Adobe LiveCycle
Barcoded Forms ES
N/A
LiveCycle Barcoded Forms 7.x ST
Adobe LiveCycle Barcoded
Forms 7.5 ST and LiveCycle
Reader Extensions 7.2.2
N/A
LiveCycle Reader Extensions 7.x
Adobe LiveCycle
Reader Extensions ES
N/A
Flex Data Services 2
Departmental
Adobe LiveCycle
Data Services ES
Departmental
Not covered in this document.
Flex Data Services 2 Enterprise
Adobe LiveCycle
Data Services ES Enterprise
Not covered in this document.
LiveCycle Policy Server 7.x
Adobe LiveCycle
Rights Management ES
N/A
LiveCycle Document Security 7.x
Adobe LiveCycle
Digital Signatures ES
N/A
17
Adobe LiveCycle ES
Understanding the Changes in LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Compatibility between LiveCycle 7.x and LiveCycle ES
Previous generation products
LiveCycle ES upgrade path
Additional information
LiveCycle Workflow 7.x
Adobe LiveCycle
Process Management ES
Includes Adobe LiveCycle
Business Activity Monitoring ES,
Adobe LiveCycle Workspace ES, and
much of the functionality of
LiveCycle Form Manager.
LiveCycle Form Manager 7.x
Adobe LiveCycle
Process Management ES
LiveCycle Process Management ES
includes LiveCycle Workspace ES,
which contains the majority of
functionality of LiveCycle Form
Manager.
LiveCycle Designer 7.x
Adobe LiveCycle Designer ES
Not covered in this document.
Included with Adobe LiveCycle
Workbench ES, which is included
with all solution components.
LiveCycle Designer 8.0 is also sold
separately and bundled with Adobe
Acrobat 8.0.
Central Pro Output Server 5.6
LiveCycle Output ES
Available as an optional migration
for maintenance and support
customers who want to move to the
LiveCycle ES platform.
LiveCycle Forms for
Documentum
LiveCycle Connector for EMC
Documentum
Automatic upgrades from LiveCycle
Forms for Documentum to
LiveCycle ES are not supported.
See “Migrating to LiveCycle ES
Connector for EMC Documentum”
on page 111.
LiveCycle Forms for FileNet
LiveCycle
Connector for FileNet
Automatic upgrades from LiveCycle
Forms for FileNet to LiveCycle ES are
not supported.
See “Migrating to LiveCycle ES
Connector for IBM FileNet” on
page 115.
Compatibility between LiveCycle 7.x and LiveCycle ES
When you upgrade your LiveCycle software, you maintain compatibility on a number of levels:
●
Electronic forms and form clients are compatible.
●
Data, processes, and configuration settings are compatible.
●
Most APIs are compatible, without requiring developers to recompile their applications.
18
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Form and client compatibility
19
Form and client compatibility
Adobe has placed top priority on separating the LiveCycle server from the Adobe Reader client. This
separation now gives your IT organization the flexibility to decide when to upgrade your client,
independent of the server. As a result, forms developed for use with Adobe Reader 7.0 are still compatible
with LiveCycle ES.
In addition, forms that you developed for LiveCycle 7.x will work as designed with Adobe Reader 8.0 and
LiveCycle ES. When users open LiveCycle 7.x forms in Adobe Reader 8.0, the PDF version will not be
incremented unless the form uses new features specific to Adobe Reader 8.0. Forms that have a flowable
layout will render the same way in Adobe Reader 8.0 as they did in Adobe Reader 7.0.
In Designer ES, the form developer now has control over the target PDF and Adobe Reader version, and
can target a form for Adobe Reader 7.0.5 and later or for Adobe Reader 8.1. LiveCycle Designer ES
generates dynamic warnings about form features that do not match the target PDF version and checks
scripts for incompatibilities.
Some changes have been made in the HTML source between LiveCycle 7.x and LiveCycle ES due to the
addition of features and the use of short-hand notations for the various attributes in HTML streams in
LiveCycle ES.
Data and process compatibility
Changes to database schemas in LiveCycle ES have been kept to a minimum. Any changes in schemas are
automatically handled during the upgrade, and data is automatically migrated.
The schema changes imply changes to the Persistent Object Framework (POF), which comprises a thin
layer over the data schema. If you are using POF, you must examine the code for necessary changes. It is
recommended that you use the new Query and Queue Manager APIs.
Changes to registry tables do not affect your applications. LiveCycle 7.x appstore URI paths are respected
in LiveCycle ES. This issue applies to forms and form authors only when they use LiveCycle Form Manager.
LiveCycle 7.x processes are supported in LiveCycle ES after you upgrade. Long-running processes will
continue after the upgrade; users can open Workspace ES and see all of their processes in the same state
they were in before the upgrade.
LiveCycle 7.x QPACs have been replaced with LiveCycle ES components. Although processes that use
QPACs are currently supported by LiveCycle ES, you must upgrade LiveCycle 7.x QPACs to ensure
compatibility with future releases of LiveCycle ES. Using the Process Upgrade Tool included in
Workbench ES, you can upgrade the QPACs when you are ready.
The Encrypt for Recipients QPAC available with LiveCycle Document Security 7.x is not supported in
LiveCycle ES. In LiveCycle ES, you cannot encrypt a PDF document for individual users with their PKI public
certificate.
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.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
API compatibility
20
API compatibility
Most APIs used with LiveCycle 7.x are compatible with LiveCycle ES. All APIs are now deprecated; therefore,
you must port your applications to ensure compatibility in future releases of LiveCycle ES. For details about
the APIs that are deprecated, see Upgrading Applications to LiveCycle ES Using APIs at
http://www.adobe.com/go/learn_lc_upgradeProgrammer.
These APIs are not compatible with LiveCycle ES:
●
Task Manager
●
Queue Manager
●
Query Manager
●
Policy Server SPI
●
Existing POF calls
LiveCycle 7.x SOAP, EJB, and REST (for LiveCycle PDF Generator) interfaces are available in LiveCycle ES.
Enabling FIPS mode
LiveCycle ES provides a FIPS mode to restrict data protection to Federal Information Processing Standard
(FIPS) 140-2 approved algorithms using the RSA BSAFE Crypto-C 2.1 encryption module.
You can enable FIPS mode when you are configuring the product for deployment with
LiveCycle Configuration Manager. (See the section “Configuring LiveCycle ES for deployment” in the
Upgrading to LiveCycle ES document for you application server or the section “Upgrading LiveCycle 7.x
to LiveCycle ES” in Upgrading to LiveCycle ES for JBoss Using Turnkey at
http://www.adobe.com /go/learn_lc_upgradeTurnkey.)
You can also enable FIPS mode through the LiveCycle Administration Console after LiveCycle ES has been
deployed. (See the section “Post-Deployment Activities” in the Upgrading to LiveCycle ES document for you
application server or in Upgrading to LiveCycle ES for JBoss Using Turnkey at
http://www.adobe.com /go/learn_lc_upgradeTurnkey.)
The following services are affected by FIPS enablement: Encryption service, Signature service, Assembler
service, and Reader Extensions service. PDF password encryption is not permitted in FIPS mode;
specifically, encrypting with RC4 is disabled when FIPS mode is enabled. You can decrypt older files that
may have been encrypted with non-FIPS approved algorithms. Using non-FIPS approved algorithms in
signing or certification causes the operation to fail. However, you can validate signatures created with
these algorithms. For the Assembler and Reader Extensions services, password-based encryption (that is,
saving with open passwords) is disabled.
FIPS mode does not support Adobe Acrobat® versions earlier than 7.0. If FIPS mode is enabled and the
processes Encrypt With Password and Remove Password include the Acrobat setting Acrobat 5, the
process fails.
Note: LiveCycle software does not validate code to ensure FIPS compatibility. It provides a FIPS operation
mode so that FIPS-approved algorithms are used for cryptographic services from the FIPS-approved
libraries (RSA).
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Upgrading your infrastructure
21
Upgrading your infrastructure
Changes in platform support for LiveCycle ES may significantly affect your upgrade.
For complete details about supported platforms, see “System requirements for LiveCycle ES” on page 33.
Supported operating systems
These operating systems are supported for LiveCycle ES:
●
Microsoft Windows Server® 2003 Enterprise Edition or Standard Edition SP1 and R2 (32-bit edition only)
●
(LiveCycle Workbench ES) Windows XP Service Pack 2
●
Solaris 9 and 10
●
AIX 5L 5.3
●
SUSE Linux Enterprise Server 9.0 (32-bit edition only)
●
Red Hat Enterprise Linux AS or ES 4.0 (32-bit edition only)
Supported application servers
When you upgrade from LiveCycle 7.x, you must install a parallel application server for LiveCycle ES. This
parallel application server is required because LiveCycle ES supports a different set of application server
versions than previous releases. A parallel installation allows you to return to LiveCycle 7.x more easily if
you experience problems with your upgrade.
These application servers are supported:
●
JBoss Application Server 4.0.3 SP1
●
WebLogic Server 9.2 (Advantage and Premium editions)
●
WebSphere Application Server 6.1.05 (Base and Network Deployment editions)
Java 5 is the only supported Java Virtual Machine (JVM) for all LiveCycle ES application servers. Some
customer code and custom QPACs may need to be recompiled, repackaged, or both. For information
about incompatibilities between Java 1.4 and Java 5, see
http://java.sun.com/j2se/1.5.0/compatibility.html.
Supported databases
These databases are supported:
●
DB2 8.2 or IBM DB2 8.1 FixPack 7
●
Oracle 9i
●
Oracle 10g
●
MySQL 5
●
Microsoft SQL Server 2005 SP1
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Upgrading your LiveCycle 7.x products
22
It is strongly recommended that you back up your database prior to upgrading to LiveCycle ES. If you are
running MySQL 4.1 or Microsoft SQL Server 00, you must upgrade your database when you upgrade to
LiveCycle ES:
●
Microsoft SQL Server 2000 to Microsoft SQL Server 2005 SP 1
●
MySQL 4.1 to MySQL 5.0, if you are not doing the turnkey upgrade
See “Upgrading the Database Server” on page 95 for more information.
If you are running Oracle 9i or DB2, you do not need to upgrade the database when you upgrade to
LiveCycle ES.
If you are concerned about losing active data when LiveCycle 7.x is shut down, you must manually look at
the Java Message Service (JMS) queues to determine what data is remaining. For instructions, consult your
application server documentation.
Upgrading your LiveCycle 7.x products
Each LiveCycle 7.x product has particular considerations for upgrading.
For more information about API compatibility, see Upgrading Applications to LiveCycle ES Using APIs at
http://www.adobe.com/go/learn_lc_upgradeProgrammer for descriptions of the API mappings.
General considerations for upgrading LiveCycle 7.x products
The SSL over IIOP is not supported in LiveCycle ES. When you upgrade LiveCycle 7.x to LiveCycle ES, SSL
over IIOP is disabled.
The SOAP-with-Attachments (SwA) web service attachment format supported in LiveCycle 7.x is not
supported in LiveCycle ES. Workflows that use this web service interface in LiveCycle ES with Document
variables will not work.
Upgrading User Management
Administrative users that are created in User Manager on the LiveCycle 7.x server are not migrated to the
LiveCycle ES database during the upgrade. You can use the default administrator account in LiveCycle ES
to create new administrative users in the LiveCycle Administration Console. See “Accessing User
Management” in the Upgrading to LiveCycle ES document for your application server.
In LiveCycle ES, Rights Management ES and Process Management ES now share a common user database;
therefore, there is only one User Management component. However, the upgrade will not merge LiveCycle
products that are on different servers.
Note: Some restrictions apply to upgrading multiple LiveCycle 7.x products that use User Management.
The details are described in the next section, Upgrading LiveCycle 7.x products that use
User Management.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Upgrading LiveCycle 7.x products that use User Management
23
Upgrading LiveCycle 7.x products that use User Management
You cannot upgrade LiveCycle Policy Server 7.x and another LiveCycle 7.x product that uses
User Management to the same instance of LiveCycle ES. This restriction includes LiveCycle Workflow,
LiveCycle Form Manager, LiveCycle PDF Generator, and LiveCycle Forms with User Management and
Administrator.
In LiveCycle 7.x, two different user databases are used—one for LiveCycle Policy Server 7.x and another for
the other LiveCycle 7.x products that use User Management. In LiveCycle 7.x, it was possible to select a
different LDAP configuration for either set of products. The upgrade cannot automatically merge the two
sets of users together.
For example, if you are running LiveCycle Policy Server 7.x and LiveCycle PDF Generator 7.x and plan to
upgrade both products, you must run two separate upgrades, resulting in two separate LiveCycle ES
servers pointing to two separate databases—one hosting Rights Management ES and the other hosting
PDF Generator ES.
You can, however, upgrade LiveCycle Workflow, LiveCycle Form Manager, LiveCycle PDF Generator 7.x, and
LiveCycle Forms 7.x with User Management and Administrator together to the same LiveCycle ES server.
Upgrading LiveCycle Workflow
After upgrading LiveCycle 7.x to LiveCycle ES, LiveCycle 7.x workflows and run-time data are persisted in
the LiveCycle ES database. LiveCycle ES supports LiveCycle 7.x workflows, which can continue to operate
without modification. However, to take advantage of new features that LiveCycle ES services provide, you
can upgrade workflows so that QPAC-based actions are replaced with equivalent LiveCycle ES service
operations.
It is necessary to eventually migrate all processes that use LiveCycle 7.x QPACs to use new LiveCycle ES
components to ensure that processes remain compatible with future releases of LiveCycle ES. The Process
Upgrade Tool is part of Workbench ES, and you can use it at any time to upgrade a LiveCycle 7.x QPAC to a
LiveCycle ES service component. Only Adobe-provided QPACs can be upgraded using the Process
Upgrade Tool.
You can upgrade custom QPACs by creating an upgrade definition file that is used by the Process Upgrade
Tool. The upgrade definition file describes how the customer QPAC created in LiveCycle 7.x maps to a
LiveCycle ES service component.
Upgrading LiveCycle Barcoded Forms QPACs is not supported by Process Upgrade Tool.
LiveCycle Policy Server QPACs will be supported in a future release of LiveCycle ES.
Note: When a LiveCycle 7.x workflow that generates CSS2HTML is upgraded to a LiveCycle ES process
using the Process Upgrade Tool in Workbench ES, the upgraded process outputs XHTML instead of
CSS2HTML.
Although Custom QPACs work in LiveCycle ES processes, compatibility issues with Java 5 may exist. If your
custom QPACs use customized application server or database functionality, you must review the QPAC
code to determine whether they need to be recompiled and redeployed. Upgraded processes should be
tested in a staging environment before deployment to a production system.
Adobe LiveCycle ES
Understanding the Changes in LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Upgrading LiveCycle Business Activity Monitor
24
Upgrading LiveCycle Business Activity Monitor
When you upgrade LiveCycle Business Activity Monitor 7.x to LiveCycle Business Activity Monitoring ES,
custom dashboards are not migrated and must be manually recreated after the upgrade. If you have
customized these dashboards extensively, contact Adobe support for assistance on updating these.
If you have not modified the default dashboards, you can use the new dashboards in
Business Activity Monitoring ES without issues. If you modified any of the default dashboards, you will
need to manually re-create the modifications after you upgrade to Business Activity Monitoring ES.
Customizations of display items in LiveCycle Business Activity Monitor 7.x, such as color or layout, are not
migrated to Business Activity Monitoring ES. These modifications must be reapplied manually by each
user.
Upgrading LiveCycle Form Manager
In LiveCycle ES, the Workspace ES solution component replaces LiveCycle Form Manager. Workspace ES
introduces many new features that you can read about in LiveCycle ES Overview, and Workspace ES Help.
Some features specific to LiveCycle Form Manager 7.x are no longer available in Workspace ES:
●
Full-text searching of task data is not available.
●
Favorites/Preferences are not available.
●
Category tree depth is limited to one level. (Top-level categories in LiveCycle Form Manager are
upgraded. Endpoints in subcategories are converted to top-level categories.) This limit results in the
following upgrade conditions:
●
●
Empty categories are converted to upgradedCategories.xml, but are not created as LiveCycle ES
categories.
●
Categories containing a loose form only are converted into upgradedCategories.xml, but are not
created as LiveCycle ES categories.
●
When an init-form (a form used in a workflow) is assigned to several categories, only the top-level
category that contains the init-form and one endpoint are created.
Loose forms (those not associated with a workflow) are not supported. All loose forms created in
LiveCycle 7.x are upgraded to the LiveCycle ES repository, but no endpoint is created. Any running or
historical data for loose forms, such as the form saved in Draft or completed in Archived folders, is not
persisted.
If you created custom interfaces for LiveCycle Form Manager 7.x, some manual updates to code may be
required.
Although changes to database schemas in LiveCycle ES have been kept to a minimum and any changes in
schemas are automatically handled during the upgrade, the schema changes imply changes to the
Persistent Object Framework (POF), which comprises a thin layer over the data schema. If you are using
POF, you must examine the code for necessary changes. It is recommended that you use the new Query
and Queue Manager APIs.
Changes to registry tables do not affect your applications. LiveCycle 7.x xappstore URI paths are respected
in LiveCycle ES. This issue applies to forms and form authors only when they use LiveCycle Form Manager.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Upgrading LiveCycle Reader Extensions
25
Upgrading LiveCycle Reader Extensions
The turnkey upgrade for LiveCycle Reader Extensions is automatic. You will require a new certificate that is
installed as part of the upgrade process. Customers who have Platinum Maintenance and Support will
receive this new certificate as part of the fulfillment process.
The usage rights applied by Reader Extensions ES are only recognized in Adobe Reader 7.0, 8.0, and later.
Authentication for the Reader Extensions ES end-user interface is now controlled by User Manager in
LiveCycle ES. It is no longer restricted to the application server security.
LiveCycle Reader Extensions 7.x does not use a database; therefore, you do not need to migrate data
during the upgrade. However, you must create a database for LiveCycle ES. See “Supported software” on
page 35 for databases supported in LiveCycle ES. See “Creating the LiveCycle ES database” on page 102 for
information about creating a LiveCycle ES database.
The APIs are backwards compatible, and the LiveCycle QPACs are generally supported in LiveCycle ES. (See
“Data and process compatibility” on page 19.)
Upgrading LiveCycle Forms and LiveCycle Print
LiveCycle Print has been replaced by Output ES. You do not need to recreate existing forms for use with
Forms ES and Output ES; form rendering is the same as for LiveCycle 7.x.
You can continue to target earlier versions of PDF and Adobe Reader. The XCI and XDC files are also
compatible.
The APIs are backwards compatible, and the LiveCycle 7.x QPACs are generally supported in LiveCycle ES.
(See “Data and process compatibility” on page 19.)
When you upgrade from LiveCycle Forms 7.x (installed without User Management and Administrator), any
forms settings you customized in the forms administration interface are lost, and the default form settings
are restored. This occurs because these settings are not stored in a database. You must reset form settings
using the LiveCycle Administration Console.
Upgrading LiveCycle Barcoded Forms
Existing LiveCycle 7.x Barcoded Forms QPACs continue to work after the LiveCycle Workflow upgrade. Only
LiveCycle Barcoded Forms Decoder Agent QPAC is updated during upgrade. The new Decoder Agent
component is Java-based and does not use the C++ Decoder Service and associated dongle that were
required in LiveCycle 7.x.
Although LiveCycle 7.x Barcoded Forms QPACS are consolidated into a smaller number of service
components in LiveCycle ES, there is no loss of functionality because some functionality is now directly
derived from the LiveCycle ES infrastructure (for example, xpath expressions). Because of this
redistribution of the functionality and because the interface has changed, the Process Mapping Tool used
to upgrade LiveCycle 7.x QPACs to LiveCycle ES service components cannot upgrade the Barcoded Forms
QPACS automatically and manual upgrade work is required. (See Upgrading to LiveCycle ES for JBoss at
http://www.adobe.com/go/learn_lc_upgradeJBoss.)
Watched folders associated with LiveCycle Barcoded Forms 7.x are migrated during the upgrade process. If
the folders contain data at the time of the upgrade, the data will be processed when LiveCycle ES is started
and the new scheduler is upgraded using the manual steps outlined in the “Post-Deployment Activities”
section of Upgrading to LiveCycle ES for JBoss at http://www.adobe.com/go/learn_lc_upgradeJBoss.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Upgrading LiveCycle Policy Server
26
Upgrading LiveCycle Policy Server
The turnkey upgrade for LiveCycle Policy Server is automatic. Instances of LiveCycle Policy Server that exist
on separate nodes will not be automatically merged with other LiveCycle product infrastructure.
Adobe Reader 7.0 and Acrobat 7.0 can connect with Rights Management ES.
Rights Management ES shares the User Management database with Process Management ES and the rest
of the LiveCycle ES solution components.
Note: If LiveCycle Workflow or another User Management product is used on the same system as
LiveCycle Policy Server, you cannot upgrade both products to LiveCycle ES on the same server.
The Service Provider Interface (SPI) interface is not compatible with LiveCycle ES. However, rewriting your
code to the new SPIs should not be time-consuming because the new interfaces are similar to the old
ones.
LiveCycle Policy Server QPACs will be supported in a future release of LiveCycle ES.
Upgrading LiveCycle Document Security Server
When you upgrade, the Trust Store is automatically migrated to the LiveCycle ES equivalent. You must
have the credential aliases and their certificate passwords during the upgrade. If you are using Hierarchical
Storage Management (HSM), you must manually migrate the configuration. See Upgrading to LiveCycle ES
for your application server for information about migrating HSM content.
The APIs are backwards compatible, and the LiveCycle 7.x QPACs are generally supported in LiveCycle ES.
(See “Data and process compatibility” on page 19.)
Note: The Encrypt for Recipients QPAC available with LiveCycle Document Security 7.x is not supported in
LiveCycle ES. In LiveCycle ES, you cannot encrypt a PDF document for individual users with their PKI
public certificate.
Upgrading LiveCycle PDF Generator
To avoid data loss, ensure that your conversion queues are clear before you upgrade LiveCycle PDF
Generator.
LiveCycle ES includes a new implementation of the Watched Folder component that is common to all
services. The LiveCycle PDF Generator 7.x watched folder configuration is automatically migrated to
LiveCycle ES when you upgrade.
Specific APIs, such as the REST APIs, web services, and EJB-based APIs, are present in LiveCycle ES for
compatibility. The APIs are backwards compatible, and the LiveCycle 7.x QPACs are generally compatible in
LiveCycle ES. (See “Data and process compatibility” on page 19.)
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Understanding the Changes in LiveCycle ES
Upgrading LiveCycle Assembler
27
Upgrading LiveCycle Assembler
LiveCycle ES includes a new implementation of Watched Folder that is common to all services.
No changes are required to your DDX files.
Note: Due to an issue in WebLogic, client applications created for LiveCycle Assembler 7.x are not
supported in LiveCycle ES running on WebLogic. To continue to use these applications, they must
be manually updated to use LiveCycle ES APIs. A fix for this incompatibility will be included in a
future release. For information about updating LiveCycle 7.x APIs to LiveCycle ES APIs, see
Upgrading Applications to LiveCycle ES Using APIs at
http://www.adobe.com/go/learn_lc_upgradeProgrammer.
LiveCycle Assembler QPACs will be supported in LiveCycle ES. They should be updated using the Process
Upgrade Tool.
3
Planning for the Upgrade Process
This section helps you to understand how the upgrade process works, and provides the information that
you need before you begin upgrading to LiveCycle ES, including system requirements, deployment
topology information, and a list of the data you need to have at hand during upgrading.
The following topics discussed in this section include:
●
“Overview of the upgrade process” on page 28
●
“Updating client applications” on page 29
●
“System requirements for LiveCycle ES” on page 33
●
“Installation and deployment topology considerations” on page 41
●
“Gathering information required before you start” on page 42
Overview of the upgrade process
Upgrading from LiveCycle 7.x to LiveCycle ES does not replace the LiveCycle 7.x server. Instead,
LiveCycle ES is installed on the same or a separate computer as the LiveCycle 7.x server, and deployed to a
new application server installed in parallel (on the same or a separate computer) to the LiveCycle 7.x
server. Configuration settings, user data, and job information is migrated from the LiveCycle 7.x EAR files to
LiveCycle ES. If the LiveCycle 7.x product or products used a database, the upgrade process may also
involve upgrading the database server (if you are using MySQL or SQL Server), and migrating data from the
LiveCycle 7.x database to the LiveCycle ES database.
Many of the tasks in the upgrade process are automated and performed (with some user input) by
LiveCycle Configuration Manager. LiveCycle Configuration Manager is a wizard-like tool used to configure,
deploy, and validate LiveCycle ES components for deployment to the application server. When run in
upgrade mode, LiveCycle Configuration Manager also performs upgrade tasks such as applying
configuration settings and data from LiveCycle 7.x EAR files to the LiveCycle ES configuration, applying a
compatibility layer to ensure backward compatibility with existing custom applications developed in
LiveCycle 7.x, and migrating fonts from LiveCycle 7.x to LiveCycle ES.
Some upgrade tasks are manual; they need to be performed by an administrator. These tasks include all
the environment preparation tasks that are described in this guide, such as exporting the LiveCycle EAR
files from the LiveCycle 7.x deployment, installing and configuring new application servers, upgrading
databases and migrating the data, stopping and restarting the server when necessary, and importing trust
credentials from the LiveCycle.7.x Trust Manager Module.
The running LiveCycle 7.x system does not have to be accessible to LiveCycle Configuration Manager
during the upgrade. The LiveCycle 7.x EAR files and the LiveCycle 7.x database must be available to
LiveCycle Configuration Manager during the upgrade process.
If LiveCycle 7.x and LiveCycle ES server are located on the same computer, the LiveCycle 7.x server must be
stopped when it is time to migrate the essential data.
When the upgrade and deployment is complete, there are several post-deployment tasks to complete. For
example, if you upgraded LiveCycle Policy Server to Rights Management ES, you must enable SSL on the
application server. Instructions for post-deployment tasks are described in the Upgrading to LiveCycle ES
document for your application server.
28
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Planning for the Upgrade Process
How LiveCycle Configuration Manager upgrades LiveCycle 7.x to LiveCycle ES
29
How LiveCycle Configuration Manager upgrades LiveCycle 7.x to LiveCycle ES
LiveCycle Configuration Manager does the following tasks to upgrade LiveCycle 7.x to LiveCycle ES:
1. Extracts configuration settings from the LiveCycle 7.x EAR files and imports them into LiveCycle ES.
Some of the information is imported to the new LiveCycle ES EAR files and some into the new
LiveCycle ES database. (You create the LiveCycle ES database as a preparatory step using instructions
provided later in this document.)
For LiveCycle Policy Server upgrades, configuration settings are migrated during critical data migration
(step 4, below).
2. Inserts the compatibility layer into the LiveCycle ES EAR file. (See “About the compatibility layer” on
page 29.)
The compatibility layer is not applied to the upgrade of LiveCycle Policy Server only.
3. Performs in-place data migration for all LiveCycle 7.x products that use a database, with the exception
of LiveCycle Policy Server.
4. Migrates LiveCycle Policy Server data to the LiveCycle ES database from the LiveCycle Policy Server
database.
5. Migrates LiveCycle Policy Server audit records from LiveCycle 7.x to LiveCycle ES
About the compatibility layer
The compatibility layer consists of the Enterprise JavaBeans™ (EJBs), classes, servlets, and CORBA APIs that
are deprecated in LiveCycle ES but are used by custom applications developed for LiveCycle 7.x. When
present in the LiveCycle ES deployment, the compatibility layer ensures that custom applications
developed for LiveCycle 7.x continue to work with LiveCycle ES.
Note: The contents of the compatibility layer are deprecated and included for backward compatibility only.
For information about how upgrading to LiveCycle ES affects existing applications at the API level, see the
Upgrading Applications to LiveCycle ES Using APIs document.
Updating client applications
Client applications developed with LiveCycle 7.x that will be deployed to LiveCycle ES running on JBoss
must be updated to delete the DocumentServicesLibrary.jar file. If a client application is packaged as a
WAR file, or a WAR file within an EAR file, the DocumentServicesLibrary.jar file is typically located in the
/WEB-INF/lib directory within the WAR file. If the client application is packaged as an EAR file, the
DocumentServicesLibrary.jar file is typically located at the root level of the EAR file.
Client applications developed with LiveCycle 7.x may also need to be updated with new client JAR files in
the following situations:
●
LiveCycle 7.x client applications for JBoss are running remotely from the LiveCycle 7.x server.
●
LiveCycle 7.x client applications running on WebSphere use the um-client.jar or are stand-alone and
running on Java 1.4.
●
LiveCycle 7.x client applications are written for LiveCycle Forms 7.0 or 7.1 (pre-7.2) running on
WebSphere.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Planning for the Upgrade Process
Updating client applications
30
Stand-alone client applications on JBoss
Client applications developed with LiveCycle 7.x that run remotely from the LiveCycle 7.x server include
the jbossall-client.jar from JBoss 3.2.5. This file is not forward compatible with JBoss 4.0.3, which is the
version supported in LiveCycle ES. To ensure that remote LiveCycle 7.x client applications remain
compatible with LiveCycle ES, you must replace the jbossall-client.jar file from JBoss 3.2.5 with the
jbossall-client.jar file from JBoss 4.0.3.
The new jbossall-client.jar file is located in the [JBoss4_ root]/jboss/client directory. In the LiveCycle ES
turnkey installation, the [JBoss4_root] directory is located in the [LiveCycleES root] installation directory
after you have installed LiveCycle ES.
If you are upgrading LiveCycle Policy Server 7.x to Rights Management ES, you must load the
namespace.jar file before jbossall-client.jar by specifying the order in the classpath. The jbossall-client.jar
from JBoss 4.0.3 packages the NamespaceContext.class, which conflicts with the namespace.jar file used in
the LiveCycle Policy Server 7.x Java SDK. (The jbossall-client.jar file in JBoss 3.2.5 does not include this class
file.)
Client applications on WebSphere
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. When
LiveCycle ES has been installed, the new um-client.jar file is located in the
[LiveCycleES root]/LiveCycle_ES_SDK/client-libs/common directory.
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 on WebSphere
LiveCycle Forms client applications 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
It is recommended that you update the client applications to point to these JAR files.
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
LiveCycle Assembler client applications on WebLogic
31
LiveCycle Assembler client applications on WebLogic
Due to an issue in WebLogic, client applications created for LiveCycle Assembler 7.x are not supported in
LiveCycle ES running on WebLogic. To continue to use these applications, they must be manually updated
to use LiveCycle ES APIs. A fix for this incompatibility will be included in a future release. For information
about updating LiveCycle 7.x APIs to LiveCycle ES APIs, see Upgrading Applications to LiveCycle ES Using
APIs at http://www.adobe.com/go/learn_lc_upgradeProgrammer.
Updating LiveCycle QPACs
Upgrading LiveCycle Workflow 7.x to Process Management ES will be supported in a future release of
LiveCycle ES. At that time, you can upgrade LiveCycle QPACs. A tool will be available within Workbench ES
to automate the QPAC upgrade. LiveCycle 7.x QPACs can run in LiveCycle ES without modifications so that
you can run the QPAC upgrade tool when you are ready.
Transferring IP address and host name
You may choose to upgrade your server hardware based on the software and hardware requirements for
LiveCycle ES. If you deploy LiveCycle ES on new hardware, you must transfer the IP address and host name
from the computer on which LiveCycle 7.x was running in order to maintain backward compatibility with
existing applications. Otherwise, URLs used in existing collateral and resources, such as existing
policy-protected documents or web service calls, will fail when run against LiveCycle ES.
Third-party infrastructure support
This section summarizes the referenced platform and database combinations for JBoss Application Server
4.0.3 SP1, BEA WebLogic Server® 9.2, and IBM WebSphere® Application Server 6.1.0.5. For a complete list of
supported software on each operating system, see “Supported software” on page 35.
Microsoft Windows Server
LiveCycle ES supports the following Microsoft Windows operating system:
●
Microsoft Windows Server® 2003, Enterprise Edition SP1, Standard Edition SP1, R2 (32 bit architectures
and VMWare ESX/GSX)
The following table lists the supported application server, JDK, and database configurations for this
operating system:
Application server
JDK
Database
Red Hat JBoss Application Server
4.0.3 SP1
Sun JDK 5.0 Update 11
or later updates to 5.0
●
MySQL 5.0
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP1
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Red Hat Enterprise Linux and SUSE Linux
Application server
JDK
Database
BEA WebLogic® 9.2, (Advantage &
Premium)
BEA JRockit® JDK
●
IBM WebSphere 6.1.0.5 (Base &
Network Deployment Edition)
JDK supplied with
application server
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP1
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP1
Note: For a detailed list of the supported database editions see “Supported software” on page 35.
Red Hat Enterprise Linux and SUSE Linux
LiveCycle ES supports the following Red Hat Enterprise Linux and SUSE Linux operating systems:
●
Red Hat Enterprise Linux AS or ES 4.0 (32 bit architectures)
●
SUSE Linux Enterprise Server 9.0 (32 bit architectures)
The following table lists the supported application server, JDK, and database configurations for these
operating systems:
Application server
JDK
Database
Red Hat JBoss Application Server
4.0.3 SP1
Sun JDK 5.0 Update 11
or later updates to 5.0.
●
MySQL 5.0
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
BEA WebLogic 9.2 (Advantage &
Premium)
BEA JRockit JDK
●
Oracle 9i, 10g
IBM WebSphere 6.1.0.5 (Base &
Network Deployment Edition)
JDK supplied with
application server
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
Note: For a detailed list of the supported database editions see “Supported software” on page 35.
IBM AIX
LiveCycle ES supports the following IBM AIX operating system:
●
IBM AIX 5L 5.3
The following table lists the supported application server, JDK, and database configurations for this
operating system:
Application server
JDK
Database
IBM WebSphere 6.1.0.5 (Base &
Network Deployment Edition)
JDK supplied with
application server
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
Note: For a detailed list of the supported database editions see “Supported software” on page 35.
32
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Sun Solaris
33
Sun Solaris
LiveCycle ES supports the following Sun Solaris operating systems:
●
Solaris 9, 10 (SPARC® Architectures)
The following table lists the supported application server, JDK, and database configurations for these
operating systems:
Application server
JDK
Database
BEA WebLogic 9.2 (Advantage &
Premium)
Sun JDK supplied with
application server
●
Oracle 9i, 10g
IBM WebSphere 6.1.0.5 (Base &
Network Deployment Edition)
JDK supplied with
application server
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
Note: For a detailed list of the supported database editions see “Supported software” on page 35.
System requirements for LiveCycle ES
The following tables list the software and hardware requirements for installing and running LiveCycle ES.
Many of the requirements are different (more current) than the software and hardware requirements for
LiveCycle 7.x. You must ensure that the target system on which you will be deploying LiveCycle ES meets
the minimum system requirements.
The most important software changes that affect your upgrade from LiveCycle 7.x to LiveCycle ES are
application server requirements and the corresponding Java SDK support, and database server
requirements.
Application server upgrade
The application server required for LiveCycle ES must be installed in parallel to the application server
hosting LiveCycle 7.x. It can be installed on the same computer (if the hardware requirements are met) or
on a separate computer. The important thing is that the LiveCycle ES application server should not replace
the LiveCycle 7.x application server.
Java SDK upgrade
Because LiveCycle ES supports Java 5 instead of Java 1.4, you may need to update your LiveCycle 7.x
applications to include the client JAR for the new application server, depending on the application server
you use. (See “Updating client applications” on page 29.)
For information about the incompatibilities in Java 5 since Java 1.4.2, see the following page on the Sun
Developer Network website: http://java.sun.com/j2se/1.5.0/compatibility.html.
Database upgrade
Depending on the LiveCycle 7.x products that you are upgrading, you must either upgrade your current
LiveCycle database, or install and configure a new database, for use with LiveCycle ES. However, if you are
using Oracle 9i or 10g, or IBM DB2, you do not need to upgrade your database or install a new one because
these database servers continue to be supported in LiveCycle ES.
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Minimum hardware requirements
34
If the LiveCycle 7.x product(s) that you are upgrading do not include User Management and therefore do
not use a database, you must create a LiveCycle ES database by following the instructions in “Creating the
LiveCycle ES database” on page 102. See “Supported software” on page 35 for a list of supported database
servers.
These LiveCycle 7.x products do not use a database and will require a LiveCycle ES database to be created:
●
LiveCycle Reader Extensions
●
LiveCycle Document Security
●
LiveCycle Forms installed without User Management and Administrator
●
LiveCycle Print
●
LiveCycle Assembler
If you are upgrading LiveCycle PDF Generator or LiveCycle Forms installed with User Management and
Administrator and using a MySQL or SQL Server 2000 database server, you must upgrade the database
server. For MySQL, this process involves installing a new parallel MySQL database server and migrating the
LiveCycle 7.x data to it. For SQL Server 2000, you can upgrade to SQL Server 2005 in-place and the data is
migrated automatically by the Microsoft upgrade program.
If you are upgrading LiveCycle Policy Server to Rights Management ES, you must create a LiveCycle ES
database by following the instructions in “Creating the LiveCycle ES database” on page 102 (not
applicable to turnkey upgrades). During the upgrade process, LiveCycle Configuration Manager migrates
all the data from the LiveCycle Policy Server database to the new LiveCycle ES database.
Note: Whether or not you are upgrading your database, you must back up the current database before
beginning the upgrade. (See “Backing Up the LiveCycle 7.x Environment” on page 47.)
Minimum hardware requirements
This table provides the minimum hardware requirement supported by LiveCycle ES.
Operating system
Minimum hardware requirement
Microsoft Windows Server 2003 Enterprise
Edition or Standard Edition SP1 and R2
(32-bit edition only)
Intel® Pentium® 3 or x86 equivalent, 1 GHz processor
VMWare ESX and GSX
RAM - 2 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
Sun Solaris 9 and 10
Sun UltraSPARC® IIe, 650 MHz processor
RAM - 2.5 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
IBM AIX 5L 5.3
P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHz
processor
RAM - 2.5 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Intel x86 compatibility
Operating system
Minimum hardware requirement
SUSE Linux Enterprise Server 9.0 i386
(32-bit edition only)
Pentium 3 or x86 equivalent, 1 GHz processor
RAM - 2.5 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
Red Hat Enterprise Linux AS or ES 4.0
(32-bit edition only)
Pentium 3 or x86 equivalent, 1 GHz processor
RAM - 2.5 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
Intel x86 compatibility
On supported Windows and Linux environments, LiveCycle ES supports Intel EDT64 and AMD64
compatible chipsets, but the operating system must be 32 bit.
Recommended hardware requirements
In addition to the minimum hardware requirements listed previously, here are the recommended
hardware requirements for a small production environment:
Intel environments: Pentium 4, 2.8 GHz or greater. Using a dual core processor will further enhance
performance.
Sun SPARC environments: UltraSPARC III or later.
Memory requirements: 4 GB of RAM.
Supported software
This table provides a summary of the application servers, web browsers, databases, database drivers,
Java™ Development Kit (JDK) versions, and LDAP servers that LiveCycle ES supports.
Required software
Supported version
Operating system
●
Microsoft Windows Server 2003 Enterprise Edition or Standard Edition
SP1 and R2 (32-bit edition only)
●
(Adobe LiveCycle Workbench ES) Windows XP Service Pack 2
●
Sun Solaris 9 and 10
●
IBM AIX 5L 5.3
●
SUSE Linux Enterprise Server 9.0 (32-bit edition only)
●
Red Hat Enterprise Linux AS or ES 4.0 (32-bit edition only)
●
JBoss 4.0.3 SP1
●
BEA WebLogic 9.2 (Advantage and Premium editions)
●
IBM WebSphere 6.1.05 (Base and Network Deployment editions)
Application server
35
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Supported software
36
Required software
Supported version
Web browser
See “Web browser support” on page 37 for a complete list of web browsers.
JDK
●
JBoss on all platforms - Sun JDK 1.5.0_11 (or later version of the 1.5.0
release) available at http://.java.sun.com
●
WebLogic on all platforms except Solaris - BEA JRockit® SDK 1.5.0_06
●
WebLogic on Solaris - Sun JDK 1.5.0_04. This version of the JDK requires
the Daylight Savings Time (TZ) update to be run in North America. You
can get it at http://java.sun.com/javase/tzupdater_README.html
●
WebSphere on all platforms except Solaris - IBM JDK 1.5.0 SR3
(embedded in application server)
●
WebSphere on Solaris - Sun JDK 1.5.0_09
For more information on JDKs, refer to “LDAP configuration” on page 41.
Database
Database driver
●
IBM DB2 8.2 or IBM DB2 8.1 Fix Pack 7 (Enterprise Edition)
●
Microsoft SQL Server 2005 SP1 (Enterprise Edition)
●
MySQL 5.0.18 (InnoDB Engine)
●
Oracle 9i or 10g (Standard and Enterprise Editions)
●
IBM DB2 - db2jcc.jar and db2jcc_license_cu.jar
●
SQL Server 2005 JDBC 1.1 - sqljdbc.jar
●
MySQL - mysql-connector-java-3.1.12-bin.jar (3.1.12)
●
Oracle 9i and 9i/10g - ojdbc14.jar, Release 2 (10.2.0.2 Thin)
Note: All Adobe LiveCycle Business Activity Monitoring ES metadata
databases use the drivers stated above.
LDAP server
Email servers
Data Services ES
●
Sun ONE 5.1
●
Sun ONE 5.2
●
Microsoft Active Directory 2000
●
Microsoft Active Directory 2003
●
Novell® eDirectory 8.7
●
IBM Tivoli Directory Server 6.0
●
Microsoft Exchange 2000
●
Microsoft Exchange 2003
●
Lotus Notes/Domino 6/7
●
SendMail (included with Red Hat 4 and SUSE 9)
●
Novel GroupWise 6/7
●
Adobe Flex™ Builder™ 2.0.1 Hot Fix 2 or higher
or
●
Flex SDK 2.0.1 Hot Fix 2 or higher
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Web browser support
Required software
Supported version
LiveCycle ES connector
LiveCycle Connector for EMC Documentum:
●
37
EMC Documentum Content Server 5.3 (and later service packs)
In addition, on your LiveCycle ES server you must install the version of EMC
Documentum Foundation Classes (DFC) that corresponds to your version of
Content Server. For more information, see Documentum Foundation Classes
Installation Guide available from EMC Documentum.
Note: EMC Documentum Content Server is not supported on Red Hat
Enterprise Linux AS or ES 4.0.
LiveCycle Connector for FileNet:
●
IBM FileNet P8 Content Engine 3.5.x
In addition, on your LiveCycle ES server you must install the version of IBM
FileNet P8 Content Java API that corresponds to your version of Content
Engine. For a list of the required JAR files, see Content Java API Developer's
Guide available from IBM FileNet.
PDF client
●
Adobe Acrobat® Professional and Acrobat Standard, versions 7.0 to 8.1
(for securing documents with policies and opening policy-protected
documents)
●
Adobe Reader®, versions 7.0 to 8.0 (for opening policy-protected
documents)
Web browser support
This section outlines the supported web browsers for the LiveCycle ES user interfaces.
End-user user interface
End-user components include these solution components:
●
Adobe LiveCycle Workspace ES (Flash Player required)
●
Adobe LiveCycle Reader Extensions ES (Flash Player required)
●
Adobe LiveCycle Rights Management ES (browser only)
●
Adobe LiveCycle PDF Generator ES (browser only)
Operating system
Flash Player
Supported browser
Microsoft Windows Vista™
Flash® Player 9*
Microsoft Internet Explorer 7 or later(1)
Firefox 2.0.0.1 or later(1)
Windows 2000
Flash Player 9*
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows XP
Flash Player 9*
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Additional requirements for Linux or UNIX operating systems
Operating system
Flash Player
Supported browser
Windows Server 2003
Flash Player 9*
Internet Explorer 6 or later(1)
38
Firefox 2.0.0.1 or later(1)
OS X v 10.4.x
(PowerPC)
Flash Player 9*
OS X v 10.4.x
(Intel)
Flash Player 9*
Firefox 2.0.0.1 or later(1)
Safari 2.x or later (not for Workspace ES)(2)
Firefox 2.0.0.1 or later(1)
Safari 2.x or later (not for Workspace ES)(2)
(1)“or later” includes major revisions. For example, Internet Explorer 6.0 or later also covers Internet
Explorer 7.0.
(2)
Workspace ES supports Internet Explorer and Firefox from the above table but not Safari.
Administrator user interface
This table outlines the supported web browsers for the LiveCycle Administration Console user interface.
Operating system
Flash Player
Supported browser
Microsoft Windows Vista
N/A
Internet Explorer 7 or later(1)
Firefox 2.0.0.1 or later(1)
Windows 2000
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows XP
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows Server 2003
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
OS X v 10.4.x (Intel)
N/A
Firefox 2.0.0.1 or later(1)
(1)
“or later” includes major revisions. For example, Microsoft Internet Explorer 6.0 or later also covers
Microsoft Internet Explorer 7.0
Additional requirements for Linux or UNIX operating systems
The installer for LiveCycle ES requires the bc tool to be available on the Linux or UNIX system. Normally, the
bc tool is present by default. Ensure that the bc tool (an arbitrary precision calculator language) is installed
on the system before you run the installer. If the tool is not present, you will experience error messages
warning about lack of disk space because the bc tool is used to compute whether enough disk space is
available prior to starting the installation. The bc tool may be provided by your operating system vendor,
or you can get the GNU bc tool at www.gnu.org.
Note: To verify that the tool is available, execute which bc from the shell. If the tool is available, the path
to the program is displayed.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Planning for the Upgrade Process
Additional requirements for PDF Generator ES
39
Additional requirements for PDF Generator ES
Note: This section applies only if your configuration requires native file format conversion (for example,
Microsoft Word to PDF conversion). If you are not installing PDF Generator ES, proceed to
“Additional requirements for Business Activity Monitoring ES” on page 40.
User account
You must use the same user account for the following tasks:
●
Installing Microsoft Office
●
Installing PDF Generator ES
●
Installing Acrobat 8.1 for PDF Generator ES
●
Running the application server process
Acrobat
PDF Generator ES requires that a supported version of Acrobat Professional or Acrobat Standard is
installed. You can choose to install Acrobat either manually prior to running the LiveCycle ES installer or as
part of the LiveCycle ES install process.
Native file conversion software installation
Before installing PDF Generator ES, you must also install the software that supports the file formats for
which PDF conversion support is required. PDF Generator ES can be extended to convert these additional
file types to PDF files using the following applications:
●
Microsoft Office 2000, XP, or 2003 (DOC, XLS, PPT)
●
Microsoft Office Visio 2003 (VSD)
●
Microsoft Project 2003 (MPP)
●
AutoCAD 2005 (DWG)
●
Corel WordPerfect 12 (WPD)
●
Adobe Photoshop® CS2 (PSD)
●
Adobe FrameMaker® 7.2 ((FM)
●
Adobe PageMaker® 7.0 (PMD, PM6, P65, PM)
●
OpenOffice 2.0 (all associated formats)
Windows environment variables
You must set the environment variables in Windows if you plan to create PDF documents from
applications such as FrameMaker, Photoshop, PageMaker, WordPerfect, and Acrobat.
The names of these environment variables are listed below:
●
Acrobat_PATH
●
FrameMaker_PATH
●
Notepad_PATH
●
OpenOffice_PATH
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
●
PageMaker_PATH
●
Photoshop_PATH
●
WordPerfect_PATH
Additional requirements for Business Activity Monitoring ES
40
These environment variables are optional and need to be set only if you are going to use the
corresponding application to convert PDF files through PDF Generator ES. The value of the environment
variable should contain the absolute path of the executable that is used to launch the corresponding
application.
For example, the variable Photoshop_PATH might contain the value D:\Program Files\Adobe\
Adobe Photoshop CS2\Photoshop.exe. However, OpenOffice_PATH is different from others. This
variable must be set to the OpenOffice installation folder (instead of the path to the executable). A typical
value of OpenOffice_PATH on Windows would be C:\Program Files\OpenOffice.org 2.0\.
You do not need to set up the paths for Microsoft Office applications such as Word, PowerPoint, Excel,
Visio, and Project or for AutoCAD. The Generate PDF service starts these applications automatically, if they
are installed on the server.
➤ To set the Windows environment variables:
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables.
4. In the System variables section, click New.
5. Enter the environment variable name you need to set (for example, Photoshop_PATH). This directory
is the directory containing the executable file. For example, type the following code:
D:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe
Service Control Manager command line tool
Before completing an automatic installation of PDF Generator ES on Windows, ensure that the Service
Control Manager command line tool, sc.exe, is installed in the Windows environment. Some Windows
servers do not have this software preinstalled. By default, the sc.exe file is installed in the
C:\Windows\system32 directory. Most OS installations will have this tool installed. If you do not have the
tool installed, it is available in the Windows Resource Kit for your specific version of Windows.
Additional requirements for Business Activity Monitoring ES
Note: These requirements are optional and required only if you are using the email functionality of
Business Activity Monitoring ES.
Business Activity Monitoring ES requires a running Simple Mail Transfer Protocol (SMTP) email server for
delivering email notifications. The server is external to Business Activity Monitoring ES and is managed by
your email system administrator. Contact that administrator to set up an account specifically for
Business Activity Monitoring ES; you need an account and password for sending mail, an address to use in
the From address field, and the name of the email server host.
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
LDAP configuration
41
LDAP configuration
Note: This configuration is optional and required only if you are using an LDAP directory to authenticate
users.
Install and configure your LDAP server and database according to the vendor’s documentation. See
“Supported software” on page 35 for a list of supported LDAP servers. Take note of the LDAP administrator
name and password to use during the LiveCycle ES configuration process. You configure LiveCycle ES to
connect with the LDAP database after you have installed and deployed your LiveCycle ES services. This
configuration is done using the User Manager service. See Installing and Deploying LiveCycle ES for your
application server.
Installation considerations
This section includes considerations for an administrator when installing LiveCycle ES.
Installing from network drives
It is recommended that you only install LiveCycle ES from the installation media or a local disk drive.
Attempting to install the software over a network will result in considerable delays in launching and
installing.
Manual use of Acrobat restricted
If you have installed the PDF Generator ES Generate PDF service for native document conversion, use of
the included Acrobat is restricted to the Generate PDF service and is not licensed for any other use.
Installation and deployment topology considerations
This section describes where to install, configure, upgrade, and deploy LiveCycle ES in relation to your
LiveCycle 7.x deployment and database.
When you install the LiveCycle ES product files, LiveCycle Configuration Manager is included in the
installation directory. This is the location of LiveCycle Configuration Manager, and it is important because
this tool performs most of the configuration, upgrade, and deployment tasks.
LiveCycle Configuration Manager must have access to the following resources.
Resource
Connection required
LiveCycle 7.x EAR files
File system access
LiveCycle 7.x database and/or LiveCycle Policy
Server database
TCP connection to database server $host at $port
LiveCycle ES database
TCP connection to database server $host at $port
LiveCycle ES target application server
TCP connection to the JNDI server
These resources do not need to be on the same computer as LiveCycle Configuration Manager if they are
accessible remotely on the network.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Planning for the Upgrade Process
Gathering information required before you start
42
LiveCycle Configuration Manager does not require access to the LiveCycle 7.x application server; it needs
access only to the LiveCycle EAR files from the deployment. To make these files available, export the
appropriate EAR files from the application server and ensure that they are located in a directory available
to LiveCycle Configuration Manager. (See “Exporting the LiveCycle 7.x EAR files” on page 45.)
LiveCycle Configuration Manager should also have network access to the Global Document Storage
directory and temporary directory configured for LiveCycle 7.x. If LiveCycle Configuration Manager cannot
connect to these directories, it prompts you to input the required data manually. Information is available
about this requirement in LiveCycle Configuration Manager Help.
As long as these conditions are met, you can install the LiveCycle ES product files on the same computer as
LiveCycle 7.x or the LiveCycle ES target application server, or a separate computer. The LiveCycle ES
application server can be installed either on the same host as the LiveCycle 7.x application server or on a
separate computer.
Gathering information required before you start
This section serves as a checklist for the information you need during the upgrade process. During the
upgrade, you will be instructed or prompted to provide this information. If you ensure that it is available
before you begin, you can speed up the process and minimize any server downtime.
Credentials
You need the Reader Extensions ES Rights credential that you received with your upgrade license.
Passwords
You need the following passwords:
●
Passwords for credential files (PFX and P12 files) (LiveCycle Document Security upgrades only)
●
Password and connection information for the HSM device if you are using one (LiveCycle Document
Security upgrades only)
●
Application server and database server administrator passwords
●
LiveCycle 7.x administrator passwords
Port information
You need to provide JNDI port information for your application server (JBoss, WebLogic, or WebSphere)
and for your database.
If you are not sure which ports the database uses, contact your database administrator.
➤ To determine the JNDI port for JBoss 3.x and 4.x:
1. Navigate to the [jboss_root]/server/all/conf directory and open the jboss-service.xml file.
2. Find the element <mbean code="org.jboss.naming.NamingService">.
3. The JNDI server port is the value of the element <attribute name="Port">.
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Gathering information required before you start
43
➤ To determine the JNDI port used by WebSphere:
●
(WebSphere 5.1.x) Log in to the WebSphere Administrative Console and, in the navigation tree, select
Servers > Application Servers > [server_name]. Under Additional Properties, click End Points and
then click BOOTSTRAP_ADDRESS.
●
(WebSphere 6.0.x) Log in to the WebSphere Administrative Console and, in the navigation tree, select
Servers > Application Servers > [server_name] > Ports, and look for the value of boostrap_address.
➤ To determine the JNDI port used by WebLogic:
●
Typically, the JNDI server port is the same as for the server created to host LiveCycle ES. If a Managed
Server is configured for deployment of LiveCycle ES, the JNDI port should be the port used by the
Managed Server.
Server names
If you are installing the LiveCycle ES product files and running LiveCycle Configuration Manager from a
different computer than the target LiveCycle ES server, you must know the server name of the system on
which LiveCycle ES will be deployed.
Location of directories
You must have the location of these directories:
Exported EAR files: You must export the LiveCycle 7.x EAR files from the application server (or for
JBoss, from the deployment directory) to a location that LiveCycle Configuration Manager has file
access to. Make a note of the location of the exported EAR files. (See “Exporting the LiveCycle 7.x EAR
files” on page 45.) These files are not required for LiveCycle Policy Server upgrades.
Database drivers: You will need to reference the database drivers for the type of database server you
are using for LiveCycle ES. The drivers for MySQL, Oracle, and DB2 are installed with LiveCycle ES and
located in the [LiveCycleES root]/lib/db directory or downloaded (SQL Server).
Java 5 (1.5.0_11) SDK (Java5 SDK): You will be instructed to include the path to the Java 5 SDK in the
JAVA_HOME and PATH variables on the system on which you install LiveCycle ES.
Global Document Storage directory: You can use the JMX console in JBoss to determine the location
of the Global Document Storage directory used in LiveCycle 7.x:
●
Open a browser and go the URL http://[servername]:[port]/.
●
Click JMX Console.
●
Click service=DataManagerService under the adobe.com heading.
●
Look for the value assigned to the property GlobalDocumentStorageRootDir. If none is specified,
the default is in use. The default value for JBoss is [java.io.tmpdir]/AdobeDocumentStorage/global,
where java.io.tmpdir is the value of the Java system property java.io.tmpdir. The value of this
property is written to the server.log file when LiveCycle 7.x is started.
Note: LiveCycle Configuration Manager must have network access to this directory.
Adobe LiveCycle ES
Planning for the Upgrade Process
Preparing to Upgrade to LiveCycle ES
Next steps
44
Watched folder locations
The instructions for preparing your system for upgrading require you to back up all watched folders on
your system. Watched folders are used with LiveCycle Assembler and LiveCycle PDF Generator. You can
determine the name and location of active watched folders in Adobe Administrator (on the LiveCycle 7.x
server).
➤ To determine watched folders for LiveCycle PDF Generator 7.x:
1. Log in to Adobe Administrator on the LiveCycle 7.x server.
2. Select PDF Generator > Sources. You will see a list of watched folders.
3. Click the name of a watched folder to determine its properties, including the location.
➤ To determine watched folders for LiveCycle Assembler 7.x:
1. Log in to Adobe Administrator on the LiveCycle 7.x server.
2. Browse to Services, click Watched Folder, and then click Watched Folder Management and Status.
Information about the watched folders is available.
Next steps
Now that you have an understanding of the upgrade process, have ensured that you have the correct
supported software and hardware you need, and have gathered the information you will need during the
upgrade, you can proceed to the first preparatory task, “Exporting the LiveCycle 7.x EAR files” on page 45.
4
Exporting the LiveCycle 7.x EAR files
Before you can import the data from the LiveCycle 7.x archives, you must export the archive files from the
production environment by using the application server's export feature. This step is required for
WebSphere and WebLogic only.
Note: This procedure is not required if you are upgrading LiveCycle Policy Server only.
For JBoss, EAR files must be copied from the deployment directory to a location that is accessible by
LiveCycle Configuration Manager. If the JBoss server directory is accessible to
LiveCycle Configuration Manager, you can specify the paths to the EAR files as they exist in the application
server deployment directory.
The following list includes all the possible archive files that must be exported from the production
environment. (Not all the archives will be present, depending on the products and versions you have
installed; however, any of the following archives that are included in your deployment must be exported).
LiveCycle.ear or Data Manager Module: Can be one of the following files:
●
DataManagerService.war (if you are running an earlier version of LiveCycle, such as LiveCycle
Document Security 7.0 or LiveCycle Reader Extensions)
●
DataManagerService.bar (if you are running an earlier version of LiveCycle, such as LiveCycle Document
Security 7.0 or LiveCycle Reader Extensions)
●
AdobeServices.sar (if you are running an earlier version of LiveCycle, such as LiveCycle Document
Security 7.0 or LiveCycle Reader Extensions)
●
LiveCycle.ear (if you are running LiveCycle 7.0 products other than those listed previously, or later
versions such as LiveCycle 7.1 or 7.2)
LiveCycle Document Security or Trust Manager Module: Can be one of the following files:
●
LiveCycle-security.ear (if you are upgrading from LiveCycle 7.2.x)
●
TrustManager.war (if you are upgrading a version that is earlier than LiveCycle 7.2)
●
TrustManager.bar (if you are upgrading from LiveCycle 7.0 for JBoss)
LiveCycle PDF Generator: Can be one of the following files:
●
pdfg-ps-all.ear (if you are upgrading from LiveCycle PDF Generator for PostScript)
●
pdfg-all.ear (if you are upgrading from LiveCycle PDF Generator Professional or Elements)
Font Manager Module: Can be one of the following files:
●
adobe-FontManager.ear (if you are upgrading from LiveCycle 7.2.x)
●
adobe-FontManager.war (if you are upgrading a version that is earlier than LiveCycle 7.2)
●
adobe-FontManager.bar (if you are upgrading from LiveCycle 7.0 for JBoss)
LiveCycle Assembler: The acceptable file is adobe-Assembler7.ear.
Note: File names may not exactly match the file names listed because they may have been modified by
administrators or during export by the application server.
45
Adobe LiveCycle ES
Exporting the LiveCycle 7.x EAR files
Preparing to Upgrade to LiveCycle ES
Next steps
46
LiveCycle Configuration Manager cannot migrate sample applications from LiveCycle 7.x to LiveCycle ES.
The following files also do not need to be exported because they are specific to LiveCycle 7.x and are not
used in LiveCycle ES:
●
FormsIVS.EAR
●
LCMBootStrapper.war
●
LCM.ear
●
adobe-printSubmitter.ear
➤ To export archive files from the production environment on WebSphere:
1. Log in to the WebSphere Administrative Console.
2. Click Applications > Enterprise Applications.
3. Select the Adobe LiveCycle deployed archive files and click Export.
4. Follow the instructions to download the exported archive files to the LiveCycle ES host. (You can do this
step using a browser from the LiveCycle ES host; the files can be downloaded to the local host without
the need to create an extra network copy.)
5. Repeat steps 2 to 4 for each LiveCycle archive file.
➤ To export archive files from the production environment on WebLogic:
1. Log in to the Weblogic Administration Console.
2. In the navigation tree, click [your domain] > Deployments > Applications.
3. For each LiveCycle archive file in the list, do the following tasks:
●
Click the application name.
●
On the General tab, note the value of the Path attribute. That value is the source archive used to
deploy the application, which is the exported application you need to reference when importing
the applications.
Next steps
You can now proceed to the next preparatory task, “Backing Up the LiveCycle 7.x Environment” on
page 47.
5
Backing Up the LiveCycle 7.x Environment
Before starting the upgrade process, you must back up all the files and directories associated with the
LiveCycle 7.x deployment, including the Java SDK, installation files, watched folder contents, and
temporary directory. Do not delete any of these items.
Backing up the files and directories associated with LiveCycle 7.x
You do not need to back up the application server because LiveCycle ES is deployed to a separate instance
of the application server, which is installed and configured in parallel with the LiveCycle 7.x servers.
During the upgrade process, the application server running LiveCycle 7.x is shut down so that the
application server running LiveCycle ES can begin taking the new requests.
➤ To back up files and directories:
1. Determine the location of all watched folders created for LiveCycle 7.x products. This includes watched
folders used with LiveCycle Assembler and LiveCycle PDF Generator.
2. Determine the location of the LiveCycle 7.x Global Document Storage directory. The Global Document
Storage directory may have been specified by the administrator who installed the product, or it may be
the default location assigned by LiveCycle 7.x. To determine the directory location for JBoss, do the
following tasks:
For products that use User Management and Administrator
●
Log in to Adobe Administrator by typing the following URL in a web browser:
http://[host name]:[port]/adminui
The default port number for JBoss is 8080.
●
Browse to Services > JMX Monitor.
●
Click adobe.com:service=DataManagerService.
For products that do not use User Management and Administrator
●
With JBoss running, type the following URL in a web browser:
http://[host name]:[port]
The default port number for JBoss is 8080.
●
Click JMX Console.
●
Click service=DataManagerService under the adobe.com heading
The temporary directory used by the LiveCycle 7.x is the value shown for "AdobeTempDir" and the
global DocumentStorageRootDirectory is the value of "GlobalDocumentStorageRootDir".
3. Look for the value assigned to property GlobalDocumentStorageRootDir. If none is specified, the
default is in use. The default value for JBoss is [java.io.tmpdir]/AdobeDocumentStorage/global, where
java.io.tmpdir is the value of the Java system property 'java.io.tmpdir'. The value of this property is
written to the server.log file when LiveCycle 7.x is started.
47
Adobe LiveCycle ES
Backing Up the LiveCycle 7.x Environment
Preparing to Upgrade to LiveCycle ES
Backing up the LiveCycle 7.x database
48
4. If the value above is blank (no directory is specified), a new default Global Document Storage directory
will be created for LiveCycle ES and you do not have to back up this directory. If you specified a value
other than the default, you must back up the directory listed at this time. During the configuration and
upgrade process, LiveCycle ES is configured to reuse this directory.
Back up the Global Document Storage directory by creating a ZIP file or TAR file of the entire directory.
Note: During the upgrade, LiveCycle Configuration Manager reads the values of the Temp and Global
document storage directories from the configured EAR files and displays the values on the
Configure LiveCycle (continued) screen.
5. Back up each watched folder contents by creating a ZIP file or TAR file of each watched folder directory.
Backing up the LiveCycle 7.x database
You must make a backup of the LiveCycle 7.x database. If you using SQL Server, Oracle, or DB2 databases,
back up the database according to your organization or database administrator’s standard method.
If you are using MySQL 4.1, you can back up the LiveCycle 7.x database by using the mysqldump.exe tool.
To back up the contents of the LiveCycle 7.x MySQL database, perform these tasks:
●
In a command prompt, type the cd command to navigate to the [LiveCycle7 root]\mysql\bin directory,
and then type the MySQL command based on the following example:
mysqldump --add-locks --lock-tables -c --default-character-set=utf8
--skip-opt -p -u root -r adobe.sql -B adobe
In the example above, the following options may be modified:
●
-p refers to the MySQL 4.1 password. Notice that this is blank in the example above because the
default password for MySQL root is blank, but the LiveCycle 7.x database may use a new password.
●
-u refers to the MySQL 4.1 user name. The value root can be replaced with the appropriate user
name.
●
-r refers to the location of the file that contains the dumped data. You can change the name of the
file from adobe.sql, or you can include the path to the directory where you want to save this file.
●
-B refers to the name of the database. The name is adobe by default; if your turnkey LiveCycle 7.x
database (installed by turnkey) has a different name, use it instead.
Dropping the SIB database tables (WebSphere only)
If you are upgrading from LiveCycle 7.x deployed on WebSphere 6.0.2.x to LiveCycle ES on WebSphere 6.1,
you must drop or truncate all database tables related to the Messaging Engine (ME) connected to the
IDP_JMS_Bus. Otherwise, WebSphere does not start up successfully.
The tables that must be dropped or truncated are found in the schema specified in the Message Store
configuration for the IDP_JMS_Bus. The table names begin with SIB.
Note: When the SIB tables are dropped or truncated, you will lose any LiveCycle Workflow 7.x tasks that
have not yet been processed. (Tasks in progress are saved in the database.) To minimize the number
of lost tasks, ensure that you stop the LiveCycle 7.x server for upgrading when server activity is
relatively low, if possible.
Complete this task after you have backed up the LiveCycle 7.x database, before you configure WebSphere
for LiveCycle ES.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Backing Up the LiveCycle 7.x Environment
Next steps
49
➤ To determine the schema that contains SIB tables:
1. Log in to the WebSphere Administrative Console.
2. In the WebSphere Administrative Console navigation tree, select Service Integration > Buses >
IDP_JMS_Bus > Messaging Engines > JMS_Bus Messaging Engine > Message Store > Schema
name.
For more information on SIB tables, see
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.doc/r
ef/rjm0640_.html
Next steps
You can now configure the application server for LiveCycle ES. Depending on the application server you
are using, see one of the following sections:
●
“Configuring JBoss Application Server” on page 50
●
“Configuring WebSphere Application Server” on page 79
●
“Configuring WebLogic Server” on page 84
6
Configuring JBoss Application Server
This section describes how to configure a JBoss Application Server for use with LiveCycle ES. The
instructions are required for upgrades that do not use the turnkey method.
Caution: If you intend to install JBoss on the same computer where LiveCycle 7.x server is located, do not
perform the tasks in this section at this time. Proceed to “Upgrading the Database Server” on
page 95 or “Creating the LiveCycle ES database” on page 102, and then continue on to begin the
upgrade.
You can minimize LiveCycle server downtime by waiting until you are prompted during the
upgrade to stop the LiveCycle 7.x server before configuring the target LiveCycle ES application
server. At that time, the documentation will direct you back to this section to make the
configuration changes required.
The non-turnkey, or manual, method of upgrading to LiveCycle ES is required if you installed the
LiveCycle 7.x product using the manual installation method. (That is, a preconfigured JBoss and MySQL
database server were not included in the LiveCycle 7.x installation.)
The non-turnkey upgrade method also applies to the following situations:
●
You are using a Linux operating system.
●
You are preparing a clustered deployment on Windows or Linux.
●
You are using DB2, Oracle or SQL Server for the database.
●
You need advanced control of the JBoss configurations.
LiveCycle ES runs on JBoss on both Windows Server 2003 (Enterprise Edition or Standard Edition), Red Hat
Linux ES/AS 4.0, and SUSE Linux ES 9 platforms.
Note: If you are planning to run the LiveCycle ES turnkey upgrade for JBoss, you do not need to review this
document. All the instructions required for preparing your environment for a turnkey installation
are available in Upgrading to LiveCycle ES for JBoss Using Turnkey at
http://www.adobe.com /go/learn_lc_upgradeTurnkey.
This section uses the following documentation conventions:
Name
Default value
[appserver root]
(Windows) C:\jboss
(Linux) /opt/jboss
Installing the J2SE SDK
You must download and install the Sun J2SE SDK version 1.5.0_11 or later update of version 1.5.0 from
www.java.sun.com.
You must create or set the JAVA_HOME environment variable to point to the location where the Java SDK
is installed. If you are installing the Java SDK on the same machine where LiveCycle 7.x is installed,
JAVA_HOME must set to point to the updated version.
50
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Installing JBoss
51
➤ To set the JAVA_HOME environment variable (Windows):
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables.
4. In the System Variables area, click New.
5. Enter JAVA_HOME as the variable name, and enter the directory where you installed the Java SDK. This
directory is the directory containing the /bin subdirectory. For example, type the following line:
C:\Program Files\Java\jdk1.5.0_11
Note: To verify your JAVA_HOME environment variable, open a command prompt and run the following
command:
%JAVA_HOME%\bin\java -version
You should receive a response beginning with Java version 1.5.0_11 (or a later version of 1.5.0).
➤ To set the JAVA_HOME environment variable (UNIX and Linux):
●
It is recommended that you set the JAVA_HOME variable for Borne and Bash shells as shown in the
following example:
JAVA_HOME=/usr/java
export JAVA_HOME
➤ To set the PATH environment variable (UNIX and Linux):
●
It is recommended that you set the PATH variable for Borne and Bash as shown in the following
example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Installing JBoss
Use one of the following two ways to proceed with the deployment of JBoss for a LiveCycle ES installation.
Select the option that is most appropriate:
●
Use the Adobe preconfigured JBoss software that is delivered as part of the LiveCycle ES media. In most
cases, this option is the simplest. Advanced knowledge of JBoss is not required.
●
Download the default JBoss software from the Internet. This option should be considered for advanced
installations only. Advanced knowledge of JBoss is typically required.
Using Adobe preconfigured JBoss
Adobe downloads the standard JBoss 4.0.3 SP1 archive from the JBoss website and configures it with the
options required to run LiveCycle ES in a stand-alone configuration. You can review these configurations in
the next section.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Manually installing JBoss
52
The preconfigured JBoss software is located on the installation media or ESD download in the /third_party
directory. Copy the JBoss directory and its contents to the location where you intend to install JBoss. This
JBoss installation has all of the configuration steps completed as described in the “Modifying JBoss
configuration files” and “Configuring MySQL” sections except for the steps detailed in “Configuring MySQL
for Adobe preconfigured JBoss” on page 58, which you must complete if you plan to use MySQL. If you do
not intend to use a MySQL database, you must complete the remaining database configuration steps.
Manually installing JBoss
If you are manually configuring JBoss for running LiveCycle ES, download and unpackage
JBoss Application Server 4.0.3 SP1.
➤ To download and unpackage JBoss:
1. In a browser, go to labs.jboss.com/portal/jbossas/download.
2. Locate the entry for JBoss Application Server 4.0.3 SP1 and click the Download link beside it.
3. On the download page, select the appropriate file for your operating system:
●
(Windows) jboss-4.0.3SP1.zip
●
(Linux) jboss-4.0.3SP1.tar.gz
4. Extract the file to the directory of your choice on your server.
Starting and stopping JBoss
Several procedures in this chapter require you to stop and start the instance of JBoss where you want to
deploy the product.
Note: These procedures apply to both the Adobe preconfigured JBoss and the manually configured JBoss
software.
➤ To start JBoss:
1. From a command prompt, navigate to [appserver root]/bin.
2. Start the application server by typing the following command:
●
(Windows) run.bat -c all
●
(Linux) ./run.sh -c all
➤ To stop JBoss:
1. From a command prompt, navigate to [appserver root]/bin.
2. Stop the application server by typing the following command:
●
(Windows) shutdown.bat -S
●
(Linux) ./shutdown.sh -S
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Modifying the JBoss configuration files
53
Modifying the JBoss configuration files
Note: This procedure is required only if you are not using the Adobe preconfigured JBoss software
provided on the installation media.
Modify the following areas on the instance of JBoss that hosts LiveCycle ES:
●
Update the xalan version.
●
Update the jacorb.properties file.
●
Modify the EAR and WAR file class-loading isolation.
●
Remove the JavaServer™ Faces (JSF) libraries.
●
Disable cluster service (for single node installations only).
●
Remove the tests directory.
●
Create the security policy file.
●
Modify the run.bat file (Windows only).
●
Modify the run.sh file (Linux only).
●
Modify run.conf.
●
Modify log4J.xml.
●
Remove the JMX Console and Web Console.
●
Create the Java Message Service (JMS) topics and queues.
➤ To update the xalan version:
1. Download the xalan-j 2.7.0 download package from the following website:
http://xml.apache.org/xalan-j/
2. Download the required file:
●
(Windows) xalan-j_2_7_0-bin.zip
●
(Linux) xalan-j_2_7_0-bin.tar.gz
3. Extract the xalan.jar file and the serializer.jar file from the downloaded archive file.
4. From the [appserver root]/lib/endorsed directory, delete the old xalan.jar file.
5. Copy the new xalan.jar file and the serializer.jar files to the [appserver root]/lib/endorsed directory.
➤ To update the jacorb.properties file:
1. Open the [appserver root]/server/all/conf/jacorb.properties file in a text editor.
2. Locate the jacorb.poa.thread_pool_max setting and change the value to 16.
➤ To modify WAR file class-loading isolation:
1. Open the [appserver root]/server/all/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml file in
an editor.
2. Locate <attribute name="Java2ClassLoadingCompliance"> and change the value to true.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Modifying the JBoss configuration files
54
3. Locate <attribute name="UseJBossWebLoader"> and ensure that the value is false.
4. Save and close the file.
➤ To modify EAR file class-loading isolation:
1. Open the [appserver root]/server/all/conf/jboss-service.xml file in an editor.
2. Locate <attribute name="CallByValue"> and change the value to true.
3. Save and close the file.
4. Open the [appserver root]/server/all/deploy/ear-deployer.xml file in an editor.
5. Locate <attribute name="Isolated"> and change the value to true.
6. Locate <attribute name="CallByValue"> and change the value to true.
7. Save and close the file.
➤ To remove the JSF libraries:
●
Navigate to the [appserver root]/server/all/deploy/jbossweb-tomcat55.sar directory and delete the
jsf-libs subdirectory and all its files.
➤ To disable the cluster service:
1. Open the [appserver root]/server/all/deploy/cluster-service.xml file in an editor, and locate and modify
the following attribute values:
●
mcast_port="34374"
●
ip_ttl="1"
2. Save and close the file.
3. Open the [appserver root]/server/all/deploy/tc5-cluster-service.xml file in an editor.
4. Locate ip_mcast and change it to false.
5. Save and close the file.
6. Open the [appserver root]/server/all/deploy/jms/hajndi-jms-ds.xml file in an editor.
7. Locate jnp.disableDiscovery and change the value to true.
8. Save and close the file.
➤ To remove the tests directory:
●
Delete the [appserver root]/docs/tests directory.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Modifying the JBoss configuration files
55
➤ To create the security policy file:
1. In a text editor, open a new document and add the following content:
grant {
// Allow everything for now
permission java.security.AllPermission;
};
2. Save the file as [appserver root]/server/all/conf/server.policy.
➤ To modify the run.bat file (Windows only):
1. Open the [appserver root]/bin/run.bat file in an editor.
2. Locate rem Sun JVM memory allocation pool parameters and insert the following text
immediately before that string:
rem for Java 2 security
set JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager
set JAVA_OPTS=%JAVA_OPTS% -Djava.security.policy=../server/all/conf/
server.policy
set JAVA_OPTS=%JAVA_OPTS% -Djava.security.debug=failure
3. Modify the line immediately following rem Sun JVM memory allocation pool parameters
to read as follows:
set JAVA_OPTS=%JAVA_OPTS% -XX:MaxPermSize=256m -Xms256m -Xmx1024m
-Djava.net.preferIPv4Stack=true
4. Modify the line immediately following rem Setup JBoss specific properties to set encoding
to UTF-8:
set JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=server1
-Dfile.encoding=utf8 -Dprogram.name=%PROGNAME%
5. Save and close the file.
➤ To modify the run.sh file (Linux only):
1. Open the [appserver root]/bin/run.sh file in an editor.
2. Modify the line immediately following Setup JBoss sepecific properties to set encoding to
UTF-8 and security manager:
JAVA_OPTS="$JAVA_OPTS -Dadobeidp.serverName=server1 -Dfile.encoding=utf8
-Dprogram.name=$PROGNAME -Djava.security.manager
-Djava.security.policy=../server/all/conf/server.policy
-Djava.security.debug=failure"
Note: Ensure that this entry appears as a single line in the run.sh file.
3. Save and close the file.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Modifying the JBoss configuration files
56
➤ To modify the run.conf file:
1. Open the [appserver root]/bin/run.conf file in an editor.
2. Locate JAVA_OPTS="-server -Xms128m -Xmx128m" and modify it to read as follows:
JAVA_OPTS="-server -XX:MaxPermSize=256m -Xms256m -Xmx1024m"
Note: If you have Linux, you must also add the "-Djava.net.preferIPv4Stack=true" flag to
remove the warning “[HANamingService] Failed to start AutomaticDiscovery”.
3. Save and close the file.
➤ To modify the log4j.xml file to increase the logging level from DEBUG to INFO:
1. Open the [appserver root]/server/all/conf/log4j.xml file in an editor.
2. Locate the following text in the FILE appender section and add the line that appears in bold:
<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppe
nder">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="File" value="${jboss.server.home.dir}/log/cluster.log"/>
<param name="Threshold" value="INFO"/>
<param name="Append" value="false"/>
3. Locate the following text in the CONSOLE appender section:
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Target" value="System.out"/>
<param name="Threshold" value="INFO"/>
Modify the last line to read as follows:
<param name="Threshold" value="WARN"/>
4. Add the com.adobe category, and then find the Limit categories section and add the following
lines:
<category name="com.adobe">
<priority value="INFO"/>
</category>
5. Add the following category under the com.adobe category:
<category name="org.apache.xml.security.signature.Reference">
<priority value="WARN"/>
</category>
6. Save and close the file.
➤ To remove the JMX Console and Web Console:
●
To remove the default insecure web pages from JBoss, delete the following directories:
[appserver root]/server/all/deploy/jmx-console.war
[appserver root]/server/all/deploy/management
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring the LiveCycle ES database connectivity
57
➤ To create JMS topics and queues:
1. Create a new file called adobe-service.xml and store it in the [appserver root]/server/all/deploy/jms
directory.
2. Add the following content to the file to define the topics and queues:
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_PECommandQueue">
<depends optional-attributename="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_PEDCommandQueue">
<depends optional-attributename="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_PEInteractionQueue">
<depends optional-attributename="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_JobManagerQueue">
<depends optional-attributename="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Topic"
name="jboss.mq.destination:service=Queue,name=adobe_TaskEventTopic">
<depends optional-attributename="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
</server>
3. Save and close the file.
Configuring the LiveCycle ES database connectivity
To configure the LiveCycle ES database connectivity, you must complete the following tasks:
●
Configure the LiveCycle ES data source.
●
Configure JBoss to use your database as the default data source.
You must install database drivers to the installation directories of the application server. Drivers are
required to enable LiveCycle Configuration Manager and the application server to connect to the
LiveCycle ES database. You must install the drivers for the type of database that you use for the database.
You must configure the data source to connect to the database. For JBoss, you can configure a MySQL, SQL
Server, Oracle, or DB2 data source.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring MySQL for Adobe preconfigured JBoss
58
Configuring MySQL for Adobe preconfigured JBoss
To enable Adobe preconfigured JBoss to connect to the MySQL database that stores LiveCycle ES data, you
must complete these tasks:
●
Obtain and copy the MySQL JDBC driver to the instance of JBoss where you will deploy LiveCycle ES.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy LiveCycle ES.
●
Configure JBoss to use MySQL for JMS.
If you are using a manually configured JBoss, see “Configuring MySQL for manually installed JBoss” on
page 60.
Configuring the MySQL data source
Before configuring the MySQL data source, you must have already created the database on MySQL. (See
“Creating a MySQL database” on page 102.)
➤ To install the MySQL database driver:
●
Copy the mysql-connector-java-3.1.12-bin.jar driver file from the [DVD_root]/third_party/jdbc directory
on the installation DVD to the [appserver root]/server/all/lib directory.
➤ To create the MySQL data source file:
1. Copy the adobe-ds-jboss-mysql.xml file from the [DVD_root]/third_party/datasources directory on the
installation DVD to the [appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-mysql.xml file in a text editor and locate this line:
<connection-url>jdbc:mysql://localhost:3306/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
3306: The port used to access the database. The default port is 3306.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring MySQL for Adobe preconfigured JBoss
59
Setting MySQL as the JMS data source
If you are running LiveCycle ES with a MySQL database, you must set MySQL as the default data source for
JBoss. (JBoss is configured by default to use Hypersonic as the data source.)
This procedure assumes that the MySQL JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set MySQL as the JMS data source:
1. Open the [appserver root]/server/all/deploy/mysql-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your MySQL connection settings:
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:mysql://yourHostname:yourPort/
yourDatabaseName/</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>yourUserName</user-name>
<password>yourPassword</password>
2. Replace the bold text with values that are specific to your database:
yourHostname, yourPort, yourDatabaseName, youruserName, and yourPassword: The
database values the application server uses to access the database.
3. Save and close the file.
4. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
code within the <policy> element:
<application-policy name="MySqlDbRealm">
<authentication>
<login-module
code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag
= "required">
<module-option name="principal">database_name</module-option>
<module-option name="userName">database_username</module-option>
<module-option name="password">database_password</module-option>
<module-option
name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,
name=Default DS </module-option>
</login-module>
</authentication>
</application-policy>
5. Replace the bold text with values that are specific to your database:
database_name, database_username, and database_password: The user name and
password that the application server uses to access the database.
6. Save and close the file.
7. Restart JBoss.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring MySQL for manually installed JBoss
60
Configuring MySQL for manually installed JBoss
To enable JBoss to connect to the MySQL database that stores LiveCycle ES data, you must complete these
tasks.
●
Obtain and copy the MySQL JDBC driver to the instance of JBoss where you will deploy LiveCycle ES.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy LiveCycle ES.
●
Configure JBoss to use MySQL for JMS.
If you are using Adobe preconfigured JBoss, see “Configuring MySQL for Adobe preconfigured JBoss” on
page 58.
Configuring the MySQL data source
Before configuring the MySQL data source, you must have already created the database on MySQL. (See
“Creating a MySQL database” on page 102.)
➤ To install the MySQL database driver:
●
Copy the mysql-connector-java-3.1.12-bin.jar driver file from the [DVD_root]/third_party/jdbc directory
on the installation DVD to the [appserver root]/server/all/lib directory.
➤ To create the MySQL data source file:
1. Copy the adobe-ds-jboss-mysql.xml file from the [DVD_root]/third_party/datasources directory on the
installation DVD to the [appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-mysql.xml file in a text editor and locate this line:
<connection-url>jdbc:mysql://localhost:3306/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
3306: The port used to access the database. The default port is 3306.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring MySQL for manually installed JBoss
61
Setting MySQL as the JMS data source
If you are running LiveCycle ES with a MySQL database, you must set MySQL to be the default data source
for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the MySQL JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set MySQL as the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file.
2. Navigate to the [appserver root]/docs/examples/jca directory and copy the mysql-ds.xml file to the
[appserver root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/mysql-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your MySQL connection settings:
<jndi-name>MySqlDS</jndi-name>
<connection-url>jdbc:mysql://yourHostname:yourPort/
yourDatabaseName</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>yourUserName</user-name>
<password>yourPassword</password>
4. Replace the bold text with values that are specific to your database:
●
MySqlDS must be changed to DefaultDS.
●
yourHostname, yourPort, yourDatabaseName, youruserName, and yourPassword are the
database values the application server uses to access the database.
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to MySQL:
<type-mapping>mySQL</type-mapping>
7. Save and close the file.
8. Open the standardjbosscmp-jdbc.xml file and change the following elements (not necessarily
contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>mySQL</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Remove the text: <!—optional since 4.0 and .." from the <datasource-mapping> tag to
uncomment it.
10. Save and close the file.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring Oracle for Adobe preconfigured JBoss
62
11. Open the login-config.xml file in a text editor and add the following text within the <policy>
element:
<application-policy name="MySqlDbRealm">
<authentication>
<login-module
code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag
= "required">
<module-option name="principal">database_name</module-option>
<module-option name="userName">database_username</module-option>
<module-option name="password">database_password</module-option>
<module-option
name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,
name=DefaultDS </module-option>
</login-module>
</authentication>
</application-policy>
12. Replace the bold text with values that are specific to your database:
database_name, database_username, and database_password: The user name and
password that the application server uses to access the database.
13. Save and close the file.
14. Replace the hsql-jdbc2-service.xml file in the [appserver root]/server/all/deploy-hasingleton/jms
directory with the mysql-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory.
15. Open the [appserver root]/server/all/deploy-hasingleton/jms/mysql-jdbc2-service.xml file and change
MySqlDS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
16. In the same file, mysql-jdbc2-service.xml, modify the SELECT_MAX_TX line to the following text:
SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
17. Rename the hsqldb-jdbc-state-service.xml file to mysql-jdbc-state-service.xml.
18. Restart JBoss.
Configuring Oracle for Adobe preconfigured JBoss
To enable JBoss to connect to the Oracle database that stores LiveCycle ES data, you must complete the
following tasks if you are manually deploying LiveCycle ES:
●
Obtain and copy the Oracle JDBC driver to the instance of JBoss where you will deploy LiveCycle ES.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy LiveCycle ES.
●
Configure JBoss to use Oracle for JMS.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring Oracle for Adobe preconfigured JBoss
63
Configuring the Oracle data source
Before configuring the Oracle data source, you must have already created the database on Oracle. (See
“Creating an Oracle database” on page 104.)
➤ To install the Oracle 10g database driver:
1. You can access the driver file from the [LiveCycleES root]/lib/db/oracle directory. You can also download
the Oracle 10g Release 2 (10.2.0.2 Thin) driver from this location:
www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
2. Copy the ojdbc14.jar driver file to the [appserver root]/server/all/lib directory.
➤ To create the Oracle data source file:
1. Copy the adobe-ds-jboss-oracle.xml file from the [DVD_root]/third_party/datasources directory on the
installation DVD to the [appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-oracle.xml file in a text editor and locate this line:
<connection-url>jdbc:oracle:thin:@//localhost:1521/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
1521: The port used to access the database. The default port is 1521.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting Oracle as the JMS data source
If you are running LiveCycle ES with a Oracle database, you must set Oracle to be the default data source
for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the Oracle JDBC driver is installed in the [appserver root]/server/all/lib
directory.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring Oracle for Adobe preconfigured JBoss
➤ To set Oracle to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the mysql-ds.xml file.
2. Navigate to the [appserver root]/docs/examples/jca directory and copy the oracle-ds.xml to the
[appserver root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/oracle-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your Oracle connection settings:
<jndi-name>OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@youroraclehost:1521:yoursid
</connectionurl>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>x</user-name>
<password>y</password>
4. Replace the bold text with values that are specific to your database:
●
OracleDS: Change this value to DefaultDS.
●
youroraclehost: Replace this value with the host name of your Oracle server.
●
1521: If Oracle is not using the default port, replace this value with the appropriate port number.
●
yoursid: Replace this value with your Oracle System Identifier.
●
Replace x with the user name to access the Oracle database and y with the password associated
with the user. The application server uses these credentials to access the database.
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to Oracle:
<type-mapping>Oracle8</type-mapping>
7. Save and close the file.
8. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>Oracle8</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Save and close the file.
10. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
text within the <policy> element:
<application-policy name = "OracleDbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
<module-option name = "principal">database_name </module-option>
<module-option name = "userName">database_username</module-option>
<module-option name = "password">password</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
64
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring Oracle for manually installed JBoss
65
</login-module>
</authentication>
</application-policy>
11. Replace the bold text with values that are specific to your database:
database_name, database_username and password: The user name and password that the
application server uses to access the database.
12. Save and close the file.
13. Delete the mysql-jdbc2-service.xml file from the [appserver root]/server/all/deploy-hasingleton/jms
directory.
14. Copy the oracle-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory to the
[appserver root]/server/all/deploy-hasingleton/jms directory.
15. In the oracle-jdbc2-service.xml file in the [appserver root]/server/all/deploy-hasingleton/jms directory,
change OracleDS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
16. Save and close the file.
17. Rename the [appserver root]/server/all/deploy-hasingleton/jms/mysqldb-jdbc-state-service.xml file to
oracle-jdbc-state-service.xml.
18. Restart JBoss.
Configuring Oracle for manually installed JBoss
To enable JBoss to connect to the Oracle database that stores LiveCycle ES data, you must complete the
following tasks if you are manually deploying LiveCycle ES:
●
Obtain and copy the Oracle JDBC driver to the instance of JBoss where you will deploy LiveCycle ES.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy LiveCycle ES.
●
Configure JBoss to use Oracle for JMS.
Configuring the Oracle data source
Before configuring the Oracle data source, you must have already created the database on Oracle. (See
“Creating an Oracle database” on page 104.)
➤ To install the Oracle 10g database driver:
●
Copy the ojdbc14.jar driver file from the [LiveCycleES root]/lib/db/oracle directory to the [appserver
root]/server/all/lib directory. In addition, you can download the Oracle 10g Release 2 (10.2.0.2 Thin)
driver from this location:
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring Oracle for manually installed JBoss
66
➤ To create the Oracle data source file:
1. Copy the adobe-ds-jboss-oracle.xml file from the [DVD_root]/third_party/datasources directory to the
[appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-oracle.xml file in a text editor and locate this line:
<connection-url>jdbc:oracle:thin:@//localhost:1521/adobe</connection-url
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
1521: The port used to access the database. The default port is 1521.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting Oracle as the JMS data source
If you are running LiveCycle ES with a Oracle database, you must set Oracle to be the default data source
for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the Oracle JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set Oracle to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file.
2. Copy the oracle-ds.xml file from the [appserver root]/docs/examples/jca directory to the [appserver
root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/oracle-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your Oracle connection settings:
<jndi-name>OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@youroraclehost:1521:yoursid
</connectionurl>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>x</user-name>
<password>y</password>
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring Oracle for manually installed JBoss
67
4. Replace the bold text with values that are specific to your database:
●
OracleDS: Change this value to DefaultDS.
●
youroraclehost: Replace this value with the host name of your Oracle server.
●
1521: If Oracle is not using the default port, replace this value with the appropriate port number.
●
yoursid: Replace this value with your Oracle System Identifier.
●
Replace x with the user name to access the Oracle database and y with the password associated
with the user. The application server uses these credentials to access the database.
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to Oracle:
<type-mapping>Oracle8</type-mapping>
7. Save and close the file.
8. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>Oracle8</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Remove the text: <!—optional since 4.0 and .. from the <datasource-mapping> tag to
uncomment it.
10. Save and close the file.
11. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
text within the <policy> element:
<application-policy name = "OracleDbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
<module-option name = "principal">database_name </module-option>
<module-option name = "userName">database_username</module-option>
<module-option name = "password">password</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
</login-module>
</authentication>
</application-policy>
12. Replace the bold text with values that are specific to your database:
database_name, database_username and password: The user name and password that the
application server uses to access the database.
13. Save and close the file.
14. Delete the hsql-jdbc2-service.xml file from the [appserver root]/server/all/deploy-hasingleton/jms
directory.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring SQL Server
68
15. Copy the oracle-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory to the
[appserver root]/server/all/deploy-hasingleton/jms directory.
16. Open the [appserver root]/server/all/deploy-hasingleton/jms/oracle-jdbc2-service.xml file and change
OracleDS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
17. Save and close the file.
18. Rename the hsqldb-jdbc-state-service.xml file located in the [appserver root]/server/all/
deploy-hasingleton/jms directory to oracle-jdbc-state-service.xml.
19. Restart JBoss.
Configuring SQL Server
To enable JBoss to connect to the SQL Server database that stores LiveCycle ES data, you must complete
the following tasks:
●
Obtain and copy the SQL Server JDBC driver files to the instance of JBoss where you will deploy
LiveCycle ES.
●
Create a SQL Server data source file and deploy it to the instance of JBoss where you will deploy
LiveCycle ES.
●
Configure JBoss to use SQL Server for JMS.
Configuring the SQL Server data source
Before configuring the SQL Server data source, you must have already created the LiveCycle ES database
on SQL Server. (See “Creating a SQL Server database” on page 106.)
➤ To install the SQL database driver:
1. Obtain the SQL Server 2005 JDBC 1.1 database driver from the Microsoft website.
2. (Windows) Download the *.exe file and run the file, and then extract the files to a temporary directory
(referred to as the [SQL_root] directory in the remainder of this section).
3. (Linux) Extract the *.tar.gz files to a temporary directory (referred to as the [SQL_root] directory in the
remainder of this section).
4. Copy the sqljdbc.jar file from the [SQL_root]/sqljdbc_1.1/enu directory to the [appserver
root]/server/all/lib directory.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring the SQL Server data source
69
➤ To create the SQL Server data source file:
1. Copy the adobe-ds-jboss-mssql.xml file from the [DVD_root]/third_party/datasources directory to the
[appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-mssql.xml file in a text editor and locate this line:
<connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=adobe</conn
ection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
1433: The port used to access the database. The default port is 1433.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
➤ To use integrated security to make a trusted connection with SQL Server:
1. Modify the adobe-ds.xml file, located in [appserver root]\server\all\deploy, to add
integratedSecurity=true to the connection URL. For example:
jdbc:sqlserver://<serverhost>:<port>;databaseName=<dbname>;integratedSec
urity=true.
2. Add the sqljdbc_auth.dll file to the Windows systems path (C:\Windows) on the computer that is
running JBoss. The sqljdbc_auth.dll file is located with the Microsoft SQL JDBC 1.1 driver installation
(default is <InstallDir>/sqljdbc_1.1/enu/auth/x86).
3. From the Windows Control Panel, navigate to the Services window.
4. Right-click the JBoss for Adobe LiveCycle ES v8.0 service and select Properties, and then click the
Log On tab.
5. Under Log On As, select the This Account option, and provide the information to a secure log in
account. This change is not required if you are running JBoss from the command line.
6. In SQL Server Management Studio Object Explorer, right-click the server and click Properties.
7. On the Security page, under Server authentication, select Windows authentication mode, and then
click OK.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring the SQL Server data source
70
8. In the SQL Server Management Studio dialog box, click OK.
9. Restart SQL Server so that the changes take effect.
Configuring JMS with Microsoft SQL Server
This section applies to both Adobe preconfigured JBoss and manually configured JBoss.
Setting SQL Server as the JMS data source
If you are running LiveCycle ES with a SQL Server database, you must set SQL Server to be the default data
source for JBoss. (It is configured by default to use Hypersonic for the data source.)
This procedure assumes that the SQL Server JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set SQL Server to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file. If you are
using the Adobe preconfigured JBoss from the DVD, delete the mysql-ds.xml file.
2. Install the JBossMQ patch file, jbossmq.jar. You must replace the existing jbossmq.jar file in the
[appserver root]/server/all/lib directory. You can obtain the updated jbossmq.jar file from the
thirdparty\jboss\patches directory in the installation media.
3. Navigate to the [appserver root]/docs/examples/jca directory and copy the mssql-ds.xml file to the
[appserver root]/server/all/deploy directory.
4. Open the mssql-ds.xml file in a text editor and modify the <local-tx-datasource> element with
your SQL Server connection settings:
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:sqlserver:// your-hostname:
your-port;DatabaseName=yourdatabase-name</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver
</driver-class>
<user-name>yourUserName</user-name>
<password>yourPassword</password>
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to SQL Server:
<type-mapping>MS SQLSERVER2000</type-mapping>
7. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>MS SQLSERVER2000</datasource-mapping>
<fk-constraint>true</fk-constraint>
8. (Manually configured JBoss only) Remove the comment tags from the <datasource-mapping> tag
to uncomment it. For example, remove “<!—optional since 4.0 ....” and the corresponding -->
tag.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring the SQL Server data source
71
9. Save and close the file.
10. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
lines within the <policy> element:
<application-policy name = "MSSQLDbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">database_name</module-option>
<module-option name = "userName">database_username</module-option>
<module-option name ="password">password</module-option>
<module-option name =
"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=
DefaultDS
</module-option>
</login-module>
</authentication>
</application-policy>
11. Replace the bold text with values that are specific to your database:
database_name, database_username, and password: The user name and password that the
application server uses to access the database.
12. Save and close the file.
13. Delete the [appserver root]/server/all/deploy-hasingleton/jms/hssql-jdbc2-service.xml file. Or, If you are
using the Adobe preconfigured JBoss from the DVD, delete the mysql-jdbc2-service.xml. Copy the
[appserver root]/docs/examples/jms/mssql-jdbc2-service.xml file to [appserver
root]/server/all/deploy-hasingleton/jms.
14. Open the [appserver root]/server/all/deployhasingleton/jms/mssql-jdbc2-service.xml file and change
the mbean code to reference MSSQLJDBCStateManager and DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="
ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
15. Rename the [appserver root]/server/all/deploy-hasingleton/jms/hsqldb-jdbc-state-service.xml file to
mssql-jdbc-state-service.xml. Or, if you are using the Adobe preconfigured JBoss from the DVD, rename
the [appserver root]/server/all/deploy-hasingleton/jms/mysql-jdbc-state-service.xml file to
mssql-jdbc-state-service.xml.
16. Open the [appserver root]/server/all/deploy-hasingleton/jms/mssql-jdbc-stateservice.xml file and
change the mbean code to reference MSSQLJDBCStateManager:
<mbean code="org.jboss.mq.sm.jdbc.MSSQLJDBCStateManager"
name="jboss.mq:service=StateManager">
17. Restart JBoss.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring DB2 for Adobe preconfigured JBoss
72
Configuring DB2 for Adobe preconfigured JBoss
To enable JBoss to connect to the DB2 database that stores LiveCycle ES data, you must complete the
following tasks if you are manually deploying LiveCycle ES:
●
Obtain and copy the DB2 JDBC driver to the instance of JBoss where you will deploy LiveCycle ES.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy LiveCycle ES.
●
Configure JBoss to use DB2 for JMS.
Configuring the DB2 data source
Before configuring the DB2 data source, you must have already created the database on DB2. (See
“Creating a DB2 database” on page 104.)
➤ To install the DB2 database driver:
●
Copy the db2jcc.jar and db2jcc_license_cu.jar files from the adobe/livecycle/lib/db/db2 directory to
the [appserver root]/server/all/lib directory.
➤ To obtain the latest db2-jdbc-service.xml file:
1. Go to labs.jboss.com/projects/download.
2. Click JBoss Application Server.
3. Click Download by 4.2.0 GA.
4. Select jboss-4.2.0.GA.zip.
5. After the file downloads, open jboss-4.2.0.GA.zip and extract the jboss-4.2.0.GA\docs\examples\jms\
db2-jdbc2-service.xml file to the [appserver root]/docs/examples/jms directory.
➤ To create the DB2 data source file:
1. Copy the adobe-ds-jboss-db2.xml file from the [DVD_root]/third_party/datasources directory to the
[appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-db2.xml file in a text editor and locate this line:
<connection-url>jdbc:db2://localhost:50000/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
50000: The port used to access the database. The default is 50000.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring DB2 for Adobe preconfigured JBoss
73
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting DB2 as the JMS data source
If you are running LiveCycle ES with a DB2 database, you must set DB2 to be the default JMS data source
for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the DB2 JDBC driver is installed in the [appserver root]/server/all/lib directory.
➤ To set DB2 to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the mysqldb-ds.xml file.
2. Copy the db2-ds.xml file from the [appserver root]/docs/examples/jca directory to the [appserver
root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/db2-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your DB2 connection settings:
<jndi-name>DB2DS</jndi-name>
<connection-url>jdbc:db2:your_database</connectionurl>
<driver-class>COM.ibm.db2.jdbc.app.DB2Driver</driver-class>
<user-name>x</user-name>
<password>y</password>
4. Replace the bold text with values that are specific to your database:
●
DB2DS: You must replace with DefaultDS.
●
your_database: The name of the DB2 database that stores the LiveCycle ES data.
●
COM.ibm.db2.jdbc.app.DB2Driver: Replace with com.ibm.db2.jcc.DB2Driver.
●
x and y: The user name and password that the application server uses to access the database.
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to DB2:
<type-mapping>DB2</type-mapping>
7. Save and close the file.
8. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>DB2</datasource-mapping>
<fk-constraint>true</fk-constraint>
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring DB2 for manually configured JBoss
74
9. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
text within the <policy> element:
<application-policy name = "DB2DbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
<module-option name = "principal">database_name </module-option>
<module-option name = "userName">database_username</module-option>
<module-option name = "password">password</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=DefaultDS
</module-option>
</login-module>
</authentication>
</application-policy>
10. Replace the bold text with values that are specific to your database:
database_name, database_username and password: The user name and password that the
application server uses to access the database.
11. Save and close the file.
12. Delete the mysql-jdbc.service.xml file from [appserver root]/server/all/deploy-hasingleton/jms.
13. Copy [appserver root]/docs/examples/jms/db2-jdbc2-service.xml file to the
[appserver root]/server/all/deploy-hasingleton/jms directory.
14. Open the [appserver root]/server/all/deploy-hasingleton/jms/db2-jdbc2-service.xml file and change
DB2DS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
15. Save and close the file.
16. Rename the mysql-jdbc-state-service.xml file, located in the [appserver root]/server/all/
deploy-hasingleton/jms directory, to db2-jdbc-state-service.xml.
17. Restart JBoss.
Configuring DB2 for manually configured JBoss
To enable JBoss to connect to the DB2 database that stores LiveCycle ES data, you must complete the
following tasks if you are manually deploying LiveCycle ES:
●
Obtain and copy the DB2 JDBC driver to the instance of JBoss where you will deploy LiveCycle ES.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy LiveCycle ES.
●
Configure JBoss to use DB2 for JMS.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring DB2 for manually configured JBoss
75
Configuring the DB2 data source
Before configuring the DB2 data source, you must have already created the database on DB2. (See
“Creating a DB2 database” on page 104.)
➤ To install the DB2 database driver:
1. Obtain the db2jcc.jar and db2jcc_license_cu.jar files from the DB2 installation directories on your DB2
server.
2. Copy the files from the adobe/livecycle/lib/db/db2 directory to the [appserver root]/server/all/lib
directory.
➤ To obtain the latest db2-jdbc-service.xml file:
1. Go to labs.jboss.com/projects/download.
2. Click JBoss Application Server.
3. Click Download by 4.2.0 GA.
4. Select jboss-4.2.0.GA.zip.
5. After the file downloads, open jboss-4.2.0.GA.zip and extract the db2-jdbc2-service.xml file to the
[appserver root]/docs/examples/jms directory.
➤ To create the DB2 data source file:
1. Copy the adobe-ds-jboss-db2.xml file from the [DVD_root]/third_party/datasources directory to the
[appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-db2.xml file in a text editor and locate this line:
<connection-url>jdbc:db2://localhost:50000/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
50000: The port used to access the database. The default is 50000.
●
adobe: The name of the database that stores the LiveCycle ES data. You will need to update the
default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You will need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring DB2 for manually configured JBoss
76
Setting DB2 as the JMS data source
If you are running LiveCycle ES with a DB2 database, you must set DB2 to be the default JMS data source
for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the DB2 JDBC driver is installed in the [appserver root]/server/all/lib directory.
➤ To set DB2 as the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file.
2. Copy the db2-ds.xml file from the [appserver root]/docs/examples/jca directory to the [appserver
root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/the db2-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your DB2 connection settings:
<jndi-name>DB2DS</jndi-name>
<connection-url>jdbc:db2:database_hostname:50000/your_database</connectionur
l>
<driver-class>COM.ibm.db2.jdbc.app.DB2Driver</driver-class>
<user-name>x</user-name>
<password>y</password>
4. Replace the bold text with values that are specific to your database:
●
DB2DS: You must replace with DefaultDS.
●
database_hostname:The hostname of the server hosting the database.
●
your_database: The name of the DB2 database that stores the LiveCycle ES data.
●
COM.ibm.db2.jdbc.app.DB2Driver: Replace with com.ibm.db2.jcc.DB2Driver.
●
x and y: The user name and password that the application server uses to access the database.
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to DB2:
<type-mapping>DB2</type-mapping>
7. Save and close the file.
8. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>DB2</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Remove the text: <!—optional since 4.0 and .. from the <datasource-mapping> tag to
uncomment it.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Configuring DB2 for manually configured JBoss
77
10. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
text within the <policy> element:
<application-policy name = "DB2DbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
<module-option name = "principal">database_name </module-option>
<module-option name = "userName">database_username</module-option>
<module-option name = "password">password</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=DefaultDS
</module-option>
</login-module>
</authentication>
</application-policy>
11. Replace the bold text with values that are specific to your database:
database_name, database_username and password: The user name and password that the
application server uses to access the database.
12. Save and close the file.
13. Delete the hssql-jdbc2-service.xml file from the [appserver root]/server/all/deploy-hasingleton/jms
directory.
14. Copy the db2-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory to the
[appserver root]/server/all/deploy-hasingleton/jms directory.
15. Open the [appserver root]/server/all/deploy-hasingleton/jms/db2-jdbc2-service.xml file and change
DB2DS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
16. Save and close the file.
17. Rename the hsqldb-jdbc-state-service.xml file, located in the [appserver root]/server/all/
deploy-hasingleton/jms directory, to db2-jdbc-state-service.xml.
18. Restart JBoss.
Adobe LiveCycle ES
Configuring JBoss Application Server
Preparing to Upgrade to LiveCycle ES
Next steps
Next steps
You can now upgrade your database, or create a new database for LiveCycle ES.
If you are upgrading LiveCycle Workflow, LiveCycle Form Manager, LiveCycle Forms with
User Management and Administrator, or LiveCycle PDF Generator, and using MySQL or SQL Server 2000,
you must upgrade your database. See “Upgrading the Database Server” on page 95.
If you are upgrading the following LiveCycle 7.x products, you must create a new database for
LiveCycle ES:
●
LiveCycle Reader Extensions
●
LiveCycle Document Security
●
LiveCycle Forms installed without User Management and Administrator
●
LiveCycle Print
●
LiveCycle Assembler
●
LiveCycle Policy Server
●
LiveCycle Barcoded Forms
See “Creating the LiveCycle ES database” on page 102.
78
7
Configuring WebSphere Application Server
This section describes how to install and configure the WebSphere Application Server that will host the
LiveCycle ES installation. WebSphere 6.1 must be installed in parallel (on the same or a different computer)
to the WebSphere 5.1.1 or WebSphere 6.0.1 server on which LiveCycle 7.x running.
Caution: If you intend to install WebSphere on the same computer where LiveCycle 7.x server is located,
do not perform the tasks in this section at this time. Proceed to “Upgrading the Database Server”
on page 95 or “Creating the LiveCycle ES database” on page 102, and then continue on to begin
the upgrade.
You can minimize LiveCycle server downtime by waiting until you are prompted during the
upgrade to stop the LiveCycle 7.x server before configuring the target LiveCycle ES application
server. At that time, the documentation will direct you back to this section to make the
configuration changes required.
This section uses the following documentation conventions.
Name
Default value
[appserver root]
(Windows) C:\Program Files\IBM\WebSphere\AppServer
(Linux and UNIX) /opt/IBM/WebSphere/AppServer
(AIX) /usr/IBM/WebSphere/AppServer
Installing WebSphere Application Server
You must install WebSphere Application Server 6.1 for running LiveCycle ES products.
When you run the LiveCycle ES installer, you should run it as the same user.
Installing a Fix Pack to WebSphere 6.1
After you have installed WebSphere 6.1, you must update to Fix Pack 5 or later before you deploy
LiveCycle ES.
Refer to the WebSphere support website for access to the WebSphere updates.
Setting the JAVA_HOME and PATH environment variables
As part of your WebSphere installation, a Java SDK was installed. The JAVA_HOME and PATH environment
variables must point to the Java SDK where LiveCycle ES is to be deployed.
➤ To set the JAVA_HOME environment variable (Windows):
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
79
Adobe LiveCycle ES
Configuring WebSphere Application Server
Preparing to Upgrade to LiveCycle ES
Setting the JAVA_HOME and PATH environment variables
80
3. Click Environment Variables.
4. In the System Variables area, click New.
5. Enter JAVA_HOME as the variable name and enter the directory where you installed Java SDK. This
directory is where WebSphere installed the Java SDK containing the /bin sub directory. For example,
type the following (including quotation marks):
"C:\Program Files\IBM\WebSphere\AppServer\java"
Note: To verify your JAVA_HOME environment variable, open a command prompt and run the following
command:
%JAVA_HOME%\bin\java -version
You should receive a response that begins with java version "1.5.0".
➤ To set the PATH environment variable (Windows):
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables.
4. In the System Variables area, select the PATH variable and click Edit. Append the following text to the
beginning of the variable value:
%JAVA_HOME%\bin;
➤ To set the DISPLAY setting (UNIX and Linux):
●
From a command prompt, type the following text:
DISPLAY=<IP Address of windows machine telnet, or cygwin to Unix-Linux
machine>:0.0
EXPORT DISPLAY.
Note: If the Display setting is not set correctly, the following error occurs when you start LiveCycle
Configuration Manager as: "No JRE is found...".
➤ To set the JAVA_HOME environment (UNIX and Linux):
●
It is recommended that you set the JAVA_HOME variable for Borne and Bash shells as shown in the
following example:
JAVA_HOME=/usr/IBM/WebSphere/AppServer/java
export JAVA_HOME
Note: The specific path varies based on the installation directory you specified and the operating system
you are installing on.
Adobe LiveCycle ES
Configuring WebSphere Application Server
Preparing to Upgrade to LiveCycle ES
Accessing WebSphere Administrative Console
81
➤ To set the PATH environment variable (UNIX and Linux):
●
It is recommended that you set the PATH variable for Borne and Bash shells as shown in the following
example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Accessing WebSphere Administrative Console
Several procedures in this section require you to access the Administrative Console of the
WebSphere Application Server.
➤ To start WebSphere Base:
1. To start the Administrative Console, from [application server home]/bin, type the appropriate command:
●
(Windows) startServer.bat server1
●
(UNIX, Linux) ./startServer.sh server1
Note: You must replace server1 with the name of your server instance.
➤ To access the WebSphere Administrative Console:
1. Start the WebSphere Application Server.
2. 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.
3. If WebSphere Global Security is enabled, type the WebSphere user ID and password in the boxes
provided.
4. Click Log In.
Directory permissions
The LiveCycle ES application needs to extract files to the [appserver root]/installedApps directory (for
example: /usr/IBM/WebSphere/AppServer); therefore, it is important that writable permissions be given to
that directory. If writable permissions cannot be given, the section below describes how to modify the
location for the extracted files.
➤ To modify the location for the extracted files:
1. Log in to the WebSphere Administrative Console.
2. Click Servers > Application Servers, and click your server name (for example, click server1).
3. Under Server Infrastructure, click Java and Process Management.
4. Click Process Definition.
Adobe LiveCycle ES
Configuring WebSphere Application Server
Preparing to Upgrade to LiveCycle ES
Preparing WebSphere Application Server
82
5. Under Additional Properties, click Java Virtual Machine.
6. Under Additional Properties, click Custom Properties.
7. Click New and create a custom property named adobeidp.RootDirectory.
8. Set the value of adobeidp.RootDirectory to the path where Adobe native files should be extracted (for
example, [appserver root]/profiles/[server]/installedApps).
9. Save and restart the application server.
Preparing WebSphere Application Server
This section describes how to prepare and configure an application server instance for your LiveCycle ES
deployment.
Required application server instances
LiveCycle ES requires one or more application server instances. LiveCycle ES is deployed into one
application server instance and, if you are using Business Activity Monitoring ES, it must be installed into
an application instance.
Increase SOAP request time-out
You must modify the SOAP request time-out value for LiveCycle ES.
➤ To increase the SOAP request time-out value:
1. Navigate to your [appserver root] directory and search for all files named soap.client.props. Multiple files
may have this name. Perform steps 2 to 4 for each of them.
2. Open the file in a text editor, find the com.ibm.SOAP.requestTimeout property, and change the value
from 180 to 1800.
3. Save the file(s).
4. In the navigation tree, click Servers > Application Servers and, in the right pane, click the server
name.
5. Under Server Infrastructure, expand Administration > Administration Services.
6. Under Additional Properties, click JMX connectors, and then click SOAPConnector from the list.
7. On the next screen, click Custom Properties, and then click requestTimeout from the list.
8. Under General Properties, in the Value box, change 600 to 1800.
9. Click OK or Apply.
10. Click Save directly to master configuration.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Configuring WebSphere Application Server
Configuring the LiveCycle ES database connectivity
83
Configuring the LiveCycle ES database connectivity
All configurations required for database connectivity are discussed in Upgrading to LiveCycle ES for
WebSphere at http://www.adobe.com/go/learn_lc_upgradeWebSphere.
Next steps
You can now upgrade your database, or create a new database for LiveCycle ES.
If you are upgrading LiveCycle Workflow, LiveCycle Form Manager, LiveCycle Forms with
User Management and Administrator, or LiveCycle PDF Generator, and using MySQL or SQL Server 2000,
you must upgrade your database. See “Upgrading the Database Server” on page 95.
If you are upgrading the following LiveCycle 7.x products, you must create a new database for
LiveCycle ES:
●
LiveCycle Reader Extensions
●
LiveCycle Document Security
●
LiveCycle Forms installed without User Management and Administrator
●
LiveCycle Print
●
LiveCycle Assembler
●
LiveCycle Policy Server
●
LiveCycle Barcoded Forms
See “Creating the LiveCycle ES database” on page 102.
8
Configuring WebLogic Server
This section describes how to install and configure WebLogic Server that will host the LiveCycle ES
installation. WebLogic Server 9.2 must be installed in parallel (on the same or a different computer) to the
WebLogic Server 8.1 on which LiveCycle 7.x is running.
Caution: If you intend to install WebSphere on the same computer where LIveCycle 7.x server is located,
do not perform the tasks in this section at this time. Proceed to “Upgrading the Database Server”
on page 95 or “Creating the LiveCycle ES database” on page 102, and then continue on to begin
the upgrade.
You can minimize LiveCycle server downtime by waiting until you are prompted during the
upgrade to stop the LiveCycle 7.x server before configuring the target LiveCycle ES application
server. At that time, the documentation will direct you back to this section to make the
configuration changes required.
This section uses the following documentation conventions:
Name
Default value
[appserver root]
(Windows) C:\bea\weblogic92
(Linux and UNIX) /opt/bea/weblogic92
BEA_HOME
(Windows) C:\bea
(Linux and UNIX) /opt/bea
[appserverdomain]
(Windows) C:\bea\user_projects\domains\base_domain
By default the domain is called
“base_domain”.
(Linux and UNIX) /opt/bea/user_projects/domains/base_domain
Overview
You will perform the following tasks to install and configure your BEA WebLogic Server 9.2 environment:
1. Obtain WebLogic Server 9.2 and install as per the manufacturer’s documentation. (See “Installing
WebLogic Server” on page 85).
2. Create and configure the WebLogic Server domain. (See “Configuring anonymous admin look-up” on
page 90).
3. Access the WebLogic Server Administration Console.
4. Create a Managed Server. (See “Creating a new WebLogic Managed Server” on page 89).
5. Configure application server and data source connections. (See “Configuring WebLogic Server” on
page 90).
84
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
LiveCycle ES requirements for WebLogic
85
LiveCycle ES requirements for WebLogic
There are two primary startup scenarios for WebLogic:
●
Using Node Manager and configuring through the Administration Server
●
Directly starting the Managed Servers with configurations in the StartManagedWebLogic scripts
To use the automatic configuration features of LiveCycle Configuration Manager (this is the recommended
option), you must use the Node Manager and configure through the Administration Server.
If you are directly starting the Managed Servers, you can still use the automatic configuration features of
LiveCycle Configuration Manager. However, you must manually enter the
LiveCycle Configuration Manager changes into the StartManagedWebLogic scripts. See Upgrading to
LiveCycle ES for WebLogic at http://www.adobe.com/go/learn_lc_upgradeWebLogic for the appropriate
steps.
Installing WebLogic Server
Obtain WebLogic Server 9.2 for your operating system and install it according to the manufacturer’s
documentation. See the BEA website for more information at http://bea.com/.
Note: If you have WebLogic Server 9.1 installed, uninstall it before installing WebLogic Server 9.2.
In addition to the space required to install LiveCycle ES, your environment variable TEMP or TMP must
point to a valid temporary directory with at least 500 MB plus another 1 GB to unpack image files.
You must install and run WebLogic Server using a user account with computer administrator privileges.
Installing the J2SE SDK
You must upgrade the BEA JRockit® JDK to 1.5.0_06 on Windows and Linux platforms.
➤ To install the JDK:
1. You can download the JDK updates for Windows or Linux from this location:
http://commerce.bea.com/products/weblogicjrockit/5.0/jr_50.jsp
2. Download the specific version for your platform from the following section:
JRockit 5.0 R26.4 CR302700 (for use with WLS 9.2 MP1)
Java Development Kit
As part of your WebLogic installation, a Java SDK was installed. The JAVA_HOME and PATH environment
variables must point to the Java SDK where LiveCycle ES is to be deployed.
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Installing the J2SE SDK
86
➤ To set the JAVA_HOME environment (Windows):
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables.
4. In the System Variables area, click New.
5. Enter JAVA_HOME as the variable name and the directory where you installed Java SDK. This directory
is where WebLogic installed the Java SDK containing the /bin subdirectory. For example, type this text:
C:\bea\jrockit-jdk1.5.0_06
Note: To verify your JAVA_HOME environment variable, open a command prompt and run the following
command:
%JAVA_HOME%\bin\java -version
You should receive a response that begins with java version "1.5.0".
➤ To set the PATH environment variable (Windows):
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables.
4. In the System Variables area, select the PATH variable and click Edit. Append the following text to the
beginning of the variable value:
%JAVA_HOME%\bin;
➤ To set the JAVA_HOME environment (UNIX and Linux):
●
It is recommended that you set the JAVA_HOME variable for Borne and Bash shells as shown in the
following example:
JAVA_HOME=/opt/java1.5
export JAVA_HOME
Note: The specific path varies based on the installation directory you specified and the operating system
you are installing on.
➤ To set the PATH environment variable (UNIX and Linux):
●
It is recommended that you set the PATH variable for Borne and Bash shells as shown in the following
example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Creating the WebLogic Server domain
87
Creating the WebLogic Server domain
To deploy applications on WebLogic Server, you must create a WebLogic Server domain. A domain is the
basic administrative unit for WebLogic Server. Here are the two basic types of WebLogic Server domains:
Standalone Server Domain: This type of domain can be used for development or test environments
in which a single server instance acts as both Administration Server and Managed Server. This option is
easier to manage and allows you to use the hot deploy feature in WebLogic on a development
environment.
Domain with Managed Servers: A production environment typically consists of an Administration
Server with one or more Managed Servers. The Administration Server is used to perform management
operations; the applications and resources are deployed to individual Managed Servers.
Note: In production environments, BEA recommends that you deploy applications only on Managed
Servers in the domain; the Administration Server should be reserved for management tasks.
➤ To create a WebLogic domain with Managed Servers:
1. From a command prompt, start the WebLogic Configuration Wizard by navigating to the
[appserver root]/common/bin directory and typing the appropriate command:
●
(Windows) config.cmd
●
(Linux, UNIX) ./config.sh
2. On the Create Or Extend A Configuration screen, select Create a new WebLogic domain and click
Next.
3. On the Select Domain Source screen, select Generate a domain configured automatically to
support the following BEA products: and click Next.
Note: By default, WebLogic Server (Required) is selected. Ensure that Workshop for WebLogic
Platform is deselected.
4. Type your WebLogic user name and password, confirm the password by retyping it, and then click
Next. Record this information because LiveCycle Configuration Manager will prompt you for the
WebLogic user name and password.
5. In the WebLogic Domain Startup Mode panel, select Production Mode.
Caution: Adobe does not recommend using Development Mode.
6. In the right panel, select the BEA-supplied JDK according to your operating system and then click Next.
●
(Windows, Linux) JRockit SDK [email protected] BEA_HOME/jrockit90_150_06. You must select Other
JDK in the UI and specify the location of the jrockit-jdk1.5.0_06.
●
(Solaris) Sun SDK 1.5.0_04 @ BEA_HOME/jdk150_04
7. On the Customize Environment And Services Settings screen, make sure that No is selected and then
click Next.
8. On the Create WebLogic Domain screen, either accept the default values or enter the domain name
and location as required, and click Create.
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
WebLogic Administration Server tasks
88
9. On the Creating Domain screen, when the configuration creation is 100% complete, do the following
tasks:
●
(Windows) Select Start Admin Server and click Done.
●
(Linux, UNIX) Click Done. Start the server by navigating from a command prompt to the
[appserverdomain] and typing ./startWebLogic.sh
10. When prompted, enter the WebLogic user name and password you entered in step 4.
WebLogic Administration Server tasks
This section outlines the steps to correctly configure the Administration Server to deploy LiveCycle ES.
➤ To set the memory size for managed servers:
1. To access the WebLogic Administration Console, type http://[host name]:[Port]/console in
the URL line of a web browser, where [Port] is the non-secure listening port. By default, this port
value is 7001.
2. On the login screen, type your WebLogic user name and password and click Log In.
3. Under Change Center, click Lock & Edit.
4. Under Domain Structure, expand Environment and click Servers.
5. In the right pane, under Servers, click the name of the Administration Server.
6. On the Configuration tab, click the Server Start tab.
7. In the Arguments field, type this text:
(Solaris) -Xms256m –Xmx1024m –XX:MaxPermSize=256m
(All other operating systems) -Xms256m –Xmx1024m
8. Click Save and then click Activate Changes.
➤ To set the memory size for the managed server:
1. Move to the following directory: BEA_HOME\user_projects\domains\[appserverdomain]\bin
2. Edit the following file in a text editor:
●
(Windows) setDomainEnv.cmd
●
(UNIX) setDomainEnv.sh
3. Search for the line set MEM_ARGS=-Xms256m -Xmx512m and change it to MEM_ARGS=-Xms256m
-Xmx1024m.
4. Search for the following line: -XX:MaxPermSize=128m and change it to -XX:MaxPermSize=256m.
Note: There are two locations of -XX:MaxPermSize=256:
●
if "%JAVA_VENDOR%"=="Sun" (...
●
If "%JAVA_VENDOR%"=="HP" (...
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Starting Node Manager
89
Starting Node Manager
You must start the Node Manager before continuing the rest of the sections in this chapter.
➤ To start Node Manager on Windows:
1. If the WebLogic Node Manager was installed as a Windows service, open the Windows Services control
panel and ensure that the WebLogic Node Manager service is running. For example, the WebLogic
Node Manager service will appear similar to the value BEA Products NodeManager
(C_bea_weblogic92).
2. If the WebLogic Node Manager was not installed as a Windows service, do these tasks:
●
From a new command prompt, navigate to the [appserver root]\server\bin directory.
●
Type the following command:
startNodeManager.cmd
➤ To start Node Manager on UNIX or Linux:
1. From a new command prompt, navigate to the [appserver root]/server/bin directory.
2. Type the following command:
./startNodeManager.sh
Creating a new WebLogic Managed Server
You must deploy LiveCycle ES applications on Managed Servers in a domain; the Administration Server
should be reserved for management tasks. For information about creating a server domain and about
Administration and Managed Servers, see the WebLogic product documentation.
Note: The following procedure highlights the changes required to the default properties. For properties
that are not provided, accept the existing settings. For more information about these screens, see
WebLogic Help.
➤ To create a new WebLogic Managed Server:
1. If WebLogic Administration Server is not already running, from a command prompt, navigate to the
BEA_HOME\user_projects\domains\[domainname] directory and type the appropriate command:
●
(Windows) startWebLogic.cmd
●
(Linux, UNIX) ./startWebLogic.sh
2. To access the WebLogic Administration Console, type http://[host name]:7001/console in the
URL line of a web browser.
3. Type the user name and password that were used to create this WebLogic configuration, and then click
Log In.
4. Under Change Center, click Lock & Edit.
5. Under Domain Structure, expand Environment and click Servers.
6. In the right pane, under Servers, click New.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Configuring WebLogic Server
Configuring WebLogic Server
90
7. In the right pane, under Create a New Server, type a name for your managed server, such as server1,
in the Server Name box.
8. In the Server Listen Port box, type a port number that is not currently in use, such as 8001. The
Administration Server is already using port 7001.
9. Click Finish and then click Activate Changes.
10. Under Change Center, click Lock & Edit.
11. Click Environment > Machines.
12. In the right pane, under Machines, click New.
13. In Create a New Machine > Enter Machine Name, select the operating system you are using.
14. Click OK.
15. Click Environment > Servers and select the Managed Server you created.
16. In the Machine list, select the computer you just created.
17. Make sure that the listen port is the same as the port number you entered in step 8.
18. Click Save and then click Activate Changes.
Note: To start a Managed Server from the Administration Console, the Node Manager must also be
running. It is recommended that you always start and stop the Managed Server from the
Administration Console.
Note: Do not restart your server at this point. After all the WebLogic configuration changes are made, the
server will be restarted when you reach the procedure “Restarting WebLogic” on page 93.
Configuring WebLogic Server
You must make the following configuration changes to optimize your application server’s performance for
your LiveCycle ES installation.
Configuring anonymous admin look-up
You must enable anonymous admin lookup on the application server. This setting allows read-only access
to the WebLogic Server MBeans.
➤ To enable anonymous admin look-up:
1. With WebLogic Server running, type http://[host name]:[port]/console in the URL line of a
web browser to access the WebLogic Server Administration Console.
2. Type the user name and password that was used in creating this WebLogic configuration, and then
click Log In.
3. Click Lock & Edit.
4. Under Domain Structure, click the name of your domain.
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Configuring WebLogic for Web Services
91
5. In the right pane, click the Security tab.
6. Select Anonymous Admin Lookup Enabled and then click Save.
7. Click Activate Changes.
Note: Do not restart your server at this point. After all the WebLogic configuration changes are made, the
server will be restarted when you reach the procedure “Restarting WebLogic” on page 93.
Configuring WebLogic for Web Services
For LiveCycle ES to accept requests using web services, you must complete the following procedure to
modify authentication of the servlet container.
Note: This step is required for the following WebLogic known issue: CASE_ID_NUM: 690940: CASE TITLE:
WebLogic 9.2 Servlet Container always tries to authenticate username/password.
“An application will prompt for user name and password even though the application is not
configured to use any security constraints. Upon adding this flag and setting it to false, it will
disable the popup that normally surfaces during the request being forwarded as we see in our case.”
➤ To modify authentication for the servlet container:
1. Start the WebLogic Administration Server.
2. Open a command prompt and set the environment using the setWLSEnv script, as shown in the
following example:
●
(Windows): From the [BEA_HOME]\weblogic92\server\bin\ folder, type:
setWLSEnv.cmd
●
(Linux/UNIX): From the [BEA_HOME]/weblogic92/server/bin/ directory, type:
setWLSEnv.sh
3. Start the WebLogic scripting tool by typing the following command:
java weblogic.WLST
If you see “Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/WLST” complete the
following:
●
From a command prompt, set the environment using <BEA
Home>/weblogic92/server/bin/setWLSEnv.cmd
●
From a command prompt, copy the CLASSPATH returned from the setWLSEnv.[cmd | sh] and
append the export CLASSPATH, for example:
CLASSPATH=/usr/local/bea92/patch_weblogic920/profiles/default/sys_manife
st_classpath/weblogic_patch.jar:/usr/local/bea92/jdk150_04/lib/tools.jar
:/usr/local/bea92/weblogic92/server/lib/weblogic_sp.jar:/usr/local/bea92
/weblogic92/server/lib/weblogic.jar:/usr/local/bea92/weblogic92/server/l
ib/webservices.jar export CLASSPATH
●
From a command prompt, copy the PATH returned from the setWLSEnv.[cmd | sh] and append
export PATH, for example:
PATH=/usr/local/bea92/weblogic92/server/bin:/usr/local/bea92/jdk150_04/j
re/bin:/usr/local/bea92/jdk150_04/bin:/usr/local/bea92/weblogic92/server
/bin:/usr/local/bea92/jdk150_04/jre/bin:/usr/local/bea92/jdk150_04/bin:/
usr/sbin:/usr/bin export PATH
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Configuring the classpath and JVM arguments
92
4. Type the following commands in WLST to update servlet container authentication:
connect('<WebLogic username>','<WebLogic password>','<WebLogic URL>')
edit()
startEdit()
cd('SecurityConfiguration')
cd('<domain name>')
set('EnforceValidBasicAuthCredentials','false')
activate()
exit()
Note: The WebLogic URL will be in the format t3://hostname:[port], where the port is probably
7001.
Configuring the classpath and JVM arguments
To ensure that the managed server starts up properly while upgrading, you must add the following file
paths to the classpath of the managed server:
●
adobe-bmc-client.jar. (This file will be located in the [appserverdomain]/lib directory when the upgrade
is complete.)
●
weblogic.jar (Located in the [appserver root]/server/lib directory)
●
tools.jar (Located in the [java_home]/lib directory)
You must also configure the JVM arguments.
➤ To modify the classpath of the managed server:
1. Open a browser and log in to the WebLogic Server Administration Console.
2. In the Change Center pane, click Lock & Edit.
3. In the navigation pane, under Domain Structure, expand Environment and click Servers.
4. In the main panel, click the managed server name.
5. Click the Server Start tab.
6. In the Class Path box, enter the location and filename for the adobe-bmc-client.jar, weblogic.jar and
tools.jar JAR files to the beginning of the class path. For example:
On Windows:
C:\bea\user_projects\domains\base_domain\lib\adobe-bmc-client.jar;C:\bea\
jrockit90_150_04\lib\tools.jar;C:\bea\weblogic92\server\lib\weblogic.jar
On Solaris:
/opt/bea/user_projects/domains/pager/lib/adobe-bmc-client.jar:/opt/bea/
weblogic92/server/lib/weblogic.jar:/opt/bea/jdk150_04/lib/tools.jar
➤ To configure the JVM arguments:
1. Log in to the WebLogic Administration Console.
2. Under Change Center, click Lock & Edit.
3. Under Domain Structure, expand Environment and click Servers.
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Restarting WebLogic
93
4. In the right pane, under Servers, click the managed server name.
5. On the Configuration tab, click the Server Start tab.
6. In the Arguments field, type this text:
-Dadobeidp.RootDirectory=/opt/bea/user_projects/domains/pager/.
-Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true
-Djava.security.policy=/opt/bea/weblogic92/server/lib/weblogic.policy
-Xms256m -Xmx1024m
7. Click Save and then click Activate Changes.
Restarting WebLogic
After you make all your configuration changes, you need to restart WebLogic for the changes to take
affect. The WebLogic Managed Server and the WebLogic Administration Server need to be restarted. The
Node Manager does not need to be restarted.
➤ To stop WebLogic Managed Server:
1. From the WebLogic Server Administration Console, under Domain Structure, click the domain name.
2. Click the Control tab.
3. Select the check box beside the server you want to stop, click Shutdown, and select one of the
following options:
When work completes: Initiates a graceful shutdown of the selected server, causing the Managed
Server to notify its subsystems to complete all in-work requests. A graceful shutdown gives the
WebLogic Server subsystems time to complete certain application processing currently in progress.
Force Shutdown Now: Initiates a forced shutdown, causing the Managed Server to instruct
subsystems to immediately drop in-work requests.
4. At the WebLogic Server Administration Console prompt, click Yes to confirm the command.
You can verify that the Managed Server has been shut down by viewing the table at the bottom of the
Control tab. The table displays a list of all of the servers and indicates their current state.
➤ To stop WebLogic Administration Server:
1. From a command prompt, navigate to BEA_HOME\user_projects\domains\[appserverdomain]\bin.
2. Type the following command:
●
(Windows) stopWebLogic.cmd
●
(Linux, UNIX) ./stopWebLogic.sh
3. Enter the WebLogic user name and password.
Adobe LiveCycle ES
Configuring WebLogic Server
Preparing to Upgrade to LiveCycle ES
Configuring the LiveCycle ES database connectivity
➤ To restart WebLogic Administration Server:
1. From a command prompt, navigate to BEA_HOME/user_projects/domains/[appserverdomain].
2. Type the following command:
●
(Windows) startWebLogic.cmd
●
(Linux, UNIX) ./startWebLogic.sh
3. Enter the WebLogic user name and password.
➤ To restart WebLogic Managed Server (if it did not start automatically):
1. When the WebLogic Administration Server has started, log in to the WebLogic Server Administration
Console.
2. Click Lock & Edit.
3. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed
server.
4. On the next screen, click the Control tab.
5. Select the check box beside the managed server you want to start, and then click Start.
6. Click Yes.
Configuring the LiveCycle ES database connectivity
All configurations required for database connectivity are discussed in Upgrading to LiveCycle ES for
WebLogic at http://www.adobe.com/go/learn_lc_upgradeWebLogic.
Next steps
You can now upgrade your database, or create a new database for LiveCycle ES.
If you are upgrading LiveCycle Workflow, LiveCycle Form Manager, LiveCycle Forms with
User Management and Administrator, or LiveCycle PDF Generator, and using MySQL or SQL Server 2000,
you must upgrade your database. See “Upgrading the Database Server” on page 95.
If you are upgrading the following LiveCycle 7.x products, you must create a new database for
LiveCycle ES:
●
LiveCycle Reader Extensions
●
LiveCycle Document Security
●
LiveCycle Forms installed without User Management and Administrator
●
LiveCycle Print
●
LiveCycle Assembler
●
LiveCycle Policy Server
●
LiveCycle Barcoded Forms
See “Creating the LiveCycle ES database” on page 102.
94
9
Upgrading the Database Server
This section describes how to upgrade the database server associated with your LiveCycle server. These
instructions do not apply to turnkey upgrades. For information about upgrading MySQL 4.1 for a turnkey
upgrade, see Upgrading to LiveCycle ES for JBoss Using Turnkey at
http://www.adobe.com /go/learn_lc_upgradeTurnkey.
If you are upgrading any of the following LiveCycle 7.x products on MySQL 4.1 database server or
Microsoft SQL Server 2000, you must upgrade the database and migrate the database contents to the
version supported by LiveCycle ES:
●
LiveCycle Forms with User Management and Administrator
●
LiveCycle PDF Generator
●
LiveCycle Workflow
●
LiveCycle Form Manager
●
LiveCycle Barcoded Forms
See “Upgrading the MySQL database” on page 96 or “Upgrading SQL Server 2000 to SQL Server 2005” on
page 99.
Note: A default schema is associated with each database user. When LiveCycle Configuration Manager
initializes using a database user, the data is populated in the default schema of the user. During
upgrade, you must use the same user that was used for LiveCycle 7.x. This applies to Oracle, DB2 and
SQL Server.
Some LiveCycle 7.x products do not use a database. If you are upgrading the following products to
LiveCycle ES, you do not need to perform the tasks in this section:
●
LiveCycle Reader Extensions
●
LiveCycle Document Security
●
LiveCycle Forms installed without User Management and Administrator
●
LiveCycle Print
●
LiveCycle Assembler
If you are upgrading any of these products (and none of the products in the first list), you must create a
new database for use with LiveCycle ES. (See “Creating the LiveCycle ES database” on page 102.)
Note: If you are upgrading a combination of products, and some use a database and others do not, you
must upgrade the database as described in the first scenario.
LiveCycle Policy Server uses a different database than that used with LiveCycle Workflow, LiveCycle Form
Manager, LiveCycle Forms, and LiveCycle PDF Generator. If you are upgrading LiveCycle Policy Server, you
must create a new database for LiveCycle ES. During upgrade, LiveCycle Configuration Manager
automatically migrates the data from the LiveCycle Policy Server database to the LiveCycle ES database.
95
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Upgrading the Database Server
Upgrading the MySQL database
96
Upgrading the MySQL database
If the LiveCycle 7.x products you are upgrading use a MySQL database, manually migrate the LiveCycle 7.x
data from the LiveCycle 7.x database on MySQL 4.1 to the new LiveCycle ES database on MySQL 5.0. This
process involves installing a MySQL 5.0 database server and migrating data from the LiveCycle database
on MySQL 4.1 to the database on MySQL 5.0.
This manual data migration is required if you are upgrading LiveCycle Workflow, LiveCycle Form Manager,
LiveCycle Barcoded Forms, LiveCycle Forms with User Management and Administrator or LiveCycle PDF
Generator. (If you are upgrading the version of LiveCycle Forms that does not include User Management
and Administrator, there is no data to migrate.)
MySQL migration is not required if you are upgrading any of the following products:
●
LiveCycle Reader Extensions
●
LiveCycle Document Security
●
LiveCycle Forms installed without User Management and Administrator
●
LiveCycle Print
●
LiveCycle Assembler
●
LiveCycle Policy Server
Creating the LiveCycle ES database
Before manually migrating LiveCycle 7.x data, you must create an empty MySQL LiveCycle ES database.
Use the MySQL tools to create a MySQL 5 database for use with LiveCycle ES and a MySQL user account
that the application server can use to connect to the database. You also need to modify the MySQL
database server configuration. For information about creating the database and user account, see the
MySQL documentation. LiveCycle ES supports MySQL 5 with JBoss 4.0.
Tip: If you want to set up a database schema and new users on MySQL using a graphical user interface
(GUI), you must install the MySQL Administrator tool. For more information, see the MySQL user
documentation.
When installing the MySQL database, you must specify UTF-8 character encoding.
You will need the following information when you configure the data source on JBoss:
●
Database name
●
User name and password of the MySQL user account
●
Host name or IP address of database server
●
MySQL port number
Adobe LiveCycle ES
Upgrading the Database Server
Preparing to Upgrade to LiveCycle ES
MySQL database server configuration
97
MySQL user account
The MySQL user account that you create requires these privileges to access the tables in the LiveCycle ES
database:
●
SELECT
●
INSERT
●
UPDATE
●
DELETE
●
CREATE
●
DROP
●
REFERENCES
●
INDEX
●
ALTER
●
CREATE_TMP_TABLE
●
LOCK_TABLES
MySQL database server configuration
To prevent issues from occurring when uploading large files to MySQL, you must set the maximum
allowed communication packet size to 25 MB. You can set this property in the MySQL my.ini file (Windows)
or my.cnf file (Linux). For more information about the maximum allowed communication packet size
property in MySQL, see http://dev.mysql.com/doc/mysql/en/packet-too-large.html.
If your MySQL installation does not include a my.ini or my.cnf file, you must create one. For information
about the location of the file or how to create the file, see the MySQL documentation.
➤ To customize the MySQL configuration:
1. Open the my.ini (Windows) or my.cnf (Linux) file in a text editor.
2. Add the following line to the [mysqld] section:
max_allowed_packet=25M
3. Save and close the file.
Adobe LiveCycle ES
Upgrading the Database Server
Preparing to Upgrade to LiveCycle ES
Migrating the LiveCycle 7.x data to the LiveCycle ES database
98
Migrating the LiveCycle 7.x data to the LiveCycle ES database
If you are upgrading LiveCycle Forms with User Management and Administrator or
LiveCycle PDF Generator, you must manually migrate the data in the LiveCycle 7.x database (running on
MySQL 4.1) to the LiveCycle ES (running on MySQL 5.0).
Note: MySQL must be running when you perform the following steps to migrate LiveCycle 7.x data from
MySQL 4.1 to MySQL 5.0.
1. Dump the LiveCycle 7.x database by using the MySQL 4.1 mysqldump.exe tool and using the following
command:
●
In a command prompt, type the cd command to navigate to the [LiveCycle7 root]\mysql\bin
directory, and then type the MySQL command based on the following example:
mysqldump --add-locks --lock-tables -c --default-character-set=utf8
--skip-opt -p -u root -r adobe.sql -B adobe
In the example above, the following options may be modified:
●
-p refers to the MySQL 4.1 password. Notice that the password (-p) is blank in the example
above because the default password for MySQL root is blank, but the LiveCycle 7.x database may
use a new password.
●
-u refers to the MySQL 4.1 user name. The value root can be replaced with the appropriate user
name.
●
-r refers to the location of the file that contains the dumped data. You can change the name of
the file from adobe.sql, or you can include the path to the directory where you want to save
this file.
●
-B refers to the name of the database. The name is adobe by default; if your turnkey LiveCycle
7.x database (installed by turnkey) has a different name, use it instead.
2. If prompted, type the root password. If the password is blank, just press Enter.
3. Drop the empty database created by the LiveCycle Configuration Manager:
●
In the command prompt, type the cd command to [LiveCycleES root]\msql\bin, and then type the
following command:
mysql.exe –u root –ppassword –P mysqlPort
(where password and mysqlPort are the password and port you specified for MySQL 5.0 when
you installed it.)
●
At the mysql prompt, type show databases;
(This command lists the existing databases of LiveCycle ES. You should see the “adobe_meta”
database which is not in LiveCycle 7.x.)
●
At the mysql prompt, type DROP DATABASE IF EXISTS adobe;
(Here, adobe is the name of the database.)
4. Restore the contents of the MySQL 4.1 database to the LiveCycle ES database on MySQL 5.0:
●
At the mysql prompt, type the following command:
\. [LiveCycle7 root]\mysql\bin\adobe.sql
●
Quit the MySQL Command Line Client by typing quit
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Upgrading the Database Server
Upgrading SQL Server 2000 to SQL Server 2005
99
Upgrading SQL Server 2000 to SQL Server 2005
Upgrading from Microsoft SQL Server 2000 to SQL Server 2005 is done in-place. When you run the
upgrade program for SQL Server 2005, it replaces SQL Server 2000 and the new database server retains all
the data and configurations.
Note: Before upgrading to the SQL Server 2005 database, it is recommended that you review the
following article on user-schema separation:
http://msdn2.microsoft.com/en-us/library/ms190387.aspx
For information about upgrading a SQL Server database, see the SQL Server documentation. LiveCycle ES
supports SQL Server 2005 SP1 with JBoss 4.0 and WebSphere 6.1.0.5.
After upgrading SQL Server 2000 to SQL Server 2005, you can perform some configurations to ensure
optimal performance with LiveCycle ES. The SQL Server database can be configured with the Windows or
SQL Server authentication types. For LiveCycle ES the authentication type must be set to SQL Server.
If you are upgrading LiveCycle Policy Server, you must install a new instance of SQL Server 2005. The
instance of SQL Server 2000 must still be available. When you run the ugprade,
LiveCycle Configuration Manager migrates the LiveCycle Policy Server 7.x data from the SQL Server 2000
database to the SQL Server 2005 database.)
For instructions about setting up a new SQL Server 2005 database, see “Creating a SQL Server database”
on page 106.
Migrating LiveCycle data stored in a 4k pagesize tablespace on
DB2
If you are using a DB2 database server and your LiveCycle 7.x database tables were in the USERSPACE1 (4k)
tablespace on DB2, you must migrate your data to an 8k tablespace before upgrading to LiveCycle ES. The
steps in this section export LiveCycle 7.x data from the DB2 tablespace USERSPACE1 and import the data
to the LC8_DBNAME_DATA_8K tablespace for LiveCycle ES.
The steps in this section assumes that the LiveCycle 7.x database name is LC7_DBNAME and the user is
db2inst, and the LiveCycle ES database name is LC8_DBNAME and the user is db2inst. You can substitute
the appropriate database and user names.
➤ To migrate the LiveCycle 7.x data to an 8k tablespace:
1. From the command line, type the following command to create DDL for the LiveCycle 7.x tables:
db2look -d LC7_DBNAME -u db2inst -e -o alltables.sql
2. Export all LiveCycle 7.x tables created by the user db2inst from tablespace USERSPACE1 by typing the
following command:
db2move LC7_DBNAME EXPORT -ts USERSPACE1 -tc db2inst
Adobe LiveCycle ES
Upgrading the Database Server
Preparing to Upgrade to LiveCycle ES
Migrating LiveCycle data stored in a 4k pagesize tablespace on DB2
100
3. Create a new LiveCycle ES database by typing the following script (LC8_DBNAME can be whatever you
want to name the LiveCycle ES database):
CREATE DATABASE LC8_DBNAME USING CODESET UTF-8 TERRITORY DEFAULT;
CONNECT TO LC8_DBNAME;
CREATE BUFFERPOOL "LC8_DBNAME_BP8K" SIZE 50000 PAGESIZE 8192 NOT EXTENDED
STORAGE;
CONNECT RESET;
CONNECT TO LC8_DBNAME;
CREATE TEMPORARY TABLESPACE LC8_DBNAME_TEMP_8K IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING
('/home/db2inst/LC8_DBNAME_TEMP') EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL
LC8_DBNAME_BP8K;
CREATE REGULAR TABLESPACE LC8_DBNAME_DATA_8K IN DATABASE PARTITION GROUP
IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING
(FILE'/home/db2inst/LC8_DBNAME_DATA'64000) EXTENTSIZE 16 PREFETCHSIZE 16
BUFFERPOOL LC8_DBNAME_BP8K;
DROP TABLESPACE USERSPACE1;
COMMIT WORK;
CONNECT RESET;
CONNECT TO LC8_DBNAME;
ALTER BUFFERPOOL IBMDEFAULTBP IMMEDIATE SIZE 96000;
ALTER BUFFERPOOL BP8K IMMEDIATE SIZE 32000;
COMMIT WORK;
CONNECT RESET;
UPDATE DB CFG FOR LC8_DBNAME USING DBHEAP 4000;
UPDATE DB CFG FOR LC8_DBNAME USING LOGBUFSZ 2048;
UPDATE DB CFG FOR LC8_DBNAME USING LOCKLIST 2000;
UPDATE DB CFG FOR LC8_DBNAME USING CHNGPGS_THRESH 40;
UPDATE DB CFG FOR LC8_DBNAME USING LOGFILSIZ 4000;
DEACTIVATE DATABASE LC8_DBNAME;
ACTIVATE DATABASE LC8_DBNAME;
4. Open the file alltables.sql in a text editor.
5. At the beginning of the file find the line CONNECT TO LC7_DBNAME; and change it to CONNECT TO
LC8_DBNAME;
6. Replace all instances of USERSPACE1 with the name of the tablespace you created in step 2. In this
example, replace USERSPACE1 with LC8_DBNAME_DATA_8K.
7. Create the LiveCycle 7.x tables in the new LiveCycle ES database by typing the following command at
the command line:
db2 -tvf ./alltables.sql > alltables.log
8. Import the LiveCycle 7.x data by typing the following command:
db2move LC8_DBNAME import -io insert > LC8db2move.log
9. Open the LC8db2move.log file in a text editor and check for errors. If there are errors, do the following:
●
Open the corresponding tab.msg file(s) and record the name of table that failed.
●
Open the db2move.lst file and remove all lines except for the lines that match the tables that failed
to import their data.
●
Execute the command from step 8 again.
●
Open LC8db2move.log again to ensure your data was imported properly.
Adobe LiveCycle ES
Upgrading the Database Server
Preparing to Upgrade to LiveCycle ES
Next steps
101
Next steps
If you upgraded MySQL, you can begin the process of upgrading your LiveCycle 7.x products to
LiveCycle ES. Go to the document that corresponds with your application server:
●
Upgrading to LiveCycle ES for JBoss at http://www.adobe.com/go/learn_lc_upgradeJBoss
●
Upgrading to LiveCycle ES for WebSphere at http://www.adobe.com/go/learn_lc_upgradeWebSphere
●
Upgrading to LiveCycle ES for WebLogic at http://www.adobe.com/go/learn_lc_upgradeWebLogic
If you upgraded SQL Server, you must configure the SQL Server database server for LiveCycle ES. (See
“Creating a SQL Server database” on page 106.)
10
Creating the LiveCycle ES database
If you are upgrading a LiveCycle 7.x product that did not use a database, you must create a database for
use with LiveCycle ES. This section includes information about creating databases with the following
database servers:
●
MySQL 5 (supported on JBoss 4.0)
●
Oracle 10g (supported on JBoss 4.0, WebSphere 6.1.0.5, and WebLogic 9.2)
●
DB2 (supported on JBoss 4.0 and WebSphere 6.1.0.5)
●
SQL Server 2005 SP1 (supported on JBoss 4.0 and WebSphere 6.1.0.5)
The database will contain the following resources:
●
LiveCycle ES product data
●
LiveCycle ES run-time configurations
●
LiveCycle ES process data
●
Customer processes’ definitions and templates
●
Application Server data (such as JMS tables)
Before creating the database, you must ensure that you have read the preinstallation requirements and
have the required software installed.
If this is the first installation of LiveCycle ES, you must create an empty database. All of the tables required
to support LiveCycle ES will be created when you run the Initialize LiveCycle ES database task using
LiveCycle Configuration Manager. See the Upgrading to LiveCycle ES document for your application server.
Creating a MySQL database
Note: The information contained in this document is meant for users installing MySQL manually and not
for a turnkey installation. See Installing and Deploying LiveCycle ES for JBoss Using Turnkey at
www.adobe.com/go/learn_lc_installTurnkey.
Use the MySQL tools to create a MySQL 5 database for use with LiveCycle ES and a MySQL user account
that the application server can use to connect to the database. You also need to modify the MySQL
database server configuration. For information about creating the database and user account, see the
MySQL documentation. LiveCycle ES supports MySQL 5 with JBoss 4.0.
Tip: To set up a database schema and new users on MySQL using a graphical user interface (GUI), you
must install the MySQL Administrator tool. (See the MySQL user documentation.)
When installing the MySQL database, you must specify UTF-8 character encoding.
You will need the following information when you configure the data source on JBoss:
●
User name and password of the MySQL user account
●
Host name or IP address of database server
●
MySQL port number
102
Adobe LiveCycle ES
Creating the LiveCycle ES database
Preparing to Upgrade to LiveCycle ES
Creating a MySQL database
103
MySQL user account
The MySQL user account that you create requires these privileges to access the tables in the LiveCycle ES
database:
●
SELECT
●
INSERT
●
UPDATE
●
DELETE
●
CREATE
●
DROP
●
REFERENCES
●
INDEX
●
ALTER
●
CREATE_TMP_TABLE
●
LOCK_TABLES
MySQL database server configuration
To prevent issues from occurring when uploading large files to MySQL, you must set the maximum
allowed communication packet size to 25 MB. You can set this property in the MySQL my.ini file (Windows)
or my.cnf file (Linux). For more information about the maximum allowed communication packet size
property in MySQL, see dev.mysql.com/doc/mysql/en/packet-too-large.html.
If your MySQL installation does not include a my.ini or my.cnf file, you must create one. For information
about the location of the file or how to create the file, see the MySQL documentation.
➤ To customize the MySQL configuration:
1. Open the my.ini (Windows) or my.cnf (Linux) file in a text editor.
2. Add the following line to the [mysqld] section:
max_allowed_packet=25M
3. Save and close the file.
MySQL initial server configuration recommendations
These configuration settings are recommended for MySQL server:
●
Key Buffer Size: 64 MB
●
Sort Buffer Size: 1 MB
●
Buffer Pool Size:100 MB
●
Additional Memory Pool Size: 5 MB
●
Log Buffer Size: 8 MB
●
Max Packet Size: 25 MB
●
Read Buffer Size: 1 MB
●
Read and Buffer Size: 1 MB
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Creating the LiveCycle ES database
Creating an Oracle database
104
Creating an Oracle database
If you prefer not to use the default database that was created when you installed Oracle 9i or Oracle 10g,
create a new database using the Database Configuration Assistant tool. LiveCycle ES supports Oracle 9i
and Oracle 10g with WebLogic 9.2, WebSphere 6.1.0.5, and JBoss 4.0.
You must create your Oracle database to support UTF-8 characters. Ensure that the database character set
is Unicode (AL32UTF8). You must use the transaction processing template when creating the database.
The connection mode for the server must be “Shared Server Mode”.
You must also create a new user on the database and assign it the following system privileges:
●
CREATE SEQUENCE
●
CREATE VIEW
●
UNLIMITED TABLESPACE
●
CREATE TABLE
●
CREATE CLUSTER
●
CREATE SESSION
For deployments on Linux, the user name must not exceed 8 characters and, on Windows, it must not
exceed 12 characters.
You need the following information when you configure the data source on the application server:
●
SID (Service ID)
●
User name and password of the Oracle user account
●
Host name or IP address of database server
●
Oracle port number (default is 1521)
For information about using Oracle 9i or Oracle 10g, see the appropriate user documentation.
Creating a DB2 database
Create a DB2 database by running the script provided in this section. The script is tuned for a system that
will use 1 GB of memory for the database. If your system has a smaller amount of memory dedicated for
the database, see the DB2 documentation for details about configuring your system settings. LiveCycle ES
supports DB2 with WebSphere 6.1.0.5 and JBoss 4.0.
You must also create a user with SYSADM and DBADM privileges that can be used when configuring the
data source on the application server. For information about creating a user, see the DB2 documentation.
For deployments on Linux and UNIX, the user name must not exceed 8 characters and, on Windows, it
must not exceed 12 characters.
You need the following information when you configure the data source on the application server:
●
Database name
●
User name and password of the DB2 user account
●
Host name or IP address of database server
●
DB2 port number
Adobe LiveCycle ES
Creating the LiveCycle ES database
Preparing to Upgrade to LiveCycle ES
Creating a DB2 database
105
➤ To create a DB2 database:
1. On the computer that hosts DB2, create a new text file that includes the following DB2 script:
create database dbname using codeset utf-8 territory default;
connect to dbname;
CREATE BUFFERPOOL "BP8K" SIZE 50000 PAGESIZE 8192 NOT EXTENDED STORAGE;
connect reset;
connect to dbname;
CREATE TEMPORARY TABLESPACE DBNAME_TEMP_8K IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING
('DB2_root\DBNAME_TEMP')
EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE DBNAME_DATA_8K IN DATABASE PARTITION GROUP
IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING
(FILE'DB2_root\DBNAME_DATA'64000) EXTENTSIZE 16 PREFETCHSIZE 16
BUFFERPOOL
BP8K;
commit work;
connect reset;
connect to dbname;
alter bufferpool ibmdefaultbp immediate size 96000;
alter bufferpool bp8k immediate size 32000;
commit work;
connect reset;
update db cfg for dbname using dbheap 4000;
update db cfg for dbname using logbufsz 2048;
update db cfg for dbname using locklist 2000;
update db cfg for dbname using chngpgs_thresh 40;
update db cfg for dbname using logfilsiz 4000;
deactivate database dbname;
activate database dbname;
2. Make the following changes to the script:
●
Replace the instances of dbname and DBNAME with the name that you want for the LiveCycle ES
database.
●
Replace DB2_root with the path to the root directory where DB2 is installed.
●
Ensure that no commands include line breaks and each command is terminated by a semicolon (“;”).
●
Change 9000 in the following line based on your database size:
(FILE'DB2_root\DBNAME_DATA'9000)
This number specifies the minimum number of pages required to initialize the database. You can
also change this number by using the DB2 administration tools after initializing the database.
3. Save the text file in a location that DB2 Command Line Processor can access.
4. Open a DB2 command prompt and type the following command to run the script:
db2 -tf <path_to_script_file>/<script_file_name>
Adobe LiveCycle ES
Creating the LiveCycle ES database
Preparing to Upgrade to LiveCycle ES
Creating a SQL Server database
106
➤ To add a user to the new database:
1. Log in to the IBM Control Center.
2. Click [database_name] > User and Group Objects > DB Users and then select Add User.
3. Select the user you want to use.
4. Under Authorities, select Connect to database, Create tables, and Database administration
authority.
5. Click OK.
Creating a SQL Server database
You can create a SQL Server database that LiveCycle ES will use to store run-time and configuration data.
For information about creating a SQL Server database, refer to the SQL Server documentation. LiveCycle ES
supports SQL Server 2005 SP1 with JBoss 4.0, BEA WebLogic 9.2, and IBM WebSphere 6.1.0.5.
Create a SQL Server database and create a user with DB_OWNER privileges that can be used when
configuring the data source on the application server. For information about creating the database and
user, see the SQL Server documentation.
You need the following information when you configure the data source on the application server:
●
Database name
●
User name and password of the SQL Server user account
●
Host name or IP address of database server
●
SQL Server port number
The SQL Server database can be configured with the Windows or SQL Server authentication types. For
LiveCycle ES, the authentication type must be set to SQL Server.
Install the SQL Server database driver:
●
If you have not done so already, download the SQL Server 2005 JDBC Driver 1.1 from the following
location on the Microsoft website:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6d483869-816a-44cb-9787-a866235
efc7c&DisplayLang=en
Follow the instructions on the website for downloading and installing the driver. Take note of the
directory location where you install the driver on your system.
Setting up SQL Server for LiveCycle ES
Before you create the LiveCycle ES database, optimize SQL Server by changing these settings.
Increasing memory
The default SQL Server settings do not aggressively allocate memory. This situation significantly impacts
performance on most deployments of a SQL Server database.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Creating the LiveCycle ES database
Setting up SQL Server for LiveCycle ES
107
➤ To increase the memory for SQL Server:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you want to
host the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Memory page and enter a size in the Minimum Server Memory (in MB) box that is equal to
the size of the free memory you have on the server.
Setting processor priority
On dedicated database servers (recommended for production installations of LiveCycle ES), the SQL Server
process is configured to prevent over-consumption of the system CPU resources.
➤ To set the processor priority:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you want to
host the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Processors page and select Boost SQL Server Priority.
Increasing the recovery interval
This setting specifies the amount of time the deployment waits for recovery after a crash. The SQL Server
default setting is 1 minute. Increasing this setting to a larger value improves performance because it
allows the server to be more relaxed in writing changes from the database log to the database files. This
setting does not compromise the transactional behavior; however, it does affect the size of the log file that
is replayed on startup.
➤ To increase the recovery interval:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you want to
host the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Database Settings page and type 5 in the Recovery Interval (Minutes) box.
Note: After you change these settings, restart the SQL Server database to ensure that the settings take
effect.
Integrated Security
If you are using SQL Server 2005 integrated security, you must set your SQL Server 2005 database to Mixed
Mode for WebSphere or WebLogic. For JBoss (Windows) you can set your SQL Server 2005 database to
either Mixed Mode or Windows Authentication Mode. If you set your SQL Server 2005 database to
Windows Authentication Mode for JBoss (Windows), you must follow the steps in “To use integrated
security to make a trusted connection with SQL Server:” on page 69.
Adobe LiveCycle ES
Creating the LiveCycle ES database
Preparing to Upgrade to LiveCycle ES
Sizing your SQL Server database
108
Sizing your SQL Server database
The default database sizes that SQL Server provides are too small for LiveCycle ES. Even if the database is
set to auto-grow, unintended consequences can occur, such as reduced performance when the database
grows or the size growth begins to fragment the disk. Because of these effects, it is best to preallocate the
database size at creation to reflect your deployment requirements:
Medium size deployments: Environments where the LDAP directory has around 100,000 users and
around 10,000 groups. Set Database Data Initial Size to 1 GB, and set autogrowth to 250 MB.
Large size deployments: Environments where the LDAP directory has around 350,000 users and more
than 10,000 groups. Set Database Data Initial Size to 2 GB, and set autogrowth to 1 GB.
Note: Database growth is always restricted to a certain size. Administrators should monitor the resource
usage of the LiveCycle ES database to ensure that it does not run out of restricted space or the space
available on the disks where the database resides.
Creating the LiveCycle ES database
After you have optimized the SQL Server, you are ready to create the LiveCycle ES database.
➤ To create the LiveCycle ES database:
1. Using Microsoft SQL Server Management Studio, click Server, and then right-click Database and select
New Database.
2. In the New Database dialog box, enter the database name of your choice, database_name.
3. Ensure that Use Full-Text Indexing is deselected.
4. In the Database Data Initial Size MB box, enter the appropriate value:
●
For small development or small production system: 200 MB.
●
For larger systems: see “Sizing your SQL Server database” on page 108.
5. In the Database Data Autogrowth box, enter 50%.
6. In the Database Log Initial Size box, enter the appropriate value:
●
For small development or small production system: 20MB
●
For larger systems: see “Sizing your SQL Server database” on page 108.
7. In the Database Log Autogrowth box, enter 50%.
Creating the LiveCycle ES user in SQL Server
In the following procedure, database_name represents the name you specified when you created your
database, and database_username represents the name you specify for the new user.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Creating the LiveCycle ES database
Associating the LiveCycle ES user with the database
109
➤ To create the LiveCycle ES user:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you created the
LiveCycle ES database.
2. Click Server > Security, and then right-click Logins and select New Login.
3. In the New Login dialog box, enter the login name database_username.
4. Select SQL Server Authentication and type a new password.
5. Deselect Enforce Password Expiration. User must change password on next login is also
deselected.
6. Leave the default database as Master, and click OK.
7. Click Server > Databases > database_name > Security, and then right-click Schemas and select New
Schema.
8. In the Schema Name box, type database_username, and then click OK.
9. Click Server > Databases > database_name > Security, right-click Users, and then select New User.
10. In the New User dialog box, enter the login name and user name database_username.
11. Set the default schema to database_username.
Note: The schema name should be the same as the database_username.
12. In the Schemas Owned By This User area, select the schema database_username.
13. In the Database Role Membership area, select db_owner.
Associating the LiveCycle ES user with the database
After you have created the LiveCycle ES user, associate it with the LiveCycle ES database.
➤ To associate the LiveCycle ES user with the database:
1. Click Security > Logins, and then right-click database_username and select Properties.
2. In the Login Properties, in the General page, set the user’s default database to database_name.
3. Select the User Mapping page. In the Users Mapped To This Login section, verify that database_name
is selected, User is set to dbo, and Default Schema is set to dbo.
4. Ensure that database_name is selected in the Users Mapped To This Login table, and ensure that
db_owner and public are selected in the Database Role Membership For database_name table.
Setting the isolation level for the LiveCycle ES database
SQL Server 2005 provides a number of new isolation levels. LiveCycle ES requires a specific isolation level
to manage deadlocking when long-running transactions occur at the same time as numerous shorter
reads.
Adobe LiveCycle ES
Creating the LiveCycle ES database
Preparing to Upgrade to LiveCycle ES
Next steps
110
➤ To set the isolation level:
1. Click Databases, and then right-click database_name and select New Query.
Note: database_name represents the name you specified when you created your database.
2. In the Query panel, type the following text:
ALTER DATABASE database_name
SET READ_COMMITTED_SNAPSHOT ON
GO
3. Click Execute. A response is displayed in the messages panel.
Next steps
You can begin the process of upgrading your LiveCycle 7.x products to LiveCycle ES. Go to the document
that corresponds with your application server:
Upgrading to LiveCycle ES for JBoss at http://www.adobe.com/go/learn_lc_upgradeJBoss
Upgrading to LiveCycle ES for WebSphere at http://www.adobe.com/go/learn_lc_upgradeWebSphere
Upgrading to LiveCycle ES for WebLogic at http://www.adobe.com/go/learn_lc_upgradeWebLogic
11
Migrating to LiveCycle ES
Connector for EMC Documentum
Automatic upgrades from LiveCycle Forms 7.x for Documentum to LiveCycle ES are not supported. The
following tasks are required to migrate from LiveCycle Forms for Documentum to
LiveCycle ES Connector for EMC Documentum:
●
Install and deploy LiveCycle ES, including LiveCycle Connector for EMC Documentum (see the Installing
and Deploying LiveCycle ES document for your application server). LiveCycle applications and forms
continue to work (with some restrictions).
●
Create new applications and forms using the samples and documentation.
●
Re-create LiveCycle 7.x applications and forms by leveraging the process samples included with the
LiveCycle ES and user interface samples from the LiveCycle Developer Center on www.adobe.com.
When you install and deploy LiveCycle ES, LiveCycle Forms for Documentum is compatible with
LiveCycle Forms ES, with some restrictions:
●
You must use LiveCycle Designer 7.x for Documentum to update existing form templates. Features
introduced in LiveCycle ES, such as fragments, are therefore not available for these forms.
●
The platforms supported for running LiveCycle Forms for Documentum is limited. (See “Supported
Platforms” on page 112.)
●
New applications or forms should not be developed on this architecture. It is recommended that you
only develop new applications and forms using LiveCycle ES Connector for EMC Documentum.
After you install and deploy LiveCycle ES Connector for EMC Documentum, you can create new forms and
applications, and migrate existing forms and applications by re-creating them with
LiveCycle Workbench ES. During the LiveCycle ES installation process, you can import samples that
provide examples of how to develop for LiveCycle ES Connector for EMC Documentum. This includes
examples of integrating with other solution components, such as LiveCycle Forms ES,
LiveCycle Reader Extensions ES, and LiveCycle Workspace ES.
For information about using existing form templates, and submitted data and forms with
LiveCycle ES Connector for EMC Documentum, see “Migrating LiveCycle 7.x Forms for Documentum
applications to LiveCycle ES” on page 112.
Running LiveCycle Forms 7.x for Documentum with
LiveCycle Forms ES
The LiveCycle Forms 7.x for Documentum included a WebTop customization, an integration servlet, and a
LiveCycle Forms 7.x license. LiveCycle ES Connector for EMC Documentum is based on
LiveCycle Foundation. However, the integration servlet in 7.x Forms connector can communicate with
Forms ES so that when you upgrade to Forms ES, you can continue to use WebTop.
111
Adobe LiveCycle ES
Migrating to LiveCycle ES Connector for EMC Documentum
Preparing to Upgrade to LiveCycle ES
Supported Platforms
112
Supported Platforms
Until you migrate existing applications to LiveCycle ES, your LiveCycle Forms for Documentum works with
Forms ES through the LiveCycle ES compatibility layer. The Documentum server and the LiveCycle ES
server must be running on the following platforms.
For information about the specific version of operating systems and application servers supported for the
LiveCycle ES Connector for EMC Documentum, see “Supported software” on page 35.
Documentum Content server
LiveCycle ES
(Running Forms ES and Reader Extensions ES)
Documentum application server
(Running WebTop and LiveCycle Forms 7.x for
Documentum)
WebLogic Server 9.2 on Solaris 9
WebLogic Server 8.1 on Solaris 9
WebLogic Server 9.2 on Windows
WebLogic Server 8.1 on Windows
WebSphere Application Server 6.1 on Windows
WebSphere Application Server 5.1.x on Windows
WebSphere Application Server 6.1 on Windows
WebSphere Application Server 6.0.x on Windows
Migrating LiveCycle 7.x Forms for Documentum applications to LiveCycle ES
This section provides an example of how you can migrate an application for LIveCycle Forms 7.x for
Documentum to LiveCycle ES.
The LiveCycle ES installation provides several process samples that can be used in those client samples
and the Documentum Web Development Kit (WDK). These process samples show how to use the
LiveCycle ES Connector for EMC Documentum with other LiveCycle ES solution components, including
Forms ES and Reader Extensions ES.
You can download a WDK sample client from the LiveCycle Developer Center at www.adobe.com. This
client demonstrates how to render forms, process form submission, and view form rendition from
Documentum WebTop.
LiveCycle Forms 7.x for Documentum used a virtual document to store a form template. These restrictions
have been removed in LiveCycle ES Connector for Documentum. To migrate your application, you need to
migrate both published forms and submitted forms. This example assumes the following details about the
application that will be migrated from LiveCycle Forms 7.x for Documentum to LiveCycle ES:
●
The published form is called LCFormXDP (type of adbe_published_from), located in the /System/Forms
directory.
●
The published form object contains three document objects: LCForm.xdp, LCForm.xsd, and LCForm.gif.
●
The submitted form object is type of adbe_submitted_form.
●
When you migrate your current application to LiveCycle ES, you want the form design to be located at
/System/ESForms.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for EMC Documentum
Migrating LiveCycle 7.x Forms for Documentum applications to LiveCycle ES
113
Migrating the published form
To migrate the published form, you must do the following tasks:
●
Find the version of the child documents that belong to the virtual document to which the Published
Form (Frozen Assembly of the Virtual Doc) is bound. AutoUpdate assets map to the head version of the
asset.
●
Correct the assets path in XDP to reflect the new location.
➤ To find the version of the child documents that belong to the virtual document:
1. In WebTop, go to /System/Forms and, in the navigation tree on the left, expand the submitted form.
The form is displayed in View mode.
2. Select the XDP and other image and schema assets and copy them to the /System/ESForms directory.
➤ To correct the assets path in XDP to match the location of the migrated form design:
1. Log in to Workbench ES and navigate to the /System/ESForms directory in the Resources view.
2. Open the LCForm.xdp file and modify the path for the LCForm.gif file to /System/ESForms/LCForm.gif.
3. Set the appropriate data connection to /System/ESForms/LCForm.xsd.
4. Save the XDP file.
Migrating the submitted form
The submitted form represents an instance of the published form that can be filled. It is a simple
document type of format xml.
The submitted form consists of an XML file and a relationship to the published form. You can reuse all the
existing submitted form objects with their rendition. To migrate the submitted form, you must update its
relationship to the published form.
The relationship to the published form is maintained by a relation object. You can reuse the existing
relation or create your own. The default relation in LiveCycle Forms 7.x for Documentum is
ADBE_PS_FORM. To reuse this relationship, you must update the parent_id from the old published form
to the new one you created in Migrating the published form.
For example, you can use the following Data Query Language (DQL) to complete the update:
update dm_relation object set parent_id='[r_object_id of new published form]'
where parent_id='[r_object_id of old published form]' and
relation_name='ADBE_PS_FORM'
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for EMC Documentum
Developing new applications using samples
114
Developing new applications using samples
After you finish the data migration, you can develop your new LiveCycle ES application by using
Connector for EMC Documentum. You can leverage the out-of-box samples for the connector. You can
install these samples by following instructions in the Installing and Deploying LiveCycle ES document for
you application server at http://www.adobe.com/go/learn_lc_documentation.
When you create a new application, you can set usage rights within the process or pass them into the
process. Your current value is in the ARES Rights property of your existing published form object. Your
current rendering preference is set to Display Format. You can also set the rendering format to Auto.
The following tasks describe how you can leverage the process samples included with LiveCycle ES and
develop processes to create a new application to render form designs with XML data and process
submission form data.
1. Design a form design using the LiveCycle Form Design perspective in Workbench ES. You can create or
edit an XDP form template and store it in the ECM repository.
2. To render the form design, you can leverage the RenderReaderEnabledFormsWithData-Documentum
sample. This process sample prepopulates the form with user-specific data and prepares a form that is
displayed to the end user as a rights-enabled document. The publish parameters set in the Publish
Form step in LiveCycle 7.x now can be set within this process. You can set form rendering and
Reader Extensions ES options in appropriate operations in this process.
3. To process form submission, you can leverage the ArchiveSubmittedData-Documentum sample. This
processes the submitted data and stores the submitted data in the Documentum repository.
This process sample creates the relationship between the submitted XML data and its form design. You
can set the form submission destination in appropriate operations within this process. You can also
extend this process to generate and store the rendition and fillable form, as well as create their
relationships.
4. Render the submitted form using the RenderFormsFromSubmittedData-Documentum sample. This
gets a submitted form from the Documentum repository and displays it to the end user.
5. For any custom code you have developed for the LiveCycle Forms 7.x for Documentum, you must
migrate the code into the LiveCycle ES process. The client samples provide examples of how to call
these processes from WebTop.
12
Migrating to LiveCycle ES
Connector for IBM FileNet
Automatic upgrades from LiveCycle Forms for FileNet to LiveCycle ES are not supported. The following
tasks are required to migrate from LiveCycle Forms for FileNet to LiveCycle ES Connector for IBM FileNet:
●
Install and deploy LiveCycle ES, including Connector for IBM FileNet (See Installing and Deploying
LiveCycle ES for your application server at http://www.adobe.com/go/learn_lc_documentation.)
LiveCycle applications and forms continue to work (with some restrictions).
●
Create new applications and forms using the samples and documentation.
●
Re-create LiveCycle 7.x applications and forms by leveraging the process samples included with the
LiveCycle ES and user interface samples from the LiveCycle Developer Center on www.adobe.com.
When you install and deploy LiveCycle ES, LiveCycle Forms 7.x for FileNet is compatible with
LiveCycle Forms ES, with some restrictions:
●
You must use LiveCycle Designer 7.x for FileNet to update existing form templates. Features introduced
in LiveCycle ES, such as fragments, are therefore not available for these forms.
●
The platforms supported for running LiveCycle Forms 7.x for FileNet is limited. (See “Supported
Platforms” on page 115.)
●
New applications or forms should not be developed on this architecture. It is recommended that you
develop only new applications and forms using LiveCycle ES Connector for IBM FileNet.
When you have installed and deployed Connector for IBM FileNet, you can create new forms and
applications, and migrate existing forms and applications by re-creating them with
LiveCycle Workbench ES. During the LiveCycle ES installation process, you can import
LiveCycle ES Samples that provide examples of how to develop for Connector for IBM FileNet. This
includes examples of integrating with other solution components such as LiveCycle Forms ES,
LiveCycle Reader Extensions ES, and LiveCycle Workspace ES.
For information about using existing form templates, and submitted data and forms with
Connector for IBM FileNet, see “Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES” on
page 116.
Running LiveCycle Forms 7.x Connector for FileNet with Forms ES
LiveCycle Forms for Filenet included FileNet P8 Workplace customization, an integration servlet, and a
LiveCycle Forms 7.x license. LiveCycle ES Connector for IBM FileNet is based on LiveCycle Foundation.
However, the integration servlet in LiveCycle Forms 7.x for FileNet can communicate with Forms ES so that
when you upgrade to Forms ES, you can continue to use your existing FileNet P8 Workplace application.
Supported Platforms
Until you migrate existing applications to LiveCycle ES, your LiveCycle Forms 7.x for FileNet works with
LiveCycle Forms ES through the LiveCycle ES compatibility layer. The IBM FileNet P8 Application Engine
and the LiveCycle ES server must be running on the following platforms.
For information about the specific version of operating system and application servers supported for the
LiveCycle ES Connector for IBM FileNet, see “Supported software” on page 35.
115
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for IBM FileNet
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES
116
IBM FileNet Content server
LiveCycle ES
(Running Forms ES and Reader Extensions ES)
FileNet Application Engine Server
(Running Workplace)
WebLogic Server 9.2 on Solaris 9
WebLogic Server 8.1 on Solaris 9
WebLogic Server 9.2 on Windows
WebLogic Server 8.1 on Windows
WebSphere Application Server 6.1 on AIX
WebSphere Application Server 5.1.x on IBM AIX
WebSphere Application Server 6.1 on Windows
WebSphere Application Server 5.1.x on Windows
WebSphere Application Server 6.1 on Windows
WebSphere Application Server 6.0.x on Windows
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES
This section provides an example of how to migrate an application for LiveCycle 7.x Forms for FileNet to
LiveCycle ES.
The LiveCycle ES installation provides several process samples that can be used in building your own Web
Development Kit (WDK) application. These process samples show how to use LiveCycle ES
Connector for IBM FileNet with other LiveCycle ES solution components including Forms ES and
Reader Extensions ES.
You can download a WDK sample client from the LiveCycle Developer Center at www.adobe.com. This
client administrates how to render forms, process form submission, and view form rendition from FileNet
Workplace. You can also download a sample that can be used to integrate LiveCycle ES with the IBM
FileNet P8 Process Engine.
LiveCycle Forms for FileNet used custom data types to store the form design, document policy or workflow
policy, and submitted document or submitted form. This restriction of LiveCycle-specific data types have
been removed in LiveCycle ES Connector for IBM FileNet. To migrate your application, you need to migrate
the published form design, data from the document policy or workflow policy, and submitted document
or submitted form.
This migration example assumes the following details about the application that will be migrated from
LiveCycle 7.x Forms for FileNet to LiveCycle ES:
Form design
●
Published form design is called LCForm (of type Adobe Form Designs), located in the
/System/Forms directory.
●
The published form contains two content elements: LCForm.xdp and publishFields. The published form
is linked to the assets LCForm.xsd and LCForm.gif.
●
When you migrate your current application to LiveCycle ES, the form design will be located at
/System/ESForms.
Document policy
●
The document policy is called LCDocumentPolicy (of type Adobe Document Policy), located in the
/System/Policy directory. The document policy contains one content element: _content.xml
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for IBM FileNet
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES
117
Submitted document
●
The submitted document is called LCSubmittedDocument (of type Adobe SubmittedDocuments),
located in the /System/Data directory.
●
The submitted document contains two content elements: LCFormData and LCFormData.pdf.
Migrating the form design
LiveCycle Forms for FileNet stored the form design in an object of class type Adobe Form Designs. The
form design object is a multi-content document that stores the XDP file and the published fields (only if
the form was published using the Publish Form Design Fields action) in the first and second content
elements respectively. The form design is linked to images and schema assets associated with the XDP by
using a link of class type XDPLinks.
To migrate the form design, do the following tasks:
●
Extract the XDP from the form design.
●
Find the version information of the assets associated with the XDP.
●
Copy the XDP and the assets to the /System/ESForms directory.
●
Correct the assets path in the XDP to reflect the new location of the migrated form design.
➤ To extract the XDP from the form design in Workplace 3.0.x:
1. In FileNet Enterprise Manager, navigate to LCForm, and open the Properties window associated with it.
2. Click the Content Elements tab, select LCForm.xdp, and download it to the local directory.
➤ To extract the XDP from the form design in Workplace 3.5.x:
1. In Workplace, go to the /System/Forms directory and select LCForm.
2. Click the information icon (i) next to the LCForm document, and then click Download.
3. Select LCForm.xdp and then save this file to a local directory.
➤ To find the version information of the assets associated with the XDP:
1. In Workplace, go to the /System/Forms directory and click the information icon (i) next to LCForm.
2. Click Links and, in the Link To: section, click XDPLinks to see all the assets linked to LCForm.
3. For each asset, click the information icon (i) and then click Show System Properties to display the
version information.
➤ To correct the assets path in XDP to match the location of the migrated form design:
1. Log in to Workbench ES and navigate to the /System/ESForms directory in the Resources view.
2. Open the LCForm.xdp file and modify the path for LCForm.gif to /System/ESForms/LCForm.gif.
3. Set the appropriate data connection to /System/ESForms/LCForm.xsd.
4. Save the XDP file.
Adobe LiveCycle ES
Migrating to LiveCycle ES Connector for IBM FileNet
Preparing to Upgrade to LiveCycle ES
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES
118
Migrating the document policy
LiveCycle Forms 7.x for FileNet stored the user preferences for rendering and processing form submissions,
and mapping of form design fields to document class properties in an object of class type Adobe
Document Policy. The preferences are stored in XML format in the first content element (called
_content.xml). The XML consists of the following information:
LiveCycle Reader Extensions rights preference: This preference is stored in the <ares> section as
boolean values. You should set these values in your Reader Extensions ES operations. In the
RenderReaderEnabledForms-FileNet sample, you must set these values in the “Ubiquitize rendered
PDF” step. The following XML code provides an example of the usage rights that are set for the
document policy:
<ares>
<basicformfillin>true</basicformfillin>
<formdataimportorexport>true</formdataimportorexport>
<digitalsignatures>true</digitalsignatures>
<comments>false</comments>
<attachments>true</attachments>
<formsubmitstandalone>false</formsubmitstandalone>
</ares>
Form rendering preference: This preference is stored in the <format> tag in the <renderformat>
section. A value of PDFForm or HTML should be mapped to the renderAsPDF or renderAsHTML
operation, respectively, in the LiveCycle ES process, as demonstrated in the
RenderReaderEnabledForms-FileNet sample in LiveCycle ES. The following example XML code shows
HTML as the rendering preference for the document policy:
<renderformat>
<format>HTML</format>
</renderformat>
Mapping form fields to class properties of submitted data object: This information is stored in the
<metadatamap> nodes in the <metadatamaps> section. For any <metadatamap> node that
contains both <field> and <property> nodes, you must set the mapping in the appropriate
operations in your new application. In the ArchiveSubmittedData-FileNet sample available with
LiveCycle ES, you can set these mappings in the Meta-Data section of “Store processed xml and set
attributes” step. The example XML code shows the mapping between the LastName field in the form
design and the Document Title property in the submitted form:
<metadatamaps>
<metadatamap>
<field>
<name>~|~form1~|~LastName</name>
…
</field>
<property>
<name>Document Title</name>
…
</property>
</metadatamap>
<metadatamap>
<field>
<name>~|~form1~|~ZipCode</name>
…
</field>
</metadatamap>
…
</metadatamaps>
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for IBM FileNet
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES
119
Any <metadatamap> node that does not include a <property> node does not have a mapping
value in the existing document policy. Therefore, users do not need to record this values and set it in
the new application.
Save static PDF: This preference indicates whether you want to store a static PDF in addition to the
XML data. This preference is stored in the <savestaticpdf> tag. If the value of this option is true,
you can modify the ArchiveSubmittedData-FileNet operation to additionally store a PDF rendition. The
example XML code shows the preference set to false (a static PDF will not be stored):
<savestatidpdf>false</savestaticpdf>
To migrate the document policy, you must perform the following tasks:
●
Extract the preferences from the LCDocumentPolicy object.
●
Specify the appropriate settings in the LiveCycle ES application as described in the example above.
➤ To extract the preferences from the LCDocumentPolicy object in Workplace 3.0.x:
1. In FileNet Enterprise Manager, navigate to LCDocumentPolicy and open the Properties window
associated with it.
2. Click the Content Elements tab.
3. Select the _content.xml file and download it to the local directory.
➤ To extract the preferences from the LCDocumentPolicy object in Workplace 3.5.x:
1. In Workplace, go to the /System/Policy directory and select LCDocumentPolicy.
2. Click the information icon (i) next to LCDocumentPolicy and then click Download.
3. Select the _content.xml file and download it to a local directory.
Migrating the Submitted Document
LiveCycle 7.x Connector for FileNet stored the Submitted Document data in an object of class type Adobe
Submitted Documents. The submitted document stores the submitted XML data and the PDF
rendition (if Save Static PDF option was chosen at the time of creation of the document policy) in content
elements one and two, respectively.
To migrate the Submitted Document, you must do the following:
●
Create a relationship between the form design and the submitted document.
●
Extract static PDF and create relationship to the submitted document.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for IBM FileNet
Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES
120
➤ To create a relationship between form design and the submitted document:
1. In Workplace, go to the /System/ESForms directory and click the information icon (i) next to the
LCForm.xdp file.
2. Click Create Link, choose a relationship (for example Related Items) and locate and select the
LCForm.xml to create the relationship between the form design and the submitted document.
Note: If you use a relationship other than Related Items, you must make the corresponding change in
the samples that are included with LiveCycle ES. In the ArchiveSubmittedData-FileNet sample,
you must change the relationship type parameter in the “Create Relationship” step. In
RenderFormsFromSubmittedData-FileNet sample, you must change the relationship type in the
“Get related XDP” step.
➤ To extract the static PDF form from the submitted document in Workplace 3.0.x:
1. In FileNet Enterprise Manager, navigate to LCSubmittedDocument and open the Properties window
associated with it.
2. Click the Content Elements tab.
3. Select the LCForm.pdf file, download it to the local directory, and save it in an appropriate FileNet
folder.
4. Create a relationship between the newly saved LCForm.pdf document object and its related submitted
document object.
➤ To extract the static PDF form from the submitted document in Workplace 3.5.x:
1. In Workplace, navigate to the /System/Data directory and select LCSubmittedDocument.
2. Click the information icon (i) next to the document and then click Download.
3. Select the LCForm.pdf file, download it to the local directory, and save it in an appropriate FileNet
folder.
4. Create a relationship between the newly saved LCForm.pdf document object and its related submitted
document object.
Migrating the workflow policy
LiveCycle Forms 7.x for FileNet stored the user preferences for rendering and processing form submissions,
mappings of form design fields to workflow step parameters and, optionally, mapping of form design
fields to document class properties in an object of class type Adobe Form Policy.
Like the document policy, these preferences are stored in XML format. See the sample on the LiveCycle
Developer Center for details on migration steps.
Adobe LiveCycle ES
Preparing to Upgrade to LiveCycle ES
Migrating to LiveCycle ES Connector for IBM FileNet
Developing new applications using samples
121
Migrating the Submitted Form
LiveCycle Forms 7.x for FileNet stored the Submitted Form data in an object of class type
Adobe Submitted Forms. The submitted form stores the submitted XML data for each workflow step
as a content element.
The migration steps are the same as that for “Migrating the Submitted Document” on page 119.
Developing new applications using samples
After you finish the data migration, you can develop your new LiveCycle ES application using
Connector for IBM FileNet. You can leverage the out-of-box samples for the connector. You can install
these samples by following instructions in the LiveCycle ES Installing and Deploying document for your
application server at http://www.adobe.com/go/learn_lc_documentation.
The following tasks describe how you can leverage the process samples included with LiveCycle ES and
develop orchestrated processes to create a new application to render form designs with XML data and
process submission form data.
1. Design a form template using the LiveCycle Form Design perspective in Workbench ES. You can create
or edit an XDP form template and store it in the FileNet repository.
2. Publish a form template using the RenderReaderEnabledFormsWithData-FileNet sample. This
prepopulates the form with user specific data and prepares a form that is displayed to the end user.
3. Submit the form using the ArchiveSubmittedData-FileNet sample. This stores the submitted data in the
FileNet repository.
4. Render the submitted form using the RenderFormsFromSubmittedData-FileNet sample. This gets a
submitted form from the FileNet repository and displays it to the end user.
If you use FileNet Workflow, you must replace the Adobe launch processor and step processor included in
LiveCycle Forms 7.x for FileNet with new processors that call the LiveCycle ES processes (as described in
step 1 to 4 above). You can download examples of such processors from the LiveCycle Developer Center at
www.adobe.com as part of the FileNet Process Engine integration sample.
Index
A
C
admin look-up, enabling anonymous for WebLogic 90
Administration Server, WebLogic, configuring 88
Administrative Console, WebSphere, accessing 81
administrative users 22
Adobe Acrobat licensing restriction 41
Adobe LiveCycle 7.x database, backing up 48
Adobe LiveCycle 7.x products
changes in LiveCycle ES 15
upgrading 22
Adobe LiveCycle Assembler, upgrading 27
Adobe LiveCycle Barcoded Forms, upgrading 25
Adobe LiveCycle Business Activity Monitor, upgrading 24
Adobe LiveCycle Business Activity Monitoring ES 40
Adobe LiveCycle Configuration Manager 28, 29
Adobe LiveCycle Document Security, upgrading 26
Adobe LiveCycle ES database
connectivity, configuring for JBoss 57
connectivity, configuring for WebLogic 94
connectivity, configuring for WebSphere 83
DB2, creating 104
MySQL, creating 96, 102
Oracle, creating 104
SQL Server, creating 106
Adobe LiveCycle ES, documentation resources 10
Adobe LiveCycle Form Manager, upgrading 24
Adobe LiveCycle Forms, upgrading 25
Adobe LiveCycle Output 25
Adobe LiveCycle PDF Generator ES, requirements for 39
Adobe LiveCycle PDF Generator, upgrading 26
Adobe LiveCycle Policy Server, upgrading 26
Adobe LiveCycle Print, upgrading 25
Adobe LiveCycle Reader Extensions, upgrading 25
Adobe LiveCycle Workflow, upgrading 23
Adobe Reader compatibility 15, 19
anonymous admin look-up for WebLogic 90
API compatibility 16, 20
application servers
instance on WebSphere, creating 82
supported 21, 35
updating client applications on 29
applications
updating 29
upgrading using APIs 13
archive files, exporting 45
certificate, LiveCycle Reader Extensions 25
client applications, updating 29
compatibility
Adobe Reader 15, 19
API 20
data 19
data and API 16
forms 15, 19
layer 29
configuration files, JBoss 53
configuring
database connectivity for JBoss 57
database connectivity for WebLogic Server 94
database connectivity for WebSphere 83
LDAP 41
WebLogic Administration Server 88
WebLogic Server 90
content management systems supported 37
conventions, file path 9
creating
application server instance on WebSphere 82
DB2 database 104
WebLogic Managed Server 89
WebLogic Server domain 87
credential
LiveCycle Document Security 26
LiveCycle Reader Extensions 42
B
backing up
files and directories 47
LiveCycle 7.x database 48
bc tool 38
D
data compatibility 16
Data Manager Module 45
data services supported 36
databases
backing up 48
combinations with platforms 31
connectivity, configuring for WebLogic Server 94
connectivity, configuring for WebSphere 83
DB2, creating 104
drivers supported 36
MySQL, creating 96, 102
Oracle, creating 104
schemas 19
SQL server, creating 106
supported 36
supported for upgrading 21
DB2 database
configuring for Adobe preconfigured JBoss 72
configuring for manually configured JBoss 74
creating 104
DDX files 27
deployment considerations 41
122
Adobe LiveCycle ES
Index
Preparing to Upgrade to LiveCycle ES
directories
backing up 47
location of 43
documentation
additional resources 10
for upgrade assistance 11
E
EAR files, exporting 45
EJB 20
email servers supported 36
environment variables
setting for JBoss 50
setting for PDF Generator ES 39
setting for WebSphere 79
exporting archive files 45
F
file formats, software support for 39
files, backing up 47
FIPS mode, enabling 20
Fix Pack, installing for WebSphere 6.1 79
Font Manager Module 45
forms compatibility 19
G
GNU bctool 38
H
hardware requirements 34
host name, transferring 31
HSM 26
HTML source 19
I
infrastructure, upgrading 21
installation considerations 41
installing
JBoss 51
native file conversion software 39
WebSphere Application Server 79
IP address, transferring 31
J
J2SE SDK, installing for JBoss 50
JAR files, updating 29
Java Virtual Machine (JVM) 21
JBoss Application Server
configuring DB2 72, 74
configuring MySQL 58, 60
configuring Oracle database 62, 65
configuring SQL Server 68
installing 51
123
JBoss Application Server (Continued)
installing the J2SE SDK 50
modifying configuration files 53
starting and stopping 52
turnkey upgrade 13
updating stand-alone client applications 30
JDK support 36
JMS, configuring for SQL Server for JBoss 70
JNDI port, determining 42
L
LDAP
configuring 41
server support 36
LiveCycle. See Adobe LiveCycle
M
Managed Server, creating for WebLogic 89
manually installing JBoss 52
MySQL
configuring database server 97
configuring for Adobe preconfigured JBoss 58
configuring for manually installed JBoss 60
database, creating 96, 102
migrating data 98
recommended server configuration 103
upgrading 96
user account 97, 103
N
Node Manager, starting 89
O
operating systems
additional requirements 38
combinations with databases 31
supported 35
supported for upgrading 21
Oracle database
configuring for Adobe preconfigured JBoss 62
configuring for manually installed JBoss 65
creating 104
P
passwords required 42
PDF clients supported 37
Persistent Object Framework (POF) 19
platforms, combinations with databases 31
preconfigured JBoss, installing 51
Process Upgrade Tool 23
Q
QPACs, updating 31
Adobe LiveCycle ES
Index
Preparing to Upgrade to LiveCycle ES
R
registry tables 19
REST 20
Rights credential 42
S
SDK
installing J2SE for JBoss 50
server names 43
Service Control Manager tool 40
Service Provider Interface (SPI) 26
SIB database tables 48
SOAP 20
SOAP-with-Attachments 22
software support 35
SQL Server
configuring data source for JBoss 68
configuring for JBoss 68
configuring JMS for JBoss 70
database, creating 106
upgrading 99
SSL over IIOP 22
starting
JBoss 52
Node Manager 89
WebLogic 93
stopping
JBoss 52
WebLogic 93
system requirements 33
T
topology considerations 41
Trust Manager Module 45
Trust Store 26
turnkey upgrade 13
U
upgrading
Adobe Reader 19
applications using APIs 13
changes in LiveCycle ES 15
documentation for 11
for JBoss using turnkey 13
information required to upgrade 42
124
upgrading (Continued)
infrastructure 21
LiveCycle products 22
MySQL 96
overview of process 28
preparing for LiveCycle ES 11
SQL Server 99
summary of tasks 13
usage rights 25
user account, MySQL 97
user accounts
MySQL 103
PDF Generator ES 39
user accounts, MySQL 97
user interfaces, supported web browsers for 37
User Management, upgrading 22
users, adding to DB2 database 104
W
Watched Folder
LiveCycle Assembler 27
LiveCycle PDF Generator 26
watched folder locations, finding 44
web browsers supported 37
Web Services, configuring WebLogic Server for 91
WebLogic Administration Server, configuring 88
WebLogic Managed Server, creating 89
WebLogic Server
configuring 90
configuring database connectivity for 94
domain, creating 87
exporting EAR files from 45
stopping and starting 93
updating LiveCycle Assembler client applications 31
WebSphere Application Server
Administrative Console, accessing 81
configuring database connectivity for 83
dropping SIB database tables 48
exporting EAR files from 45
installing 79
updating client applications 30
X
xappstore 19
XCI files 25
XDC files 25
Was this manual useful for you? yes no
Thank you for your participation!

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

Download PDF

advertisement