
53
LIVECYCLE ES4 OVERVIEW
Content Management
Last updated 1/15/2015
Workbench developers can easily map values from other LiveCycle modules, such as Forms, Reader Extensions, or
PDF Generator, to the attributes of an ECM object. Connectors for ECM make it possible to reuse and scale the same
LiveCycle process to handle forms in different folders of the ECM system. In addition, the connectors include service
components to support ECM run-time integration.
Improved performance and scalability
Connectors for ECM preserve existing content schemas defined in an ECM system. By protecting the investment made
in the ECM infrastructure, customers have choices for designing schemas to achieve higher performance and
scalability of their ECM application.
Flexible deployment
Running the connectors on the same application server and operating system as the ECM system is no longer
necessary. Connectors for ECM are deployed with the other LiveCycle components. Flexibility exists because the
operating system and application server requirements are independent of those required for the ECM server.
Unified invocation methods
Using the expanded user interface choices, developers can develop applications by using a variety of client interfaces.
The following interfaces are supported:
• ECM user interfaces such as Documentum Webtop and FileNet P8 Workplace
• Portals
• Flex or desktop applications
• Workspace
Note: The Flex Worksapce is deprecated for AEM forms. It is available for the LiveCycle ES4 release.
Developers can programmatically invoke the content repository connector services and repository provider services
by using web services, (Deprecated for AEM forms) LiveCycle Remoting, and Java APIs. They can also invoke the
content repository connector services by using watched folders and email invocation methods. These methods are
available for calling the services within LiveCycle processes developed in Workbench.
How the Connectors for ECM work
In a typical process that interacts with an ECM system, a LiveCycle application retrieves a document from the ECM
repository and stores content in the repository.
Comentários a estes Manuais