...
Claim configuration
You can enabled or disbale enable or disable claiming/cancel claiming of Camunda Tasks after a TASKANA task was claimed/cancel claimed with the following boolean property:
...
| Code Block |
|---|
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
...
| Code Block |
|---|
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= |
Adapter Clustering
Locking of the entries in the events table is configured by the parameter taskana.adapter.events.lockDuration
that describes the duration of the lock for one event in seconds. The parameter is set to zero by default. To enable running multiple Adapter instances, the parameter needs to be configured to a suitable positive number. A good value for taskana.adapter.events.lockDuration depends on the application.
Batch Size
The number of Tasks that are synchronized from Taskana to Camunda at once is configured in taskana.adapter.sync.taskana.batchSize