Enterprise Edition on Linux
These instructions rely on the Enterprise installer application. If you need to do fast installations repeatedly, download the Tomcat and Magnolia CMS bundle instead and follow the Community Edition installation steps. You still need to register for a license key.
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.
Register for license key
Magnolia CMS Enterprise Edition is available for a free 60-day trial. To get a license key you must register.
- Go to http://registration.magnolia-cms.com/.
- Fill the form with your details. A license key will be sent to the email address you provide.
Download, install and run Magnolia CMS
Download
- Go to http://files.magnolia-cms.com/.
- Click the latest Magnolia CMS version.
- Download the Installer (Installer bundle with Tomcat) JAR file. The file name depends on the release, for example
magnolia-enterprise-installer-4.2.3.jar.
Install
- Run the installer JAR file you downloaded:
java -jar magnolia-enterprise-installer-4.2.3.jar - Select an installation language and click OK.
- Click Next.
- Click Next.
- Accept the license terms and click Next.
- Optional: Configure Magnolia CMS to use a Java Runtime Environment other than your default JRE. The default is usually fine. Click Next.
- Click Next.
- Select the installation path. Default is
/home/userAccount/MagnoliaEnterpriseEdition. If you are installing Magnolia CMS for personal use extract to the default or equivalent directory. If you are installing a production server extract to/usr/localor/opt. - Click Next. Installation will start.
- Click Next.
- Clear the Start menu and desktop shortcuts. They only work in Windows. Click Next.
- Click Done.
/home/
userAccount/
MagnoliaEnterpriseEdition/
add-ons/
apache-tomcat/
bin/
common/
conf/
logs/
server
shared/
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
Use ./magnolia_control.sh start && tail -f ../logs/catalina.out to start Magnolia.
The first part of the command ./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. 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 use ./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.
Register
Now you need the license key that was sent to your email address. Copy only the key string part from the message. Fill in the same email address that you used when registering.
Before you paste the license key make sure that it is a continuous string of characters with no spaces or line breaks. If you have any problems you can paste the key to Notepad or another plain text editor first to strip out any formatting.
Log in to author instance
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.
The AdminCentral is displayed.