To configure the adapter the following properties must be set in the application.properties file of your Spring Boot adapter application:
Scheduled methods:
Time intervals for the different scheduled methods in milliseconds which are performed by the adapter.
Example for a pull every 10 seconds:
taskana.adapter.scheduler.run.interval.for.start.taskana.tasks.in.milliseconds=10000
All available properties:
taskana.adapter.scheduler.run.interval.for.start.taskana.tasks.in.milliseconds= taskana.adapter.scheduler.run.interval.for.complete.referenced.tasks.in.milliseconds= taskana.adapter.scheduler.run.interval.for.claim.referenced.tasks.in.milliseconds= taskana.adapter.scheduler.run.interval.for.cancel.claim.referenced.tasks.in.milliseconds= taskana.adapter.scheduler.run.interval.for.check.finished.referenced.tasks.in.milliseconds=
To use JaasSubject for scheduled methods, add this property :
taskana.adapter.run-as.user
example: taskana.adapter.run-as.user=peter
The provided userId has to have the needed taskadmin-role, which can be configured in the taskana.properties
Claim configuration
You can enable or disable claiming/cancel claiming of Camunda Tasks after a TASKANA task was claimed/cancel claimed with the following boolean property:
taskana.adapter.camunda.claiming.enabled
TASKANA datasource and schema
The adapter connects to TASKANA via JDBC, therefore you need to provide a datasource and schema in the application properties:
taskana.datasource.jdbcUrl = taskana.datasource.driverClassName = taskana.datasource.username = taskana.datasource.password = taskana.schemaName=
System Connectors
When synchronizing from TASKANA to Camunda, the adapter connects to Camunda via REST-API.
When synchronizing from Camunda to TASKANA, the adapter retrieves events from Camunda Tasks via REST-API of the separate Outbox-REST Service.
Therefore you need to provide the corresponding URLS to these services in the following property:
taskana-system-connector-camundaSystemURLs
The URLs are delimited by a “|”. The first argument must be the Camunda REST-API URL and the second one must be the Outbox-REST URL.
example:
taskana-system-connector-camundaSystemURLs=http://localhost:${server.port}/rest/engine/default | http://localhost:${server.port}/outbox-rest
To synchronize from/to multiple camunda system, you can configure multiple of those pairs with a delimiter of “,”. For each pair a SystemConnector will be created.
example for 2 camunda systems:
taskana-system-connector-camundaSystemURLs=http://localhost:10020/rest/engine/default | http://localhost:10020/outbox-rest, http://localhost:10021/rest/engine/special | http://localhost:10021/outbox-rest
It is also possible to have multiple camunda systems share the same outbox. In that case you will have to provide a system engine identifier (the name of the camunda engine) as a third argument in the configuration.
example for 2 camunda systems sharing the same outbox:
taskana-system-connector-camundaSystemURLs=http://localhost:10020/rest/engine/default | http://localhost:10020/outbox-rest | default, http://localhost:10021/rest/engine/special | http://localhost:10020/outbox-rest | special
This system engine identifier is necessary in order for the CamundaSystemConnectors to only process events from their respective camunda system.
Object Reference defaults
A TASKANA task can’t be created without a primary object reference object. Since a referenced task doesn’t directly carry information about the POR, some defaults have to be provided and are configurable with the following properties:
taskana.adapter.mapping.default.objectreference.company= taskana.adapter.mapping.default.objectreference.system= taskana.adapter.mapping.default.objectreference.system.instance= taskana.adapter.mapping.default.objectreference.type= taskana.adapter.mapping.default.objectreference.value=