Chapter 5. Asset execution options with Red Hat Process Automation Manager

Execution in Process Server

If you deployed Red Hat Process Automation Manager project assets to Process Server, you can use the Process Server REST API or Java client API to execute and interact with the deployed assets. You can also use Business Central or the headless Process Automation Manager controller outside of Business Central to manage the configurations and KIE containers in the Process Server instances associated with your deployed assets. For process definitions, you can use Business Central directly to execute process instances.

Interacting with Red Hat Process Automation Manager using KIE APIs

Executing a business process in Business Central

Execution in an embedded Java application

If you deployed Red Hat Process Automation 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 Process Server APIs) to execute assets in the embedded engine.

KIE Public API

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 Process Automation 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