[jbpm-commits] JBoss JBPM SVN: r4377 - jbpm4/trunk/modules/userguide/src/main/docbook/en/modules.
do-not-reply at jboss.org
do-not-reply at jboss.org
Wed Apr 1 11:22:15 EDT 2009
Author: tom.baeyens at jboss.com
Date: 2009-04-01 11:22:15 -0400 (Wed, 01 Apr 2009)
New Revision: 4377
Modified:
jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml
jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch02-Installation.xml
Log:
docs updates
Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml
===================================================================
--- jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml 2009-04-01 14:39:14 UTC (rev 4376)
+++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml 2009-04-01 15:22:15 UTC (rev 4377)
@@ -35,8 +35,6 @@
<title>What is it</title>
<para>jBPM is an extensible and flexible process engine that can run
as a standalone server or embedded in any Java application.
- jBPM can run multiple process languages and it supports multiple
- execution modes.
</para>
</section>
@@ -50,12 +48,8 @@
</para>
<para>This user guide explains the supported way on how to use jBPM.
The developers guide explains more advanced customization options that
- are not supported.
+ are not part of the support offerings.
</para>
- <para>TODO ?Explain what is meant by supported? Shouldn't it be clear to user's that it is more
- geared towards extenders? That they can use it but that there is no guarantee of infinite stability?
- END TODO
- </para>
</section>
<section id="processdefinitionprocessinstanceandexecutions">
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-04-01 14:39:14 UTC (rev 4376)
+++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch02-Installation.xml 2009-04-01 15:22:15 UTC (rev 4377)
@@ -5,16 +5,31 @@
application environments.
</para>
+ <section id="runningtheinstaller">
+ <title>Running the installer</title>
+ <para>Start the installer on a command line like this:</para>
+ <programlisting>java -jar jbpm-installer-${version}.jar</programlisting>
+ <para>The installer has 2 purposes
+ </para>
+ <itemizedlist>
+ <listitem>Install jBPM on your system. This includes the
+ jBPM jars, jBPM sources, third party jars, docs, examples,
+ db scripts and more. This contains all you need to get
+ going with jBPM in your application.
+ </listitem>
+ <listitem>Install jBPM into JBoss, this part can install jBPM
+ into a JBoss server. JBoss will be deployed as a service and
+ be accessible to all applications running on it.
+ </listitem>
+ </itemizedlist>
+ </section>
+
<section id="libraries">
<title>Libraries</title>
- <para>jBPM can run on a JVM without a dependency on any library.
- See object execution mode in the developers guide. But in this
- userguide we'll cover the most common way to use jBPM, which is
- where jBPM stores its process definitions, executions and
- history in a relational database. In that case, hibernate has to
- be added to the classpath. Also some of the jPDL features require
- extra libraries. Therefore, by including all the libraries in the
- lib directory, you get access to all those features and persistence.
+ <para>The lib directory you'll find the jbpm libs and the third party libs.
+ Including all the libraries in the lib directory, is the simplest way to get
+ started. To minimize the number of jars that you need to include, see
+ the developers guide.
</para>
</section>
More information about the jbpm-commits
mailing list