I have deployed test.esb that calls BpmProcessor from one of the services that is defined in jboss-esb.xml. This works great and creates bpm process-instance.
With default settings of jbpm-cfg.xml. but when I modify jbpm-cfg.xml to use JmsschedulerService instead of default DBScheduler it stopped working.
Please provide your inputs what else do I need to change to initiate process instance from jboss-esb to work with jbpm that is using jmsscheduler instead for JobExecuter.
jboss-esb.xml
<action name="startProcessInstance" >
<property name="command" value="StartProcessInstanceCommand" />
<property name="process-definition-name" value="EsbFileProcess"/>
<property name="esbToBpmVars">
<mapping esb="BODY_CONTENT" bpm="message" />
</property>
</action>
From default
<service factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />
To Jms
<service name="scheduler" factory="org.jboss.soa.esb.services.jbpm.integration.timer.JmsSchedulerServiceFactory"/>
<null name="jbpm.job.executor"/>