Decision services from the run service

Decision services can be built and deployed in the run service when you trigger it from Decision Designer. These decision services are deployed to the decision runtime for execution.

The build, deployment, and execution processes involving the run service are composed of a series of tasks.

The following diagram shows a flow for execution:

Automation Decision Services architecture
  1. A business expert authors decision artifacts in Decision Designer and shares the decision artifacts.
  2. Building and deploying a decision service is triggered from Decision Designer.
  3. The run service builds a decision service and deploys a decision service archive with metadata to the runtime service through its REST API. Decision service archives are deployed to the decision runtime in the deployment space ID (deploymentSpaceId) named embedded. The decision service is ready for execution.
  4. 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.
    • You download the decision service archive from the decision runtime. 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.