Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Magnolia Community Edition is distributed free-of-charge and without any warranty under the terms of the GNU General Public License (version 3), a license that permits you to redistribute and modify the software under certain terms and conditions. It is important that you read the license to understand your rights and obligations.
Installing Magnolia on Solaris works the same as . For an already-installed application server, works the same way too. If you need to install the Tomcat-Magnolia bundle, edit the
/apache-tomcat/bin/catalina.sh file and change the shell from
/bin/bash. The shell is the first line in the file.
Magnolia needs a Java Runtime Environment (JRE). Most likely you already have it on your Linux computer. Use the Java Tester to check.
If you don't have JRE, download and install it from http://java.sun.com/javase/downloads/index.jsp. Installation directory varies from one Linux system to another. For example on Ubuntu Linux 10 the OpenJDK Runtime Environment is installed in
/usr/lib/jvm/java-6-openjdk/jre by default.
Download Magnolia Tomcat bundle .tar.gz file from http://sourceforge.net/projects/magnolia/files/. File name depends on the release, for example
magnolia-tomcat-bundle-4.3.2-tomcat-bundle.tar.gz. Get the latest.
Extract the zip to a directory on your computer. If you are installing Magnolia for personal use extract to
/usr/home/yourAccount or equivalent directory. If you are installing a production server extract to
/opt. Regular user accounts may not have permissions to extract files into a target directory such as
/opt. If this is the case extract the zip in the folder where you downloaded it, then open a terminal window and move the extracted folder using
sudo mv magnolia-4.3.2. The
sudo command will execute the
mv (move) command as superuser, prompting you for a password.
The extracted folder structure looks like this:
./magnolia_control.sh start && tail -f ../logs/catalina.out
The first part of the startup command
./magnolia_control.sh start launches Magnolia. The second part
&& tail -f ../logs/catalina.out displays startup messages written to
/apache-tomcat/logs/catalina.out log file. This makes it easier to troubleshoot startup errors.
Magnolia reports startup information. If startup fails, look for the reason in the report. See Troubleshooting to resolve the issues. In a successful startup the last line reads:
INFO: Server startup in 12345 ms
To stop Magnolia, type
Repeat the update on the public instance.
The AdminCentral is displayed.