(i) Construction of JPBM environment

When using JBPM, one of the things called graphical process designer, graph process Designer (GPD), is the ability for a user to design a business process through graphical drag-and-drop, property setting, and so on, creating and presenting a business process model. This model is typically a. jpdl.xml file in Jbpm4, followed by the JPDL specification, which is a "process definition" file that is interpreted by the workflow engine at run time to generate a "process instance."

jbmp4.4 Download: http://sourceforge.net/projects/jbpm/files/jBPM%204/

First, installation
Eclipse integrated GPD, due to the JBPM4 GPD integration Eclipse has version limitations, namely eclipse3.5.x. and myeclipse8.5, the corresponding eclipse version is Eclipse 3.5.2.

After myeclipse8.5, the software update and the first few versions are not the same, first help-->myeclipse Configuration Center, go in, click Software, and then add from Archive File, select ${jbpm.home}/install/src/gpd/jbpm-gpd-site.zip file, take a name such as JBPMGPD, expand the node, right-click, Add to Profile (do not bring the source), and finally click Apply Change (pay attention to disconnecting the network cable, if connected to a network cable, it may be a long time, because MyEclipse will automatically update other files online), at this time open window-perferences there will be a JBPMGPD column, restart OK. (These steps are easy to make mistakes, be careful, I tried, it is best to configure JBoss First, when you click on Apply change to see if the number is correct).

After success, you will see the JBoss jbpm section in Window-->preferences. Then select runtime locations to configure the runtime environment, click Add, enter a name such as JBPM44, and then select the JBPM installation directory, OK.

Second, the configuration
Next, define a JBPM user Libraries for your workspace, which can be used to consume all of JBPM's dependent library files. If you create a new JBPM project, simply add the JBPM user library to the build path.
1, select Window-->preferences
2, select the Java-build path-user Libraries option, click New, enter the name JBPM Libraries.
3. Click Add jars to locate the Lib directory under the JBPM installation directory.
4. Select all the jar files in the Lib directory and click the Open button.
5, select the newly created JBPM Libraries, click Add Jars, and select the Jbpm.jar file under the JBPM installation directory
6, click Open
7, select Sourceattachment under Jbpm.jar.
8, click Edit, in the Source attachement Configuration dialog box, click the External Folder button.
9, locate the SRC directory under the JBPM installation directory.
10, click the Choose button for JBPM. Jar Association source code.
11, click the OK button two times to close all the dialog boxes, done.

Add JPDL4 schema validation, just to say that JBDL is JBPM's unique process definition language, which describes the business process in the form of an XML file. Because the graphical process designer provided by JBPM is not fully functional, so in many cases we need to directly edit the JPDL XML source code, so it is best to specify the schema for JPDL XML, so that you can use the shortcut key "alt+/" to quickly call out the grammar question is, and help you verify the JPDL syntax error.
The process for configuring this schema in Eclipse is:
1, select Window-preferences, select Xml-->xml CataLog.
2, click Add, click File System, then select the ${jbpm.home}/src/jpdl.xsd file, OK, configuration complete.

After the top of the whole, we now hand in hand, to get a program run, look good.

Third, testing
In the JBPM4 package, which contains rich sample processes and test code, these examples are imported into your eclipse species as a examples project for learning and research, step: file-->import, and then select ${jbpm.home} The next examples,ok is complete.

After configuring the JBPM4 user-dependent library, all of the unit test classes (inherited from Jbpmtestcase) in the sample can be run as JUnit test and the Run As-->junit Test command is selected on each test class. Run a few to see it.

    of course, all-purpose ant can also help you publish your program. First, select the window-->show view-->other-->ant-->ant command to open Ant's attempt, and then drag the ant build file from the sample project Build.xml from the package view to the Ant view. You can use the Ant build Task (target) To publish the sample process to the target server, the details of the deployment process, later.