Show Table of Contents
7.28. JBPM Deployment
Table 7.10. JBPM Deployment
| Property | Description |
|---|---|
jbpm.esb/META-INF
|
This directory contains the
deployment.xml and jboss-esb.xml files.
|
deployment.xml
|
Specifies the two resource files the ESB archive depends on: the
jbossesb.esb and the JbpmDS data source files. The information in these files is used to determine the order of deployment:
<jbossesb-deployment> <depends>jboss.esb:deployment=jbossesb.esb</depends> <depends>jboss.jca:service=DataSourceBinding,name=JbpmDS</depends> </jbossesb-deployment> |
jboss-esb.xml
|
This file deploys an internal service called
JBpmCallbackService:
<services>
<service category="JBossESB-Internal" name="JBpmCallbackService"
description="Service which makes Callbacks into jBPM">
<listeners>
<jms-listener name="JMS-DCQListener"
busidref="jBPMCallbackBus" maxThreads="1" />
</listeners>
<actions mep="OneWay">
<action name="action"
class="org.jboss.soa.esb.services.jbpm.actions.JBpmCallback"/>
</actions>
</service>
</services>
This internal service listens to the
jBPMCallbackBus, which, by default, is set to be either JBossMQ (via the jbmq-queue-service.xml file) or JBossMessaging (via the jbm-queue-service.xml file.) The latter is a messaging provider for the Java Message Service Queue. Ensure that only one of these files is deployed in the jbpm.esb archive.
|

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.