Difference between revisions of "Eclipse plugin: Usage"
From OpenKM Documentation
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | {{Warning|This article is deprecated, please go to [[Workflow Guide]].}} | ||
+ | |||
To create a new process definition, go to File → New → Other and select "Process Definition", but before you need to create a "Process Project". Will appear another form where you need to specify the source folder and the process name. Lets call it simply "hello". | To create a new process definition, go to File → New → Other and select "Process Definition", but before you need to create a "Process Project". Will appear another form where you need to specify the source folder and the process name. Lets call it simply "hello". | ||
Line 19: | Line 21: | ||
[[File:Jbpm eclipse new 04.jpg|767px|center]] | [[File:Jbpm eclipse new 04.jpg|767px|center]] | ||
+ | {{Note|There is a new revision of the jBPM Eclipse plugin with some changes. They are described at: | ||
+ | * [http://docs.jboss.org/tools/whatsnew/jbpm/jbpm-news-3.2.0.M2.html jBPM Tools 3.2.0.M2 What's New] | ||
+ | * [http://docs.jboss.org/tools/whatsnew/jbpm/jbpm-news-3.2.0.M1.html jBPM Tools 3.2.0.M1 What's New] | ||
+ | * [http://docs.jboss.org/tools/whatsnew/jbpm/jbpm-news-3.3.0.M2.html jBPM Tools 3.3.0.M2 What's New] | ||
+ | }} | ||
* '''Diagram''': This is the main work zone. Here you can construct your process definitions on a visual way. | * '''Diagram''': This is the main work zone. Here you can construct your process definitions on a visual way. | ||
Line 26: | Line 33: | ||
− | * '''Deployment''': Here you can deploy the created process definition directly to the server or save it to deploy manually. The file extension should be ".par". | + | * '''Deployment''': Here you can deploy the created process definition directly to the server or save it to deploy manually. You can create a deployable archive going to "Local Save Settings" section, marking the "Save Process Archive Locally" option, selecting a location and clicking in the "Save Without Deploying..." button. The file extension should be ".par". |
Line 43: | Line 50: | ||
[[File:Jbpm eclipse new 08.jpg|549px|center]] | [[File:Jbpm eclipse new 08.jpg|549px|center]] | ||
− | + | See also: | |
+ | * [http://www.redhat.com/developer_studio/guides/jbpm/html_single/ jBPM Tools Reference Guide] | ||
[[Category: Workflow Guide]] | [[Category: Workflow Guide]] |
Latest revision as of 11:20, 3 December 2012
This article is deprecated, please go to Workflow Guide. |
To create a new process definition, go to File → New → Other and select "Process Definition", but before you need to create a "Process Project". Will appear another form where you need to specify the source folder and the process name. Lets call it simply "hello".
If is the first time you create a Process Definition, you have to configure the jBPM runtime. Remember the path of the jBPM library installation (See JBPM installation)
Once the wizard has finished, you can see an Eclipse environment with a central panel divided in four tabs:
There is a new revision of the jBPM Eclipse plugin with some changes. They are described at: |
- Diagram: This is the main work zone. Here you can construct your process definitions on a visual way.
- Deployment: Here you can deploy the created process definition directly to the server or save it to deploy manually. You can create a deployable archive going to "Local Save Settings" section, marking the "Save Process Archive Locally" option, selecting a location and clicking in the "Save Without Deploying..." button. The file extension should be ".par".
- Design: Is the source code of the process definition. It is an hierarchical representation of the XML which describe the nodes and transitions. See jPDL xml schema chapter in jBPM jPDL User Guide for more info.
- Source: Is the source code of the process definition. It is an XML which describe the nodes and transitions. See jPDL xml schema chapter in jBPM jPDL User Guide for more info.
See also: