Persisting async history data in NoSQL DB

Hi Flowable team,

We are using flowable spring boot version 6.2.0 need to separate the Runtime data (goes into MySQL DB) and History data (goes into Cassandra/MongoDB)

I have enabled these configurations:

flowable.database-schema-update=true
flowable.async-executor-activate=true
flowable.history-level=full
flowable.db-history-used=false
flowable.db-identity-used=true

After this configurations i have deployed my application only the runtime tables got created in mysql db, but i need to add a new datasource for other NoSQL DB to store history data.

How can this be done ?

Thanks,
Manjunath

2 Likes

Have a look at the async history example: https://github.com/flowable/flowable-examples/tree/master/async-history or this example: https://github.com/flowable/flowable-examples/tree/master/demo/demo-introducing-machine-learning/demo-process. You can use the async history to have a queue in between and them send it to Cassandra/MongoDB. Note that this can’t be configured through properties yet, so you’ll need a Spring bean configuration if the process engine config and processEngine.

2 Likes

Thanks @joram.

So, I need to publish all the async history to Rabbit MQ and from there i need to have a listener which listens to that message and then persist the data to the tables i have created manually right ? And also, I have to create the tables manually by myself right?

Thanks,
Manjunath

1 Like

@mtmanju : sorry missed your response.
Yes - indeed: you’ll need to create the tables yourself, and in the listener you can do whatever you want with the json that comes in.
Also, doesn’t need to be RabbitMQ, can be any message queue or protocol :-).

2 Likes

Thanks @joram :slight_smile:

Hi @mtmanju

can please tell how did you done the same problem, Actually i am new in the flowable
i need to persist the flowable history data into mongo db