bbc Preparing to Upgrade to LiveCycle ES from LiveCycle 7.x Adobe LiveCycle ES September 2007 Version 8.0

Transcription

1 bbc Preparing to Upgrade to LiveCycle ES from LiveCycle 7.x Adobe LiveCycle ES September 2007 Version 8.0

2 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 ( This product includes code licensed from RSA Data Security. This product includes software developed by the JDOM Project ( Macromedia Flash 8 video is powered by On2 TrueMotion video technology On2 Technologies, Inc. All Rights Reserved. This product includes software developed by the OpenSymphony Group ( Portions of this code are licensed from Nellymoser( MPEG Layer-3 audio compression technology licensed by Fraunhofer IIS and THOMSON Multimedia ( This product includes software developed by 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 ( 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.

3 Notice to U.S. Government End Users. The Software and Documentation are Commercial Items, as that term is defined at 48 C.F.R , consisting of Commercial Computer Software and Commercial Computer Software Documentation, as such terms are used in 48 C.F.R or 48 C.F.R , as applicable. Consistent with 48 C.F.R or 48 C.F.R through , 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 , 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, , and The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.

4 Contents About This Document... 8 Who should read this document?... 9 Conventions used in this document... 9 Additional information Introduction to Upgrading LiveCycle 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 Understanding the Changes in LiveCycle ES 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

5 Contents Preparing to Upgrade to LiveCycle ES 5 3 Planning for the Upgrade Process 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 Exporting the LiveCycle 7.x EAR files Next steps Backing Up the LiveCycle 7.x Environment 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

6 Contents Preparing to Upgrade to LiveCycle ES 6 6 Configuring JBoss Application Server 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 Configuring WebSphere Application Server Installing WebSphere Application Server...79 Installing a Fix Pack to WebSphere 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 Configuring WebLogic Server 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

7 Contents Preparing to Upgrade to LiveCycle ES 7 8 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 Upgrading the Database Server 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 Migrating LiveCycle data stored in a 4k pagesize tablespace on DB Next steps Creating the LiveCycle ES database Creating a MySQL database Creating an Oracle database Creating a DB2 database Creating a SQL Server database Install the SQL Server database driver: Setting up SQL Server for LiveCycle ES Increasing memory Setting processor priority Increasing the recovery interval Integrated Security Sizing your SQL Server database Creating the LiveCycle ES database Creating the LiveCycle ES user in SQL Server Associating the LiveCycle ES user with the database Setting the isolation level for the LiveCycle ES database Next steps Migrating to LiveCycle ES Connector for EMC Documentum Running LiveCycle Forms 7.x for Documentum with LiveCycle Forms ES Supported Platforms Migrating LiveCycle 7.x Forms for Documentum applications to LiveCycle ES Developing new applications using samples Migrating to LiveCycle ES Connector for IBM FileNet Running LiveCycle Forms 7.x Connector for FileNet with Forms ES Supported Platforms Migrating LiveCycle 7.x Forms for FileNet applications to LiveCycle ES Developing new applications using samples Index...122

8 About This Document This document provides the information required to prepare your server environment for upgrading Adobe LiveCycle 7.x products to (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 /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

9 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] [LiveCycle7 root] [appserver root] Windows: C:\Adobe\LiveCycle8\ Linux: /opt/adobe/livecycle8/ Windows: C:\Adobe\LiveCycle\ Linux: /opt/adobe/livecycle/ The home directory of the application server that runs the LiveCycle ES services. 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. 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

10 About This Document Preparing to Upgrade to LiveCycle ES Additional information 10 Name Default value Description BEA_HOME [appserverdomain] [dbserver root] The install directory for WebLogic as specified for the BEA_HOME environment variable. The domain that you configured on WebLogic. The location where the LiveCycle ES database server is installed. WebLogic on Windows C:\bea WebLogic on Linux and UNIX: /opt/bea WebLogic on Windows: C:\bea\user_projects\domains\base_domain WebLogic on Linux and UNIX: /opt/bea/user_projects/domains/base_domain 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 Performing the upgrade from LiveCycle 7.x to LiveCycle ES Performing the upgrade from LiveCycle 7.x to LiveCycle ES using the turnkey method Upgrading custom applications to LiveCycle ES Performing administrative tasks for LiveCycle ES Installing Adobe LiveCycle Workbench ES Other services and products that integrate with LiveCycle ES Patch updates, technical notes, and additional information on this product version See Upgrading to LiveCycle ES for JBoss at Upgrading to LiveCycle ES for WebSphere at Upgrading to LiveCycle ES for WebLogic at Upgrading to LiveCycle ES for JBoss Using Turnkey at /go/learn_lc_upgradeturnkey Upgrading Applications to LiveCycle ES Using APIs at Administering LiveCycle ES at Installing Your Development Environment at

11 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

12 Introduction to Upgrading LiveCycle Preparing to Upgrade to LiveCycle ES 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 Upgrading to LiveCycle ES for WebSphere at and Upgrading to LiveCycle ES for WebLogic at 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.

13 Introduction to Upgrading LiveCycle Preparing to Upgrade to LiveCycle ES 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 /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 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.

14 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 Understand upgrade process (high-level section). Understand the upgrade process and implications for LiveCycle 7.x QPACs. Understand the upgrade implications of custom applications and related APIs. See Understanding the Changes in LiveCycle ES on page 15 Data and process compatibility on page 19 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. Back up all LiveCycle 7.x data, resources, directories. Upgrade MySQL or SQL Server database server (if LiveCycle 7.x product used User Management). Create database (if LiveCycle 7.x product did not use a database). Install LiveCycle ES. Run LiveCycle Configuration Manager to configure LiveCycle ES and begin upgrading from LiveCycle 7.x. Stop LiveCycle 7.x and configure new application servers when instructed by the documentation. Do this task now only if LiveCycle 7.x server and target LiveCycle ES server are on the same computer. 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. Configuring JBoss Application Server on page 50 or Configuring WebSphere Application Server on page 79 or Configuring WebLogic Server on page 84 Backing Up the LiveCycle 7.x Environment on page 47 Upgrading the Database Server on page 95 Creating the LiveCycle ES database on page 102 Upgrading to LiveCycle ES for your application server Upgrading to LiveCycle ES for your application server, and LiveCycle Configuration Manager Help The Upgrading to LiveCycle ES document for your application server tells you when to do this step. The instructions in this guide describe the configuration steps required. 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.

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 LiveCycleES. AdobeReader 7.x and AdobeReader 8.x are compatible with both LiveCycle 7 and LiveCycle ES. 15

16 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.

17 Understanding the Changes in LiveCycle ES Preparing to Upgrade to LiveCycle ES Mapping LiveCycle 7.x products to LiveCycle ES solution components 17 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) LiveCycle Assembler 7.x LiveCycle Barcoded Forms 7.x LiveCycle Barcoded Forms 7.x ST LiveCycle Reader Extensions 7.x Flex Data Services 2 Departmental Flex Data Services 2 Enterprise LiveCycle Policy Server 7.x LiveCycle Document Security 7.x Adobe LiveCycle PDF Generator ES Adobe LiveCycle PDF Generator ES Adobe LiveCycle Barcoded Forms ES Adobe LiveCycle Barcoded Forms 7.5 ST and LiveCycle Reader Extensions Adobe LiveCycle Reader Extensions ES Adobe LiveCycle Data Services ES Departmental Adobe LiveCycle Data Services ES Enterprise Adobe LiveCycle Rights Management ES Adobe LiveCycle Digital Signatures ES N/A PDF Generator ES is the standard upgrade target for LiveCycle Assembler, which is included. Forms ES or Output ES are optional upgrade targets. N/A N/A N/A Not covered in this document. Not covered in this document. N/A N/A

18 Understanding the Changes in LiveCycle ES Preparing to Upgrade to LiveCycle ES Compatibility between LiveCycle 7.x and LiveCycle ES 18 Previous generation products LiveCycle ES upgrade path Additional information LiveCycle Workflow 7.x LiveCycle Form Manager 7.x Adobe LiveCycle Process Management ES 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 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 Forms for FileNet LiveCycle Connector for EMC Documentum LiveCycle Connector for FileNet 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. 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.

19 Understanding the Changes in LiveCycle ES Preparing to Upgrade to 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 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.

20 Understanding the Changes in LiveCycle ES Preparing to Upgrade to 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 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) 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 /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 /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).

21 Understanding the Changes in LiveCycle ES Preparing to Upgrade to 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 SP1 WebLogic Server 9.2 (Advantage and Premium editions) WebSphere Application Server (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 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

22 Understanding the Changes in LiveCycle ES Preparing to Upgrade to 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 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.