I didn't really discuss this much when I did the change a few weeks
ago as it is something that has been discussed in the past but was
waiting for realization.
There is now a new EE data file set called "seed-initial" that is
meant to only be loaded the first time. I originally added this so
that scheduled services would not get reloaded over and over, causing
multiple sets of service to run at once. In other words previously if
you loaded the seed data after a code update 10 times you would have
11 (10 plus the initial one) scheduled instances of the back order
checking service, the entity sync remove cleanup service, and so on
all running.
To help with this problem I just added the securityext/data/
PasswordSecurityData.xml file to the seed-initial file set. Now if you
just load the "seed" data it won't reset the passwords.
I did notice that this file doesn't have all of the passwords in it
anymore though... but at least admin, system, and anonymous are in
there. In a way this is good because most other users are in the demo
data, and their passwords are with them there, so updating the "seed"
data file set is still safe.
-David
On Mar 1, 2008, at 1:29 PM, Jacopo Cappellato wrote:
Case Torres wrote:
Hi,
I want to make sure I understand what this command does before I
run it on
my production server.
It will install the seed data but not the demo data.
It will *NOT* remove any data currently in the database.
Is this correct??
It is correct.
Another thing to mention is that the password for the "admin" user
(and the flexadmin etc) will be overriden (to "ofbiz").
You'll have to change them right after the update.
Jacopo
Thanks much,
---
Case Torres
[EMAIL PROTECTED]
