Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
Moving from sources to runnin enviroment
Hi all.<br /><br />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 ?<br /><br /><br />TIA <br /><br /><br />Marco
13041, 21 Jaren geleden aangepast.
Junior Member
Berichten: 76
Aanmelddatum: 28-2-05
Recente berichten
Hi all.<br /><br />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 ?<br />TIA <br />Marco<br /><br /><br /><br />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.<br /><br /><br />
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.<br /><br /><br />Hi,<br />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 ? <br /><br />TIA <br /><br /><br />Marco
Hi,<br />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 ? <br /><br />TIA <br />Marco<br /><br /><br />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.
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.<br /><br /><br />Solved.<br />Just in case someone needs it :<br />0) save a copy of test.* from the "running" portal <br />1) in the "running" portal delete test.* files ( in tomcat theese are found under /bin dir ) <br />2) create an empty hsqldb ( with username sa and empty password ) in the directory you deleted the files previously and call it test<br />3) copy test.script from the "source" portal to the "running" portal<br /><br />this should do the trick . <br /><br />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.
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.<br /><br /><br />This is the reason why a export of the db is so handy, then one just inerts new records.<br /><br />Thanks for sharing the solution, it is valuable for other people searching for answeres to the same problems.<br /> <br />
Community
Company
Feedback