-
Bug
-
Resolution: Done
-
Major
-
6.x.x
-
BPM Suite 6.4.x
Using Rest API to start a new process instance
During BPM Suite server startup, it is possible to start a process from a "deactivated" deployment in a short period of time by using rest call. Please see part of the log which shows that a jar project is loaded and then deactivated:
13:08:35,584 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EJB default - 4) KieModule was added: ZipKieModule[releaseId=org.acme:ticket-support:1.5,file=/home/ajuricic/.m2/repository/org/acme/ticket-support/1.5/ticket-support-1.5.jar] ... 13:08:36,244 INFO [org.jbpm.kie.services.impl.store.DeploymentSynchronizer] (EJB default - 4) Deployment unit org.acme:ticket-support:1.5 deactivated successfully 13:08:36,293 INFO [stdout] (http-127.0.0.1:8080-3) hi
Between these tasks (loading jar and deactivating it), a process from that project can be started by using rest call as follows:
curl -X POST -H "Accept: application/json" -H "Content-Type: application/json" --user user:password 'http://localhost:8080/business-central/rest/runtime/deployment_id/process/process_id/start'
- is cloned by
-
RHBPMS-4745 [GSS](6.4.z) Deactivated deployments are temporarily active during business central startup in BPM Suite 6.4.x
- Verified