I am in the process of running jbpm as a service. As part of this, we downloaded jboss-native-2.0.10-windows-x64-ssl.zip. I have modified the bat script of service.bat as follows:
jbosssvc.exe -p 1 "Starting %SVCDISP%" > %JBOSS_HOME%\standalone\log\standalone.log
set >> %JBOSS_HOME%\standalone\log\standalone.log
call mvn help:effective-settings >> %JBOSS_HOME%\standalone\log\standalone.log
call standalone.bat -b 0.0.0.0 --server-config=standalone-full.xml -Dorg.kie.demo=true -Dorg.kie.example=false -Dorg.kie.executor.disabled=false -Dorg.kie.executor.pool.size=20 -Dorg.kie.executor.retry.count=0 < .r.lock >> %JBOSS_HOME%\standalone\log\standalone.log 2>&1
rem call ant -f C:\jbpm-installer\build.xml start.jboss
rem jbosssvc.exe -p 1 "Started %SVCDISP% service" >> %JBOSS_HOME%\standalone\log\standalone.log
I have tried two scenarios which are as follows
Scenario One: JBPM is started using the Service Control Manager … the KIE Dashboard is accessible using krisv/krisv...when deployments are requested … there are none available.
The state of the service (running/stopped) displays correctly in the SCM.
Scenario Two: Commenting out the call to standalone bat and uncommenting the call to ant results in the KIE Dashboard being accessible using krisv/krisv...and the expected deployments are available.
The state of the service (running/stopped) is no longer correctly displayed in the SCM. The service will show as stopped even though the code is running.
Both of the scenarios, have some issues related to them as described above.