Another possible option (which I've never tried), is to use the multi tenancy functionality to allow two different sets of data without needing to restart OFBiz or run multiple instances.
Regards Scott On 12 October 2016 at 07:40, Craig Parker <[email protected]> wrote: > I was initially thinking of having two xml files (test.xml and clean.xml) > with appropriate settings in each, and just running cat test.xml > > entityengine.xml (or cat clean.xml --whicever one I'm going to run) but > will this mean I have to sit for a few minutes after each switch while > OFBiz loads? Not sure if this is a better or worse idea than two instances > of OFBiz running. Six of one, a half-dozen of the other? > > > > On 10/10/2016 11:35 PM, Taher Alkhateeb wrote: > >> Hi Craig, >> >> Take a look at the data loading tasks in README.md as it shows you >> different data loading scenarios for different environments. >> >> You can switch between two databases, but not the way you might recognize >> it in Ruby on Rails or so. If the two databases are both embedded (Derby) >> then you have to switch their folders manually in between restarts. If >> they >> are standalone like postgres then you have to update entityengine.xml in >> between restarts. >> >> I hope that helps, good luck OFBizzing. >> >> Taher Alkhateeb >> >> On Oct 11, 2016 6:21 AM, "Craig Parker" <[email protected]> wrote: >> >> Is there a doc somewhere on starting with a fresh DB? I'm still tooling >>> with the data that comes with a default install, but I'm going to want >>> another "squeaky clean" DB to be playing with also. >>> >>> There's nothing saying I can't have two instances of ofbiz running on the >>> same server is there, or is there a better way to swap back and forth >>> between the "test" DB that I'm currently running and what will eventually >>> be my live DB in a hurry? >>> >>> >>> >
