Specifications
11
LIVECYCLE ES4 OVERVIEW
About Adobe LiveCycle Enterprise Suite 4
Last updated 1/15/2015
Deployment phases
In an enterprise-wide deployment, the system is set up so that several people have different roles in the system. For 
example, an IT administrator installs and deploys the production system (and possibly the testing system), and sets up 
the security infrastructure. Form developers design forms; process developers design processes; administrators deploy 
services, manage server performance, and so on. The system integrates with the organization’s back-end database 
infrastructure. 
Typically, various users use LiveCycle in three phases: 
Development:  Form authors, process developers, or programmers use the development and programming tools to 
create processes and custom applications for deployment. 
Staging:  Administrators and testers deploy and test the applications in a system that mimics the final production 
deployment scenario.
Production:  Administrators deploy, monitor, and maintain services and applications. End users interact with services 
within and outside your organization (and within and outside the firewall). 
Administrators move all assets (such as PDF forms, images, process diagrams, and other files required) for an 
application to work from one phase to the next. Developers typically package all application assets into a LiveCycle 
archive (LCA) file and transfer it from development to staging to production.
?
Firewall• Firewall • Firewall
Development
LC 1
LC 1
 LiveCycle 
Archive
Permanent
Storage
 No    Yes
 Acceptance? 
LiveCycle 
SDK
LC 2
LC 3
Workbench 
Customers 
beyond 
rewall
Flex Builder
LC 1
LC 2
LC 3
Staging Production










