Executing decision services with execution Java API
The execution Java API does not use or depend on any installed services in Decision Intelligence. It does not use the decision runtime REST API or decision service storage. Instead, decision service archives are directly used in the execution API. These decision service archives can be packaged in your Java application or accessed with a URL.
For more information, see the Execution Java API reference in Reference.
| License and entitlements to use IBM Decision Intelligence Client Managed Software | Description |
|---|---|
| IBM Decision Intelligence Client Managed Software |
You must use IBM® License Metric Tool (ILMT) to monitor the number of execution. For more information, see Monitoring executions with IBM License Metric Tool. |
| IBM Cloud Pak® for Business Automation |
You must use IBM License Service (ILS) and enable metering to track usage. For more information, see Metering and tracking usage for execution Java API. |
Environment
The execution API must be used in an environment in Java 25. The Java libraries that are used by the external libraries for your decision services must be compatible with the Java version (Java 25) for the execution.
Samples
- Sample: Executing a decision service in Java (available in the ExecutionApiSample subfolder) – You can execute decision services by using the execution Java API, and display execution traces.
- Sample: Creating a web microservice for executing a decision service (available in the WebMicroServiceSample subfolder) – You can create a web microservice to execute a decision service. You can use a decision service with or without a predictive model.