bb c Upgrading to LiveCycle ES2 from 8.x
bc
Upgrading to LiveCycle® ES2 from 8.x
(for JBoss® Turnkey)
Adobe® LiveCycle® ES2
November 30, 2011
Version 9
© 2011 Adobe Systems Incorporated and its licensors. All rights reserved.
Upgrading to Adobe® LiveCycle® ES2 from 8.x (for JBoss Turnkey)
November 30, 2011
This guide is licensed for use under the terms of the Creative Commons Attribution Non-Commercial 3.0 License. This License allows users to
copy, distribute, and transmit the guide for noncommercial purposes only so long as (1) proper attribution to Adobe is given as the owner of
the guide; and (2) any reuse or distribution of the guide contains a notice that use of the guide is governed by these terms. The best way to
provide notice is to include the following link. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/.
Adobe, the Adobe logo, Acrobat, Flash, FrameMaker, LiveCycle, PageMaker, and Photoshop are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and/or other countries. IBM is a trademark of International Business Machines Corporation
in the United States, other countries, or both. Intel and Pentium are trademarks or registered trademark of Intel Corporation or its subsidiaries
in the U.S. and other countries. Oracle, Java, Solaris, and Sun are trademarks or registered trademarks of Oracle and/or its affiliates. Red Hat is
a registered trademarks of Red Hat, Inc. in the United States and other countries. Linux is the registered trademark of Linus Torsvalds in the
U.S. and other countries. Microsoft, SharePoint, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Contents
About This Document.................................................................................................................. 5
Who should read this document? ............................................................................................................................................ 5
Conventions used in this document ....................................................................................................................................... 5
Additional information................................................................................................................................................................. 6
1
Upgrading to LiveCycle ES2 (Turnkey) ...................................................................................... 7
Turnkey installation overview.................................................................................................................................................... 7
In-place or out-of-place upgrade ....................................................................................................................................... 7
Turnkey installation architecture.............................................................................................................................................. 8
Optional Business Activity Monitoring ES2 deployment........................................................................................... 8
How the LiveCycle ES2 upgrade works .................................................................................................................................. 9
Task checklist .................................................................................................................................................................................11
2
System prerequisites................................................................................................................. 12
Development versus production environments ..............................................................................................................12
Additional prerequisites ............................................................................................................................................................12
Hardware...................................................................................................................................................................................12
Operating system...................................................................................................................................................................13
Web browser support...........................................................................................................................................................13
Application server..................................................................................................................................................................16
Backing up the LiveCycle ES (8.x) data files ........................................................................................................................16
Before you upgrade.....................................................................................................................................................................16
Configuration for 64-bit Windows Server 2008, Windows 7 or Vista installations.........................................17
Preconfiguration for PDF Generator ES2 and PDF Generator 3D ES2.................................................................18
3
Upgrading to LiveCycle ES2 (JBoss Turnkey) .......................................................................... 20
Checking the installer .................................................................................................................................................................20
Upgrading exceptions................................................................................................................................................................20
Installing LiveCycle ES2..............................................................................................................................................................21
Install service packs .....................................................................................................................................................................23
Preparing the Connectors for ECM for upgrade ...............................................................................................................23
Upgrading LiveCycle ES (8.x) to LiveCycle ES2 ..................................................................................................................24
Upgrade and deploy Business Activity Monitoring ES2.................................................................................................31
Next steps........................................................................................................................................................................................32
4
Post-Deployment Activities ...................................................................................................... 33
Removing JMS from the JBoss server ...................................................................................................................................33
Restarting the JBoss services....................................................................................................................................................34
Disabling status pages for JBoss.............................................................................................................................................34
Setting the correct date, time, and time zone ...................................................................................................................34
Manually enabling SSL for JBoss.............................................................................................................................................34
Enabling SSL for JBoss..........................................................................................................................................................35
Installing LiveCycle ES2.5 Solution Accelerators...............................................................................................................37
Upgrading to Workbench ES2 .................................................................................................................................................37
Accessing LiveCycle Administration Console ....................................................................................................................37
Change default password ...................................................................................................................................................38
Accessing module web applications.....................................................................................................................................38
3
Adobe LiveCycle ES2
Contents
4
Accessing Reader Extensions ES2 ....................................................................................................................................38
Accessing Workspace ES2...................................................................................................................................................38
Accessing Rights Management ES2 ................................................................................................................................39
Accessing Business Activity Monitoring ES2................................................................................................................39
Accessing Content Services ES2 .......................................................................................................................................40
Accessing User Management ..................................................................................................................................................40
Encrypting the plaintext password........................................................................................................................................41
Managing the MySQL database..............................................................................................................................................41
Resetting the Forms ES2 cache ...............................................................................................................................................41
Configuring LiveCycle ES2 to access LDAP .........................................................................................................................41
Considerations when upgrading from LiveCycle 7.x ......................................................................................................42
Configuring HTML digital signature ......................................................................................................................................43
Configuring PDF Generator ES2 or PDF Generator 3D ES2...........................................................................................43
Setting environment variables..........................................................................................................................................43
Configuring the application server to use HTTP proxy server...............................................................................44
Setting the Adobe PDF Printer as the default printer...............................................................................................45
Configuring Acrobat Professional....................................................................................................................................45
Installing East Asian characters in Windows Server 2003 .......................................................................................46
Setting PDF Generator ES2 or PDF Generator 3D ES2 watched folder performance parameters............46
Configuring user accounts for multi-threaded file conversions...........................................................................46
Adding fonts to PDF Generator ES2 or PDF Generator 3D ES2 .............................................................................47
Configuring HTML to PDF conversions..........................................................................................................................48
Modifying Microsoft Visio 2007 default macro settings ..........................................................................................49
Installing the PDF Generator ES2 Network Printer client ........................................................................................50
Configuring LiveCycle ES2 Connectors for ECM ...............................................................................................................51
Configuring SharePoint client access ...................................................................................................................................56
Obtain and edit the share.war file....................................................................................................................................56
Deploy the share.war file.....................................................................................................................................................56
Enabling CIFS in IPv6 mode......................................................................................................................................................57
Edit the contentservices.war file.......................................................................................................................................57
Uninstalling LiveCycle ES post-upgrade ..............................................................................................................................58
Deleting working files after upgrade ....................................................................................................................................58
Performing a system image backup......................................................................................................................................58
Uninstalling LiveCycle ES2 .......................................................................................................................................................59
5
Advanced Configuration Activities .......................................................................................... 60
Enabling Federal Information Processing Standard (FIPS)............................................................................................60
Enabling AES-256 encryption ..................................................................................................................................................60
About This Document
This document explains how to upgrade to Adobe® LiveCycle® ES2 (Enterprise Suite) for Red Hat®JBoss®
and MySQL from LiveCycle ES (8.x) for Red Hat® JBoss®and MySQL by using the turnkey method. The
turnkey method automatically installs, configures and upgrades the product and is the recommended
installation option for rapid evaluation, development, and small production deployments.
Perform this type of upgrade to get a LiveCycle ES2 system up and running rapidly for a 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 ES2
environment.
Ensure that you read Preparing for Upgrading to LiveCycle ES2 before you perform the tasks described in
this document. Although all the steps that are required to upgrade by using turnkey are included in this
document, Preparing for Upgrading to LiveCycle ES2 contains important information that will help you plan
your upgrade.
Note: If you are upgrading from LiveCycle 7.x, you must first upgrade to LiveCycle ES Update 1 (8.2) before
upgrading to LiveCycle ES2. (Upgrading to version 8.0.x is possible but not recommended.) See the
Upgrading from LiveCycle 7.x to LiveCycle ES2 document for details.
Who should read this document?
This document is intended for users who are upgrading from a LiveCycle ES (8.x) turnkey deployment.
These users include evaluators, administrators, or developers who are responsible for installing,
configuring, administering, or deploying LiveCycle ES2. The information provided is based on the
assumption that anyone reading this document is familiar with the Microsoft® Windows® operating
systems and web environments.
Conventions used in this document
This document uses the following naming conventions for common file paths.
Name
Default value
Description
[LiveCycleES2 root]
C:\Adobe\Adobe LiveCycle ES2\
The installation directory that is used for
all LiveCycle ES2 modules. This directory
contains subdirectories for LiveCycle
Configuration Manager, the
LiveCycle ES2 SDK, and each LiveCycle ES2
solution component installed.
[JBossES2 root]
C:\Adobe\Adobe LiveCycle ES2\jboss The home directory of the application
server that runs LiveCycle ES2.
[Adobe_JAVA_HOME] C:\Adobe\Adobe LiveCycle ES2\Java
The home directory of the Java JDK
installed by the LiveCycle ES2 turnkey.
5
Adobe LiveCycle ES2
About This Document
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
6
Additional information
The resources in this table can help you learn about LiveCycle ES2.
For information about
See
Upgrading to LiveCycle ES2 using the
non-turnkey method
Upgrading to LiveCycle ES2 for JBoss
Upgrading to LiveCycle ES2 for WebSphere
Upgrading to LiveCycle ES2 for WebLogic
General information about LiveCycle ES2 and
the modules
LiveCycle ES2 Overview
What’s new in this LiveCycle ES2 release
What’s New for LiveCycle ES2
LiveCycle ES2 release information and
LiveCycle ES2 Release Notes
last-minute changes that occur to the product
LiveCycle ES2 terminology
LiveCycle ES2 Glossary
Fresh turnkey install
Installing and Deploying LiveCycle ES2 Using Turnkey
Other services and products that integrate
with LiveCycle ES2
Adobe Development Center
LiveCycle ES2 modules
Adobe LiveCycle ES2 (Enterprise Suite)
All documentation available for LiveCycle ES2
Adobe LiveCycle ES2 documentation
Patch updates, technical notes, and additional LiveCycle Technical Support
information about this product version
1
Upgrading to LiveCycle ES2 (Turnkey)
This chapter describes how to upgrade from LiveCycle ES (8.x) turnkey to LiveCycle ES2 by using the
turnkey method. The turnkey installation option is most appropriate for rapid installations of evaluation,
developer, and small production environments. If you installed LiveCycle ES (8.x) using a non-turnkey
method (manual configuration and deployment to JBoss or deployment to WebSphere or WebLogic), see
the Upgrading to LiveCycle ES2 document for your application server.
Note: You can upgrade using the turnkey method only if you installed LiveCycle ES (8.x) using turnkey and
the LiveCycle ES (8.x) solution components are deployed to the JBoss instance that was included as
part of the turnkey installation.
The following information is included in this document:
●
A description of the system requirements for upgrading to the LiveCycle ES2 turnkey.
●
Backing up the LiveCycle ES (8.x) data.
●
All the steps required to initiate and complete the upgrade. (When you complete these steps,
LiveCycle ES2 is running on JBoss and ready to accept requests.)
●
Details about what you can do next, including accessing LiveCycle Administration Console and
User Management, and accessing some of the web applications that may be available (depending on
the LiveCycle ES2 modules you have licensed).
Note: LiveCycle ES2 turnkey installer disables JBoss JMS services, therefore, the JMS service of LiveCycle
Foundation is unavailable. The sample for LiveCycle Foundation JMS service will not work. To
enable LiveCycle Foundation JMS service and the samples, revert the steps described in the section
“Remove JMS and clustering configuration files” in the Preparing to Install guide.
Turnkey installation overview
LiveCycle Configuration Manager automatically performs most of the tasks required to upgrade a
LiveCycle ES (8.x) turnkey deployment to LiveCycle ES2 on a JBoss Application Server and MySQL database
running on Windows only.
In-place or out-of-place upgrade
When upgrading from LiveCycle ES (8.x), two scenarios will influence how LiveCycle Configuration
Manager configures your LiveCycle ES2 environment.
Note: You cannot perform an upgrade if you are changing your application server type, your operating
system type or your database type; this is considered a new installation. For example, if you are
changing your application server from WebLogic to JBoss, you must perform a new installation.
In-place upgrade: If you are upgrading to LiveCycle ES2 using your existing LiveCycle ES (8.x) application
server instance, this upgrade is considered in-place.
Caution: In-place upgrade is not possible with a JBoss turnkey upgrade because LiveCycle ES2 does not
support JBoss 4.0.x. The LiveCycle ES2 turnkey upgrade installs a fresh instance of JBoss 4.2.1.
7
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
8
Out-of-place upgrade: If you are upgrading to LiveCycle ES2 and are changing computers or updating
your application server version (major revision), this upgrade is considered out-of-place. Therefore, a
turnkey upgrade is out-of-place because of the new JBoss version.
If you are moving from a 32-bit version of your application server to a 64-bit version, this is also considered
out-of-place. This method can be used when installing LiveCycle ES2 either locally or on a remote server.
Prepare your new operating system, application server, or database according to the instructions in
Preparing to Install LiveCycle ES2 (single server).
Turnkey installation architecture
The following diagram illustrates a LiveCycle ES2 Turnkey installation.
Some of the components are optional as part of the turnkey installation. For example:
●
LDAP Directory Server - you do not need to authenticate with LDAP to set up LiveCycle users. For lab
trials and testing purposes, you can use LiveCycle ES2 User Management (available from LiveCycle
Administration Console) to create new user accounts.
●
Partial Turnkey - External database server - the typical turnkey installation includes a preconfigured
MySQL database.
●
Connectors - LiveCycle ES2 can connect to your ECM vendor’s datasource (if applicable)
Note: The above illustration shows LiveCycle Workbench ES2 required for creating and deploying
processes to the LiveCycle ES2 server. To install LiveCycle Workbench ES2, refer to Installing Your
Development Environment.
Optional Business Activity Monitoring ES2 deployment
With the LiveCycle ES2 turnkey installation, you can install and configure LiveCycle
Business Activity Monitoring ES2 as a standalone application. Performance increases when BAM is
installed on a standalone server independent of LiveCycle ES2 server.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
9
Note: LiveCycle Business Activity Monitoring ES2 is only supported on 64-bit operating systems. If you
install BAM using the turnkey option it will install a standalone version of JBoss on your server.
Therefore, if you are installing BAM along with other LiveCycle ES2 components your server will
have two instances of JBoss installed.
The following diagram illustrates a LiveCycle ES2 turnkey deployment and a standalone BAM installation.
How the LiveCycle ES2 upgrade works
Upgrading to LiveCycle ES2 from LiveCycle ES (8.x) involves the following major tasks, many of which are
automated when you use the turnkey method of installation and deployment:
1. Manually backing up the LiveCycle ES (8.x) data.
2. Installing LiveCycle ES2 product files including a new application server (a new version is supported in
LiveCycle ES2).
3. (Optional - LiveCycle 7.x compatibility layer only) Extracting configuration settings and data from
LiveCycle 7.x EAR files and applying them to the LiveCycle ES2 EAR files and database. (Not applicable
to LiveCycle Policy Server upgrades.)
4. Upgrading and deploying the LiveCycle ES2 EAR files.
5. Updating (patching) the LiveCycle ES2 services components.
6. (Optional) Applying a compatibility layer to the LiveCycle ES2 EAR files. The compatibility layer
comprises a set of deprecated Enterprise JavaBeans™ (EJBs), classes, servlets, and CORBA APIs, which
support custom applications developed with LiveCycle 7.x and enable these legacy applications to
continue to work with LiveCycle ES2.
7. Migrating data to the LiveCycle ES2 database for LiveCycle 7.x products that used User Management
(LiveCycle Forms, LiveCycle PDF Generator, and LiveCycle Workflow).
8. Remove all LiveCycle ES (8.x) JMS configurations.
The installation program or LiveCycle Configuration Manager performs most of the tasks. You are
prompted for input throughout the process, as described by the steps in this document.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
10
Detailed outline of tasks performed in the turnkey upgrade process
If you originally installed LiveCycle ES (8.x) using the turnkey method, you can use the turnkey upgrade
process to move from LiveCycle ES (8.x) to LiveCycle ES2. The turnkey installation and upgrade process
performs the following tasks:
●
Installs the LiveCycle ES2 product files
●
Installs a preconfigured version of JBoss 4.2.1 Application Server (with Apache Tomcat servlet container
embedded)
●
Reuses the existing MySQL 5.0.18 database - you must manually update your database version to
MySQL 5.1.30 prior to upgrading (see “Upgrading the MySQL database from 5.0.18 to 5.1.30 for LiveCycle
ES JBoss turnkey installation”)
Note: During the upgrade process LiveCycle Configuration Manager updates your existing MySQL
database schema, thus rendering it no longer usable with LiveCycle ES (8.x). Be sure to back up
your database prior to running the upgrade.
●
Starts LiveCycle Configuration Manager
●
Stops the JBoss for Adobe LiveCycle ES (8.x) service
●
Migrates contents of Global Document Storage (GDS) from the default location of LiveCycleS ES (8.x) to
LiveCycle ES2 default location.
Note: If you changed the GDS location in LiveCycle ES, you need to ensure that your LiveCycle ES2 GDS
location should be the same or copy the LiveCycle ES (8.x) contents manually to the new
LiveCycle ES2 GDS location.
●
●
Migrates custom datasources from LiveCycle ES (8.x) to LiveCycle ES2.
Extracts configuration data from LiveCycle ES (8.x) EAR files. This task is applicable only if you choose
to install LiveCycle 7.x compatibility layer.
●
Configures and assembles the LiveCycle ES2 EAR files. This task includes merging the compatibility
layer into the EAR files, if you select this option to support LiveCycle 7.x API support.
●
Applies applicable data extracted from LiveCycle 7.x EAR files, and applies the LiveCycle API
compatibility layer to LiveCycle ES2
●
Starts the JBoss for Adobe LiveCycle ES2 service
●
Deploys LiveCycle ES2 to JBoss
●
Initializes the MySQL 5.1.30 database
●
Deploys all the required components to JBoss
●
Updates (patches) the LiveCycle ES components, preserving previous service configuration
parameters, endpoints, watched folders, and so on.
●
Migrates essential data, including settings, configuration data, fonts, and documents from GDS
directory from LiveCycle ES (8.x) to LiveCycle ES2
●
Deploys the LiveCycle 7.x compatibility solution components
●
Configures modules such as LiveCycle ES2 Connectors for ECM, PDF Generator ES2 and
Reader Extensions ES2
●
Imports LiveCycle ES2 Samples to JBoss
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
11
Task checklist
Instructions for all upgrade tasks are included in this document. You must perform the following tasks to
upgrade LiveCycle ES (8.x) products to LiveCycle ES2 using the turnkey method on a single server.
Task
Topic
Back up the LiveCycle ES (8.x) environment.
“Backing up the LiveCycle ES (8.x) data files” on
page 16
(LiveCycle PDF Generator ES2 upgrade only) Install
Adobe Acrobat from the Acrobat media.
“Installing Acrobat for PDF Generator ES2 or
PDF Generator 3D ES2” on page 19
Install LiveCycle ES2 using the LiveCycle ES2
installation program.
“Installing LiveCycle ES2” on page 21
Start LiveCycle Configuration Manager and choose
Upgrade to LiveCycle ES2.
“Upgrading LiveCycle ES (8.x) to LiveCycle ES2” on
page 24
Complete the post-deployment activities.
“Post-Deployment Activities” on page 33
2
System prerequisites
This section provides the hardware and software requirements to install LiveCycle ES2 using the turnkey
method.
2.1 Development versus production environments
Use the turnkey installation to install all the modules on a single system for development and evaluation.
Ensure that your target computer has at least 4 GB RAM. In addition, install LiveCycle
Business Activity Monitoring ES2 on a different 64-bit Windows server. Business Activity Monitoring ES2 is
not supported on 32-bit systems, but other LiveCycle ES2 components are supported on 32-bit operating
systems.
For production use, deploy Business Activity Monitoring ES2 on a separate application server. For larger
production use, Business Activity Monitoring ES2 must be installed on a dedicated system running both a
64-bit operating system and application server.
2.2 Additional prerequisites
Before you install LiveCycle ES2, ensure that you have the following prerequisite hardware and software
installed:
●
“Hardware” on page 12
●
“Operating system” on page 13
●
“Web browser support” on page 13
●
“Application server” on page 16
Additionally, if you include LiveCycle PDF Generator ES2 as part of your LiveCycle ES2 solution, complete
the following tasks before you begin the installation:
●
“Granting the Logon As Service right when installing PDF Generator ES2 or PDF Generator 3D ES2” on
page 19
●
“Installing Acrobat for PDF Generator ES2 or PDF Generator 3D ES2” on page 19
2.2.1 Hardware
For any installation, these settings are recommended as the minimum:
●
Disk space for installation: 3 GB (an additional 3 GB is required if you are using an ESD download and
not installing from a DVD)
●
System temporary space during installation: 5.4 GB
●
Memory for running LiveCycle ES2: 3.4 GB
●
Processor: Intel® Pentium® 4 or equivalent, 1.6 GHz, or higher processor
12
Adobe LiveCycle ES2
System prerequisites
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Operating system
13
2.2.2 Operating system
The turnkey method supports the following Microsoft Windows operating systems:
●
Windows Server 2003 Standard and Enterprise Edition SP2 running on 32-bit and 64-bit architectures.
●
Windows Server 2003 Standard and Enterprise Edition R2 SP2 running on 32-bit, 64-bit, and VMWare
ESX/GSX architectures
●
Windows Server 2008 Standard and Enterprise Edition running on 64-bit architectures (required for
production environment)
●
Business Activity Monitoring ES2 requires 64-bit operating system. If you want to install BAM also on
the same machine, choose a 64-bit Windows operating system for installing LiveCycle ES2.
For preconfiguration settings on Windows Server 2008 Enterprise Edition environment, see “Configuration
for 64-bit Windows Server 2008, Windows 7 or Vista installations” on page 17.
Note: Microsoft Windows XP (SP2 or SP3), Windows Vista (32-bit and 64-bit), and Windows 7 (32-bit and
64-bit) are supported for LiveCycle ES2 evaluation and development.
Business Activity Monitoring ES2 is not supported on Windows 7.
Note: You must have administrator privileges on Windows. If you run the installer using an account that
does not have these privileges, you will be prompted for the credentials of an account with
administrator privileges.
2.2.3 Web browser support
This section outlines the supported web browsers for the LiveCycle ES2 user interfaces. Although
LiveCycle ES2 turnkey only installs on Windows, the end-user user interfaces can be accessed remotely
from computers running on other operating systems. Refer to the following tables for supported web
browsers.
To view some LiveCycle ES2 modules, you must install a supported version of Flash Player available from
www.adobe.com.
2.2.3.1 End-user user interface
End-user components include these modules:
●
LiveCycle Workspace ES2 (Flash Player required)
Note: Adobe Flash Player 9.0.115.0 or later is required for Workspace ES2 or for using form guides in
Workspace ES2.
●
LiveCycle Reader Extensions ES2 (Flash Player required)
●
LiveCycle Rights Management ES2 (Flash Player required)
●
LiveCycle PDF Generator ES2 and LiveCycle PDF Generator 3D ES2 (browser only)
●
LiveCycle Content Services ES2 (browser only)
Adobe LiveCycle ES2
System prerequisites
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Web browser support
Operating system
Flash Player
Microsoft Windows Vista™
Flash Player 9 or 10 Microsoft Internet Explorer 7 or later(1)
14
Supported browser
Firefox 3.0 or later(1)
Windows 2000
Flash Player 9 or 10 Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Windows XP
Flash Player 9 or 10 Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Microsoft Windows 7
Flash Player 9 or 10 Microsoft Internet Explorer 8.0 or later
Firefox 3.0 or later
Windows Server 2003
Flash Player 9 or 10 Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Microsoft Windows Server
2008
Flash Player 9 or 10 Microsoft Internet Explorer 7 or later(1)
Mac OS X v 10.4.x or 10.5.x
(PowerPC)
Flash Player 9 or 10 Firefox 3.0 or later (not for Workspace ES2)(1)(2)
Mac OS X v 10.4.x, 10.5.x., or
10.6.x (Intel)
Flash Player 9 or 10 Firefox 3.0 or later (not for Workspace ES2)(1)(2)
Firefox 3.0 or later(1)
Safari 3.x or 4.x (Workspace ES2 and
Content Services ES2 require version 3.0.3 or later)
Safari 3.x or 4.x (Workspace ES2 and
Content Services ES2 require version 3.0.3 or later)
(1)“or later” includes major revisions. For example, Internet Explorer 6 or later also covers Internet Explorer
7 and 8.
(2)
Workspace ES2 supports Internet Explorer and Firefox on Windows but only Safari 3.0.3 or later on the
Mac.
●
LiveCycle Forms ES2
Operating system
Flash Player
Supported browser
Microsoft Windows Vista™
N/A
Microsoft Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Netscape 8.x or later
Windows XP
N/A
Microsoft Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Netscape 8.x or later
Windows 7
N/A
Microsoft Internet Explorer 7.0 or later
Firefox 3.0 or later
Adobe LiveCycle ES2
System prerequisites
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Web browser support
Operating system
Flash Player
Supported browser
Windows Server 2003
N/A
Firefox 3.0 or later(1)
Windows 2008 Server
N/A
Microsoft Internet Explorer 7.0 or later
15
Firefox 3.0 or later
Linux (Intel)
Firefox 3.0 or later(1)
N/A
Netscape 8.x or later
Mac OS X v 10.4.x or 10.5.x
(PowerPC)
N/A
Safari 3.x or 4.x
Mac OS X v 10.4.x, 10.5.x., or
10.6.x (Intel)
N/A
Safari 3.x or 4.x
(1)“or later” includes major revisions. For example, Internet Explorer 6 or later also covers Internet Explorer
7 and 8.
●
LiveCycle Business Activity Monitoring ES2
Operating system
Flash Player
Supported browser
Microsoft Windows Vista™
Flash Player 9 or 10 Microsoft Internet Explorer 7or later(1)
Windows XP
Flash Player 9 or 10 Microsoft Internet Explorer 6 or later(1)
Windows Server 2000
Flash Player 9 or 10 Microsoft Internet Explorer 6 or later(1)
(1)“or later” includes major revisions. For example, Internet Explorer 6 or later also covers Internet Explorer
7 and 8.
2.2.3.2 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 3.0 or later(1)
Windows 2000
N/A
Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Windows XP
N/A
Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Windows Server 2003
N/A
Internet Explorer 6 or later(1)
Firefox 3.0 or later(1)
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
System prerequisites
Application server
16
(1)
“or later” includes major revisions. For example, Microsoft Internet Explorer 6 or later also covers
Microsoft Internet Explorer 7 and 8.
2.2.4 Application server
The turnkey method supports JBoss 4.2.1 (which includes the Apache Tomcat servlet container).
When you upgrade your existing LiveCycle ES (8.x) environment, the LiveCycle ES2 installation will install
and configure a new instance of JBoss Application Server 4.2.1. Once you have verified that your upgraded
environment is working properly, you can remove the old JBoss instance from your server.
2.3 Backing up the LiveCycle ES (8.x) data files
Before starting the upgrade process, you must back up all the files and directories associated with the
LiveCycle ES (8.x) deployment, including the Java SDK, installation files, watched folder contents,
temporary directory, and so on. Do not delete any of these items. The backup tasks involved are as follows:
●
Stop the LiveCycle ES (8.x) server. Wait until all long-lived processes have stopped (or stop them
manually, if necessary), and then proceed to perform a cold backup according to the following
documents:
LiveCycle ES (version 8.0): Refer to the technical article LiveCycle ES Database and GDS Backup and
Recovery.
LiveCycle ES Update 1 (version 8.2): Refer to the Backup and Recovery chapter of the Administering
LiveCycle ES guide.
The following LiveCycle data must be included in your back up:
GDS directory: This directory can reside either locally or on a shared network drive.
Database: Use the database backup utility as described in the guides mention above. If your current
database is no longer supported, you must also migrate your data to the new LiveCycle ES2 database.
LiveCycle ES (8.x) EAR files: You will need to point LiveCycle Configuration Manager to the location of
these files during upgrade. If you upgraded from LiveCycle 7.x, the related information is extracted
from these files during configuration. As well, these files are required to restore your system if you
encounter upgrade issues.
Content Storage Root directory: If you have Content Services ES deployed on your current system,
back up the lccs_data directory. This directory can reside either locally or on a shared network drive.
LiveCycle fonts: Back up all Adobe and customer font directories that are specified in LiveCycle
Configuration Manager (go to Settings > Core System > Configurations). Ensure that you back up the
entire directory.
Customer installed fonts: If you installed additional fonts on your LiveCycle ES (8.x) environment,
back them up separately.
2.4 Before you upgrade
Before you begin upgradingto LiveCycle ES2, read through the following information to ensure that your
installation runs smoothly:
●
To reduce the time to complete the installation, install LiveCycle ES2 either by using a local copy of the
installation file set or directly from the DVD instead of installing from a shared network location.
Adobe LiveCycle ES2
System prerequisites
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey) Configuration for 64-bit Windows Server 2008, Windows 7 or Vista installations
17
●
Ensure that the installation media that you received is not damaged. If you copy the installer media to
the hard disk of your computer, ensure that you copy the entire DVD contents on to the hard disk.
●
If you downloaded the installer file set, verify its integrity using an MD5 check sum utility. Use this
utility to check the MD5 check sum values with the value displayed on the Adobe download web site.
You can use a tool such as WinMD5.
●
To avoid installation errors, do not copy the DVD install image to a directory path which exceeds the
maximum path length limitation. Typically, long network paths cause this error. See
http://msdn.microsoft.com/en-us/library/aa365247.aspx for more information.
●
Download any patch updates for LiveCycle ES2 available from LiveCycle Technical Support.
●
To improve the speed of installation on Windows, disable any on-access virus scanning software for the
duration of the installation.
●
The turnkey installation creates the following Windows services, which, by default, are set to run
automatically on startup:
●
JBoss for Adobe LiveCycle ES2
●
MySQL for Adobe LiveCycle ES2 (not applicable if you are installing LiveCycle ES2 on the same
computer as the existing LiveCycle ES (8.x) turnkey being upgraded)
These services manage the application server and the database for the turnkey upgrade. You can start,
stop, and pause these services by using the Windows Services Control Manager. To open the Windows
Services Control Manager, go to Control Panel > Administrative Tools > Services. Using this tool, you
can also configure the services to start when the computer starts or to require manual startup.
●
By default, the turnkey installation places LiveCycle ES2 components in the
C:\Adobe\Adobe LiveCycle ES2\ directory (referred to as the [LiveCycleES2 root] directory).
Caution: If you choose to install to a non-default directory, do not use the name test as your directory
name (for example, C:\test) or the MySQL install process will fail.
●
By default, JBoss is installed to and run from the [LiveCycleES2 root]/jboss directory.
2.4.1 Configuration for 64-bit Windows Server 2008, Windows 7 or Vista
installations
On 64-bit Windows Server 2008 or Vista operating systems, modify the Admin Approval Mode security
option as follows:
1. Go to Start > Control Panel > Administrative Tools > Local Security Policy > Local Policies >
Security Options.
2. Locate User Account Control: Behavior of the elevation prompt for administrators in Admin
Approval Mode and set it to Elevate without prompting.
3. Restart your computer.
Caution: The Windows User Account Control (UAC) must remain disabled for PDF Generator ES2 or
PDF Generator 3D ES2 to work properly. You can run the installation and configuration process
by turning on the UAC with the Elevate without prompting option enabled. However, you must
disable UAC to run PDF Generator ES2 or PDF Generator 3D ES2.
If you are installing and configuring on an evaluation system, you can enable the UAC on the
computer after you have deployed to your production computer or uninstalled
PDF Generator ES2 or PDF Generator 3D ES2.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
System prerequisites
Preconfiguration for PDF Generator ES2 and PDF Generator 3D ES2
18
➤ Disable the Windows UAC on Vista:
1. To access the System Configuration Utility, go to Start > Run and in the Open: box enter MSCONFIG.
2. Click the Tools tab and scroll down and select Disable UAC.
3. Click Launch to run the command in a new window.
4. When finished, close the command window and close the System Configuration window.
5. Restart your computer.
To enable the UAC again, repeat the steps above and select Enable UAC before clicking Launch.
➤ Disable the Windows UAC on Server 2008:
1. Go to Start > Control Panel > User Accounts > Turn User Account Control on or off.
2. Deselect the Use User Account Control (UAC) to help protect your computer option and then click
OK.
3. Restart the computer.
To enable the UAC again, repeat the steps above and select the Use User Account Control (UAC) to help
protect your computer option before restarting the computer.
➤ Disable the Windows UAC on Windows 7:
1. To access the System Configuration Utility, go to Start > Run and in the Open: box enter MSCONFIG.
2. Click the Tools tab and scroll down and select Change UAC Settings.
3. Click Launch to run the command in a new window.
4. Adjust the slider to the Never notify level.
5. When finished, close the command window and close the System Configuration window.
6. Restart your computer.
To enable the UAC again, repeat the steps above and adjust the slider to a desired level before restarting
your computer.
2.4.2 Preconfiguration for PDF Generator ES2 and PDF Generator 3D ES2
Before you install PDF Generator ES2 or LiveCycle PDF Generator 3D ES2, complete the tasks listed in the
following two sections. To enable native application support for PDF Generator ES2 or
LiveCycle PDF Generator 3D ES2, grant the Logon As Service right to the Microsoft Administrator in
Windows before you begin the turnkey installation. With native application file support,
PDF Generator ES2 and PDF Generator 3D ES2 can convert files from native formats such as Microsoft
Word to Adobe PDF format.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
System prerequisites
Preconfiguration for PDF Generator ES2 and PDF Generator 3D ES2
19
2.4.2.1 Granting the Logon As Service right when installing
PDF Generator ES2 or PDF Generator 3D ES2
If you are installing PDF Generator ES2 or PDF Generator 3D ES2 on any Windows operating system, grant
the Logon As Service right to the user that installs LiveCycle ES2.
➤ To set the Logon As Service right:
1. Select Start > Control Panel > Administrative Tools > Local Security Policy > Local Policies > User
Rights Assignment.
2. Double-click Log on as a service and click Add User or Group.
3. Type the user name for the Microsoft Administrator and click OK.
2.4.2.2 Installing Acrobat for PDF Generator ES2 or PDF Generator 3D ES2
LiveCycle PDF Generator ES2 or PDF Generator 3D ES2 can convert many native file formats to PDF. Such
native file formats include Microsoft Word, Microsoft Excel, Microsoft PowerPoint, Microsoft Project,
Microsoft Visio, Corel WordPerfect, Adobe Photoshop® (CS2 only), Adobe FrameMaker®, and Adobe
PageMaker®.
If you plan to use PDF Generator ES2 or PDF Generator 3D ES2 native application format conversion or
optical character recognition (OCR) generation, install Acrobat 9.2 Professional Extended on the computer
where PDF Generator ES2 will run before you run the LiveCycle ES2 installation program. You can also
install Acrobat 9.2 later and perform some additional manual tasks.
If you do not want to configure PDF Generator ES2 or PDF Generator 3D ES2 to support this functionality,
you do not need to install or upgrade to Acrobat 9.2 Professional Extended. However, it is recommended
that you upgrade to Acrobat 9.2 Professional Extended in order to support conversions that use Microsoft
Office 2007.
➤ To install Acrobat 9.2 Professional Extended for PDF Generator ES2 or PDF Generator 3D ES2:
1. Uninstall any other version of Acrobat by using the Add/Remove Programs window in the Windows
Control Panel.
2. Restart your computer if prompted.
3. Install Acrobat 9.2 Professional Extended by running the AutoPlay.exe file from the installation media
or folder which contains the installer file set.
4. Follow the instructions on the Acrobat installer screens.
3
Upgrading to LiveCycle ES2 (JBoss Turnkey)
This chapter describes how to upgrade from LiveCycle ES (8.x) turnkey for JBoss to LiveCycle ES2.
3.1 Checking the installer
Observe the following best practices with the installer files before you begin the installation process.
➤ Check the DVD installation media:
Ensure that the installation media that you received is not damaged. If you copy the installer media
contents to the hard disk of your computer where you are installing LiveCycle ES2, ensure that you copy
the entire DVD contents on to the hard disk. To avoid installation errors, do not copy the DVD install image
to a directory path that exceeds the Windows maximum path length limit.
➤ Check the downloaded files:
If you downloaded the installer from the Adobe web site, verify the integrity of the installer file using the
MD5 checksum. Use a tool such as WinMD5 to calculate and compare the MD5 checksum of the
downloaded file with the checksum published on the Adobe download web page.
➤ Expanding the downloaded archive files:
If you downloaded the ESD from the Adobe web site, extract the entire [appserver]_DVD.zip (Windows)
archive file to your computer.
Note: Be sure to keep the directory hierarchy unchanged from the original ESD file.
3.2 Upgrading exceptions
The following list shows exceptions you may encounter during the installation and configuration process
when upgrading to LiveCycle ES2. These exceptions do not indicate that there is a problem and the
upgrade can conclude successfully. Once LiveCycle Configuration Manager has successfully finished and
the application server is restarted, these exceptions will not occur.
●
no setup for com.adobe.edc.server.spi.storage.entity.PrincipalEntity
●
javax.naming.NameNotFoundException: JobManagerBeanLocal not bound
●
com.adobe.pof.schema.AttributeNotFoundException
●
no setup for com.adobe.edc.server.spi.storage.entity.LicenseEntity
●
java.lang.NoSuchMethodError:
com.adobe.idp.event.util.EventDBHelper.getNewAsynchEvents()[Lcom/adobe/idp
/event/boi/Event
●
com.adobe.idp.dsc.registry.ServiceNotFoundException: Service:
HTTPDocumentAuthenticationService not found
●
com.adobe.idp.dsc.registry.service.DuplicateServiceConfigurationException:
Service Configuration: DocumentManagementService already exists
20
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Installing LiveCycle ES2
●
java.lang.ClassNotFoundException: http-0.0.0.0-8080-4Class name
com.adobe.idp.taskmanager.dsc.userservice.UserServiceImpl from package
com.adobe.idp.taskmanager.dsc.userservice not found.
●
com.adobe.idp.dsc.InvalidStateException: Service:
PDFMMPdfFactoryEncryption is not in a RUNNING state
21
3.3 Installing LiveCycle ES2
The default target installation directory for LiveCycle ES2 is C:\Adobe\Adobe LiveCycle ES2. After you
install LiveCycle ES2, you will run LiveCycle Configuration Manager to perform the upgrade from
LiveCycle ES (8.x) to LiveCycle ES2.
Before you install LiveCycle ES2, make sure you have reviewed the following sections:
●
“System prerequisites” on page 12
●
“Installing LiveCycle ES2” on page 21
➤ To install LiveCycle ES2 using Turnkey:
1. Do one of the following:
●
From the download site, download and extract the entire JBoss_DVD.zip file (the LiveCycle ES2
Electronic Software Download or ESD file) to your file system. Be sure to keep the directory
hierarchy unchanged from the JBoss_DVD.zip file.
●
●
After extracting the ZIP file, launch the installer using one of the following methods:
●
Navigate to the livecycle_server folder and double-click the run_windows_installer.bat file.
This file will determine the correct LiveCycle ES2 installer and run it.
●
(for 32 bit systems) double-click the install.exe file from the
\livecycle_server\9.0\Disk1\InstData\Windows\VM folder
●
(for 64 bit systems) double-click the install.exe file from the
\livecycle_server\9.0\Disk1\InstData\Windows_64bit\VM folder
From the JBoss DVD, navigate to the livecycle_server folder. Launch the installer using one of the
following methods:
●
Navigate to the livecycle_server directory and double-click the run_windows_installer.bat
file. This file will determine the correct LiveCycle ES2 installer and run it.
●
(for 32 bit systems) double-click the install.exe file from the
\livecycle_server\9.0\Disk1\InstData\Windows\VM folder
●
(for 64 bit systems) double-click the install.exe file from the
\livecycle_server\9.0\Disk1\InstData\Windows_64bit\VM folder
2. When prompted, select the language for the installation to use, and then click OK.
3. On the Introduction screen, click Next.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Installing LiveCycle ES2
22
4. Choose whether to upgrade your existing LiveCycle ES (8.x) environment using your existing database
or perform a fresh LiveCycle ES2 installation, and click Next.
If your LiveCycle ES (8.x) environment was installed using a non-default directory or if you have
multiple LiveCycle ES (8.x) instances installed, click Browse to locate the install directory.
If you see a Ports in Use error when installing LiveCycle ES2 on the same machine where
LiveCycle ES (8.x) is installed, it is safe to ignore. Click OK to continue.
Caution: If you select a directory that is different from the directory where the previous version of
LiveCycle was installed, you will see an Install Path Error message.
5. (PDF Generator ES2 and PDF Generator 3D ES2 on Windows Server 2003 only) In the Adminstrative
Credentials screen, select Yes, enable native application support for PDF Generator ES2 and enter
the user name and password, and click Next.
The native application support functionality allows you to convert native applications, such as
Microsoft Word, to PDF. However, you must install these native applications on the same server as you
are installing PDF Generator ES2 and PDF Generator 3D ES2.
Note: PDF Generator 3D ES2 requires native application support to convert 3D files to PDF. Adobe
Acrobat® version 9.2 is required to configure support for native Windows applications. For
information about installing Acrobat 9.2, see “Installing Acrobat for PDF Generator ES2 or
PDF Generator 3D ES2” on page 19.
Note: The password for the user must not contain two consecutive $ characters (for example,
dollar$$) as this causes the install wizard to return an ‘invalid credentials’ error.
Caution: You must provide the correct administrator name and password; otherwise, LiveCycle ES2 will
not run. Use the same administrator account you used in “Installing Acrobat for
PDF Generator ES2 or PDF Generator 3D ES2” on page 19. This administrator account must be
the same account which was used to install Microsoft Office on the system and include the
Windows Machine Name prefix if that user is not a local account on the target computer. Do not
use either localhost or the IP address of the Windows Server.
6. Read the Adobe LiveCycle ES2 Server License Agreement and, if you agree, select I accept, and then
click Next.
7. Read the MySQL License Agreement and, if you agree, select I accept, and then click Next.
8. Read the JBoss Application Server License Agreement and, if you agree, select I accept and then click
Next.
9. Review the preinstallation summary, and then click Install. The installation program displays the
progress of the installation. This process may take several minutes to complete.
10. Review the Release Notes and click Next.
11. Review the post-installation summary information and choose one of these options:
●
If no service pack updates are required, ensure that Start the LiveCycle Configuration Manager is
selected, and then click Done.
●
If service pack updates are required or if you are installing Connector for EMC Documentum,
Connector for IBM FileNet, or LiveCycle Content Manager, deselect this option and click Done to
continue with the following sections before you run LiveCycle Configuration Manager.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
●
Install service packs
23
(New for 9.5) If you plan to install LiveCycle ES2.5 Solution Accelerators, you are required to first
apply LiveCycle ES2 service pack 2 or later and install LiveCycle ES2.5 Solution Accelerators. In that
case, deselect this option and click Done to continue with Installing and Deploying LiveCycle ES2.5
Solution Accelerators before you run LiveCycle Configuration Manager.
Note: If you deselect Start the LiveCycle Configuration Manager and exit the installer, you can run
LiveCycle Configuration Manager by using the ConfigurationManager.bat file located in
[LiveCycleES2 root]\configurationManager\bin
3.4 Install service packs
Before you complete the configuration using LiveCycle Configuration Manager, apply the latest
LiveCycle ES2 service packs. These updates are available from LiveCycle Technical Support.
3.5 Preparing the Connectors for ECM for upgrade
If you are upgrading to LiveCycle ES2 Connector for EMC Documentum, LiveCycle ES2
Connector for IBM FileNet, or LiveCycle ES2 Connector for IBM Content Manager from LiveCycle ES (8.x),
you must configure an application server system property after you install LiveCycle ES2 and before you
start LiveCycle Configuration Manager to complete the upgrade process.
➤ Configure the Connectors for ECM for upgrade:
Note: If you are not upgrading on a new computer, skip to step 2.
1. (For out-of-place to a new computer only) Install the client for your ECM repository on the
LiveCycle ES2 server that hosts the new application server.
2. Perform all settings related to Connectors for ECM (except for LiveCycle Administration Console
settings) on the new application server prior to beginning the upgrade. See the “Configuring the
Connector...” section of the Post Deployment chapter for your EMC product in the Installing and
Deploying LiveCycle ES2 for JBoss guide.
3. Navigate to the [appserver root]/bin directory on your LiveCycle ES (8.x) server and copy the
adobe-component-ext.properties file to the appropriate directory on the target server.
4. (Upgrade from version 8.0 only) Open the adobe-component-ext.properties file in a text editor.
5. (Upgrade from version 8.0 only) Copy the system property [component id]_[component
version].ext=[JAR files and/or folders] and paste or add it as a new system property in
the file.
6. (Upgrade from version 8.0 only) Delete [component version] from the new system property so
that the line appears as [component id].ext=[JAR files and/or folders].
7. Ensure that the new line ends with a hard return and then save the file.
8. Restart the application server.
You can now continue to run LiveCycle Configuration Manager to upgrade to LiveCycle ES2. (See “Next
steps” on page 32.)
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
24
Caution: For LiveCycle ES Connector for EMC Documentum or Connector for IBM FileNet, the default
repository must be set to LiveCycle ES Native Repository Provider or the upgrade deployment
will fail. If you have configured the ECM repository provider as the default repository for either of
these connectors, open the LiveCycle ES (8.x) LiveCycle Administration Console and navigate to
Services > LiveCycle ES [connector type] > Configuration Settings. Select the LiveCycle ES
Repository Provider option and then click Save.
3.6 Upgrading LiveCycle ES (8.x) to LiveCycle ES2
Now that LiveCycle ES2 is installed on the computer where LiveCycle ES (8.x) is running, you are ready to
begin the upgrade configurations. LiveCycle Configuration Manager performs the tasks required for
upgrading.
When LiveCycle Configuration Manager completes the upgrade process, LiveCycle ES2 will be deployed
and started.
Tip: You can press F1 in LiveCycle Configuration Manager to view Help information for the screen you are
viewing.
➤ To configure LiveCycle ES2 :
1. If you are continuing from the LiveCycle ES2 installation, proceed to step 3; otherwise, navigate to the
[LiveCycleES2 root]\configurationManager\bin folder and run ConfigurationManager.bat.
2. When prompted, select the language for LiveCycle Configuration Manager to use, and then click OK.
3. If you are prompted to choose to use existing Configuration Data, click OK.
4. On the Welcome screen, click Next.
5. On the Upgrade Tasks Selection screen, select the appropriate option for your existing version of
LiveCycle ES (8.x), and then click Next.
Note: The Install the LiveCycle 7.x Compatibility Layer option is available for any install or upgrade
scenario. Choose this option if you are installing LiveCycle ES2 on a development system on
which you plan to use client applications originally developed with LiveCycle 7.x.
6. On the Module Selection screen, ensure that the LiveCycle ES2 modules that you have licensed and
want to deploy are selected, and then click Next.
Note: You do not need to deploy all of your licensed modules at the same time. You can rerun
LiveCycle Configuration Manager later to deploy more modules.
Caution: Do not select Adobe Business Activity Monitoring ES2, version 9.0.0.0 even if it is part of your
LiveCycle ES (8.x) environment. See “Upgrade and deploy Business Activity Monitoring ES2” on
page 31.
7. (LiveCycle 7.x compatibility layer only) On the LiveCycle 7.x compatibility screen, deselect any
LiveCycle 7.x product for which you do not want merge the compatibility layer, and then click Next.
8. On the Task Selection screen, ensure that all the available tasks are selected, and then click Next.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
25
Note: The Configure Application Server and Validate Application Server Configuration tasks are
not available for selection for JBoss turnkey. The JBoss turnkey method does not support these
tasks because the application server is already configured for LiveCycle ES2.
9. On the Pre-upgrade Steps and Pre-upgrade Steps Contd screens, review the requirements and perform
all tasks relevant to your environment and then click Next.
10. On the Stop LiveCycle ES screen, click the Stop LiveCycle ES button to stop the LiveCycle ES (8.x) JBoss
service, and then click Next.
11. On the Migrate Global Document Storage (GDS) directory and other LiveCycle ES contents screen, click
Migrate Contents to copy the contents of the existing GDS directory to the new LiveCycle ES2
location. When complete, click Next.
12. On the Migrate Custom Data Sources screen, if you have created custom data sources after installing
LiveCycle ES (8.x), select the Import datasources option, click Start to import them, and then click
Next when done.
If you do not have custom data sources, leave the option deselected and click Next.
13. (Import LiveCycle ES (8.x) data sources only) On the Migrate Custom Data Sources (Contd.) screen,
select (or deselect) the data sources to migrate, and then click Start. When done, click Next.
Note: You can skip migrating the data sources by clicking Next without first clicking Start. Run
LiveCycle Configuration Manager again later to perform these steps.
14. (LiveCycle 7.x compatibility layer only) On the Import LiveCycle ES Files screen, provide the path to
the deployable archive files that are associated with LiveCycle ES (8.x). After you provide the required
information, click Next.
Note: These files contain important configuration data that must be migrated to the new
LiveCycle ES2 server for the upgrade to succeed.
15. (LiveCycle 7.x compatibility layer only) On the Extract LiveCycle 7.x Configuration Data screen, click
Start to extract the data from the LiveCycle 7.x EAR files. When the process is finished, click Next.
Note: This screen appears only if the LiveCycle 7.x product has extractable data.
16. On the Configure LiveCycle ES2 (1 of 5) screen, click Configure and, when the EAR files have been
configured, click Next. Depending on the number of modules that are included in the configuration,
this process may take several minutes to complete. Click View Progress Log to view the status of the
EAR file configuration.
17. (LiveCycle 7.x compatibility layer only) On the Apply LiveCycle 7.x Compatibility screen, click Start to
add the compatibility layer to the LiveCycle ES2 EAR files, and then click Next to continue.
18. On the Configure LiveCycle ES2 (2 of 5) screen, set the directories that LiveCycle ES2 will use to access
fonts and store temporary data that is associated with processing jobs, and then click Next.
Tip: Edit the configuration only if you need to change any of the values on this screen.
●
(Optional) To change the default location of the Adobe server fonts directory, type the path or
browse to the directory.
●
Accept the value in the Customer fonts directory box. If you did not specify a location for the
customer fonts directory, this box appears empty, and you can choose to specify a new location for
your customer fonts. (Accepting the empty box accepts the default font directory location.)
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
26
Note: Your right to use fonts provided by parties other than Adobe is governed by the license
agreements provided to you by such parties in connection with those fonts, and is not covered
under your license to use Adobe software. Adobe recommends that you review and ensure you
are in compliance with all applicable non-Adobe license agreements before using non-Adobe
fonts with Adobe software, particularly with respect to use of fonts in a server environment.
●
●
(Optional) To change the default location of the System fonts directory, type the path or browse to
the directory.
(Optional) To enable FIPS, ensure that Enable FIPS is selected. Select this option only if you require
the Federal Information Processing Standards (FIPS) to be enforced.
Note: Any modification to the System fonts directory or Enable FIPS values made on this screen will
not be configured during the upgrade process. You must manually update your system fonts
directories and enable the FIPS option in LiveCycle Administration Console after configuration is
complete. See “Core Configurations” in the LiveCycle ES2 Administration Help.
19. On the Configure LiveCycle ES2 (3 of 5) screen, accept the default location for the Location of the
temporary directory, or enter the path or browse to it. Click Next to continue.
20. On the Configure LiveCycle ES2 (4 of 5) screen, accept the default location for the Global document
storage directory path, or click Browse to specify the fully qualified path. You determined the
location of the GDS root directory during the directory backup process. (See “Backing up the
LiveCycle ES (8.x) data files” on page 16.) If LiveCycle ES (8.x) did not use the default GDS directory,
specify a directory for LiveCycle ES2.
Note: Do not modify the prepopulated value if your LiveCycle ES (8.x) GDS directory existed in the
default location and you migrated the GDS contents to LiveCycle ES2 installation in step 11.
21. On the Configure Persistent Document Storage (5 of 5) screen, select either Use GDS or Use Database.
22. Click Configure to configure the persistent document storage method and when the process is
finished, click Next.
23. (LiveCycle Content Services ES2 only) On the LiveCycle Content Services ES2 Configuration screen, set
the parameters that Content Services ES2 will use:
Deploy Type: Select single server for the turnkey installation.
Content storage root directory: The root directory used by Content Services ES2.
Enable CIFS: Select this option to allow mapping to a networked Content Services ES2 space.
Note: The content storage root directory should either point to LiveCycle ES (8.x) content storage root
directory or to a new location into which you have copied the contents of LiveCycle ES (8.x)
content storage root directory to this new directory created.
24. (LiveCycle Content Services ES2 only) Click Configure to configure Content Services ES2. When
complete, click Next.
25. (LiveCycle Content Services ES2 - CIFS option only) On the LiveCycle Content Services ES2 CIFS
Configuration screen, set the parameters that Content Services ES2 CIFS requires:
CIFS Server Name: Specify the name through which the Content Services ES2 Repository will be
accessible. By default, LiveCycle Configuration Manager populates the server name of the
LiveCycle ES2 server with ‘a’ attached to it. For example, if the LiveCycle ES2 server name is
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
27
lcserver, the CIFS Server name will be populated as lcservera. You must ensure that the CIFS
server name that you specify is unique within the network.
Choose the CIFS Server Implementation: Select the type of CIFS implementation supported on
the server as one of the following:
Windows Native (DLL Based): Click Browse to select the path (usually,
C:\Windows\system32) to where LiveCycle ES2 LiveCycle Configuration Manager will copy
the DLL files.
JAVA (Socket Based): Specify the alternate IP address assigned to the CIFS Server, and how the
server name will be resolved in the local domain. For example, if the primary IP is 10.40.68.142,
assign 10.40.68.143 as the alternate IP. Ensure that this IP is not allocated to any other machine
on the network.
Use WINS Server or Broadcast to resolve Local Domain: Select the method used to resolve local
domain.
Broadcast: Specify the broadcast address (subnet mask) of the network segment in the local
domain. For example, 10.40.91.255. In Broadcast mode, the CIFS server and clients must be in
the same subnet.
WINS Server: Specify the IP addresses of the primary and secondary WINS servers. For example,
10.40.4.248. If WINS server is selected, the clients can reside in any subnet in the local domain.
26. (LiveCycle Content Services ES2 - CIFS option only) Click Configure to configure Content Services ES2.
When complete, click Next.
27. (LiveCycle Content Services ES2 only) On the LiveCycle Content Services ES2 Module Configuration
screen, select the AMPS to configure in LiveCycle Content Services ES2. Select F1 to display the help on
this topic.
28. (LiveCycle Content Services ES2 only) Click Configure to configure Content Services ES2 modules.
When complete, click Next.
29. On the Configure LiveCycle ES2 Summary screen, click Next.
30. (If you selected Configure SSL only) On the Configure turnkey JBoss SSL screen, enter all the required
values and click Configure JBoss SSL, or select the Skip configuration option, and then click Next.
31. (Forms ES2, Output ES2 and PDF Generator ES2 only) Select the Include IVS EARs in deployment set
option to install three service specific sample applications.
For example, Forms IVS is a sample application that allows you to verify that Forms ES2 is properly
deployed and running.
Note: Do not deploy the IVS EAR files in a production environment.
32. (PDF Generator ES2 only) On the Configure Acrobat For LiveCycle PDF Generator ES2 screen, click
Configure to run the configuration script. When complete, click Next.
33. On the Deploy LiveCycle ES2 EARs screen, select the EAR files you want to deploy to JBoss, click Deploy
and when complete, click Next.
34. On the LiveCycle ES2 Database Initialization screen, verify the host and port information, and then click
Initialize. The database initialization task creates tables in the database, adds default data to the tables,
and creates basic roles in the database. When the initialization completes successfully, click OK on the
dialog and manually restart the JBoss server. and then click Next.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
28
Note: Do not skip this step. Initialization does not harm legacy data.
35. On the LiveCycle ES2 Server Information screen, type the LiveCycle ES (8.x) administrator password,
and click Verify Server Connection. When the validation is complete, click Next.
Note: The server information that appears on this screen represents default values for the deployment.
Verifying the server connection helps narrow troubleshooting in case failures that occur in the
deployment or validation. If the connection test passes but deployment or validation fails in the
next few steps, connectivity issues can be eliminated from the troubleshooting process.
.
36. (Central Migration service only) Select Include Central Migration service in deployment if you are
licensed to configure LiveCycle ES2 with Central Pro or Web Output Pak, and then click Next.
37. On the LiveCycle Component Deployment screen, click Deploy. The components deployed at this time
are Java archive files that plug into the LiveCycle ES2 service container for purposes of deploying,
orchestrating, and executing services. When the deployment has completed successfully, click Next.
38. On the LiveCycle Component Deployment Validation screen, click Validate. LiveCycle Configuration
Manager validates that the Java archive files are deployed to and running on the LiveCycle ES2 server.
When the validation is completed successfully, click Next.
39. On the LiveCycle Server JNDI Information screen, specify the JNDI server host name and port number
and click Verify Connection. When complete, click Next.
40. On the Migrate ECM form templates screen, choose one of the following options:
●
Select the Skip Form Templates Import option to skip importing your existing form templates,
and then click Next.
●
Deselect the Skip Form Templates Import option, click Start to import all of your existing form
templates, and then click Next.
41. (If you deselected Skip Form Templates Import only) On the Migrate ECM form templates (Contd.)
screen, select or deselect the LiveCycle ES (8.x) form templates to migrate, and add or remove the paths
to any directories that contain existing custom form templates. When complete, click Next.
42. On the Migrate Data Essential to LiveCycle ES2 Operation screen, click Start to migrate the data from
your LiveCycle ES (8.x) environment. When complete, click Next.
This step involves copying forms, form data, processes, preferences, FileType settings, job options,
security settings, watched folders, and email job sources (depending on the product you are
upgrading), custom fonts, and documents in the GDS directory.
Caution: (LiveCycle ES2 Connector for IBM FileNet only) When upgrading from LiveCycle ES version 8.0,
the migration log displays the error “[IBMFileNetProcessEngineConnector] failed to start” when
trying to start the Connector for IBM FileNet Process Engine service. This service was not
available in version 8.0 and can be configured manually after you have performed the tasks in
“Post-Deployment Activities” on page 33.
43. (LiveCycle 7.x compatibility layer only) On the Deploy 7.x compatibility DSCs screen, click Start to
deploy the component files. When complete, click Next.
44. Restart the application server.
45. On the Configure LiveCycle Components screen, select the LiveCycle ES2 modules to configure, and
then click Next. The screens that appear next depend on your selection on this screen.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
29
Note: Do not select any of the Connectors for ECM for configuration on this screen if you are
upgrading from LiveCycle ES (8.x).
Steps 46 to 49 are optional and applicable only if you are installing the connectors for the first time, not
upgrading them.
46. (Configure Connector for EMC Documentum only) On this screen, do one of the following tasks:
●
Leave the Configure Connector for EMC Documentum Content Server option deselected to
manually configure EMC Documentum later, and then click Next.
●
Select the option, enter the appropriate version and directory path, and then click Verify. When
complete, click Next and complete the tasks on the following screens:
●
On the EMC Documentum Content Server Settings screen, enter the required values and then
click Next.
●
On the Configure Adobe Connector for EMC Documentum screen, click Configure
Documentum Connector. When complete, click Next.
47. (Configure Connector for IBM Content Manager only) On this screen, do one of the following tasks:
●
Leave the Configure Connector for IBM Content Manager option deselected to manually
configure IBM Content Manager later, and then click Next.
●
Select the option, enter the appropriate directory path, and then click Verify. When complete, click
Next and complete the tasks on the following screens:
●
On the IBM Content Manager Server Settings screen, enter the required values and then click
Next.
●
On the Configure Adobe Connector for IBM Content Manager screen, click Configure IBM
Content Manager Connector. When complete, click Next.
●
On the Required Manual Configurations for LiveCycle Connector for IBM Content Manager
screen, review and perform the manual steps listed and then click Next.
48. (Configure Connector for IBM FileNet only) On this screen, do one of the following tasks:
●
Leave the Configure Connector for IBM FileNet Content Manager option deselected to manually
configure IBM FileNet later, and then click Next.
●
Select the option, enter the appropriate version and directory path, and then click Verify. When
complete, click Next and complete the following screens:
●
On the IBM FileNet Content Server Settings screen, enter the required values and then click
Next.
●
On the Configure Connnector for IBM FileNet Process Engine screen, enter the appropriate
version (if enabled) and directory path, and then click Verify. When complete, click Next.
●
On the IBM FileNet Process Engine Server Settings screen, enter the required values and then
click Next.
●
On the Configure Adobe Connector for IBM FileNet screen, click Configure FileNet Connector.
When complete, click Next.
●
On the Required Manual Configurations for LiveCycle Connector for IBM FileNet Content
Manager screen, review and perform the manual steps listed and then click Next.
49. (Configure ECM Connectors only) On the Verify Configurations screen, do one of the following:
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Upgrading LiveCycle ES (8.x) to LiveCycle ES2
30
●
If you are configuring the connectors for the first time or have modified any of the configurations on
the previous screens, leave the Restart Application Server option selected and click Validate
Configurations. When successfully validated, click Next.
●
If you are configuring the connector after LiveCycle ES2 configuration, deselect the option and click
Validate Configurations. When successfully validated, click Next.
50. (Configure LiveCycle PDF Generator ES2 only) On the Administrator user credentials for LiveCycle
server machine screen, enter the user name and password of a user with administrative privileges on
the server machine. Click Add.
You must add at least one administrative user for Windows 2008 Server. For Windows 2003 Server,
adding a user is not mandatory.
Note: On Windows 2008 Server, User Account Control (UAC) must be disabled for the users you add. To
disable UAC, click Control Panel > User Accounts > Turn User Account Control on or off and
deselect Use User Account Control (UAC) to help protect your computer. Click OK. Your
changes become effective when the system is restarted.
51. (Only for LiveCycle PDF Generator ES2 when LiveCycle Configuration Manager is running locally on a
server machine) On the LiveCycle PDF Generator System Readiness Test screen, click Start to validate if
the system has been appropriately configured for PDF Generator ES2.
52. Review the System Readiness Tool Report and click Next.
53. (LiveCycle Reader Extensions ES2 only) On the Default Reader Extensions Credentials screen, review
the information and then click Next.
Note: If no credential was configured on your LiveCycle ES (8.x) system, then the following screen appears
instead.
54. (LiveCycle Reader Extensions ES2 only) On this screen, specify the following details that are associated
with the Reader Extensions ES2 credential that activates the Module services:
Credential file: The path and file name of the Reader Extensions ES2 credential (.pfx or .p12 file
type).
Credential password: The password that is associated with the credential. This password was
provided with the credential file.
User-defined name for the credential: The name (or alias) that LiveCycle Configuration Manager
gives the credential when it is configured. This name can be any name.
This name appears in the Reader Extensions ES2 web interface, as well as the alias used to reference
the credential through SDK calls. You can create any unique name for the Reader Extensions ES2
credential.
Tip: You can skip this step at this time by selecting Configure later using LiveCycle Administration
Console. You can configure the Reader Extensions ES2 credential by using LiveCycle Administration
Console after the deployment is completed. (After you log in to LiveCycle Administration Console,
click Settings > Trust Store Management > Local Credentials.)
Click Configure and then Click Next.
55. (Optional) On the LiveCycle ES2 Samples Import screen, do one of the following:
●
Click Import to import the LiveCycle ES2 Samples, and then click Next.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
●
Upgrade and deploy Business Activity Monitoring ES2
31
To skip this step, select Skip LiveCycle ES2 Samples Import and click Next. You can import the
samples at a later date by restarting LiveCycle Configuration Manager and choosing to import the
samples.
Caution: Do not import the LiveCycle ES2 Samples if either of these options apply to your situation:
●
If you are deploying LiveCycle ES2 to a production system, importing the samples creates
users with default passwords, which may be a security concern for your production
environment.
56. When the import completes successfully, click Next.
57. On the Summary page, click Next.
58. Review the Next Steps information. When finished, click Finish to exit LiveCycle Configuration
Manager.
Note: After you configure LiveCycle ES2, complete the post-configuration activities that apply to your
solution implementation.(See “Post-Deployment Activities” on page 33.)
59. If you configured SSL, you must restart JBoss for the SSL configuration to take affect.
3.7 Upgrade and deploy Business Activity Monitoring ES2
If you installed LiveCycle Business Activity Monitoring ES (BAM) as part of your LiveCycle ES (8.x) solution,
you need to perform the following tasks to ensure it will work in LiveCycle ES2.
Note: The BAM installation requires its own JBoss instance. This instance can reside either on another
computer or on the same computer along side the JBoss instance for LiveCycle ES2.
➤ Install and configure Business Activity Monitoring ES2:
1. Perform a partial turnkey installation of BAM. See Installing and Deploying LiveCycle ES2 Using Turnkey.
2. Modify the BAM settings as follows:
●
Open a web browser and log in to LiveCycle Administration Console by typing
http://[hostname]:[port]/adminui.
●
Go to Services > LiveCycle Process Management ES2 > Server Settings > BAM Configuration
Settings.
●
Modify the following values as appropriate for your BAM server: BAM Host, BAM Port, LiveCycle
Server Host, and LiveCycle Server SOAP Port.
●
Change the User Name to CognosNowAdmin and click Save.
●
Restart the LiveCycle ES2 server.
➤ Disable and enable all Data Stream:
1. Open a web browser and log in to BAM Workbench by typing http://[hostname]:[BAM
port]/bam/workbench.
2. Click the Workbench tab > Public Folders, find Data Stream AdobeEvent and select AdobeEvent.
From the Activities list, click Disable and then on the popup dialog, click Disable Dependencies.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 (JBoss Turnkey)
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Next steps
32
3. Select AdobeEvent, and then from the Activities list, click Enable and and then on the popup dialog,
click Enable All.
4. Repeat steps 2 and 3 for all other Data Streams.
➤ Import the LiveCycle ES (8.x) Business Activity Monitoring ES2 metadata:
1. Locate the LiveCycle ES (8.x) Business Activity Monitoring ES2 metadata JAR file you exported prior to
performing the upgrade. See “Export and backup Business Activity Monitoring ES2 metadata” in the
Preparing to Upgrade to LiveCycle ES2 guide.
2. Go to Administration Console tab and click Import/Export.
3. Select Import metadata from a JAR file (upload), click Browse and navigate to your exported
metadata JAR file.
4. Select Import Mode > Do not overwrite and click OK.
Your LiveCycle ES (8.x) process data should now appear in LiveCycle ES2 Business Activity Monitoring ES2.
5. Some LiveCycle ES (8.x) objects have been deprecated in LiveCycle ES2. These objects will not be
displayed in BAM Workbench.
3.8 Next steps
If you used LiveCycle Configuration Manager to configure and deploy LiveCycle ES2, you can now
complete the post-deployment tasks. (See “Post-Deployment Activities” on page 33.)
4
Post-Deployment Activities
This section details post-installation tasks and describes how to get started using LiveCycle ES2 modules
and services after they are installed, configured, and deployed to your application server:
●
“Removing JMS from the JBoss server” on page 33
●
“Restarting the JBoss services” on page 34
●
“Disabling status pages for JBoss” on page 34
●
“Setting the correct date, time, and time zone” on page 34
●
“Manually enabling SSL for JBoss” on page 34
●
“Installing LiveCycle ES2.5 Solution Accelerators” on page 37 (Optional)
●
“Upgrading to Workbench ES2” on page 37
●
“Accessing module web applications” on page 38
●
“Accessing User Management” on page 40
●
“Encrypting the plaintext password” on page 41
●
“Managing the MySQL database” on page 41
●
“Resetting the Forms ES2 cache” on page 41
●
“Configuring LiveCycle ES2 to access LDAP” on page 41
●
“Considerations when upgrading from LiveCycle 7.x” on page 42
●
“Configuring HTML digital signature” on page 43
●
“Configuring PDF Generator ES2 or PDF Generator 3D ES2” on page 43
●
“Configuring LiveCycle ES2 Connectors for ECM” on page 51
●
“Configuring SharePoint client access” on page 56
●
“Enabling CIFS in IPv6 mode” on page 57
●
“Uninstalling LiveCycle ES post-upgrade” on page 58
●
“Deleting working files after upgrade” on page 58
●
“Performing a system image backup” on page 58
●
“Uninstalling LiveCycle ES2” on page 59
4.1 Removing JMS from the JBoss server
LiveCycle ES2 no longer uses JMS configurations to manage Java messaging. Once you have verified that
your LiveCycle ES2 works properly, you must remove all JMS configurations from your LiveCycle ES (8.x)
installation to avoid potential conflicts.
➤ Remove JMS from JBoss:
1. Locate [LiveCycle8x_root]\jboss\server\all\deploy\jms\adobe-service.xml and open it in an editor.
2. Remove all <mbean> properties from the <server> element.
33
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Restarting the JBoss services
34
3. Save and close the file.
4.2 Restarting the JBoss services
After completing the LiveCycle ES2 installation, restart the JBoss service to ensure that it is in a clean
running state. After an install, JBoss service will be in a high-memory-use initialization state.
4.3 Disabling status pages for JBoss
Due to a possible information disclosure issue, remove access to the JBoss status page by following these
steps for your version of the application server.
➤ To disable the status page for JBoss Application Server 4.2.1:
1. Locate [JBossES2 root]/server/lc_turnkey/deploy/ jbossweb.deployer/ROOT.war/WEB-INF, and open the
web.xml file in an editor.
2. Comment out the servlet and servlet-mapping tags as follows:
<!-- <servlet>
<servlet-name>Status Servlet</servlet-name>
<servlet-class>org.jboss.web.tomcat.service.StatusServlet
</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Status Servlet</servlet-name>
<url-pattern>/status</url-pattern>
</servlet-mapping> -->
3. Save and close the file.
4.4 Setting the correct date, time, and time zone
Setting the correct date, time, and time zone on all servers connected to your LiveCycle ES2 environment
will ensure that time-dependent modules, such as LiveCycle Digital Signatures ES2 and
LiveCycle Reader Extensions ES2, will function correctly. For example, if a signature appears to have been
created in the future, it will not validate.
Servers that require synchronization are database servers, LDAP servers, HTTP servers and J2EE servers.
4.5 Manually enabling SSL for JBoss
During Turnkey installation, the JBoss application server is set up with Secure Sockets Layer (SSL) disabled
by default. Enable SSL for JBoss if you want to use Rights Management with Adobe Acrobat for securing
documents. Enabling SSL requires a signed certificate issued by a trusted certificate authority (CA) like
VeriSign. However, you can also generate and use a self-signed certificate to enable SSL.
Following broad tasks are involved in enabling SSL for JBoss on a Turnkey installation:
1. Create a keystore using the keytool utility that ships with the Java SDK.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Enabling SSL for JBoss
35
2. Generate the certificate or use a certificate issued by a CA.
3. Copy the keystore and the certificate files to the JBoss root configuration folder—
C:\Adobe\Adobe LiveCycle ES2\jboss\server\lc_turnkey\conf.
4. Import the certificate into [Adobe_JAVA_HOME]\lib\security\cacerts.
5. Update the JBoss server.xml file to uncomment the SSL configuration settings and specify reference
attributes for the certificate.
6. Restart the JBoss server to apply your changes.
4.5.1 Enabling SSL for JBoss
You can configure SSL for JBoss using LiveCycle Configuration Manager. If you skipped this option, this
section describes how to manually configure SSL.
X.500 distinguished names are used as identifiers when you generate a keystore and a certificate. The
keytool command that you use to generate a certificate supports the following subparts for the –dname
option:
CN: The complete hostname of the machine for which you’re creating the certificate. For example,
“machine.adobe.com”.
OU: The name of a small organizational unit, such as a department or a division. For example,
“Purchase”.
O: The name of the organization. For example, “Adobe Systems”.
L: The name of a locality or city. For example, “San Jose”.
S: The name of a state or province. For example, “California”.
C: A two letter country code. For example, “US”.
➤ To enable SSL for JBoss on a Turnkey installation
1. Navigate to [Adobe_JAVA_HOME]/bin and type the following command to create the keystore:
keytool -genkey -dname "CN=Host Name, OU=Group Name, O=Company Name, L=City Name,
S=State, C=Country Code" -alias "LC Cert" –keyalg rsa -keypass key_password -keystore
keystorename.keystore
Replace [Adobe_JAVA_HOME] with the name of the directory where the JDK is installed, and replace the
text in bold with values that correspond to your environment. The Host Name is the fully qualified
domain name of the application server.
2. Enter the keystore_password when prompted for a password.
Note: The keystore_password entered at this step may be the same password (key_password) that you
entered in step 1, or may be different.
3. Copy the keystorename.keystore file to the [appserver root]\server\lc_turnkey\conf directory by typing
the following command:
copy keystorename.keystore [JBoss_ES2 root]/server/lc_turnkey/conf
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Enabling SSL for JBoss
4. Export the certificate file by typing the following command:
keytool -export -alias "LC Cert" -file LC_cert.cer -keystore [appserver
root]\server\lc_turnkey\conf\keystorename.keystore
5. Enter the keystore_password when prompted for a password.
6. Copy the LC_cert.cer file to the [appserver root] conf directory by typing the following command:
copy LC_cert.cer [appserver root]\server\lc_turnkey\conf
7. View the contents of the certificate by typing the following command:
keytool -printcert -v -file [appserver
root]\server\lc_turnkey\conf\LC_cert.cer
8. If necessary, provide write access to the cacerts file in [Adobe_JAVA_HOME]\lib\security. Right-click
the cacerts file, select Properties, and then deselect the Read-only attribute.
9. Import the certificate by typing the following command:
keytool -import -alias “LC Cert” -file LC_cert.cer -keystore
[Adobe_JAVA_HOME]\lib\security\cacerts
10. Type changeit as the password. changeit is the default password for a Java installation.
11. When prompted if you Trust this certificate? [no]:,type yes. The confirmation
"Certificate was added to keystore” is displayed.
12. In a text editor, open the file [JBossES2_root]\server\lc_turnkey\deploy\jboss-web.deployer\server.xml.
13. Uncomment the following lines in the server.xml file:
<!-- SSL/TLS Connector configuration using the admin devl guide keystore
<Connector port="8443" address="${jboss.bind.address}" maxThreads="100"
strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/keystoreFile.keystore"
keystorePass="keystorePass" sslProtocol = "TLS" />
-->
14. For the keystoreFile attribute in server.xml, specify the path of the keystore file you created. Specify
keystore_password for the keystorePass attribute in server.xml.
15. Save the server.xml file.
16. Restart the application server:
●
From the Windows Control Panel, click Administrative Tools, and then click Services.
●
Select JBoss for Adobe LiveCycle ES2.
●
Select Action > Stop.
●
Wait for the status of the service to appear as stopped.
●
Select Action > Start.
36
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Installing LiveCycle ES2.5 Solution Accelerators
37
4.6 Installing LiveCycle ES2.5 Solution Accelerators
*New for 9.5*
If you are planning to install LiveCycle ES2.5 Solution Accelerators, you are required to first apply LiveCycle
ES2 service pack 2 or later and install LiveCycle ES2.5 Solution Accelerators. However, note that you need
to rerun LiveCycle Configuration Manager after installing LiveCycle ES2.5 Solution Accelerators.
For more information about installing Solution Accelerators, see Installing and Deploying LiveCycle ES2.5
Solution Accelerators.
4.7 Upgrading to Workbench ES2
Once you have completed your LiveCycle ES2 server upgrade and verified that it is working properly, you
must install the new version of Workbench ES2 in order to continue creating and modifying your LiveCycle
ES2 applications. See Installing Your Development Environment.
4.8 Accessing LiveCycle Administration Console
LiveCycle Administration Console is the web-based portal for accessing various configuration pages,
where you set run-time properties that control the way LiveCycle ES2 operates. When you log in to
LiveCycle Administration Console, you can access User Management, watched folder, and e-mail client
configuration, as well as administrative configuration options for other services. Access Applications and
Services, which administrators use for deploying services to a production environment, from within
LiveCycle Administration Console.
The default user name and password for logging in to LiveCycle Administration Console is administrator
and password. After you log in the first time, you can access User Management and change the password
of the LiveCycle ES2 administrator account. (See “Accessing User Management” on page 40.) Use the same
administrator account and password configured on your LiveCycle ES (8.x) system.
Before you access LiveCycle Administration Console, LiveCycle ES2 must be deployed and running on your
application server.
For information about using the administration web pages, see LiveCycle Administration Console Help
(available from the Help menu of the LiveCycle Administration Console home page).
➤ To access LiveCycle Administration Console:
1. Open a web browser and enter this URL:
http://localhost:8080/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Login.
4. Click Services to access the services’ pages, and click Settings to access the Core System Settings, User
Management, and Trust Store Management pages.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Change default password
38
4.8.1 Change default password
LiveCycle ES2 creates one or more default users during the installation. The password for these users is in
the product documentation and is publicly available. You must change this default password, depending
on your security requirements.
The LiveCycle ES2 administrator user password is set to “password” by default. You must change it in
LiveCycle Administration Console > User Management.
4.9 Accessing module web applications
After LiveCycle ES2 is deployed, you can access the web applications that are associated with the following
modules:
●
LiveCycle Reader Extensions ES2
●
LiveCycle Workspace ES2
●
LiveCycle Rights Management ES2
●
LiveCycle Business Activity Monitoring ES2
●
LiveCycle Content Services ES2
For information about using Reader Extensions ES2, Workspace ES2, and Rights Management ES2, see the
Help that is available within each application.
Access the web applications using the default administrator permissions and create additional users and
roles so that others can log in and use the applications. (See User Management Help, which is also available
within LiveCycle Administration Console Help or the User Management page.)
4.9.1 Accessing Reader Extensions ES2
5. Open a web browser and enter this URL:
http://localhost:8080/ReaderExtensions (local deployment using the default port)
6. Log in using the default user name and password:
User name: administrator
Password: password
Note: You must have administrator or super user privileges to log in using the default user name and
password. To allow other users to access Reader Extensions ES2, you must create the user accounts
in User Management and grant the users the Reader Extensions Web Application role.
4.9.2 Accessing Workspace ES2
7. Open a web browser and enter this URL:
http://localhost:8080/workspace (local deployment using the default port)
8. Log in using the default user name and password:
User name: administrator
Password: password
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Accessing Rights Management ES2
39
4.9.3 Accessing Rights Management ES2
To log in to Rights Management ES2, you must be assigned the LiveCycle Rights Management End User
role.
All new and existing users, including the Super Administrator, are not granted the LiveCycle Rights
Management End User role by default. You must create a user account with the LiveCycle Rights
Management End User role in User Management, or grant the End User role to existing users. Then, log in
to Rights Management ES2 by using the login information that is associated with the user you create.
➤ To access the Rights Management ES2 web application:
1. Open a web browser and enter this URL:
http://localhost:8080/edc/Login.do (local deployment using the default port)
2. Log in using the default user name and password:
User name: Administrator or any user who has the Rights Management ES2 End User role
Password: Password for the user account entered above
Note: Restart the application server if you cannot log in as a user other than administrator.
For information about setting up users and roles and configuring SSL for Rights Management ES2, see
Administering LiveCycle ES2.
When a user adds a principal user to a policy entry in Rights Management ES2, no principal users are
visible by default, because the My Policies policy set does not include a domain. To add visible users and
groups, you can change the My Policies configuration in the Rights Management ES2 administration web
application to add a domain. All the users in the added domains are visible and can be added to a user
policy. (see Administering LiveCycle ES2).
4.9.4 Accessing Business Activity Monitoring ES2
1. Launch Internet Explorer and enter the appropriate URL:
●
http://localhost:8888/bam/login/dashboard.htm (local deployment using the default port)
●
http://localhost:8888/bam/login/workbench.htm (local deployment using the default port)
2. Log in using the default user name and password:
User name: CognosNowAdmin
Password: manager
➤ To populate BAM Dashboard:
Perform the following steps to synchronize LiveCycle ES2 process data into BAM.
1. Log into BAM Workbench.
2. Click the Workbench tab, and select Public Folders.
3. Locate Data Stream AdobeEvent and select AdobeEvent.
4. From the Activities list, click Disable and then on the popup dialog, click Disable Dependencies.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Accessing Content Services ES2
40
5. Select AdobeEvent, and then from the Activities list, click Enable and then on the popup dialog, click
Enable All.
6. Repeat steps 3 to 5 for all other Data Streams.
➤ To reset BAM recovery log directory for backup and restore BAM:
BAM recovery log directory is set to ../server/lc_turnkey/logs for JBoss by default. You can set a separate
directory used for BAM recovery log directory so that you won't loss data if you forget to backup the
DEFAULTRECOVERYLOGGER file during for restore.
1. Log into BAM Workbench.
2. On the Administration Console tab, click System Settings... .
3. In the Configure list, select Checkpoint Configuration.
4. Locate the Recovery Log Directory and make the required changes.
4.9.5 Accessing Content Services ES2
Note: Apply the LiveCycle Contentspace ES2 Administrator or LiveCycle Contentspace ES2 roles for a new
user to log in to this web application. To enable users to log in, create the users in User Management
and grant them the appropriate role.
5. Open a web browser and enter this URL:
●
http://localhost:8080/contentspace (local deployment using the default port)
6. Log in using the default user name and password:
User name: administrator
Password: password
4.10 Accessing User Management
User Management allows administrators to maintain a database of all users and groups. The database can
be synchronized with one or more third-party user directories to include users and groups from those
databases. User Management provides authentication, authorization, and user management for
LiveCycle ES2 modules, including Reader Extensions ES2, Workspace ES2, Rights Management ES2,
LiveCycle Process Management ES2, and LiveCycle Forms ES2.
➤ To access User Management:
1. Open a web browser and enter this URL:
http://localhost:8080/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
3. Click Settings > User Management.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Encrypting the plaintext password
41
Note: For information about configuring users with User Management, click User Management Help in
the upper-right corner of the User Management page.
4.11 Encrypting the plaintext password
To encrypt the plaintext password in the data source configuration, go to here: http://wiki.jboss.org and
search on EncryptingDataSourcePasswords.
4.12 Managing the MySQL database
The turnkey installation and configuration supports the transaction-safe storage engine (InnoDB) in
MySQL. This means that all document services must operate in the same storage engine and have
consistent version support. (See MySQL InnoDB Storage Engine.)
4.13 Resetting the Forms ES2 cache
After upgrading your LiveCycle ES (8.x) system that included Forms ES, it is recommended that you reset
the Forms ES2 cache to avoid any possible issues with form generation from migrated processes.
Access the Reset Cache button from LiveCycle Administration Console by clicking Services > LiveCycle
Forms ES2 > Forms Cache Control Settings.
4.14 Configuring LiveCycle ES2 to access LDAP
If you did not previously configure Lightweight Directory Access Protocol (LDAP), you can use the
following procedure as a guideline when configuring User Management to support authentication using
LDAP.
Note: Skip these steps if you configured LDAP for previous LiveCycle products. LDAP configurations are
migrated during the upgrade process.
➤ To configure User Management with LDAP:
1. Open a web browser, navigate to http://localhost:8080/adminui, and log in. (See “Accessing module
web applications” on page 38.)
2. Click Settings > User Management > Domain Management, and click New Enterprise Domain.
3. In the ID box, type a unique identifier for the domain.
4. In the Name box, type a descriptive name for the domain.
5. Click Add Authentication and, in the Authentication Provider list, select LDAP.
6. Click OK and, on the page that appears, click Add Directory.
7. In the Profile Name box, type a name, and then click Next.
8. Specify values in the Server, Port, SSL, and Binding boxes, as required.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Considerations when upgrading from LiveCycle 7.x
42
9. Under Populate Page With, select a directory settings option (for example, select Default Sun ONE
values), and then click Next.
10. Configure User Settings as required, and then click Next
11. Configure Group Settings as required, and then click either Test or Finish.
12. (Optional) Test your configuration:
●
Click Test.
●
In the Test Directory pane, in the Find box, enter an object name and, in the using box, select the
object’s type, such as Login ID.
●
Click Test. If successful, your object’s details are displayed. You can then click Back.
13. Click Finish to exit the Add Directory page, and then click OK again.
Note: Sync the LDAP server to ensure that the new settings take effect.
4.15 Considerations when upgrading from LiveCycle 7.x
When upgrading to LiveCycle ES2 Process Management from either LiveCycle 7.x or 8.x, several
email-related settings require manual configuration in order to restore proper function. Therefore, if you
have configured any of the following user preferences in Form Manager 7.x or Process Management 8.x,
you will need to set them manually as described here.
➤ Attach Forms in email:
The Attach Forms in email setting specifies whether a copy of a form is attached to email notification
messages, thus allowing the user to edit the form content (the task) and then submit it via email.
Note: Only PDF and XDP file attachments are supported.
To continue submitting tasks by email, each user must configure their preferences in Workspace ES2 as
follows:
1. Log in to the Workspace ES2 application by going to http://[host]:[port]/workspace.
2. Go to Preferences > Manage UI Settings.
3. Set the Attach Forms in Email value to Yes.
Due to changes in the way email tasks are managed in LiveCycle ES2, the LiveCycle Administrator user
must create a Complete Task email endpoint so that processes created in Form Manager 7.x that required
the user to complete a task using email can be completed.
➤ Complete Task email endpoint:
1. Log in to LiveCycle Administration Console by going to http://[host]:[port]/adminui.
2. Go to Services > Applications and Services > Service Management and click the Complete Task:
1.0 service.
3. On the Configure Complete Task screen, click the Endpoint tab, select Email from the list and then
click Add.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Configuring HTML digital signature
43
4. Configure the endpoint as required and then click Add.
5. If required, go to Services > Applications and Services > Endpoint Management, and enable the
new endpoint.
The Task Assignment and Reminder email settings are set back to the default values during the upgrade
process.
4.16 Configuring HTML digital signature
To use the HTML digital signature feature of Forms ES2, complete the following procedure.
➤ To enable HTML digital signature:
1. Manually deploy the [LivecycleES2 root]/deploy/adobe-forms-ds.ear file to your application server.
2. Log in to LiveCycle Administration Console and click Services > LiveCycle Forms ES2.
3. Select HTML Digital Signature Enabled and then click Save.
4.17 Configuring PDF Generator ES2 or PDF Generator 3D ES2
If you installed LiveCycle PDF Generator ES2 or LiveCycle PDF Generator 3D ES2 as part of your
LiveCycle ES2 solution, complete the following tasks:
●
“Setting environment variables” on page 43
●
“Configuring the application server to use HTTP proxy server” on page 44
●
“Setting the Adobe PDF Printer as the default printer” on page 45
●
“Configuring Acrobat Professional” on page 45
●
“Installing East Asian characters in Windows Server 2003” on page 46
●
“Setting PDF Generator ES2 or PDF Generator 3D ES2 watched folder performance parameters” on
page 46
●
“Configuring user accounts for multi-threaded file conversions” on page 46
●
“Adding fonts to PDF Generator ES2 or PDF Generator 3D ES2” on page 47
●
“Configuring HTML to PDF conversions” on page 48
●
“Modifying Microsoft Visio 2007 default macro settings” on page 49
4.17.1 Setting environment variables
If you installed PDF Generator ES2 or PDF Generator 3D ES2 and configured it to convert files to PDF, for
some file formats, you must manually set an environment variable that contains the absolute path of the
executable that is used to start the corresponding application. This table lists the native applications for
which PDF Generator ES2 or PDF Generator 3D ES2 requires you to set up environment variables.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Configuring the application server to use HTTP proxy server
Application
Environment variable Example
Acrobat 9.3
Acrobat_PATH
C:\Program
Files\Adobe\Acrobat 9.3\Acrobat\Acrobat.exe
Adobe
FrameMaker®
FrameMaker_PATH
C:\Program
Files\Adobe\FrameMaker7.1\FrameMaker.exe
Notepad
Notepad_PATH
C:\WINDOWS\Notepad.exe
OpenOffice.org
OpenOffice_PATH
C:\Program Files\OpenOffice.org 3.0
Adobe
PageMaker®
PageMaker_PATH
C:\Program
Files\Adobe\PageMaker 7.0\PageMaker.exe
WordPerfect
WordPerfect_PATH
C:\Program Files\WordPerfect Office
12\Programs\wpwin12.exe
44
Note: The OpenOffice_PATH environment variable is set to the installation folder instead of the path to
the executable.
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.
4.17.2 Configuring the application server to use HTTP proxy server
If the computer that LiveCycle ES2 is running on uses proxy settings to access external websites, the
application server should be started with the following values set as Java Virtual Machine (JVM™)
arguments:
-Dhttp.proxyHost=[server host]
-Dhttp.proxyPort=[server port]
➤ To add the setting to JBoss:
1. Ensure that the JBoss Application Server is stopped.
2. From command line, edit the run script in the [JBossES2 root]/bin/ directory:
●
(Windows) run.bat
3. Add the following text to the script file:
Set JAVA_OPTS=%JAVA_OPTS%
-Dhttp.proxyHost=[server host]
-Dhttp.proxyPort=[server port]
4. Save and close the file.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Setting the Adobe PDF Printer as the default printer
45
4.17.3 Setting the Adobe PDF Printer as the default printer
Set the Adobe PDF Printer to be the default printer on the server. If the Adobe PDF Printer is not set as the
default, PDF Generator ES2 or PDF Generator 3D ES2 cannot convert files successfully.
➤ To set the default printer:
1. Select Start > Printers and Faxes.
2. In the Printers and Faxes window, right-click Adobe PDF and select Set as Default Printer.
4.17.4 Configuring Acrobat Professional
This procedure can be completed after you run LiveCycle Configuration Manager and deploy
LiveCycle ES2 to the application server.
➤ To configure Acrobat Professional Extended for use with PDF Generator ES2 or
PDF Generator 3D ES2:
1. If an earlier version (8.1 or earlier) of Acrobat is installed, uninstall it by using Add or Remove Programs
in the Windows Control Panel.
2. Do one of the following:
●
If you are using the media, insert the Acrobat Professional Extended CD.
●
If you are using the ESD downloads, download Acrobat Professional Extended from your ESD
location.
3. Install Acrobat Professional Extended by running the AutoPlay.exe file.
4. Navigate to the additional\scripts folder on the LiveCycle ES2 installation media.
5. Run the following batch file:
Acrobat_for_PDFG_Configuration.bat [LiveCycleES2 root]/pdfg_config
6. Open Acrobat and select Help > Check for updates > Preferences.
7. Deselect Automatically check for Adobe updates.
➤ To validate the Acrobat Professional Extended installation:
1. Navigate to a PDF file on your system and double-click it to open it in Acrobat. If the PDF file opens
successfully, Acrobat Professional Extended is installed correctly.
2. If the PDF file does not open correctly, uninstall Acrobat and reinstall it.
Note: Ensure that you dismiss all the Acrobat dialog boxes that are displayed after the Acrobat installation
is completed and disable the automatic updates for Acrobat.
Set the Acrobat_PATH environment variable to point to Acrobat.exe (such as C:\Program Files\
Adobe\Acrobat 9.0\Acrobat\Acrobat.exe).
➤ To configure native application support:
1. Install and validate Acrobat as described in the previous procedure.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Installing East Asian characters in Windows Server 2003
46
2. Set Adobe PDF printer as the default printer.
3. (PDF Generator 3D ES2) Register the DLL file located at [LiveCycleES2 root]\plugins\x86_win32\
PDFG3dAddin.dll.
4.17.5 Installing East Asian characters in Windows Server 2003
When HTML files are converted to PDF by using PDF Generator ES2 or PDF Generator 3D ES2, some East
Asian languages, such as Japanese, Korean, and Chinese, and also right-to-left languages, such as Arabic,
Armenian, Georgian, Hebrew, Indic, Thai, and Vietnamese, may not be displayed in the PDF file.
To ensure that these languages are displayed in Windows Server 2003, appropriate fonts must be present
on the client and server.
➤ To install East Asian characters in Windows Server 2003:
1. Select Start > Control Panel and open Regional and Language Options.
2. Click the Languages tab and select Install Files for East Asian Languages.
3. Click the Advanced tab and select all the options under Code Page Conversion Tables.
If converted PDF files are still missing fonts, verify that the Arial Unicode MS (TrueType) font (ARIALUNI.TTF)
is present in the C:\WINDOWS\Fonts directory.
4.17.6 Setting PDF Generator ES2 or PDF Generator 3D ES2 watched folder
performance parameters
To avoid java.io.IOException error messages indicating that not enough disk space is available to
perform PDF conversions using a watched folder, you can modify the settings for PDF Generator ES2 or
PDF Generator 3D ES2 in LiveCycle Administration Console.
➤ To set performance parameters for PDF Generator ES2 or PDF Generator 3D ES2:
1. Log in to LiveCycle Administration Console and click Services > Application and Services > Service
Management, and click PDFGConfigService in the list of services.
2. On the Configure PDFGConfigService page, set the following values:
PDFG Cleanup Scan Seconds: 1800
Job Expiration Seconds: 6000
Server Conversion Timeout: 450
4.17.7 Configuring user accounts for multi-threaded file conversions
By default, PDF Generator ES2 can convert only one OpenOffice, Microsoft Word, or PowerPoint document
at a time. If you enable multi-threaded conversions, PDF Generator ES2 can convert more than one of the
documents concurrently by launching multiple instances of OpenOffice or PDFMaker (which is used to
perform the Word and PowerPoint conversions).
Note: Only Microsoft Word 2007 and Microsoft PowerPoint 2007 are supported with multi-threaded file
conversions. Microsoft Excel 2003 or 2007 versions are not supported.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Adding fonts to PDF Generator ES2 or PDF Generator 3D ES2
47
If you need to enable multi-threaded file conversion, you must first perform the tasks outlined in the
Enabling multi-threaded file conversions section of the Preparing to Install LiveCycle ES2 (Single Server) guide.
➤ Add a user account:
1. In LiveCycle Configuration Manager, click Services > LiveCycle PDF Generator ES2 > User Accounts.
2. Click Add and enter the user name and password of a user who has administrative privileges on the
LiveCycle ES2 server. If you are configuring users for OpenOffice, dismiss the initial OpenOffice
activation dialogs.
Note: If you are configuring users for OpenOffice, the number of instances of OpenOffice cannot be
greater than number of user accounts specified in this step.
3. Restart the LiveCycle ES2 server.
4.17.8 Adding fonts to PDF Generator ES2 or PDF Generator 3D ES2
LiveCycle ES2 provides a central repository of fonts named Adobe LiveCycle ES2 Fonts Management, which
is accessible to all LiveCycle ES2 modules. Make the extra fonts available to non-LiveCycle ES2 applications
on the server so that PDF Generator can use these fonts to create PDF documents that are created with
these applications.
4.17.8.1 Non-LiveCycle applications
The following list contains non-LiveCycle ES2 applications that PDF Generator ES2 or
PDF Generator 3D ES2 can use for PDF generation on the server side:
Windows-only Applications
●
Microsoft Office Word
●
Microsoft Office Excel
●
Microsoft Office PowerPoint
●
Microsoft Office Project
●
Microsoft Office Visio
●
Microsoft Office Publisher
●
AutoDesk AutoCAD
●
Corel WordPerfect
●
Adobe Photoshop CS
●
Adobe FrameMaker
●
Adobe PageMaker
●
Adobe Acrobat Professional Extended
Multiplatform applications
●
OpenOffice Writer
●
OpenOffice Calc
●
OpenOffice Draw
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
●
Post-Deployment Activities
Configuring HTML to PDF conversions
48
OpenOffice Impress
Note: In addition to these applications, your list may include additional applications that you added.
Of the above applications, the OpenOffice Suite (which includes Writer, Calc, Draw, and Impress) is
available on Windows, Solaris™, and Linux® platforms, whereas other applications are available on
Windows only.
4.17.8.2 Adding new fonts to Windows applications only
All the Windows-only applications that are mentioned above can access all the fonts that are available in
the C:\Windows\Fonts (or equivalent) folder. In addition to C:\Windows\Fonts, each of these applications
may have its own private fonts folders.
Therefore, if you plan to add any custom fonts to the LiveCycle ES2 fonts repository, ensure that the same
fonts are available to the Windows-only applications also by copying these fonts to either
C:\Windows\Fonts or to an equivalent folder.
Your custom fonts must be licensed under an agreement that allows you to use them with the applications
that have access to these fonts.
4.17.8.3 Adding new fonts to OpenOffice Suite
Adding custom fonts to OpenOffice Suite is explained on the OpenOffice Fonts-FAQ page at
http://wiki.services.openoffice.org.
In addition, OpenOffice Suite has these resources about the fonts-related behavior:
●
OpenOffice Fonts Troubleshooting Guide at http://www.openoffice.org/FAQs/fontguide.html. Some of the
text in this guide is applicable only to OpenOffice 1.x and therefore may be obsolete for OpenOffice 3.x
and above.
●
Importing Fonts into OpenOffice 2.1 at http://openoffice.blogs.com/openoffice/2007/02/
font_import_wiz.html. Even though this blog mentions OpenOffice 2.1, the instructions that are
mentioned should be applicable to OpenOffice 2.2 and later.
4.17.8.4 Adding new fonts to other applications
If you added support for PDF creation in other applications, see the Help for these applications to add new
fonts. In Windows, copying your custom fonts to the C:\Windows\Fonts (or equivalent) folder should be
sufficient.
4.17.9 Configuring HTML to PDF conversions
The HTML-to-PDF conversion process is designed to use the settings from Acrobat 9 that override the
settings from LiveCycle PDF Generator ES2.
Note: This configuration is required to enable the HTML-to-PDF conversion process, otherwise this
conversion type will fail.
➤ To configure the HTML-to-PDF conversion:
1. Install and validate Acrobat as described in “Configuring Acrobat Professional” on page 45.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Modifying Microsoft Visio 2007 default macro settings
49
2. Locate the pdfgen.api file in the [LiveCycleES2 root]\plugins\x86_win32 directory and copy it to
[Acrobat root]\Acrobat\plug_ins directory.
4.17.9.1 Enabling support for Unicode fonts in HTML to PDF conversions
Caution: The HTML-to-PDF conversion fails if a zipped input file contains HTML files with double-byte
characters in filenames. To avoid this problem, do not use double-byte characters when naming
HTML files.
1. Copy the Unicode font to any of the following directories as appropriate for your system:
●
[Windows root]\windows\fonts
●
[Windows root]\winnt\fonts
2. Modify the font-name mapping in the cffont.properties file located in the
[LiveCycleES2 root]/adobe-generatepdf-dsc.jar file:
●
Extract this archive, and locate the cffont.properties file and open it in an editor.
●
In the comma-separated list of Java font names, add a map to your Unicode system font for each
font type. In the example below, kochi mincho is the name of your Unicode system font.
dialog=Arial, Helvetica, kochi mincho
dialog.bold=Arial Bold, Helvetica-Bold, kochi mincho ...
●
Save and close the properties file, and then repackage and redeploy the adobe-generatepdf-dsc.jar
file.
Note: On a Japanese operating system, specify the font mapping in the cffont.properties.ja file as well,
which takes precedence over the standard cffont.properties file.
Tip: Fonts in the list are searched from left to right, using the first font found. HTML-to-PDF conversion
logs return a list of all the font names that are found in the system. To determine the font name you
need to map, add the font to one of the directories above, restart the server, and run a conversion.
You can determine from the log files the font name to use for mapping.
To embed the font in the generated PDF files, set the embedFonts property in the cffont.properties file to
true (the default is false).
4.17.10 Modifying Microsoft Visio 2007 default macro settings
When a Microsoft Visio 2007 file containing macros is submitted for conversion, the resultant Microsoft
Office Visio Security Notice dialog causes the conversion to time out. To successfully convert files that
contain macros, the default macro settings in Visio must be changed.
➤ Change the default Visio 2007 macro settings:
●
In Visio 2007, click Tools > Trust Center > Macro Settings and select either of the following options
and then click OK:
●
Disable all macros without notification
●
Enable all macros
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Installing the PDF Generator ES2 Network Printer client
50
4.17.11 Installing the PDF Generator ES2 Network Printer client
PDF Generator ES2 includes an executable file to install the PDF Generator ES2 network printer on a client
computer. After the installation is complete, a PDF Generator ES2 printer is added to the list of existing
printers on the client computer. This printer can then be used to send documents for conversion to PDF.
Note: The PDF Generator ES2 Network Printer Client (wizard) is supported on 32-bit Windows platforms
only.
If the PDFG Network Printer fails to install on Windows, use the operating system’s native Add Printer utility
and configure it as described in “To configure PDFG Network Printer on Windows using the native Add
Printer wizard:” on page 50.
➤ To install the PDF Generator ES2 Network Printer Client:
1. Ensure that you successfully installed PDF Generator ES2 on your server.
2. From a Windows client computer, enter the following URL in your web browser, where [server] is the
name of the server where you installed PDF Generator ES2 and [port] is the application server port
used:
http://[server]:[port]/pdfg-ipp/install
3. On the Configure Internet Port screen, select Use the specified user account and provide the
credentials of a LiveCycle user who has the PDFG Administrator/User role. This user must also have an
email address that can be used to receive the converted files. To have this security setting apply to all
users on the client computer, select Use the same security options for all users, and then click OK.
Upon successful installation, a dialog box appears, indicating that “The Printer Adobe LiveCycle
PDF Generator ES2 has been successfully installed.”
4. Click OK. You will now have a printer named Adobe LiveCycle PDF Generator ES2 in your list of available
printers.
➤ To configure PDFG Network Printer on Windows using the native Add Printer wizard:
1. Click Start > Printers and Faxes and double-click Add Printer.
2. Click Next, select A network printer, or a printer attached to another computer, and then click
Next.
3. Select Connect to a printer on the internet or on a home or office network and type the following
URL for the PDFG printer, where [server] is the server name and [port] is the port number where
the server is running:
http://[server]:[port]/pdfg-ipp/printer
4. On the Configure Internet Port screen, select Use the specified user account and provide valid
User Management credentials.
5. In the Printer Driver Select box, choose any standard PostScript-based printer driver (for example, HP
Color LaserJet PS).
6. Complete the installation by choosing appropriate options (for example, setting this printer as default).
Note: The user credentials used while adding the printer must have a valid email ID configured in
User Management to receive the response.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Configuring LiveCycle ES2 Connectors for ECM
51
7. Configure the email service’s sendmail service. Provide a valid SMTP server and authentication
information in the service’s configuration options.
➤ To install and configure the PDF Generator ES2 Network Printer Client using Proxy server port
forwarding
1. Configure port forwarding on the CC Proxy server on a particular port to the LiveCycle ES2 server, and
disable the authentication at proxy server level (since LiveCycle ES2 uses its own authentication). If a
client connects to this Proxy server on the forwarded port, then all the requests will be forwarded to
the LiveCycle ES2 server.
2. Install PDFG Network Printer using the following URL:
http://[proxy server]:[forwarded port]/pdfg-ipp/install.
3. Provide the necessary credentials for authentication of the PDFG Network Printer.
4. The PDFG Network Printer will be installed on the client machine which you can use for PDF conversion
using the firewall protected LiveCycle ES2 server.
4.18 Configuring LiveCycle ES2 Connectors for ECM
If you are installing any of the supported ECM connectors (IBM FileNet, EMC Documentum, or IBM Content
Manager), there are manual tasks you must perform to complete the LiveCycle ES2 configuration. See the
appropriate sections of the “Post-Deployment Activities” chapter in Installing and Deploying LiveCycle ES2
for JBoss.
If you installed the Connector for IBM FileNet service as part of your LiveCycle ES2 solution, you must
configure the service to connect to the FileNet object store.
➤ To configure the connector using FileNet 4.x or FileNet 5.0 and CEWS transport:
1. Open the application server run file in a text editor. The run file is as follows:
●
(Windows) [appserver root]/bin/run.bat
●
(UNIX) [appserver root]/bin/run.sh
2. Add the location of the FileNet Configuration files as a Java option to the application server start
command, and then save the file.
Note: If JBoss is running as a service, add the Java option in the registry where other JVM arguments
are defined.
-Dwasp.location= <configuration files location>
For example, using a default FileNet Application Engine installation on a Windows operating system,
add this Java option:
-Dwasp.location=C:/Progra~1/FileNet/AE/CE_API/wsi
3. If your deployment uses the Process Engine Connector service, copy the file
[appserver root]\client\logkit.jar to the following directory:
●
(Manually-configured JBoss) [appserver root]/server/all/lib
●
(Adobe-preconfigured JBoss) [appserver root]/server/lc_<db-name>/lib
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Configuring LiveCycle ES2 Connectors for ECM
52
4. Locate the adobe-component-ext.properties file in the [appserver root]/bin folder (if the file does not
exist, create it).
5. Add a new system property that provides the location of these FileNet Application Engine JAR files:
●
javaapi.jar
●
soap.jar
●
wasp.jar
●
builtin_serialization.jar (FileNet 4.0 only)
●
wsdl_api.jar
●
jaxm.jar
●
jaxrpc.jar
●
saaj.jar
●
jetty.jar
●
runner.jar
●
p8cjares.jar
●
Jace.jar
●
(optional) pe.jar
Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service.
The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
Note: Do not overwrite the existing contents of the properties file. Simply append the new system
property to the contents.
For example, using a default FileNet Application Engine installation on a Windows operating system,
add the following system property on a new line with no line breaks and end the line with a carriage
return:
Note: The following text contains formatting characters for line breaks. If you copy this text to a
location outside this document, remove the formatting characters when you paste it to the new
location.
Note: For FileNet 4.x, add following .jar files
com.adobe.livecycle.ConnectorforIBMFileNet.ext=
C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar,
C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/soap.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/wasp.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/wsdl_api.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxm.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxrpc.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/saaj.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/jetty.jar,
C:/Program Files/FileNet/AE/CE_API/wsi/lib/runner.jar,
C:/Program Files/FileNet/AE/CE_API/lib2/p8cjares.jar,
C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar,
C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Configuring LiveCycle ES2 Connectors for ECM
53
Note: Add C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar only if your
deployment uses the IBMFileNetProcessEngineConnector service.
Note: For FileNet 4.5, remove the line C:/Program
Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar,
Note: For FileNet 5.0, add following .jar files
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
C:/Program
Files/FileNet/AE/CE_API/lib/Jace.jar,
Files/FileNet/AE/CE_API/lib2/javaapi.jar,
Files/FileNet/AE/CE_API/lib2/log4j.jar,
Files/FileNet/AE/Router/lib/mailapi.jar,
Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar
Files/FileNet/AE/CE_API/lib/stax-api.jar,
Files/FileNet/AE/CE_API/lib/xlxpScanner.jar
Files/FileNet/AE/CE_API/lib/xlxpScannerUtils.jar
Files/FileNet/AE/Router/java/jre/lib/xml.jar
6. (FileNet Process Engine Connector only) Configure the connection properties for the process engine as
follows:
●
Using a text editor, create a file with the following content as a single line and end the line with a
carriage return:
RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/
wsi/FNCEWS40DIME/
●
Save the file as WcmApiConfig.properties in a separate folder, and add the location of the folder that
contains the WcmApiConfig.properties file to the adobe-component-ext.properties file.
For example, if you save the file as c:/pe_config/WcmApiConfig.properties, add the path
c:/pe_config to the adobe-component-ext.properties file.
Note: The filename is case-sensitive.
7. Locate the login-config.xml file in the following folder and add the following application policy as a
child of the <policy> node:
●
(Manually-configured JBoss) [appserver root]/server/all/conf
●
(Adobe-preconfigured JBoss) [appserver root]/server/lc_<db-name>/conf
<application-policy name = "FileNetP8WSI">
<authentication>
<login-module code = "com.filenet.api.util.WSILoginModule" flag =
"required" />
</authentication>
</application-policy>
8. (FileNet Process Engine Connector only) If your deployment uses the process engine, add the following
node to the login-config file:
<application-policy name = "FileNetP8">
<authentication>
<login-module code = "com.filenet.api.util.WSILoginModule" flag =
"required" />
</authentication>
</application-policy>
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Configuring LiveCycle ES2 Connectors for ECM
54
9. If the application server is not currently running, start the server. Otherwise, stop and then restart the
server.
10. If JBoss runs as as service, start (or restart) the JBoss for Adobe LiveCycle ES2 service.
11. Open a web browser and enter this URL:
http://[host]:[port]/adminui
12. Log in using the default user name and password:
User name: administrator
Password: password
13. Click Services > LiveCycle ES2 Connector for IBM FileNet.
14. Provide all of the required FileNet repository information and, under Repository Service Provider
Information, select IBM FileNet Repository Provider.
If your deployment uses the optional process engine service, under Process Engine Settings, select Use
Process Engine Connector Service and specify the process engine settings. For more information,
click the Help link in the upper-right corner of the page.
Note: The credentials that you provide in this step are validated later when you start the IBM FileNet
repository services. If the credentials are not valid, an error is thrown and the services will not
start.
15. Click Save and navigate to Services > Applications and Services > Service Management.
16. Select the check box next to IBMFileNetProcessEngineConnector (if configured) and then click Start.
17. Do one of the following tasks:
●
To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a
FileNet object store in the Resources view of Workbench ES2, continue with this procedure. Using
the FileNet Authorization service overrides the default LiveCycle ES2 authorization and must be
configured to log in to Workbench ES2 by using FileNet credentials.
●
To use the LiveCycle ES2 repository, log in to Workbench ES2 by using the LiveCycle ES2 super
administrator credentials (by default, Administrator and password). The credentials provided in step
14 use the default LiveCycle ES2 authorization service for accessing the default repository in this
case.
18. Enable the Remoting and EJB endpoints by doing these tasks:
●
Log in to LiveCycle Administration Console and click Home > Services > Application and Services
> Service Management.
●
Filter the category Connector for IBM FileNet and click
IBMFileNetContentRepositoryConnector:1.0.
●
Select the disabled endpoints and enable them.
19. Restart your application server.
20. Log in to LiveCycle Administration Console and click Settings > User Management > Domain
Management.
21. Click New Enterprise Domain and then type a domain ID and name. The domain ID is the unique
identifier for the domain. The name is a descriptive name for the domain.
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Configuring LiveCycle ES2 Connectors for ECM
55
22. Add a custom authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select Custom.
●
Select IBMFileNetAuthProviderService and then click OK.
23. Add an LDAP authentication provider:
●
Click Add Authentication.
●
In the Authentication Provider list, select LDAP and then click OK.
24. Add an LDAP directory:
●
Click Add Directory and, in the Profile Name box, type a unique name, and then click Next.
●
Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select
User for the Binding option, you must also specify values for the Name and Password fields.
●
(Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,
click Next.
●
Configure the user settings, click Next, configure group settings as required, and then click Next.
For details about the settings, click Help link in the upper-right corner of the page.
25. Click OK to exit the Add Directory page, and then click OK again.
26. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups
in your LDAP network and the speed on your connection, the synchronization process may take several
minutes.
(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current
Sync State column.
27. Navigate to Settings > User Management > Users and Groups.
28. Search for users that were synchronized from LDAP and perform these tasks:
●
Select one or more users and click Assign Role.
●
Select one or more LiveCycle ES2 roles and click OK.
●
Click OK a second time to confirm the role assignment.
Repeat this step for all users you want to assign roles to. For more information, click the Help link in the
upper-right corner of the page.
29. Start Workbench ES2 and log in using the following credentials for the IBM FileNet repository:
User name: [username]@[repository_name]
Password: [password]
The FileNet object store should now be visible in the Resources view within Workbench ES2. If you do
not log in using the [email protected] name, Workbench ES2 attempts to log in to the default
repository specified in step 14.
30. (Optional) If you intend to install the LiveCycle ES2 Samples for Connector for IBM FileNet, create a
FileNet object store named Samples and install the samples in that object store.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Configuring SharePoint client access
56
After you configure your Connector for IBM FileNet service, it is recommended that you see LiveCycle ES2
Administration Help. for information about configuring Workbench ES2 functions properly with your
FileNet repository.
4.19 Configuring SharePoint client access
You can configure Microsoft SharePoint clients to access content services from LiveCycle ES2. For this, you
should add the SharePoint Alfresco Module Package using LiveCycle Configuration Manager. The
SharePoint AMP file (adobe-vti-module.amp) is available in
[LiveCycleES2 root]\LiveCycle_ES_SDK\misc\ContentServices folder.
After you add the SharePoint AMP, perform the following steps:
4.19.1 Obtain and edit the share.war file
Alfresco CMS uses the file share.war to connect with Content Services ES2. You should modify the
share.war file to enable SharePoint clients to access Content Services ES2.
1. Obtain the share.war from the Alfresco installation. See your Alfresco documentation for more details.
2. Copy the file share.war to a directory in your file system.
3. Use a file archive utility such as WinRar to open the share.war file.
4. From the file archive utility window, extract the file
WEB-INF/classes/alfresco/webscript-framework-config.xml and open it using a text
editor.
5. Locate the line <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
and change it to
<endpoint-url>http://localhost:8080/contentspace/s</endpoint-url>
6. Save and close the file.
4.19.2 Deploy the share.war file
1. Open the archive file adobe-contentservices.ear using an archive utility such as WinRar from
the [JBossES2 root]/server/lc_turnkey/deploy/ directory.
2. Add the updated share.war file to the adobe-contentservices.ear archive that is opened in the archive
utility window.
3. From the file archive utility window, extract the file application.xml to a folder in the local file
system, and open it using a text editor. This file is in the adobe-contentservices.ear\META-INF
directory.
4. Add the following lines under the <application > tag:
<module id="Share">
<web>
<web-uri>share.war</web-uri>
<context-root>/share</context-root>
</web>
Adobe LiveCycle ES2
Post-Deployment Activities
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Enabling CIFS in IPv6 mode
57
</module>
5. Copy the updated application.xml file back to the adobe-contentservices.ear archive.
6. Save and close the archive.
7. Deploy the updated EAR file by copying the updated EAR file to the
[JBossES2 root]/server/lc_turnkey/deploy/ directory.
4.20 Enabling CIFS in IPv6 mode
If you want to enable CIFS for Content Services ES2 on an IPv6 implementation, you must explicitly add an
additional IPv6 address to the machine that hosts LiveCycle ES2. This IPv6 address should be a static IP
address that resides in the same subnet as the clients. You need to do the following tasks after you
configure LiveCycle ES2 using LiveCycle Configuration Manager. Typically, you should pause the LiveCycle
Configuration Manager after the EAR file configuration and then edit the EAR file. After you have edited
the EAR file, you can go back to the LiveCycle Configuration Manager to deploy the updated EAR file along
with other selected EAR files.
4.20.1 Edit the contentservices.war file
1. Navigate to [LiveCycleES2 root]\configurationManager\export directory.
2. Use a file archive utility such as WinRar to open the contentservices.war file.
3. From the file archive utility window, extract the file
contentservices.war\WEB-INF\classes\alfresco\file-services-custom.xml and
open it using a text editor.
4. Locate the following line and change it by adding ipv6=”enabled”:
<tcpipSMB platforms="linux,solaris,macosx,windows,AIX"/>
to
<tcpipSMB platforms="linux,solaris,macosx,windows,AIX" ipv6="enabled"/>
5. Save and close the file
6. From the file archive utility window, extract the file
contentservices.war\WEB-INF\classes\alfresco\extension\file-servers-proper
ties into a folder in the local file system, and open it using a text editor.
7. Locate the line cifs.ipv6=disabled and replace it with cifs.ipv6=enabled.
8. Save and close the file.
9. Copy the updated file-servers-custom.xml file into the archive under
contentservices.war\WEB-INF\classes\alfresco\extension\.
10. Save the contentservices.war file.
After you update the EAR files, you should use the LiveCycle Configuration Manager to deploy the updated
EAR file.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Uninstalling LiveCycle ES post-upgrade
58
4.21 Uninstalling LiveCycle ES post-upgrade
After you have upgraded your LiveCycle ES (8.x) environment to LiveCycle ES2 and have verified that the
new system is working properly, you can remove your LiveCycle ES (8.x) product files.
Caution: When uninstalling your LiveCycle ES2 product files, do not select the MySQL option during the
uninstall process because this database is used by your new LiveCycle ES2 installation. Deleting
the database will cause serious failure.
The uninstallation program does not remove Acrobat, which you may have installed with
PDF Generator ES. You must use Acrobat’s uninstallation program.
➤ Remove the product files:
1. Select Start > Control Panel > Add or Remove Programs, click [LiveCycle ES (8.x)] and click
Remove.
2. Select JBoss to remove this component along with the LiveCycle ES components.
3. Follow the on-screen instructions and then click Finish.
4. Restart your computer.
Note: You can also uninstall LiveCycle ES (8.x) from [LiveCycleES_root]\_uninst\server.
4.22 Deleting working files after upgrade
During upgrade, information is extracted from the LiveCycle ES (8.x) database and written to working files,
from which the information is then migrated into the LiveCycle ES2 database. The files remain in the
[LiveCycleES2 root]/configurationManager/working/upgrade directory after the data migration is
complete.
When the upgrade is complete, most of these files are not needed, and some of this data may contain
sensitive information, such as passwords and document encryption keys, depending on the LiveCycle
solution components upgraded. To save disk space and to maintain the security of your system, delete
most of the files in this directory after you verify that the upgrade is complete (essential and non-essential
data is migrated) and LiveCycle ES2 is working as expected.
Navigate to the [LiveCycleES2 root]/configurationManager/working/upgrade directory, and delete all the
files except for the sharedData file.
4.23 Performing a system image backup
After LiveCycle ES2 is installed and deployed into production areas and before the system is live, it is
recommended that you perform a system image backup on servers to which LiveCycle ES2 is
implemented. The LiveCycle ES2 database, GDS directory, and application servers must be part of this
backup. This is a complete system backup that you can use to restore the contents of your computer if
your hard drive or entire computer stops working. See the “LiveCycle ES2 Backup and Recovery” topic in
LiveCycle ES2 Administration Help.
Adobe LiveCycle ES2
Upgrading to LiveCycle ES2 from 8.x (for JBoss Turnkey)
Post-Deployment Activities
Uninstalling LiveCycle ES2
59
4.24 Uninstalling LiveCycle ES2
The LiveCycle ES2 uninstaller allows you to selectively remove JBoss, MySQL or LiveCycle ES2 components
if you have a turnkey installation. Before removing MySQL, back up any data you want to keep.
➤ To remove the product files:
1. Select Start > Control Panel > Add or Remove Programs, click LiveCycle ES2 and click Remove.
2. Select JBoss and MySQL to remove these components along with the LiveCycle ES2 components.
3. Follow the on-screen instructions and then click Finish.
4. Restart your computer if prompted to do so.
Note: If you choose to retain JBoss/MySQL while uninstalling LiveCycle ES2, you can remove these
applications later using the Add or Remove Programs utility in Microsoft Windows. Attempts to
remove JBoss/MySQL may fail if a JDK is not installed on the server.
5
Advanced Configuration Activities
This section describes advanced post-installation tasks that you may require for your LiveCycle ES2
environment. The following topics are discussed:
●
“Enabling Federal Information Processing Standard (FIPS)”
●
“Enabling AES-256 encryption”
5.1 Enabling Federal Information Processing Standard (FIPS)
LiveCycle ES2 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.
If you did not enable this option by using LiveCycle Configuration Manager during LiveCycle ES2
configuration or if you enable it but want to turn it off, you can change this setting through LiveCycle
Administration Console.
Modifying FIPS mode requires you to restart the server.
FIPS mode does not support Acrobat versions earlier than 7.0. If FIPS mode is enabled and the Encrypt
With Password and Remove Password processes include the Acrobat 5 setting, the process fails.
In general, when FIPS is enabled, the Assembler service does not apply password encryption to any
document. If this is attempted, a FIPSModeException is thrown, indicating that “Password encryption
is not permitted in FIPS mode.” Additionally, the PDFsFromBookmarks element is not supported in FIPS
mode when the base document is password-encrypted.
➤ To turn FIPS mode on or off:
1. Log in to LiveCycle Administration Console.
2. Click Settings > Core System Settings > Configurations.
3. Select Enable FIPS to enable FIPS mode or deselect it to disable FIPS mode.
4. Click OK and restart the application server.
Note: LiveCycle ES2 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).
5.2 Enabling AES-256 encryption
To use AES 256 encryption for PDF files, obtain and install the Java Cryptography Extension (JCE) Unlimited
Strength Jurisdiction Policy files. These files replace the local_policy.jar and US_export_policy.jar files in
the [JAVE_HOME]/lib/security folder. For example, if you are using Sun JDK 1.6, copy the downloaded files
to the [LiveCycleES2 root]/Java/jdk1.6.0_14/lib/security folder.
You can download these files from Java SE Downloads.
60
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