Show Table of Contents
8.3. JBossESB to jBPM 5
JBossESB can make calls into jBPM 5 using the Bpm5Processor action. This action uses the jBPM 5 command API to make calls into jBPM. The following jBPM commands have been implemented:
Table 8.1. jBPM 5 commands
| Command | Description |
|---|---|
startProcess |
Start a new ProcessInstance given a process definition that was already deployed to jBPM.
|
signalEvent |
Signal to an already-started process that an event has occurred.
|
abortProcessInstance |
Cancel a ProcessInstance. That is, when an event comes in which should result in the cancellation of the entire ProcessInstance. This action requires some jBPM context variables to be set on the message, in particular the ProcessInstance Id.
|
There are two required action attributes:
- nameRequired attribute. You are free to use any value for the name attribute as long as it is unique in the action pipeline.
- classRequired attribute. This attributes needs to be set to “org.jboss.soa.esb.services.jbpm5.actions.Bpm5Processor”
Warning
Using signalEvent is inherently risky because there is nothing to indicate what states the process instance or work item is in. Use the request-reply functionality of the ESBActionWorkItemHandler rather than signalEvent.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.