Thanks for the feedback guys. I think you're missing my question though. I have changed the magnolia.repositories.home to point to a place outside of my expanded WAR because I want the content and such to persist after I reload my app. It's located at /opt/repositories. Within my WAR I have WEB-INF/config/PhysicalMachineName/magnolia.properties. When the app starts up it sees that file and uses the repository home at /opt/repositories. But since I want to have two instances on the same physical they both want to use that same repository home. How do I tell one app to use /opt/repositories and another to use /opt/repositoriesTest?
Thanks again for all the help, Scott On Tue, Mar 4, 2008 at 9:54 AM, Ryan Gardner <[email protected]> wrote: > > On Mar 4, 2008, at 9:45 AM, Scott Anders wrote: > > > Hey Guys, > > > > I can't figure out how to do this. I have one physical box for our > > dev and test environments. I want to run two magnolia instances on > > there. In the WEB-INF/configs I have the machine name and then a > > magnolia.properties file that points to the repository location on the > > hard drive. I want both the dev instance and test instance to be > > installed at the context root of root (/) and use different virtual > > hosts to control which app it goes to (dev.boiseinc.com and > > test.boiseinc.com). This all works fine except I don't know how to > > tell magnolia to look at one repository for one (dev) and a different > > repository for the other (test). We're running Magnolia 3.5.3 on Suse > > Linux with WebSphere 6.1.0.13. The dev and test instances run in > > different app servers (different JVMs). > > If you are running in completely different appservers, this shouldn't > be an issue. What persistence manager are you using? The default > derby persistence manager will set up its files inside of the webapp/ > repositories directory and build its files there. You could even run > both instances on the same app server and the repositories wouldn't > touch each other (I have mine set up this way) > > On one of my soon-to-be-in-production machines, I have both the > author and the public instance running inside the same Tomcat - I use > apache and mod_jk to act as a front and proxy the tomcat / > magnoliaAuthor and /magnoliaPublic to different domain names. I am > going to adjust it so that I use mySQL as my persistence manager on > them, but as of now they are running off of Derby. I didn't have to > adjust any files. > > If you are changing the name of the webapp from magnoliaAuthor or > magnoliaPublic to something else, you will want to look at the > properties files that describe how things get bootstrapped. > Basically, the .war file can contain tons of different configuration > files, and can look at the name of itself when it is initially > bootsrapping itself and from there load up whatever files it is > configured to load. The default name "magnoliaAuthor.war" will create > an author instance with superuser / superuser login - and the default > "magnoliaPublic.war" will create a public instance. > > Unless there is a very good reason that you already have multiple > tomcats installed for this configuration, I would recommend > consolidating it to one. Dev and Test can coexist just fine, I would > presume. > > Oh, and the mod_jk setup I have was kind of a pain-in-the-butt and I > would recommend using mod_proxy_ajp and proxypass instead - since > that is what I am going to be switching to when I get a chance. ( I > have run into a problem with mod_jk where occasionally pages on my > public instance will dump gibberish to the browser when they are hit > - it is almost as if the binary ajp is just getting passed straight- > through instead of being decoded and passed through Apache... which > is annoying to say the least.) > > Hope that helps. > > Ryan > > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
