It didn’t work for me. I need to upgrade from 1.0.009 to 1.2 and to
migrate from pgsql to mysql. Since we have 1.0.009 in a production
server, I need to test the upgrades and migration in a devel server.
Here’s a step-by-step breakdown of what I did. I think the poblems are
in the 1.0.009->1.2 upgrade, but still can’t prove it.
- In the production server, dump the database:
pg_dump --no-owner --disable-triggers --data-only
-f egroupware-data-date +%Y%m%d.sql egroupware
[code:1:323d9a0649]pg_dump --schema-only -f egroupware-schema-date +%Y%m%d.sql egroupware[/code:1:323d9a0649]
2. (In the devel server:) install egw from 1.0.007. Upgrade to
1.0.009. Had to do it this way, since I found out that if I didn’t, a
clean install fo 1.0.009 would put the wiki and other apps under
tables with ‘egw_’ prefix, and that wouldn’t let me restore the
schema and contents for the DB we have in the production server.
3. restore DB I got from the production server:
[code:1:323d9a0649]psql egroupware < egroupware-schema.sql
[/code:1:323d9a0649]
[code:1:323d9a0649]psql egroupware < egroupware-contents.sql
[/code:1:323d9a0649]
4. modify some config values so that this installation will work:
[code:1:323d9a0649]egroupware=# update phpgw_config set
config_value=’/~user/egwpostgres’ where config_app=‘phpgwapi’ and
config_name=‘webserver_url’;[/code:1:323d9a0649]
[code:1:323d9a0649]egroupware=# update phpgw_config set
config_value=’/home/user/egwpostgresfiles/’ where
config_app=‘phpgwapi’ and
config_name=‘files_dir’;[/code:1:323d9a0649]
[code:1:323d9a0649]egroupware=# update phpgw_config set
config_value=‘develserver’ where config_app=‘phpgwapi’ and
config_name=‘hostname’;[/code:1:323d9a0649]
5. upgrade from 1.0.009 to 1.2.
6. make a backup of 1.2 using the backup tool.
7. clean install of egw 1.2 on mysql DB.
8. restore backup of 1.2 on psql DB on the newly installed version on
mysql.
9. After restoring the backup, I had to modify again the values
modified in step 4.
I think that’s all. I have the following problems:
a) Trouble Ticket System: not working. In the production server we
have a working TTS configured so that all users can assign new
tickets to one user. I can see (from mysql) that the registers are
there, but cannot see all tickets in the new version.
b) Calendar: one of the users’ calendars gets all messed up. It’s an
admin user, so I suspect it has something to do with how acl
privileges are handled, either after the restoration of the DB or
after the upgrade, still have to carry out some tests though.
Your help would be greatly appreciated 
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users