Hi guys,
I’d like to run a shared process engine. I am reading this: https://docs.camunda.org/get-started/spring/shared-process-engine/
And my question is: what is “src/main/resources/META-INF/processes.xml”? Is this like another source of .bmpn files?
To the best of my understanding, this provides for some global process configuration elements. In the example below, which is used in the WildFly container, we do the following:
Set the name of the deployment unit to MyProcessDeployment.
Set the property “isDeleteUponUndeploy” to false, which means that if we undeploy the process in the container (in this case WildFly), the processes will not also be deleted.
Set the property “isScanForProcessDefinitions” to true so that processes are created from the deployment.
Set the property “jobExecutorDeploymentAware” to true so that if you do not explicitly deploy a process to a server (e.g. one node of a cluster of Camunda servers sharing a common database), then Camunda will not attempt to run the process or its activities on that server. This prevents class not found or other errors where the process may be dependent upon an external resource only included in the actual deployment archive.
<?xml version="1.0" encoding="UTF-8" ?>
<process-application
xmlns="http://www.camunda.org/schema/1.0/ProcessApplication"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<process-archive name="MyProcessDeployment">
<process-engine>default</process-engine>
<properties>
<property name="isDeleteUponUndeploy">false</property>
<property name="isScanForProcessDefinitions">true</property>
<property name="jobExecutorDeploymentAware">true</property>
</properties>
</process-archive>
</process-application>
There are other properties and elements which may be set here also.
Michael
In addition to Michael’s excellent answer, see the documentation on processes.xml here: https://docs.camunda.org/manual/7.7/reference/deployment-descriptors/descriptors/processes-xml/