Installing Magnolia

Installing the webapp in your container

Deploying a war file in an application server is a procedure which is dependent on the given application server, and we expect you already know how to do this. If you don't, we highly recommend you use the standalone distributions ("bundles").

If the you deploy the webapp with the name is "magnoliaPublic" (i.e you renamed the war file to magnoliaPublic.war for instance), it will automatically be deployed as a public instance, otherwise it will be deployed as an author instance. This little magic is done by using the webapp folder name to determine what configuration file to use. More details can be found in the cookbook.

See the container specific notes page for extra steps that might be needed with your container of choice.

Installing a standalone Magnolia distribution

Using the installer should hopefully be straightforward (after its download, Windows users might have to rename the file and make sure the extension is .jar), and we don't expect unpacking a bundle should pose any issue either.

Starting Magnolia

After unpacking or installing, you will probably want to start Magnolia !

Unix (all flavors), OSX, ...

Open a shell or terminal, and make sure you Java environment is set properly (this is usually done through setting the JAVA_HOME, although this is not necessary on OSX, for instance). You should then use the provided magnolia_control.sh script to start and stop Tomcat. If you're new to Magnolia, it might be a good idea to keep an eye on the log files for a little while, at least until your system is installed.

export JAVA_HOME=YOUR_JDK_HOME
cd INSTALL_DIRECTORY/apache-tomcat-5.5.25/bin
./magnolia_control.sh start && tail -f ../logs/catalina.out

To stop Magnolia, you can use the same script, with the stop parameter: 

./magnolia_control.sh stop && tail -f ../logs/catalina.out

If you used the installer, the magnolia_control.sh script has been modified to use the JDK you selected when installing, so you don't need to explicitly set the JAVA_HOME environment variable.

Microsoft Windows

Open a command prompt, and similarly to what you'd do on Unix, do:

set JAVA_HOME=YOUR_JDK_HOME
cd "C:\Program Files\MagnoliaEnterpriseEdition\apache-tomcat-5.5.25\bin\"
magnolia_control.bat start

To stop Magnolia, you can use the same script, with the stop parameter: 

magnolia_control.bat stop

If you used the installer, the magnolia_control.bat script has been modified to use the JDK you selected when installing, so you don't need to explicitly set the JAVA_HOME environment variable.

Alternatively, you can use the shortcuts which have been created by the installer, which have a similar behaviour.

Accessing Magnolia

If you used a bundle or the installer, we customized Tomcat's default root page to give you links to the author and public instances. Try http://localhost:8080/, or the appropriate host name if you didn't install Magnolia on your own computer. You will have to follow the installation wizard on both instances before using Magnolia.

If you installed the webapp in your own container, you probably know how to reach it by now. You'll also have to follow the installation wizard on all your instances. If you need to access the AdminCentral on a public instance, simply suffix the webapp's url by .magnolia, i.e. http://localhost:8080/magnoliaPublic/.magnolia