any web container would work since we only rely on servlet capablility. But we test on Tomcat primarily).
any web container would work since we only rely on the servlet capablility. But we test on Tomcat primarily).
<itemizedlist>
<listitem>
<para>Copy the downloaded activiti-explorer.war to the webapps directory of Tomcat.</para>
...
...
@@ -104,6 +104,26 @@
</para>
</section>
<sectionid="activiti.setup.database">
<title>Activiti database setup</title>
<para>As said in the one minute demo setup, the Activiti Explorer runs an in-memory H2 database by default.
To run the Activiti Explorer with a standalone H2 or another database the db.properties in the WEB-INF/classes of the Activiti Explorer web application
should be changed.
</para>
<para>In addition, be aware that the Activiti Explorer generates demo user and groups, process definitions and models by default.
To disable this, the activiti-standalone-context.xml file in the WEB-INF folder should be changed. To disable the demo setup fully you can use the following snippet
of the demoDataGenerator bean definition. But as you can see you can also enable and disable items individually.
Since we've configured our ProcessEngine to use the same database as the demo setup is using (run the <linklinkend="demo.setup">demo setup</link> if you haven't done it yet'),
Since we've configured our ProcessEngine to use the same database as the demo setup is using,
we can now log into <ulinkurl="http://localhost:8080/activiti-explorer/">Activiti Explorer</ulink>
(login with fozzie/fozzie), and we fill find that we can start our business process after
selecting the <emphasis>Processes</emphasis> page and
