47
21
4
Connector Services for ECM
Adobe LiveCycle ES 8.2 Connector for EMC Documentum, Adobe LiveCycle ES 8.2
Connector for IBM Content Manager, and Adobe LiveCycle ES 8.2 Connector for IBM FileNet provide the
following services:
A repository provider service: The Repository Provider service for EMC Documentum and the
Repository Provider service for IBM FileNet provide storage and retrieval capabilities through the
Repository Service API. These services enable developers to access and manage assets stored in the
ECM content repository at design time.
When a developer designs a form, and creates an application in LiveCycle Workbench ES or using the
Repository Service API, the developer can use the assets in an ECM content repository instead of the
repository provided with LiveCycle ES. Such assets may include forms, PDF files, fragments, images,
XML schemas, and test data. Developers can create an application allowing LiveCycle ES services to
access these assets through the Repository Service API, process variables, and property sheets. Form
designers can access and store these assets directly in the ECM content repository within
Workbench ES.
A content repository connector service: The Content Repository Connector for EMC Documentum
service, the Content Repository Connector for IBM Content Manager service, and the
Content Repository Connector for IBM FileNet service are all independent and usable as operations in a
LiveCycle ES process. Workbench ES developers can use these services in a process to store content in
and retrieve content from custom content models in an ECM content repository. Each connector
service provides access to content objects and their metadata stored in the ECM content repository.
Take the example of a financial institution automating an account opening process. The process must
enable applicants to digitally sign application forms, archive the completed forms in the ECM
repository, retrieve the final declaration and other relevant documentation, assemble those documents
into a single PDF file, and deliver the PDF file to applicants through email or post. The LiveCycle ES
application that the financial institution develops for this process includes content repository
connector service operations to store the completed forms in a customer-defined content object type
in the ECM repository and to retrieve the documentation, which can be generated from other ECM
applications, for assembly from the ECM repository.
Process Engine Connector for IBM FileNet service: Workbench ES developers can also use the
Process Engine Connector for IBM FileNet service to create processes that set and retrieve IBM FileNet
Workflow Step parameters and dispatch a workflow step. (See L
iveCycle
Workbench ES H
elp
.)
At run time, assets can be retrieved from the ECM content repository as part of completing a business
process. For example, end users can access forms and submit form data from
Adobe LiveCycle Workspace ES (8.2), EMC Documentum Webtop, IBM Content Manager client, or IBM
FileNet P8 Workplace. Alternatively, a client application can retrieve and store content as part of an
automated business process.
Using the ECM connector services
To access an ECM from Resource View in Workbench ES or programmatically using the
Repository Service API, administrators must select the appropriate ECM repository service provider in
LiveCycle Administration Console instead of the default repository provider service provided with
54
Adobe LiveCycle ES
Connector Services for ECM
LiveCycle ES Services
Using the ECM connector services 22
LiveCycle ES. For information about setting up the ECM connector services, see the LiveCycle ES
installation guides, such as
I
nstalling and Deploying
LiveCycle ES f
or JBoss
.
You can access an ECM content repository by using the LiveCycle Form Design perspective in
Workbench ES. You will be logged in to the default Documentum repository or FileNet object store. You
can also specify a Documentum or FileNet repository when you log in to Workbench ES. You must have the
appropriate credentials to access the content repository. Each time you use Workbench ES, a connection
to the selected content repository is made. The content repository is exposed as a hierarchical directory
structure (below a docbase or objectstore directory) in the Resources View in Workbench ES. You can share
the content repository from Workbench ES with other developers.
When developing a process that uses a Repository Provider service, you can specify the resource URL to
the ECM content repository in the properties associated with a service, such as the Forms service. You can
also specify the resource URL using the Forms Service API.
Note:ConnectorforIBMContentManager does not currently support the Repository Provider service.
You can also access an ECM content repository 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 used by the repository
provider).
●
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.
For information about developing processes that use these services, see LiveCycle WorkbenchES Help
. For
information about developing client applications that programmatically interact with these services, see
Programming with
LiveCycle ES
.
You configure the default connection to the ECM content repository, change the repository service
provider, and specify other ECM-specific default settings by using LiveCycle Administration Console. (See
Applications and Services
Administration Help
, Documentum Administration Help
, IBM Content Manager
Administration Help
, and FileNet Administration Help
.)
27
23
5
Convert PDF Service
The Convert PDF service converts PDF documents to PostScript® or image files (JPEG, JPEG 2000, PNG, and
TIFF). Converting a PDF document to PostScript is useful for unattended server-based printing on any
PostScript printer. Converting a PDF document to a multipage TIFF file is practical when archiving
documents in content management systems that do not support PDF documents.
Using the Convert PDF service
You can accomplish the following tasks using the Convert PDF service:
●
Convert PDF documents to PostScript. When converting to PostScript, the conversion operation allows
you to specify the source document and whether to convert to PostScript level 2 or 3. The PDF
document you convert to a PostScript file must be a non-interactive PDF document.
●
Convert PDF documents to JPEG, JPEG 2000, PNG, and TIFF image formats. When converting to any of
these image formats, the conversion operation allows you to specify the source document and an
image options specification containing various preferences, such as image conversion format, image
resolution, and color conversion.
For information about developing processes that use this service, see LiveCycle WorkbenchES Help
. For
information about developing client applications that programmatically interact with this service, see
Programming with
LiveCycle ES
.
You use the Applications and Services pages of LiveCycle Administration Console to configure default
properties for this service. (See Applications and Services Administration Help
.)
27
24
6
Decision Point Service
The Decision Point service provides the capability to identify a point in the process where a decision is
made that affects how the process progresses.
Several situations require the use of the Decision Point service:
●
Several routes need to be evaluated to determine the first operation to execute in a process.
This situation occurs when a process is initiated when a person submits a form, and form data
determines the first action to execute in the process map. For example, a customer can fill an invoice
dispute form through your corporate web site. The dollar amount of the invoice determines whether
the form is routed to a first-level manager for approval or to a credit representative for processing.
●
Several different routes in a process converge at a point where a set of rules are evaluated.
This situation can occur when the process loops to a step where a set of rules are re-evaluated. For
example, in a quality assurance process, an issue may have to go through a retesting process until it is
fixed and the process can proceed.
This situation can also occur if several branches converge after running in parallel. For example, in a
process for hiring new employees, when an applicant is hired, several subprocesses are initiated as part
of the hiring process. When each of the subprocesses completes, multiple rules based on the data of
each subprocess are evaluated to determine the next step.
Using the Decision Point service
You can use this service in a process when you need multiple routes to originate at an operation but there
is no single step in the business process that requires the evaluation of routes. The Decision Point service
acts as a node in the process that serves as the origin of many routes, but has no executable function itself.
For information about developing processes that use this service, see LiveCycle WorkbenchES Help
.
39
25
7
Distiller Service
The Distiller® service converts PostScript, Encapsulated PostScript (EPS), and printer text files (PRN) to
compact, reliable, and more secure PDF files over a network. The Distiller service is frequently used to
convert large volumes of print documents to electronic documents, such as invoices and statements.
Converting documents to PDF also allows enterprises to send their customers a paper version and an
electronic version of a document.
Using the Distiller service
When converting a PostScript, Encapsulated PostScript, or PRN file to a PDF file, the conversion operation
allows you to specify several options to apply to the resulting PDF document. For example, you can specify
the following options:
●
Adobe PDF settings, such as high quality print, oversized pages, and press quality. When this parameter
is not provided, the Distiller service will use the default PDF settings as configured using LiveCycle
Administration Console.
●
Job configuration settings to apply while generating the PDF document, such as optimizing for fast
web viewing. This optional parameter contains the file with settings to apply while generating the PDF
document (for example, optimization for web view) and settings to apply when the PDF document is
created (for example, initial view and security).
●
Metadata information to apply to the generated PDF document. This optional parameter contains the
file with metadata information to apply to the generated PDF document. Only UTF-8 encoded Adobe
Extensible Metadata Platform (XMP) metadata is supported. For details of the format and for the
specifications, please visit the main XMP page
at the Adobe website.
For information about developing processes that use this service, see LiveCycle WorkbenchES Help
. For
information about developing client applications that programmatically interact with this service, see
Programming with
LiveCycle ES
.
In LiveCycle Administration Console, you can use the Applications and Services pages to configure default
properties of the Distiller service. (See Applications and Services Administration Help
.) You can also use the
LiveCycle PDF Generator ES page to specify default PDF settings and security settings to apply when
converting to PDF. (See Generate PDF Administration Help
.)
57
26
8
DocConverter Service
The DocConverter service transforms signed or unsigned PDF documents, XML forms (typically created in
LiveCycle Designer ES), and Acrobat forms to PDF/A-compliant documents. You can also use this service to
validate whether PDF documents are compliant with the PDF/A format, which is primarily used for
archiving.
The DocConverter service is included with the following solution components:
●
Adobe LiveCycle PDF Generator ES (8.2)
●
Adobe LiveCycle PDF Generator 3D ES (8.2)
●
Adobe LiveCycle Output ES (8.2)
To use the DocConverter service with XML forms, you must have Output ES. To use the DocConverter
service with documents that contain signed or unsigned signature fields, you must have Adobe LiveCycle
Digital Signatures ES (8.2).
Using the DocConverter service
You can accomplish the following tasks using the DocConverter service:
●
“
Validating whether
P
DF document
s
are c
ompliant with the PDF/A format
” on page 26
●
“
Converting
P
DF document
s
to PDF/A format
” on page 26
For information about developing processes that use this service, see LiveCycle WorkbenchES Help
. For
information about developing client applications that programmatically interact with this service, see
Programming with
LiveCycle ES
.
Validating whether PDF documents are compliant with the PDF/A format
You can use the DocConverter service to validate whether a PDF document is compliant with the
PDF/A-1b format.
Converting PDF documents to PDF/A format
You can use the DocConverter service to transform signed or unsigned PDF documents, XML forms
(typically created in Designer ES), and Acrobat forms to PDF documents that are compliant with PDF/A-1b,
a format that is primarily used for archiving. Because long-term preservation is the goal, the document
contains only what is needed for opening and viewing throughout the intended life of the document. For
example, PDF/A-compliant documents contain only text, raster images, and vector objects; they do not
contain encryption and scripts. In addition, all fonts are embedded and the file is uncompressed so that
the documents can be opened and viewed as created. As a result, a PDF/A document is typically larger
than a standard PDF document. Also, a PDF/A document does not contain audio and video content.
If the DocConverter service cannot perform a complete conversion to PDF/A format for a particular file, it
partially converts the file. In addition to the converted file, the DocConverter service also creates a report
that indicates any fixes that were applied to the file and any violations that could not be fixed.
9
Adobe LiveCycle ES
DocConverter Service
LiveCycle ES Services
Converting PDF documents to PDF/A format 27
Although PDF/A is the standard for archiving PDF documents, it is not mandatory that PDF/A be used for
archiving if a standard PDF document meets your company’s requirements. The purpose of the PDF/A
standard is to establish a PDF file meant for long-term archiving and document preservation needs. For
more information about PDF/A, see PDF as a Standard for Archiving
.
51
28
9
Document Management Service
The Document Management service enables processes to use the content management functionality
provided by Adobe LiveCycle Content Services ES (8.2). For information about Content Services ES, see
LiveCycle ES O
verview
.
Using the Document Management service
You can accomplish the following tasks using the Document Management service:
●
“
W
orking with contents and spaces
” on page 28
●
“
Working with associations
” on page 29
●
“
Working with content attributes
” on page 29
For information about developing processes that use this service, see LiveCycle WorkbenchES Help
. For
information about developing client applications that programmatically interact with this service, see
Programming with
LiveCycle ES
.
You can use the Applications and Services pages of LiveCycle Administration Console to configure default
properties for this service. (See Applications and Services Administration Help
.)
Working with contents and spaces
Content is a file or document that consists of two main elements: the content itself and information about
the content (metadata). For example, the files can be documents, video, audio, images, XML, HTML, and so
on. Content can be added to or created in spaces within the Content Services ES repository and can be
classified and organized into categories.
A space is used to store and organize content items and other spaces. A space can hold any type of
content.
You can use the Document Management service operations to perform the following tasks:
Create a space: Create a space in Content Services ES.
Create a space from an existing space or template: Create a space in Content Services ES, based on
an existing space or a template. All the rules, contents, and users are copied to the new space from the
existing space or template.
Delete content or a space: Delete specified content or a space and its related metadata. When you
delete a space, all its contents are deleted too. When you delete content, all versions of that content are
deleted.
Copy a content item or space: Copy a specified content item or space and its related metadata from
one space to another. When you copy a space, all its contents are copied too.
Note:If the target location already contains a space with the same name, the new space is named
Copy of [space name].
37
Adobe LiveCycle ES
Document Management Service
LiveCycle ES Services
Working with associations 29
Store content: Store or update content and its metadata in the Content Services ES repository.
Move a content item or space: Move specified content or a space and its related metadata from one
location (space) to another. When you move a space, all of its contents are moved too.
Retrieve content: Retrieve specified content and its related metadata.
Working with associations
An association is a way to tie together two or more content items in the repository. Types of associations
available in LiveCycle Workbench ES include the following:
●
An association between an XML data file and an attachment
●
An association that links an XML data file and a PDF form
●
An association that links two PDF documents
You can also create your own custom associations. You can use the Document Management service
operations to perform the following tasks:
Create associations between content items: Create an association between two content items or
folders in the repository.
Get associated: Retrieve a list of IDs of content items that are associated with specified content using a
specified type of association.
Working with content attributes
Content attributes are the metadata for a content item. Metadata is stored in a database, separate from the
content item that it applies to. This structure allows for faster searching of the metadata.
You can use the Document Management service operations to perform the following tasks:
Get content attributes: Retrieve the attributes associated with specified content.
Set content attributes: Set metadata attributes for specified content without modifying the content.
The content is not versioned in this operation.
Considerations for LiveCycle Contentspace ES
Users can open and fill forms from within Adobe LiveCycle Contentspace ES (8.2) by browsing to the space
where the form is located, viewing the details for the file, and then clicking Fill Form. When the user
submits the form, the data is extracted and saved as an XML file. When using LiveCycle Designer ES to
design an XDP form that will be accessed in this way, do not include a Submit URL on the form. If you do,
the submitted form data will not be available inside Contentspace ES because the Submit URL will not be
overridden.
37
30
10
Email Service
Email is commonly used to distribute content or provide status information as part of an automated
process. The Email service enables processes to receive email messages from a POP3 or IMAP server, and
send email messages to an SMTP server.
For example, a process uses the Email service to send an email message with a PDF form attachment. The
Email service connects to an SMTP server to send the email message with the attachment. The PDF form is
designed to let the recipient click Submit after completing the form, which causes the form to be returned
as an attachment to the designated email server. The Email service retrieves the returned email message
and stores the completed form in a process data form variable.
When the Email service connects to a POP3 or IMAP server to retrieve an email message, it requires a way
of identifying a unique email message from several that may exist in the mailbox. Typically this
identification is done by embedding a unique identifier in the subject line, such as the process ID, or by
searching for a particular sender. The Email service provides the capability to customize the “from”, “to”,
“subject”, and “body” text of an email message. Developers can specify search criteria for a matching email
message, such as the sender or subject of the email message.
Using the Email service
You can interact with the Email service by developing a process in LiveCycle Workbench ES that uses the
service. You can accomplish the following tasks using the Email service:
●
Configure the Email component with default properties for connecting to an SMTP server for sending
email messages, and to either a POP3 or IMAP server for receiving messages
●
Receive email messages and attachments from either a POP3 or IMAP email server. You can save
metadata about the email, as well as the message content. You can also set filters for email messages,
and set properties about the email server and user account to use.
●
Send an email message that has one or more attachments to an SMTP server.
For information about developing processes that use this service, see L
iveCycle
Workbench ES H
elp
.
You can also use the Applications and Services pages of LiveCycle Administration Console to configure
default properties for this service. (See Applications and Services Administration Help
.)
Documents you may be interested
Documents you may be interested
