此内容没有您所选择的语言版本。
Chapter 11. Integrating Red Hat JBoss BPM Suite with Red Hat JBoss Fuse
Red Hat JBoss Fuse integration allows users of Red Hat JBoss Fuse to complement their integration solution with additional features provided by Red Hat JBoss BPM Suite and Red Hat JBoss BRMS.
Red Hat JBoss BPM Suite integration is provided by two features.xml
files:
drools-karaf-features-VERSION-features.xml
This file provides core Red Hat JBoss BPM Suite and Red Hat JBoss BRMS features, which defines the OSGi features that can be deployed into Red Hat JBoss Fuse. This file is a part of the Red Hat JBoss BPM Suite and Red Hat JBoss BRMS product. OSGi users can install features from this file in order to install Red Hat JBoss BRMS engine or Red Hat JBoss BPM Suite engine into Red Hat JBoss Fuse and use it in their applications.
karaf-features-VERSION-features.xml
This file provides additional features used for integrating Red Hat JBoss BPM Suite and Red Hat JBoss BRMS with Apache Camel, primarily in Red Hat JBoss Fuse. This file is part of the Integration Pack and it defines OSGi features that enable integration with Apache Camel and SwitchYard. In addition to the
karaf-features
XML file, the Integration Pack also contains afeatures.xml
file for quick starts.
For further information about integration of Red Hat JBoss BPM Suite with Red Hat JBoss Fuse, see the Install Integration Pack chapter of the Red Hat JBoss Fuse Integration Guide.
Core Red Hat JBoss BPM Suite and Red Hat JBoss BRMS features are provided by the drools-karaf-features-VERSION-features.xml
file present in your product Maven repository or the jboss-brms-bpmsuite-VERSION-redhat-VERSION-fuse-features.zip
file. It provides the following features:
-
drools-common
-
drools-module
-
drools-templates
-
drools-decisiontable
-
drools-jpa
-
kie
-
kie-ci
-
kie-spring
-
kie-aries-blueprint
-
jbpm-commons
-
jbpm-human-task
-
jbpm
-
droolsjbpm-hibernate
-
h2
The following table provides example of use cases for some of the features listed above.
Feature | Use Case |
---|---|
| Use the Red Hat JBoss BRMS engine for rules evaluation, without requiring persistence, processes, or decision tables. |
|
Use the Red Hat JBoss BRMS engine for rules evaluation with persistence and transactions, but without requiring processes or decision tables. The |
| Use the Red Hat JBoss BRMS engine with decision tables. |
|
Use the Red Hat JBoss BPM Suite (or Red Hat JBoss BRMS engine with processes). The |
| Use the Red Hat JBoss BPM Suite (or Red Hat JBoss BRMS engine with processes) with Human Task. |
core engine JARs and |
Use Red Hat JBoss BRMS or Red Hat JBoss BPM Suite with |
| Use KIE-Spring integration. See the section called “kie-spring Feature Further Information” for more information. |
| Use KIE-Aries-Blueprint integration. |
kie-spring Feature Further Information
-
Use
org.drools.osgi.spring.OsgiKModuleBeanFactoryPostProcessor
instead oforg.kie.spring.KModuleBeanFactoryPostProcessor
to postprocess KIE elements in an OSGi environment. Do not install the
drools-module
feature before thekie-spring
feature. Otherwise, thedrools-compiler
bundle does not detect packages exported bykie-spring
.Run
osgi:refresh drools-compiler_bundle_ID
if you have installed the features in the incorrect order to forcedrools-compiler
to rebuild its Import-Package metadata.