adobe® livecycle® enterprise suite 4 devices with a browser and includes a forms manager web...

Adobe® LiveCycle® ES4 White Paper

Adobe® LiveCycle® Enterprise Suite 4

Organizations are finding it challenging to effectively engage with customers beyond the firewall while making efficient use of back-end resources. The explosion of mobile devices is complicating the situation. IT departments need to make investment choices that allow them to better organize and use distributed capabilities. These capabilities must work in concert with scalable applications that engage customers through appropriate and familiar interfaces.

Effectively reaching and engaging customers while reducing development costs and maximizing return on investment demands a service-oriented approach to application delivery. This type of delivery exposes back-end processes as loosely coupled services that are easily assembled into targeted solutions. Applications must be presented to customers through familiar interfaces that increase user satisfaction, improve process utilization and completion rates, and increase transaction size.

Adobe LiveCycle Enterprise Suite 4 (ES4) dramatically extends the reach of previous LiveCycle releases by adding significant features:

• Mobileworkerscancaptureinformationandworkeffectivelyinthefield,whetheronlineoroffline.• Organizationscanrendernewandexistingformtemplatesonpaper,asPDF,andnowHTML5.• Userscanaccessformsfrommobiledevicesusingonlyawebbrowser.• Organizationscanefficientlycreate,update,manage,andpublishthousandsofformsandtheirassets.

This paper discusses the LiveCycle ES4 architecture and how it employs service-oriented principles that enable developers to rapidly build scalable document applications with excellent user experiences for desktop and mobileworkersandusers.ByleveragingPDFandHTML5intheLiveCycleservice-orientedarchitecture(SOA),organizations can engage with their various constituents, such as citizens, customers, partners, and contractors, to a degree not previously possible. This paper also discusses how LiveCycle ES4 captures and processes data, manages communications, and secures and tracks sensitive information.

Table of Contents 2: LiveCycle ES4

architecture overview 3: Designing document

service applications 4: Enabling mobile

applications 4: Deploying applications 5: Running applications 5: LiveCycle Service

Container 7: Invocation layer 8: LiveCycle Foundation 8: LiveCycle Work

Manager 8: Registry and repository 8: Integrating applications

in the enterprise 9: Correspondence

Management Solution 9: Administering

applications10: Summary

2Adobe® LiveCycle® ES4 White Paper

LiveCycle ES4 architecture overviewThe LiveCycle ES4 architecture encompasses clients, design and development tools, and optional modules. The following sections discuss these themes in the context of designing, running, integrating, and administering customer form and document applications.

Customer Applications, Systems, and Devices

Programming Languages

End-User ApplicationsUser Interface Technologies Cross-platform Clients and Enterprise Portals

Administrative Tools

Standards, Technologies,and Protocols

Consistent Object and Event Models

ConsistentArchitectural Models

ActionScript/Flex

Java™

.Net

Flash® and Flex®

Adobe Reader®

Flex HTML Mobile

HTML + Ajax

PDF + XML

Administration Console

UForms Manager

ser Manager

Forms

MortgageLoan

Flex Applications

Repository

Processes

Service Container

Invocation LayerWeb Services | Java APIs | Remoting | Email | Watched Folders

Service Provider Interface — Foundation Components — ECM Connectors

Fax Servers and Devices Enterprise Information Systems DirectoriesPrinters

Process Engine

Job Management

Monitoring

Event Framework

Versioning

Auditing

ComponentFramework

Service Registry

Dat

a M

anag

emen

t

Mes

sagi

ng

Form

s

Righ

ts M

anag

emen

t

Dig

ital S

igna

ture

Out

put

Gen

erat

e PD

F

. .

.

Rea

der E

xten

sion

s

LiveCycle Services

Services

Databases ECM Repositorys Message Queues Legacy Systems CRX

The LiveCycle ES4 architecture

Start ProcessesTo DoTrackingFlex

Workspace

Start ProcessesTask List

Mobile Workspace

Manage PoliciesAudit Documents

Rights Management Console

Manager View

HTML Workspace

Apply Usage Rights

Reader Extensions Console

DesignerModel and Create Processes

Workbench

PhoneGap™Flash Builder®Adobe CQ Web Content Management

Development Tools

LiveCycle design and development tools work within the application model to coordinate shared assets and dependencies, streamlining the development process and allowing multiple users to work on the same applicationsimultaneously.Design-timerevisioncontrol,security,andauditingcomponentsprovideadministrators with the tools they need to ensure end-to-end management of the application development process. LiveCycle design and development tools include

