[OFBiz] Dev - Upgrading running copy

[Si Chen]

My suggestion is similar:
1.  First, figure out how much the database would change.  You can do 
this by letting the new version create a database from scratch and 
comparing some tables.  You can also write a script to diff all the 
different entitymodel.xml files.
2.  Do a test: make a copy of your old database and let the new version 
point to it.  The new instance would modify the database.  See if it 
would run.  Sometimes the change in data model could cause some services 
to crash.  (I had this problem upgrading from 3.0 to 3.1 with the 
JobSandbox entity.)
3.  Once the test works, set up the a new version in production mode and 
point it to your production database.  Have your users start using this 
new version (perhaps by changing your mod_jk ports to point to the new 
version?)
4.  Upgrade the old version by taking it down, rebuilding, and upgrading.


I hope this helps.

Si

Rafiu Fakunle wrote:

> About 8 weeks old. I don't actually know how much the db / data model 
> has to change hence my question :).
>
> Any recommended ways of doing this?
>
> Cheers,
>
> Rafiu.
>
> Si Chen wrote:
>
>> How old is the live installation?  How much would the database or 
>> data model have to change?
>>
>> Rafiu Fakunle wrote:
>>
>>> Hi there,
>>>
>>> What's the best way to migrate an existing live CVS installation to 
>>> the latest SVN tree  (including data in DB)?
>>>
>>> Cheers,
>>>
>>> Rafiu.
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> Dev at lists.ofbiz.org
>>> http://lists.ofbiz.org/mailman/listinfo/dev
>>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.ofbiz.org
>> http://lists.ofbiz.org/mailman/listinfo/dev
>
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.ofbiz.org
> http://lists.ofbiz.org/mailman/listinfo/dev
>