I also write code and understand how hard it is to back off to a point
of sufficient ignorance to be able to write documentation for someone
who knows nothing about the wonderful thing that I just made.
It is easy to forget a step.
Easy to assume the "everyone knows this" or "this is obvious from the
section above".
Easy to get excited about some edge case that was a challenge to solve
and to skip over the normal use cases.
I am worried about the state of documentation as a criteria for adopting
OfBiz but if I go ahead with it, I will try to use my ignorance to
advantage in fixing the docs.
I appreciate the help that I get in these forums from people who are
donating their time or whose companies are donating it.
I will contribute to help return the favour.
Ron
On 04/06/2014 5:46 AM, Jacques Le Roux wrote:
Thanks, I will review and update.
It's never easy for someone which is acquainted with something to see
how someone new to it see it, moreover when time is passing.
We tend to see through our eyes, not the eyes of others, it's not a
matter of empathy or not, it's just like that (though empathy helps)
I found in my all life that this is a major problem we often neglect
or are sometimes not even aware of.
It's of course also a matter or resources, human resources are sparse
for open source projects like OFBiz...
Jacques
Le 03/06/2014 09:51, Ron Wheeler a écrit :
The thread has also been hijacked.
I finally got the information that is missing from the wiki page at
https://cwiki.apache.org/confluence/display/OFBTECH/Apache+OFBiz+Technical+Production+Setup+Guide.
The description about how to switch database technologies is missing
some key information
It needs to describe why 3 group-names need to be defined for the
database. I still don't know why one needs to have
- group-name="org.ofbiz"
- group-name="localmysqlolap"
- group-name="localmysqltenant"
all pointing to the same database but it is required.
Need an explanation.
The following steps need to be added to the list of things to be done
to set up the database to be in a technology other than Derby.
- Modify the "localmysql", "localmysqlolap" and "localmysqltenant"
datasources elements to connect to your database.
- Modify the "default" delegator element:
Change
<group-map group-name="org.ofbiz" datasource-name="localderby"/>
to
<group-map group-name="org.ofbiz" datasource-name="localmysql"/>
The OLAP and Tenant data sources will still use Derby. If you want to
change those to use MySQL also, then:
- Modify the "localmysqlolap" datasource element to connect to your
OLAP database.
- Modify the "localmysqltenant" datasource element to connect to your
Tenant database.
- Modify the "default" delegator element:
Change
<group-map group-name="org.ofbiz.olap"
datasource-name="localderbyolap"/>
to
<group-map group-name="org.ofbiz.olap"
datasource-name="localmysqlolap"/>
Change
<group-map group-name="org.ofbiz.tenant"
datasource-name="localderbytenant"/>
to
<group-map group-name="org.ofbiz.tenant"
datasource-name="localmysqltenant"/>
Pbviously this needs to be described in terms that can apply to other
DB technologies.
That got me past the "ant load-demo".
Ron
On 03/06/2014 3:11 AM, Jacques Le Roux wrote:
And please use rather the user ML for such discussions, see why here
: http://ofbiz.apache.org/mailing-lists.html
Jacques
Le 03/06/2014 08:40, Pierre Smits a écrit :
Hi James,
>From the posting Ron wrote I can't determine what specific use
case he is
trying to address, but OFBiz does allow companies to work with
multiple
currencies.
Are you working on the same aspect, or together? If so, please
provide more
details.
Regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
