8.4. jBPM Context Configuration Properties

Note

The following properties can be set as so: 
Message esbMessage = MessageFactory.getInstance().getMessage();

ContextImpl ctxi = (ContextImpl) esbMessage.getContext();
ctxi.setContext("jbpm5-session-id", 10);
ctxi.setContext("jbpm5-processinstance-id", 10L);

Table 8.2. jBPM Configuration Properties

Property Description Required?
process-action
Needs to be one of: startProcess, signalEvent, or abortProcessInstance.
Yes
process-definition-name
Required property. The value of this property should reference a process definition that is already deployed to jBPM and of which you want to create a new instance.
Yes
process-id
The value of this property should reference a process definition id in jBPM of which you want to create a new instance.
Yes
esbToBpmVars
Optional property. This property defines a list of variables that need to be extracted from the EsbMessage and set into jBPM context for the particular process instance. The list consists of mapping elements. Each mapping element can have the following attributes:
  • esb
    required attribute which can contain an MVEL expression to extract a value anywhere from the EsbMessage.
  • bpm
    optional attribute containing the name which be used on the jBPM side. If omitted the esb name is used.
  • value
    optional attribute which can hold a hard coded value.
No
handlerClass
WS Human Task handler class (default: org.jbpm.task.service.hornetq.CommandBasedHornetQWSHumanTaskHandler)
Yes
handlerHost
WS Human Task server hostname (default: 127.0.0.1)
Yes
handlerPort
WS Human Task server hostname (default: 5446)
Yes

Note

jBPM uses HornetQ by default. Another option is to use Mina which requires the following settings:
  • org.jbpm.process.workitem.wsht.CommandBasedWSHumanTaskHandler
  • handlerHost - WS Human Task server hostname (default: 127.0.0.1)
  • handlerPort - WS Human Task server hostname (default: 9123)