Chapter 5. Asset execution options with Red Hat Decision Manager
After you build and deploy your Red Hat Decision Manager project to KIE Server or other environment, you can execute the deployed assets for testing or for runtime consumption. You can also execute assets locally in addition to or instead of executing them after deployment.
The following options are the main methods for Red Hat Decision Manager asset execution:
Table 5.1. Asset execution options
| Execution option | Description | Documentation |
|---|---|---|
| Execution in KIE Server | If you deployed Red Hat Decision Manager project assets to KIE Server, you can use the KIE Server REST API or Java client API to execute and interact with the deployed assets. You can also use Business Central or the headless Decision Manager controller outside of Business Central to manage the configurations and KIE containers in the KIE Server instances associated with your deployed assets. | |
| Execution in an embedded Java application | If you deployed Red Hat Decision Manager project assets in your own Java virtual machine (JVM) environment, microservice, or application server, you can use custom APIs or application interactions with core KIE APIs (not KIE Server APIs) to execute assets in the embedded engine. | |
| Execution in a local environment for extended testing | As part of your development cycle, you can execute assets locally to ensure that the assets you have created in Red Hat Decision Manager function as intended. You can use local execution in addition to or instead of executing assets after deployment. | "Executing rules" in Designing a decision service using DRL rules |