• LiveCycleFormsManagerES• LiveCycleWorkbenchES• LiveCycleDesignerES

LiveCycle ES4 modules provide reusable services that can be easily assembled into customer document applications. These modules provide wide-ranging and robust support for automating business processes and improvingcommunications.Forexample:

• LiveCycleFormsStandardES4andFormsProES4letorganizationscreate,deploy,andmanageXFAtemplatesandrendertheminpaper,HTML5,orPDFforanyplatform.FormsProES4extendsformstomobiledeviceswithabrowserandincludesaFormsManagerwebapplicationthatmakesiteasytomanagethousands of form assets.

• LiveCycleProcessManagementES4buildsworkflowsandautomatesandprovidesvisibilityintobusinessprocesses,includingextendingprocessestofieldworkerswithmobiledevices.

• LiveCycleES4ConnectorsforECMhelpsintegrateLiveCycleapplicationswithindustry-leadingenterprisecontentmanagement(ECM)systemssuchasEMCDocumentum,IBMFileNet,IBMContentManager,andMicrosoftSharePointServer.

• Otherautomatedprocessestocreate,manipulate,secure,andoutputarchive-readydocumentsareavailable throughtheLiveCyclePDFGenerator,LiveCycleRightsManagement,andLiveCycleDigitalSignatures modules.


AdobeLiveCycleFoundationprovidesanintegratedenvironmentthatenablesthedeployment,execution,and managementofcustomerengagementapplications.IntegraltotheFoundationistheServiceContainer,whichprovidesacommonruntimeenvironmentforallmodulesandassociatedservices.LiveCycleFoundationservices provide facilities that enable solutions to integrate with common IT infrastructures, such as web services,LDAP,JDBC,andFTP.LiveCycleFoundationincludescentralizedtoolsthatsimplifyawiderangeof administrative tasks, including configuration, administration, deployment, user management, forms management, and monitoring. Each tool can be independently administered from a single web interface.

LiveCycleFoundationincludesAdobeCRXandhastheability—inconjunctionwithFormsManager—toactivateanddeactivateassets,search,andprovideformmetadata.ThisinstanceofCRXalsoprovidestheinterfacefortheAdobeFormsPortalsolution,whichrunswithinAdobeCQWebContentManagementorthird-partyportalsthroughRESTcallstolist,search,andpresentaformcardfortemplates.

DesigningdocumentserviceapplicationsLiveCycle Workbench provides integrated form, process, and document services that expose the appropriate functionalitytospecificteammembers.Forexample,formdesignersandbusinessanalystscan workcollaborativelywithinLiveCycleWorkbenchES4.Developerscanextendapplicationfunctionalitythrough data integration, scripting, and extension of module capabilities through the LiveCycle ES4 software developmentkit(SDK).Businessanalystscandefineconceptualprocesses,whileformdesignerscanreuseformfragmentsandscriptcomponentscreatedbydevelopers.Reusablecontentcomponents,suchasformtemplates,servicedefinitions,processdefinitions,policies,DDXfiles,XMLschemas,andimages,andformfragments, such as headers and footers that can be reused across multiple forms, are stored, version-controlled, and protected in LiveCycle ES4. This approach greatly simplifies the maintenance and update tasks related to application development.

ES4

The LiveCycle Workbench Process Design view simplifies business process modeling with concepts such as swim lanes.


LiveCycleWorkbenchunifiesauthoringtasksforforms,processes,documentdescriptionXML(DDX),anddata models. Integration with the repository simplifies management of artifacts, providing support for critical management activities, such as revision control and security. The process design perspective gives business analyststheabilitytocreateprocessesusingstandardBusinessProcessModelingNotation(BPMN)constructs(forexample,swimlanesandpools).TheformdesignperspectiveembedstheLiveCycleDesignerES4functionalityforthegraphicallayoutofXMLformtemplatesthatcanberenderedasPDForHTML5,supportingbothdesktopandmobiledevices.Formsareeasilyintegratedwithback-enddatasourcesand destinations to build applications that automate common tasks, such as data capture. The data model perspective allows developers to write applications at a higher level, thus reducing development time and simplifying data integration.

ThedocumentbuilderperspectiveallowsdocumentauthorstovisuallyconstructDDXcommandfilesthatdynamicallymanipulatePDFdocuments.BasedonEclipse,LiveCycleWorkbenchminimizesupfronttraining,costs, and risks and supports the Eclipse plug-in environment.

