[jbpm-commits] JBoss JBPM SVN: r5177 - jbpm4/trunk/modules/userguide/src/main/docbook/en/modules.

[do-not-reply at jboss.org]

Author: tom.baeyens at jboss.com
Date: 2009-07-01 10:44:38 -0400 (Wed, 01 Jul 2009)
New Revision: 5177

Modified:
   jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch02-Installation.xml
Log:
JBPM-2363 document purpose of ant installation scripts

Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch02-Installation.xml
===================================================================
--- jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch02-Installation.xml	2009-07-01 13:28:51 UTC (rev 5176)
+++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch02-Installation.xml	2009-07-01 14:44:38 UTC (rev 5177)
@@ -1,10 +1,6 @@
 <chapter id="installation">
   <title>Installation</title>
   
-  <para>This chapter describes how to install jBPM in different 
-    application environments.
-  </para>
-
   <section id="thedistribution">
     <title>The distribution</title>
     <para>Just unzip the jBPM download to some location on your hard drive.
@@ -97,6 +93,23 @@
 
   <section id="antscripts">
     <title>Ant scripts</title>
+	  <para>This chapter describes how to install jBPM in different 
+	  application environments.  Currently we only have a JBoss installation, but we 
+	  soon hope to expand that to incorporate other application environments.
+	  </para>
+	     
+	  <para>As part of the installation, the jBPM configuration 
+	  files will be deployed to the target environment.  Those jBPM configuration 
+	  files themselves should not be changed after installation.  Instead
+	  the installation scripts take a specific configuration parameters 
+	  that will build a valid configuration on the target environment.
+	  </para>
+	  
+	  <para>So it's best to stick to the installations and jBPM configuration files 
+	  as done with these installation scripts.  Customizing jBPM configuration files 
+	  directly, is possible, but not supported. 
+	  </para> 
+	
     <para>As you already saw one example in the demo setup, the distribution a couple of ant 
     scripts:
     </para>