| Wiki Markup |
|---|
h3. Building the Activiti Modeler for the first time |
...
Check out the excellent documentation by Signavio: [http://code.google.com/p/signavio-core-components/wiki/InstallationInstructions |
...
Set the following properties and follow the instructions of the next section ('Preparing for a release') to get a working Activiti Modeler:
| Code Block |
|---|
] Set the following properties and follow the instructions of the next section ('Preparing for a release') to get a working Activiti Modeler: {code}war = activiti-modeler configuration = Activiti{code} All other properties are optional. |
...
h3. Preparing for a release |
...
* Update your local version (svn up). |
...
* Update the version property in the build.properties file. |
...
* Here is my build.properties for reference (Joram): |
...
| No Format |
|---|
{noformat}
# This is the Signavio Core Components configuration file. Most users only have to configure this file.
# The path to your Apache Tomcat webapps folder
dir-tomcat-webapps = /apache-tomcat-6.0.16/webapps
# The path to your jBoss deployment folder
dir-jboss-webapps = /jboss-5.1.0/server/default/deploy
# The folder the war file(s) is/are stored
target = target
# The version of the application. If you want to integrate the Signavio Core Components into
# your own software product, you can align the version number.
version=5.0-SNAPSHOT
# The name of the war file, if you use the all-in-one-war build target
war = activiti-modeler
# The configuration you want to use. This is the name of the folder in the 'configuration' project
# that contains the configuration and skin files. The following configurations are available:
# default, Activiti, jBPM
# You can also add your own configuration in the 'configuration' project.
configuration = Activiti
# The URL of your server. Format: http(s)://<domain>(:<port>)
# Do not add a trailing slash here!
host = http://localhost:8080
# The path on your system the directories and diagram files are created.
# Do not use \ ! Always use / !
fileSystemRootDirectory = ../../../workspace/activiti-modeler-examples
|
...
{noformat} * Build the war using (on the root of signavio-core-components): |
...
{code |
...
}ant build-all-in-one-war |
...
{code}The war file will be stored in the _target_ folder. |
...
* Set or verify in _user.home/.activiti/build.properties_ the {{modeler.target.folder}} property to point to the _target_ folder, into which the Activiti Modeler has been built. |
...
eg. |
...
{code |
...
} modeler.target.folder=/Users/jbarrez/Development/workspace/signavio-core-components/target |
...
{code} * Call the Ant target {{patch.activiti.modeler}} in _distro/build.xml_ in the Activiti codebase. The easiest is to create a small script that does that for you on the root of the Modeler source: |
...
This will patch the modeler war to include the Cycle plugin and the Activiti stencil set. |
...
{code |
...
} ant -f /Users/jbarrez/Development/workspace/activiti/distro/build.xml patch.activiti.modeler |
...
{code} The patched war will be created in */target/patched |
...
Testing the war
...
* h3. Testing the war # Checkout the to-be-released (tag) version |
...
# Edit _distro/src/setup/build.xml :_ change the property 'activiti.modeler.download.url' to the war on your local system. Example: |
...
{code |
...
}<property name="activiti.modeler.download.url" value="file:///Users/jbarrez/Development/signavio/signavio-core-components/signavio-core-components-read-only/target/patched/activiti-modeler-${activiti.version}.war" /> |
...
{code} # Comment the _'skip.deploy.activiti.modeler=true_' property in the $user.home/.activiti/build.properties |
...
# Build a new activiti distro (in qa dir: _ant build.clean.distro_ or in distro dir: _ant clean distro_) and run the demo setup (in qa dir: _ant test.demo.setup_ or in distro/target/activiti-$\{activiti.version\}/setup/ dir: _ant demo.setup_). |
...
# Verify if the [modeler|http://localhost:8080/activiti-modeler/p/explorer] is correctly working. h2. {color:#027dc0}Changing the location of the process model repository{color} After running the demo setup, process XML files are stored in the _workspace/activiti-modeler-examples/_ folder. The location of the file-based repository can be switched by changing the *fileSystemRootDirectory* property in the *(exploded)activiti-modeler.war/WEB-INF/classes/configuration.properties* file. h2. {color:#027dc0}Changing the host of the Modeler{color} After running the demo setup, the Activiti Modeler will accessible only on the _localhost_ address. When you want to change the host of the Modeler, e.g. to run it centrally on a server, change the *host* property in the *(exploded)activiti-modeler.war/WEB-INF/classes/configuration.properties* file.> cat configuration.properties host = http://192.168.1.101:8080 fileSystemRootDirectory = /Users/jbarrez/Development/model-repo h2. {color:#027dc0}Configuring Apache Tomcat for Activiti Modeler{color} In the context of the activiti demo setup Apache Tomcat is configured correctly. If Apache Tomcat is configured manually we need to make sure that UTF-8 encoding is enabled for accessing the filesystem and for URI-encoding. To this end, * ensure that *\-Dfile.encoding=UTF-8* is added to the java-call in ${catalina.home}/bin/catalina.bat or${catalina.home}/bin/catalina.sh, respectively. * ensure that *URIEncoding="UTF-8"* is set on the HTTP-connector in ${catalina.home}/conf/server.xml, i.e. like this:<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" /> |