regarding blank database:

you may keep the db in shutdown state for a while  and attempt to operate
the ofbiz instance
if it still operates and does not complaint of db being down , it may mean
that its using the
embedded database derby only.

please check on following

(1) Did you change the delegator tags in entityengine.xml ?
(2) after changing entityengine.xml i had to run gradlew to make below 2
identical

./framework/entity/config/entityengine.xml
./build/resources/main/entityengine.xml

I think the runtime uses the latter.

I hope you have come across the below link

https://cwiki.apache.org/confluence/display/OFBIZ/How+to+migrate+OFBiz+from+Derby+to+MySQL+database

which i used to configure my postgres with ofbiz .


Also : working version of my entityengine.xml ( with passwords masked)

https://pastebin.com/17XcW0Bb


>> " I'm not sure what to make of the http lines in Rajesh's reply.  ... "

the http lines were created by conversion of links (created by gmail)
to text/plain by the mailing list software (ezmlm)  ( i use gmail composing)
it was not typed by me.

Hope it helps.

regds
mallah.


On Sun, Aug 27, 2017 at 10:02 AM, Craig Parker <[email protected]> wrote:

> Well, I've got two instances, but they're using the same db. I loaded demo
> data from within /ofbiz and was able to launch with said demo data. I shut
> down ofbiz, then moved to /test-ofbiz, ran ./gradlew "ofbiz --load-data
> readers=seed,seed-initial,demo" and my test_xxx DBs are still blank. I
> fired up the regular instance of ofbiz (on port 8443) and have a blank DB.
> Here's a snippet of my entityengine.xml. I've got three new DBs setup,
> test_xxx (where xxx are the same as my regular install). I'm not sure what
> to make of the http lines in Rajesh's reply. Those wouldn't have anything
> to do with gradle writing to the DB anyway, would they?
>
> Everyone's PostgreSQL comments are duly noted, by the way. I'd been
> contemplating moving at some point anyway (heard years ago it's better at
> maintaining connections over a network than MySQL-- not sure if that's
> still true) but since I'm this far along, and trying to keep track of
> making it work for the sake of documentation, I'm going to keep trucking
> down this road for the moment.
>
> <datasource name="localmysql"
> helper-class="org.apache.ofbiz.entity.datasource.GenericHelperDAO"
>             field-type-name="mysql"
>             check-on-start="true"
>             add-missing-on-start="true"
>             check-pks-on-start="false"
>             use-foreign-keys="true"
>             join-style="ansi-no-parenthesis"
>             alias-view-columns="false"
>             drop-fk-use-foreign-key-keyword="true"
>             table-type="InnoDB"
>             character-set="latin1"
>             collate="latin1_general_cs">
>         <read-data reader-name="tenant"/>
>         <read-data reader-name="seed"/>
>         <read-data reader-name="seed-initial"/>
>         <read-data reader-name="demo"/>
>         <read-data reader-name="ext"/>
>         <read-data reader-name="ext-test"/>
>         <read-data reader-name="ext-demo"/>
>         <inline-jdbc
>                 jdbc-driver="com.mysql.jdbc.Driver"
> jdbc-uri="jdbc:mysql://127.0.0.1/test_ofbiz?autoReconnect=true"
>                 jdbc-username="ofbiz"
>                 jdbc-password="password"
>                 isolation-level="ReadCommitted"
>                 pool-minsize="2"
>                 pool-maxsize="250"
>                 time-between-eviction-runs-millis="600000"/>
>     </datasource>
>
>
> On 08/26/2017 04:46 AM, Rajesh Mallah wrote:
>
>> 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.
>>>>>
>>>>>
>>>>>
>>>>>
>

Reply via email to