Dev Services for Kogito
If any Kogito process-related extension is present (e.g.
kogito-quarkus-processes), Dev Services for Kogito automatically starts a Data Index in dev mode. So, you don’t have to start it manually or have any other service set-up manually. The application is configured automatically, meaning that will replicate any Kogito messaging events related to Process Instances and User Tasks into the provisioned Data Index instance.
For more details about how to query data about processes and user tasks, please visit Kogito Data Index documentation.
Dev Services for Kogito is automatically enabled unless:
quarkus.kogito.devservices.enabledis set to
Dev Services for Kogito relies on Docker to start the broker. If your environment does not support Docker, you will need to start the broker manually, or connect to an already running Data Index.
In case you would like to share the Data Index instance between applications. Dev Services for Kogito implements a service discovery mechanism for your multiple Quarkus applications running in dev mode to share a single instance.
Dev Services for Kogito starts the container with the
If you need multiple (shared) Data Index instances, you can configure the
quarkus.kogito.devservices.service-name attribute and indicate the instance name. It looks for a container with the same value, or starts a new one if none can be found. The default service name is
Sharing is enabled by default in dev mode. You can disable the sharing with
By default, Dev Services for Kogito starts a Data Index using port 8180. You can set the port by configuring the
Dev Services for Kogito uses:
kiegroup/kogito-data-index-ephemeral images. You can select any version from https://quay.io/repository/kiegroup/kogito-data-index-ephemeral?tab=tags.