Hope this post clarifies the reasons why you would need a XA Datasource when your JavaEE Application has to store data in two different places using a single transaction. (Or for example, when you want to use PVP to store the domain information from your project in a different database from the one used by jBPM to store its data.)
Tag: persistence
Run and access PostgreSQL DB in 30 seconds [4steps]
Quick and simple, as should every technology be. Here's a quick step-by-step to bootstrap and access a local PSQL Database without needing to install it: Pre-req: Docker #TLDR; Ready... Set... Go: mkdir -p $HOME/docker/opt/db/psql docker run --rm --name psql-jbpm -e POSTGRES_PASSWORD=psql@123 -d -p 6543:5432 -v $HOME/docker/opt/db/psql:/var/lib/postgresql/data postgres:9.4 That's it, now you have a local psql… Continue reading Run and access PostgreSQL DB in 30 seconds [4steps]
Persisting custom process variables in different DB on jBPM
Intro So you want to store the data used in your process separately from jBPM database schema. To achieve this, you need to use Pluggable Variable Persistence. This is an objective post on the requirements to implement PVP on your project. TLDR; Sample project repo with a working example: pvp-sample The persistable classes needs to… Continue reading Persisting custom process variables in different DB on jBPM
Keep Kalm 