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:

Automation Decision Services architecture
  1. A business expert authors decision artifacts in Decision Designer and shares the decision artifacts.
  2. The published artifacts are pushed to a remote repository where the decision source files are stored.
  3. 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.
    • Both the decision library and the decision service archive are stored in the binary repository.
  4. The decision service archive is deployed with metadata to the runtime service through its REST API. The decision service is ready for execution.
  5. The client application connects to the decision runtime and calls the decision service by using the runtime REST API for more information, see Calling decision services.