It's nice to know that I can choose which database to use for Ametys repository. I am thinking of using MySQL or HSQLDB for the repository. I'll probably have to change repository.xml.
I'm wondering if there's a way to convert the existing derby repository to MySQL.
Ken
]]>At the end, you'll effectively store your data in a MySQL database, but yon won't be able to access each content and each field directly with SQL requests.
I hope to have been clear enough
Cédric
]]>We currently use the derby db (even in production) but if you prefer you can configure jackrabbit to use a mysql impl. The repository.xml file is in the WEB-INF/param directory. See the jackrabbit doc here to know more about this file
]]>I'll use the scripts you posted in the meantime.
I have another question. I am curious about the database used for the content repository. Is it flat-file database, derby or some other database? I hope I could use MySQL for the repository, too.
Ken
]]>In the meanwhile, you can get the missing scripts directly at
]]>Thanks for your answer. I'll use a single database for all 3 occasions. Can I just use the database scripts included in Ametys to create the database? The scripts don't seem to create tables for page cache statistics.
Ken
]]>We use three connections for :
- kernel : CMS users/groups/rights/... : is accessed only by the back-office
- monitoring : page cache statistics : is accessed by both back- and front-office
- front-office : site users/groups/rights/... : is accessed by both back- and front-office
We allow setting up three different databases, but in the great majority of cases, the same one is used three times, given that is is accessible by both back- and front-office application.
Cédric
]]>I am trying to install Ametys 3.5 and have questions about the databases used in Ametys 3.5. In the back office configuration page, I see 3 separate databases to fill in: Kernel, monitoring and front-office. Can somebody tell me what I should enter for each database? Please see the attachment.
Thanks.
Ken
]]>