Deploying and executing decision services

When a decision service is ready for deployment, it can be securely deployed through a continuous integration and delivery (CI/CD) stack before being rolled out to production. Alternatively, you also can deploy decision services directly from Decision Designer.

Multiple deployment options are available to help you execute decisions at scale where you need them:

Diagram depicting the deployment and execution workflow

Building and deploying in a CI/CD stack

To build and deploy decision services, the IT department can connect the Decision Designer web interface to the CI/CD stack in use in your organization. The built-in execution server, known as the decision runtime, enables decision services to be run with a simple REST API.

If you do not have your own processes and tools in place already, Automation Decision Services provides a sample CI/CD stack that can be easily installed and configured, primarily for evaluation purposes.

Building and deploying from Decision Designer

As an alternative, you can easily deploy decision services from Decision Designer.

Deployed decision services can be published to the Business Automation Studio catalog to be reused in other applications, or called by any client application by using the runtime REST API.