Information Technology Reference
In-Depth Information
Once we complete all the fields and click on the Deploy Unit button, we will see the unit
details available as a new row in the deployment units table as shown in the following
screenshot:
By default, the KIE Workbench will allow you to have one runtime manager per KIE ses-
sion definition. If you define multiple different sessions, you should be aware that the
place where they will be used (from the KIE Workbench perspective) is the Process
Definitions and Process Instances perspectives. In these perspectives, you
will have access to the process definitions from which you can start process instances.
Having a specific runtime manager configured for a specific KIE session configuration
will allow us to not only run a process in the KIE Workbench, but also to customize it
with the specific configuration we chose. We can configure our KIE session name to run
on a specific KIE base with many rules and processes together and to run them all in a
single KIE session or in multiple ones.
You have to make sure that for the same KIE Workbench installation, if you have multiple
deployment units, you can only access a process definition from one of them, which is a
limitation of the tooling. The API has access to anything you want, though. If you wish to
have any kind of runtime manager in different parts of your application for the same KIE
session configuration, you just have to provide the proper CDI annotations to use the one
you prefer.
You could also extend the available runtime managers to provide different strategies for
KIE session and Human task component initialization. We will discuss that topic in the
next section.
Search WWH ::




Custom Search