If that's the case, it looks like the messaging engine is having trouble getting an exclusive lock on its mesage store tables in the DB (that all start with SIB*):http://blogs.adobe.com/livecycle/2007/07/what_are_those_sibtables_in_my.htmlSince this is a new install, you can safely drop them.  Shut ...

A "messaging engine" is hosted by a WebSphere application "server" instance or cluster of instances.  In the case of a LiveCycle cluster, we recommend that a separate appserver cluster be created to host just the WebSphere messaging engine.Is that done?  Have you started that JMS cluster (it is sepa...

It looks like you chose com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper as the datastore helper class and you shouldn't have.  More here:http://blogs.adobe.com/livecycle/2007/10/livecycle_for_the_sql_server_2.html

In ES2, LiveCycle's memory requirements exceed that afforded by 32-bit JDKs in Windows /Linux (1.2 - 1.5 GB).

There is no optimal memory setting for LiveCycle.It depends on the components you have chosen to deploy.  If Content Services ES2 is deployed, your heap size settings should be about 2 GB, otherwise 1.0 - 1.7 GB might suffice.http://blogs.adobe.com/livecycle/2010/01/optimal_livecycle_es2_jboss_ru.ht...

Windows 2003 Server is supported and tested for ES2.

Please use a tool such as TCPView to see which process running on your machine is using port 1100:http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

It'll help you scale as long as your server instance has enough CPU cores and memory.

The process pool size for XMLForm is controlled by the property:com.adobe.xmlform.bmc.POOL_MAXIf you want to increase it from the default 4 to let's say 8, pass the following in as a JVM init argument in run.sh:-Dcom.adobe.xmlform.bmc.POOL_MAX=8

1) Change the WC_defaulthost port of the appserver instance from 9080 to 802) Make sure "80" is listed as a "Host alias" for the "default_host" virtual host or another virtual host you have created exclusively for LiveCycle3) Re-start the appserver instance4) Check the SystemOut.log and verify that ...