Note: The LiveCycle Workbench ES2 add-ons are unsupported tools that are provided to improve developer productivity. Later releases of LiveCycle ES have included these tools or concepts similar to them in LiveCycle Workbench.

The Component Development Tool lets you quickly and easily build a custom Java Component ready to be deployed on your LiveCycle ES Server using Adobe LiveCycle Workbench ES. Specifically, the Component Development Tool provides a new type of Project in Eclipse that automatically generates your "component.xml", your Service Classes and an Ant build that emits a JAR file ready to deploy on your server. The Component Development Tool provides a Wizard to graphically create a new LiveCycle Component from scratch, or from existing Java code. It also lets you toggle between the XML view of your component descriptor and a graphical view of all its services and operations.

The Component Development Tool is great for any LiveCycle developer who wants to develop a new custom component for LiveCycle and use it in their LiveCycle Applications. It’s particularly suited to Java developers who are already familiar with Eclipse and need a more rapid way to develop new custom Components for LiveCycle.

The Component Development Tool is free for anyone to use. But it requires you to have access to a LiveCycle server in order to deploy your new Components.

Download the Component Development Tool

Getting started

Follow these steps to get started with the Component Development Tool:

Configure your system

The Component Development Tool is designed for use as a Plug-in within Eclipse (minimum version 3.4.2) and Java JDK version 1.6.

The tool requires you to set up the following Eclipse frameworks in your Eclipse installation. Before using this tool with Eclipse you will need to install and configure the following frameworks in your Eclipse environment.

The Eclipse Modeling Framework Project (EMF) version 2.4.2 in your Eclipse environment.
The Eclipse Graphical Editing Framework (GEF) version 3.4.2 in your Eclipse environment.
The Web Tools Platform (WTP SDK) into your Eclipse environment.

If you are not already familiar with these frameworks or need help configuring your Eclipse environment, please refer to the more detailed guide Configuring Eclipse for the LiveCycle Workbench ES Component Development Tool.

Installing and using Component Development Tool

When you have completed installation of the Eclipse frameworks above, you are ready to install the Component Development Tool.

Download the Component Development Tool
In Eclipse Open Help > Software Updates.
Select the Available Software Tab.
Select Add Site…
Select Archive…
Browse and open the Component Development Tool file in your download folder (from step 1).
Select OK
Click Install
Accept the license agreement and click Finish.
Restart eclipse. Now you should be able to open File > New > Other > Adobe LiveCycle > Component Project.

Community

Adobe Developer Connection

Read tutorials, samples, articles, and other resources to help you learn more about LiveCycle in the LiveCycle Developer Center.

Resources

If you want to learn more about releases on Labs as well as other Adobe technologies, visiting a user group or connecting with an Adobe Community Expert is a great place to start.

Product details

FAQ

What is the Adobe LiveCycle Workbench ES Component Development Tool?
LiveCycle Workbench ES Component Development Tool a plug-in for Eclipse that Java developers can use to build Custom Components for LiveCycle (also called, "DSCs").

Who should try the Component Development Tool?
This tool is great for anyone already familiar with LiveCycle who wants to extend it by adding their own Services written in Java. These Services can then be used with all of the other Services provided in LiveCycle to build LiveCycle Applications.

Which platforms are supported?
Being a plug-in to Eclipse, the Component Development Tool runs on all platforms that support Eclipse. The minimum supported version of Eclipse is 3.4.2.

Will the source code be made available on Adobe¹s open source site in the future?
No. This plug-in is a binary distribution only.

How is it the Component Development Tool related to LiveCycle Workbench ES?
The tool produces the JAR file for your new Custom Component that you can deploy on your LiveCycle server using LiveCycle Workbench ES.

System requirements

Any development environment that has Eclipse (version 3.4.2) installed. Please see the guide, Configuring Eclipse for the LiveCycle Workbench ES Component Development Tool for detailed Eclipse requirements.

Release notes

This release of the LiveCycle Workbench ES Component Development Tool is prerelease software and is designed for evaluation purposes only. The plug-in not final; but, many portions of the technology are fully implemented and ready for you to try and discuss.

