Installing your Development Environment

Installing your Development Environment
bc
Installing Your Development
Environment
Adobe® LiveCycle® ES2.5
September 24, 2010
Version 9.5
© 2010 Adobe Systems Incorporated and its licensors. All rights reserved.
Installing Your Development Environment
September 24, 2010
This installation 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, Adobe Reader, Acrobat, Flash, Flex, and LiveCycle 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. JBoss is a registered trademark of Red Hat, Inc. in the United States and other countries. Microsoft, Windows,
and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Intel and Pentium are trademarks or registered trademark of Intel Corporation or its subsidiaries in the U.S. and other countries. Oracle, Sun
and Java are trademarks or registered trademarks of Oracle and/or its affiliates. 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.................................................................................................................. 4
Who should read this document? ............................................................................................................................................ 4
Additional information................................................................................................................................................................. 4
1
Before You Install ........................................................................................................................ 5
Workbench installation overview............................................................................................................................................. 5
System prerequisites..................................................................................................................................................................... 6
Minimum hardware and software requirements ......................................................................................................... 6
Supported platforms .............................................................................................................................................................. 7
Upgrade considerations .............................................................................................................................................................. 7
Designer 9 installation considerations ................................................................................................................................... 8
2
Installing LiveCycle Workbench ................................................................................................. 9
Installing and running Workbench .......................................................................................................................................... 9
Enabling LiveCycle 7.x processes for your application server......................................................................................10
About LiveCycle 7.x support files .....................................................................................................................................10
Configuring Workbench for JBoss 4.2.x .........................................................................................................................11
Configure the startup parameters.............................................................................................................................11
Configuring Workbench for WebLogic Server 10 ......................................................................................................11
Generate the WebLogic full client JAR file .............................................................................................................11
Configure Workbench startup parameters ............................................................................................................11
Configuring Workbench for WebSphere Application Server 6.1..........................................................................12
Install the Application Client for WebSphere 6.1 .................................................................................................12
Install the application client EJB support plugins................................................................................................12
Configure the Workbench startup parameters.....................................................................................................12
Configuring Workbench for WebSphere Application Server 7 .............................................................................13
Install the Application Client for WebSphere 7.....................................................................................................13
Install the application client EJB support plugins................................................................................................13
Configure the Workbench startup parameters.....................................................................................................13
Installing LiveCycle 7.x QPACs.................................................................................................................................................14
Upgrading processes ..................................................................................................................................................................14
Installing the Workbench Eclipse feature............................................................................................................................15
Configuring Eclipse update feature for Workbench .................................................................................................16
Configuring and logging in to a server ................................................................................................................................17
Configuring time-out settings.................................................................................................................................................17
Configuring Workbench to connect over HTTPS..............................................................................................................17
Configuring cache settings for dynamically generated templates............................................................................19
Uninstalling Workbench ............................................................................................................................................................20
3
Configuring LiveCycle ES2 XDC Editor..................................................................................... 21
3
About This Document
This document provides instructions for installing and configuring Adobe® LiveCycle® Workbench 9.5. The
installation program also installs Adobe® LiveCycle® Designer 9.
Who should read this document?
This document is intended for administrators or developers who are responsible for installing, configuring,
administering, or deploying Workbench. Also included is information needed to configure your system to
support your upgraded LiveCycle 7.x or LiveCycle ES (8.x) processes. The information provided is based on
the assumption that anyone reading this document is familiar with Microsoft® Windows® operating
systems.
Additional information
The resources in this table can help you learn more about and get started using Adobe LiveCycle
Enterprise Suite 2.5 (ES2.5).
For information about
See
Procedural information for Workbench 9
LiveCycle Workbench 9 Help
Procedural information for Workbench 9.5
LiveCycle Workbench 9.5 Help
General information about LiveCycle ES2.5 and
how it integrates with other Adobe products
LiveCycle ES2.5 Overview
What’s new in LiveCycle ES2.5
What’s New for LiveCycle ES2.5
LiveCycle ES2.5 terminology
LiveCycle ES2.5 Glossary
A tutorial for creating a LiveCycle ES2.5
application and testing it in Workspace ES2
Creating Your First LiveCycle ES2.5 Application
All the documentation available for
LiveCycle ES2.5
Adobe LiveCycle ES2.5 documentation
LiveCycle ES2.5 release information and
last-minute changes that occur to the product
LiveCycle ES2.5 Release Notes
Other services and products that integrate with
LiveCycle ES2.5
www.adobe.com
Patch updates, technical notes, and additional
information on this product version
LiveCycle Technical Support
4
1
Before You Install
Workbench is an integrated development environment (IDE) that developers and form authors use to
create automated business processes and forms. It is also used to manage the resources and services that
the processes and forms use.
1.1 Workbench installation overview
The following illustration depicts the LiveCycle Workbench installation including:
●
Process Design using Workbench
●
Form Design using Designer
Note: The LiveCycle ES2.5 server requires a separate installation program. For more information refer to
the Preparing to Install LiveCycle ES2 (Single Server) document.
5
Adobe LiveCycle ES2.5
Before You Install
Installing Your Development Environment
System prerequisites
6
1.2 System prerequisites
This section outlines the hardware and software requirements and supported platforms.
1.2.1 Minimum hardware and software requirements
Workbench
The following requirements are recommended as the minimum:
●
Disk space for installation:
1.5 GB for Workbench only
1.7 GB on a single drive for a full installation of Workbench, Designer, and the samples assembly
400 MB for temporary install directories - 200 MB in the user \temp directory and 200 MB in the
Windows temporary directory
Note: If all of these locations reside on a single drive, there must be 1.5 GB of space available during
installation. The files copied to the temporary directories are deleted when installation is
complete.
●
RAM for running Workbench: 2 GB
●
Hardware requirement: Intel® Pentium® 4 or AMD equivalent, 1 GHz processor.
●
Download and install the latest version of Adobe AIR (from http://www.adobe.com) required for
Community Help Client, integrated with LiveCycle Workbench 9.5. *New for 9.5*
●
Java™ Runtime Environment (JRE) 6.0 update 21 or later updates to 6.0 *New for 9.5*
●
Minimum1024 X 768 pixels or greater monitor resolution with 16-bit color or higher
●
TCP/IPv4 or TCP/IPv6 network connection to the LiveCycle ES2.5 server
Note: You must have Administrative privileges to install Workbench. If you are installing using a
non-administrator account, the installer will prompt you for the credentials for an appropriate
account.
Designer
The following minimum requirements are necessary to take advantage of the latest Designer features.
●
A minimum of Acrobat Pro Extended is required to benefit from all the new features in Designer 9,
including the 3D features.
●
Adobe Flash® Player 9.0 or later.
●
(Optional) Flash® Builder™ 4.0 or later.
●
(Optional) Flex 4 SDK (required for customizing form guide components that are shipped with
Designer 9).
Note: Use the Flex 4 SDK included with the Designer installer only. Do not use any version of Flex SDK
obtained from the Adobe web site.
Adobe LiveCycle ES2.5
Before You Install
Installing Your Development Environment
Supported platforms
7
1.2.2 Supported platforms
The following platforms are supported for Workbench.
Operating system
Architecture
Windows XP Professional (Service Pack 3 or later)
32-bit
Windows Vista Business (Service Pack 1 or later)
32-bit and 64-bit
Windows Vista Home Basic/Premium (Service Pack 1 or
later)
32-bit and 64-bit
Windows Vista Ultimate (Service Pack 1 or later)
32-bit and 64-bit
Windows 2003 Server® (with Service Pack 2/R2 and above)
32-bit and 64-bit
Windows 2008 Server (Service Pack 1 or later)
32-bit and 64-bit
Windows 7 (Home Basic/Premium), Professional,
Enterprise)
32-bit and 64-bit
Note: Workbench is an English-only application. However, you can install Workbench on English, French,
German, and Japanese operating systems.
1.3 Upgrade considerations
The Workbench installer creates new directories and installs all new files, which allows Workbench to
co-exist on the same computer as an existing Workbench ES installation. Your LiveCycle ES (8.x) processes
will run as expected on your upgraded LiveCycle ES2.5 server, but you must import these processes in
order to modify them in Workbench. (See “Upgrading processes” on page 14)
Once you have determined that your Workbench installation is running properly, you can uninstall
Workbench ES. (See “Uninstalling Workbench” on page 20)
Upgrading LiveCycle 7.x processes
The Workbench installation program allows you to continue using migrated LiveCycle 7.x processes.
During the Workbench installation, all supporting files are installed in the following directory:
C:\Program Files\Adobe\Adobe LiveCycle Workbench ES2\workbench\upgrade\7x
You will need to install the Java™ Runtime Environment (JRE) appropriate for your application server. (See
“Enabling LiveCycle 7.x processes for your application server” on page 10.)
Processes based on LiveCycle 7.x QPACs remain compatible in LiveCycle ES2.5. To ensure future
compatibility, upgrade these processes using the Process Upgrade Tool available in Workbench.
See also “Upgrading processes” on page 14.
Adobe LiveCycle ES2.5
Before You Install
Installing Your Development Environment
Designer 9 installation considerations
8
1.4 Designer 9 installation considerations
By default, the Workbench installation includes a corresponding English-only version of Designer. If the
Workbench installation application detects an existing version of Designer on your computer, the
installation may terminate and you will be required to remove the current version of Designer before you
can continue.
The table below has a complete list of possible Designer installation scenarios that you may encounter, as
well as any actions you must take, when installing Workbench.
Version of Designer 9 currently
installed
Acrobat Pro or Acrobat Pro Extended
(includes Designer)
Required actions
None. The Workbench installation detects an instance of
Designer on your computer that was installed with either
Acrobat Pro or Acrobat Pro Extended.
Different versions of Designer can coexist on the same system,
for example Designer 8.2.x and 9.0.x. It is not necessary to
uninstall the version of Designer installed with Acrobat 9.2 Pro
or Acrobat 9.2 Pro Extended.
Designer (stand-alone)
None. The version of Designer included with Workbench is
English-only. The Workbench installer will not reinstall a new
version of Designer. Instead an updated version, bundled with
the Workbench installer, will be patched. This also allows you
to use your localized version of Designer within Workbench.
To replace your current version of Designer with the
English-only version included with Workbench, uninstall the
existing version of Designer 9 and then begin the Workbench
installation. (See To uninstall Designer (stand-alone):)
➤ To uninstall Designer (stand-alone):
1. Select Start > Settings > Control Panel > Add/Remove Programs.
2. In the Currently installed programs list, select Adobe LiveCycle Designer ES2.
3. Click Remove and then click Yes.
➤ To uninstall Designer included with Acrobat Pro or Acrobat Pro Extended:
1. Select Start > Settings > Control Panel > Add/Remove Programs.
2. In the Currently installed programs list, select Adobe Acrobat Pro or Adobe Acrobat Pro Extended.
3. Click Change/Remove and then click Next.
4. Select Modify, and then click Next.
5. Select Adobe LiveCycle Designer ES2, select This feature will not be available, and then click Next.
6. Click Update and then click Finish.
2
Installing LiveCycle Workbench
This chapter describes how to install LiveCycle Workbench.
Before you install Workbench, you must ensure that your environment includes the software and
hardware required to run it. (See “Before You Install” on page 5.)
The Workbench installation program installs two applications:
●
“Installing and running Workbench” on page 9
●
“Installing the Workbench Eclipse feature” on page 15
2.1 Installing and running Workbench
This procedure explains how to install Workbench and also how to enable upgrading of LiveCycle 7.x
processes if required. This procedure installs LiveCycle Designer 9, LiveCycle ES2.5 samples, and the
Workbench Eclipse feature.
➤ To install and run Workbench:
1. Do one of these tasks:
●
Navigate to the \livecycle_workbench directory on the install media and double click the
run_windows_installer.bat file.
●
Download and decompress the Workbench to your file system. After it is downloaded, navigate to
the \livecycle_workbench directory and double click the run_windows_installer.bat file.
Caution: The Workbench installer only runs from a DVD or local drive. It cannot be run from a remote site.
2. On the Introduction screen, click Next.
3. Read the Product License Agreement, select I accept the terms of the License Agreement, and then
click Next.
4. (Optional) Select LiveCycle Designer ES2 if you require this tool to create and modify forms.
5. Accept the default directory as listed, or click Choose and navigate to the directory where you will
install Workbench, and then click Next.
6. Review the preinstallation summary and click Install. The installation program displays the progress of
the installation.
7. Review the installation summary. Select Start Adobe LiveCycle Workbench to launch Workbench and
click Next.
8. Review the Release Notes and click Done.
9. The following items are now installed on your computer:
Workbench: To run Workbench from the Start menu, select Programs > Adobe > Adobe
LiveCycle Workbench ES2, if you chose to store the shortcut folder there. For information about
9
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Enabling LiveCycle 7.x processes for your application server
10
using Workbench, see Application Development Using LiveCycle Workbench 9 for Workbench 9 or
Application Development Using LiveCycle Workbench 9.5 for Workbench 9.5.
Designer: You can access Designer from inside Workbench. For information about using Designer,
see LiveCycle Designer 9 Help.
Workbench plug-in: Follow the instructions in “Installing the Workbench Eclipse feature” on
page 15.
LiveCycle ES2 SDK and SDK samples: You can access the LiveCycle ES2 SDK. For more information
on using the SDK see Programming with LiveCycle ES2.5.
2.2 Enabling LiveCycle 7.x processes for your application server
By default, LiveCycle Workbench installs upgrade support for LiveCycle 7.x along with the files required for
all supported application servers. These files are located here:
C:\Program Files\Adobe\Adobe LiveCycle Workbench ES2\workbench\upgrade\7x.
This section refers to the following default Workbench installation directory as [Workbench_HOME]:
C:\Program Files\Adobe\Adobe LiveCycle Workbench ES2\workbench
Workbench must be configured to connect to the host server using the EJB protocol in order to use the
Process Designer to manipulate the properties of activities from LiveCycle 7x QPACs. To do this, you will
need to modify the [Workbench_HOME]\workbench.ini file as appropriate for your application server.
When properly configured, the Workbench Adding New Server dialog will prompt for these additional
EJB-specific options:
●
Enable EJB connections for LiveCycle 7.x QPACs: Select this option to enable EJB connections.
●
EJB Port: Keep the default value if you are using the default SOAP/HTTP protocol.
Note: Install DSC component from Components View to launch the properties of activities of LiveCycle 7.x
processes.
Caution: Workbench will cache configuration information from earlier sessions. If the changes described
below are made to a Workbench instance that has run previously (that is, not a freshly installed
Workbench), you must start Workbench with the command line flag -clean to recognize the
newly provided plugin and configuration information. The flag only needs to be passed once.
Passing the flag again will slow down the startup time, but otherwise will not hinder
functionality.
2.2.1 About LiveCycle 7.x support files
By default, Workbench installs upgrade support for LiveCycle 7.x along with the files required for all
supported application servers. These files are located here:
C:\Program Files\Adobe\Adobe LiveCycle Workbench ES2\workbench\upgrade\7x.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Configuring Workbench for JBoss 4.2.x
11
2.2.2 Configuring Workbench for JBoss 4.2.x
Note: JBoss Application Server version 4.0.x is not supported.
2.2.2.1 Configure the startup parameters
1. Locate and open the [Workbench_HOME]\workbench.ini file in an editor.
2. Insert the bootclasspath specifier as follows:
upgrade\7x\qpacimages.jar;upgrade\7x\jbossall-client.jar
It will look like this:
-vmargs
-Xms128M
-Xmx512M
-Xbootclasspath/a: .;upgrade\7x\qpacimages.jar;upgrade\7x\jbossall-clien
t.jar
-XX:MinHeapFreeRatio=40
3. Save and close the file.
2.2.3 Configuring Workbench for WebLogic Server 10
Note: WebLogic Server 9.2 is not supported.
2.2.3.1 Generate the WebLogic full client JAR file
1. Obtain the document from the following web site and follow the steps to generate the full WebLogic
client jar file called wlfullclient.jar:
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs100/client/jarbuilder.html
2. Copy the generated wlfullclient.jar file into the [Workbench_HOME]\upgrade\7x
2.2.3.2 Configure Workbench startup parameters
1. Locate and open the [Workbench_HOME]\workbench.ini file in an editor.
2. Insert the bootclasspath specifier as follows:
7x/qpacimages.jar;7x/wlfullclient.jar
It will look like this:
-vmargs
-Xms128M
-Xmx512M
-Xbootclasspath/a: .;upgrade/7x/qpacimages.jar;7x/wlfullclient.jar
-XX:MinHeapFreeRatio=40
3. Save and close the file.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Configuring Workbench for WebSphere Application Server 6.1
12
2.2.4 Configuring Workbench for WebSphere Application Server 6.1
2.2.4.1 Install the Application Client for WebSphere 6.1
You must use the application client for WebSphere 7.0 but follow these instructions to install it for
WebSphere 6.1.
1. Download the application client for WebSphere 7.0 from the following location:
www14.software.ibm.com/webapp/download/preconfig.jsp?id=2009-09-15+16%3A54%3A48.621697
R&S_TACT=104CBW71&S_CMP=
2. Install the application client in the C:\Program Files\IBM\WebSphere\WASAppClient6.1 directory.
3. Configure the Workbench startup parameters to use the JRE 5 contained within the application client
as follows:
workbench –vm ..\..\..\IBM\WebSphere\WASAppClient6.1\java\jre\bin\java.exe
2.2.4.2 Install the application client EJB support plugins
1. Locate the application client plugins directory:
[WebSphere_install]\IBM\Websphere\WASAppClient6.1\plugins
2. Copy the entire contents of this directory (including all sub-directories) to the Workbench plugin
directory:
[Workbench_HOME]\plugins
2.2.4.3 Configure the Workbench startup parameters
1. Locate and open the [Workbench_HOME]\workbench.ini file in an editor.
2. Delete the entry -XX:MinHeapFreeRatio=40.
3. Insert the bootclasspath specified as follows:
upgrade\7x\qpacimages.jar;..\..\..\IBM\WebSphere\WASAppClient6.1\lib\boo
tstrap.jar;..\..\..\IBM\WebSphere\WASAppClient6.1\java\jre\lib\ext\iwsor
butil.jar;..\..\..\IBM\WebSphere\WASAppClient6.1\lib\j2ee.jar
It will look like this:
-vmargs
-Xms128M
-Xmx512M
-Xbootclasspath/a: .;upgrade\7x\qpacimages.jar;..\..\..\IBM\WebSphere\WA
SAppClient6.1\lib\bootstrap.jar;..\..\..\IBM\WebSphere\WASAppClient6.1\j
ava\jre\lib\ext\iwsorbutil.jar;..\..\..\IBM\WebSphere
\WASAppClient6.1\lib\j2ee.jar
4. Save and close the file.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Configuring Workbench for WebSphere Application Server 7
13
2.2.5 Configuring Workbench for WebSphere Application Server 7
2.2.5.1 Install the Application Client for WebSphere 7
1. Download the application client for WebSphere 7 from the following location:
www14.software.ibm.com/webapp/download/preconfig.jsp?id=2009-09-15+16%3A54%3A48.621697
R&S_TACT=104CBW71&S_CMP=
2. Install the application client in the C:\Program Files\IBM\WebSphere\WASAppClient7 directory.
3. Configure the Workbench startup parameters to use the JRE 6 contained within the application client
as follows:
workbench –vm ..\..\..\IBM\WebSphere\WASAppClient7\java\jre\bin\java.exe
2.2.5.2 Install the application client EJB support plugins
1. Locate the application client plugins directory:
[WebSphere_install]\IBM\Websphere\WASAppClient7\plugins
2. Copy the entire contents of this directory (including all sub-directories) to the Workbench plugin
directory:
[Workbench_HOME]\plugins
2.2.5.3 Configure the Workbench startup parameters
1. Locate and open the [Workbench_HOME]\workbench.ini file in an editor.
2. Delete the entry -XX:MinHeapFreeRatio=40.
3. Insert the bootclasspath specifier as follows:
upgrade\7x\qpacimages.jar;..\..\..\IBM\WebSphere\WASAppClient7\lib\boots
trap.jar;..\..\..\IBM\WebSphere\WASAppClient7\java\jre\lib\ext\iwsorbuti
l.jar;..\..\..\IBM\WebSphere\WASAppClient7\lib\j2ee.jar
It will look like this:
-vmargs
-Xms128M
-Xmx512M
-Xbootclasspath/a: .;upgrade\7x\qpacimages.jar;..\..\..\IBM\WebSphere\WA
SAppClient7\lib\bootstrap.jar;..\..\..\IBM\WebSphere\WASAppClient7\java\
jre\lib\ext\iwsorbutil.jar;..\..\..\IBM\WebSphere
\WASAppClient7\lib\j2ee.jar
4. Save and close the file.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Installing LiveCycle 7.x QPACs
14
2.3 Installing LiveCycle 7.x QPACs
Processes created in LiveCycle Workflow 7.x are compatible with and can be run in the LiveCycle ES2.5
environment whether you upgraded from a previous version of LiveCycle or installed and deployed a new
version of LiveCycle ES2.5.
Caution: LiveCycle ES2.5 is the last release to support QPACs. To ensure future compatibility, processes
using QPACs must be upgraded using the Process Upgrade Tool that is available in Workbench.
To enable compatibility of LiveCycle 7.x processes running in a LiveCycle ES2.5 environment that has not
been upgraded, you must perform the following actions:
●
During configuration with LiveCycle Configuration Manager, select Install the LiveCycle 7.x
Compatibility Layer on the Upgrade Task Selection screen, and complete the configuration and
deployment for this task. (See “Configuring, upgrading to, and deploying LiveCycle ES2” in the
Upgrading to LiveCycle ES2 from ES document for your application server.)
●
Deploy LiveCycle 7.x QPACs to Workbench.
Note: If you already installed and deployed LiveCycle ES2.5 but did not install the LiveCycle 7.x
compatibility layer, you can add it by running LiveCycle Configuration Manager at any time. Select
Install the LiveCycle 7.x Compatibility Layer on the Upgrade Selection screen, and then select
the Configure LiveCycle ES2 EARs and Deploy LiveCycle EARs tasks on the Task Selection screen.
You do not need to reinitialize the database or redeploy LiveCycle ES2.5 components.
The LiveCycle 7.x QPACs are located in the directory C:\Program Files\Adobe\Adobe LiveCycle Workbench
ES2\workbench\upgrade.
2.4 Upgrading processes
If you have upgraded from LiveCycle ES (8.x), your legacy processes will work as usual without any
intervention. If you need to manipulate these processes in any way, you must include them in a
LiveCycle ES2.5 application in order to edit them in Workbench.
Upgrading LiveCycle ES (8.x) processes upgraded from LiveCycle 7.x
If your LiveCycle ES (8.x) system was previously upgraded from LiveCycle 7.x, there are two upgrade
options:
●
In Workbench 8.x, upgrade the legacy processes using the Process Upgrade Tool, and then test and
redeploy them to the server. (See “About the Process Upgrade Tool” in the Application Development
Using LiveCycle Workbench 9 for Workbench 9 or Application Development Using LiveCycle Workbench
9.5 for Workbench 9.5.)
●
If you have already updated the LiveCycle 7.x processes, refer to the methods outlined in
“Upgrading LiveCycle ES (8.x) processes” on page 14 to update your LiveCycle ES (8.x) processes.
Upgrading LiveCycle ES (8.x) processes
If you have migrated processes from LiveCycle ES (8.x), the assets that migrated during LiveCycle ES2.5
server configuration will work as usual without any intervention. But if you need to modify these assets,
they must be imported into a LiveCycle ES2.5 application in order to edit them in Workbench.
Adobe LiveCycle ES2.5
Installing Your Development Environment
Installing LiveCycle Workbench
Installing the Workbench Eclipse feature
15
In order to modify LiveCycle ES (8.x) assets in Workbench, perform the following steps. (See “Upgrading
processes” in Application Development Using LiveCycle Workbench 9 for Workbench 9 or Application
Development Using LiveCycle Workbench 9.5 for Workbench 9.5)
1. Select an existing LiveCycle ES2.5 application or create a new one.
2. Right click the application and select Import.
3. Expand the LiveCycle Runtime Content folder to select Process and click Next.
4. On the Select Process screen, select your desired process and click Finish.
5. Deploy the application to the LiveCycle ES2 server.
6. Test and debug the application as necessary.
7. Repeat steps 1 to 6 to upgrade all LiveCycle ES (8.x) processes.
To migrate the LiveCycle ES (8.x) assets so that they are deployed as part of this updated application, click
[asset name] > Properties > Reset Deployment ID to deploy them to the location used by the
LiveCycle ES2.5 application. (See “Upgrading processes” in Application Development Using LiveCycle
Workbench 9 for Workbench 9 or Application Development Using LiveCycle Workbench 9.5 for Workbench
9.5)
2.5 Installing the Workbench Eclipse feature
You can optionally add the Workbench feature to Eclipse. You can add Workbench either after you have
installed Workbench or you can access the workbench-updatesite.zip file from the application
server specific DVD. For example, for JBoss the following location contains the file:
Workbench_DVD/additional/eclipse
Download and install Eclipse 3.4 from www.eclipse.org/downloads/.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Configuring Eclipse update feature for Workbench
16
2.5.1 Configuring Eclipse update feature for Workbench
Workbench supports the update feature to ensure you are using the most updated Eclipse version.
However, you must ensure that certain additional modules are included with each download:
Eclipse Version
Workbench required modules
Eclipse 3.4.x
●
Graphical Editing Framework GEF
●
WST XML Core
●
WST Web UI
●
Graphical Editing Framework GEF
[org.eclipse.gef.feature.group]: This is contained in the
'Graphical Modeling Framework SDK'
[org.eclipse.gmf.sdk.feature.group]
●
WST XML Core
[org.eclipse.wst.xml_core.feature.feature.group]: This is
contained in the 'Eclipse XML Editors and Tools'
[org.eclipse.wst.xml_ui.feature.feature.group]
●
Plug-in 'org.apache.commons.lang_2.3.0' [n/a]: This is
contained in the 'Mylyn Task List (Required)'
[org.eclipse.mylyn_feature.feature.group]
Eclipse 3.5.x and Eclipse 3.6.x
➤ Configuring the Eclipse update feature for Workbench:
1. Launch Eclipse.
2. Click Help > Software Updates.
3. Click the Available Software tab.
4. Select Add Site > Archive.
➤ To install and deploy the Workbench feature to Eclipse:
1. Start Eclipse.
2. Select Help > Software Updates > Find and Install, select Search for new features to install, and
then click Next.
3. Click New Archived site, browse to the directory where the Workbench installation saved the plug-in
ZIP file, select workbench-updatesite.zip, and then click Open.
4. Follow the instructions on the subsequent screens to deploy the Workbench feature to Eclipse.
Note: Ignore the message "Warning: You are about to install an unsigned feature,” and click Install to
continue.
Tip: The Adobe® LiveCycle® Service Discovery Plug-in for Adobe Flash® Builder™ 4 enables you to quickly
build Adobe Flex and AIR applications that invoke a LiveCycle ES2.5 service through its remoting
endpoints. Information about how to install and update the plug-in is available on the Adobe web
site at www.adobe.com/go/learn_flex4_sdp_en.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Configuring and logging in to a server
17
2.6 Configuring and logging in to a server
To use Workbench, you must have an instance of LiveCycle ES2.5 running, typically on a separate
computer. You must have a user name and password to log in to LiveCycle ES2.5, as well as details about
the location of the server.
Note: If you configured LiveCycle ES2.5 to use the EMC Documentum or IBM FileNet repository provider
and you want to log in to a repository other than the repository that is configured as the default in
LiveCycle Administration Console, provide the user name as [email protected]
2.7 Configuring time-out settings
By default, Workbench times out after two hours, regardless of activity or inactivity. To edit the time-out
setting, see “Configuring User Management > Configure advanced system attributes” in the LiveCycle
Administration Console Help.
2.8 Configuring Workbench to connect over HTTPS
To connect Workbench to a LiveCycle ES2.5 server over HTTPS, you must ensure that the certificate
authority (CA) that issued the public key will be recognized as being trusted by Workbench. If the
certificate is not recognized as coming from a trusted source, you must update the cacert file located in the
[Workbench_HOME]/jre/lib/security directory.
Note: [Workbench_HOME] represents the directory where you installed Workbench. The default location is
C:\Program Files\Adobe\Adobe LiveCycle Workbench ES2\workbench.
Ensure that you connect to HTTPS by using the name that is specified in the certificate. This name is
typically the fully qualified host name.
➤ To update the cacert file:
1. Ensure that you have a copy of the Secure Sockets Layer (SSL) certificate. Either contact the
administrator who configured the SSL server or export the certificate by using a web browser.
Tip: To export the certificate, open a web browser and log in to LiveCycle Administration Console, install
the certificate in the browser, then export the certificate from the browser to a temporary storage
location (or directly to the [Workbench_HOME]/jre/lib/security directory).
2. Copy the certificate to the [Workbench_HOME]/jre/lib/security directory.
3. Open a command prompt window, navigate to [Workbench_HOME]/jre/bin, and then type the
following command:
keytool -import -storepass changeit -file ssl_cert_for_certname.cer
-keystore cacerts -alias example
where:
●
changeit is the default password to the cacerts keystore.
●
certname is the certificate you selected in step 1.
●
example is the alias you choose for the certificate. This value can be changed.
Adobe LiveCycle ES2.5
Installing Your Development Environment
Installing LiveCycle Workbench
Configuring Workbench to connect over HTTPS
18
4. When prompted to trust the certificate, type Yes and hit the Enter key. The keytool proceeds to import
the cacerts file in to the [Workbench_HOME]/jre/lib/security directory.
5. Close and restart Workbench for the changes to take affect.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
Configuring cache settings for dynamically generated templates
19
2.9 Configuring cache settings for dynamically generated
templates
The following aspects of cache operation should be considered if your application generates unique
templates on the fly by automatically updating XFA content. In effect, each transaction uses a new, unique
template.
When LiveCycle Forms ES2 or Output ES2 searches for, or updates, entries in the cache for a specific form
template, it uses several key values to locate the specific cache entry that will be accessed.
Template file name: The location and filename of the template used as the primary unique identifier
of the cached form.
Timestamp: The template file contains a timestamp used to determine the last update time of the
form.
Template UUID: Designer inserts in each template a unique identifier (UUID) for the form and its
version. Each time the form is updated, the embedded UUID is updated. For example, an XDP template
might show the following content:
<?xml version="1.0" encoding="UTF-8"?>
<?xfa generator="AdobeLiveCycleDesignerES_V8.2"
APIVersion="2.6.7185.0"?><xdp:xdp
xmlns:xdp=http://ns.adobe.com/xdp/
timeStamp="2008-07-29T21:22:12Z"
uuid="823e538f-ff6c-4961-b759-f7626978a223"><template
xmlns="http://www.xfa.org/schema/xfa-template/2.6/">
Render options: Within the rendered form cache, the cache contents are stored separately for each set
of unique render options.
The Forms service receives templates by reference to filename or repository location, or by value as a XML
object in memory.
Templates passed by reference: Uses the content root and the form name. If unique templates with
different filenames are passed in every request using this method, the disk cache will grow endlessly
and will never be reused. To prevent this, unique templates should be passed with same filename to
ensure that same cache is updated for all requests.
Templates passed by value: Uses template bytes passed along with the data using theinDataDoc
parameter. If unique templates with different UUID are passed using this method, the disk cache will
grow endlessly and will never be reused. To prevent this, the UUID attribute should be stripped from all
templates to ensure that no cache is created for the template. Alternatively, passing the same non-null
UUID allows the cache objects to be created, but ensures that the same cache is updated with each
request.
As well, in order to prevent the cache from growing endlessly, consider the following factors for rendering
dynamically generated templates using the new LiveCycle ES2.5 APIs, those being renderHTMLForm2
and renderPDFForm2.
When using the new APIs, the template is passed as a document object, which is handled in the Forms
service based on whether it is passivated or not:
For passivated documents in which the UUID and content root serve as the cache key, consider the
following aspects:
●
The cache is not created for passivated input templates with no UUID.
Adobe LiveCycle ES2.5
Installing LiveCycle Workbench
Installing Your Development Environment
●
Uninstalling Workbench
20
If more than one passivated input template having the same UUID and content root are passed,
then the same cache is overwritten.
For non-passivated documents in which the filename and content root serve as the cache key, consider
the following aspect:
●
For non-passivated input templates, caching depends on the content root and filename from which
the document was generated. The same cache will be used only for requests with the same content
root and template filename.
The following best practices will ensure that the cache does not grow endlessly when dynamically
generated templates are passed to the Forms service:
●
Strip the UUID or pass the same UUID in all dynamically generated templates.
●
Generate the document either from template bytes or from the same filename on disk.
2.10 Uninstalling Workbench
In Windows XP, use the Add or Remove Programs function in the Control Panel to start the Uninstaller. The
Workbench and Designer applications have separate uninstall programs.
In Windows Vista, click Start > Control Panel > Programs > Programs and Features. Select Adobe LiveCycle
Workbench ES2 and then click Uninstall.
In Windows 7, click Start > Control Panel > Programs and Features. Select Adobe LiveCycle
Workbench ES2 and then click Uninstall.
3
Configuring LiveCycle ES2 XDC Editor
Using the Adobe LiveCycle ES2.5 XDC Editor, network printer administrators can create and modify XML
Forms Architecture Device Configuration (XDC) files. XDC files describe the capabilities of printers, such as
the printer language or the correlation between paper size and tray location.
Before your network printer administrator uses the XDC Editor, relocate the sample XDC files and
download LiveCycle ES2.5 XDC Editor Help.
➤ To obtain the sample XDC files:
1. On the LiveCycle ES2.5 server, locate the XDC folder in [LiveCycleES2 root]\LiveCycle_ES_SDK\samples\
Output\IVS.
2. Copy the contents of this folder into a directory that is accessible from the Workbench or Eclipse
system.
➤ To obtain the XDC Editor Help:
1. Go to the LiveCycle ES2.5 documentation website.
2. Click the Develop tab and navigate to LiveCycle ES2.5 XDC Editor Help. Download the
xdc_editor_help_web.zip file and install the Help files by following the instructions provided in the
Readme file.
21
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