Hello,
I have few XQuery based scripts that I hook up as external script resources for Task and ExecutionListeners. I need to deploy them engine wide so that they’re available for all processes.
In the tomcat-standalone version I put them into a custom folder: webapps/camunda/WEB-INF/classes/scripts.
This worked and all scripts were called when interacting both from Tasklist app and from the REST API.
It has been much harder to understand why this doesn’t work deploying Camunda with latest Docker image. I managed to make the scripts callable by placing them through COPY into the image at /camunda/webapps/camunda/WEB-INF/classes/com. But this seems not to be working when calling the REST engine API.
What should I try next?
In general I find it very hard to deploy and maintain scripts to be fed into classloaders… is there the possibility to get them via some kind of URL mechanism like file:// or http://
Thank you very much for possible support!
Hi @nubisware,
you can reference your scripts with deployment://. Have a look at the docs for further details: https://docs.camunda.org/manual/7.11/user-guide/process-engine/scripting/#script-source.
Put the process model and the script file into one deployment.
Hope this helps, Ingo
No matter how hard I try with deployment:// I don’t get it to work.
Could you explain what you mean with “Put the process model and the script file into one deployment.”? Sorry but I’m using Camunda-modeler and deploygin the BPM process from there so I have no clue on ho to bundle processes and scripts together…
I stepped back to classpath:// and now I’ve noticed that scripts will be available also to the REST-engine API only if the Tasklist app is accessed first.
Hi @nubisware,
the modeler could only deploy the currect selected process model.
You have to use the REST API for deployment: Post Deployment | docs.camunda.org.
Using Postman it may look like this:
Hope this helps, Ingo
