-
1. Re: JBPM 6 Virtual File System - where are the files actually stored?
swiderski.maciej Oct 1, 2014 2:09 AM (in response to badtea)files are stored in git repository that is under .niogit folder. If not configured differently it will be in current directory although it might be reconfigured via system properties. So there are three important location that you should set to preserve them across container restarts:
- org.uberfire.nio.git.dir
- org.uberfire.metadata.index.dir
- org.guvnor.m2repo.dir
HTH
-
2. Re: Re: JBPM 6 Virtual File System - where are the files actually stored?
badtea Oct 1, 2014 9:51 AM (in response to swiderski.maciej)Thanks swiderski.maciej!
I created a simple BPMN process with a script task that outputted those three properties you mentioned. All the properties were printed as null. Does that mean they are simply set to the defaults that are listed on the documentation page? I looked through the filesystem, and it does look like they are being stored in the default locations.
So I could either persist those three directories, or simply persist the entire "jbpm-installer" directory. I will have to decide the best approach and try this later today.
Thanks again!
-
3. Re: JBPM 6 Virtual File System - where are the files actually stored?
swiderski.maciej Oct 2, 2014 1:56 AM (in response to badtea)correct, if the properties are not set then defaults apply. Personally for real deployments (e.g. production) I'd go for defining locations for these folders via properties, easier to move installation around while keeping same storage.
HTH
-
4. Re: Re: JBPM 6 Virtual File System - where are the files actually stored?
badtea Oct 3, 2014 8:59 AM (in response to swiderski.maciej)Thanks swiderski.maciej! I'm using the defaults now to get it working, but I'm probably going to use the system properties in the future. Anyway, I preserved those three folders that you mentioned, and now my business processes are persisted across container restarts.