|
To access an ECM programmatically using the Repository
Service API, administrators must select the appropriate ECM repository
service provider. For information about setting up the ECM connector
services, see the installation document specific to your application
server, from the LiveCycle ES3 Documentation page.
When developing a process that uses a repository provider service,
you can specify the resource URL to the ECM content repository.
The URL Is specified in the properties associated with a service,
such as the Forms service. You can also specify the resource URL
by using the Forms Service API.
Note: Connector for IBM Content Manager does not currently
support the repository provider service.
You can also access an ECM content repository by using the Repository
Service API to programmatically store and retrieve information.
For example, you can obtain a list of files or retrieve specific
files stored in an ECM content repository when a file is needed
as part of processing an application.
You can use a content repository connector service in a process
to interact with content objects in an ECM content repository. When
using this service in a process, you can accomplish tasks such as
these:
Access a user-defined content repository (a repository
other than the one the repository provider uses)
Retrieve content and its attributes from the content repository
that another service can consume in a subsequent step in the process
Store content and its attributes in the content repository
that another service produced in a previous step in the process
Get a list of available custom data models from the content
repository and map process variables to content attributes in the
content repository
(LiveCycle Connector for Microsoft SharePoint only) Create
and initiate SharePoint workflows that use services in LiveCycle
(LiveCycle Connector for Microsoft SharePoint only) Convert
documents to Adobe PDF format, apply usage rights, and enable additional
features in Adobe Reader
The LiveCycle 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 LiveCycle 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
For
information about developing processes that use these services,
see Workbench Help. For information about
developing client applications that programmatically interact with
these services, see Programming with LiveCycle. For information
about configuring SharePoint sites to invoke LiveCycle processes
and perform LiveCycle actions, see the installation document specific
to your application server, from the LiveCycle ES3 Documentation page.
Configure
the default connection to the ECM content repository, change the repository
service provider, and specify other ECM-specific default settings
by using Administration Console. (For more information, see the LiveCycle Administration Console Help.)
|
|
|
