3.4. Important Notes About Quickstarts

Each quickstart needs to be built and deployed using Apache Ant.

Each quickstart uses the samples/quickstarts/conf/quickstarts.properties file to store environment-specific configuration options such as the directory where the server was installed. You must create a quickstarts.properties file that matches your server installation. An example properties file (quickstarts.properties-example) is included.

Each quickstart has different requirements. These are documented in their individual readme.txt files.

Not every quickstart can run under every server profile.

The jBPM quickstarts require a valid jBPM Console user name and password. Supply these by adding them as properties in the SOA_ROOT/jboss-as/samples/quickstarts/conf/quickstarts.properties file:

jBPM console security credentials

# jBPM console security credentials
jbpm.console.username=admin 
jbpm.console.password=adminpassword

The quickstarts that are affected by this requirement are bpm_orchestration1, bpm_orchestration2, bpm_orchestration3 and bpm_orchestration4.

You can only execute some of the quickstarts (such as groovy_gateway) if the server is not running in headless mode. (The JBoss Enterprise SOA Platform is configured to launch in headless mode by default.)