Executing decision services

After you deploy your decision service, you can execute it.

The build, deployment, and execution processes are composed of a series of tasks:

  1. You create a decision service in Decision Designer and share your changes with collaborators.
  2. You build and deploy the decision service from Decision Designer. The decision service archive is deployed to the decision runtime in the development deployment space.
  3. The client application connects to the decision runtime and calls the decision service by using the decision runtime REST API.
A deployment space is a set of decision service archives and their associated metadata, and it is a logical way to group decisions. The set of metadata is associated to each decision service contains the following information:
  • Information about the decision service; for example, date of build and decision ID (decisionId).
  • Parameters that are used by the execution; for example, machine learning credentials
  • User custom parameters
The decision runtime comes with a set of REST API for the following purposes:
  • Executing decisions
  • Managing the metadata that are associated to the decision service.
  • Retrieving execution traces

Each decision runtime instance is able to execute multiple distinct decisions. The runtime caches decision service archives and metadata to decrease the cost of loading the decision service archives.

A deployed decision service archive cannot be modified. When a modifiable metadata is changed, the runtime automatically uses the new value after a configurable delay.