JBoss in the Virtual Appliance does not have a "default" configuration.  You should not start it with the command "./run.sh -c default".Please read the readme.pdf before you use it:http://d2x45prcet210j.cloudfront.net/readme.pdf

Configuring SSL is a purely WebSphere Application Server (AS) administrative task.Although LiveCycle's documentation provides you with instructions on how to configure WebSphere AS for SSL, it is better if it is done based on your IT shop's WebSphere security policies.  This is because in many cases...

I tested it from a Windows command prompt (using the Windows FTP client) and it does not work right now.  Adobe is closed this week but we will get this fixed next week.  Sorry about the inconvenience.ftp eftp.adobe.comConnected to eftp.adobe.com.220-GlobalSCAPE Enhanced File Transfer Server (v. 5.0...

JAVA_HOME might be set but the environment variable PATH should contain the following entry, among other things:$JAVA_HOME/bin:Verify using the command:which javaand make sure it is not picking up any 1.4.2 JDKs that might be present.Also, Fedora is not a supported Linux distribution but that should...

This blog entry might help:http://blogs.adobe.com/livecycle/2009/01/initializing_livecycle_databas.htmlThe bootstrap servlet is part of the LiveCycle EAR file.If it says that it "Could not connect to bootstrap servlet", the following might be at work:- The EAR file is deployed but not "Active", just...

Here's the direct URL ("Permalink"):http://blogs.adobe.com/livecycle/2008/11/livecycle_mysql_jdbc_data_sour.html

Multiple, non-clustered LiveCycle instances against a single database is neither tested, nor supported. For each instance, you'd need a separate database (with multiple sets of tables, views and sequences). All changes have to be repeated for every instance you have.This technical whitepaper from Ad...

Based on the description of your orchestration, this is "normal".Can you use CPU-Z and report the type of CPUs the server has?http://www.cpuid.com/cpuz.php

Does this test work in your environment?http://blogs.adobe.com/livecycle/2009/02/validating_livecycle_process_m.html

You need to set the following environment variables with valid values:JAVA_HOME and PATHexport JAVA_HOME=/opt/java/jdk1.5.0_17export PATH=$JAVA_HOME/bin:$PATHVerify with the following commands:which javajava -version