Adobe LiveCycle Workbench ES2 Add-ons

Adobe LiveCycle Workbench ES2 Add-ons provides new tools and enhancements for LiveCycle Workbench ES2. The set of plugins update an existing installation with new features to improve developer productivity building LiveCycle ES2 applications.

LiveCycle Workbench ES2 is an integrated development environment (IDE) that developers use to create and manage LiveCycle ES2 applications and assets. Users can model, create, or automate processes and forms. The new tools and feature enhancements in this technology include the following:

Variable Highlighting — The feature enables users to clearly see which variables are used for each activity that is selected on the process.
Approval Wizard — The feature enables users to design an approval task with ease of answering a few questions in a wizard.
Record & Playback shortcut — The feature allows users to start recording and open their recording from the invocation dialog.
Schema Editor — The feature enables users to use a visual editor to create schemas.
Application Filter — The feature simplifies the dialog that allows users to retrieve applications by filtering the application that already exist in their workspace.
Event Tooling — The new wizard and user interface designed for events will make creating events much easier.
Relationship Viewer — The feature allows users to see the relationship of forms to their fragments.
Type Selection Improvements — The display of the data types in the variable creation dialog has been made easier.
Server Log Viewer — Support for viewing the LiveCycle Server log in the new Workbench Server Log viewer.

The new set of enhancements is perfect for any developer who wishes to get new features for their existing LiveCycle Workbench ES2 installation without having to change their LiveCycle ES2 server installation.

Download the LiveCycle Workbench ES2 Add-ons

Getting started

Follow these steps to get started with the LiveCycle Workbench ES2 Add-ons:

Before you begin: The LiveCycle Workbench ES2 Add-ons require an existing installation of LiveCycle Workbench ES2, which is purchased or downloaded with a LiveCycle ES2 server. The plugins can also be installed in an existing Eclipse (minimum version 3.2.4) and Java JDK version 1.6.

Download the LiveCycle Workbench ES2 Add-ons
Launch LiveCycle Workbench ES2.
If you have an existing version of the LiveCycle Workbench ES2 Add-ons installed, perform an uninstall prior to installing the new version:
1. Go to Help > Software Updates > Manage Configurations.
2. Expand Adobe LiveCycle Workbench ES2 in the left panel.
3. Select Adobe LiveCycle Workbench ES 9.5.0 and right click to Uninstall.
Go to Help > Software Updates > Find and Install, select Search for new features to install and then click Next.
Click New Archive site, browse to the download directory of the LiveCycle Workbench ES2 Add-ons ZIP, and select it. Click OK.
Follow the instructions on the subsequent screens to deploy the Workbench ES2 features. Ignore the message "Warning: You are about to install an unsigned feature", and click Install to continue. When done, Workbench will prompt you to restart.
Follow the Configuring the XML Schema Editor instructions
Follow the Deploying and Configuring the Server Log Component instructions

Community

Adobe Developer Connection

Read tutorials, samples, articles, and other resources to help you learn more about LiveCycle in the LiveCycle Developer Center.

Resources

If you want to learn more about releases on Labs as well as other Adobe technologies, visiting a user group or connecting with an Adobe Community Expert is a great place to start.

Product details

FAQ

What are the LiveCycle Workbench ES2 Add-ons?
The set of plugins update an existing Adobe LiveCycle Workbench ES2 with new features to improve developer productivity building LiveCycle ES2 applications.

Who should try the LiveCycle Workbench ES2 Add-ons?
The new set of enhancements is perfect for any developer who wishes to get new features for their existing LiveCycle Workbench ES2 installation without having to change their LiveCycle ES2 server installation.

System requirements

The system requirements for the LiveCycle Workbench ES2 Add-ons are the same as that for LiveCycle Workbench ES2.

Operating system

Microsoft® Windows® XP Professional; Windows Server® 2003; or Windows Vista® Home, Business, or Ultimate

Memory

1GB of RAM

Processors

Intel® Pentium® 4 at 2GHz or equivalent

Hard drive

2 GB space available (plus 1 GB temp space needed for installation)

In addition, users are required to have access to a LiveCycle ES2 server installation.

Release notes

