Jawe Workflow modeling and shark Workflow Engine Example Description

First, Jawe Workflow modeling
1. Create a Package
Click New Package.
Figure 1.1
Type: Text/java, Text/javascript and Text/pythonscript have these three species.
2. Create Application
2.1 Create a new application
Figure 1.2
A new STRONGIT_APP1 application is created here, and a new one of the following form parameters is string type.
2.2 Create a new form parameter
Figure 1.3
2.3 Again create two applications
The same way to create two more applications.
Figure 1.4
3. New Workflow Related data
Figure 1.5
4. New Process
4.1 Creating the Process
Figure 1.6
Right-click to select Action for the procedure
Figure 1.7
4.2 Modifying process Properties
Figure 1.8
4.3 Editing process
New contributor


Figure 1.9
4.3.1 New Contributor
Figure 1.10
There are two new names for employees and department managers who are participants in the two roles.
Figure 1.11
You can create a new activity only after you have created a new contributor.
4.3.2 New Activity
Activity type has start/end, child activity, block activity and normal activity and path activity, after creating good activity, connect an activity with transfer line.
In this example, only the start/end and normal activities are used.
The start/end activity does not have a property setting.
The following is a description of the Leave request activity:
(1), General Property Description
The name is changed to: Leave Application (is the name of the activity)
Start mode: Change to Manual
Figure 1.12
(2) Create a new tool in the tool properties associated with the previously defined application
Figure 1.13
The application in the new tool interface selects the "Application" application defined previously. If the previously defined application has formal parameters, be sure to create a new actual parameter that matches the formal argument. The actual parameter here is the workflow-related data defined previously.
Figure 1.14
Figure 1.15
Such a simple activity is defined, which defines the relevance of the activity to the application.
4.3.3 defines manager approval and archiving activities in the same way.
After the process has been defined well, the workflow modeling process is tested in legality.
Figure 1.16
Second, in the face of the newly built workflow modeling process to configure
2.1 Loading modeling files
Start shark Service and admin end program, login to package management
Figure 2.1
Click the Load button below
Figure 2.2
Select the Xpdl file that was modeled on the previous step. Click Load to load again, and the contents of the Red Line box will appear in Figure 2.1.
2.2 Associated Users
Select, user management->mapping interface, click the "Add" button, the figure 2.4 Interface for User Role Association.
Figure 2.3
Figure 2.4
Here select the employee role to associate with the QQ user, and the department manager role is associated with the Admin user. The red box contents of Figure 2.3 appear after the association.
2.3 Application Association
Select Application Mapping and click the "Add" button to appear in Figure 2.6 interface.
Figure 2.5
Figure 2.6
Here is an application that associates a Java class,
In Select application is the application of the modeling definition.
Figure 2.7
The Select tool Agent tool Proxy is shark provides all of the agent tools, because the application is a Java class to select Org.enhydra.shark.toolagent.JavaClassToolAgent
Figure 2.8
The following application name is the full name of the application class class, which must be in classpath.
This class must have a static Execute method, and if the application defined above has formal arguments, use the
Import Org.enhydra.shark.api.internal.toolagent.AppParameter; As a parameter.
The following code:

public static void Execute (Appparameter a) {
System.out.println ("Application app1+a:" + a.the_value.tostring ());
}
Figure 2.9
Click the Apply button and the contents of the red box appear in the figure 2.5 interface.
2.4 Instantiating an instance of a process
Select the process instantiation management interface, select the previously loaded flow, and click the "Instantiate" button below to create a process instance.
Figure 2.10
2.5 View User Work list
Select Worklist management interface, select "QQ", the user "QQ" work list can see the red line out of the work is just created a process instance work item.
The buttons in the Red line box in Figure 2.11 can change the performer of a work item.
Figure 2.11
Figure 2.12
Figure 2.13
2.6 View instance progress and instance management
Select Process Monitor, select the flow, the following will list all the instances, click on the right side of the area to see progress, which is the process is currently in which activity. The following figure the yellow active node represents the active node that is currently in place.
Below are some action buttons to manage the currently selected process instance.
Figure 2.14
Configuring to Web server applications