Decision services from a CI/CD stack

Decision services can be built and deployed in a CI/CD stack. These decision services are deployed to the decision runtime for execution.

The build, deployment, and execution processes involving a CI/CD stack are composed of a series of tasks.

The following diagram shows a flow for execution:

A business expert authors decision artifacts in Decision Designer and shares the decision artifacts.
The shared artifacts are pushed to a remote repository where the decision source files are stored.
The build orchestrator compiles the decision source files and links them into a decision library. The compiled artifacts are contained in the decision library and bundled into a decision service archive.
The decision service archive can be deployed by using the decision runtime REST API. For more information, see Deploying to decision runtime with REST API.
The client application calls the decision service with one of the following methods:
- The client application connects to the decision runtime and calls the decision service by using the decision runtime REST API. For more information, see Calling decision services.
- The client application calls the decision service archive by using the execution Java™ API. For more information, see Executing decision services with execution Java API.