Community Edition on Solaris
Magnolia CMS Community Edition and STK are GPL v3 licensed. By downloading and installing either package, you agree to the conditions of the license.
Installing Magnolia CMS on Solaris works the same as on Linux. For an already-installed application server, deploying the WAR file 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/sh to #!/bin/bash. The shell is the first line in the file.
- Check the prerequisites
- Download, install and run Magnolia CMS
- Run the Web update
- Log in to author instance
- Troubleshooting
Check the prerequisites
Java Runtime Environment (JRE)
Magnolia CMS 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, install and run Magnolia CMS
Download
Download Magnolia CMS 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.
Install
Extract the zip to a directory on your computer. If you are installing Magnolia CMS for personal use extract to /usr/home/yourAccount or equivalent directory. If you are installing a production server extract to /usr/local or /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-4.2.3
add-ons
apache-tomcat
bin
conf
logs
webapps
MagnoliaAuthor
MagnoliaPublic
ROOT
Run
- Open a terminal window.
- Go to the Magnolia CMS installation directory:
cd /home/userAccount/magnolia-4.2.3/apache-tomcat/bin
Your path may be different. - Start Magnolia CMS:
./magnolia_control.sh start && tail -f ../logs/catalina.out
./magnolia_control.sh start launches Magnolia CMS. 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 CMS 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 CMS, type ./magnolia_control.sh stop.
Run the Web update
- Open a browser and go to
http://localhost:8080. - Click the Run the Web update on the author instance link.
A list of modules that need updating is displayed. - Click Start install.
The modules are updated. - Click Start up Magnolia.
- Open a browser and go to
http://localhost:8080. - Click the Run the Web update on the public instance link.
A list of modules that need updating is displayed. - Click Start install.
The modules are updated. - Click Start up Magnolia.
Log in to author instance
- Open a browser and go to
http://localhost:8080/magnoliaAuthor/.magnolia. - At the login page, sign in with:
- Username:
superuser - Password:
superuser

Superuser is a system administration account that has permission to every function. End users should not use this account. See Users for instructions how to create new user accounts and Default users for accounts that you can use for testing right away.