7.1.0-M13
Release 7.1.0-M13
You can consume all the Activiti artifacts for this release from Alfresco Nexus:
1
<repositories>
2
<repository>
3
<id>activiti-releases</id>
4
<url>https://artifacts.alfresco.com/nexus/content/repositories/activiti-releases</url>
5
</repository>
6
</repositories>
Copied!
Activiti Cloud:
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti.cloud</groupId>
5
<artifactId>activiti-cloud-dependencies</artifactId>
6
<version>7.1.0-M13</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!
Activiti Core
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti</groupId>
5
<artifactId>activiti-dependencies</artifactId>
6
<version>7.1.0-M13</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!
- ​Add support for partitioned message streams: messages used to transfer data from the runtime bundle to query and audit service can be partitioned. There will be as many instances of the consumer as the number of partitions. Each instance will consume data from a single partition. In Helm deployment, partitioning can be enabled by providing the following extra values (
partitionCountdefines how many partitions will be used and the Helm deployment will create that many replicas of query service using aStatefulSetrather than aDeployment):
1
global:
2
messaging:
3
# global.messaging.partitioned -- enables partitioned messaging in combination with messaging.enabled=true && messaging.role=producer|consumer
4
partitioned: true
5
# global.messaging.partitionCount -- configures number of partitioned consumers
6
partitionCount: 2
Copied!
Result of
kubectl get pods:1
NAME READY STATUS RESTARTS AGE
2
m13-activiti-cloud-connector-66bb74576-j42hm 1/1 Running 0 153m
3
m13-activiti-cloud-modeling-769fcb67b5-kx9qk 1/1 Running 0 153m
4
m13-activiti-cloud-query-0 1/1 Running 0 153m
5
m13-activiti-cloud-query-1 1/1 Running 0 153m
6
m13-activiti-modeling-app-847d8dfbb-2lggd 1/1 Running 0 153m
7
m13-keycloak-0 1/1 Running 0 153m
8
m13-postgresql-0 1/1 Running 0 153m
9
m13-postgresql-id-0 1/1 Running 0 153m
10
m13-runtime-bundle-7d568d9844-5vhtq 1/1 Running 0 153m
11
rabbitmq-0 1/1 Running 0 153m
Copied!
- ​Add Activiti Cloud application support for Kafka binder: in addition to Rabbit MQ binder (that remains the default one), the example docker images generated by activiti-cloud-application are also embedding Kafka binder. In order to use it instead of Rabbit MQ binder, pass the following values during Helm deployment:
1
global:
2
messaging:
3
broker: kafka
4
kafka:
5
enabled: true
6
rabbitmq:
7
enabled: false
Copied!
Result of
kubectl get pods:1
NAMESPACE NAME READY STATUS RESTARTS AGE
2
m13-kafka activiti-activiti-cloud-connector-6ff67bc988-s88jj 1/1 Running 0 4h35m
3
m13-kafka activiti-activiti-cloud-modeling-98499f5d5-lw9hd 1/1 Running 0 4h35m
4
m13-kafka activiti-activiti-cloud-query-fd5bcbc9f-89jrl 1/1 Running 0 4h35m
5
m13-kafka activiti-activiti-modeling-app-bbd8d97c8-qnl46 1/1 Running 0 4h18m
6
m13-kafka activiti-keycloak-0 1/1 Running 0 4h35m
7
m13-kafka activiti-postgresql-0 1/1 Running 0 4h35m
8
m13-kafka activiti-postgresql-id-0 1/1 Running 0 4h35m
9
m13-kafka activiti-runtime-bundle-865895df8d-hhgwm 1/1 Running 0 4h35m
10
m13-kafka kafka-0 1/1 Running 0 4h35m
11
m13-kafka zookeeper-0 1/1 Running 0 4h35m
Copied!
Kafka or Rabbitmq message brokers can be deployed conditionally as part of Helm release using
rabbitmq.enabled or kafka.enabled. The default values for Kafka and Rabbitmq have been set up to use message brokers provided with the Helm chart. It is possible to disable message broker deployments and use external Kafka or Rabbitmq by overriding global.kafka or global.rabbitmq values, i.e. global.kafka.brokers (Multiple brokers can be provided in a comma-separated list, e.g. host1:port1,host2:port2),global.kafka.zkNodes (External Zookeeper nodes).Changes from previous milestones
Last modified 5mo ago