Red Hat Training

A Red Hat training course is available for JBoss Enterprise SOA Platform

7.21. List of ESB Notifier Sub-Elements

Table 7.6. List of ESB Notifier Sub-Elements

Sub-element Description
esbCategoryName
This is the ESB service's category name and is required if you are not using the reply-to-originator functionality.
esbServiceName
This is the name of the ESB service and required if you are not using the reply-to-originator functionality.
replyToOriginator
Use this to specify the 'reply' or 'fault' originator address previously stored in the process instance on creation.
globalProcessScope
This element is an optional Boolean-valued parameter. Use it to set the default scope within which the bpmToEsbVars variables are to be found. If the globalProcessScope is set to true, it searches for the variables within the token hierarchy (the process-instance scope). If it is set to false, it retrieves the variables in the scope of the token. If the token itself does not possess a variable for a given name, the token hierarchy is used to search for that variable. If the element is omitted altogether, the globalProcessScope defaults to false.
bpmToEsbVars
This element is optional. It takes a list of sub-elements and uses them to map a JBPM context variable to an ESB message location. Each of these mapping sub-elements can have the following attributes:
bpm
This is a required attribute. It is the name of the variable in JBPM context. The name can be MVEL type expression so you can extract a specific field from a larger object. The MVEL root is set to the JBPM “ContextInstance”, so for example you can use mapping like:
<mapping bpm="token.name" esb="TokenName" />
<mapping bpm="node.name" esb="NodeName" />      	
<mapping bpm="node.id" esb="esbNodeId" />      	
<mapping bpm="node.leavingTransitions[0].name" esb="transName" />
<mapping bpm="processInstance.id" esb="piId" /> 
<mapping bpm="processInstance.version" esb="piVersion" />
The JBPM context-variable names can also be referenced directly.
esb
Optional. This is the name of the variable in the Enterprise Service Bus Message. It can be an MVEL-type expression. (The attribute value TokenName in the example above is equal to body.TokenName. A special value called BODY_CONTENT "addresses" the body directly.) By default, the variable is set as a named parameter on the body of the ESB Message. To omit the esb attribute, replace it with the value of the bpm attribute.
process-scope
This attribute is optional. It is a parameter that can contain a Boolean value used to override the setting of the globalProcessScope for this mapping.

Important

Always activate debug-level logging when working on the variable mapping configuration.