Moving from sources to runnin enviroment

2005-04-14T10:39:01Z

Notice that all the users and passwords that you eventually created on the "running" portal are deleted/overwritten with the ones of the "source" portal.

This is the reason why a export of the db is so handy, then one just inerts new records. Thanks for sharing the solution, it is valuable for other people searching for answeres to the same problems.

Moving from sources to runnin enviroment

2005-04-14T09:58:48Z

The default database is the hypersonic database. I've never tried to do this but you might want to check out :<a href='http://hsqldb.sourceforge.net/' target='_blank'>Hypersonic</a>.  It is supposed to be management tools included in the full Hypersonic distribution there, it's worth a shot to check these tools out.

Solved. Just in case someone needs it : 0) save a copy of test.* from the "running" portal 1) in the "running" portal delete test.* files ( in tomcat theese are found under /bin dir ) 2) create an empty hsqldb ( with username sa and empty password ) in the directory you deleted the files previously and call it test 3) copy test.script from the "source" portal to the "running" portal this should do the trick . Notice that all the users and passwords that you eventually created on the "running" portal are deleted/overwritten with the ones of the "source" portal.

Moving from sources to runnin enviroment

2005-04-14T08:04:12Z

Hi, thanks for your reply. The database I am using ( at the moment ) is the default one ( HSQL ?? ) . Do you know if there's something internal to liferay to enable theese dumps or is it to be figured out ? TIA Marco

The default database is the hypersonic database. I've never tried to do this but you might want to check out :<a href='http://hsqldb.sourceforge.net/' target='_blank'>Hypersonic</a>. It is supposed to be management tools included in the full Hypersonic distribution there, it's worth a shot to check these tools out.

Moving from sources to runnin enviroment

2005-04-14T07:58:05Z

It really depends on database used. Usually there is some "dump" feature that produces SQL script which will re-insert the data. For MySQL, for example, it is called mysqldump.

Hi, thanks for your reply. The database I am using ( at the moment ) is the default one ( HSQL ?? ) . Do you know if there's something internal to liferay to enable theese dumps or is it to be figured out ? TIA Marco

Moving from sources to runnin enviroment

2005-04-13T21:46:45Z

Hi all. I have a "src" version of liferay that deploys and runs fine. Now, After having made the changes I need in /portal/ext dirs I need a way to reproduce all my changes to a "binary" version of liferay. What I did was put all the files that I have changed under a loca cvs tree and created a script that ( in case of disaster ) downloads the sources from liferay and applies the changes that I have saved under my cvs to the unpacked sources. Up to here no problems. My propbles arises when I try to do the same with the database ...  which ( obviously ) I cannot save "as is" . So what I need to know is how can I save all the modifications that concerns added pages, choosen colors, wich portlet is loaded in wich page, etc, and put it back in a new/binary installation ? TIA Marco

It really depends on database used. Usually there is some "dump" feature that produces SQL script which will re-insert the data. For MySQL, for example, it is called mysqldump.

Moving from sources to runnin enviroment

2005-04-13T13:24:01Z

Hi all. I have a "src" version of liferay that deploys and runs fine. Now, After having made the changes I need in /portal/ext dirs I need a way to reproduce all my changes to a "binary" version of liferay. What I did was put all the files that I have changed under a loca cvs tree and created a script that ( in case of disaster ) downloads the sources from liferay and applies the changes that I have saved under my cvs to the unpacked sources. Up to here no problems. My propbles arises when I try to do the same with the database ... which ( obviously ) I cannot save "as is" . So what I need to know is how can I save all the modifications that concerns added pages, choosen colors, wich portlet is loaded in wich page, etc, and put it back in a new/binary installation ? TIA Marco