What is Java Workflow Editor?
Java Workflow Editor is a graphical editor for creating, editing, managing and reviewing WfMC XPDL process definition files. Workflow management is an evolving technology with lots of vendors claiming their approach is the best. We have chosen an approach which relies on WfMC and XPDL, thus supporting efforts to establish the standard. Java Workflow Editor is based on version 2.1 of the XPDL XML schema published by WfMC. The editor makes creating and editing XPDL easy. It represents all XPDL elements graphically through property panels and a graph component using BPMN graphical notation, to give the user a better understanding and an overview of the process definitions. Various functions help in finding specific activities, participants, applications, errors in the model, etc. The final output of the editor is an XML file (using the standardized WfMC XPDL schema) which can then be interpreted and executed by all WfMC XPDL compliant workflow engines.

System requirements
  • Minimum JRE version is 1.6
  • Graphics card with minimum resolution of 1024x768 with 16-bit color depth.
  • 128Mb RAM

Java Workflow Editor on an eComStation machine with Open JDK

Installing Java Workflow Editor
Download twe-4.4-1.zip. Next versions needs Java 7 or later. Open the zip file and copy the directory (folder) to a drive of choice. Use the following installation command file to install the program.
@echo off
set BEGINLIBPATH=[drive: java]\JAVA160ga5\bin
set path=[drive: java]\JAVA160ga5\bin
set CLASSPATH=
[drive: twe-4.4-1]
cd [drive: twe-4.4-1]\twe-4.4-1
java -cp [drive: twe-4.4-1]\twe-4.4-1\lib\ant.jar;[drive: twe-4.4-1]\twe-4.4-1\lib\ant-launcher.jar;
[drive: twe-4.4-1]\twe-4.4-1\lib\xercesImpl.jar org.apache.tools.ant.Main 
-DSYSTEMROOT=[drive: twe-4.4-1]\twe-4.4-1 2>twe-instalbugs.txt
The last three lines are actual one line, but I had to break it up in parts. I use 2 separate folders (directories), one for Java and one for Java Workflow Editor with the files created by this program. The references used in the cmd file;

  • [drive: java] = drive with Java
  • [drive: twe-4.4-1] = drive with Java Workflow Editor (TWE stands for Together Workflow Editor)

should be replaced with real drive letters. Save the file and name it "TWE-install.cmd" or use the install file from the distribution. This file is copied to the "twe-4.4-1" folder (directory). Furthermore, different paths?, adjust according to your needs. The installation starts automatic as soon as you have launched the file. You get something like this in your screen;
[I:\PROGRAMS\twe-4.4-1]TWE-install
Buildfile: I:\PROGRAMS\twe-4.4-1\build.xml

init:

configure:
    [touch] Failed to change file modification time
     [copy] Copying 1 file to I:\PROGRAMS\twe-4.4-1\tmp
     [copy] Copying 1 file to I:\PROGRAMS\twe-4.4-1
   [delete] Deleting directory I:\PROGRAMS\twe-4.4-1\tmp

BUILD SUCCESSFUL
Total time: 3 seconds
Of course it doesn't understand a thing, "build succesful", my you know what. It thinks its Linux if I see what it build. The best thing is not to use the startup batch. I examined the startup batch and translated this into one which can be used for OS/2-eCS.

The used cmd file
Java Workflow Editor works well with Open JDK in OS/2-eCS. I have a twe.cmd file with the following contents; 
@echo off
SET CLASSPATH=
set BEGINLIBPATH=[drive: java]\JAVA160ga5\bin
set path=[drive: java]\JAVA160ga5\bin
[drive: twe-4.4-1]
cd [drive: twe-4.4-1]\twe-4.4-1
javaw -Xmx128M -Duser.home=[drive: twe-4.4-1]\twe-4.4-1 -DJaWE_HOME=[drive: twe-4.4-1]\twe-4.4-1
-Djava.ext.dirs=[drive: twe-4.4-1]\twe-4.4-1\lib org.enhydra.jawe.JaWE %1 2>twe-bugs.txt
The last two lines are actual one line, but I had to break it up in parts. I use 2 separate folders (directories), one for Java and one for Java Workflow Editor with the files created by this program. The references used in the cmd file;

  • [drive: java] = drive with Java
  • [drive: twe-4.4-1] = drive with Java Workflow Editor

should be replaced with real drive letters. Save the file and name it "twe.cmd" or use the commandfile from the distribution. This file is copied to the "Java Workflow Editor" folder (directory). Furthermore, different paths?, adjust according to your needs.
Create a new program object. Specify the path and file name: "[drive: twe-4.4-1]\twe-4.4-1\twe.cmd". In the tabpage Session check the boxes "OS/2 window", "Running as an icon" and "Close Window to end program". In the tabpage General you can enter the name "Java Workflow Editor".

Parameters / options explained
  • The statement "-Duser.home=[drive: twe-4.4-1]\twe-4.4-1" will ensure that Java Workflow Editor will save all necessary files in own directory instead of saving them in the home directory.
  • The addition "2>twe-bugs.txt" ensures that errors are saved in the file "twe-bugs.txt". The 2 in "2>" is not a typo! See this as an option if something does go wrong, the file grows rapidly because the program records what it is doing!
  • The specification "-Xmx128m" indicates the maximum limit of the used memory.
  • The other specifications comes from the created run.bat file from the installation.

Download
In the file you can find the above command files (all drive letters are on set to C:) and an OS/2 Java Workflow Editor icon: TWE-eCS.zip.

revision May 6, 2016