Chapter 9. Integrating Red Hat JBoss BPM Suite with Red Hat JBoss Fuse
features.xml files: one providing core JBoss BPM Suite and JBoss BRMS features, which defines the OSGi features that can be deployed into JBoss Fuse, and the other providing additional support for integration with SwitchYard and Camel.
Note
Important
jboss-brms-bpmsuite<version>-redhat<version>fuse-features.zip:
- 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
Table 9.1. Features and Use Case Examples
| Feature | Use Case |
|---|---|
drools-module | Use the JBoss BRMS engine for rules evaluation, without requiring persistence, processes, or decision tables. |
drools-jpa | Use the JBoss BRMS engine for rules evaluation with persistence and transactions, but without requiring processes or decision tables. The drools-jpa feature already includes drools-module, however you may also need to install the droolsjbpm-hibernate feature, or ensure there is a compatible hibernate bundle installed. |
drools-decisiontable | Use the JBoss BRMS engine with decision tables. |
jbpm | Use the JBoss BPM Suite (or JBoss BRMS engine with processes). The jbpm feature already includes drools-module and drools-jpa. You may also need to install the droolsjbpm-hibernate feature, or ensure that there is a compatible hibernate bundle installed. |
jbpm and jbpm-human-task | Use the JBoss BPM Suite (or JBoss BRMS engine with processes) with Human Task. |
Core engine jars and kie-ci. | Use JBoss BRMS or JBoss BPM Suite with KieScanner (KIE-CI) to download kJARs from a Maven repository. |
kie-spring | Use KIE-Spring integration. |
kie-spring and kie-aries-blueprint. | Use KIE-Aries-Blueprint integration. |
- fuse-bxms-switchyard-common-knowledge
- fuse-bxms-switchyard-rules
- fuse-bxms-switchyard-bpm
- kie-camel
- jbpm-workitems-camel
installDir/etc/org.ops4j.pax.url.mvn.cfg.
9.1. Install/Update Core Integration Features
Note
jboss-brms-bpmsuite<version>-redhat<version>fuse-features.zip file. For additional integration features, refer to Section 9.2, “Install Additional Integration Features”.
drools-karaf-features-6.2.0.Final-redhat-6-features.xml), you need to remove them and all associated files before installing the most recent features.xml file.
Procedure 9.1. Removing an Existing drools-karaf-features Installation
- Start the Fuse console using:
$ ./installDir/bin/fuse
- Unistall old features/apps that used the previous
features.xmlfile. For example:JBossFuse:karaf@root> features:uninstall drools-module JBossFuse:karaf@root> features:uninstall jbpm JBossFuse:karaf@root> features:uninstall kie-ci
- Search for references of bundles using drools/kie/jbpm and remove them:
list -t 0 -s | grep drools list -t 0 -s | grep kie list -t 0 -s | grep jbpm
To remove the bundles:karaf@root> osgi:uninstall <BUNDLE_ID>
- Remove the old drools-karaf-features url:
karaf@root> features:removeurl mvn:org.drools/drools-karaf-features/6.2.0.Final-redhat-<old-version>/xml/features
- Restart Fuse
drools-karaf-features:
Procedure 9.2. Install core JBoss BPM Suite and JBoss BRMS features
- Configure required repositories
- Edit the
installDir/etc/org.ops4j.pax.url.mvn.cfgfile in your JBoss Fuse installation and add the following entry to theorg.ops4j.pax.url.mvn.repositoriesvariable, noting that entries are separated by ‘, \’:- http://maven.repository.redhat.com/ga/@id=bxms-product-repo
- Start JBoss Fuse:
$ ./installDir/bin/fuse
- Add a reference to the core features file by running the following console command:
JBossFuse:karaf@root> features:addurl mvn:org.drools/drools-karaf-features/6.2.0.Final-redhat-<version>/xml/features
- You can now install the features provided by this file by running, for example, the following console command:
JBossFuse:karaf@root> features:install drools-module

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.