A simple DMN service to evaluate a loan approval and generate tracing events that might be consumed by the Trusty service.
You will need:
When using native image compilation, you will also need:
The default configuration pushes the decision tracing events to the kafka topic kogito-tracing-decision and the DMN models used by the kogito application to kogito-tracing-model under the group-id kogito-runtimes. The configuration can be customized according to https://quarkus.io/guides/kafka and https://kafka.apache.org/documentation/#producerconfigs using the prefix mp.messaging.outgoing.kogito-tracing-decision.<property_name>. For example, in order to change the topic name for the decision tracing events, add the following line to the application.properties file:
mp.messaging.outgoing.kogito-tracing-decision.topic=my-kogito-tracing-decision
mvn clean compile quarkus:dev
mvn clean package java -jar target/quarkus-app/quarkus-run.jar
or on Windows
mvn clean package java -jar target\quarkus-app\quarkus-run.jar
Note that this requires GRAALVM_HOME to point to a valid GraalVM installation
mvn clean package -Pnative
To run the generated native executable, generated in target/, execute
./target/dmn-quarkus-example-runner
Note: This does not yet work on Windows, GraalVM and Quarkus should be rolling out support for Windows soon.
You can take a look at the OpenAPI definition - automatically generated and included in this service - to determine all available operations exposed by this service. For easy readability you can visualize the OpenAPI definition file using a UI tool like for example available Swagger UI.
In addition, various clients to interact with this service can be easily generated using this OpenAPI definition.
When running in either Quarkus Development or Native mode, we also leverage the Quarkus OpenAPI extension that exposes Swagger UI that you can use to look at available REST endpoints and send test requests.
Once the service is up and running, you can use the following example to interact with the service.
Returns penalty information from the given inputs -- driver and violation:
Given inputs:
{ "Bribe": 0, "Client": { "age": 0, "existing payments": 0, "salary": 0 }, "Loan": { "duration": 0, "installment": 0 }, "SupremeDirector": "yes" }
Curl command (using the JSON object above):
curl -X POST -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"Bribe": 0,"Client": {"age": 0,"existing payments": 0,"salary": 0},"Loan": {"duration": 0,"installment": 0},"SupremeDirector": "yes"}' http://localhost:8080/LoanEligibility
or on Windows:
curl -X POST -H "Accept: application/json" -H "Content-Type: application/json" -d "{\"Bribe\": 0,\"Client\": {\"age\": 0,\"existing payments\": 0,\"salary\": 0},\"Loan\": {\"duration\": 0,\"installment\": 0},\"SupremeDirector\": \"yes\"}" http://localhost:8080/LoanEligibility
As response, penalty information is returned.
Example response:
{ "Eligibility": "No", "Judgement": null, "Loan": { "duration": 0, "installment": 0 }, "SupremeDirector": "yes", "Bribe": 0, "Client": { "existing payments": 0, "salary": 0, "age": 0 }, "Is Enough?": 0, "Decide": null }
When the tracing addon is enabled, the tracing events are emitted and pushed to a Kafka broker. The Trusty Service can consume such events and store them on a storage. The Trusty Service exposes then some api to consume the information that has been collected.