For those who have attempted to use a remote database before, there is actually a much more complicated solution for 3.0 than has been presented by others..
My fears were well-founded, it turns out .. Nowhere is it documented that the war files are prepackaged with a magnolia/repositories/magnolia/* directory that has all the repository paths hard-coded to the derby repository. Also, the bootstrap files for both magnoliaPublic.war and magnoliaAuthor.war both make the repository into an admin repository when you rebuild it, instead of magnoliaPublic.war making the repository into a public one, and magnoliaAuthor.war making it into an admin one. So, until the war files are packaged such that the bootstrap directories are used to generate the repositories for the first time, we must do the following... First, remove: webapps/magnoliaAuthor/repositories/magnolia webapps/magnoliaPublic/repositories/magnolia Then, change: webapps/magnoliaAuthor/WEB-INF/config/repo-conf/jackrabbit-mysql-search. xml and: webapps/magnoliaPublic/WEB-INF/config/repo-conf/jackrabbit-mysql-search. xml To have two distinct mysql databases (I used magnolia_author and magnolia_public) Then, change: webapps/magnoliaAuthor/WEB-INF/config/default/repositories.xml and: webapps/magnoliaPublic/WEB-INF/config/default/repositories.xml To use the jackrabbit-mysql-search.xml instead of jackrabbit-derby-search.xml Then, change: webapps/magnoliaPublic/WEB-INF/bootstrap/common/config/config.modules.ad minInterface.virtualURIMapping.default.xml To have the "toURI" property to be set to "/help" instead of "/.magnolia/adminCentral.html" Then, change: webapps/magnoliaPublic/WEB-INF/bootstrap/author/config/config.server.xml To have the "admin" property to be set to "false" instead of "true" Then, remove: webapps/magnoliaPublic/WEB-INF/bootstrap/author/config/config.server.sec ureURIList.root.xml (this will cause an exception to occur the first time the app is started up because there is no secureURIList, which is fine for a public site's default configuration.. perhaps there's a better way to do this..) Then, copy your mysql-connector-java-x.x.x.jar into each of the magnolia*/WEB-INF/lib directories. THEN Start up Tomcat, which will recreate the two repositories based off the properly configured data in the bootstrap directories, storing the data for each in the appopriate database. To configure the public instance directly, use http://localhost:8080/magnoliaPublic/.magnolia If there are any developers reading this, please let me know if I've missed anything. This particular configuration works out-of-the box for us, so I recommend the war files be changed appropriately. -Stephen. > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 28, 2006 9:39 AM > To: [email protected] > Subject: Re: [magnolia-user] Difficulties setting up Magnolia > > Changing persistence manager and/or database implementation > away from default is not something that should be undertaken > without some basic knowledge of Magnolia and Jackrabbit. If > you're afraid to touch stuff you won't get very far :) ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
