Where are these demo data files located?  Is there any documentation
specifically on these demo data files?  I want to remove all of the
invoices, sales orders, extra users, etc.

Thanks,
Tim


> From: Raj Saini <rajsa...@gmail.com>
> Reply-To: <user@ofbiz.apache.org>
> Date: Sat, 04 Jun 2011 11:21:21 +0530
> To: <user@ofbiz.apache.org>
> Cc: David E Jones <d...@me.com>
> Subject: Re: Best way to remove demo data?
> 
> Also, define your modified data as "ext" in ofbiz-component.xml. This
> will help you keeping, seed, ext and demo separately and you can load
> ext+seed data.
> 
> Thanks,
> 
> Raj
> 
> On Saturday 04 June 2011 02:42 AM, David E Jones wrote:
>> Take a look at the Business Production Setup Guide and the Technical
>> Production Setup Guide.
>> 
>> The easiest way (IMO) to handle what you're describing is to modify the demo
>> data files to match your desired configuration, and then load just your
>> modified files along with the seed data.
>> 
>> It's also nice to have a test system somewhere with all of the demo data so
>> you can try out various features without having to configure/etc first.
>> 
>> -David
>> 
>> 
>> On Jun 3, 2011, at 12:59 PM, Tim Stoel wrote:
>> 
>>> I have OfBiz 10.04 installed on a local server with MySQL as the database
>>> engine, we¹ve been working with this for about six months now. We are
>>> intending to use OfBiz for eCommerce, as well as sales order processing for
>>> eBay orders and have made a lot of progress in adapting it to our business.
>>> When we installed OfBiz, there is a lot of demo data in the database.  I
>>> wondered what the best way is to deal with this data.  When I setup OfBiz
>>> with only seed data, it seemed a lot of things were not configured that were
>>> useful, which is why I went back to using all of the demo data.  Should it
>>> be deleted one record at a time manually using another database tool?  What
>>> is the best path to get from an install of OfBiz to using it without the
>>> excess demo entries?  Is there any documentation on this?
>>> 
>>> Thanks,
>>> Tim
>> 
> 


Reply via email to