
7
LIVECYCLE ES4 OVERVIEW
About Adobe LiveCycle Enterprise Suite 4
Last updated 1/15/2015
This illustration provides a closer view of how the key product components fit together within the server architecture.
The development area includes Workbench tools and the repository. Development of forms and Guides (deprecated),
process flows, and related collateral is done in Workbench. The Eclipse-based development environment can also
include Flash Builder (available separately). You can use Flash Builder to develop RIAs, create custom components for
use in Guides (deprecated), customize Workspace, and more. (See
LiveCycle Workspace Help.)
Note: The Flex Worksapce is deprecated for AEM forms. It is available for the LiveCycle ES4 release.
The resultant design assets are stored in the repository, which provides versioning and maintains resource
dependencies. This central storage and maintenance model promotes the reusability of artifacts, enables developers to
collaborate on application development, and provides security within the development environment.
The common invocation layer ensures consistent interaction with the server through various invocation methods. It
supports programmatic and non-programmatic invocation methods, including web services, Java APIs, watched
folders, and email-based invocation methods. All of these invocation methods are available to use with any service.
LiveCycle provides integration adapters to ensure compatibility with your enterprise back-end systems. These back-
end systems include user directories, authentication systems, ECM systems, web services, JMS, Java Remote Method
Invocation (RMI), and email.
The LiveCycle service-oriented architecture maximizes the scalability and reusability of services. It ensures that you
can easily add, remove, and upgrade services. User authentication, service deployment, and invocation are all managed
within a common server infrastructure to ensure system security and performance.
Using cross-platform clients, such as Adobe Reader, Flash Player, and Adobe AIR™, you can ensure that your
applications will be easily accessible, immediately usable, and consistent across platforms and devices.
The Adobe AIR run time lets developers use proven web technologies to build RIAs that deploy to the desktop and run
across operating systems. Adobe AIR offers an exciting new way to engage customers with innovative, branded,
desktop applications without requiring changes to existing technology, people, or processes.
Customer Applications, Systems, and Devices
Programming Languages
End-User Applications
User Interface Technologies
Cross-platform Clients and Enterprise Portals
Administrative Tools
Standards,
Technologies,
and Protocols
Consistent
Object and Event
Models
Consistent
Architectural
Models
ActionScript/Flex
Java™
.Net
Flash® and Flex®
Adobe
Reader®
Flex
HTML Mobile
HTML + Ajax
PDF + XML
Administration Console
U
Forms Manager
ser Manager
Forms
Mortgage
Loan
Flex
Applications
Repository
Processes
Service Container
Invocation Layer
WebServices |Java APIs |Remoting | Email|Watched Folders
Service Provider Inter face — Foundation Components — ECM Connectors
Fax Servers and Devices Enterprise Information Systems DirectoriesPrinters
Process Engine
Job Management
Monitoring
Event Framework
Versioning
Auditing
Component
Framework
Service Registry
Data Management
Messaging
Forms
Rights Management
Digital Signature
Output
Generate PDF
. . .
Reader Extensions
LiveCycle Services
Services
Databases ECM Repositorys Message Queues Legacy Systems CRX
The LiveCycle ES3 architecture
Start Processes
To Do
Tracking
Flex
Workspace
Start Processes
Task List
Mobile Workspace
Manage Policies
Audit Documents
Rights Management Console
Manager View
HTML Workspace
Apply Usage Rights
Reader Extensions Console
Designer
Model and Create Processes
Workbench
PhoneGap™
Flash Builder
®
Adobe CQ Web
Content Management
Development Tools
Kommentare zu diesen Handbüchern