Enabling mobile applicationsLiveCycleES4supportsrenderingexistingXFAformtemplatesintoHTML5,extendingcurrentinvestmentsin thesetemplatestomobiledevices.DesignerscancreatenewtemplateswithLiveCycleDesignerfollowingcurrent design principles. The form designer does not need to design multiple templates to target a particular device or render format.

MobileformrenderinginLiveCycleFormsES4ProproducesanHTML5renditionofthetemplatethatmatchestheoriginaldesignorPDFrenderingoftheform,withminorexceptions.Scriptscreatedwithinthetemplatearealso supported, including dynamic forms, validations, and device-specific interfaces such as a date picker, providingarichexperiencefortheuser.Beforetheformissenttotheuser,theinterfaceobjectscanbeupdatedusingJQuerytoprovideacustomform-fillingexperience.Formsarealsoaccessibilitycompliant.

Manyorganizationsarenowequippingstaffwithtabletdevicestoextendworkwhileoutoftheoffice,butthisproducessomechallenges.Forexample,workersmightnothavenetworkaccessinalllocations.Whentheyare able to connect to the network, the application must synchronize captured data into back-end systems for processing.TheLiveCycleProcessManagementES4MobileWorkspaceapplicationallowsworkersinthefieldtocapturedataofflineandthenwhenthenetworkisavailable,theapplicationautomaticallysendsthequeuesubmissionstotheLiveCycleserverforprocessing.MobileWorkspacedatacapturecapabilitiesincludegeolocation,scribble,signature,photos,andvideos.CompaniescancustomizeandbrandtheMobileWorkspace app according to corporate standards.

DeployingapplicationsLiveCycle application-commissioning tasks related to testing, staging, and deploying to production servers are simplified through the use of LiveCycle Archive (LCA) files that automatically package application-related resources in a single archive for transfer between individuals and systems. Administrators can stage or deploy applications to production servers using LiveCycle administrative tools. Staging and production servers do not requiredevelopmenttoolsforapplicationdeploymentandmanagement.


RunningapplicationsThe LiveCycle architecture embraces SOA principles that enhance an organization’s ability to organize and use distributed capabilities. The LiveCycle framework allows enterprise and application architects, business analysts, and form designers and developers to match business needs with capabilities by exposing back-end processes as services that are readily assembled into targeted solutions, greatly improving an organization’s agility to meet changing business needs.

LiveCycle exposes business functionality as discrete services with clearly defined interfaces that allow them to berepurposedandusedasrequiredbyotherapplications.Forexample,LiveCycleRightsManagementES4 providesthesamerobust,document-levelaccesscontroltoallapplicationsrequiringthisfunctionality.Because exposed services often operate across domains of ownership, organizations must be able to declare policies that describe a service in technical and business terms, encompassing security, governance, and relatedfunctions.LiveCycleservicesaredeployedwithXMLdescriptionsthatqualifytheiruse.

LiveCycle Service ContainerThe LiveCycle Service Container, in which all standard and custom LiveCycle services execute, is a single, scalable, and unified runtime environment based on SOA principles. The Service Container functionality includes orchestrating services into synchronous and asynchronous processes, monitoring, auditing, and coordinatedsecurity.Developersandadministratorsalsobenefitfromsimplifiedandfine-graineddevelopment,deployment,securing,andmaintenanceofservices.Whenanasynchronousclientrequestisauthenticated,itispassedtotheJobManager,whichinvokestheservice.

Some of the key attributes of the Service Container are:

Component model—TheServiceContaineremploysanextensiblecomponentmodelinwhichlooselycoupledservicescaninteracttoprovidecompellingcustomerexperiences.LiveCycleFoundationprovidesservices that enable the LiveCycle platform to integrate with common enterprise infrastructure, such as directoryserversoverLDAP,webservices,JDBC,FTP,andfilesystems.LiveCyclealsoencompassesstandard services,suchasLiveCycleReader®ExtensionsES4toenableenhancedfeaturesinAdobeReader,andLiveCycleFormstointegratecustomerengagementapplicationswithLiveCycleservicesandback-end systems.

Orchestration—AkeyaspectoftheLiveCycleruntimeenvironmentisasetoffacilitiesthatorchestrateprocesses to complete complex tasks. Organizations can orchestrate multiple processes together into a new service, provide end-user interaction with LiveCycle services as part of long-lived business processes, and integrate services with third-party products and services.

