A common question frequently asked by developers new to LiveCycle is – just how big is this thing? As the discussion below proves, you need a laptop/desktop with at least 4 GB of RAM to get started. Here’s the total footprint of a Windows development desktop with LiveCycle…
DISK
| Component | Disk Space |
|---|---|
| LiveCycle ES2 |
1.90 GB
|
| LiveCycle Workbench |
0.90 GB
|
| LiveCycle Designer |
0.40 GB
|
| LiveCycle Data Services 3.0 |
0.17 GB
|
| Microsoft Office 2007 |
0.57 GB
|
| Adobe Acrobat Pro Extended |
1.60 GB
|
| Windows 7 |
16.2 GB
|
| JBoss AS 4.2.1 |
2.3 GB
|
| Sun "HotSpot" 1.6 JDK 64-bit |
0.18 GB
|
| MySQL |
0.78 GB
|
|
TOTAL
|
25.00 GB
|
MEMORY
| Component | Peak Working Set |
|---|---|
| JBoss 4.2.1 (java.exe) |
2.10 GB
|
| Gemfire TCP Locator (java.exe) |
60.0 MB
|
| MySQL (mysqld.exe) |
252.0 MB
|
| LiveCycle Designer (FormDesigner.exe) |
75.0 MB
|
| LiveCycle Workbench (javaw.exe) |
290.0 MB
|
| XMLForm.exe (4) |
66.0 MB x 4
|
| pdfgen.exe + java.exe (PDFG) |
100.0 MB
|
| Firefox browser with Workspace loaded |
230.0 MB
|
|
TOTAL
|
3.3 GB
|
Free RAM on the 4 GB Windows (64-bit) machine instance was 0.5 GB. JBoss heap size was set to 1.5 GB minimum and maximum. Size of the Permanent Generation was set to 0.5 GB minimum and maximum.
JConsole reported a total of 295 JVM threads (Windows java.exe process had 305 native threads) during single-user tests with about 38,600 classes loaded.
Good information, thanks!Further to the topic of “…developers new to LiveCycle…”, let me give a hypothetical scenario: A gov’t agency is looking to web-enable the front end to a legacy client-server system w/ a WebSphere middle tier and a DB2 back-end. The new front end is expected to consist of all LiveCycle developed components, and will be given its own dedicated data-store (maybe another DB2 database, maybe XML) for items (mostly form data) that will ultimately be stored in the primary production database.Given these functional objectives and w/ an understanding devlopment environments for the the middle tier and back-end exist, what needs to be installed/configured on the developer workstations?My guesses (based on your information):LiveCycle ES2LiveCycle WorkbenchLiveCycle DesignerLiveCycle Data ServicesAdobe Acrobat Pro ExtendedWebSphere Application clientOPTIONAL: Local db2 (UDB)Am I close to the mark?Any advice would be greatly appreciated.
Doug:I think you are on the mark. I would put WebSphere Application client also under OPTIONAL.
Jayan,Again, I wanted to say thanks for your help here.(I later began reading the prepareinstallcluster.pdf document from the Adobe LiveCycle site and found that document to be very helpful as well!)A follow up question (specific to workstation security at this site):The Windows workstation administrative folks have determined that software engineers should only have “Power User” rights and NOT full administrative control over their development workstations. Would you see this configuration as a hindrance to LiveCycle application development (assuming the local installs are handled by machine administrators, of course)?Thanks,Doug
Neither Adobe Acrobat, Designer nor Workbench require the user to be a member of the ‘Local Administrators” group.