Document URL: Section Number and Name: Describe the issue: According to Maciej in BZ 1193789, the deployment units moved from git repository to database. Therefore, when we create a new deployment unit it is persisted into the database instead of the system.git repository. Since BPMS 6.1.0, this is default behaviour, however, it is still possible to use git repository for backward compatibility by setting 'org.kie.git.deployments.enabled' system property to true. Maciej also mentions that this change was "introduced as part of EJB/services work as without db storage it would require always to be setup with zookeeper and helix which complicates the runtime architecture especially that it does sync only system.git as for runtime there won't be anything else." It might be also good to describe what is happening during migration: "First time it will run on new setup it will read up from system.git and deploy into runtime which will result in db store. At the same time it will remove it from system git to clean it up completely." Suggestions for improvement: Additional information:
I have added this as a note in the Project Deployments section of the User Guide here [1] AND the Migration Guide in the topic 6.0 --> 6.1 Changes here [2]. The Migration Guide description is more detailed than the User Guide one. Moving this to ON_QA. [1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/User_Guide/#chap-Deploying_projects [2] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Migration_Guide/#Migrating_from_6.0.x_to_6.1
Verified in the User Guide and Migration Guide.