Support for BPM allows you to send/receive messages to/from a running process. A message from Mule can start or advance a process, the message can be stored as a process variable, and a running process can send messages to any endpoint in your Mule application. BPMBPM Support A process backed by a BPMS such as jBPM. An optional reference to the underlying BPMS. This is used to disambiguate in the case where more than one BPMS is available. The logical name of the process. This is used to look up the running process instance from the BPMS. 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. This field will be used to correlate Mule messages with processes. If not specified, it will default to MULE_BPM_PROCESS_ID. 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. The configuration file for jBPM, default is "jbpm.cfg.xml" if not specified. 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. A service backed by a rules engine such as Drools. A reference to the underlying Rules Engine. The resource containing the rules definition. This will be used to deploy the ruleset to the Rules Engine. A reference to a collection of initial facts to be asserted at startup. Are we using the knowledge base for CEP (Complex Event Processing)? (default = false) Entry point for event stream (used by CEP). An optional name for this Rules Engine. Refer to this from the "rulesEngine-ref" field of your component in case you have more than one Rules Engine configured.