BPM Configuration Reference
| Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version. |
This page provides details on the process components you configure for BPM. Some of this information is pulled directly from mule-bpm.xsd and is cached. For more information on BPM, see BPM Module Reference. Information on jBPM is available at http://www.jbpm.org.
Process
A process backed by a BPMS such as jBPM.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
bpms-ref |
string |
no |
An optional reference to the underlying BPMS. This is used to disambiguate in the case where more than one BPMS is available. |
|
processName |
string |
yes |
The logical name of the process. This is used to look up the running process instance from the BPMS. |
|
processDefinition |
string |
yes |
The resource containing the process definition, this will be used to deploy the process to the BPMS. The resource type depends on the BPMS being used. |
|
processIdField |
string |
no |
This field will be used to correlate Mule messages with processes. If not specified, it will default to MULE_BPM_PROCESS_ID. |
| Name | Cardinality | Description |
|---|
Jbpm
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
name (no spaces) |
no |
An optional name for this BPMS. Refer to this from the "bpms-ref" field of your process in case you have more than one BPMS available. |
|
configurationResource |
string |
no |
The configuration file for jBPM, default is "jbpm.cfg.xml" if not specified. |
|
processEngine-ref |
string |
no |
A reference to the already-initialized jBPM ProcessEngine. This is useful if you use Spring to configure your jBPM instance. Note that the "configurationResource" attribute will be ignored in this case. |
| Name | Cardinality | Description |
|---|