jBPM Introduction

jBPM is a flexible Business Process Management (BPM) Suite. It’s light-weight, fully open-source (distributed under Apache license) and written in Java. It allows you to model, execute and monitor business processes, throughout their life cycle.

A business process allows you to model your business goals by describing the steps that need to be executed to achieve that goal and the order, using a flow chart. This greatly improves the visibility and agility of your business logic. jBPM focuses on executable business process, which are business processes that contain enough detail so they can actually be executed on a BPM engine. Executable business processes bridge the gap between business users and developers as they are higher-level and use domain-specific concepts that are understood by business users but can also be executed directly.


The core of jBPM is a light-weight, extensible workflow engine written in pure Java that allows you to execute business processes using the latest BPMN 2.0 specification. It can run in any Java environment, embedded in your application or as a service.

On top of the core engine, a lot of features and tools are offered to support business processes throughout their entire life cycle:

1. Eclipse-based and web-based editor to support the graphical creation of your business processes (drag and drop)
2. Pluggable persistence and transactions based on JPA / JTA
3. Pluggable human task service based on WS-HumanTask for including tasks that need to be performed by human actors
4. Management console supporting process instance management, task lists and task form management, and reporting
5. Optional process repository to deploy your process (and other related knowledge)
6. History logging (for querying / monitoring / analysis)
7. Integration with Seam, Spring, OSGi, etc.

BPM makes the bridge between business analysts, developers and end users, by offering process management features and tools in a way that both business users and developers like it. Domain-specific nodes can be plugged into the palette, making the processes more easily understood by business users.

jBPM supports adaptive and dynamic processes that require flexibility to model complex, real-life situations that cannot easily be described using a rigid process. We bring control back to the end users by allowing them to control which parts of the process should be executed, to dynamically deviate from the process, etc.

jBPM is also not just an isolated process engine. Complex business logic can be modeled as a combination of business processes with business rules and complex event processing. jBPM can be combined with the Drools project to support one unified environment that integrates these paradigms where you model your business logic as a combination of processes, rules and events.

Apart from the core engine itself, there are quite a few additional (optional) components that you can use, like an Eclipse-based or web-based designer and a management console.

jBPM Overview:


wait for my next posts.
Credit: article directly taken from JBoss Documents.

Happy Coding , Happy SOA and jBPM 🙂


BPEL HelloWorld Example with Eclipse and Apache ODE

Hi Guys as i explained in my previous post how to install Apache ODE and Eclipse BPEL Designer now im here to explain how to deploy the first BPEL process flow

Objective: deploying a BPEL process which receives an input string from a client and responses it exactly that input.
Tools: Eclipse 3.6.2, BPEL Designer 0.5.0 Plugin, Tomcat 7.0.12, ODE 1.3.5

step1.Create new BPEL project: File→New→Others→BPEL 2.0→BPEL Project.
step2.Name it BPEL_HelloWorld. Select the Target Runtime as Apache ODE 1.x Runtime and Configuration as Defaut Configuration for Apache ODE 1.x Runtime. Click Finish.


step3.In the folder BPEL_HelloWorld\bpelContent, File → New → Other → BPEL 2.0 → New BPEL process file.
step4.Name it HelloWorld, Namespace http://helloworld.localhost and select Template Synchronous BPEL Process. Click Next.


step5.Edit the Service Address to : http://localhost:8080/ode/processes/HelloWorld (suppose that your Tomcat environment runs at port 8080) and keep other default declarations. Click Finish.


step6. Three files are created in the folder bpelContent and the HelloWorld.bpel is opened for editing the BPEL process.
step7. Click to open the Palette panel on the right of the canvas. (or right click on the canvas, select Show Pallette on Palette View)


step8. Drag the Assign action next to the receiveInput action and delete the FIX_ME-Add_Business_Logic_Here.


step9. Right click on the Assign activity. Select Show in properties.
step10.In the Properties tab, select Details. Click on the New button to define an assign operator.
step11.Assign from input→payload→input to output→payload→result. An Initializer popup dialog appear. Click Yes to initialize the output variable and save the process.


step12. It’s time now to deploy the BPEL project. Click on the folder bpelContent, select File→New→Others→BPEL 2.0→Apache ODE Deployment Descriptor.
step13. Click Next. Verify the BPEL Project name as BPEL_HelloWorld. Click Finish.


step14 .Double click on the deploy.xml file in the bpelContent folder.
step15. In the Inbound Interfaces table, select the Partner Link as client, Associate Port as HelloWorldPort. Click on Related Service then other fields will be automatically filled. Save the deploy.xml file.