By orchestrating existing document services, solutions can be easily assembled and tailored to specific requirements.Forexample,considertheneedtocombineaseriesofdocumentstogether,includingaformprefilledwithdataattachedtoaformattedemailtobesenttotherequester.DeveloperscaneasilymeetthisrequirementusingLiveCycleWorkbenchtocombinemultipleservicesintoasingle,orchestratedservicecalledSendCustomDocument.Thisserviceusesasingleinvokeoperationandtakesfulladvantageoftheinvocationmethods available to LiveCycle.

Example of LiveCycle Workbench helping developers combine multiple services into a single, orchestrated service.


Event framework—LiveCycleprovidesaframeworkthroughwhichsolutiondeveloperscanraiseandreceivecustomized events to facilitate communication between running processes. Events can be used to accomplish tasks, such as initiating, terminating, or causing a state change in a process when a dependent operation in a relatedprocesscompletes.InformationaboutaneventisstoredinanXMLvariableavailabletotheeventreceiver. Events can be filtered to determine which event filters are triggered. LiveCycle supports asynchronous, exception, and timer events.

A representative process utilizing the event framework is a loan application in which a CreditCheckComplete asynchronous event is thrown after the credit check completes. This process is initiated when the customer submits a loan application.

�e loan application process uses the event framework to asynchronously signal completion of a credit check.

TheCreditCheckCompleteeventreceiverfunctionsasthestartingpointforthesubsequentApproveApplicant process.

Upon completion of the credit check, additional processes may be invoked, automating additional business activities.


Invocation layerThe LiveCycle invocation layer allows people and external applications to initiate processes via a wide range of mechanisms.Theinvocationlayerinterceptsallservicerequests,performssecurity,auditing,logging,andtransactionmanagementfunctions,andultimatelyinvokesatargetservice.Anyclient,suchas.NET,PHP,oremail, can start a service. This unified invocation framework reduces complexity and improves interoperability.

LiveCycle ES4

Invocation Layer

Client

REST SOAP

Work Manager

ServiceAuthentication

Email Remoting

Mobile /Task Manager Watched Folder

Flow of activity when a client makes an asynchronous request to a LiveCycle service is represented by the blue arrows. Synchronous communication is represented by the gray arrows.

LiveCycle provides several integration methods for invoking a service.

REST—AcommonnameforanHTTPserviceisaRepresentationalStateTransfer(REST)-stylewebservice.RESTisanarchitecturalstylefordistributedhypermediasystems.ProcessescreatedinLiveCyclecanbeinvokedthroughRESTrequests.Forexample,anywebbrowsercanbeusedtoinvokeaLiveCycleprocessandloadarenderedPDFdocumentwithdatathatwassentinanHTTPPOSTrequest.

SOAP—ServiceinvocationinLiveCycleviawebservicesisWS-IBasicProfile1.1compliant.ItsupportsSimpleObjectAccessProtocol(SOAP)withBase64,MIME,DIME,HTTP,MTOM,andSwaRefattachments,theWS-Security1.0standard,dynamicgenerationofSOAPendpoints,andWSDL.Webserviceinvocationallowsbothsynchronous(short-lived)andasynchronous(long-lived)servicerequests.

EJB—ServiceinvocationviaJava™utilizesRemoteMethodInvocation(RMI)andutilizesastronglytypedAPI.Java-basedinvocationmethodsarehighlyoptimizedfordocumentthroughputandprovideexcellentperformance when submitting a large document to a service.

Email—Aservicecanbeinvokedwhenaspecifiedemailaccountreceivesanemail.ThismethodsupportsIMAPandPOP3usingbasicauthenticationorSSL.Designerscandefinepatternsforemailattachmentsandmapdatafromemailheaders,body,andattachments.Forexample,aPDFfileemailedtoaspecifiedaccountcouldinvokeanapplypolicyoperationandreturnthePDFfiletothesendingemailaddress.

Watched folders—ServicescanbeinvokedbywritingfilestonetworkfoldersthatLiveCyclehasbeenconfiguredtowatch.ThefoldersarescannedusingconfigurablefilenamepatternssuchasPDF,andadesiredprocessing action is then taken. Processed output files can be written back to a designated folder for consumption by external applications or users.

Remoting—FlexclientscancallLiveCycleservicesviatheFlexRemoteObjecttag.ThismethodprovidesActionScript® to LiveCycle bridging, supports synchronous and asynchronous invocations, and provides dynamic endpoint creation, saving substantial development resources.

