LiveCycle ES Architecture in a Nutshell
Architecturally, LiveCycle ES is an extendable service container and a set of tools to use these services. From the functional point of view, LiveCycle ES services can be grouped as foundation services and solution services.
Foundation services provide basic functionality such as querying or modifying a database, reading and writing to the filesystem, sending and receiving messages from a Java Message Service (JMS) queue, or sending and receiving emails.
Solution services relevant to this chapter are further grouped by LiveCycle ES as two components:
Process Management ES
Data Services ES
Data Services is software that enables messaging between a Flex
frontend and a Java application server. It was known as Flex Data Services
in the previous releases of Flex. The services of the former component,
Process Management ES, allow you to programmatically start an instance of
the process, query tasks available for a given user, complete the tasks,
retry the stalled tasks or terminate them, and more. Importantly, any
business process that you design automatically becomes a new service, with
a single operation, invoke().
All current implementations of LiveCycle ES are built on top of JEE server technology and require an EJB container. For the full list of LiveCycle ES 8.2 services, you can view online references at http://help.adobe.com/en_US/livecycle/8.2/services.pdf.
The ecosystem of LiveCycle ES service components, tools, and technologies shown in Figure 10-8 ...
Get Agile Enterprise Application Development with Flex now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