This release of the LiveCycle Workbench ES2 Add-ons is prerelease software and is designed for evaluation purposes only. The add-ons are not final; but, many portions of the technology are fully implemented and ready for you to try and discuss.

Known Issues

Creating a form with a data model on Workbench fails with "The file was not found. Please verify the file name" after using the update site plugins. The reason for this is that a new Designer is required after the update of the plugins. We recommend users to update their Workbench ES2 to the SP1 version.
Creating a fragment on Workbench fails with the OK button disenabled at the last step after using the update site plugins. The reason for this is that a new Designer is required after the update of the plugins. We recommend users to update their Workbench ES2 to the SP1 version. If users try to delete an application with a form where a fragment is being created and the fragment creation failed with Designer not closed, and they succeed, a form will not be created again with error “The operation cannot be completed because LiveCycle Designer has a dialog box open. Please close the dialog box and try again."

Adobe LiveCycle Workbench ES2 Archive Migration Tool

Adobe LiveCycle Workbench ES2 Archive Migration Tool is a plug-in designed for LiveCycle Workbench users to migrate a LiveCycle 8.x archive into a LiveCycle ES2 application. This plug-in should be installed on Adobe LiveCycle Workbench ES2 or newer.

Without this archive migration tool, users can import and manage a LiveCycle 8.x archive manually (details can be found in the online tutorial).

With this archive migration tool installed, LiveCycle Workbench ES2(SP1) users can import a LiveCycle 8.x archive into the Workbench workspace directly. A new LiveCycle ES2 application is created and all the resources in the 8.x archive are imported into the ES2 application.

Download the LiveCycle Workbench ES2 Archive Migration Tool

Getting started

The archive migration tool requires an existing installation of LiveCycle Workbench ES2 SP1 (or newer) which is purchased or downloaded with a LiveCycle ES2 server.

Follow these steps to get started with the LiveCycle Workbench ES2 Archive Migration Tool:

Download the LiveCycle Workbench ES2 Archive Migration Tool
Unzip the the download into local disk.
Copy com.adobe.livecycle.workbench.lca.migration.jar into WORKBENCH_HOME/plugins dir. For example: C:\Program Files (x86)\Adobe\Adobe LiveCycle Workbench ES2\workbench\plugins.
After starting Workbench, you will see new menu items under File > Archive Migration Tool.

Community

Resources

If you want to learn more about releases on Labs as well as other Adobe technologies, visiting a user group or connecting with an Adobe Community Expert is a great place to start.

Product details

FAQ

What is the LiveCycle Workbench ES2 Archive Migration Tool?
It is a plugin that imports a LiveCycle 8.x archive(8.x lca) into a Workbench workspace and migrates the archive into an ES2 application.

Who should try the LiveCycle Workbench ES2 Archive Migration Tool?
The tool is perfect for the LiveCycle developer who wishes to reuse a LiveCycle 8.x archive on a LiveCycle ES2 environment.

System requirements

To use LiveCycle Workbench ES2 Archive Migration Tool, users must have LiveCycle Workbench ES2 installed and patched to SP1 or newer.

Release notes

This release of the LiveCycle Workbench ES2 Archive Migration Tool is prerelease software and is designed for evaluation purposes only. The plug-in is not final; but, many portions of the technology are fully implemented and ready for you to try and discuss.

Known Issues

When an 8.x lca is migrated into an ES2 application by the tool, the references to assets contained in the lca are all updated except the process variables and activity configurations. Users need to go through all the process variables and parameters of each activity configuration, and update the literal values if any. It is possible the embedded literal values are still referring to some paths that only exist on the previous LiveCycle server.
If the existing 8.x lca used deprecated services, WBP-152 will be triggered in validation report view and users are recommended to replace it using its new version in ES2 after migrated. For example, if LC8.x process was using Process Management > User-1.0(deprecated), users need to replace it using Process Management > User-2.0 and select form asset by manual in its configuration panel.
User needs to deploy the application on the the server and refresh events view in order to trigger catch event properties when upgraded from LC8.x event by 8.x upgrade/migration tool.
Custom components(aka DSCs) and service configuration contained in the lca will be skipped.