Central Pro migration support
LiveCycle Designer ES2 imports Output Designer templates to help Central Pro users migrate to LiveCycle
Output ES2. Migrating templates can however be a considerable effort if a large template library exists. Data
for templates may also be generated or sourced from a number of existing systems that may not be easy to
change. To help mitigate this process LiveCycle Output ES2 contains a set of services called the Central
Migration Bridge. These services allow Central Pro data transformations and Output Designer template merges
with existing data sources to be executed on the LiveCycle ES2 platform using Central Pro 5.7 executables. In
this way the Central Pro migration can be staged with process integration with the source system being
implemented first, utilizing the Central Migration Bridge services in LiveCycle Workbench ES2. Existing
transformation scripts, Output Designer templates and data sources including Field Nominated data continue
to be used. New applications can be developed using Designer ES2 and run with existing Central Pro
applications on the same server.
Representative use cases
There are many possible use cases for LiveCycle Output ES2. The following items are some representative use
Example Case 1: A bank teller completes a foreign exchange transaction for a client. He presses the “receipt”
button on the teller application. XML data representing the transaction is merged with a receipt template that
was designed with LiveCycle Designer ES2. A PDF document is generated and opens in the browser on the
teller’s terminal. The teller prints the receipt to his local printer and hands it to the client.
Example Case 2: A loan officer in a bank needs to complete the delivery of an approved loan agreement to a
client. Within the banking system, she has the option to print locally, print to a mail center for physical mailing,
or e-mail as a PDF file. Depending on the selection, LiveCycle Output ES2 will merge loan details with the
appropriate template and format as required. The document can be generated as PCL and printed to the loan
officer’s office printer; generated with a mail instruction separator sheet in PostScript; printed to a network
printer in the mailroom of the bank’s regional HQ; or generated as PDF. It can also be certified by LiveCycle
Digital Signatures ES2 and e-mailed to the client’s e-mail address automatically. The instruction sheet is
printed on blue paper located in a second paper tray on the printer. In all cases, a PDF/A version of the
document is stored in the bank’s archive.
Example Case 3: A social services administrator works with clients in a neighborhood housing office, where he
meets with them individually and reviews their cases for housing benefits. The core administration system is
used for tracking claims and determining eligibility. When a decision has been made, the administrator meets
with clients to explain the results of their claims, at which point a document that is carefully regulated for
content and reviewed by social services lawyers must be printed and handed to the client. The client’s
information from the core administration system is merged with the required template, and a correct
regulatory document is formatted and printed on the administrator’s office printer.
Example Case 4: A warehouse product picker places all of the required items in a shipping box, confirms the
pick activity is complete in the warehouse order system, and presses the “shipping documents” button. The
warehouse order system makes a request to LiveCycle Output ES2 to pass XML transaction data. The data is
merged with a packing list template, which is sent to a PCL laser printer and also merged with a shipping label
template, which is sent to a Zebra label printer at the station. The packing list is placed in the box, closed and
sealed with the shipping label attached.
Example Case 5: A financial adviser at a call center completes a client call in which she discusses three mutual
funds. From a Flash-based interface, she selects the three funds from a list and launches a letter application
provided by Forms ES2. The letter application presents a standard layout for such a call. She adds standard
clauses and a personal message, and then presses a “deliver” button. A standard letter is generated containing
the added clauses and personal message and indicating that mutual fund datasheets will follow. The
formatted letter is passed to Assembler along with the three datasheets. Assembler creates a single document
with the letter and the three datasheets. A branded header and footer are placed on each page with the
advisor’s name, rep number, and today’s date. The PDF file is e-mailed to the client.
Example Case 6: A distributor provides a partner portal that lets partners request and download PDF product
datasheets with the distributor’s logo and details. The distributor logs into the portal and selects a datasheet.
The portal has all of the distributor’s information available in a database. LiveCycle Output ES2 formats a PDF
overlay containing only the distributor logo, name, address, and other pertinent details in prearranged
positions. This PDF overlay is imposed on top of the base datasheet requested. Placing the logo and
information in prearranged blank areas, the distributor downloads the personalized PDF document and from
Adobe Reader® software, he prints as many copies as required on the office color printer.
LiveCycle Production Print ES2
Document templates for LiveCycle Production Print ES2 can be created using Designer ES2. A key capability of
LiveCycle ES2 is that the same designer can be used with LiveCycle Forms ES2, LiveCycle Output ES2, and
LiveCycle Production Print ES2. This allows you to leverage skills development in LiveCycle Designer ES2 and a
library of forms, templates, and fragments across all three products.
Production Print ES2 features a dedicated process design environment called Design Center. LiveCycle
Designer ES2 is integrated into Design Center, allowing direct access to templates. Design Center allows each
step in a production print process to be defined via GUI-based tools. Steps include converting incoming data
formats, data identification, association with a LiveCycle Designer ES2 template, formatting, sorting, page
imposition, marking for enveloping machines, and final output formatting.
Workbench ES2 is capable of generating a LiveCycle archive (LCA), which can include a template and its
related fragments. LiveCycle Production Print ES2 can read LCA files and import templates with related
fragments into its repository. In this way, it can process both self-contained LiveCycle Designer ES2 templates
and templates with fragments. In addition, templates and fragments can be read from the Workbench
repository. Design Center provides a method to check for and apply any changes in referenced templates and
fragments in a project. The LiveCycle Repository can also be used to manage a combined template library
shared by multiple LiveCycle ES2 modules.
LiveCycle Production Print ES2 is accessible via a service in Workbench which invokes a named process and a
LiveCycle ES2 process can pass work and control to a LiveCycle Production Print ES2 process. For instance,
during the day, call center operators generate letters confirming changes in client accounts, a Workbench
process passes a letter template and data to a named process on LiveCycle Production Print ES2 which formats
and places the document in the post-processing repository. At night an operator releases all of the letters for
batch printing and enveloping.
Design Center organizes processes into projects, which are exported for runtime use. Each project contains all
of the process definition, templates, fragments, and other resources required to execute in the runtime
environment. The Control Center component manages the runtime server instances and places exported
projects into production.
The LiveCycle Production Print ES2 runtime environment is a dedicated performance-oriented runtime that
runs natively on the operating system. The runtime scales, processing transactions across multiple processors
and cores. Control Center can manage multiple servers running the same or different projects making the
solution highly scalable and configurable for fault-tolerant applications.
Processes can be invoked through a number of mechanisms, including web services (SOAP), watched folders,
COM, and Java technologies. It is also possible to integrate with the LiveCycle ES2 runtime.
Data and page input
LiveCycle Production Print ES2 accepts both text and XML input formats. Design Center has tools to map and
process ASCII data files of fixed-record format and to overlay text format. This data is made available for use in
templates. XML and text data can be merged with LiveCycle Designer ES2 templates at runtime.
LiveCycle Production Print ES2 provides tools and runtime capability to read PDF and AFP pages. These pages
can be read into the post-processing repository and combined with other pages into document packages for
single documents or batch use cases. Objects on the pages in the post-processing repository may be read,
altered, or new objects may be added. Since documents can then be formatted into any supported output
format, this process acts as a document conversion process. For instance, a large AFP print file designed for a
preprinted roll paper with a company logo can be read, be split into individual documents, have a company
logo added in the top right where it is on the roll paper with each document saved in a PDF file to support an
LiveCycle Production Print ES2 can generate documents in a variety of formats:
• Electronic formats (PDF, PDF/A-1a, PDF/A-1b, TIFF, JPEG, HTML, BMP, GIF, PNG);
• Laser printer formats (PostScript, PCL);
• Label printer formats (Zebra, Printronix, Intermec, TEC);
• Production print formats (AFP, IJPDS, PostScript, PDF).
Production Print ES2 offers control and access to printer features, duplex, paper trays, staple, and copies via its
own post-processing capabilities. It does not use the capabilities of Designer ES2 templates the same way as
LiveCycle Output ES2.
Document manipulation and processing
LiveCycle Production Print ES2 offers extensive post-processing and document manipulation capabilities. It
can sort batches of documents and split batches into individual documents or smaller batches based on
document metadata such as State. Sorting can also be accomplished based on the number of pages including
preprinted inserts that will be placed in one envelope to accommodate two or more separate enveloping
machine configurations. Documents can be imposed for different configurations such as two-up, duplex, and
booklet printing. You may mark documents for enveloping machines using OMR marks or barcodes, control
envelope inserts, and add processing tags for operational needs.
Some capabilities rely on use of the post-processing repository. This is a database of formatted pages that can
be manipulated in various ways to create document packages and perform advanced sorting such as
householding, where all documents for one address are treated as one document and placed in one envelope.
The post-processing repository can also be used to store single documents for eventual release to process
them as a batch. It is also possible to create and store queries to release sets of documents. For instance, all of
the documents for the State of Florida could be released for processing as one batch.
Document delivery options
LiveCycle Production Print ES2 provides a number of document delivery options: to a file system, to a network
printer, as an e-mail attachment, or to a fax server, as well as integrated with various archives. Production Print
ES2 provides the capabilities needed to deliver documents in envelopes into the physical mail stream.
Although the focus so far has been on the batch-oriented capabilities of LiveCycle Production Print ES2, it is
also capable of formatting single documents for office printing and label-printing applications.
Representative use cases
LiveCycle Production Print ES2 may be used in many different scenarios. The following items are some
representative use cases.
Example Case 1: A brokerage firm sends trade confirmations to clients. Clients may perform multiple trades a
day and trade confirmations must be printed and delivered to the client by law. Hundreds of thousands of
trades may be processed daily. The costs of mail confirmation must be optimized and householding is one way
to accomplish this, with all confirmations for an account delivered in a single envelope. Due to the volume of
trade and other mailed communications, the brokerage firm has a centralized printing and mailing facility with
an on-site post office. A data set is generated for the day’s trades, and a document for each trade is generated
and stored in the post-processing repository. It is then sorted for householding, placed into one of two streams
for different envelope sizes, and sorted by ZIP code. Once sorting is complete, two AFP print streams are
generated with OMR marks to instruct the enveloping machines. The streams are printed on a 400 page-per-
minute roll-fed printer. Rolls are moved to a page cutter and processed, and pages are processed by the
enveloping machine in order. Hundreds of thousands of envelopes are placed into the mail stream.
Example Case 2: During the day, a call center deals with client account requests and changes. Some
transaction confirmations must be printed and mailed as not all clients have e-mail access. Client services
representatives can select standard letters through an interface, depending on the situation, and any personal
messages needed to clarify the results of interactions. A supervisor must approve some letters and this
capability is enabled with Process Management ES2. Throughout the day, this process is used to generate
letters in response to calls and manage any required approvals. XML data representing one letter is sent to
LiveCycle Production Print ES2 and each is processed using the appropriate LiveCycle Designer ES2 template
and stored in the post-processing repository. Twice a day a mail run is processed and all available letters in the
post-processing repository are processed as a batch. PostScript is used to drive a 100 page-per-minute cut
sheet printer, and documents are marked for enveloping.
Example Case 3: A government agency prints letters of notice using AFP print streams and a legacy solution.
The executive IT committee mandates that all letters of notice must henceforth be archived in PDF/A format
for each client. The AFP print stream is read page by page to the LiveCycle Production Print ES2 post-
processing repository. Each formatted page is represented, and the original AFP TLE information is captured as
metadata so that the number of pages is known. Each individual letter is written as PDF/A in a separate file. The
files are bulk-loaded into the agency’s archive system.
Central Pro Output Server
Document templates for Central Pro Output Server are created using Output Designer, a graphical design tool
that enables users to design, test, and maintain templates containing fixed text, logos, images, barcodes, lines,
boxes, tables, and fields for variable text. It also allows designers to establish colors and fonts. Output Designer
is not as sophisticated as LiveCycle Designer ES2 and does not support fragments or a comprehensive scripting
and event model.
Templates are composed of objects and groupings of objects known as subforms. The relationship between
objects and subforms can be established in Output Designer or controlled through a type of primitive script
called a Preamble. The flow of generated documents is dependant on the data.
Output Designer allows documents to be designed for specific output targets, notably PDF, specific pre-
configured printer models, and fax servers. You can define duplex formatting using templates and select paper
Output Designer supports a range of template languages: Latin 1 (English, French, and German), Latin 2 (Greek
and Russian), and Asian languages (Japanese, Korean, and Chinese).
Documents you may be interested
Documents you may be interested