The tables belonging to LiveCycle's User Manager are created first.  It looks like the DB2 database is not configured completely to LiveCycle's requirements.Please dbl-check the DB2 DB configuration, make sure that there are tablespaces and buffer pools in there with 8 KB page size or higher.  See h...

Yes, you have to re-start LiveCycle for them to be loaded.

Yes, you have to install Workbench separately.  It is a client/desktop application that you usually do not install on a server.  It is LiveCycle's IDE.

No.Page 11:http://help.adobe.com/en_US/livecycle/8.2/prepareinstallsingle.pdf

LiveCycle 8.0.1 is not tested or supported with Microsoft SQL Server 2008, let alone R2.  LiveCycle ES2 is supported on SQL Server 2008 but not R2.  But it might work nevertheless.This document is the authoritative document on supported platforms for ES2 (pages 10-15):http://help.adobe.com/en_US/liv...

Please see the second post (from the top) of this e-mail thread.

If you post the complete appserver log (from startup), we might be able to help.  When there are services that are unable to start, usual culprits turn out to be earlier configuration steps that went badly.

Use port 443 and the same idea should work.

LiveCycle ES and ES2 are supported on the enterprise server versions of Red Hat Linux and Novell SUSE Linux.

XMLForm is a process, not a thread.  If you see 8 of them getting started, you are indeed utilizing the system (it is seeing 8 concurrent requests or more).  I'm not sure about what your load reports are tracking but the overall CPU utilization of the server instance is a better indicator.