Document the 6.1 PRD Requirement: https://issues.jboss.org/browse/BPMSPL-48. This will require installation of the products on Fuse. It will be a good candidate for the Installation Guides.
Note that I am not creating two separate issues for BRMS and BPMS and the work for both will be tracked through this bug only.
This is now been documented in the Admin & Config Guides and can be verified here  for BPMS (it is same content for BRMS).
Moving this to ON_QA.
The example seems correct, what I miss is the information how KIE/Drools/jBPM dependencies should be configured in the sample application. There are several approaches in OSGi environment:
1. to bundle required dependencies into your application bundle:
-- this means declaring all required artifacts as compile/runtime dependencies in your pom.xml,
-- you do not need to declare <Import-Package> for those packages which are provided by the artifacts you have added as dependencies (you might still need e.g. org.osgi.framework).
2. to let the OSGi framework wire bundles providing packages that your application bundle needs in runtime:
-- this means declaring only the API jars (such as org.kie:kie-api) as (provided) dependencies in your application bundle,
-- you must declare <Import-Package> for all packages your application needs to use from Drools/jBPM bundles,
-- before attempting to install/start your application bundle, you should have installed required bundles (for instance, feature drools-module defined in drools-karaf-features xml as mentioned in Comment 2).
The first option is less OSGi-friendly, since it bundles everything and you are not able to upgrade used Drools version just by installing newer version of Drools bundles in runtime, for instance. Additional description of this approach can be found in Dependency management section in .
The second option is probably preferred in OSGi world for its flexibility, but it depends on the exact use case.
To sum it up:
- extend the Basic Usage from Chapter 10 to mention the above two approaches (or describe only the second one) for building OSGi application bundles; the current description proposes something in between,
- please consider updating the guide according to comments in Comment 2.