After some research in this forum and my understanding of chapter 5 of the docs, I came to the conclusion that I will need one knowledge session per process instance.

I use jbpm5.3, with spring integration and persistence.

1 - For what I realized, the spring integration does not allow the "one knowledge session per process instance" architecture that I require. Is that true?

2 - I've found the possibility of defining the id of the ksession that will be loaded during boot

(...)
<jbpm:ksession id="ksession" type="stateful" kbase="kbase1">
     <jbpm:configuration>
          <jbpm:jpa-persistence load="1">
               <jbpm:transaction-manager ref="transactionManager"/>
               <jbpm:entity-manager-factory ref="entityManagerFactory2" />
          </jbpm:jpa-persistence>
     </jbpm:configuration>
</jbpm:ksession>
(...)

The load parameter allows to load the ksession with the given id, but it fails to do so the first time it boots (as there is no ksession in the DB). So, even if I consider to have only one ksession for all process instances, I will have to implement some workaround to load the app for the first time. It is supposed to be like that? (The goal is to create a config file that does not need to be changed)