The Kie workbench is an authoring and governance application for kie resources (jbpm, drools etc) You will need to build an application.
There are two ways how data from a database can make into the working memory of drools:
- Pushing in the facts from outside using the kie api
- using
from
and pull in data from the database using some custom java code (often known as a repository class or by the earlier term dao/data acess objects
By far the first option is the preferred method. A rule set is about facts and rules, not how or where you obtain those facts from.
A common deployment strategy is:
- Create a maven archetype for the facts
- Define rules in a kie module
- Create an application that uses the facts and rules from above
You can manage and govern the rules in business central. Once you "build & deploy", the kie module with the rules is available in the maven repository.
The application (a third archetype) would then either pull in the rules at build time or at run-time (using maven/wagon)
You could also use an "execution server". In this scenario you deploy the rules to a drools run-time engine and use a remote API (e.g. JMS, HTTP) to push in the facts / fire the rules.
However IMHO rules don't really lend themselves well for a shared/remote approach. But it really depends on your Applications Architecture(!) In contrast jbpmn typically requires a shared remote run-time engine (as there are typically many applications involved with a single business process)