step16. To deploy the project on the server, right click on the Ode v1.x Server at localhost, select Add and Remove Projects.
step17.Select the BPEL_HelloWorld/HelloWorld in the Available projects box and click Add. Then, click Finish


step18. Start the ODE server. If the deployment was successful, you will see the following output in the console tab.


step19. We will test the project with Web Services Explorer provided by Eclipse. Right click on the HelloWorldArtifacts.wsdl file. Select Web Services→Test with Web Services Explorer.
step20. Select the operation process. Then, type Hello ODE in the input textbox. If your deployment was success, you will get the same string in the SOAP response.


We are Done
Happy Coding 🙂

SOA part-1 Installing BPEL Designer and Apache ODE

Hi all, in my last project i was trying some BPEL process to execute from Eclipse and Apache ODE and finally i made the process to work so here is my experience and my tutorial to install BPEL designer in Eclipse3.6 and Apache ODE

Installing Eclipse BPEL designer
1.Suppose that you have already downloaded and installed your Eclipse > v3.6.2(Helios,or Indigo), version for Java EE Developers and JDK (version > 1.5).
2.Open the Eclipse, go to the menu Help→Install New SoftWare.
3.Click on the button Add and define a new Eclipe update site with the location:
4.Now you have the update-site of BPEL available on the eclipse. Select the check box to BPEL Visual Designer and click on the button Next.
5.Follow the installation windows, you will now have your BPEL installed on Eclipse. Note that: the BPEL dependencies(WTP, EMF, GEF, JEM) should be installed before the BPEL designer. Fortunately, with Eclipse Helios for JavaEE, you have all.
6.After finishing the installation, restart it.
7.To verify the installation was successful, after the restart, click on File→New→Other, you will see the BPEL 2.0 is on the list.
The BPEL designer is now ready to use. However, to run the BPEL process, you should have the server’s environment. Now, we are going to install the Apache ODE for the BPEL deployment.

Installing Apache ODE

1.Download and extract the latest ODE from the Apache web site. The current stable version is the ODE 1.3.5.
2.Inside the “apache-ode-war-1.3.5” folder, you will see an “ode.war” file. Deploy this file on your Tomcat server.
3.The simple way to do this is extracting the “ode.war” file to get the ode folder.
4.Copy this ode folder to your TOMCAT_DIR/webapps directory.
That’s all.

Setting up the ODE server on Eclipse
1.Show the “Servers” view by selecting the menu Windows→Show View→Servers.
2.Right click on the empty space of the “Servers” view, select New→Server.
3.Leave the server host name as localhost and select the server type as the Apache→Ode v1.x Server. Rename the server’s name if you want. In my installation, I keep the default name. Then click on the button Next.
4. Show the “Servers” view by selecting the menu Windows→Show View→Servers.
Right click on the empty space of the “Servers” view, select New→Server.
Leave the server host name as localhost and select the server type as the Apache→Ode v1.x Server. Rename the server’s name if you want. In my installation, I keep the default name. Then click on the button Next.

Note that: the ODE Runtime configuration above can also be added or editted using the menu Windows→Preferences→Server→Runtime Environments.

5. Click Finish. You now have the ODE server which is ready to run on the Eclipse. You can see this server on the Server View.
6.Now, you should test the server’s configuration by right click on the ODE server entry and select Start. Or you can click on the Start button on the Server View. If the server is sucessfully started, you will see the status like this.

Note:If you are using Tomcat v.6 or v.7, you probably get the error

Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
  at org.apache.catalina.startup.Bootstrap.<clinit>(Bootstrap.java:54)
Caused by: java.lang.ClassNotFoundException: org.apache.juli.logging.LogFactory
  at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
  at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336)
  ... 1 more
Could not find the main class: org.apache.catalina.startup.Bootstrap. Program will exit.

7. This error occurs maybe because it misses the tomcat-juli.jar in the Launch environment.
8. To fix this, double click on the installed Ode v1.x Server in the Server View to see the configuration.
9. k on Open launch configuration → Classpath tab → Add External JARs → [your TOMCAT_DIR]\bin\tomcat-juli.jar. Then Ok
10. Now try to start your ODE server in the Server View.
11.Terminate the server by clicking on the Stop button or right click on the server and select Stop. Every thing is

Ready now for the first BPEL program. i will be teaching the first HelloWorld BPEL Process in SOA-2 tutorial
Happy Coding 🙂