the db_name has to be specified properly in the jdbc-uri eg:
jdbc-uri="jdbc:mysql://127.0.0.1/test_ofbiz?autoReconnect=true <http://127.0.0.1/ofbiz?autoReconnect=true>"... jdbc-uri="jdbc:mysql://127.0.0.1/test_ofbizolap?autoReconnect=true <http://127.0.0.1/ofbiz?autoReconnect=true>"... an so on. On Sat, Aug 26, 2017 at 2:12 PM, Craig Parker <[email protected]> wrote: > <inline-jdbc > jdbc-driver="com.mysql.jdbc.Driver" > jdbc-uri="jdbc:mysql://127.0.0.1/ofbiz?autoReconnect=true"... > > > If I've created three new DBs, each with a test_ prefix (test_ofbiz, > test_ofbizolap, and test_ofbiztenant) has this got to say: ... > 127.0.0.1/test_ofbiz... in each of the three relevant datasource > sections? I've tried and failed, but just not sure yet if this is what's > screwy, or something else. > > > > On 08/26/2017 03:36 AM, Deepak Dixit wrote: > >> Hi Craig, >> >> You can use portoffset feature >> Please reade README.md file for example >> >> Thanks & Regards >> -- >> Deepak Dixit >> www.hotwaxsystems.com >> www.hotwax.co >> >> On Sat, Aug 26, 2017 at 12:44 PM, Craig Parker <[email protected]> >> wrote: >> >> I've got OFBiz up and running on my Linux laptop with a MySQL backend. Is >>> it possible to have another instance running somehow at the same time >>> that >>> uses a different DB? Well, maybe three different DBs -- looks like I'm >>> currently using ofbiz, ofbizolap, and ofbiztenant. >>> >>> What I'm aiming for is to have a "live" and a "play" area eventually. If >>> I >>> want to go try something, I want to keep from breaking my install. >>> >>> Initially though, I want to have the default data in one, and the other a >>> blank slate. >>> >>> Right now the install is sitting in /ofbiz and being started up with a >>> bash script via systemctl. I've not tried it yet, but I'm wondering if I >>> have to create the three new DBs, and duplicate what I have in /ofbiz to >>> something like /ofbiz-play, then create a similar startup script that >>> fires >>> up things in that /ofbiz-play directory. >>> >>> >>> >