Task manager—ThisintegrationmethodisonlyavailableinLiveCycleProcessManagementES4.Byexposinga service as a task in LiveCycle Workspace ES4, users with appropriate access rights can manually invoke that taskfromtheWorkspaceStartProcesslist.Forexample,anemployeereturningfromabusinesstripcouldstartan expense submission process.

Afteranasynchronousrequestisreceivedviaoneoftheseinvocationmethods,themessagereceiverauthenticatestherequestandcreatesanormalizedinvocationrequest.Itlooksuptheserviceandoperationname and passes this information to the router.


LiveCycleFoundationLiveCycleFoundationprovidesunderlyingfunctionalitycommontoallapplications,includingroutingandmanagementofrequestsfromclients.Whenanasynchronousrequest’sserviceandoperationdetailsareretrieved,theroutercallstheinvocationmanager.AjobIDisthenreturnedtotheclientthroughthereceiver.

LiveCycleWorkManagerOperations performed by services in LiveCycle can be either short-lived or long-lived. Short-lived operations completesynchronouslyonthesamethreadfromwhichtheywereinvoked.Familiartomostprogramminglanguages,theseoperationswaitforaresponsebeforecontinuing.However,manytasksperformedinenterprise processes cannot be expected to complete synchronously. These long-lived operations often span systems or even extend beyond the organization, such as when a client or citizen must complete and submit an application form as part of a larger solution that integrates multiple automated and human tasks. Such operations must continue while awaiting a response.

Long-lived operations perform their underlying work asynchronously, permitting resources to be otherwise engagedwhileawaitingcompletion.Unlikeashort-livedoperation,theLiveCycleWorkManagerdoesnotconsideralong-livedoperationcompletewhenitisinvoked.Anexternaltrigger,suchasasystemrequestinganother operation on the same service or a user submitting a form, must occur to complete the operation. The LiveCycleWorkManagerutilizesindustrystandardJSR-237WorkManagerforApplicationServerstoreceivestatus information. LiveCycle provides a ready-to-use framework for long-lived operations, including tracking and recovery.

RegistryandrepositoryThe LiveCycle repository provides advanced facilities for application developers that greatly enhance the accessibilityandmanagementofassets.TherepositoryseamlesslyspanssingleormultipleclusteredJ2EEsystems, simplifying scalable and failover deployments. Versioning of deployment assets helps structure and control these activities at runtime. Components and services in the central repository are inventoried in respective registries that facilitate browsing, lookup, starting, and stopping components and services, and deploying and undeploying services.

Whenaserviceisinvoked,theregistryandrepositoryareutilizedtoaccesstheruntimeassetsrequiredtocompletetherequest.Clientspollthestatusoftheirasynchronousrequestsandwhenthejobismarkedascomplete, they call the service manager to retrieve the result.

Integrating applications in the enterpriseLiveCycleFoundationprovidesacomprehensiverangeofmethodsforintegration,bothasaserverandasaclient of other processes. In addition to the invocation methods described above, LiveCycle supports several methodsforrequestingtheservicesofotherprocessesintheenterpriseandreturningtheresulttoanapplication. These methods provide flexibility to leverage existing resources.

Web services—Aservicecanbeimplementedasaproxytoanexistingwebservice.Theproxydefinitioninthecomponent.xml file, a single file describing all aspects of the component, contains the information necessary to define the operations and parameters to be exposed as part of the proxy service.

Custom components—DeveloperscanaddtheirownservicesbycreatingstatelessplainoldJavaobjects(POJOs)containingoneormoreoperations.Javadeveloperscanoftenreuseexistingcodewithminimaleffort.ThePOJO,acomponent.xmlfiledescribingit,andanydependencies,suchaslibraries,arecombinedintoasingleJARfile.Whenthecomponentisdeployed,itsmanifesthelpstheservicecontainerrealizethedesiredserviceendpoints,makingthedocumentservicecomponent(DSC)accessibleasaservice.Whenthecomponent is deployed, its manifest helps the service container realize the desired service endpoints, making theDSCaccessibleasaservice.


Connectors for ECM—Connectorsprovidecontentrepositoryservicessuchascheckinandcheckout,lock,and content metadata access. The connector service components receive and output document and other contentobjectsthroughtheLiveCycleprocess,connectingECMtocustomerapplications.

JMS—LiveCyclesupportstheJMSAPIforcommunicatingwithotherJava-basedapplicationsinadistributed environment.

