Key features

Connectors for ECM provide the following features:

  • Integrated content repository services to other LiveCycle components

  • Improved performance and scalability

  • Flexible deployment

  • Unified invocation methods through expanded user interface choices

  • Expanded support for ECM platforms

The Connector for Microsoft SharePoint provides the following features:

  • Allows users to invoke LiveCycle processes, such as an approval process from within SharePoint

  • Allows users to convert documents to Adobe PDF and manage the rights on a file in PDF or native formats

  • Provides the ability to create and initiate SharePoint workflows that use services in LiveCycle

  • Enables users to apply usage rights to PDF files to enable additional features in Adobe Reader

  • Allows automation of running LiveCycle processes from within SharePoint workflows

  • Enables users to manage assigned tasks and claim new tasks from within SharePoint 2010

  • Allows integration of LiveCycle forms with SharePoint Server 2010 and effectively use SharePoint as the repository for form data

Integrated content repository services

Customers can develop LiveCycle engagement applications that process and consume contents that are stored in ECM systems. Connectors for ECM provide integrated content repository services, including content library services, version control, and secure access, to the entire LiveCycle product. Also, through the component services, the connector components provide basic content repository services, such as checkin, checkout, and content metadata access. The Connector for Microsoft SharePoint allows you to integrate LiveCycle forms with SharePoint Server 2010 and use SharePoint as the repository for form data.

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

Developers can programmatically invoke the content repository connector services and repository provider services by using web services, 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.

// Ethnio survey code removed