The Polling Client is a useful tool for the extraction of Camunda process data and their permanent storage in Apache Kafka. As such it is used in the projects bpmn.ai or vPW, that aim to open up standard process data for data mining and exploration.
Two different polling modes are supported: Polling via JDBC access from a Camunda database using an embedded Camunda engine and polling via the Camunda engines own REST API from an existing Camunda instance.
We provide a pre-configured docker image on Amazon Elastic Container Registry (ECR).
The polling mode selection is done by using Spring profiles. The polling client can be configured on several levels, i.e. directly via the applications properties files or by setting environment variables.
| Property | Value | Example |
|---|---|---|
| KAFKA_BOOTSTRAP_SERVERS | name:port | 127.0.0.1:19092 |
Depending on its retention policy your Kafka server might discard messages after a defined time period. You can set the retention policy for the broker by adjusting the value for the key log.retention.hours.
bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type brokers --entity-default --alter --add-config log.retention.hours=1073741824| Property | Value | Example |
|---|---|---|
| SPRING_PROFILES_ACTIVE | rest | rest |
| CAMUNDA_REST_URL | url to camunda rest api | http://localhost:8080/engine-rest/ |
| CAMUNDA_REST_USERNAME | (optional) username for authentication | demo |
| CAMUNDA_REST_PASSWORD | (optional) password for authentication | demo |
| CAMUNDA_REST_SOURCE_TIME_ZONE | (optional) Time zone used for formatting timestamps provided to camunda rest api (Default: System timezone) | CEST |
| CAMUNDA_REST_DATE_FORMAT_PATERN | (optional) Format string used for formatting timestamps provided to camunda rest api (Default: See example) | yyyy-MM-dd'T'HH:mm:ss.SSSZ |
| Property | Value | Example |
|---|---|---|
| SPRING_PROFILES_ACTIVE | jdbc | jdbc |
| CAMUNDA_JDBC_URL | jdbc url | |
| CAMUNDA_JDBC_USERNAME | db username | demo |
| CAMUNDA_JDBC_PASSWORD | db password | demo |
| Property | Value | Example |
|---|---|---|
| POLLING_RUNTIME_DATA_INITIAL_TIMESTAMP | (optional) initial start time the polling of runtime data (only relevant for initial polling); format: "yyyy-MM-dd HH:mm:ss". Default is the current time. |
2018-01-01 00:00:00 |
| POLLING_REPOSITORY_DATA_INITIAL_TIMESTAMP | (optional) initial start time the polling of repository data (only relevant for initial polling); format: "yyyy-MM-dd HH:mm:ss. Default is the current time." |
2018-01-01 00:00:00 |
Further configurations can be made via the application.properties file, e.g. setting the polling interval (default: every 30000 ms).
There are several tags available on Amazon Elastic Container Registry (ECR) and docker hub:
- Version tags (e.g. 1.0.2) are build from corresponding release tags and reflect the release version which is also available from maven central.
latestrefers the latest version.
All data is stored in /data. This is also the working directory and the only directory with write permissions.
All JAR files available in /app/lib are included in applications classpath. Adding e.g. an additional jdbc
driver can thus be done by just adding the driver library to /app/lib.
The project is operated and further developed by the viadee Consulting AG in Münster, Westphalia.
- Community contributions to the project are welcome: Please open Github-Issues with suggestions (or PR), which we can then edit in the team. For contribution please take account of our contributing guidelines.
- We are also looking for further partners who have interesting process data to refine our tooling as well as partners that are simply interested in a discussion about AI and data warehouses in the context of business process automation.
This library will remain under an open source licence indefinately.
We follow the semantic versioning scheme (2.0.0).
In the sense of semantic versioning, the resulting JSON outputs are the only public "API" provided here. We will keep these as stable as possible.
This software component is considered to be stable and ready for production use. However, we plan to extend on it if there is demand or if the Camunda APIs change.
This project is licensed under the BSD 3-Clause "New" or "Revised" License - see the LICENSE file for details.