Service provider interface—LiveCycleincludesaserviceproviderinterface(SPI)tostandardexternalauthenticationmethods,suchasLightweightDirectoryAccessProtocol(LDAP)servers,MicrosoftActiveDirectory,andcustomauthenticationandauthorizationmethods.

Foundation services—LiveCyclesupportsanumberofout-of-the-boxcomponentsandlibrariesthatprovidecore functionality for integration with common IT infrastructures. Support includes integration to the user directorythroughLDAP,authentication,ECM,JMS,SOAP,email,andotherback-endsystems,applications,and resources.

LiveCycle Data Services—Thismoduleprovidesreal-timemessaging,guaranteedmessaging,qualityofservice,anddatamanagementservicesforhigh-volumedataexchangeandsynchronizationbetweenFlex,nativemobileclients,HTML5andJavaScript,orAjax-basedapplicationinterfacesandback-endsystems,including enterprise connectivity to SAP.

CorrespondenceManagementSolutionTheCorrespondenceManagementSolutionstreamlinespersonalizedcorrespondencecreationandmanagement. Business users can intuitively assemble individualized customer correspondence with preapproved content blocks, interactive elements, and prefilled electronic forms. It is then delivered securely to the customer, enabling them to fill in the appropriate information and submit it back to continue the process, eliminating wasteful paper submissions.

Administering applicationsThe LiveCycle Administration Console is a web-accessible tool that system administrators use to perform a widerangeoftasks,suchasadjustingportnumberandloggingoptions,andmanagingthedeploymentandconfiguration of LiveCycle applications. Administrators also use the LiveCycle Administration Console to create and manage service endpoints and to deploy applications. It also provides a common authentication management service used throughout the platform and across all services, easing tasks such as defining and configuringusersandgroupsandintegrationwithLDAPs.AdministratorsalsohaveaccesstoJMX-compatibleservice monitoring via the LiveCycle Administration Console.

Administrators can import and manage LCA files that contain an application’s process definitions and related resources,suchasforms,images,andXMLfiles.LCAfilessimplifytheexportandtransferofapplicationsbetween systems, and they can be imported into LiveCycle without stopping the system. This mechanism, which also supports scripted deployment, eases the workload for organizations wanting to stage solutions from development through testing and deployment, and simplifies the sharing and distribution of applications with partners and customers.

10

SummaryLiveCycle is a scalable, unified platform that captures and processes information, delivers personalized communications, and secures and tracks sensitive data to help enterprises create and deliver rich and engaging applications that reduce paperwork, accelerate decision-making, and ensure regulatory compliance. LiveCycle providesthetoolstodevelopanddeliverapplicationsinasingle,J2EE-compatibleandstandards-basedenvironment that eases integration of LiveCycle applications with existing IT assets.

Organizations can use LiveCycle to solve diverse problems, ranging from data capture to complex business transformations.Forexample,governmentagenciessupportprocessesrangingfromelectronictaxsubmissionstofulleGrantapplicationmanagement.Financialservicessolutionsincludeloanapplicationprocessing and account opening that help institutions distinguish themselves in a highly commoditized market.

LiveCycle eases development through an integrated toolset that enables business analysts, developers, form designers, and others to work collaboratively with shared, reusable resources. Central to LiveCycle is a single runtime environment that provides invocation, event management, process management, and other essential functions to foundation and modules. Integration with users and external processes is facilitated through commoninvocationandrequestmethods,suchasFlexremotingandwebservices.

The service-oriented design of LiveCycle greatly simplifies the assembly, deployment, and maintenance of customer engagement applications, combining rich and effective user experiences with back-end processes exposed as services in a consistent way. By assembling customer engagement applications from loosely coupled services in the LiveCycle platform, organizations can reduce development, deployment, and maintenance complexity, align IT systems with business priorities, reduce costs, and improve agility and return on investment.

Adobe Systems Incorporated 345ParkAvenue SanJose,CA95110-2704 USA www.adobe.com

Adobe,theAdobelogo,Acrobat,ActionScript,AdobeAIR,theAdobeAIRlogo,theAdobePDFlogo,Flash,theFlashlogo,Flex,FlashBuilder,LiveCycle,PostScript,andReaderareeitherregisteredtrademarksortrademarksofAdobeSystemsIncorporatedintheUnitedStatesand/orothercountries.JavaisatrademarkorregisteredtrademarkofSunMicrosystems,Inc.intheUnitedStatesandothercountries.Allothertrademarksarethepropertyoftheirrespectiveowners.

©2013AdobeSystemsIncorporated.Allrightsreserved.PrintedintheUSA.

910671752/13